Migration planning for the integrated translator

To install application programs into CICS® libraries, you can use one of the CICS-supplied procedures for use with the integrated translator. Start of changeNote that the procedures, DFHZITCL (for COBOL), DFHZITPL (for PL/I), and DFHZITDL, DFHZITEL, DFHZITFL, and DFHZITGL (for XL C/C++), include the CICS load library SDFHLOAD in STEPLIB, which is necessary for the compilers to load the translation tables.End of change Also, if you are using the PL/I procedure or XL C/C++ procedures, the SYSLMOD DD statement in the binder step must refer to a PDSE (not a PDS as for the older PL/I compilers). See Translator support for high-level languages for a list of all the procedures supplied for assembling and compiling application programs.

To use the CICS-supplied procedures to invoke the integrated translator, add the required language options to indicate that you want the compiler to invoke the translator:

Notes:
  1. If you specify CICS translator options for the integrated translator in the PARM string, you need double apostrophes as shown in this example. If, however, you specify the options in your source program, you need single apostrophes (for example, you might have CBL CICS('COBOL3,SP') APOST as the CBL statement in your source program.
  2. The COBOL compiler recognizes only the keyword CICS for defining translator options, not the alternative options XOPT or XOPTS as in the case of the stand-alone translator supplied with CICS TS.
  3. If the CICS TS 1.3 translator is set up to run with a CICS TS 3.1 LPALIB, Error Return Code 16 will be produced.

    CICS TS 3.1 uses AMODE(31) settings, while CICS TS 1.3 uses AMODE(24). If you intend to run a CICS TS 1.3 translator, you must add to your STEPLIB, an SDFHLOAD that contains the modules DFHEITAB and DFHEITBS from CICS TS 1.3. This addition must be placed prior to the CICS TS 3.1 SDFHLOAD. This will allow the CICS TS 1.3 translator to operate in a CICS TS 3.1 region.

[[ Contents Previous Page | Next Page Index ]]