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:
Figure 22 shows a sample job that you can use or modify to start a 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
//STEPLIB DD DSN=CICSTS31.CICS.EXCI.LOADLIB,DISP=SHR
// DD DSN=CICSTS31.CICS.SDFHEXCI,DSIP=SHR
//SYSPRINT DD SYSOUT=A
//SYSMDUMP DD DSN=SYS1.SYSMDP00,VOL=SER=volid,SPACE=(CYL,(1,1)),
DISP=OLD,UNIT=3390
See EXCI security for information about security when using the external CICS interface.
CICS provides seven procedures to enable you to translate, compile, and link-edit your client programs. Four of these are for use with specific language compilers or assembler, the other three being for use with Language Environment®. These procedures, with the four language-specific procedures shown first, are:
To ensure that the EXCI stub is included with your client program, all these procedures include a step, COPYLINK, that unloads the stub into a temporary data set defined with a block length suitable for the linkage-editor. This temporary data set is then concatenated with the temporary data set containing your object program on the SYSLIN DD statement in the LKED step.
These procedures are supplied in the CICSTS31.CICS.SDFHPROC library. You are recommended to copy these to SYS1.PROCLIB or another suitable procedure library.