7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.1 SMF Processing Options (SMFOPS) › 7.3.1.7 NJEJOB/NONJEJOB Statement

7.3.1.7 NJEJOB/NONJEJOB Statement

The NJEJOB/NONJEJOB statement is optional and has the
following format:

NONJEJOB (Default)

or

NJEJOB

CA MICS, by default, only writes batch activity to the BATJOB
file.  An observation is written to the BATJOB file for each
job that executed.  Certain non-execution batch jobs also
qualify for the BATJOB file:

o Jobs submitted for non-execution, for example,
  TYPRUN=SCAN (CA MICS data element JOBSCAN) or
  TYPRUN=COPY (CA MICS data element JOBCOPY))

o JCL Errors (CA MICS data element JOBJCLER)

o Jobs canceled (Operator Cancels (CA MICS data element
  JOBCANCL))

o Jobs that incur Job System abends (CA MICS data element
  JOBSYSAB) or Job User abends (CA MICS data element
  JOBUSRAB)

o Jobs that are in execution when the system fails (System
  Failure During Job Execution (CA MICS data element
  JOBCRASH))

CA MICS does not, by default, create BATJOB observations for
NJE SYSOUT or "late" SYSOUT.  You can force CA MICS to create
a BATJOB observation from the SMF records representing NJE
SYSOUT by coding an NJEJOB option statement in SMFOPS.  For
more information about NJE SYSOUT, refer to Section 6.3.4.2.

The NJEJOB option is not recommended.  Specifying NJEJOB will
result in two BATJOB observations for the same job in
different cycles of the DETAIL timespan if CA MICS has
previously encountered and discarded the execution records
from the job that created the NJE SYSOUT.  The first
observation will represent the execution of the job and any
SYSOUT printed before the SMF type 26 execution purge record
was encountered.  The second observation will represent the
NJE-routed SYSOUT that was printed after CA MICS had
discarded the SMF records for the job because the execution
purge record was encountered.  Most of the JOB data elements
in the second observation will contain SAS missing values.
The only resource usage data elements containing information
will be print-related.

A better strategy is to specify NONJEJOB (the default) or
omit the statement and account for SYSOUT from the BATSPL
file.

SPECIFYING THE NJEJOB/NONJEJOB OPTION STATEMENT

Nothing is required to specify NONJEJOB.  This is the default
value.  To specify a NJEJOB option statement, follow these
steps:

1. Edit prefix.MICS.PARMS(SMFOPS).

2. Insert a line as follows:

   NJEJOB

3. Execute the job in prefix.MICS.CNTL(SMFPGEN).  If the
   NJEJOB/NONJEJOB option statement 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 NJEJOB/NONJEJOB option statement, MICSLOG will
   tell you that the option is missing and that the default
   (NONJEJOB) was used.

   Note:  Another optional SMFOPS statement,
   SUSPENDNJE/NOSUSPENDNJE, discussed in Section 7.3.1.3, is
   related to the NJEJOB/NONJEJOB option.  If NJEJOB is
   specified, NOSUSPENDNJE must also be specified.  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

We strongly discourage coding an NJEJOB statement.  It may be
conceptually easier to account for everything from the BATJOB
file, but BATJOB observations created from NJE SYSOUT with an
NJEJOB statement will waste space in your CA MICS database.
Most of the data elements in the BATJOB file are
execution-related.  BATJOB observations created from NJE
SYSOUT will have missing values for all execution-related
data elements.  Use the BATSPL file for SYSOUT accounting and
printer utilization studies.