Previous Topic: 5.2.3.2 Data Elements List

Next Topic: 5.2.4 TSO User Interactive Usage File (TSOTSI)

5.2.3.3 Usage Considerations


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

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

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

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

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

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

5.  The data element COMMAND contains a value of '*UNKNOWN'
    if the command's abbreviation, COMABB, did 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 &PTSOX..TSOTSC01;
    IF COMMAND='EDIT';
    PROC PRINT; VAR SYSID USER ENDTS TSCCOUNT;

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 &PTSOM..TSOTSC01 &PTSOM..TSOTSC02;
    IF USER='COM001';
    PROC SORT DATA=FILE1; BY COMPRIM COMMAND;
    PROC FREQ; TABLES COMMAND; BY COMPRIM;

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

    DATA FILE1;
    SET &PTSOM..TSOTSC01 END=EOF;
    IF COMMAND='*UNKNOWN';
    COUNTX+TSCCOUNT;
    IF EOF THEN PUT COUNTX=;