Link editing your program

The CICS® 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. Because 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 TS programs. EYU9AMSI is supplied in the CICSTS56.CPSM.SEYULOAD library.
EYU9ABSI: For batch, TSO, or NetView programs. EYU9ABSI is supplied in the CICSTS56.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. Failure to include the appropriate stub module and SYSLIB dataset during the linkedit step will result in a message reporting that symbol EYUEI1 is unresolved, similar to the following IEW2456E SYMBOL EYUEI1 UNRESOLVED.

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. Likewise, if your program runs under NetView, refer to the NetView information for your programming language: IBM Tivoli NetView for z/OS Programming: Assembler or IBM Tivoli NetView for z/OS Programming: PL/I and C.