Accessing VSAM in a DB2 Stored Procedure

Bernie Polley

Accessing VSAM in a DB2 Stored Procedure
We have a stored procedure written in COBOL for OS390 that reads a VSAM =
file. The stored procedure abends with a SYSTEM COMPLETION CODE=3D0C4 =
REASON CODE=3D00000004 in module IGZCPAC. This occurs as soon as the sp =
opens the VSAM file. We have the JCL DD statement in the stored procedures=
address space JCL procedure. Does anyone have any clues?

Any help would be greatly appreciated.

Bernard Polley
Johns Hopkins University
[login to unmask email]



Piontkowski Michael ML

Re: Accessing VSAM in a DB2 Stored Procedure
(in response to Bernie Polley)
Ensure the DB2 Stored Procedure JCL proc is using
the correct Language Environment (LE) run time library
*.SCEERUN - either through the link list or a steplib.

The LE runtime version must support the COBOL for
OS/390 version.


Mike Piontkowski
Voice/Fax: 302.886.4612
mailto:[login to unmask email]

> ----------
> From: Bernie Polley[SMTP:[login to unmask email]
> Sent: Wednesday, December 29, 1999 12:08 PM
> To: [login to unmask email]
> Subject: [DB2-L] Accessing VSAM in a DB2 Stored Procedure
>
> We have a stored procedure written in COBOL for OS390 that reads a VSAM =
> file. The stored procedure abends with a SYSTEM COMPLETION CODE=3D0C4 =
> REASON CODE=3D00000004 in module IGZCPAC. This occurs as soon as the sp =
> opens the VSAM file. We have the JCL DD statement in the stored
> procedures=
> address space JCL procedure. Does anyone have any clues?
>
> Any help would be greatly appreciated.
>
> Bernard Polley
> Johns Hopkins University
> [login to unmask email]
>
>
>
> http://www.ryci.com/db2-l. The owners of the list can be reached at
> [login to unmask email]
>