7. PARAMETERS › 7.2 Complex Level Parameters

7.2 Complex Level Parameters

Complex level parameters describe components to the CA MICS
system.  Each CA MICS component has a generation definition
member in the sharedprefix.MICS.GENLIB library.  The
generation definition member for the Hardware and SCP
Analyzer is RMFGENIN.

Section 4.2.4 of the System Modification Guide describes the
generator definition statements in detail.  The discussion
presented here provides RMF component-specific details about
the following generator definition statements:

o the COMPJOB statement
o the INPUTSOURCE statement
o the FILE statements
o the CYCLES statements
o the COMPRESS statement

Note:  The RMFGENIN member contains uppercase and lowercase
       characters.  Enter the keywords in UPPERCASE.

COMPJOB Statement
-----------------

The optional COMPJOB statement defines product processing in
the operational jobs.

By default, the Hardware and SCP Analyzer's data is
processed by the DAILY, WEEKLY, MONTHLY, and YEARLY jobs.
Exceptions will be reported by the DAILY, WEEKLY, and
MONTHLY jobs, and archive audit, weekly history, and
monthly history files will be maintained.

If you choose to change these specifications following the
guidance in the System Modification Guide, the new
specifications will not take effect until an RMFCGEN is
successfully completed.

INPUTSOURCE Statement
---------------------

The optional INPUTSOURCE statement lists the data source
(SMF) and record types supported by the Hardware and SCP
Analyzer.

The default statement delivered with the product is:

INPUTSOURCE SMF 70 71 72 73 74 75 76 77 78 79

indicating that the data source is SMF data from records
70 through 79.  Edit this statement if your site does not use
all of these record types, and run an RMFCGEN to activate
your new definitions.

FILE Statements
---------------

Each file supported by the Hardware and SCP Analyzer is
defined by a required FILE statement.  FILE statements are
described in Section 4.2.4.2.1 of the System Modification
Guide.

The timespan activation values in the Hardware and SCP
Analyzer FILE statements specify whether the file is active
in each particular timespan.

Considerations for Derived Files:

Certain Hardware and SCP Analyzer files are derived from
other files.  Derived files cannot be turned on in any
timespan unless their source files are turned on and have a
cycle retention value (see CYCLES Statements below) of at
least one in the DAYS timespan.

Derived files contain an E in their DAYS timespan definition
indicating that special processing must be performed on the
file by means of an exit.  Derived files cannot be turned on:

o In the DETAIL timespan

o In any other timespan unless their source files are turned
  on and have a cycle retention value of at least one in the
  DAYS timespan

Following is a list of derived and source Hardware and SCP
Analyzer files:

Derived File      Source Files
------------      ----------------------
  HARDTA          HARDVA
  HARSGA          HARDVA
  HARPHY          HARDVA, HARIPU
  SCPLCU          HARDVA, SCPLCA, SCPIOC

CYCLES Statements
-----------------

Each FILE statement has a corresponding required CYCLES
statement that specifies the number of cycles of data to keep
for the file in each timespan if the file has been activated
for that particular timespan (through its FILE statement).

If a file has been activated as a whole, but if it has been
deactivated for a particular timespan, the database cycle
retention value is zero, regardless of its CYCLES statement
value.

$HEDE COMPRESS Statement
------------------

The optional COMPRESS statement defines whether a file is
eligible to be compressed when the compression facility is
activated.

COMPRESS statements apply to FILE statements; only one
COMPRESS statement is permitted per file.

If you code a COMPRESS statement, first review the default
statement provided in RMFGENIN.  If the default COMPRESS
statement is coded with a comment stating that the file
should not be compressed, DO NOT change the specification.
Doing so will inhibit the performance of your CA MICS system.

If you deactivate a file, review its COMPRESS statement, if
present, and ensure that compression is set to NO for the
deactivated timespan.