Statistics for tuning and capacity planning

Capture statistics when the CICS Transaction Gateway is operating under a number of different operating conditions. This will help you understand changes that might affect the performance of the system.

CM_CALLOC

The current number of connection manager threads allocated to clients.

CM_CCURR

The current number of connection manager threads created. If this value is greater than the configuration parameter initconnect, it signifies the peak number of remote clients connected at any one time. This value cannot exceed the maximum number of connection managers defined in CM_SMAX.

CM_CWAITING

The current number of connection managers waiting for a worker thread to become available. This statistic shows the number of requests that are queuing in the Gateway daemon. It is usually low or zero in a well-tuned Gateway daemon. If it is higher than expected, consider increasing the maxworker configuration parameter.

CM_IALLOC

The number of allocations for connection manager threads representing the number of connections that have been established from remote clients. A low value represents efficient connection reuse.

CM_IALLOCHI

The peak number of connection manager threads concurrently allocated to client applications. This number represents a high water mark for CM_CALLOC.

CM_ICREATED

The number of connection manager threads created.

CM_ITIMEOUTS

The number of times that the Gateway daemon failed to allocate a connection manager thread to a client application within the defined connecttimeout length of time.

CM_LALLOC

The number of allocations for connection manager threads representing the number of connections that have been established from remote clients. A stable value represents efficient connection reuse.

CM_LTIMEOUTS

The number of times that the Gateway daemon failed to allocate a connection manager thread to a client application within the defined (connecttimeout) length of time. This statistic shows the number of incoming connection requests that have been refused. It is usually low or zero in a well-tuned Gateway daemon. If it is high, consider increasing the connecttimeout or maxconnect configuration parameters.

CM_SMAX

The maximum number of connection manager threads maxconnect that can possibly be created and allocated by the Gateway daemon. This value limits the number of Java™ clients that can be connected at any one time.

WT_CALLOC

The current number of worker threads that are being used by connection managers. Another way of viewing this value is the number of worker threads processing requests. If this value is close to WT_SMAX, consider increasing the maxworker configuration parameter.

WT_CCURR

The current number of worker threads created. If this value is greater than the configuration parameter initworker, it signifies the peak number of parallel requests that have been in process at any one time. This value cannot exceed the maximum number of worker threads defined in WT_SMAX.

WT_IALLOCHI

The peak number of worker threads concurrently allocated to connection manager threads. This number represents a high water mark for WT_CALLOC.

WT_ITIMEOUTS

The number of times the Gateway daemon failed to allocate a worker thread to a connection manager within the defined workertimeout length of time.

WT_LTIMEOUTS

The number of times the Gateway daemon failed to allocate a worker thread to a connection manager within the defined workertimeout length of time. This number signifies that requests are timing out while queuing in the Gateway daemon. It is typically low or zero in a well-tuned Gateway daemon. If it is higher than expected, consider increasing the maxworker or workertimeout configuration parameters.

WT_SMAX

The maximum number of parallel requests maxworker that the Gateway daemon can process.