7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.1 SMF Processing Options (SMFOPS) › 7.3.1.4 SPLLIMIT Statement

7.3.1.4 SPLLIMIT Statement

The SPLLIMIT statement is optional.  This statement, if
specified, prevents the writing of "lone" SYSOUT records to
the BATSPL file.  Lone SYSOUT records, characterized by a
SPLMASK value of ...W..  are fully discussed in Section
6.3.4.4.

The SPLLIMIT statement directs CA MICS to wait a specified
number of daily updates before writing the record to the
BATSPL file.  This is important because most account code
setting schemes rely on information either in the execution
records for the job that created the SYSOUT, or the purge
record created when all output for a given job is printed or
purged.  The presence of a lone output writer record means
that additional output data sets for the job are still
waiting to print.  At minimum, an SMF type 26 purge record
will eventually be written and merged with the lone SYSOUT
record.

The SPLLIMIT statement has the following format:

SPLLIMIT nn

where nn ranges from 0 to 10

The default is SPLLIMIT 0.

The value of nn tells CA MICS how many daily update cycles to
delay writing the lone SYSOUT record to the BATSPL file.  If
you code SPLLIMIT 0 or do not include the SPLLIMIT statement
in SMFOPS, CA MICS will write a BATSPL observation
immediately upon encountering a lone writer record.  Because
most account code routines rely on other SMF record types to
set ACCTNOx values, lone writer records are generally
assigned overhead account codes.

A better strategy for dealing with lone writer records is to
add the SPLLIMIT statement with a nonzero value for nn.
CA MICS will then suspend the record and avoid creating a
BATSPL observation until one of the following events occurs:

o Some other SMF record type is associated with the output
  writer record and the lone designation no longer applies.

o An observation from the Job Account Derivation Hold
  (BATSFH) file is associated with the output writer record
  and the lone designation no longer applies.

o nn daily update cycles pass.

o The CA MICS SUSPENDLIMIT value is exceeded.

When any of these events occurs, a BATSPL observation is
created.  Lone output writer records are usually lone for
only one daily update cycle.  By delaying the writing of a
BATSPL observation, you increase the chance to assign
accountability for the printer resources consumed.

SPECIFYING THE SPLLIMIT OPTION STATEMENT

To specify the SPLLIMIT option statement, follow these steps:

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

2. Insert a line as follows:

   SPLLIMIT nn

   where nn ranges from 1 to 10.

   Note:  Specifying SPLLIMIT 0 has no effect. SPLLIMIT 0 is
   the default assumed by CA MICS if the SPLLIMIT option
   statement is not present in SMFOPS.

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