6. DATA SOURCES › 6.1 Data Collector Considerations

6.1 Data Collector Considerations

Before installing the CA MICS TSO Analyzer, the CA MICS
System Administrator must address the data collection
considerations that TSO/MON requires.  These include space
considerations, record type identification, and the
availability of TSO/MON data sets.

   o  The TSO/MON Command Records provide the data for the
      TSO User Interactive Usage File (TSOTSI) and the TSO
      Data Set Name File (TSOTSA).  Thus, whenever TSO/MON
      detail command recording is changed to substantially
      increase the number of TSO/MON command records
      generated, the System Administrator must assess the
      space impact on these files.

   o  The SMF record type numbers used for the TSO/MON System
      and Command Records must be identical to those
      specified on the INPUTSOURCE statement in
      sharedprefix.MICS.GENLIB(TSOGENIN).

   o  Prior to TSO/MON Version 6, the daily execution of the
      data base update step reads the TSO/MON Command Table
      parameters from the source library specified in the
      TSMPARMS DD card of prefix.MICS.PARMS(JCLDEF), parses
      it, and translates the two character command
      abbreviations found in the input records back to the
      full command and subcommand name.  The TSO Analyzer
      uses standard TSO/MON routines to open and search the
      TSO/MON Command Table, which must be available during
      execution of the daily step.  These routines are
      specified on the TSMLINK DD card.

      At TSO/MON Version 6 and higher, the daily execution of
      the data base update step reads the full command name
      directly from the TSO/MON System and Command records,
      so parsing and translating command abbreviations from
      the TSO/MON Command Table is unnecessary.