An explanation of the difference between a DFHSTUP transaction report and an RMF workload report

CICS® transaction manager global statistics include all transactions in all regions in the interval or summary reports from DFHSTUP, but the z/OS WLM workload activity report includes only the transactions in Begin-To-End (BTE) phase and execution (EXE) phase. For WLM reporting purposes, the execution phase applies to only routed transactions in the AOR.

Figure 1 shows the significance of the difference between the performance reports created for the region by DFHSTUP, and those generated by the RMF™ workload activity report for the service class. If you are not familiar with the RMF workload activity report, see Interpreting the RMF workload activity data for more information.

In the terminal-owning region (TOR), the WLM reports for a given transaction are included in the RMF workload activity reports for the service class (for example, CICSPROD). In the application-owning region (AOR), notifications for routed transactions are included in the RMF workload activity reports when reporting execution phases in the CICS AOR. Transaction WLM notifications for mirror transactions are ignored by the z/OS WLM when reporting execution phases in the CICS FOR.

Figure 1. CICS MRO transaction workflow
In this example, a transaction arrives in VTAM, and moves to the TOR, then the AOR. It moves between the AOR and a database region (IMS or DB2) a couple of times. When this activity is completed, the transaction moves from the AOR back to the TOR, then departs via VTAM. z/OS system services (including WLM) are used in all the regions, but the transaction is classified by WLM when it is in the TOR for the first time.

z/OS Resource Measurement Facility Report Analysis has more information about understanding RMF reports.



dfht3sn.html | Timestamp icon Last updated: Sunday, 4 June 2017