5. FILES › 5.2 Batch Information Area Files › 5.2.12 Measured Usage Address Space File (BATMUA) › 5.2.12.3 BATMUA Usage Considerations

5.2.12.3 BATMUA Usage Considerations

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

1.  The identity of the software product measured is uniquely
    determined by the following:

    MUPROD      - Product
    MUVER       - Product Version
    MUPRODID    - Product ID
    MUOWNER     - Owner/Vendor
    MUQUAL      - Product Qualifier

2.  Because the source for BATMUA observations is SMF type 30
    step or interval records, there is a partner observation
    in one of the CA MICS step-level files (BATPGM, BAT_TS,
    BAT_ST, BAT_TP, BAT_OE).  The following data elements
    allow you to uniquely identify the CA MICS step-level
    partner observation:

    ENDTS       - End Time Stamp
    STARTTS     - Start Time Stamp
    RDRTS       - Reader Time Stamp
    JOB         - Job Name
    STEPNUM     - Step Number
    JESJOBNO    - JES Job Number
    PROGRAM     - Program Name
    PGMINTVL    - Interval Measurement Type
    PGMTYPE     - Program Execution Type (Batch, TSO, STC,
                  etc.)

    Note that PGMTYPE in the BATMUA file directs you to the
    appropriate CA MICS step-level data base file:

    PGMTYPE=1   - BATPGM (Batch)
    PGMTYPE=2   - BAT_TS (TSO)
    PGMTYPE=3   - BAT_ST (Started Task)
    PGMTYPE=4   - BAT_TP (APPC/MVS TP)
    PGMTYPE=5   - BAT_OE (Open Edition/MVS)

3.  The BATMUA usage measurements consist of SRB and TCB CPU
    time as well as a general purpose measurement field that
    can be optionally populated by a vendor's software
    product:

    MUATCBTM    - Product TCB CPU Time
    MUASRBTM    - Product SRB CPU Time
    MUACPUTM    - Product CPU (SRB+TCB) Time

    MUAPDATA    - Product Specific Resource Data
    MUAPTYPE    - Product Specific Resource Data Type

4.  CA MICS Accounting and Chargeback support is provided for
    the BATMUA file.  Note that the SRB, TCB, and CPU time
    measurements recorded in the BATMUA file represent a
    subset of the CPU time measurements recorded in data
    elements PGMSRBTM, PGMTCBTM, and PGMCPUTM in the partner
    step-level CA MICS observation. This makes the BATMUA
    file ideal for surcharging for the use of specific
    software products, but you must be aware that the CPU
    time has also been recorded in the step-level file
    observations.

5.  An MULC-registered software product can be accessed
    multiple times within a given step or interval.  Each
    product use results in a separate usage data segment in
    the SMF type 30 step or interval records.  CA MICS
    consolidates multiple segments representing the same
    software product to one per step or interval.  In a
    DETAIL time-span data base observation, data element
    MUACOUNT (Product Execution Count) contains the number of
    times the product was accessed.

6.  The STARTTS and ENDTS values in DETAIL time-span BATMUA
    file observations are identical to the same data element
    values in the partner step level data base observation.
    They represent the start and end of the step or interval
    record that contained the usage data.