Previous Topic: 4.10.3 CA SMF Director Implementation Scenarios

Next Topic: 4.10.3.2 CA SMF Director without DAYSMF

4.10.3.1 CA SMF Director with DAYSMF Only


In this configuration, CA SMF Director data and SMF data sets
are input directly to the DAYSMF step only.  This is useful
to those sites that write records used by multiple components
to the same duplicate split index.  This should be considered
as a transitional approach only while migrating SMF dump
processes to CA SMF Director control.

Note:  Processing CA SMF Director data through DAYSMF
minimizes the benefit to be derived from CA SMF Director.
Best practice would be to customize CA SMF Director to record
the split data set entries to separate duplicate split
indices based on the SMF record types and CA MICS component
needs.  For more information, see section 4.10.1 of this
guide.

In this configuration, the CA SMF Director duplicate split
index is not directly input to the component steps.  This
configuration is an extension of default CA MICS processing.
In addition, standard SMF data is also input to DAYSMF.

 JCLDEF Options
 ---------------
 COMPONENTS   TSO RMF CIC SMF
 SMFRECORDING CIC
 SMFDIRECTOR  TSO RMF CIC SMF
 DAYSMF FILES PERMANENT

    +--------+        prefix.MICS.PARMS(INPUTRDR)
    | DAYSMF |        //INPUTSMF  DD
    +--------+        //SMFDRCTR  DD
        |
        V
    +--------+        (generated from DAYSMF)
    | DAY010 |        //INPUTSMF DD . . prefix.MICS.TSO.DATA
    +--------+
        |
        V
    +--------+        (generated from DAYSMF)
    | DAY020 |        //INPUTSMF DD . . prefix.MICS.RMF.DATA
    +--------+
        |
        V
    +--------+        (generated from DAYSMF)
    | DAY030 |        //INPUTSMF DD . . prefix.MICS.SMF.DATA
    +--------+
        |
        V
    +--------+        (generated from DAYSMF)
    | DAY040 |        //INPUTSMF DD . . prefix.MICS.CIC.DATA
    +--------+        prefix.MICS.PARMS(INPUTCIC)