PROBLEM
When looking in ESMAC CONTROL at 'Monitor 1 and 15' to see the statistics 'average task len', why do these not go up when there is a looping task?
RESOLUTION
These monitor screens contain statistics from a system point of view for the last minute or 15 minutes.
The statistics are averages of latency and task duration and the number of tasks per second for completed tasks. So if a task is still in progress, as in this case, then it will not be part of those statistics (this information can be seen on active tasks on the SEPs page).
For further information on individual tasks, then you will need to use HSF. Note that HSF records are only generated when tasks have completed.
How can you see a runaway task;
Look into Runaway Timeout/Input timeout options:
Runaway Timeout is the amount of time that the region will allow the transaction to run without making a CICS, EZASOKET or MQSeries API call. The system is checked to see if any running transactions have exceeded this timeout every 10 seconds. The actual amount of time to abend a transaction may take longer.
If the runaway task is looping performing CICS, EZASOCKET or MQSeries API calls then the runaway task timeout will never come into effect and one of the other timeouts such as Input Timeout (see below) should be used instead.
Timeout values less than 10 seconds will not work. This is because the system only checks for runaway transactions approximately every 10 seconds. Even setting a value greater than 10 seconds does not guarantee that the transaction will be stopped after precisely that time as it will depend upon when the system check for runaway transactions after the time period has passed.
The actual time it takes to timeout a runaway transaction will depend on what the transaction is doing. It will only timeout if the transaction has not issued a CICS, EZASOCKET or MQ Series API calls for the specified period. So if your transaction is in a loop where it is making new CICS calls within the period it will not time out.
In addition to the runaway timeout there are two additional timeouts that can be set:
1. ID timeout - This is the amount of time a terminal session can be idle before it is disconnected.
2. Input timeout - Similar to ID Timeout except that it's the amount of time to wait for input from a terminal before terminating.
#Enterprise
#Server
#EnterpriseServer
