Using the XISQUE and XZIQUE global user exits
You can control the queuing of allocate requests through a global user exit program, which provides more flexibility than setting a queue limit on the connection. Use XISQUE to manage IPIC queues and XZIQUE to manage MRO and APPC queues.
With the XISQUE and XZIQUE exits, you can quickly detect queuing problems (bottlenecks). Both exits enable allocate requests to be queued or rejected, depending on the length of the queue. You can use XISQUE and XZIQUE to stop and then reestablish a connection that has a bottleneck.
The XZIQUE exit extends the function that the XISCONA exit provides for MRO and APPC connections. XISCONA is called for function shipping and DPL requests only, including function shipped EXEC CICS® START requests used for asynchronous processing. XZIQUE is called for transaction routing, asynchronous processing, and distributed transaction processing requests, in addition to function shipping and DPL. Compared with the XISCONA exit, XZIQUE receives more detailed information on which to base its action. For information about the relationship between XISCONA and XZIQUE, see Interaction with the XISCONA exit.
Uses of a queuing global user exit program
When the exit is enabled, your XZIQUE or XISQUE global user exit program can check on the state of the allocate queue for a particular connection in the local system.
Information is passed to the exit program in a parameter list that is structured to provide data about nonspecific allocate requests or requests for specific modegroups, depending on the session request. If you are using the XZIQUE exit, nonspecific allocate requests are for MRO, LU6.1, and APPC sessions that do not specify a modegroup.
- Queue the allocate request. This action is possible only if the queue limit has not been reached.
- Reject the allocate request.
- Reject this allocate request and purge all queued requests for the connection.
- Reject this allocate request and purge all queued requests for the modegroup.
- The length of the allocate queue.
- Whether the number of queued requests has reached the limit set by the QUEUELIMIT option. If the queue limit has not been reached, you might decide to queue the request.
- The rate at which sessions are being allocated on the connection. If the queue limit has been reached but session allocation is acceptably quick, you might decide to reject only the current request. If the queue limit has been reached and session allocation is unacceptably slow, you might decide to purge the whole queue.
For details of the information passed in the XISQUE parameter list, and advice about designing and coding an XISQUE exit program, see the programming information in XISQUE exit for managing IPIC intersystem queues.
For details of the information passed in the XZIQUE parameter list, and advice about designing and coding an XZIQUE exit program, see the programming information in XZIQUE exit for managing MRO and APPC intersystem queues.