EXCI considerations

For EXCI workloads, CICS Transaction Gateway and CICS must be configured to ensure there are is not an EXCI pipe shortage.

A connection manager uses one worker thread for every request to run a transaction in CICS®. A worker thread allocates one EXCI pipe (MRO session) to every CICS server (APPLID) with which it communicates. This can be limited to a single pipe using the setting CTG_PIPE_REUSE.

Configure your system as follows:

When EXCI connections are used by a Gateway daemon, the maximum number of worker threads is restricted to LOGONLIM. Because all CICS server connections share the same pool of worker threads, this restriction also affects any IPIC connections. If EXCI has been disabled using the CTG_EXCI_INIT parameter, this restriction does not apply.

EXCI connections

When you define your EXCI connections you can choose between generic EXCI pipes and specific EXCI pipes. Specific EXCI pipes give slightly better performance. See CICS server connection definition for more information on selecting your EXCI connections.

EXCI resource shortage

An insufficient number of EXCI pipes causes intermittent resource shortage errors to be reported to the API. Requests receive ECI_ERR_RESOURCE_SHORTAGE errors. This can occur when any of the following events is happening. The EXCI options table, generated by the DFHXCOPT macro, enables you to specify the time interval, in hundredths of a second, during which the EXCI waits for a DPL command to complete.

If CS_CALLOC = CS_SLOGONLIM all EXCI pipes are in use. Resource shortage errors might occur because there are not enough EXCI pipes available to support the number of incoming requests from the worker threads.

If several CICS servers are being used by each Gateway, change the CICS Transaction Gateway pipe usage model by setting the CTG_PIPE_REUSE=ONE configuration parameter.

If large numbers of worker threads are being used, increase the value of the CICS LOGONLIM system parameter for the LPAR.

If large numbers of worker threads are in use, or significant numbers of requests are being timed out by the EXCI timeout mechanism, and the value of the RECEIVECOUNT parameter in the CICS SESSIONS definition is less than double the value of the number of worker threads created (WT_CCURR), increase the value of the RECEIVECOUNT parameter in the CICS SESSIONS definition to be at least double the value of WT_CCURR.

Other factors

When you define your EXCI connections you can choose between generic EXCI pipes and specific EXCI pipes. Specific EXCI pipes give slightly better performance. See CICS server connection definition for more information on selecting your EXCI connections.


Reference Reference

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//ctgzos/thread_sess.html