5. FILES › 5.2 Batch Information Area Files › 5.2.4 SMF User TSO Activity File (BAT_TS) › 5.2.4.3 BAT_TS Usage Considerations
5.2.4.3 BAT_TS Usage Considerations
Special considerations or techniques related to using the
BAT_TS file are provided below.
1. The identity of the TSO session accounted for in the
BAT_TSnn files in the DETAIL time-span is given by the
following:
JOB - Jobname (userid)
RDRTS - Reader Time Stamp (logon time-stamp)
2. This file is physically identical to the BATPGM file and
has the same data element names, labels, and formats.
3. The contents of the following data elements depend on the
CA MICS options and exits used at your site.
PGMWPETM - Pseudo Elapsed Time
PGMWSRU - System Resource Units
PGMCOST - Processing Charges
4. The PGMINTVL data element is extremely important when
processing the BAT_TS file in the DETAIL time-span and
SMF interval accounting is used for TSO sessions. It is
important to understand that when a TSO session has been
interval accounted that the data maintained in the BAT_TS
file is a record per interval and not a single record for
the total TSO session.
PGMINTVL='SE24' standard batch full program record built
from SMF type 30 subtype 4 step record.
PGMINTVL='SE22' standard batch interval record built from
SMF type 30 subtype 2 delta record.
PGMINTVL='SE23' standard batch end interval record built
from SMF type 30 subtype 3 delta record.
5. The ENDTS and STARTTS, when appearing in the MONTHS time-
spans, bound the span of time over which the data has
been summarized, with STARTTS being the lowest date and
time, and ENDTS the highest date and time for the data
summarized. The data elements STARTTS and ENDTS have
different meanings when used in the DETAIL time-span
versus their role in the MONTHS time-spans. Their
purpose in DETAIL is described below:
STARTTS represents program initiation time
ENDTS represents program termination time