SMF SUSPENDNJE/NOSUSPENDNJE Statements
The SUSPENDNJE/NOSUSPENDNJE statement is optional. This statement determines how NJE SYSOUT is treated by each
MICS
unit. MICS
units receiving SMF data from two or more JES spools should specify NOSUSPENDNJE. This will eliminate SYSOUT accountability problems caused by discrepancies in the timing of SMF dumps for each SYSID.micsrm140
The SUSPENDNJE/NOSUSPENDNJE statement is optional. This statement determines how NJE SYSOUT is treated by each
MICS
unit. MICS
units receiving SMF data from two or more JES spools should specify NOSUSPENDNJE. This will eliminate SYSOUT accountability problems caused by discrepancies in the timing of SMF dumps for each SYSID.NOSUSPENDNJE can also significantly reduce the size of the BATSFW Writer Suspension file at sites that have large volumes of NJE SYSOUT originating from either non-MVS sources (for example, VM) or from other MVS nodes whose SMF data is not input into this
MICS
unit.This option statement affects how
MICS
processes NJE SYSOUT. NJE SYSOUT is explained in detail in the NJE SYSOUT section.Your choice of SUSPENDNJE or NOSUSPENDNJE is checked whenever
MICS
encounters NJE SYSOUT. NJE SYSOUT is characterized by an SPLMASK of ...WPx, where W represents the presence of at least one SMF type 6 output writer record and P represents the presence of an SMF type 26 purge record from a spool other than where execution occurred. The x can be either . or H, meaning the absence or presence of an observation from the Job Account Derivation Hold (BATSFH) file.The SUSPENDNJE/NOSUSPENDNJE statement has the following format:
SUSPENDNJE (Default)
or
NOSUSPENDNJE
How MICS processes NJE SYSOUT when SUSPENDNJE is specified
MICS
processes NJE SYSOUT when SUSPENDNJE is specifiedSpecifying SUSPENDNJE or leaving the option out of SMFOPS has the following influence when
MICS
encounters NJE SYSOUT:- BATSPL observations are written for each SMF type 6 output writer record when first encountered byMICS.
- The SMF type 26 non-execution spool purge record is discarded.
- The SMF type 6 output writer records are suspended to allow matching with the execution records in a later daily update cycle.
Subsequent daily updates will again encounter the suspended SMF type 6 output writer records. They have already been written to the BATSPL file, so their only useful purpose is to contribute to the job-level output-related data elements if
MICS
encounters the execution records for the job that created the SYSOUT. If the execution records are not encountered, the output writer records simply cycle through subsequent daily updates until the MICS
SUSPENDLIMIT value is exceeded. Then they are discarded. This wastes BATSFW writer suspend file DASD space in environments where the NJE SYSOUT will never be associated with the execution records from the creating address space.How MICS processes NJE SYSOUT when NOSUSPENDNJE is specified
MICS
processes NJE SYSOUT when NOSUSPENDNJE is specifiedSpecifying NOSUSPENDNJE changes the way that
MICS
processes NJE SYSOUT. The value of the SPLMASK data element can be either ...WPH or ...WP:- When SPLMASK is ...WPH,MICShas already processed and discarded the execution records for the job that created the NJE SYSOUT.MICSwrites a BATSPL observation and discards the output writer and purge records. No record suspension occurs.
- When SPLMASK is ...WP, the following happens:
- MICSimmediately suspends all SMF type 6 output writer records and the SMF type 26 non-execution node purge record. Nothing is written to the BATSPL file.
- The next daily update re-inputs the suspended records. If SPLMASK is still ...WP,MICSwrites the BATSPL observations and discards all records. No suspension occurs. If the execution records are now present, SPLMASK will no longer be ...WP, and the NOSUSPENDNJE statement has no affect.
This is a better strategy than that used with SUSPENDNJE.
MICS
automatically suspends NJE SYSOUT for one cycle to allow merging with the execution records if they were missing due to SMF dump timing problems. If the execution records have already been processed and discarded, as evidenced by an SPLMASK of ...WPH, no suspension occurs. In either scenario, NJE SYSOUT records only reside in the BATSFW suspend file for a maximum of one update cycle, reducing the DASD space requirements for this file.Specifying the SUSPENDNJE/NOSUSPENDNJE option statement
Nothing is required to specify SUSPENDNJE. This is the default value. To specify a NOSUSPENDNJE option statement, follow these steps:
- Edit prefix.MICS.PARMS(SMFOPS).
- Insert a line as follows:NOSUSPENDNJE
- Execute the job in prefix.MICS.CNTL(SMFPGEN). If the SUSPENDNJE/NOSUSPENDNJE option is coded incorrectly, the job will abend. Correct the problem as explained in the MICSLOG and resubmit. Make sure the job completes with a condition code of zero. If your SMFOPS member does not contain a SUSPENDNJE/NOSUSPENDNJE option, MICSLOG will tell you that the option is missing and that the default (SUSPENDNJE) was used.
Note:
Another optional SMFOPS statement, NJEJOB, discussed in Section 7.3.1.7, is related to the SUSPENDNJE/NOSUSPENDNJE option. If NJEJOB is specified, NOSUSPENDNJE must also be specified. The reverse is not true. You may specify NOSUSPENDNJE without adding an NJEJOB statement. If you code an NJEJOB statement in SMFOPS without specifying NOSUSPENDNJE, SMFPGEN will abend and MICSLOG will contain an error message stating that NOSUSPENDNJE must be specified with NJEJOB.Tips and hints
- The firstMICSdaily update cycle run after you change to NOSUSPENDNJE will write fewer observations to the BATSPL file than would have been written with SUSPENDNJE. This is normal and is due to the automatic one-day suspension of NJE SYSOUT with an SPLMASK of ...WP.. The next daily update cycle should show a normal range of BATSPL observations because any new NJE SYSOUT records that are automatically suspended will be offset by BATSPL records written for the SYSOUT records automatically suspended in the previous update cycle.
- You can reduce the number of automatically suspended NJE SYSOUT records by activating the BATSFH (Job Account Derivation Hold) file severalMICSupdate cycles before activating NOSUSPENDNJE. If the SPLMASK for NJE SYSOUT is ...WPH, the automatic one-day suspension does not occur. The H in SPLMASK means that a BATSFH file observation was associated with the NJE SYSOUT records.
Note:
The BATSFH file can only be associated with NJE SYSOUT that originated from a job whose execution SMF records were previously encountered in the same MICS
unit that processes the NJE SYSOUT records.