5. Maintenance › 5.15 Excluding a Component from the DAYSMF Step

5.15 Excluding a Component from the DAYSMF Step

During CA MICS DAILY processing, the DAYSMF step is used to
split SMF data into separate data sets for each component
that has SMF data as input.  This helps to reduce I/O, CPU
time and execution time because each component processes only
the SMF data it requires.

Instead of using the DAYSMF step in the CA MICS DAILY job, CA
SMF Director or other processes can be used to split the SMF
data into discrete data sets outside of the CA MICS DAILY
job.
CA MICS supports this configuration by allowing components to
be excluded from the DAYSMF step on an individual basis.

The following checklist contains the steps necessary to
exclude a component from the DAYSMF step.

__  1. Determine components in the unit that use SMF or CA
       SMF Director as an input data source

       MICSLOG message BAS10083 in any JCLGEN lists the
       components that have SMF and CA SMF Director as an
       input source.  The following will regenerate the
       JCLGENU job with JCLGEN to identify the components
       that use SMF data as input.

       Edit prefix.MICS.PARMS(JCLGENU) and make sure it has
       the following line in it:

       JCLGENU

       Save prefix.MICS.PARMS(JCLGENU).

       Submit prefix.MICS.CNTL(JCLGENU). This job should
       complete with a return code of zero.  Review the
       MICSLOG and locate message BAS10083.  This message
       lists the components that use SMF data as input.
__  2. Specify the components to exclude from DAYSMF

       Edit prefix.MICS.PARMS(JCLDEF) and find the DAYSMF
       keyword and change it to:

       DAYSMF EXCLUDE ccc ccc . . .

       ccc is the 3 character identifier as defined on the
       COMPONENTS statement.


       Note: If you wish to exclude all the SMF eligible
       components from the DAYSMF step, specify DAYSMF OFF
       and follow the checklist in section 5.10 of this
       guide.

       Excluding a component from DAYSMF is not restricted to
       components that use CA SMF Director input, but can be
       any component that uses SMF input.
__  3. Specify the input data set for the component step

       For each defined component that has SMF data as an
       input source, a prefix.MICS.PARMS(INPUTccc) member
       must exist.  If the INPUTccc member does not exist, it
       must be created or the CA MICS DAILY job will not
       generate.

       For each INPUTccc, a DD for INPUTSMF must be added or,
       if the input data source is CA SMF Director, an
       SMFDRCTR DD must be added or modified. Use this
       example for SMF input:

       //INPUTSMF DD DISP=SHR,DSN=SMF.SPLIT.DATASET

       Use this example for CA SMF Director input:

       //SMFDRCTR DD DISP=SHR,DSN=CA.SMF.duplicate.index

       Note:  Excluding a component (or multiple components)
       that results in a single component remaining as an SMF
       eligible component in this unit, will automatically
       deactivate the DAYSMF step.  In this case,
       prefix.MICS.PARMS(INPUTRDR) will be used to specify
       the input data source for the remaining SMF component
       step.
__  4. Generate the DAILY job

       Edit prefix.MICS.PARMS(JCLGENU) and add the following
       line:

       DAILY

       Edit prefix.MICS.CNTL(JCLGENU) and submit the job for
       execution. This job should complete with a return code
       of zero.

Note:  If the input data set names for a component change,
the INPUTccc members or INPUTRDR can be modified and the
DAILY regenerated using JCLGENU.