10. MODIFICATION › 10.1 Parameter Modification › 10.1.2 Special Notes on Updating SMFGENIN

10.1.2 Special Notes on Updating SMFGENIN

Modification of sharedprefix.MICS.GENLIB(SMFGENIN) is
required to activate or deactivate a file or element in a
timespan, to change the status of archive or history files,
to change specifications on the OPTION statement, or to
perform any complex-level modification to the Batch and
Operations Analyzer files.

SMFGENIN contains file definitions for the CA MICS production
database files and the SMF suspend files.  The suspend file
definitions define both the data kept from the raw SMF input
and the data kept in suspension for jobs, TSO sessions,
started tasks, and APPC/MVS ASCH-scheduled transaction
programs (TPs).

When you decide to activate an element in one of the database
files, you must make sure that the element is also activated
in the DETAIL timespan of the corresponding suspend file.
Simply turning it on in the production file, BATPGM for
example, will not work if the element is turned off in the
BATSFS step-level suspend file.  Each suspend file name
begins with the characters SFx.  The CA MICS production
database files and their corresponding suspend files are
shown below:

  Production Database File          Suspend Files

        BATPGM                          BATSFS
        BAT_TS                          BATSFS
        BAT_ST                          BATSFS
        BAT_TP                          BATSFS

        BATSPL                          BATSFW

        BATATP                          BATSFT

        BATJOB                           none *

        BAT_JS                           none *

* Both the BATJOB and BAT_JS files are built from the step-
  level suspend files.

In addition to the suspend files shown above, three
intermediate process files are defined for the Batch
Information Area:

BATSFC
BATXCS
BATXCP

NEVER turn any data elements off in these three files! They
are created and deleted as part of the DAY030 daily update
step.  Turning elements off in these three files will not
save you any database space, but will instead invalidate the
processing of SMF type 30 continuation records.

Some additional suspend files hold key fields from the raw
SMF records:

       Raw SMF Record                 Suspend File

   Job INITIATION (30-1)                 BATSFI

   Job END record (30-5)                 BATSFJ

   Job PURGE record (26)                 BATSFP

   JES3 MDS (25)                         BATSFA

In general, these files should also be left untailored.  They
do not consume much space in your database and they hold
important elements like the job card accounting fields, RACF
values, and so on.

When you want to turn an element on in one of the Batch
Information Area database files, use the TSO find command to
locate each occurrence of the element in SMFGENIN.  If the
element is found in one of the SF*  files, it must be turned
on in the DETAIL timespan.  If not, the element in the
corresponding production file will receive missing values.