Statistic to show number of ConnectionManagers in limbo state

The CM_CCURR statistic includes those that are in a 'limbo' state - i.e. those ConnectionManagers which are no longer connected to a client, but cannot be returned to the free pool because there is still a worker thread outstanding waiting for work to complete. This is by design since they are to all intent and purpose 'allocated' and cannot be used.

However, without knowing the number that are in limbo state, you cannot work out the current number of 'real active' TCP/IP connections, nor what capacity you currently have to do real work.
In the case where requests get stuck in CICS, using TCP/IP and with no ECI Timeout, when connections inbound from WAS disconnect, any CM which had one of these stuck requests would then be stuck in a limbo state, until some corrective action is taken. Potentially, all ConnectionManagers could end up in limbo state, but this would not be apparent from the stats.

Having a specific stat to show how many ConnectionManagers are in the limbo state (and possibly how many workers are attached to connection managers in limbo state) would help determine the real state of a gateway.

For example:
CM_CCURR= 132
CM_CLIMBO=53

WT_CCURR = 63
WT_CCMLIMBO = 53

This would show there are 53 CMs in Limbo, and 53 workers waiting for a response allocated to CMs that were in limbo.
It would show that of the 132 currently allocated ConnectionManagers, only 79 are handling active TCP/IP connections.
If the Limbo count starts to rise, it might indicate a problem which needs to be investigated