TranView displays activity in terms of the individual transactions detected. It divides the activity of these transactions into six major groups and displays the percentage of time each transaction spends in one of these groups. A description for each field in TranView follows.
Name of a transaction detected by CA Mainframe Application Tuner during the monitoring of an IMS or CICS region.
"X" indicates the transaction has been tagged for analysis.
Number of times the transaction completed processing during the monitored period.
Average time (in seconds) for this transaction during the monitored period.
Cumulative CPU seconds for this transaction during the monitored period.
Average CPU time required for this transaction during the monitored period.
Percentage of time during the monitored period that the CPU was actively processing the monitored transaction.
Percentage of time during the monitored period that the transaction was delayed because of an I/O request.
Percentage of time during the monitored period that was not attributable to any of the categories known to CA Mainframe Application Tuner.
Summation of the categories of delay.
Graphical representation of the total delay associated with the transaction.
Total amount of CPU time in service units used by this transaction.
CA Mainframe Application Tuner calculates this amount by using the following formula:
(Tot CPU * 16000000) / CPU Adjustment Rate
The CPU Adjustment Rate can be seen on the OverView report.
Average number of CPU Service Units required to process a transaction.
CA Mainframe Application Tuner calculates this amount by using the following formula:
(Avg CPU * 16000000) / CPU Adjustment Rate
The CPU Adjustment Rate can be seen on the OverView report.
CA Mainframe Application Tuner gives you flexibility when monitoring a job; you can specify user IDs, terminal IDs, and transaction codes, or use generic transaction codes on the CICS Monitoring Criteria panel to focus the monitoring on specific units of work. The data displayed in TranView represents the selected transaction only. Refer to "Additional monitoring criteria" on page 80 to see how to specify transaction code information.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |