6. DATA SOURCES › 6.3 CA MICS SMF Requirements and Considerations › 6.3.4 SYSOUT Considerations › 6.3.4.2 NJE SYSOUT › 6.3.4.2.1 NJE SYSOUT and CA MICS Configurations

6.3.4.2.1 NJE SYSOUT and CA MICS Configurations

This section discusses how to maximize accountability for NJE
routed SYSOUT where the SYSOUT both originates and prints at
MVS nodes whose SMF files are input to a single CA MICS unit.

SYSOUT originating from non-MVS nodes, such as VM, is
discussed in the next section.  SYSOUT originating at an MVS
node and routed to a non-MVS node for printing does not
produce SMF records, and is therefore not captured or
processed by this CA MICS product.

The easiest way to maximize accountability for NJE routed
SYSOUT is to ensure that all SMF data from all the various
interconnected MVS nodes is fed into a single CA MICS unit.
This will ensure that the CA MICS unit will always encounter
the execution records for the activity that produced the
print.

   NJE Network:  Two Different MVS Nodes Feeding One CA MICS
                 Unit

               MVS                         MVS
              NODE A                      NODE B
         +-------------+         +----------------------+
         |  JES SPOOL  |         |       JES SPOOL      |
         |   +------+  |         |  +------+  +------+  |
         |   | SYSA |  |<- NJE ->|  | SYSB |  | SYSC |  |
         |   +---|--+  |         |  +---|--+  +---|--+  |
         +-------|-----+         +------|---------|-----+
                 |                      |         |
                 | SMF +---------+  SMF |     SMF |
                 +---->| CA MICS |<-----+---------+
                       |  UNIT   |
                       +---------+


NJE SYSOUT WHERE CA MICS PROCESSES THE EXECUTION RECORDS

Even when all SMF data from MVS nodes involved in NJE SYSOUT
transmission is fed into a single CA MICS unit, there are two
problems that complicate the association of the execution
records with the SYSOUT records.

The most common problem occurs because CA MICS discards the
suspended records for a job when the SMF type 26 execution
node purge record is encountered.  Any NJE-routed SYSOUT
printed after the execution node record is written and
processed by CA MICS will not be associated with the
execution records from the job.

The solution to this accountability problem is to activate
the Job Account Derivation Hold (BATSFH) file.  The BATSFH
file is described in Section 5.2.10.  To activate the file,
use the SFHLIMIT option statement as discussed in Section
7.3.1.4.  The BATSFH file contains the accounting fields used
by your account code exit routine (ACCTRTE).  An observation
is written to the BATSFH file when CA MICS is about to
discard the execution records for the job.  The BATSFH
observations are available for a site-specified number of
daily update cycles to provide accountability for NJE-routed
SYSOUT.

The second problem involves the timing of SMF dumps.  In the
NJE network shown above, consider the case where SMF is
dumped on SYSA.  Immediately after SMF dumping is completed,
a job runs on SYSA and transmits SYSOUT to SYSB via NJE.  The
SYSOUT immediately prints at SYSB and then SMF is dumped at
SYSB.

In this scenario, CA MICS will encounter the SMF type 6
output writer record(s) and SMF type 26 non-execution node
purge record before it encounters the execution records for
the creating job.  Because SMF was dumped at SYSA before the
job execution that created the SYSOUT, CA MICS will not
encounter the job's execution until the next daily update
cycle.  The SMF type 6 records from SYSB will not have the
job information available to set ACCTNOx account codes in
your account code exit routine.

The solution to this problem is to specify a NOSUSPENDNJE
option statement.  The SUSPENDNJE/NOSUSPENDNJE statement is
fully discussed in Section 7.3.1.2.  When CA MICS encounters
NJE SYSOUT records for the first time and the NOSUSPENDNJE
option is in effect, the NJE SYSOUT SMF records are
immediately suspended for one update cycle without writing
any BATSPL observations.  This allows an additional daily
update cycle for the execution records from the creating job
to be dumped and processed by CA MICS.

NJE SYSOUT WHERE CA MICS ONLY PROCESSES THE SYSOUT RECORDS

Accountability is limited for NJE SYSOUT originating from an
MVS node that is not included in the SMF input files because
the CA MICS unit processing the NJE SYSOUT records will never
encounter the execution records from the creating job.  The
accounting options for this configuration are discussed in
the next section.