ECI Client API exits

The ECI Client API exits are available for use with ECI requests that are sent to servers connected by the TCP/IP and SNA protocols. They are not available if using the IPIC protocol.

The exits are called from the Gateway daemon process when running in remote mode and from the application process when running in local mode. The exits are called for ECI requests issued from all APIs. For more information on creating and deploying user exits see ../progde/eiexits.html.

Table 1 summarizes the exit names, the parameters passed to each exit, and the possible return codes.
Table 1. Summary of ECI exits
Function name Parameters Return codes:

CICS_EciInitializeExit

Version
Anchor

CICS_EXIT_OK
CICS_EXIT_NO_EXIT
CICS_EXIT_CANT_INIT_EXITS
user-defined

CICS_EciTerminateExit

Anchor

CICS_EXIT_OK
CICS_EXIT_BAD_ANCHOR
CICS_EXIT_BAD_STORAGE
user-defined

CICS_EciExternalCallExit1

Anchor
Token
ParmPtr

CICS_EXIT_OK
CICS_EXIT_BAD_ANCHOR
CICS_EXIT_BAD_PARM
user-defined

CICS_EciExternalCallExit2

Anchor
Token
ParmPtr

CICS_EXIT_OK
CICS_EXIT_BAD_ANCHOR
CICS_EXIT_BAD_PARM
user-defined

CICS_EciSystemIdExit

Anchor
Token
ParmPtr
Reason

CICS_EXIT_OK
CICS_EXIT_BAD_ANCHOR
CICS_EXIT_BAD_PARM
CICS_EXIT_GIVE_UP
user_defined

CICS_EciDataSendExit

Anchor
Token

CICS_EXIT_OK
CICS_EXIT_BAD_ANCHOR
CICS_EXIT_BAD_PARM
user_defined

CICS_EciDataReturnExit

Anchor
Token
ParmPtr

CICS_EXIT_OK
CICS_EXIT_BAD_ANCHOR
CICS_EXIT_BAD_PARM
user_defined

CICS_EciSetProgramAliasExit

Anchor
EciParms
Program

CICS_EXIT_OK
CICS_EXIT_BAD_ANCHOR
CICS_EXIT_BAD_PARM
user_defined


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//proref/apceci.html