Loading the exits

During ECI, EPI, cicsterm, and cicsprnt initialization, CICS Transaction Gateway attempts to load the objects, described in the following table, from the <install_path>\bin subdirectory, and to call the corresponding entry points.

Table 1. ECI and EPI exits
  Object name Entry point name
ECI cicsecix CICS_ECIEXITINIT
EPI cicsepix CICS_EPIEXITINIT
cicsterm cicsepix CICS_EPIEXITINIT
cicsprnt cicsepix CICS_EPIEXITINIT

Each entry point is passed a single parameter, a pointer to a structure that contains a list of addresses. The initialization code of the program puts the addresses of all the exits into the structure, and then the exits are called at appropriate points in ECI, EPI, cicsterm, and cicsprnt processing. Because the exits are entered by using the addresses supplied, you can give the exits any valid names. In this information center, conventional names are used for the exits.

For upgrade purposes, the CICS® Transaction Gateway first looks for a lowercase named object, and then for an uppercase named object. If the objects are not found, no exit processing occurs.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//progde/apcurp.html