Transactions: Summary resource statistics - resource information
Transactions summary resource statistics - resource information 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
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 Writing a dynamic routing program.
|
| 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 Writing a dynamic routing program
|
| 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 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.
|