Transaction statistics

Interpreting transaction manager statistics
The Times the MAXTASK limit reached indicates whether MXT is constraining your system, or any possible integrity exposures are resulting from forced resolutions of UOWs relating to the transactions. The only time that you must constrain your system in this way is to reduce virtual storage usage.
Transaction manager: Global statistics
You can retrieve transaction manager global statistics by using the EXEC CICS EXTRACT STATISTICS TRANSACTION system command. They are mapped by the DFHXMGDS DSECT.
Transactions: resource statistics
You can retrieve transaction resource statistics by using the EXEC CICS EXTRACT STATISTICS TRANSACTION system command. They are mapped by the DFHXMRDS DSECT.
Transactions: Resource statistics - resource information
The transaction statistics show how often each transaction is called.
Transactions: Resource statistics - integrity information
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.
Transaction manager: Summary global statistics
Transaction manager summary global statistics are not available online.
Transactions: Summary resource statistics - resource information
Transactions summary resource statistics - resource information are not available online.
Transactions: Summary resource statistics - integrity information
Transactions summary resource statistics - integrity information are not available online.
Interpreting transaction class (TRANCLASS) statistics
If you are never at the limit of your transaction class setting, you might consider resetting its value, or review whether there is any need to continue specifying any transaction types with that class.

Parent topic: DFHSTUP reports

Last updated: Friday, 18 December 2020 08:52