6. DATA SOURCES › 6.3 CA MICS SMF Requirements and Considerations › 6.3.4 SYSOUT Considerations › 6.3.4.3 "Late" SYSOUT

6.3.4.3 "Late" SYSOUT

"Late" SYSOUT refers to SMF type 6 records generated for
SYSOUT printed after CA MICS has already created a BATJOB
observation for a job because the SUSPENDLIMIT was exceeded.
"Late" SYSOUT is common at sites where SYSOUT is allowed to
remain on the JES spool for more than the CA MICS
SUSPENDLIMIT value (maximum of 10 update cycles).  "Late"
SYSOUT is characterized by the SMF record set represented by
a SPLMASK of '...WPx' where:

   ... - indicates the absence of execution records

   W   - indicates the presence of one or more SMF type 6
         output writer records

   P   - indicates the presence of an SMF type 26 execution
         node purge record

   x   - can have a value of 'H' or '.'  indicating the
         presence or absence of the Job Account Derivation
         Hold (BATSFH) file

The Late SYSOUT Record Count (SPLLATE) data element
identifies "late" SYSOUT observations written to the BATSPL
file.  SPLLATE only has a value of one when the BATSPL
observation represents "late" SYSOUT.

You should try to minimize the occurrence of "late" SYSOUT in
your CA MICS environment. The BATJOB observation written from
the SMF execution records for the job does not include print
measurements for any "late" SYSOUT.  Accountability is more
difficult because the execution records are not present when
CA MICS processes the "late" SYSOUT records. The following
suggestions enable you to minimize "late" SYSOUT and allow
accountability for any "late" SYSOUT encountered.

Examine the CA MICS SUSPENDLIMIT value in
prefix.PARMS.MICS(SMFOPS).  The value specified controls how
long CA MICS will wait for SYSOUT before creating a BATJOB
observation and deleting the job from the CA MICS suspend
files.  If output remains on your JES spool for a maximum of
seven days, your CA MICS SUSPENDLIMIT value should be greater
than seven.  CA MICS starts "aging" a job when the first
execution record is encountered.  This "age" is compared to
SUSPENDLIMIT.  So, select a SUSPENDLIMIT value large enough
to allow job execution and printing to occur.  This may not
always possible because sites sometimes require that SYSOUT
remain on the JES spool for very long periods of time.

You can still ensure that "late" SYSOUT receives the same
account code values used for the creating job by activating
the Job Account Derivation Hold (BATSFH) file.  This file
will always be able to provide account information for "late"
SYSOUT, because by definition, CA MICS has already
encountered the execution records from the job that created
the "late" SYSOUT.  The BATSFH file is discussed in Section
5.2.10.  BATSFH file activation is discussed in Section
7.3.1.4.

You can also force CA MICS to create a second BATJOB
observation for the "late" SYSOUT records by specifying a
LATEJOB option statement in prefix.MICS.PARMS(SMFOPS).  The
LATEJOB option statement is fully discussed in Section
7.3.1.5.  The LATEJOB option in not recommended, however.  It
is preferable that you account for SYSOUT from the BATSPL
file.