Joined: 14 Jan 2008 Posts: 2504 Location: Atlanta, Georgia, USA
From the manual -
"If the dynamic COBOL CALL fails, CICS abend handling is not invoked, and you may get a COBOL abend code (1013)." A 1013 is generated by LE (Language Environment).
Are you CALLING or LINKING to the program?
If you're using COBOL, make sure you're using compiler option "NODYNAM", as "DYNAM" is never correct for a CICS/COBOL program and could cause "Unpredictable Results".
In a COBOL "CALL USING" statement, you must provide addressability to the EIB and COMMAREA, so you must specify DFHEIBLK DFHCOMMAREA as the first two parms, followed by whatever other necessary required parms.
for the compile In the calling CICS program, we added an INCLUDE to another non-CICS COBOL batch program to the linkedit step to make it static. the batch is program is called with CALL USING. THis is working.
the batch program merely adds a century indicator to a date field.
Is this new code, or just being relinked with the "new" Binder? Why else do you feel the Binder is the issue? This is testing for the first time with your new method of compile/link or it is already working elsewhere?
You mention "another" batch program, implying there is a "first" batch program somewhere. Can you explain clearly?
Can you show your linkedit/bind control cards and explain what you mean about the INCLUDE? Did you check messages on the output?