Integrated and separate CICS and Db2 steps

If your COBOL or PL/I programs use CICS® or Db2®, you can indicate whether to use the integrated CICS translator or Db2 coprocessor or a separate step. Settings on the COBOL and PL/I Procedures and Steps window control how JCL for these procedures is generated.

With COBOL programs

If you select DB2 on the Runtime Environments window and the ELAXFCOP procedure is disabled, then ELAXFCOC is generated with PARMs that tell the compiler to use the integrated Db2 coprocessor. However, if you select Db2 and the ELAXFCOP procedure is enabled, then ELAXFCOC is generated with PARMs that tell the compiler not to use the integrated Db2 coprocessor. Instead, it uses the separate step (ELAXFCOP). In either case, the compiler is started with ELAXFCOC, but whether it uses the integrated Db2 coprocessor depends on the PARMs passed.

If you select CICS on the Runtime Environments window and the ELAXFCOT procedure is disabled, then ELAXFCOC is generated with PARMs that tell the compiler to use the integrated CICS coprocessor. However, if you select CICS and the ELAXFCOT procedure is enabled, then ELAXFCOC is generated with PARMs that tell the compiler not to use the integrated CICS coprocessor. Instead, it uses the separate step (ELAXFCOT). In either case, the compiler is started with ELAXFCOC, but whether it uses the integrated CICS coprocessor depends on the PARMs passed.

With PL/I programs

If you select Db2 on the Runtime Environments window and the ELAXFPLP procedure is disabled, then ELAXFPL1 is generated with PARMs that tell the compiler to use the integrated Db2 coprocessor. However, if you select Db2 and the ELAXFPLP procedure is enabled, then ELAXFPL1 is generated with PARMs that tell the compiler not to use the integrated Db2 coprocessor. Instead, it uses the separate step (ELAXFPLP). In either case, the compiler is started with ELAXFPL1, but whether it uses the integrated Db2 coprocessor depends on the PARMs passed.

If you select CICS on the Runtime Environments window and the ELAXFPLT procedure is disabled, then ELAXFPL1 is generated with PARMs that tell the compiler to use the integrated CICS coprocessor. However, if you select CICS and the ELAXFPLT procedure is enabled, then ELAXFPL1 is generated with PARMs that tell the compiler not to use the integrated CICS coprocessor. Instead, it uses the separate step (ELAXFPLT). In either case, the compiler is started with ELAXFPL1, but whether it uses the integrated CICS coprocessor depends on the PARMs passed.