View previous topic :: View next topic |
Author |
Message |
Vreddy Beginner
Joined: 03 Feb 2003 Posts: 12 Topics: 5
|
Posted: Fri Apr 23, 2004 9:43 am Post subject: Stored Procedrue calling a cobol program having SQL statemen |
|
|
I am getting -927 when a stored procedure calls a cobol program having SQL's
I saw the meaning of -927 it says language interface. I link edited cobol program with DSNELI and Stored procedure as DSNRLI. Is there any problem with that. Please let me know the right way of link editing or compiling.
Thanks
Vreddy _________________ Thanks
Vreddy |
|
Back to top |
|
|
SureshKumar Intermediate
Joined: 23 Jan 2003 Posts: 211 Topics: 21
|
Posted: Fri Apr 23, 2004 10:26 am Post subject: |
|
|
Vreddy,
Where is the SP being invoked from ? DDF or MVS |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
|
Posted: Fri Apr 23, 2004 10:28 am Post subject: |
|
|
Vreddy,
Try to be consitent and link-edit all your modules using DSNELI
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
Vreddy Beginner
Joined: 03 Feb 2003 Posts: 12 Topics: 5
|
Posted: Fri Apr 23, 2004 10:42 am Post subject: |
|
|
Kosulu,
do we need to link edit stored procedure also as DSNELI. Our shop is using standard JCL for stored procedures and it it is link editing to DSNRLI.
I am link editing db2-cobol as DSNELI and Stored procedure as DSNRLI.
question.
Can a stored procedure call a db2-cobol program. if so how to link edit and make it work.
Thanks
Vreddy _________________ Thanks
Vreddy |
|
Back to top |
|
|
Manas Biswal Intermediate
Joined: 29 Nov 2002 Posts: 382 Topics: 27 Location: Chennai, India
|
Posted: Mon Apr 26, 2004 1:28 pm Post subject: |
|
|
I have never really called an external program from a stored procedure but the manual says that it can be done. If you have linkedited you SP with DSNRLI, then that means you are using WLM managed address space for your SP. You can try link editing your called COBOL program also with DSNRLI and see if that works. I think the load library of your called COBOL program needs to be concatenated to the STEPLIB of the job running the WLM established Stored procedure address space.
And finally check whether the package of your called COBOL program is in the same collection as the package for your SP. If it is not so, then you probably have to invoke a SET CURRENT PACKAGESET before calling the COBOL program.
Regards,
Manas |
|
Back to top |
|
|
|
|