4. Operation › 4.5 Integrating CA MICS Data to NSM › 4.5.2 Integration with NSM Performance Trend › 4.5.2.1 Parameter Specification

4.5.2.1 Parameter Specification

To enable a CA MICS component to NSM Performance Trend, you
must first add a member in sharedprefix.MICS.PARMS defining
what data should be extracted from a CA MICS component:

The following statements are supported:

COMP ccc
FILE iiifff <file description>
SASDS saswork
NAME element <element label>
DEPADD element element ...
WORKLOAD element element ...

Note:  All statements are required unless explicitly labeled
       as optional.

COMP       Specifies the three-letter CA MICS component
           identifier from which performance data will be
           extracted.  It must be the first statement in the
           member and can only be specified once.  For
           example, RMF.

FILE       Specifies the six-character CA MICS file from
           which to extract output data, e.g., HARCPU.  This
           file must pertain to the component specified in
           the COMP statement.  Optionally, following the
           CA MICS file name, you can specify the file
           description.  The description will appear in the
           Resource Type column in the output.  If omitted,
           the three-letter component identifier followed by
           the file description defined in cccGENIN will be
           used.

SASDS      Specifies a valid one- to eight-character SAS work
           data set name.  The data set name is assigned
           using the "CA MICS File Selection" panel in MICF
           during MICF inquiry creation (Step 2.3).

NAME       Specifies a CA MICS element name.  The element
           will be extracted from the SAS data set defined by
           the SASDS statement.  Optionally, you can specify
           a label for the element following the element
           name.  The label will appear in the Resource
           Subtype column in the output.  If omitted, the
           label defined for the element in cccGENIN will be
           used.  You can specify one or more NAME
           statements.

DEPADD     (Optional) Specifies one or more dependent
           elements that were erroneously excluded from
           cccGENIN for a computed element selected by the
           NAME statement.  You may specify one or more
           DEPADD statements.  Note that this statement
           should ONLY be used to circumvent the problem when
           cccGENIN does not list all the dependent elements
           in the DEPEND statement(s) for the elements that
           you want to retrieve.

WORKLOAD   (Optional) Specifies one or more CA MICS elements
           that will be used to group the CA MICS data into
           categories for each unique combination of values
           from the elements.  The values of the WORKLOAD
           elements will appear in the Resource Instance
           column in the output file.

*          Comments.  Lines beginning with asterisks (*) are
           ignored.

For Example:

   COMP RMF
   *
   FILE HARCPU   MVS CPU Activity
   SASDS FILE1
   NAME CPUPCBSY Pct Processor Busy
   NAME CPUAVB   Avg Batch Users
   NAME CPUAVT   Avg TSO Users
   NAME CPUAVS   Avg Started Tasks
   NAME CPUSLIH  Total # of Entries to the I/O SLIH
   NAME CPUTPI   Total # of TPI I/O Events
   *
   FILE SCPPSD   MVS Page/Swap Data Set Activity
   SASDS FILE2
   NAME PSDAVU   Avg Used Slots or Swap Sets
   NAME PSDAVA   Avg Allocated Slots
   NAME PSDPGX   Pages Transferred
   NAME PSDAVSTM Avg Service Time
   WORKLOAD PSDPST

Note:  When a Performance Trend inquiry runs for the first
       time, SAS code is generated and stored in a member in
       sharedprefix.MICS.SOURCE based on the associated
       parameter file in sharedprefix.MICS.PARMS.  The member
       name in sharedprefix.MICS.SOURCE is the same as the
       parameter file.  The code in SOURCE will be directly
       invoked by the subsequent runs if it has been built.
       The CA MICS data extract program will not regenerate
       the code again for efficiency reasons.  Therefore, if
       you make a change to a parameter file, you MUST delete
       the corresponding member in sharedprefix.MICS.SOURCE
       for the change to take effect.