Hello learned and gentle folks,
I am trying to simplify the compile JCL and use the "CICS" compiler option ... unfortunately I get a diagnostic at compiletime:
IGYOS0230-S The "CICS" compiler option was in effect, but the compiler was unable to load the CICS integrated translator services module. All "EXEC CICS" statements were discarded.
Anybody: what do I do wrong?
This topic has been locked.
4 replies Latest Post - 2012-12-24T15:07:57Z by SystemAdmin
Pinned topic cannot use integrated CICS processor with COBOL V4R2 - message: IGYOS0230-S
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-24T15:07:57Z at 2012-12-24T15:07:57Z by SystemAdmin
Re: cannot use integrated CICS processor with COBOL V4R2 - message: IGYOS0230-S2012-12-19T09:58:04Z in response to SystemAdminHello,
Look at CICS runtime. If CICS runtime is not in linklist, add it to STEPLIB :
//COB EXEC PGM=IGYCRCTL,REGION=4M,
// PARM='OPTFILE' * SYSOPTF
//STEPLIB DD DISP=SHR,DSN=SYS1.SIGYCOMP * COBOL
// DD DISP=SHR,DSN=G$PRODUI.&DB2V..SDSNEXIT * DSNHDECP
// DD DISP=SHR,DSN=G$LINK.&DB2V..SDSNLOAD * CO-PRO DB2
// DD DISP=SHR,DSN=G$LINK.&CICSV..SDFHLOAD * CO-PRO CICS
//SYSIN DD DISP=SHR,DSN=&PREFIX..SRCELIB(&P.) * SOURCE COBOL
//SYSLIB DD DISP=SHR,DSN=&PREFIX..SRCELIB * COPY/INCLUDE
// DD DISP=SHR,DSN=G$PRODUI.&CICSV..SDFHCOB *
// DD DISP=SHR,DSN=G$PRODUI.&CICSV..SDFHMAC *
//SYSOPTF DD DISP=SHR,DSN=&PREFIX..PARMLIB(&COBDEF.) * OPTIONS DEFAUT
// DD DISP=SHR,DSN=&PREFIX..PARMLIB(&COBOPT.) * OPTIONS SPECIF
Note : CICS coprocessor does'nt support EXCI interface :-(
Re: cannot use integrated CICS processor with COBOL V4R2 - message: IGYOS0230-S2012-12-19T13:26:44Z in response to SystemAdminThank you Denis ... strange one: I moved the SDFHLOAD card from the JOBLIB concat to STEPLIB and now it works!?!? What up with that?
brataj 100000816340 PostsACCEPTED ANSWER
Re: cannot use integrated CICS processor with COBOL V4R2 - message: IGYOS0230-S2012-12-19T14:30:39Z in response to SystemAdminNot having used JOBLIBs much myself, I was surprised to discover
If you include a STEPLIB DD statement for a job step and a JOBLIB DD statement for the entire job, the system first searches the step library and then the system library for the requested program. The system ignores the job library for a step that has a STEPLIB DD statement.