SMF Local and Remote SYSOUT

A node is the description given to a single Job Entry Subsystem (JES) (e.g., MVS JES2, MVS JES3, VM RSCS, VS1 JES, VSE POWER, etc.).
rm
Nodes are connected in an NJE network. All input and output in an MVS node is managed and controlled by either a JES2 or JES3 subsystem in a data area called a spool.
All printers in an MVS node are defined to JES. They can be defined in two ways, either locally attached or as Remote Job Entry (RJE) printers owned by an RJE station.
From an accountability perspective, it is not important whether the SYSOUT prints on a local or remote printer. What is important is where the execution occurred for the activity that created the SYSOUT. This section discusses accountability for SYSOUT created and printed within a single MVS node.
Accountability for remote and local SYSOUT is relatively simple as long as the SMF data from all SYSIDs sharing the JES spool is fed into a single
MICS
unit. This is because
MICS
will always encounter the execution records for the batch job, TSO session, started task, or APPC/MVS transaction program that created the SYSOUT. The execution records provide the accounting information.
The
MICS
suspend process ensures that the account information found in the execution records remains available for any SYSOUT waiting to print in the JES spool where the execution occurred. The key to the
MICS
suspend process is the SMF type 26 execution node purge record. JES only writes the execution node purge record when an address space has completed execution and all SYSOUT data sets for the job have been printed, purged, or transmitted to another NJE node.
MICS
in turn continues to suspend the records for the job until the execution node purge record is encountered or the
MICS
SUSPENDLIMIT value is exceeded.
The
MICS
SUSPENDLIMIT, discussed in the PGMALL/NOPGMALL Statement section, controls how long
MICS
will wait for the execution node purge record. When local or remote SYSOUT remains on the JES spool longer that the SUSPENDLIMIT value,
MICS
creates a BATJOB observation and purges the suspend files of all records relating to the job. This creates an accountability problem for this "late" SYSOUT if eventually printed, but the problem is solvable by activating the Job Account Derivation Hold (BATSFH) file. The "Late" SYSOUT section discusses "late" SYSOUT and the BATSFH file accounting solution in detail.