Rational Developer for System z

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. This topic explains the settings on the COBOL and PL/I Procedures and Steps window that 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 will be 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 will be generated with PARMs that tell the compiler not to use the integrated DB2 coprocessor. Instead, it will use the separate step (ELAXFCOP). In either case, the compiler is invoked using ELAXFCOC, but whether or not 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 will be 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 will be generated with PARMs that tell the compiler not to use the integrated CICS coprocessor. Instead, it will use the separate step (ELAXFCOT). In either case, the compiler is invoked using ELAXFCOC, but whether or not 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 will be 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 will be generated with PARMs that tell the compiler not to use the integrated DB2 coprocessor. Instead, it will use the separate step (ELAXFPLP). In either case, the compiler is invoked using ELAXFPL1, but whether or not 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 will be 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 will be generated with PARMs that tell the compiler not to use the integrated CICS coprocessor. Instead, it will use the separate step (ELAXFPLT). In either case, the compiler is invoked using ELAXFPL1, but whether or not it uses the integrated CICS coprocessor depends on the PARMs passed.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)