Found the problem:
I needed to specify PACKAGE PATH in the CREATE PROCEDURE.
On Tue, 7 Feb 2023 15:21:07 -0600 Mike Bell wrote:
:>start from the basics - I assume the plan name is DSNREXX. you can
:>1. bind the DSNREXX plan with your collection and it will find it in the
:>search list
:>2; SET
start from the basics - I assume the plan name is DSNREXX. you can
1. bind the DSNREXX plan with your collection and it will find it in the
search list
2; SET CURRENT PACKAGESET = 'your collection'
I haven't played in this area but those are the basics.
Mike
On Tue, Feb 7, 2023 at 2:25 PM Binyamin
On Tue, 7 Feb 2023 19:36:12 + Sri h Kolusu wrote:
:>>> The -805 is occurring for the SQL statement (a SELECT INTO) in the SP.
:>Try the steps listed under "Problem determination" in the link below
:>https://www.ibm.com/docs/en/db2-for-zos/11?topic=codes-805
Thanks. The only possibility is
>> The -805 is occurring for the SQL statement (a SELECT INTO) in the SP.
Binyamin,
Try the steps listed under "Problem determination" in the link below
https://www.ibm.com/docs/en/db2-for-zos/11?topic=codes-805
Thanks,
Kolusu
---
On Tue, 7 Feb 2023 09:48:28 -0600 Mike Bell wrote:
:>you forgot the bind step - when you created the stored procedure the JCL
:>should have had a ddname for DBRMLIB usually a pds with a member name the
:>same as your stored procedure. I don't have a sample bind handy but the
:>manual has several.
you forgot the bind step - when you created the stored procedure the JCL
should have had a ddname for DBRMLIB usually a pds with a member name the
same as your stored procedure. I don't have a sample bind handy but the
manual has several.
Mike
On Tue, Feb 7, 2023 at 5:40 AM Binyamin Dissen
wrote
I have written a COBOL Stored Procedure and have successfully invoked it from
REXX.
But when I add an SQL statement to the SP, the SQL statement is getting -805.
Is there a requirement to add the package(s) of external SPs to the PLAN of
the invoking program? Seems like an onerous requirement.
