Formatting a system dump using the keyword XM=1 provides a number of transaction manager
summaries that are useful for identifying why tasks have failed to run.
The transaction summary lists all transactions (user and system) that currently exist. The
transactions are listed in order of task number and the summary contains two lines per
transaction.
The primary transaction id associated with the transaction
Tran num
The unique transaction number assigned to the transaction
Txn Addr
The address of the transaction control block
Txd Addr
The address of the transaction definition instance associated with the transaction
Start Code
The reason the transaction was attached, as follows:
C A CICS® internal attach
T A terminal input attach
TT A permanent transaction terminal attach
QD A transient data trigger level attach
S A START command without any data
SD A START command with data
SZ A front end programming interface (FEPI) attach
DF Start code not yet known — to be set later.
Sys Tran
Indicator (Yes or No) of whether the transaction is attached as a system transaction. System
transactions do not contribute toward MXT.
Status
An indicator of how far through attach the transaction has progressed and whether the transaction
is abending or not. The first line may take the following values:
PRE
The transaction is in the early stages of attach.
TCLASS
The transaction is waiting to acquire membership of a tclass.
MXT
The transaction is waiting on MXT.
ACT
The transaction is active, that is, it has been DS attached.
Depending on the value in the first line, the second line of the status field may further qualify
the transaction state. For each first line value, the meaning of the second line is as follows:
PRE
No data is displayed in the second line
TCLASS
The second line contains the name of the tclass that the transaction is waiting to join.
MXT or ACT
If applicable, the second line indicates if the transaction is flagged for deferred abend or a
deferred message, or if the transaction is already abending, as follows:
DF(xxxx)
Indicates that the transaction is scheduled for deferred abend, where xxxx is the abend
code.
DM(yy)
Indicates that the transaction is scheduled for a deferred message, and yy indicates the message
type
AB(xxxx)
Indicates that the transaction is already abending with abend code xxxx.
DS token
The token identifying the DS task (if any) assigned to the transaction.
Facility type
Type of the principal facility owned by the transaction.
Facility token
Transaction token for the principal facility owner.
AP token
The AP domain transaction token.
The first word of this token contains the address of the
TCA (if any) associated with the transaction.
PG token
The program manager transaction token.
XS token
The security domain transaction token.
US token
The user domain transaction token.
RM token
The recovery manager transaction token.
SM token
The storage manager domain transaction token.
MN token
The monitoring domain transaction token.
MXT summary
The MXT summary indicates whether CICS is currently at the
maximum number of tasks, showing the current number of queued and active
transactions.
To check the status of an individual transaction, consult the main transaction summary (see Transaction summary). Figure 2. MXT
summary
==XM: MXT SUMMARY
Maximum user tasks (MXT): 7
System currently at MXT: Yes
Current active user tasks: 7
Current queued user tasks: 2
* Peak active user tasks: 7
* Peak queued user tasks: 2
* Times at MXT limit: 1
* NOTE: these values were reset at 18:00:00 (the last statistics interval collection)
Transaction class summary
The transaction class summary lists each transaction class that is currently installed. For each
class, the current number of active and queued transactions is shown.
A transaction class is at its MAXACTIVE limit if its ‘current active’ total is greater than or
equal to its ‘max active’ setting. If a transaction class is at its MAXACTIVE limit, a number of
transactions could be queueing in that transaction class. The transaction id and number of each
queued transaction is listed with its transaction class (for example, transaction classes DFHCTL01,
DFHCTL02, and DFHCTL03 in Figure 3). Figure 3. Transaction class summary
==XM: TCLASS SUMMARY
Tclass Max Purge Current Current Total Queuing Queuing Queuing
Name Active Threshld Active Queued Attaches TranNum Transid Start Time
-------- -------- -------- -------- -------- -------- ------- ---- ------------
DFHTCL01 1 0 0 0 0
DFHTCL02 1 3 1 2 7 95175 TA02 18:00:19.677
95187 TA02 18:00:24.624
DFHTCL03 1 4 1 3 29 93920 TA03 17:55:40.584
93960 TA03 17:55:42.230
93967 TA03 17:55:52.253
DFHTCL04 1 0 1 1 23 96649 TA04 18:06:04.348
DFHTCL05 1 0 0 0 0
DFHTCL06 1 0 0 0 0
DFHTCL07 1 0 0 0 0
DFHTCL08 1 0 0 0 0
DFHTCL09 1 0 0 0 0
DFHTCL10 1 0 0 0 0
*** Note that the 'Total Attaches' figures were reset at 18:00:00 (the last statistics interval collection)