Using the integrated CICS translator

The language compilers provide various procedures that you can use with the integrated CICS® translator. They are documented in the Programming Guides for Enterprise COBOL for z/OS® , z/OS XL C/C++ , and for Enterprise PL/I for z/OS.

About this task

The procedure that you use needs to have CICSTS56.CICS .SDFHLOAD added to the STEPLIB concatenation for the compilation step and the link-edit step should include the interface module DFHELII at the start of the step.

To use the integrated CICS translator for PL/I, you must specify the compiler option SYSTEM(CICS).

To use the integrated CICS translator for COBOL, the compiler options CICS, NODYNAM, and RENT must be in effect. NODYNAM is not a restriction specific to the integrated translator. DYNAM is not supported for code that is separately translated and compiled. Do not use SIZE(MAX), because storage must remain in the user region for integrated CICS translator services. Instead, use a value such as SIZE(4000K), which should work for most programs.

Note: The compiler LIB option is no longer required for COBOL 5 and later, and has been removed. For earlier versions of COBOL, this option must be manually reinstated.

To use the integrated CICS translator for C and C++, use the CICS option.

If you are running DB2® Version 7 or later and preparing a COBOL program using a compiler with integrated translator, the compiler also provides an SQL statement coprocessor (which produces a DBRM), so you do not need to use a separate Db2® precompiler. See CICS Db2 program preparation and Programming for Db2 for z/OS in Db2 for z/OS product documentation for more information on using the SQL statement coprocessor.