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.2 NJE SYSOUT from Non-MVS Sources (VM)
6.3.4.2.2 NJE SYSOUT from Non-MVS Sources (VM)
This section discusses how to provide accountability for NJE-
routed SYSOUT where the SYSOUT originates from:
o A non-MVS source, such as VM
NJE Network: SYSOUT Originating from a Non-MVS Node
VM MVS
NODE A NODE B
+-------------+ +----------------------+
| RSCS SPOOL | | JES SPOOL |
| +------+ | | +------+ +------+ |
| | SYS1 | |<-- NJE -->| | SYSB | | SYSC | |
| +------+ | | +---|--+ +---|--+ |
+-------------+ +------|---------|-----+
| |
+-------+ | SMF |
|CA MICS| <-------+----+----+
| UNIT |
+-------+
o An MVS node whose SMF data is not input into the same
CA MICS unit that processes the NJE SYSOUT SMF data.
NJE Network: SYSOUT Originating from Two Different MVS
Nodes Going to Two Different CA MICS Units
MVS MVS
NODE A NODE B
+-------------+ +----------------------+
| JES SPOOL | | JES SPOOL |
| +------+ | | +------+ +------+ |
| | SYSA | |<-- NJE -->| | SYSB | | SYSC | |
| +---|--+ | | +---|--+ +---|--+ |
+-------|-----+ +------|---------|-----+
| | |
| SMF +-------+ | SMF | +-------+
+---->|CA MICS| +----+----+-->|CA MICS|
| UNIT | | UNIT |
| A | | B |
+-------+ +-------+
NJE SYSOUT records in both of these configurations have the
same accountability problems. In the VM to MVS example, the
only SMF records produced are the SMF type 6 and 26 records
written when the VM-originating SYSOUT is printed. The MVS
to MVS example is similar. A job running on SYSA will
generate execution records processed by CA MICS UNIT A. Any
SYSOUT transmitted for printing to NODE B will produce SMF
type 6 and 26 records processed by CA MICS UNIT B.
Most account code exit routines rely on information found in
the execution records produced for a job. In both NJE SYSOUT
cases described above, the execution records will never be
available to the CA MICS unit that processes the NJE SYSOUT
records.
SYSOUT transmitted between NJE nodes consists of two logical
parts, the SYSOUT data sets and the NJE header record. The
NJE header record contains the information required by the
receiving node to ensure correct processing of the SYSOUT
data set. It also contains fields useful for assigning
ownership to the SYSOUT. Some of these fields are written to
the SMF type 26 purge record created when the NJE-routed
SYSOUT data sets are printed.
USING THE NETWORK ACCOUNT NUMBER
One field, the Network Account Number (JOBNETAC), is
available if specified at the originating node. NJE SYSOUT
originating from an MVS node would use a /*NETACCT JCL
statement to specify the network account number. NJE SYSOUT
originating from VM would require that RSCS populate the
network account number prior to NJE transmission.
The network account number is found in the SMF type 26
record. It is important, therefore, to avoid writing BATSPL
observations from NJE-routed SYSOUT until the purge record is
written. The purge record is only written when all SYSOUT
data sets for a given job are printed or purged. When NJE-
routed SYSOUT consists of two or more SYSOUT data sets,
CA MICS will encounter a "lone" writer record when some, but
not all, of the SYSOUT data sets are printed prior to SMF
dumping. "Lone" writer records are discussed in Section
6.3.4.4. Use the SPLLIMIT option statement to delay writing
BATSPL observations from "lone" SYSOUT. The SPLLIMIT option
statement is fully discussed in Section 7.3.1.3.
The sample global account code exit routine (ACCTRTE) in
Section 7.2.2.1 shows an example of using the JOBNETAC data
element for NJE SYSOUT account code setting. In general, any
field in the SMF type 26 purge record may be used for
assigning accountability for NJE-routed SYSOUT.
