Job control language to run an EXCI client program
An EXCI client program runs in an MVS™ address space, for example, as a batch job.
Note the following requirements when writing the JCL
for your client program:
- Include in the STEPLIB concatenation those libraries that contain
the CICS-supplied external CICS® interface modules and also
the client program. The external CICS interface
modules are supplied in CICSTS53.CICS.SDFHEXCI,
which contains the following: DFH$AXCC
DFHMEBMX
DFHMET4E
DFHXCEIX
DFHXCIE (alias of DFHXCSTB)
DFHXCIS (alias of DFHXCTSB)
DFHXCOPT
DFHXCPRX
DFHXCSTB
DFHXCTRA
DFHXCURM - You are recommended to include a DD statement for SYSMDUMP. The external CICS interface uses SYSMDUMP for some error conditions.
- The REGION parameter must specify a large enough region size to allow for the size of the internal trace table specified by the TRACESZE parameter in the DFHXCOPT options table.
- Include a SYSPRINT or equivalent DD statement for any output from the client program.
Figure 1 shows a sample job
that you can use or modify to start a client program.
Note:
- The job user ID, specified on the USER parameter, must be defined to RACF® , or an equivalent external security manager (ESM).
- In addition to being used for job step initiation security, the
job user ID is also used for MRO logon and bind-time security checking.
See Security for EXCI for information about security when using the external CICS interface.
- See Installing the EXCI sample definitions for information about modifying the sample connection definitions before you run the sample application programs in an environment that does not have RACF, or an equivalent external security manager (ESM), installed and active.