Link editing your program

The CICS®/ESA translator inserts a call to the CICSPlex® SM EXEC interface stub program. The stub entry name is not the name of an object or load module. Since CICSPlex SM API programs can run in a variety of environments, the stub reference must be resolved to a module consistent with the intended usage. This resolution is performed at link-edit time using the INCLUDE linkage editor control statement.

You must link edit all program load modules with the correct CICSPlex SM stub module for the environment where the program will run. To do this, specify one of the following stub modules in the INCLUDE statement:

EYU9AMSI
For CICS/ESA and CICS TS programs. EYU9AMSI is supplied in the CICSTS31.CPSM.SEYULOAD library.
EYU9ABSI
For batch, TSO, or NetView® programs. EYU9ABSI is supplied in the CICSTS31.CPSM.SEYUAUTH library.

Each of these stub modules contains the appropriate entrypoint identifier. The services provided by the entrypoint are unique to the type of execution environment.

Note:
You should not attempt to run a program identified as a CICS program in a batch environment. Likewise, batch programs are not suitable for running under CICS.

You can use your CICS link-edit JCL as a model for link editing CICSPlex SM programs. Be sure to review the language-specific considerations in the remainder of this section and modify your JCL accordingly.

In addition, if your program contains EXEC CICS commands, you should review the link-edit considerations in the Application Programming Guide for your version of CICS. Likewise, if your program runs under NetView, you should refer to the NetView customization book for your programming language, either Customization: Using Assembler, or Customization: Using PL/I and C.

Assembler considerations

Assembler load modules can reside in 24- or 31-bit storage and can be entered in either addressing mode.

To link edit an Assembler module to run with a CICSPlex SM program, you must include a SYSLIB statement for the SEYULOAD load library in your link-edit step. This allows you to include the appropriate CICSPlex SM stub module when link editing. For example:

  //LKED     EXEC  PGM IEWL,
  //    PARM='XREF,LET,LIST,AMODE=ANY,RMODE=31',
  //    REGION=4096K,COND=(7,LT,ASM)
                                .
                                .
                                .
  //SYSLIB   DD DSN=CICSTS31.CPSM.SEYULOAD,DISP=SHR
                                .
                                .
                                .
    INCLUDE  SYSLIB(userprog)
    INCLUDE  SYSLIB(EYU9AMSI)
    NAME     LMODNAME(R)

PL/I, COBOL, and C considerations

PL/I, COBOL, and C load modules can reside in 24- or 31-bit storage and can be entered in either addressing mode.

To link edit a module to run with a CICSPlex SM program, you must include a SYSLIB statement for the SEYULOAD load library in your link-edit step. This allows you to include the appropriate CICSPlex SM stub module when link editing. For example:

  //LKED     EXEC  PGM=IEWL,
  //    PARM='XREF,LET,LIST,AMODE=ANY,RMODE=31',
  //    REGION=4096K,COND=(8,LE,COMPILE)
                       .
                       .
                       .
  //SYSLIB   DD DSN=CICSTS31.CPSM.SEYULOAD,DISP=SHR
                       .
                       .
                       .
    INCLUDE  SYSLIB(userprog)
    INCLUDE  SYSLIB(EYU9AMSI)
    NAME     LMODNAME(R)
[[ Contents Previous Page | Next Page Index ]]