|
|
|
You use the TSO User Session Trace Report when a TSO user
complains of erratic response time problems and the TSO
Activity, TSO Command Activity, and TSO User Ranking reports
do not provide the information necessary to solve the
problem. The TSO User Session Trace Report presents detailed
performance information that you can use to resolve most
complaints of this type.
The TSO User Session Report provides a clear picture of what
a user did and what kind of service the user received during
each CA TSO/MON PM recording interval. The report lists the
TSO commands executed by the user in the sequence in which
each unique TSO command was executed. This lets you
determine a general sequence of events. The report shows
response times classified as either short, medium, or long.
The report also provides a summary of the logon and logoff
times for each TSO user being audited. This is a quick way
to obtain the time periods during which the TSO users
examined were actually logged on to TSO. In addition, the
report provides terminal identification of the TSO terminal
associated with each session so that you can determine the
origin of a TSO session.
The report also provides all response distributions and
presents a complete scenario of TSO resources consumed or
generated by the user. Finally, the program that generates
the User Session report calculates a set of ratios based on
the data presented under "RESOURCES:".
Figure 3-19 illustrates a TSO User Session Trace Report.
INQUIRY ID:
TSOLXM - User Session Trace
DATA SOURCE (File/Timespan):
TSOTSU - DETAIL
TSOTSC - DETAIL
RUNNING THE REPORT
Run this report under MICF, selecting the following runtime
parameters:
o database ID to be processed
o range of CA MICS file cycles to be processed
o SYSID values to be included
o range of dates to be processed
o time range to be processed
o zone values
o user IDs to be included
o user IDs to be excluded
o terminals to be included
o terminals to be excluded
o performance group numbers or workload manager service
classes to be included
o performance group numbers or workload manager service
classes to be excluded
o report format options
TSOLXM CA MICS IS/MSS PAGE 1 YOUR COMPANY NAME TSO AUDIT REPORT (SYSTEM TSOP) USER SESSION TRACE DATE SELECTION: NONE SPECIFIED CURRENT DATE/TIME: 12JUN08/17:29 OPTIONS: AUDIT=USER=(SESSION=(LOGONOFF COMMANDS RESPONSE RESOURCES RATIOS)) DATA LEVEL: 51 TIME=(10:00-12:00) USER=(ABC45) ******************************************************************************************************************************** ABC45 NO LOGON INDICATION - INTERVAL START: 01FEB08:09:59:59.54 ABC45 PROCESSING INTERVAL - START: 01FEB08:09:59:59.54 END: 01FEB08:10:04:59.57 VTAM TERMINAL: ABC30001 SPFPANELS: VIOFSCRN 2 TOTAL PANELS: 2 COMMANDS: DELETE 2 FIND 1 RFIND 6 SPFEDIT 1 TOTAL COMMANDS: 10 RESPONSE: D I S T R I B U T I O N P E R C E N T A G E S W I T H I N CATEGORY EVENTS AVERAGE 0.25S 0.50S 1.00S 2.00S 5.00S 10.00S 30.00S -------- ------ ------- ------ ------ ------ ------ ------ ------ ------ SHORT 23 0.30 65.2 87.0 91.3 100.0 100.0 100.0 100.0 MEDIUM 2 2.23 0.0 0.0 50.0 50.0 100.0 100.0 100.0 TOTAL 25 0.45 60.0 80.0 88.0 96.0 100.0 100.0 100.0 RESOURCES: TCB CPU TIME 0.84 ENDED SRM TRANSACTIONS 25 NON-TERMINAL I/O 169 SRB CPU TIME 0.16 SERVICE UNITS 7110 TERMINAL READS 25 COMMAND RESIDENCY 10.80 PERFORMANCE GROUP 2 TERMINAL WRITES 25 TERMINAL CHARS READ 147 TERMINAL CHARS WRITTEN 22131 TOTAL SWAPIN TIME 0.29 NUMBER SWAPIN EVENTS 4 TOTAL SWAPIN DELAY TIME 0.01 NUMBER SWAPIN DELAY EVENTS 4 TOTAL 2K BYTES SWAPPED 718 MAXIMUM 2K BYTES SWAPPED 198 NUMBER SWAPOUTS 4 NUM. NETWORK DELAY EVENTS 0 AVERAGE NETWORK DELAY 0.00 RATIOS: % TCB CPU/ELAPSED 0.3 COMMANDS/SECOND 0.03 NON-TERM I-O/SECOND 0.56 % TOTAL CPU/ELAPSED 0.3 TRANSACTIONS/SECOND 0.08 NON-TERM I-O/TCB CPU SEC 200 % SRB CPU/TCB CPU 19.5 SERVICE UNITS/SECOND 23.70 TERM READS/SECOND 0.08 TERM CHARS READ/SECOND 0.49 AVG MSG LENGTH READ 5.88 TERM WRITES/SECOND 0.08 TERM CHARS WRITE/SECOND 73.76 AVG MSG LENGTH WRITTEN 885.2
Figure 3-19. TSO User Session Trace Report
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |