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 NJE SYSOUT

The previous section discussed SYSOUT created and printed
within the same MVS node.  This section discusses NJE routed
SYSOUT.  NJE routed SYSOUT can originate from any other node
defined to an NJE network.  The originating node can be as
physically close as another spool defined within the same
physical processor, or as distant as a data center on the
other side of the earth.

NJE SYSOUT in your BATSPL file is characterized by
observations with a SPLMASK of '...WPx' where:

   ... - indicates the absence of execution records

   W   - indicates the presence of one or more SMF type 6
         output writer records

   P   - indicates the presence of an SMF type 26 non-
         execution node purge record

   x   - can have a value of 'H' or '.'  indicating the
         presence or absence of the Job Account Derivation
         Hold (BATSFH) file observation

You can easily identify BATSPL observations representing NJE
SYSOUT by examining the value of the NJE SYSOUT Record Count
(SPLNJESR) data element.  SPLNJESR has a value of one when
the BATSPL observation represents NJE SYSOUT.  Note that
SPLNJESR is not a comprehensive count of NJE routed SYSOUT.
When NJE routed SYSOUT records are associated with the
execution records from the originating job, SPLNJESR is not
set.  SPLNJESR simply indicates that the execution records
from the originating job were not present when CA MICS
created the BATSPL observation.

Providing accountability for NJE routed SYSOUT is complex and
the solutions depend on how you configure CA MICS and where
the SYSOUT originated.

The following sections explore the accounting problems and
solutions for NJE routed SYSOUT accountability.

    1 - NJE SYSOUT and CA MICS Configurations
    2 - NJE SYSOUT From Non-MVS Sources (VM)