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.3 CA Dispatch Generated SMF Type 6 Records

6.3.4.5.3 CA Dispatch Generated SMF Type 6 Records

CA Dispatch is a report distribution management system.
CA Dispatch produces SMF type 6 records to allow users to be
charged for the number of report lines printed. These records
contain standard IBM SMF type 6 record fields and some
additional fields from the CA Dispatch database.  These
records are non-standard SMF type 6 records.

CA Dispatch SMF type 6 records are built once for each
recipient who receives a report, so end users can be charged
for reports they receive.  These CA Dispatch pseudo type 6
records do not contain a device name, since it is not known
where the recipient's report will be printed at the time the
report recipient is processed.

Standard SMF type 6 records will be created by JES-, PSF, or
External Writer sub systems as a started task, with a task
name of 'DISPATCH'.  To determine printer activity, use the
standard SMF type 6 records, because they identify the actual
output device name used to print a report.

The printed SYSOUT data sets are accounted for twice, once by
CA Dispatch-generated records, and again by the JES-, PSF-,
or External Writer-generated SMF type 6 records.  Both
CA Dispatch and standard SMF type 6 records should be allowed
to create BATSPL observations.  The CA Dispatch record should
be used to provide accountability back to the original job.

As with BUNDL, CA Dispatch requires no action for CA MICS to
write CA Dispatch-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 CA Dispatch utility job that transfers
   SYSOUT data sets from CA Dispatch's data area back to JES.

2) Add code to the _USRSSPL macro to identify the job name of
   the CA Dispatch 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='DISPATCH' THEN DO;
      ACCTNO1='***' ;
      ACCTNO2='*****' ;
      ACCTNO3='********' ;
    ...  (logic appropriate to your purpose)
    END;
    ...
    %

    In the above example, the job name of the CA Dispatch
    utility program is 'DISPATCH'.  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 CA Dispatch 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 CA Dispatch 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 CA Dispatch 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 CA Dispatch data area
   before actual printing.

The CA Dispatch 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 CA Dispatch type 6 records.