Steve Sullivan
New User
Joined: 01 Feb 2013
Posts: 2
Location: USA
|
|
|
|
We have a CICS transaction which executes a CICS COBOL program. This program dynamically calls several IBM C load modules.
Each of these load modules mallocs storage that we expect to own for the duration of the transaction.
It appears that the storage is being reused as it has been over-written with STKL and STKU entries.
We have gotten around this problem by replacing mallocs with CICS GETMAINS.
We did not have this problem when our C load modules were built with SAS C and statically linked with our COBOL program.
We're wondering whether there are compile or linking options relevant to this problem that we have overlooked.
The CICS translator parameters for the COBOL program are: COBOL3,NODEBUG,NOSOURCE,SP
The compile parameters for the COBOL program are: NODYN,LIB,OBJ,RENT,RES,APOST,MAP,XREF,LIST,SSRANGE.
The link parameters for the COBOL program are: LIST,XREF,AMODE(31),RMODE(ANY),RENT
The compile parameters for the IBM C programs are: SO,XR,EXPMAC,NOMAR,NOSEQ,LONGNAME,SSCOMM,RENT,
GONUMBER,LIST,OFFSET,OPTIMIZE(2),INLRPT,CICS(SP,DEBUG)
The pre-link parameters for the IBM C programs are: NONCAL, NOMEMORY, ER, DUP, MAP,NOOMVS NOUPCASE DYNAM
Lastly, the link parameters for the IBM C programs are: LIST,LET.
Thanks in advance for your responses. |
|
