7. PARAMETERS › 7.1 Environmental Considerations

7.1 Environmental Considerations

Before coding product parameters, you need to know about the
MVS environment(s) at your installation.  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 you 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 to 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 Network Analyzer processes input data from more
than one source.  All input data is processed by the DAY056
step in the DAILY job as part of the same process.  By
reviewing the MICSLOG output of the DAY056 step of the DAILY
job, you can determine exactly what SMF record types and
subtypes were present in the input data stream for each of
your MVS or VM hosts.

Following CA MICS standards, if an installation fails to
provide input from ANY source, the DAY056 step will fail with
a U300 ABEND.  When you expect this problem but must run the
DAILY job anyway, code SYSPARM=NODATA on the EXEC statement
of the DAY056 step to prevent the ABEND.

There is no parameterized provision in CA MICS to cause a
similar ABEND when data from one of the required sources is
missing but data from other sources is present.  If this
might happen at your installation, consider coding the
_USRIHL exit to examine the Input History Log file from the
DETAIL timespan at the end of DAILY processing.  This
routine, and a sample exit which provides this function, are
documented in Chapter 10.