You can use CICS® Transaction
Server for OS/390® to provide
translation support for EXEC CICS statements. Using
separate CICS translation causes CICS translation to occur as a
separate step from the compilation step. The translation results are
handed off to your compiler.
About this task
It is recommended
that you use integrated CICS translation
whenever possible, but you may need to use separate CICS translation under the following circumstances:
- You prefer to use your own tested and stable JCL to compile your
code
- Your compiler does not support integrated CICS translation
Note that in order to perform syntax checks on your code,
you must use integrated CICS translation. The
syntax check feature does not support separate CICS translation. To enable separate CICS translation support for PL/I
using CICS Transaction Server
for OS/390, follow these
steps:
Procedure
- Open the Properties for the resource.
- Open the property group editor to the PL/I Settings page.
- Click on the Runtime Environments.
- Select the CICS check box. This activates the drop-down list beside the check box.
- From the drop-down list, select the level of CICS Transaction Server installed on the remote
system.
- Click Procedures and Steps.
- Enable the translation procedure by selecting ELAXFPLT and
clicking Enable Procedure.
- Click + next to ELAXFPLT, select PLITRAN, and
click Edit. The CICS Translator Step Options window opens.
- Complete the following fields and save the settings:
- Options
- Options to be set for your CICS translator.
Leave this field blank to use the default set of options.
- SYSLIB
- The location of your system library (SYSLIB). You need to specify
this so that your CICS translator
can find your include libraries.
- Click Link Options in the menu on
the left in the Properties window. The linker properties
pane opens on the right.
- Click + next to ELAXFLNK, select LINK, and
click Edit step. The Link
Step Options window opens.
- Complete the following fields and click OK:
- Link Libraries
- Libraries to link your code with. For example, you might specify
CICSVS.TS230.CICS.SDFHLOAD and CEEV2R10.SCEELKED in this field.
- Use specified link instructions
- Select this option and fill in the field below it with the following
link edit control cards:
INCLUDE SYSLIB(DFHELII)
INCLUDE SYSLIB(EQUDCCXT)
ORDER CEESTART
- Load Module Location
- The data set where your load module should be placed after the
link step. For example, you might set this to the DFHRPL concatenation
of your CICS region.
- Click Apply.
What to do next
You can now execute remote syntax checks and perform remote
builds on your configured resource. You can specify additional include
libraries, compiler options, and JCL in the compiler properties pane
by clicking + to expand
ELAXFPLT, clicking
PLITRAN,
and then clicking
Edit step.