4. Operation › 4.10 Integration with CA SMF Director › 4.10.3 CA SMF Director Implementation Scenarios › 4.10.3.2 CA SMF Director without DAYSMF
4.10.3.2 CA SMF Director without DAYSMF
In this configuration, the DAYSMF step is not used to split
SMF data. This is used when SMF data is preprocessed or
split independent of CA MICS processing. In the case of CA
SMF Director, the data for each component is recorded in a
unique CA SMF Director duplicate split index.
When the DAYSMF step is deactivated, the INPUT is defined in
the prefix.MICS.PARMS(INPUTccc) members.
In this example:
o The DAYSMF step will not be generated owing to the
'DAYSMF OFF' statement in prefix.MICS.PARMS(JCLDEF).
o The SMFDIRECTOR statement in prefix.MICS.PARMS(JCLDEF) is
optional as it only affects the DAYSMF step. The
presence of the SMFDRCTR DD within the individual
component steps automatically triggers processing of CA
SMF Director input.
o The prefix.MICS.PARMS(INPUTccc) (where ccc is the
component identifier) is used to define the CA SMF
Director duplicate split index via the SMFDRCTR DD
statement. If a data set containing standard SMF data is
used, the INPUTSMF DD is also specified.
o The DAY010 step has input data from a standard SMF
data set.
o The DAY020 and DAY040 steps have input data from a
standard SMF data set and from CA SMF Director.
o The DAY030 step has standard SMF input.
JCLDEF Options
---------------
COMPONENTS TSO RMF CIC SMF
SMFDIRECTOR CIC RMF
SMFRECORDING CIC
DAYSMF OFF
+--------+ prefix.MICS.PARMS(INPUTTSO)
| DAY010 | //INPUTSMF DD
+--------+
|
V
+--------+ prefix.MICS.PARMS(INPUTRMF)
| DAY020 | //INPUTSMF DD
+--------+ //SMFDRCTR DD
|
V
+--------+ prefix.MICS.PARMS(INPUTSMF)
| DAY030 | //INPUTSMF DD
+--------+
|
V
+--------+ prefix.MICS.PARMS(INPUTCIC)
| DAY040 | //INPUTSMF DD
+--------+ //SMFDRCTR DD
