I am facing a strange issue. I get a S0C4 abend sometimes (not regularly) when I execute my DB2 COBOL Stored Procedure. Please find the details below:
1. The SP takes XML as Input into a CLOB variable. The I/P parm for the field is as below:
IN SP_IP_PARM CLOB(60000) CCSID EBCDIC FOR SBCS DATA
Though I am skeptical, I am still changing that because I am calling no other COBOL module from ym stored procedure. However, I do see that calls are being made some internal DB2 modules and hence maybe you're right. I will wait for 24 hours to see if there is any problem even after that.
A 24 bit program can call a 31 bit program with no problem.
A 31 bit program can call a 24 bit program, but will usually have problems.
If the called program is 24 bit, then compile the calling program with AMODE(24).
Every program that runs in MVS/ESA is assigned two attributes,
an AMODE (addressing mode) and an RMODE (residency mode):
AMODE Specifies the addressing mode in which the program is
designed to receive control. Generally, the program is also designed to run
in that mode, although a program can switch modes and can have different
AMODE attributes for different entry points within a program module.
MVS/ESA uses a program's AMODE attribute to determine whether a
program invoked using ATTACH, LINK, or XCTL is to receive control in
24-bit or 31-bit addressing mode.
RMODE Indicates where the program can reside in virtual storage.
MVS/ESA uses the RMODE attribute to determine whether a program
must be loaded into virtual storage below 16 megabytes, or can reside
anywhere in virtual storage (above or below 16 megabytes).