5. FILES › 5.2 Batch Information Area Files › 5.2.11 Measured Usage Global File (BATMUG) › 5.2.11.3 BATMUG Usage Considerations

5.2.11.3 BATMUG Usage Considerations

Special considerations or techniques related to using the
BATMUG 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.  The identity of the system where the measurements were
    taken is determined by the following:

    SYSID System Identifier
    SYSPLEX Sysplex Name

    Note that SYSPLEX is not a sort/summarization key for the
    BATMUG file.  If your installation has two or more
    sysplexes and you use the same SYSID value for two or
    more different MVS images in separate sysplexes (e.g.,
    'SYSA' is an MVS image in SYSPLEX1 and also in SYSPLEX2)
    you should process the SMF data from each sysplex in
    separate CA MICS units, maintaining the separation of
    usage data from the two different systems.  An easy way
    to avoid this problem is to use unique SYSID names for
    all MVS images.

3.  Due to variations in how interval recording can be
    specified, multiple SMF type 89 usage data records can be
    produced for the same usage interval.  For more
    information about interval recording specifications for
    usage data collection, see IBM documentation.

4.  The SMF type 89 record contains two separate sets of
    start and end time stamps, one reporting interval start
    and end and the other reporting usage start and end.

    The interval start and end values are stored in MUGRISTS
    (Reporting Interval Start Time Stamp) and MUGRIETS
    (Reporting Interval End Time Stamp).  When MUGRIETS falls
    on an hour boundary, one second is subtracted from the
    value (e.g., 9:00:00 becomes 8:59:59).

    The usage start and end values are stored in STARTTS
    (Start Time Stamp) and ENDTS (End Time Stamp).

    STARTTS is always set equal to the usage start time
    unless the interval start time falls within the same hour
    as the usage start time.  In this case, STARTTS is set to
    the maximum value of the two start times.

    Similarly, ENDTS is always set to the usage end time
    unless the interval end time falls within the same hour
    as the usage end time.  In this case, ENDTS is set to the
    minimum value of the two end times.  Prior to the
    comparison and setting of ENDTS, both the interval and
    usage end times are adjusted downward by 1 second if
    their values fall on an hour boundary.

    The following examples illustrate how STARTTS and ENDTS
    are populated:

    Example 1:
                           SMF Type 89 Values

               INTERVAL START 8:00:00    USAGE START 8:00:00
               INTERVAL END   8:30:00    USAGE END   9:00:00

                         Resulting CA MICS Values

               MUGRISTS       8:00:00    STARTTS     8:00:00
               MUGRIETS       8:30:00    ENDTS       8:30:00

    Example 2:
                           SMF Type 89 Values

               INTERVAL START 8:30:00    USAGE START 8:00:00
               INTERVAL END   9:00:00    USAGE END   9:00:00

                         Resulting CA MICS Values

               MUGRISTS       8:30:00    STARTTS     8:30:00
               MUGRIETS       8:59:59    ENDTS       8:59:59

    Example 3:
                           SMF Type 89 Values

               INTERVAL START 8:45:00    USAGE START 8:00:00
               INTERVAL END   9:15:00    USAGE END   9:00:00

                         Resulting CA MICS Values

               MUGRISTS       8:45:00    STARTTS     8:45:00
               MUGRIETS       9:15:59    ENDTS       8:59:59

    Example 4:
                           SMF Type 89 Values

               INTERVAL START 8:45:00    USAGE START 9:00:00
               INTERVAL END   9:15:00    USAGE END  10:00:00

                         Resulting CA MICS Values

               MUGRISTS       8:45:00    STARTTS     9:00:00
               MUGRIETS       9:15:59    ENDTS       9:15:00

5.  IBM uses service units to quantify product utilization in
    the IFAURP usage report program.  The service units are
    computed during the report generation process as the
    product of CPU time (taken from SMF type 89 records) and
    a CPU time to service unit factor.  A table of
    machine-specific service unit factors is stored in the
    IFAURP report program.  These factors are not recorded in
    the SMF type 89 usage records.

    The BATMUG file contains the SRB, TCB, and total CPU time
    values.  The IFAURP report program reports the CPU time
    to service unit factor used for each system encountered
    in the SMF type 89 records.  You can, therefore, report
    on service unit utilization from the BATMUG file if you
    first pre-process the file to derive service units by
    multiplying MUGCPUTM by the appropriate factor reported
    in the IFAURP report for each system (SYSID).