Why tasks fail to get attached to the dispatcher
Two valid reasons why a user task might fail to get an initial attach to the dispatcher are that the system has reached the maximum number of tasks (MXT) limit or the task belongs to a transaction class that has reached its MAXACTIVE limit.
For a system task, there may not be enough storage to build the new task. This sort of problem is more likely to occur near peak system load times.
Is the MXT limit preventing tasks from getting attached?
Before the transaction manager can attach a user task to the dispatcher, the task must first qualify under the MXT (maximum tasks in the system) and transaction class limits. If a task is not getting attached, it is possible that one or both of these values is too small.You might be able to use CEMT INQ TASK to show that a task is failing to get attached because of the MXT or transaction class limits. If you cannot use CEMT because the task is held up for too short a time, you can look at either the transaction global statistics, transaction class statistics, or the CICS performance-class monitoring records. Another option is to use CICS system tracing. For more information on setting MXT, see Setting the maximum task specification (MXT).