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. When writing the JCL for your client program, you should note these requirements.
Requirements
- 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
CICSTS54
.CICS.SDFHEXCI, which
contains the following:
DFH$ATCC
DFH$AXCC
DFH£AXNC
DFH£DXVC
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.
If the EXCI client program uses channels and containers, instead of
a COMMAREA, to pass
data to
CICS
, the
MEMLIMIT
parameter must be specified as container data is stored in 64-bit
storage above the bar. Storage for containers cannot exceed 5% of
the
MEMLIMIT
value.

- Include a SYSPRINT or equivalent DD statement for any output from the client program.
Sample job for starting an EXCI client program
Figure 1 shows a sample job that you can use or modify to start a client program.
Figure 1. Sample job for starting an EXCI client program
//EXCI JOB (accounting_information),CLASS=A,TIME=1440,
// USER=userid,PASSWORD=pswd,REGION=100M
//*===============================================================*
//* JCL to execute an external CICS interface client program *
//*===============================================================*
//
EXEC PGM=pgmname,REGION=nnM,MEMLIMIT=nnG
//STEPLIB DD DSN=
CICSTS54
.CICS.EXCI.LOADLIB,DISP=SHR
// DD DSN=
CICSTS54
.CICS.SDFHEXCI,DISP=SHR
//SYSPRINT DD SYSOUT=A
//SYSMDUMP DD DSN=SYS1.SYSMDP00,VOL=SER=volid,SPACE=(CYL,(1,1)),
DISP=OLD,UNIT=3390
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 EXCI security for information about security when using the external CICS interface.
- See Setting up the EXCI sample programs 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.