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:

Figure 22 shows a sample job that you can use or modify to start a client program.

Figure 22. 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
//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

Notes:
  1. The job user ID, specified on the USER parameter, must be defined to RACF® , or an equivalent external security manager (ESM).
  2. 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.

  3. 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.

CICS-supplied procedures for the EXCI

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:

DFHEXTAL
The assembler procedure for assembler versions of client programs
DFHYXTEL
The procedure for C++ versions of client programs running under Language Environment
DFHYXTDL
The procedure for C versions of client programs running under Language Environment
DFHYXTPL
The procedure for PL/I versions of client programs running under Language Environment
DFHYXTVL
The procedure for COBOL versions of client programs running under Language Environment.

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.

Related concepts
Introduction to the external CICS interface
Related tasks
The EXCI CALL interface
The EXCI EXEC CICS interface
EXCI programming considerations
Using EXCI sample application programs
[[ Contents Previous Page | Next Page Index ]]