5. Maintenance › 5.10 Removing the DAYSMF Step from the DAILY Job

5.10 Removing the DAYSMF Step from the DAILY Job

 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 the DAYSMF
 step to be removed from the DAILY job and allowing the
 installation to specify the input data sets of the SMF data
 for processing by each component.
 
 The following checklist shows the steps necessary to
 deactivate the DAYSMF step and manually specify the input
 data sets for components that use SMF data:
 
 __  1. Determine components in the unit that use SMF as an
        input data source
 
        MICSLOG message BAS10083 in any JCLGEN lists the
        components that have SMF 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. Deactivate the DAYSMF step
 
        Edit prefix.MICS.PARMS(JCLDEF) and find the DAYSMF
        keyword and change it to:
 
        DAYSMF OFF
 
 __  3. Specify input data set for each component
 
        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 or SMFDRCTR 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
 
 __  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.
 
        If the JCLGENU fails with a user abend of 998 and
        the following message:
 
        BAS10117E MEMBER INPUTccc INDICATED ON A ":INCLUDE" OR
                  A ":INCLUDEPARM" STATEMENT NOT IN LIBRARY
 
        then the INPUTccc member was not created per step 3.
        In this case, create the member; then run the
        prefix.MICS.CNTL(JCLGENU).
 
 __  5. (Optional) Delete SMF work data sets
 
        When the DAYSMF step is present, an SMF work data set,
        prefix.MICS.ccc.DATA (where ccc is the component
        identifier), is created for each component that uses
        SMF data. This data set is either temporary or
        permanent, depending on the value of JCLDEF keyword
        DAYSMF.
 
        Since the DAYSMF is no longer being used, these
        data sets are not required and may be deleted.
 
 
 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.