6. DATA SOURCES › 6.1 Data Collector Options and Operation › 6.1.3 Velocity Monitor Data Options

6.1.3 Velocity Monitor Data Options

Velocity monitor data is placed in the MONDCSS saved segment
after it is prepared by CP. The Velocity Software application
program, ESAWRITE, which resides on another virtual machine,
retrieves the monitor data from the saved segment after it
receives an IUCV interrupt from the monitor.  The IUCV
interrupt tells ESAWRITE the type and the location of the
data.  After ESAWRITE has accessed the data and processed it,
ESAWRITE issues an IUCV reply to tell CP it is done with
processing the data.  ESAWRITE will write the data to either
disk or tape.  ESAWRITE will reconnect to *MONITOR every hour
so a current set of configuration data can be extracted.

The output file from ESAWRITE is written as VB 1248 record
length records, which is a format accepted by the CA MICS
Analyzer Option for VM/CMS.  The VM File Transfer Program
(FTP) can be used to transmit the ESAWRITE output to z/OS for
processing by the CA MICS Analyzer Option for VM/CMS.

The CA MICS Analyzer Option for VM/CMS requires certain
Domain 1 configuration records to process to maintain
database file integrity and report any exceptions if they
occur.  If a subset of monitor records is being extracted
from the ESAWRITE output monitor file, review Section 6.2.6
to ensure you are selecting the required Domain 1
configuration records.

To set the options for monitor data collection, refer to
Velocity Software documentation.