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:

In either case, CICS cannot start any new work.

CICS provides two methods to prevent these problems:

For further information about controlling intersystem queues, see Intersystem session queue management.



dfht13y.html | Timestamp icon Last updated: Sunday, 4 June 2017