6. DATA SOURCES › 6.3 CA MICS SMF Requirements and Considerations › 6.3.4 SYSOUT Considerations › 6.3.4.5 Report Distribution Products › 6.3.4.5.1 CA BUNDL Generated SMF Type 6 Records

6.3.4.5.1 CA BUNDL Generated SMF Type 6 Records

CA BUNDL Report Distribution product can write nonstandard
SMF type 6 records that identify the original job that
created the SYSOUT data set(s).  CA MICS recognizes BUNDL-
generated SMF type 6 output writer records and assigns a
unique SUBSYSID value of 'BNDL' to any BATSPL observation
created from these records.  Additionally, the Data Set
Control Indicator (SPLDSCI) data element is set to 'BUNDL
GENERATED SMF TYPE 6' in the BATSPL observation.

BUNDL-generated SMF type 6 records are created by a BUNDL
utility program that executes as a batch job.  This job
returns the selected SYSOUT data sets to JES for actual
printing.  It also writes nonstandard SMF type 6 output
writer records to the SMF files.

The net result is that the printed SYSOUT data sets are
accounted for twice--once by the BUNDL-generated and again
by the JES-, PSF-, or External Writer-generated SMF type 6
records.  You should allow both the BUNDL and real SMF type 6
records to create BATSPL observations.  Use the BUNDL record
for accounting because it will provide accountability back
to the original job.  Use the standard SMF type 6 record for
printer utilization studies because it identifies the
actual output device name used to print the report.

No action is required for CA MICS to write BUNDL-generated
SMF type 6 records to the BATSPL file.  In order to ensure
SYSOUT accountability and to avoid double billing, perform
the following steps:

1) Identify the batch BUNDL utility job that transfers SYSOUT
   data sets from BUNDL's data area back to JES.

2) Add code to the _USRSSPL macro to identify the job name of
   the BUNDL utility program and assign the ACCTNOx values to
   some nonbillable, overhead category.  The   _USRSSPL macro
   is found in sharedprefix.MICS.SOURCE(#SMFEXIT).

    MACRO _USRSSPL
     ...  (existing exit code, if any)
    IF JOB='BNDLUTY' THEN DO;
      ACCTNO1='***' ;
      ACCTNO2='*****' ;
      ACCTNO3='********' ;
    ...  (logic appropriate to your purpose)
    END;
    ...
    %

    In the above example, the job name of the BUNDL utility
    program is 'BNDLUTY'.  The overhead account numbers
    prevent charging for these records, but allow them to
    populate the BATSPL file for printer resource analysis.

3) Activate the Job Account Derivation Hold (BATSFH) file.

   When BUNDL originally removes the SYSOUT from the JES
   spool, CA MICS typically will encounter the SMF type 26
   execution purge record for the job that created the
   SYSOUT.  CA MICS will subsequently delete the job from the
   suspend files.  Some time later, the BUNDL utility will
   send the SYSOUT data sets back to JES for printing.  At
   this point, CA MICS will need the BATSFH file to supply
   accounting information for the BUNDL nonstandard SMF type
   6 records.

   The BATSFH file is described in Section 5.2.10.  The
   SFHLIMIT option statement that activates the BATSFH file
   is discussed in Section 7.3.1.4.  Make sure the SFHLIMIT
   argument value reflects the amount of time that you expect
   the SYSOUT data sets to remain in BUNDL's data area before
   actual printing.

The BUNDL-generated SMF type 6 output writer records will
always be written to the BATSPL file by the first daily
update cycle encountering them.  A BATSFH file observation
will provide accountability if the originating job's
execution SMF records were processed earlier by the same
CA MICS units that encounter the BUNDL type 6 records.

NOTE:  You must be at BUNDL Release 4.5 or later for CA MICS
       to recognize the BUNDL-generated SMF type 6 output
       writer records.