6. DATA SOURCES › 6.1 Data Collection and Transport to CA MICS › 6.1.1 Data Collector Operations › 6.1.1.2 VMS MONITOR Data Collection

6.1.1.2 VMS MONITOR Data Collection

To start VMS MONITOR, enter:

    MONITOR / RECORD=filename / NODISPLAY / INTERVAL=interval
            / ENDING=23:59   ALL_CLASSES

where

    filename

          is the name of the data set on which the VMS
          MONITOR data will be recorded.

    NODISPLAY

          indicates that a data file will be created rather
          than generating terminal displays.

    interval

          is the number of seconds between VMS MONITOR
          recordings.

          It is difficult to specify a recording interval
          that is correct for all situations.  In a fairly
          well-tuned system, an interval of 20 seconds is
          reasonable for ongoing performance monitoring.
          When analyzing system performance problems, the
          recording interval must be made much shorter.  When
          using the PROCESS file for system diagnosis, a
          recording interval of 2 to 5 seconds is suggested.
          When using the MODES file, an interval of 10
          seconds is appropriate.  When analyzing file system
          problems with the RMS file, an interval of 1 to 3
          seconds is required.

          We recommend that you also consider the CA MICS
          database space requirements in choosing a
          reasonable interval value for data input to CA
          MICS. While an interval of 20 seconds may be useful
          for specific performance studies using VMS MONITOR
          in real-time, a more reasonable value for
          historical data summarization and retention
          purposes should be considered.  Too small an
          interval generates so much data that its use is
          prohibitive.  We suggest you start with a 10 or 15
          minute interval (600 to 900 seconds) when setting
          up data collection for CA MICS use. You can adjust
          this setting after you have determined the data
          transfer and storage requirements from a low volume
          data flow.

    ENDING=23:59

          indicates that the recording should stop and the
          data file should be closed at midnight.  The system
          operator should rename the file and restart VMS
          MONITOR.

    ALL_CLASSES

          indicates that all data record types should be
          created.

    This command starts recording VMS MONITOR data in
    specified intervals until 23:59 and then stops recording.
    The binary file name in the RECORD subcommand is the file
    that will be passed over to MVS for the CA MICS DAILY run
    for VMS MONITOR data.  When this file is passed to MVS,
    it must be in its original ASCII format (use binary
    transfer) and must be created on the MVS system with
    DCB=(RECFM=VB,LRECL=32752,BLKSIZE=32756).


Sample Procedure:

    At midnight, submit a command procedure to each cluster
    node that cleans out a holding area, stops the VMS
    MONITOR, moves the VMS MONITOR files to the clean holding
    area and restarts the VMS MONITOR, and passes the data in
    the holding area to MVS for processing in the CA MICS
    daily run.