6. DATA SOURCES › 6.3 Correlating Data Sources › 6.3.6 Ensuring All Required Input Data Is Present

6.3.6 Ensuring All Required Input Data Is Present

The CA MICS Network Analyzer Option is different from most CA
MICS components because it processes input data from more
than one source.  All input data is processed by the DAY056
step in the CA MICS DAILY job as part of the same process. By
reviewing the MICSLOG output of the DAY056 step of the CA
MICS DAILY job, you can determine exactly what SMF record
types and subtypes were present in the input data stream for
each of your z/OS or VM hosts.

Following CA MICS standards, if the data center fails to
provide input from ANY source, the DAY056 step will fail with
a U300 abend.  When you expect this problem but must run the
DAILY job anyway, SYSPARM=NODATA may be coded on the EXEC
statement of the DAY056 step to prevent the abend.

However, there is no parameterized provision in CA MICS to
cause a similar abend when data from one of the required
sources is missing, but data from other sources is present.

An example will help to illustrate the point.  It is
Corporation ABC's requirement that NPM Network (SMF Type 28
Record), NPM Session (SMF type 28 record), and NetView
Hardware Monitor/NPDA (SMF type 37 record) data be input to
the CA MICS Network Analyzer Option on a daily basis. If one
of these sources, such as the NPM Session data, is not
provided, the DAY056 step should fail so that the data may be
located and the update may be run with it.

To provide for this case, the user may code an exit routine,
_USRIHL, in which the Input History Log DETAIL File may be
examined at the end of DAILY processing.  This routine, and a
sample exit that provides this function, are documented in
Chapter 10.