Previous Topic: Default ProcessingNext Topic: Building on z/OS


Customizing the Exit

This exit is used by the server runtime to enable changing the parameters required to issue the Server-to-Server request. TIRALLOX-RETURN must be set to spaces to indicate success or non-space to indicate failure. In case of failure, the FAIL-MESSAGE can be populated with a message that will be returned to the client.

The CICS implementation differentiates between a Local and Remote requests.

A Local request means both servers will execute in the same CICS region. The method used for this implementation is to call user exit TIRCQNAM, issue a CICS Start command to start the target server transaction passing it the name of a TSQ containing the cooperative buffer, issue a CICS Post ECB with an interval of WAIT-TRAN-TIMEOUT and a CICS Wait ECB. User exit TIRCQNAM provides a customized name for the TSQ used in the CICS Start command and located as specified in MAIN-OR-AUX-STORAGE parameter.

Modify the MAIN-OR-AUX-STORAGE or the WAIT-TRAN-TIMEOUT as required by the application. Note that the WAIT-TRAN-TIMEOUT value should be large enough to enable all activity of the Server-to-Server flow to complete.

A Remote request means each server executes in a different CICS region using an APPC (LU6.2) connection between the two CICS. A CICS Allocate Sysid command using the ALLOCATE-PARTNER-NAME as the Sysid is used to allocate the conversation followed by a CICS Connect Process and CICS Send using the Convid returned by the Allocate. The ALLOCATE-PROFILE-NAME becomes DFHCICSA if left blank. Modify the ALLOCATE-PARTNER-NAME or ALLOCATE-PROFILE-NAME as required by the application. The CICS APPC definitions need to be in place, the Profile must include the name of the VTAM Logmode Table as the MODENAME and the Connections must be ACQUIRED prior to the CICS Allocate being issued.