7. PARAMETERS › 7.1 Environmental Considerations

7.1 Environmental Considerations

Before coding product parameters, you need to know about the
Web Server environment(s) at your installation.  Prior to
specifying parameters for the product:

   o  Examine existing web server applications, and internal
      ownership rules at your site.  You may want to define
      ownership based on file path or other criteria.

   o  Review current CA MICS parameter specifications:

      -  Review database unit specifications to determine
         which unit or units should include Web server data.

      -  Review the SYSID parameter to determine whether it
         conflicts with the Web server data.  Your site's
         SYSID definition is located in the prefix.MICS.PARMS
         data set for each database unit.

      -  Review the CA MICS ZONE parameter to ensure that it
         reflects the variations in Web server data.  This
         parameter is located in the prefix.MICS.PARMS data
         set for each database unit.

      -  Examine existing accounting standards for other
         CA MICS components, if applicable, to ensure that
         the CA MICS Accounting and Chargeback Product
         aggregates information consistently.

The CA MICS Web Analyzer processes input data from the SMF
type 103 record and optionally from the WebSphere Application
Server for OS/390 log data.  All input data is processed by
the DAY052 step in the CA MICS DAILY job as part of the same
process.  By reviewing the MICSLOG output of the DAY052 step
of the CA MICS DAILY job, you can determine exactly what SMF
records and what WLE utility records were present in the
input data stream for each Web Server.

Following the CA MICS standards, if an installation fails to
provide input from ANY source, the DAY052 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 DAY052 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 (SMF
or Log) is missing but data from the other source is present.
If this occurs 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 of this guide.