5. FILES › 5.2 TSO Information Area Files › 5.2.8 TSO Batch Data Set Name File (TSO_BD) › 5.2.8.3 Usage Considerations

5.2.8.3 Usage Considerations

This section identifies any special considerations or
techniques related to using the TSO_BD file.  Additionally, a
retrieval example is 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.  This file is similar to the TSOTSI and TSOTSA files
    in that observations are generated only upon
    execution of TSO commands.

2.  The TSO_BD file is relevant in the DETAIL time-span
    only.

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

Retrieval Example
-----------------


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.  Identify the batch TSO job(s) that deleted member
    DUMP from SYS2.PROCLIB.

    DATA;
    SET &TSOX..TSO_BD01;
    IF DSNAME='SYS2.PROCLIB' AND MEMBER='DUMP' AND
       TSAMFUNC='D';
    PROC PRINT;VAR ENDTS USER;
    RUN;