9. PROCESSING › 9.1 Processing Considerations

9.1 Processing Considerations

The DAY080 step (of the Daily Update job) processes VM data.
The input data may reside in any sequential file, as defined
by INPUTVMC.

CP Account Data

CP account data consists of 80-byte fixed-length records.
This data must be read from the VM spool. Then, it must be
transported to your z/OS system, which will be running
CA MICS.  The VM Data Transfer Program will perform this
function for you.

VM Monitor Data

In VM, the monitor data is written directly to disk or tape
by IBM's MONWRITE program or another application designed to
interface with the *MONITOR system service.  VM Monitor data
can be transferred to z/OS using the CA MICS VM Data Transfer
Program.  VM Monitor data must be extracted from the MONWRITE
format by the VM Data Transfer Program.

You may want to exclude portions of the raw data from
processing, particularly if event data is being collected.
Data for an entire domain, or particular record type within a
domain, can be excluded by using the VM Data Transfer Program
or by using the USRSEL exit provided in CA MICS. For example,
you may choose to exclude data from the domain 2 (Scheduler)
record, types 1 through 6 and 8 through 10; the domain 4
(User) record, types 8 through 10; and the domain 7 (Seek)
record.

Be careful when excluding records, because certain types of
data are needed to properly process input.  For example,
Domain 1 (Monitor) data cannot be excluded, because it is
necessary for obtaining fundamental configuration data.

Chapter 6 includes a more detailed discussion of monitor
collection and data inclusion/exclusion considerations for
VM.

U300 ABEND

The U300 abend in CA MICS can be issued from two locations
within the CA MICS Analyzer Option for VM/CMS Daily update:

1.  VMCACTFI - at the end-of-input, for all systems providing
    CP account data

2.  VMCMXAFI - at the end-of-input, for all systems providing
    VM Monitor data

If any of the input processes (CP account or VM monitor)
encounters a situation in which no data or insufficient data
has been read and kept, a U300 abend occurs.  BOTH input
processes must read and keep enough data to satisfy the test.
For more information, see the Abnormal Terminations
documentation in chapter 4 in the PIOM.