Intersystem queuing
Performance problems can occur when function shipping requests that are waiting for free sessions are queued in the issuing region.
Requests that are to be function shipped to a resource-owning region
might be queued if all bound contention winner sessions are busy,
so that no sessions are immediately available. If the resource-owning
region is unresponsive, the queue can become so long that the performance
of the issuing region is severely impaired. Further, if the issuing
region is an application-owning region, its impaired performance can
spread back to the terminal-owning region.
Note: Contention
winner is the terminology used for APPC connections. On MRO
and LUTYPE6.1 connections, the SEND sessions (defined in the session
definitions) are used for ALLOCATE requests; when all SEND sessions
are in use, queuing starts.
On IPIC connections, queuing starts
when there are no available send sessions. The number of send sessions
are specified using the SENDCOUNT attribute on the IPCONN resource
definition on the local server. The number of receive sessions are
specified using the RECEIVECOUNT attribute defined in the IPCONN resource
definition on the remote system. The number of send sessions that
are used is the lower of the following two values:
- SENDCOUNT on the local definition
- RECEIVECOUNT on the remote definition
The symptoms of this impaired performance are as follows:
- The system reaches its maximum transactions (MXT) limit, because many tasks have requests queued.
- The system becomes short on storage.
In either case, CICS cannot start any new work.
CICS provides two methods to prevent these problems:
- The QUEUELIMIT and MAXQTIME options on both the IPCONN and CONNECTION definitions. You can use these options to limit the number of requests that can be queued against particular remote regions, and the time that requests must wait for sessions on unresponsive connections.
- The global user exits XZIQUE, XISCONA, and XISQUE. The XZIQUE
or XISCONA exit program is invoked if no contention winner session
is immediately available. The exit program can instruct CICS to queue
the request, or to return SYSIDERR to the application program. Its
decision can be based on statistics accessible from the user exit
parameter list. For programming information about writing XZIQUE
and XISCONA exit programs, refer to Intersystem communication program exits, XISCONA, XISLCLQ, and XISQLCL.
For information about the statistics records that are passed to your
exit program, refer to Introduction to CICS statistics.
The global user exit XISQUE is used to manage IPIC intersystem queues.
See XISQUE exit for managing IPIC intersystem queues.Note: For non-IPIC connections, it is best practice to use the XZIQUE exit, rather than XISCONA. XZIQUE provides better function, and is of more general use than XISCONA. It is driven for function shipping, DPL, transaction routing, and distributed transaction processing requests, whereas XISCONA is driven only for function shipping and DPL. If you enable both exits, XZIQUE and XISCONA can both be driven for function shipping and DPL requests, which is not recommended.
If you already have an XISCONA exit program, you might be able to modify it for use at the XZIQUE exit point.
For further information about controlling intersystem queues, see Intersystem session queue management.