5. FILES › 5.2 Batch Information Area Files › 5.2.10 Job Account Derivation Hold File (BATSFH) › 5.2.10.3 BATSFH File Customization

5.2.10.3 BATSFH File Customization

You must customize the BATSFH file to meet your accounting
requirements.  Your accounting requirements are defined in
the SAS code you wrote in sharedprefix.MICS.PARMS(ACCTRTE),
the Batch Account Code Exit Routine.  The account routine is
thoroughly explained in Section 7.2.2.1.  If you are familiar
with the I_AUDIT and J_AUDIT SMF record type flags, but
unfamiliar with the ACCTINFO flag, you should read Section
7.2.2.1 before continuing.

To get started, print a listing of your account routine.  All
data elements that your account routine uses to assign values
to ACCTNO1-ACCTNO9 need to be turned on in the BATSFH file.
For example, consider the following ACCTRTE:

     /*                                         */
     /*     ASSIGN OVERHEAD ACCOUNT NUMBERS     */
     /*                                         */
     ACCTNO1='***'      ; /* DIVISION   */
     ACCTNO2='*****'    ; /* DEPARTMENT */
     ACCTNO3='********' ; /* USER       */
     /*                                         */
     IF ACCTINFO THEN DO ;/* I_AUDIT, J_AUDIT, or H_AUDIT  */
       ACCTNO1=ACTFLD1 ;  /* FIRST JOB CARD ACCOUNT FIELD  */
       ACCTNO2=ACTFLD2 ;  /* SECOND JOB CARD ACCOUNT FIELD */
       ACCTNO3=RACFUSID;  /* RACF USER IDENTIFICATION */
     END ;

This trivial account routine assigns ACCTNO1 and ACCTNO2 from
the first two account fields from the job card.  ACCTNO3 is
set equal to the RACF User ID.

The BATSFH file definition is contained in the SMFGENIN
member of sharedprefix.MICS.GENLIB.  The file definition is
illustrated below:

   FILE SFHJOB 50 1 Y N N N N N N N Job Account Derivation ..
   FOPT DEFAULT DEFAULT STD
   CYCLES   01 00 00 00 00 00 000 000
   TYPE R 2 . 2 . 2 .
   NAME SFHAGE       00  0 N N N N Processing Cycles
   NAME SFHHAGE      00  0 N N N N Cycle Age Last Used For ..
   * COMMON
   NAME RDRTS        99  1 1 1 1 1 .
   NAME JOB          99  2 2 2 2 2 .
   *
   * Data Elements below this comment may be turned on or off
   * according to ACCTRTE requirements.  Data elements above
   * this comment must NEVER be modified in any way.
   *
   TYPE R $8. . $8. . $8. .
   NAME SMF20UIF     00  N N N N N Initiation User Field
   NAME SFHGRID      00  N N N N N RACF Group ID
   NAME SFHUSID      00  N N N N N RACF User ID
   NAME SFHTERM      00  N N N N N RACF Terminal
   * COMMON
   NAME PGMTYPE      99  N N N N N .
   NAME JOBPRTY      99  N N N N N .
   NAME PERFGRP      99  N N N N N .
   NAME JOBCLASS     99  N N N N N .
   NAME JOBPRGNM     99  N N N N N .
   NAME MICSVER      99  N N N N N .
   NAME SYSID        99  N N N N N .
   NAME TERMID       99  N N N N N
   NAME ACTFLD1      99  N N N N N .
   NAME ACTFLD2      99  N N N N N .
   NAME ACTFLD3      99  N N N N N .
   NAME ACTFLD4      99  N N N N N .
   NAME ACTFLD5      99  N N N N N .
   NAME ACTFLD6      99  N N N N N .
   NAME ACTFLD7      99  N N N N N .
   NAME ACTFLD8      99  N N N N N .
   NAME ACTFLD9      99  N N N N N .

The BATSFH file customization required to satisfy the sample
ACCTRTE shown above is trivial.  Simply activate the
following data elements in the DETAIL time-span:

   NAME SFHUSID      00  0 N N N N RACF User ID
   NAME ACTFLD1      99  0 N N N N .
   NAME ACTFLD2      99  0 N N N N .

The 'N' in the DETAIL time-span column was changed to a '0'
for these three elements.  This tells CA MICS to include
these three elements in each BATSFH file observation.  You
must execute the component generator,
sharedprefix.MICS.CNTL(SMFCGEN), after customization to
generate the internal file macros.

NOTE: CA MICS sets the value of the three RACF fields,
      RACFUSID, RACFGRID, and RACFTERM, from one of several
      different SMF records types prior to execution of your
      ACCTRTE.  If your ACCTRTE uses RACF fields to determine
      ACCTNOx values, activate the three fields SFHUSID,
      SFHGRID, and/or SFHTERM in the BATSFH file.  When a
      BATSFH observation is present for NJE or "late" sysout,
      CA MICS will set the RACF values from these SFH file
      elements prior to execution of your ACCTRTE.

Because the BATSFH file exists only in the DETAIL time-span,
data element activation in the summarized time-spans is
ignored by the component generator program.

Section 6.2 of the CA MICS System Modification Guide explains
CA MICS file tailoring. If your ACCTRTE requires data
elements other than those delivered in the BATSFH file, you
must add them to the file.  If the required element is not a
common data element, you may need to add a TYPE statement so
the CA MICS component generator uses the appropriate length
and format for the element(s).  Make sure you execute
sharedprefix.MICS.CNTL(SMFCGEN) after activating and/or
adding the data elements you need.

You should customize and generate the BATSFH file before you
activate it with an SFHLIMIT option statement.  The BATSFH
file remains empty until activated with an SFHLIMIT statement
in prefix.MICS.PARMS(SMFOPS).