|
|
|
The inclusion of the SMFDRCTR DD statement is controlled by
the SMFDIRECTOR keyword in prefix.MICS.PARMS(JCLDEF).
However, the successful implementation of CA SMF Director is
influenced not only by this keyword but also the combination
of several other JCLDEF parameters as well as external
factors related to the actual CA SMF Director installation
itself.
Prior to processing CA SMF Director managed data, you will
need to have collected information regarding the way CA SMF
Director is deployed at your installation. To assist you in
identifying the optimum CA MICS implementation scenario for
your installation, this section provides a worksheet with
which you can document this information and use it to tailor
CA MICS and CA SMF Director accordingly. This worksheet is
not used by CA MICS directly, but is meant as a reference for
you. The CA SMF Director Definitions worksheet is
illustrated in Figure 4-03.
The following checklist contains both the considerations and
practical steps for implementing CA SMF Director in a unit.
Preparation:
__ 1. Review the previous subsections of chapter 4.10 to
ensure you are familiar with the requirements of
activating this feature. At a minimum, you must
review both the prerequisite information in sections
4.10.1 and 4.10.2, as well as the usage notes in
section 4.10.5.
__ 2. Consult the Systems Programmer responsible for the SMF
data at your installation to obtain the name of the CA
SMF Director duplicate split indices defined in the
SMF DUMP job and which record types they contain.
__ 3. Use the CA SMF Director Definitions Worksheets in
Figures 4-01 through 4-03 to obtain and document the
information necessary to implement CA SMF Director.
__ 4. See the sharedprefix.MICS.PARMS(cccSMFD) member if
needed to correlate the record types to a CA MICS
component to complete the worksheet.
Repeat these steps for every unit database as necessary.
JCLDEF definitions:
__ 5. Insert or update the SMFDIRECTOR statement.
Edit prefix.MICS.PARMS(JCLDEF) and find the
SMFDIRECTOR statement and add the components
identified in step 3 above.
__ 6. Specify your DAYSMF requirements.
Edit prefix.MICS.PARMS(JCLDEF) and find the DAYSMF
keyword and based on your needs identified in step 3
above, either leave it as is, or change it to:
DAYSMF OFF
or
DAYSMF EXCLUDE ccc
ccc is the 3 character component identifier to remove
those products that no longer require the additional
split processing performed by DAYSMF.
Note: This is not restricted to products using CA SMF
Director as input, but may include any SMF eligible
component.
__ 7. Review your SMFRECORDING statement.
Edit prefix.MICS.PARMS(JCLDEF) and find the
SMFRECORDING statement and ensure it still accurately
reflects the component input source. You only need to
include an optional SMF component on the
SMFRECORDING statement if you wish to process
the data in DAYSMF.
INPUTccc and INPUTRDR definitions:
__ 8. For each component defined on the SMFDIRECTOR
statement, that is NOT being processed
in DAYSMF:
Edit prefix.MICS.PARMS(INPUTccc) and insert the
SMFDRCTR DD referring to the CA SMF Director duplicate
split index, identified in step 5 above.
If you are also processing standard SMF input for the
same component, insert the completed INPUTSMF
DD in the same member.
The 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.
Note: If only one component uses SMF input,
JCLGEN does not create a DAYSMF step to split the SMF
input file. Rather, the SMF File that is defined in
prefix.MICS.PARMS(INPUTRDR) goes directly into the
DAILY job step for that one product.
If you specified DAYSMF OFF, then all input data,
regardless of its origin will be input from each
component's corresponding prefix.MICS.PARMS(INPUTccc)
member.
__ 9. If you have enabled Incremental Update for a component
in this unit and wish to process the CA SMF Director
split data sets, you must define the duplicate split
index in the corresponding prefix.MICS.PARMS(INPUTccc)
member.
If however, you are using the SPLITSMF job for this
component, you must instead update the
prefix.MICS.PARMS(INPUTRDR) member.
Generation:
__ 10. 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. Verify whether
this message correctly reflects your definitions for
products using SMF and CA SMF Director, as well as the
components included in the DAYSMF step. Make any
changes necessary and submit the job again until you
achieve the desired results.
__ 11. Suspend Unit Operations
At this point, you must suspend the operation of the
unit database being changed. Enter the Operational
Status and Tracking SUSPEND command to suspend
operational processing in the unit (MWF;5;1).
__ 12. Generate Operational Jobs
Edit prefix.MICS.PARMS(JCLGENU) and add a line to
generate the DAILY, INCRccc and DAYSMFR jobs as
applicable. For example,
DAILY INCRccc DAYSMFR
Edit prefix.MICS.CNTL(JCLGENU) and submit the job for
execution. This job should complete with a return code
of zero.
__ 13. Prior to execution of the DAILY job, review the
checklist in section 4.10.4.2 for additional
operational considerations.
__ 14. (Optional) Delete SMF work data sets
When the DAYSMF step is present, a 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 FILES.
If you deactivated DAYSMF or excluded a component,
you should review these data sets and if they
are no longer being used, these data sets may be
deleted.
+--------------------------------------------------------------------------+ | CA SMF Director Integration - CA SMF Director Definitions | | | +--------------------------------------------------------------------------+ Control Definitions | | | COMPONENTS ____ ____ ____ ____ ____ (RMF, SMF, TSO, etc.) | | SMFRECORDING ____ ____ ____ (AST, CIC, IDM, HSM, SNT, VCA, WEB) | | | | PARMS Library Member is JCLDEF - Reference Sections: 2.3.3.2.1 | +--------------------------------------------------------------------------+ | | Execution Option | DAYSMF FILES _________ (TEMPORARY or PERMANENT) | | DAYSMF OFF _________ (deactivates DAYSMF step in this unit) | | DAYSMF EXCLUDE ___ ___ ___ ___ (RMF, SMF, TSO, etc.) | | SMFDIRECTOR ____ ____ ____ ___ (RMF, SMF, TSO, etc.) | | | | PARMS Library Member is JCLDEF - Reference Sections: 2.3.3.2.1 | +--------------------------------------------------------------------------+
Figure 4-01. CA SMF Director Worksheet Part 1 of 2
+----------------------------------------------------------------------------------------------------------------------+ | CA SMF Director Integration Worksheet - Duplicate Split Index Layout | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | | | | Std |Duplicate|Duplicate|Duplicate|Duplicate|Duplicate|Duplicate|Duplicate|Duplicate|Duplicate| | CA MICS | Unit | SMF | Split | Split | Split | Split | Split | Split | Split | Split | Split | | Product | Identifier| Input| Index 1 | Index 2 | Index 3 | Index 4 | Index 5 | Index 6 | Index 7 | Index 8 | Index 9 | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | AST | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | CIC | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | DB2 | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | HSM | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | IDM | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | MQS | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | RMF | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | SMF | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | SNT | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | TSO | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | VCA | | | | | | | | | | | | |---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | WEB | | | | | | | | | | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | | | | | | | | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | | | | | | | | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | | | | | | | | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | | | | | | | | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | | | | | | | | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | | | | | | | | | | +---------+-----------+------+---------+---------+---------+---------+---------+---------+---------+---------+---------+ | | | | | CA SMF Director Integration - Reference Sections: 4.10 | | Note: The figure ends at CA SMF Duplicate Split Index 9, but there is no restriction on the number of indices you | | may define or input to a CA MICS component step. | +----------------------------------------------------------------------------------------------------------------------+
Figure 4-02. CA SMF Director Worksheet Part 2 of 2 The ideal CA SMF Director implementation for your CA MICS environment should base the creation of the SMF split data sets and corresponding duplicate split index entries on your component and unit requirements. In other words, you must consider the components within a unit and across multiple units when deciding how to record the SMF split data sets into the duplicate split index. Proper planning will save processing time and system resources by enabling CA MICS to select ONLY the necessary SMF data for a component and/or unit. Important items to consider: o Is this same component defined in multiple units? If the answer is yes, then each unit should record their split index entries to separate duplicate split indices. In this way, each unit will read ONLY the records needed for their unit. o Do I have SMF data from multiple systems all processed within the same CA MICS unit? If the answer is yes, then each system should record their split index entries to the same duplicate split index. This way, CA MICS can read one index and obtain all the records required for that unit's DAILY update. Alternatively, each system could record their split index entries to a unique duplicate split index and all the indices for that component could be input to the same component step. In either case, it is extremely important to ensure that the duplicate split index ONLY contains the entries required for this component and no other. In other words, no other record types should be using the same duplicate split index, regardless of the unit. o Do I have units with multiple components? If the answer is yes, the split index entries should also be segregated by component. Each component in the unit should have their split index entries recorded to a separate duplicate split index. This enables the duplicate split index to be input directly to the component step and select only the split index entries necessary to satisfy that components needs. The Worksheet in Figure 4-02 can be both a planning tool for new CA SMF Director implementations as well as a visual aid for migrating your current CA SMF Director implementation to the optimum setup to suit your CA MICS environment. Using the worksheet provided in Figure 4-02, enter the Unit Identifier for each component you have installed in a unit. If the SMF data for a component is contained in a CA SMF duplicate split index, type X in the duplicate split index column for that SMF data type. For example, if RMF data is recorded to duplicate split index 1, type X in that column. Once you have identified all the components, their corresponding unit identifier, SMF data source (standard SMF or CA SMF Director) and in which duplicate split index their entries reside, you're prepared to evaluate the contents of the worksheet and tailor CA SMF Director (or CA MICS) accordingly. Visually, the best implementation is to have only one 'X' per column. This would mean that each component can simply input the CA SMF Director duplicate split index that contains only their required entries, and avoid processing any unnecessary data. If you have multiple 'X's per row, this would mean you have multiple indices to input to the same component. This too is fine as long as none of the indices are shared between components (again, only one 'X' per column). This would be the equivalent of Implementation Scenario 2, in section 4.3.2 of this guide. For example, using the sample completed worksheet in Figure 4-03, would result in the following CA MICS implementation: Unit P contains components AST, RMF, SMF, and TSO. To avoid redundant processing of SMF data, each are recording their split index entries to distinct CA SMF Director duplicate split indices. This allows each to be directly input to their component step. The SMF component is only in one unit, P, but has entries for split data sets in both duplicate split indices 3 and 9. Both should be defined to the DAY030 step in unit P. The CIC component resides in two units. Both unit's split index entries are recorded to distinct duplicate split indices, (in this example, indices 5 & 6) enabling each unit to read just the SMF records required for that unit. Since no other SMF data is being recorded to the same duplicate split index we will modify prefix.MICS.PARMS(INPUTCIC) for unit C to include the SMFDRCTR DD defining CA SMF Director duplicate split index 5 for direct input to DAY040. We will also modify prefix.MICS.PARMS(INPUTCIC) for unit 4 to include the SMFDRCTR DD defining CA SMF Director duplicate split index 6 for direct input to DAY040. The split data sets for the DB2 component in Unit D as well as the VCA component in unit S, are also recorded to a separate CA SMF Director duplicate split index so they too will be input directly to the corresponding component step. The worksheet also shows that the VCA component has standard SMF input.
+--------------------------------------------------------------------------------------------------------------------------+ | CA SMF Director Integration Worksheet - Duplicate Split Index Sample Layout | | | +---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | | | | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | CA SMF | | | | Std | Duplicate| Duplicate| Duplicate| Duplicate| Duplicate| Duplicate| Duplicate| Duplicate| Duplicate| | CA MICS | Unit | SMF | Split | Split | Split | Split | Split | Split | Split | Split | Split | | Product | ID | Input| Index 1 | Index 2 | Index 3 | Index 4 | Index 5 | Index 6 | Index 7 | Index 8 | Index 9 | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | | SYSPROG. | SYSPROG. | SYSPROG. | SYSPROG. | SYSPROG. | SYSPROG. | SYSPROG. | SYSPROG. | SYSPROG. | | Index Data Set Name : | DIRCTR. | DIRCTR. | DIRCTR. | DIRCTR. | DIRCTR. | DIRCTR. | DIRCTR. | DIRCTR. | DIRCTR. | | | SPLITIN1 | SPLITIN2 | SPLITIN3 | SPLITIN4 | SPLITIN5 | SPLITIN6 | SPLITIN7 | SPLITIN8 | SPLITIN9 | +---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | AST | P | | X | | | | | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | CIC | C | | | | | | X | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | DB2 | D | | | | | | | | X | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | HSM | | | | | | | | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | IDM | | | | | | | | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | MQS | | | | | | | | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | RMF | P | | | X | | | | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | SMF | P | | | | X | | | | | | X | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | SNT | | | | | | | | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | TSO | P | | | | | X | | | | | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | VCA | S | Yes | | | | | | | | X | | |---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | WEB | | | | | | | | | | | | +---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | | | | | | | | | | | | | +---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | CIC | 4 | | | | | | | X | | | | +---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | | | | | | | | | | | | | +---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | | | | | | | | | | | | | +---------+------+------+----------+----------+----------+----------+----------+----------+----------+----------+----------+ | | | | | CA SMF Director Integration - Reference Sections: 4.10 | | Note: The figure ends at CA SMF Duplicate Split Index 9, but there is no restriction on the number of indices you may | | define or input to a CA MICS component step. | +--------------------------------------------------------------------------------------------------------------------------+
Figure 4-03. CA SMF Director Sample Worksheet
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |