SMF LATEJOB/NOLATEJOB Statement

The LATEJOB/NOLATEJOB statement is optional.
micsrm140

The LATEJOB/NOLATEJOB Statement Format

NOLATEJOB (Default)
or
LATEJOB
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:
  • Jobs submitted for non-execution, for example, TYPRUN=SCAN (
    MICS data element
    JOBSCAN) or TYPRUN=COPY (
    MICS data element
    JOBCOPY))
  • JCL errors (
    MICS data element
    JOBJCLER)
  • Jobs canceled (Operator Cancels (
    MICS data element
    JOBCANCL))
  • Jobs that incur Job System abends (
    MICS data element
    JOBSYSAB) or Job User abends (
    MICS data element
    JOBUSRAB)
  • Jobs that are in execution when the system fails (System Failure During Job Execution (
    MICS data element
    JOBCRASH))
MICS
does not, by default, create BATJOB observations for NJE SYSOUT or late SYSOUT. You can force
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 the "Late" SYSOUT Sections.
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
MICS
SUSPENDLIMIT was exceeded. The second observation will represent SYSOUT printed after
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
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.