This section contains the following statistics:
These statistics can be accessed online using the EXEC CICS® COLLECT STATISTICS TRANSACTION command, and are mapped by the DFHXMGDS DSECT. For programming information about the EXEC CICS COLLECT STATISTICS command, see the CICS System Programming Reference manual.
DFHSTUP name | Field name | Description |
---|---|---|
Total number of transactions (user + system) | XMGNUM | is the number of transactions (user + system) that have
run in the system.
Reset characteristic: reset to zero
|
Current MAXTASKS limit | XMGMXT | is the latest MXT value (expressed as a number of tasks)
specified in the SIT, or as an override, or changed dynamically using CEMT
SET SYSTEM MAXTASKS(value) or EXEC CICS SET SYSTEM MAXTASKS(fullword binary data-value)
commands.
Reset characteristic: not reset
|
Current number of active user transactions | XMGCAT | is the current number of active user transactions in the
system.
Reset characteristic: not reset
|
Current number of MAXTASK queued user transactions | XMGCQT | is the current number of queued user transactions in the
system. Note that this does not include transactions queueing for transaction
class membership. Note that the current queueing time for these transactions
is in field XMGCQTME.
Reset characteristic: not reset
|
Times the MAXTASKS limit reached | XMGTAMXT | is the number of times the MXT limit has been reached
Reset characteristic: reset to zero (or one if at MXT)
|
Peak number of MAXTASK queued user transactions | XMGPQT | is the peak number of MAXTASK queued user transactions
reached in the system.
Reset characteristic: reset to current value (XMGCAT)
|
Peak number of active user transactions | XMGPAT | is the number of user transactions that have become active.
Reset characteristic: reset to zero
|
Total number of active user transactions | XMGTAT | is the total number of user transactions that have become
active.
Reset characteristic: reset to zero
|
Number of MAXTASK delayed user transactions | XMGTDT | is the number of user transactions that had to queue for
MXT reasons. This value does not include those transactions that are currently
queueing for MXT (see XMGCQT). Note that the queueing time for these transactions
is in field XMGTQTME.
Reset characteristic: reset to zero
|
Total MAXTASK queuing time | XMGTQTME | is the total time spent waiting by those user transactions
that had to queue for MXT reasons. This value does not include the time spent
by those transactions that are currently queueing for MXT (see XMGCQTME).
Reset characteristic: reset to zero
|
Total MAXTASK queuing time of currently queued user transactions | XMGCQTME | is the total time spent waiting so far by those user transactions
currently queuing for MXT reasons.
Reset characteristic: not reset
|
NOT IN THE DFHSTUP REPORT | XMGTNUM | is the total of user and system transactions attached
to date, up to the time of the last statistics reset.
Note:
The
total of XMGNUM and XMGTNUM represents the total number of transactions attached
so far. Reset characteristic: reset to XMGNUM + XMGTNUM at the time of the last reset.
|
These statistics can be accessed online using the EXEC CICS COLLECT STATISTICS TRANSACTION command and are mapped by the DFHXMRDS DSECT. For programming information about the EXEC CICS COLLECT STATISTICS command, see the command, see the CICS System Programming Reference manual.
There are two sections in the DFHSTUP report for transaction manager resource statistics:
The transaction statistics show how often each transaction is called.
DFHSTUP name | Field name | Description |
---|---|---|
Trans ID | XMRTI | is the transaction identifier associated with the transaction
definition.
Reset characteristic: not reset
|
Program Name | XMRPN | is the name of the initial program to which the transaction
linked.
Reset characteristic: not reset
|
Tclass Name | XMRTCL | is the name of the transaction class in which the transaction
is defined.
Reset characteristic: not reset
|
Prty | XMRPRTY | is the priority of the transaction, from 0-255.
Reset characteristic: not reset
|
Remote Name | XMRRNAM | is the name of the transaction on the remote system.
Reset characteristic: not reset
|
Remote Sysid | XMRRSYS | is the name of the remote system where the transaction
resides.
Reset characteristic: not reset
|
Dynamic | XMRDYN | indicates whether the transaction has been defined as
DYNAMIC=YES (Y) or DYNAMIC=NO (N).
Reset characteristic: not reset
|
Attach Count | XMRAC | is the number of times that this transaction has been
attached. If a transaction definition is used to start a transaction remotely,
the transaction is included in the Attach Count for the region where the transaction
actually runs.
Reset characteristic: reset to zero
|
Retry Count | XMRRC | is the number of times that this transaction definition
has been used to retry a transaction.
Reset characteristic: reset to zero
|
Dynamic Local | XMRDLC | is the number of times the dynamic transaction routing
exit has chosen to run this transaction on the local system. This field is
zero if the transaction was not defined as DYNAMIC=YES. For further information
about dynamic transaction routing, see the programming information in the CICS Customization Guide.
Reset characteristic: reset to zero
|
Dynamic Remote | XMRDRC | is the number of times the dynamic transaction routing
exit has chosen to run this transaction on a remote system. This field is
zero if the transaction was not defined as DYNAMIC=YES. For further guidance
about dynamic transaction routing, see the programming information in the CICS Customization Guide.
Reset characteristic: reset to zero
|
Remote Starts | XMRRSC | is the number of times that this transaction definition
has been used to attempt to start the transaction on a remote system. (This
might not necessarily be the same as the number of successful starts.) A Remote
Start is only counted in the CICS region that initiates the process, and
not in the remote system where the transaction actually runs. In some circumstances,
the use of a transaction definition for a remote start is not counted. This
includes the case where a transaction definition that specifies the local
sysid or nothing as the REMOTESYSTEM value, is used to start a transaction
in a remote system, with the remote system specified on the SYSID option of
the START command.
Reset characteristic: reset to zero
|
Storage Violations | XMRSVC | is the number of storage violations for this transaction
that have been detected by CICS storage management.
This is a serious concern if it occurs in a production system. You should act immediately to identify the cause of the problem because it can lead to data corruption, and therefore should not be allowed to continue in an operational system. Reset characteristic: reset to zero
|
The integrity information statistics show the potential integrity exposures that may have occurred during transaction execution as a result of inabilities to shunt UOWs, or forcing of shunted UOWs to complete regardless of the decisions made by participating systems.
DFHSTUP name | Field name | Description |
---|---|---|
Trans ID | XMRTI | is the transaction identifier associated with the transaction
definition.
Reset characteristic: not reset
|
Indoubt Wait | XMRIWTOP | Is the indicator of whether the transaction has been defined
to support Indoubt Waiting in the event of an two-phase commit indoubt window
failure. This means the failing UOW will be shunted by the CICS recovery manager
awaiting resynchronisation with its coordinator. The indoubt wait option can
have the following settings:
Reset characteristic: not reset
|
Indoubt Wait timeout | XMRITOV | Is the indoubt wait timeout limit defined for this transaction,
specified in minutes. This value has meaning only if the transaction is also
defined to be able to wait indoubt (see XMRIWTOP). A value of zero, specifies
that there is no timeout should this transaction be shunted by the CICS recovery manager.
Reset characteristic: not reset
|
Indoubt Action | XMRIACTN | Is an indicator of which way this transaction will commit
its UOWs in the event of not being able to wait indoubt (shunted), when an
indoubt wait failure occurs. Or if the transaction had been waiting that,
the timeout value specified has expired. Both of these events will force a
resolution of the UOW in the direction specified by this field. The values
can be :
Reset characteristic: not reset
|
Indoubt Waits | XMRIWAIT | Is the number of indoubt waits (shunts) that have occurred
for UOWs executing on behalf of this transaction.
Reset characteristic: not reset
|
Indoubt action forced: Trandefn | XMRFATXN | Is the number of times this transaction id had a UOW that
could not be shunted when an indoubt failure occurred, because the transaction
definition for this transaction id specified that it could not support indoubt
waiting (ie. XMRIWTOP = XMTIWTN). The UOW would have been forced to resolve
in the direction specified by XMRIACTN, regardless of the actions taken by
any other participating region in this distributed UOW.
Reset characteristic: not reset
|
Indoubt action forced: Timeout | XMRFAIT | Is the number of times this transaction id had a UOW that,
although shunted because of an indoubt failure, had the wait for resynchronization
with its recovery coordinator terminated prematurely, because the indoubt
wait timeout value (XMRITOV) had been exceeded. The UOW would have been forced
to resolve in the direction specified by XMRIACTN, regardless of the actions
taken by any other participating region in this distributed UOW.
Reset characteristic: not reset
|
Indoubt action forced: Operator | XMRFAOP | Is the number of times this transaction id had a UOW that
although shunted because of an indoubt failure, had the wait for resynchronization
with its recovery coordinator terminated prematurely, because an operator
(CEMT) or SPI command forced a resolution. The UOW would have been forced
to resolve in the direction specified by XMRIACTN by default, or in the direction
specified by the operator, regardless of the actions taken by any other participating
region in this distributed UOW.
Reset characteristic: reset to zero
|
Indoubt action forced: No waiting | XMRFANW | Is the number of times this transaction id had a UOW that
could not be shunted when an indoubt failure occurred, although the transaction
definition specified that it could (XMRIWTOP = XMRIWTY), because the resource
managers (RMIs) or CICS resources or CICS connections used by the UOW could not
support indoubt waiting (shunting). The UOW would have been forced to resolve
in the direction specified by XMRIACTN, regardless of the actions taken by
any other participating region in this distributed UOW.
Reset characteristic: reset to zero
|
Indoubt action forced: Other | XMRFAOT | Is the number of times this transaction id had a UOW that
although shunted because of an indoubt failure, had the wait for resynchronization
with its recovery coordinator terminated prematurely, for reasons other than
those stated above. This could be, for example, a cold started recovery coordinator,
a resynchronization protocol violation or failure, or because the level of
resource manager (RMI) adaptor has not yet been changed to support indoubt
resolution. The UOW would have been forced to resolve in the direction specified
by XMRIACTN, regardless of the actions taken by any other participating region
in this distributed UOW.
Reset characteristic: reset to zero
|
Action mismatch | XMRAMISM | is the number of times this transaction id had a UOW that
was forced to resolve using the indoubt action attribute, whether by definition,
option or operator override (as detailed in the above fields), and on doing
so detected an indoubt action attribute mismatch with a participating system
or resource manager (RMI). For example, a participating system in a distributed
UOW resolves its work forward while other systems back out theirs. The opposite
also applies.
Reset characteristic: reset to zero
|
Summary statistics are not available online.
DFHSTUP name | Description |
---|---|
Total number of transactions (user + system)
|
is the total number of tasks that have run in the system.
|
MAXTASK limit | is the last MXT value (expressed as a number of tasks)
that was specified in the SIT, or as an override, or changed dynamically using
CEMT SET SYSTEM MAXTASKS(value) or EXEC CICS SET SYSTEM MAXTASKS(fullword binary data-value)
commands.
|
Times the MAXTASK limit reached | is the total number of times MXT has been reached.
|
Peak number of MAXTASK queued user transactions | is the peak number of MAXTASK queued user transactions
reached in the system.
|
Peak number of active user transactions | is the peak number of active user transactions reached
in the system.
|
Total number of active user transactions | is the total number of user transactions that have become
active.
|
Total number of MAXTASK delayed user transactions | is the total number of transactions that had to queue
for MXT reasons.
|
Total MAXTASK queuing time | is the total time spent waiting by those user transactions
that had to queue for MXT reasons.
|
Average MAXTASK queuing time of queued transactions | is the average time spent waiting by those user transactions
that had to queue for MXT reasons.
|
Summary statistics are not available online.
DFHSTUP name | Description |
---|---|
Trans ID | is the transaction identifier associated with the transaction
definition.
|
Program Name | is the name of the initial program to which the transaction
was linked.
|
Tclass Name | is the name of the transaction class in which the transaction
is defined.
|
Prty | is the priority of the transaction, from 1-255.
|
Remote Name | is the name of the transaction on the remote system.
|
Remote Sysid | is the name of the remote system where the transaction
resides.
|
Dynamic | indicates whether the transaction has been defined as
DYNAMIC=YES (Y) or DYNAMIC=NO (NO).
|
Attach Count | is the number of times that this transaction has been
attached. If a transaction definition is used to start a transaction remotely,
the transaction is included in the Attach Count for the region where the transaction
actually runs.
|
Retry Count | is the total number of times that this transaction definition
has been used to retry a transaction.
|
Dynamic Local | is the total number of times the dynamic transaction routing
exit has chosen to run this transaction on the local system. This field is
zero if the transaction was not defined as DYNAMIC=YES. For further guidance
and programming information about dynamic transaction routing, see the CICS Customization Guide.
|
Dynamic Remote | is the total number of times the dynamic transaction routing
exit has chosen to run this transaction on a remote system. This field is
zero if the transaction was not defined as DYNAMIC=YES. For further information
about dynamic transaction routing, see the CICS Customization Guide.
|
Remote Starts | is the number of times that this transaction definition
has been used to attempt to start the transaction on a remote system. (This
might not necessarily be the same as the number of successful starts.) A Remote
Start is only counted in the CICS region that initiates the process, and
not in the remote system where the transaction actually runs. In some circumstances,
the use of a transaction definition for a remote start is not counted. This
includes the case where a transaction definition that specifies the local
sysid or nothing as the REMOTESYSTEM value, is used to start a transaction
in a remote system, with the remote system specified on the SYSID option of
the START command.
|
Storage Violations | is the total number of storage violations for this transaction
that have been detected by CICS storage management.
This is a serious concern if it occurs in a production system. You should act immediately to identify the cause of the problem because it can lead to data corruption, and therefore should not be allowed to continue in an operational system.
|
Summary statistics are not available online.
DFHSTUP name | Description |
---|---|
Trans ID | is the transaction identifier associated with the transaction
definition.
|
Indoubt Wait | is the last value encountered for the indicator of whether
the transaction has been defined to support indoubt waiting in the event of
an two-phase commit indoubt window failure. This means the failing UOW will
be shunted by the CICS recovery manager awaiting resynchronization with its
coordinator.
|
Indoubt Wait timeout | is the last value encountered for the indoubt wait timeout
limit defined for this transaction, specified in minutes. This value only
has any meaning if the transaction is also defined to be able to wait indoubt
(see 'Indoubt Wait'). A value of zero specifies that there is no timeout should
this transaction be shunted by the CICS recovery manager.
|
Indoubt Action | is the last value encountered for the indicator of which
way this transaction will commit its UOWs in the event of not being able to
wait indoubt (shunted), when an indoubt wait failure occurs. Or if the transaction
had been waiting, that the timeout value specified had expired. Both of these
events will force a resolution of the UOW in the direction specified by this
field.
|
Indoubt Waits | is the number of indoubt waits (shunts) that have occurred
for UOWs executing on behalf of this transaction.
|
Indoubt action forced: Trandefn | is the number of times this transaction id had a UOW that
could not be shunted when an indoubt failure occurred, because the transaction
definition for this transaction id specified that it could not support indoubt
waiting (ie. Indoubt Wait = No). The UOW would have been forced to resolve
in the direction specified by 'Indoubt Action', regardless of the actions
taken by any other participating region in this distributed UOW.
|
Indoubt action forced: Timeout | is the number of times this transaction id had a UOW that
although shunted because of an indoubt failure, had the wait for resynchronization
with its recovery coordinator terminated prematurely, because the indoubt
wait timeout value had been exceeded. The UOW would have been forced to resolve
in the direction specified by 'Indoubt Action', regardless of the actions
taken by any other participating region in this distributed UOW.
|
Indoubt action forced: Operator | is the number of times this transaction id had a UOW that
although shunted because of an indoubt failure, had the wait for resynchronization
with its recovery coordinator terminated prematurely, because an operator
(CEMT) or SPI command forced a resolution. The UOW would have been forced
to resolve in the direction specified by 'Indoubt Action' by default, or in
the direction specified by the operator, regardless of the actions taken by
any other participating region in this distributed UOW.
|
Indoubt action forced: No waiting | is the number of times this transaction id had a UOW that
could not be shunted when an indoubt failure occurred, even though the transaction
definition specified that it could (Indoubt Wait = Yes), because the resource
managers (RMIs) or CICS resources or CICS connections used by the UOW could not
support indoubt waiting (shunting). The UOW would have been forced to resolve
in the direction specified by 'Indoubt Action', regardless of the actions
taken by any other participating region in this distributed UOW.
|
Indoubt action forced: Other | is the number of times this transaction id had a UOW that
although shunted because of an indoubt failure, had the wait for resynchronization
with its recovery coordinator terminated prematurely, for reasons other than
those stated above. This could be, for example, a cold started recovery coordinator,
a resynchronization protocol violation or failure, or because the level of
resource manager (RMI) adaptor has not yet been changed to support indoubt
resolution. The UOW would have been forced to resolve in the direction specified
by 'Indoubt Action', regardless of the actions taken by any other participating
region in this distributed UOW.
|
Action mismatch | is the number of times this transaction id had a UOW that
was forced to resolve using the indoubt action attribute, whether by definition,
option or operator override (as detailed in the above fields), and on doing
so detected an indoubt action attribute mismatch with a participating system
or resource manager (RMI). For example, a participating system in a distributed
UOW resolves its work forward while other systems back out theirs. The opposite
also applies.
|