7. PARAMETERS › 7.1 Environmental Considerations
7.1 Environmental Considerations
Prior to coding product parameters, you need to know about
the environment at your data center. Before you specify
parameters for the product:
o Examine existing user groups, account codes, and job
control information used on the system. This
information helps to code appropriate values for
account codes.
o Review the default options for the parameters to determine
their applicability to your site.
o Review current CA MICS parameter specifications:
- Review database unit specifications to determine which
unit or units should include SMF data.
- Review the SYSID parameter to determine whether it
correlates with the SMF data. Your site's SYSID
definition is located in the prefix.MICS.PARMS data set
associated with each database unit.
- Review the CA MICS ZONE parameter to ensure that it
reflects the variations in SMF data. This parameter is
located in the prefix.MICS.PARMS data set associated
with each database unit.
- Examine existing accounting standards for other CA MICS
products, if applicable, to ensure that CA MICS
Accounting and Chargeback aggregates information
consistently.
The CA MICS Analyzer Option for CA IDMS uses data from the CA
IDMS Performance Monitor. This data can be generated in SMF
data format with a default record type of 230, or in the
DC/UCF system log area. CA MICS only processes data
generated in the SMF data format. It is assumed that the SMF
records will be processed daily.
The SMF record types used by the CA MICS Analyzer Option for
CA IDMS are specified with the INPUTSOURCE statement in
sharedprefix.MICS.GENLIB(IDMGENIN).
By default, each IDMS unit will accept and process the SMF
record types specified with the INPUTSOURCE statement. If
your data center has multiple IDMS units, and you want a unit
to process a subset of the records specified with the
INPUTSOURCE statement, you can use the SMFTYPE parameter in
the unit level prefix.MICS.PARMS(IDMOPS). Details on SMF
record type specifications are described in Section 7.3.2.2,
SMFTYPE Statement.