9. PROCESSING › 9.1 Processing Considerations

9.1 Processing Considerations

The CA MICS Network Analyzer update process is unique to CA
MICS because it involves reading two input files from
different DD statements.  The DAILY update process reads the
INPUTSMF DD statement processing SMF type 28, 37, 39, 118,
and 119 records.  Then it switches to the INPUTSNT DD
statement and processes the NPM Session Statistics Detail
records.

Checkpoint Update
-----------------

To distinguish the input of CA MICS Network and permit you to
invoke the SELECT or FORCE functions for any of the input
data sources, an entry is made in the CA MICS checkpoint
file, prefix.MICS.CHECKPT.DATA, for each source and unique
SYSID.  A typical checkpoint file entry after the DAY056
update step would look like this:

SYSA SNT NPDA 20AUG05:12:49:29.33 20AUG05:16:17:57.41
SYSA SNT NPMN 20AUG05:10:29:49.41 20AUG05:16:08:29.54
SYSA SNT NLDM 20AUG05:03:00:00.67 20AUG05:08:00:04.88
SYSB SNT NPDA 21AUG05:18:37:06.44 21AUG05:18:44:04.88
SYSC SNT NPMS 21AUG05:06:29:45.00 21AUG05:18:35:46.00
SYSC SNT TCP  10NOV05:08:24:93.00 10NOV05:23:59:99.91

The first three entries are for SYSID SYSA and include data
from NetView Hardware Monitor/NPDA, Network Performance
Monitor Network (NPMN) (network), and NetView Session
Monitor/NLDM.  The fourth entry is for SYSID SYSB and
includes only data from NetView Hardware Monitor/NPDA.  The
fifth entry is from SYSID SYSC and its input is from NetView
Performance Monitor Session (NPMS) data.  The last entry is
from SYSID SYSC and its input is from IBM TCP/IP Telnet, FTP,
and Stack data.

Select and Force
----------------

Should it be necessary to use the SELECT or FORCE option
(described in Section 4.3 of the PIOM), ensure that all
required data is selected.

Missing Data
------------

It is possible (even likely in some environments) that there
will be days in which there is no data for some of the SYSIDs
from all of the monitors involved.  In these cases, the
system administrator should ensure that this is intentional
and data has not been lost due to software or operational
problems.  The DAY056 step processes normally if any input
data is received for any SYSID defined to this data base
unit.  See Chapter 10 of this guide for an exit example that
you could use to detect a situation in which data is missing
for expected SYSIDs and data sources (_USRIHL exit).

If it is possible to have update runs where there is no data
from any SYSID, specify SYSPARM=NODATA on the EXEC statement
for the DAY056 step to prevent a USER 300 ABEND.