7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.1 SMF Processing Options (SMFOPS) › 7.3.1.6 LATEJOB/NOLATEJOB Statement

7.3.1.6 LATEJOB/NOLATEJOB Statement

The LATEJOB/NOLATEJOB statement is optional and has the
following format:

NOLATEJOB (Default)

or

LATEJOB

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 late
SYSOUT by coding a LATEJOB option statement in SMFOPS.  For
more information about late SYSOUT, refer to Section 6.3.4.3.

The LATEJOB option is not recommended.  Specifying LATEJOB
will result in two BATJOB observations for the same job in
different cycles of the DETAIL timespan.  The first
observation will represent the execution of the job and any
SYSOUT printed before the CA MICS SUSPENDLIMIT was exceeded.
The second observation will represent SYSOUT printed after
CA MICS had discarded the SMF records for the job because the
SUSPENDLIMIT was exceeded.  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 NOLATEJOB or omit the
statement and account for SYSOUT from the BATSPL file.

SPECIFYING THE LATEJOB/NOLATEJOB OPTION STATEMENT

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

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

2. Insert a line as follows:

   LATEJOB

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

TIPS and HINTS

We strongly discourage coding a LATEJOB statement.  It may be
conceptually easier to account for everything from the BATJOB
file, but BATJOB observations created from late SYSOUT with a
LATEJOB 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 late
SYSOUT will have missing values for all execution-related
data elements.  Use the BATSPL file for SYSOUT accounting and
printer utilization studies.