5. FILES › 5.2 TSO Information Area Files › 5.2.7 TSO Batch User Command Counts File (TSO_BC) › 5.2.7.3 Usage Considerations

5.2.7.3 Usage Considerations

This section identifies special considerations or techniques
related to using the TSO_BC 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_BC file, refer to data base file
    tailoring discussion in Chapter 6 of the CA MICS System
    Modification Guide.

2.  The data element TSCCOST (Processing Charges) obtains its
    value from code you write in the user exit _USRSTSC.

3.  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.

4.  STARTTS and ENDTS in the MONTHS time-span bounds 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.

5.  The data element COMPRIM identifies the type of the
    command (primary, TSO EDIT subcommand, etc.) based on the
    order in which the TSO/MON commands table has been
    defined.

6.  The data element COMMAND contains a value of '*UNKNOWN'
    if the command's abbreviation, COMABB, does not have a
    corresponding match in the TSO/MON Commands Table.


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.  Print the users who used the TSO EDIT command yesterday:

    DATA;
    SET &TSOX..TSO_BC01;
    IF COMMAND='EDIT';
    PROC PRINT; VAR SYSID USER ENDTS TSCCOUNT;
    RUN;

2.  Display what commands user COM001 used for the last two
    months and group them by command type (e.g., SPF, TSO,
    primary, etc.):

    DATA FILE1;
    SET &TSOM..TSO_BC01 &TSOM..TSO_BC02;
    IF USER='COM001';
    PROC SORT DATA=FILE1; BY COMPRIM COMMAND;
    PROC FREQ; TABLES COMMAND; BY COMPRIM;
    RUN;

3.  Total the number of commands which are being executed and
    are not defined in the TSO/MON Commands Table:

    DATA FILE1;
    SET &TSOM..TSO_BC01 END=EOF;
    IF COMMAND='*UNKNOWN'THEN COUNTX+TSCCOUNT;
    IF EOF THEN PUT COUNTX=;
    RUN;