ATCH
Explanation
The task was purged before a domain call was able to complete successfully. The task that first detected the purged condition provides an exception trace.
System action
The task is abnormally terminated with a CICS transaction dump.
User response
Investigate why the task was purged. It was purged either as a result of a purge from the main terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction, or by CICS issuing a purge request.
If the main terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.
If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.
When CICS purges a task, it does so to allow an operation to complete which would be held up by the presence of active tasks, or to ensure data integrity. For example, CICS will purge a task which has made recoverable updates to a coupling facility data table if it determines that the coupling facility data table server for the pool in which that table resides has recycled, to ensure that all updates in the unit of work will be backed out.
For module list,see Diagnostics reference.