6. DATA SOURCES › 6.2 Record Descriptions
6.2 Record Descriptions
The TSO/MON records shown in Figure 6-1 are used by the
CA MICS TSO Analyzer. The figure shows when each record is
written and what each record contains.
Two types of records are generated by TSO/MON: System
Records and Command Records. A brief description of these
records follows. You can find more detailed information in
the TSO/MON Technical Reference Guide.
+--------------+------------------+-------------------------+
|Record name | Written | Record contents |
+==============+==================+=========================+
| System (200)| For every | TSO System Resource |
| | TSO/MON | Usage |
| | recording | User Resource Usage |
| | interval | TSO Performance |
| | | Information |
| | | TSO Dynamic Resource |
| | | Usage |
| | | WLM Goal Mode Usage |
+--------------+------------------+-------------------------+
| Command (199)| At the end of | Performance and Resource|
| | each interactive | Usage Information for |
| | command execution| Selected Commands |
| | or checkpoint | |
| | interval | |
+--------------+------------------+-------------------------+
Figure 6-1. TSO/MON Record Descriptions
TSO/MON System Record (Type 200)
---------------------------------
This record describes system and user activity over the
installation-defined processing interval (a time period).
Because this record could become very large with many
concurrent users, it is split into multiple physical records
when it exceeds a set maximum length. To obtain system level
statistics, the user level information in each physical
record is aggregated and then combined with similar data from
any other system records that describe the same interval.
The System Record is a variable length physical record
comprised of logical sections. The System Record always
contains both TSO system status and user activity
information. The exact size of a physical record depends on
the number of users logged on to TSO during the interval.
The System Record consists of:
o One System Control Block (SCB) section that contains
system level information. Half-word offsets in the SCB
point to the EXCB, PGB (not running the WLM in goal mode),
or WSCB (running the WLM in goal mode), and the first UCB.
The offset value of the EXCB and the PGB or WSCB is zero
in the second and subsequent System Records describing the
same time period. The offset value for the first UCB is
zero when no user activity occurs in the interval. There
is an SCB section in every System Record describing the
same time period.
o One Exception Control Block (EXCB) section that contains
system exception information. There is only one EXCB for
each processing interval, and it is in the first physical
record. There is no EXCB in the second and subsequent
System Records describing the same time period.
o For TSO/MON releases not running the WLM in goal mode, one
Performance Group Block (PGB) section that contains the
performance groups and service values used during the
processing interval. This block is variable length and
contains one to ten entries. There is at most one PGB for
each processing interval, and it is in the first physical
record. There is no PGB in the second and subsequent
System Records describing the same time period. The PGB
is appended to the System Record only if the Service Unit
response type option was selected.
o For TSO/MON releases running the WLM in goal mode, one
Workload Manager Service Class Block (WSCB) section that
describes the workload manager policy used during the
measurement interval. It contains the policy name, the
number of service classes in the policy, and, for each
service class, information about performance periods.
o One User Control Block (UCB) section for each user logged
on during the interval. Each UCB has a half-word offset
field which points to the next UCB and a half-word offset
field which points to the User Control Block Extension
(UCBE) for the current UCB. The value of the 'next ucb'
pointer is zero in the last UCB section in a record. A
flag byte within the UCB identifies the source of the
information as batch TSO or online TSO.
o For TSO/MON releases prior to Version 6, one Command
Control Block (CCB) section for each unique command issued
by the user during the interval. The UCB contains the
number of unique commands issued in the interval. CCBs
are appended to UCBs only for TSO users who issued
commands during the interval.
o One User Control Block Extension (UCBE) section for each
user logged on during the interval. Each UCBE has a half-
word offset field which points to the first Full Command
Block (FCB). The value of this offset is zero when there
is no FCB section.
o One Full Command Block (FCB) section for each unique
command, each user dialog program, each user dialog panel,
and the name of each CLIST invoked by the user during the
processing interval. The UCBE contains a count of the
number of FCB sections. FCBs are appended to the UCBEs
only if the Full Command Name option was specified in the
TSO/MON Options Table.
o One Accounting Segment (ACT) is appended to each UCBE
after any FCBs if ACCOUNTING=YES is specified in the
TSO/MON Options Table. Each accounting segment is
variable in length and is an exact duplicate of the
accounting information available in the SMF type 35, or
type 30 records.
o One Dynamic Resource Usage Block (DRU) section for each
command executed within the interval. The SCB contains a
half-word offset field which points to the first DRU and a
half-word count field which contains the number of DRU
segments present in the System Record. The DRU segments
are contained in 1 or more System Records following the
last UCB containing System Record. The DRU segment is
optional and will be present only if TSO/MON is instructed
to record all command usage.
Each separate physical record consists of one SCB (see
description) and zero or more UCB/CCB/UCBE/FCB/ACT and DRU
logical sections. There can be many physical records per
interval. For a given processing interval, the EXCB and PGB
or WSCB segments are present only in the first physical
record.
The record generation date/time stamps of these physical
records are identical. The length-of-processing-interval
field (TSMSINTV) of the SCB is zero in all physical records
but the first. From the standard SMF header (starting at the
system indicator field) down through the zero TSMSINTV field,
the second and subsequent physical records for the same
processing interval are identical. The next field in the SCB
is named TSMSSEGN. It increments by one for each physical
record, starting at one.
TSO/MON Command Record (Type 199)
----------------------------------
When the Command Record Generation option is specified in the
TSO/MON Options Table, a command record is written to SMF
each time a TSO user issues a command or subcommand that the
installation has selected for recording. An installation
selects commands for which recording is desired by specifying
DETAIL=COMMAND or PROGRAM in the TSO/MON Commands Table entry
for the individual commands. Coding DETAIL=COMMAND in the
Commands Table entry indicates that a command record with no
program information is to be generated. Coding
DETAIL=PROGRAM indicates that a program name is to be
provided in the command record. If the Data Set Name
Recording option is also specified in the TSO/MON Options
Table, then coding DETAIL=PROGRAM in the Commands Table entry
indicates that a command record containing program name and
data set name is to be generated.
Command Records contain resource usage measurements, response
and swap statistics, and TSO terminal characteristics for
each invocation of the selected commands. A flag byte in the
record indicates whether the record was generated as a result
of a command executing under batch TSO or online TSO.
If the checkpoint option is specified in the TSO/MON Options
Table, a checkpointed command record is written for long-
running TSO commands each time the checkpoint number of
processing intervals is exceeded.
The DSname and member blocks are present only if a positive
integer value was specified for the DSNAME=nnn option in the
TSO/MON Options Table and DETAIL=PROGRAM was specified for
this particular command in the TSO/MON Commands Table (see
above). The length of this additional information varies and
could theoretically reach 32760 bytes in length (including
the standard portion of the Command Record).
The information below is repeated for as many data sets as
are accessed in the invocation of the command. For example,
if the command is CALL, then only one data set name and one
member name will be appended to the Command Record if the
data set name information is available in the command buffer.
If the command is SPFEDIT (PDF Option 2), the data set names
and member names are appended to the end of the Command
Record as they are accessed during execution of the SPFEDIT
Command. PDF Functions 1 (BROWSE), 2 (SPFEDIT), and 3.x
(UTILITIES) are supported by the SPF Interface for data set
name capture.
The accounting segment is present only if ACCOUNTING=YES has
been specified in the TSO/MON Options Table.
