5. FILES › 5.2 TSO Information Area Files › 5.2.10 TSO Batch User Activity File (TSO_BU) › 5.2.10.3 Usage Considerations

5.2.10.3 Usage Considerations

This section identifies any special considerations or
techniques related to using the TSO_BU file.  Additionally,
retrieval examples are provided to help you use this file.

Special Considerations/Techniques
---------------------------------

Before using the TSO batch files for accounting or capacity
planning, carefully consider these impacts:

o Data duplication can occur because resource utilization
  information for batch TSO jobs appears in both the CA MICS
  TSO Analyzer batch files and the Batch Information Area
  files of the CA MICS MVS Batch and Operations Analyzer.

  Please contact CA MICS Product Support before using the TSO
  batch files for these purposes.

o Accounting Considerations

  If both the TSO batch files and the MVS Batch and
  Operations Analyzer files are used for accounting, the
  redundant resource utilization data will result in
  duplicate accounting charges unless you account for
  different resource items from each information area.

  For example, if you account for command count from the TSO
  batch files and CPU time from the MVS Batch and Operations
  Analyzer files, you will not incur duplicate charges.

  If you charge for the same resource item (such as CPU time)
  in both information areas, you end up with duplicate
  charges to the same user.

o Capacity Planning Considerations

  If both the TSO Analyzer's batch files and the MVS Batch
  and Operations Analyzer's Batch Information Area files are
  used for capacity planning purposes, the duplication of
  resource data can skew workload utilization information.

  Consequently, do not use the TSO Analyzer's batch files for
  capacity planning purposes.

  Please note that this recommendation applies only to the
  batch files of the CA MICS TSO Analyzer and not to the
  online-oriented files.

1.  To activate the TSO_BU file, refer to data base file
    tailoring discussion in Chapter 6 of the CA MICS System
    Modification Guide.

2.  To populate account code data elements (TSOACTn),
    a. code the TSOACCT and TSOACRT parameters as described
       in sections 7.2.1 and 7.2.2 of this guide.
    b. change the COMP statement in TSOGENIN as described in
       section 7.2.3 of this guide.

3.  The following data elements only have meaning when using
    the TSO_BUnn file in the DETAIL time-span.  They lose
    significance once summarization has been performed.
    These data elements should only be referenced when using
    the TSO_BUnn file in the DETAIL time-span.

    PERFGRP  - Performance Group Number
    ASID     - Address Space Identification
    LOGPROC  - Logon Procedure Name
    LOGTS    - LOGON Time-stamp
    TSUSOPTS - Response Option Flags

4.  The data element TSUCOST (Processing Charges) obtains its
    value from code you write in the user exit _USRSTSU.

5.  The following data elements are user-defined or option
    dependent, and they should be used within the frame of
    reference of the option's definition.

    CA MICS PARMS SYSID
        CPUMODEL - CPU Model Identification
        TSUCPUNI - Instructions Executed

    TSO/MON Options
        TSMRVAL1-TSMRVAL8 - Response Distribution Limits
        TSMERESP - Excessive Response Time Threshold

6.  STARTTS and ENDTS in the DAYS, MONTHS, or YEARS
    time-spans bound the span of time over which the data has
    been summarized.  STARTTS is the lowest date and time,
    and ENDTS is the highest date and time, for the data
    summarized.

    In the DETAIL time-span, STARTTS represents TSO/MON
    recording interval start time and ENDTS represents
    TSO/MON recording interval end time.

Retrieval Examples
------------------


In the examples, a SAS macro variable is used to specify the
DDname part of the CA MICS file name. These macro variables
are a standard part of CA MICS and are available for all
files. The macro variable name has the form &diiit, where d
is the database identifier, iii is the information area
name, and t is the timespan.  For the examples, a database
identifier of P is used.  The identifier is installation
dependent, so you should find out what the identifiers are at
your installation.

1.  Total the service units used by department REG for
    last month by system (SYSID):

    %LET BY = SYSID YEAR MONTH;
    %LET BREAK = MONTH;
    DATA FILE1;
    SET &TSOM..TSO_BU01;
    IF USER=:'REG';
    DATA FILE1;
    SET FILE1;
    %_BUSUM;
    PROC PRINT; VAR SYSID YEAR MONTH USER TSUSERVU;
    RUN;

2.  Total the service units used by department REG for
    last month on all systems:

    %LET BY = YEAR MONTH;
    %LET BREAK = MONTH;
    DATA FILE1;
    SET &TSOM..TSO_BU01;
    IF USER=:'REG';
    PROC SORT DATA=FILE1; BY &BY;
    DATA FILE1;
    SET FILE1;
    %_BUSUM;
    PROC PRINT; VAR YEAR MONTH USER TSUSERVU;
    RUN;