7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.4 Physical Hardware Data Element Assignment (RMFPHYDE)

7.3.4 Physical Hardware Data Element Assignment (RMFPHYDE)

This section shows you how to assign values to Physical
Hardware (HARPHY) file data elements through RMFPHYDE
parameters.

This facility is intended for assignment of power consumption
ratings to mainframe hardware, enabling the calculation of
hardware power use and cost.  While pre-supplied power
related HARPHY data elements are delivered in RMFGENIN for
that purpose, this facility is designed to be customer
extensible via the addition of any desired hardware related
data elements. Additionally, the _USRSPHY user exit is
provided to perform any desired calculations.

Generation of the RMFPHYDE parm member is optional. If
RMFPHYDE is present in prefix.MICS.PARMS during execution of
RMFPGEN, the $RMFPHY format will be created.  The $RMFPHY
format is subsequently used during DAY020 daily processing to
assign values to HARPHY data elements as specified in
RMFPHYDE.



Physical Hardware Data Element Assignment Processing Steps


------------    .--------.   1. Run RMFPHYCP. Creates
|          |   .  DETAIL  .     prefix.MICS.PARMS member
| RMFPHYCP |<--|.        .|     RMFPHYDU.  RMFPHYDU contains
|          |   | -------- |     one Key ID statement (CPC,
------------   |  HARDVA  |     DEV, or LDV) for each
     |         |  HARIPU  |     physical CPC or device, or
     v         .          .     logical device group.
 /----------    ----------
/          |
| RMFPHYDU |
|          |
------------
     |
     v
------------                 2. Update RMFPHYDU. Insert Data
|-Update   |                    Element Assignment statements
| RMFPHYDU |                    after Key ID statements to
|          |                    assign specific Data Element
|-Copy to  |                    values.
| RMFPHYDE |
------------                    The DEFAULT statement may be
|  qwerty  |                    used to indicate that
------------                    follow-on Data Element
     |                          Assignment statements apply
     |                          globally.
     v
 /----------                    Once updates are complete,
/          |                    copy or rename RMFPHYDU to
| RMFPHYDE |                    RMFPHYDE.
|          |
------------
     |
     v
------------    .--------.   3. Run RMFPGEN. RMFPGEN creates
|          |   .  MUOLIB  .     the $RMFPHY format used to
| RMFPGEN  |-->|.        .|     assign values for data
|          |   | -------- |     elements specified in
------------   | $RMFPHY  |     RMFPHYDE.
               |          |
     ----------.          .
     |          ----------
     v
------------    .--------.   4. Daily processing. DAY020 uses
|          |   .  DAYS    .     the $RMFPHY format to obtain
| DAY020   |-->|.        .|     values for each physical CPC
|          |   | -------- |     or device, or logical device
-------------  |  HARPHY  |     group that had a Data Element
 | _USRSPHY |  .          .     Assignment statement, either
 ------------   ----------      explicit or via a DEFAULT
                                assignment statement. If any
                                computed or accumulated
                                HARPHY data elements are
                                required, code must be placed
                                in the _USRSPHY user exit.



Optional Statements
-------------------
CPC, DEV and LDV Key ID statements
DEFAULT statement
Data Element Assignment statement

Comments are coded by beginning the statement with an
asterisk (*).  Blank statements are allowed.

The following sections explain each of the statements
specified in prefix.MICS.PARMS(RMFPHYDE) and the utility used
to create them.

    1 - Physical Hardware Create Parms (RMFPHYCP) Utility
    2 - CPC, DEV, and LDV Key ID Statements
    3 - DEFAULT Statement
    4 - Data Element Assignment Statement