CICS Considerations for the EZA Interfaces

Before the EZA API (EZASMI macro and EZASOKET call interface) can be used in a CICS TS Transaction Environment, its "task-related-user-exit" (TRUE) routine has to be started. This EZA "task-related-user-exit" is named EZATRUE. It is responsible for allocating task-related working storage to the EZA API processing environment and for possible cleanup processing during CICS end-of-task processing.

The "task-related-user-exit" EZATRUE is started/stopped with program EZASTRUE by one of the following means:
  • transaction EZAT (EZAT START starts EZATRUE, EZAT STOP stops it)
  • entry of EZASTRUE to the PLTPI (for auto-startup during CICS startup) and to the PLTSD (for auto-shutdown during CICS shutdown)
  • an EXEC CICS® LINK to program EZASTRUE with the following COMMAREA parameter list:
    Table 1. COMMAREA parameter list
    Offset Length Description
    0 8 Eyecatcher "EZATRUE"
    8 1 Request Type:
    "S" Start Request
    "T" Termination Request
    9 1 Return Code from EZASTRUE:
    0 EZATRUE start/termination successful
    4 EZATRUE already in requested state
    8 Failure to start/terminate EZATRUE
    16 Invalid parameter list