5. FILES › 5.2 Batch Information Area Files › 5.2.15 System Address Space Activity File (BAT_SA) › 5.2.15.3 BAT_SA Usage Considerations

5.2.15.3 BAT_SA Usage Considerations

Special considerations or techniques related to using the
BAT_SA file are provided below.

1.  The identity of the system address space
    accounted for in the BAT_SAnn files in the DETAIL
    timespan is given by the following:

    JOB      - Jobname (userid)

2.  This file is structured similarly to the BATPGM file but
    contains fewer data elements.  This is because SMF type
    30 subtype 6 records, produced for address spaces that
    did not go through full function start, are missing
    several sections found in type 30 subtypes 2, 3, and 4.
    Additionally, sections that are present in the type 30
    subtype 6 record contain blanks or zeros in many of the
    raw data fields.  For example, Reader Time Stamp (RDRTS)
    is not present.  To provide compatibility with other step
    level files CA MICS calculates a value for RDRTS that
    corresponds to the start time of the system address
    space.

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_SA.  Because only SMF type 30 subtype
    6 records are created for system address spaces/MVS.  It
    is important to understand that when an address space has
    been interval accounted that the data maintained in the
    BAT_OE file is a record per interval and not a single
    record for the total step or substep execution.

    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
    timespans, 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 timespan
    versus their role in the MONTHS timespans.  Their purpose
    in DETAIL is described below:

    STARTTS represents program initiation time
    ENDTS represents program termination time