Previous Topic: 7.3.4 Physical Hardware Data Element Assignment (RMFPHYDE)

Next Topic: 7.3.4.2 CPC, DEV, and LDV Key ID Statements

7.3.4.1 Physical Hardware Create Parms (RMFPHYCP) Utility


The Physical Hardware Create Parms (RMFPHYCP) Utility creates
parm member RMFPHYDU in your prefix.MICS.PARMS library.  This
parm member can then be modified to provide values to be
assigned during the creation of the Physical Hardware
(HARPHY) file.  The generated RMFPHYDU parm member will
contain CPC, DEV, and LDV Key ID statements representing
hardware found in the Individual Processor Activity (HARIPU)
and Device Activity (HARDVA) files.

Note:  Customers who install CA MICS for the first time must
       execute a daily processing update in order to populate
       the HARIPU and HARDVA files before executing the
       RMFPHYCP utility.

The RMFPHYCP utility can be run in any unit that has the
HARPHY file activated and where data element assignments are
required.  RMFPHYCP does not create the RMFPHYDE member used
by RMFPGEN, but instead creates the RMFPHYDU PARM member,
leaving an existing RMFPHYDE production member unmodified.
Once RMFPHYDU is updated, it can be copied or renamed to
RMFPHYDE and RMFPGEN can be run.  RMFPGEN creates the $RMFPHY
format in the unit level MUOLIB.  $RMFPHY is subsequently
used by the DAY020 daily processing to assign values to
HARPHY data elements.

The first time RMFPHYCP is run in a given unit, the RMFPHYDU
parm member will be created exclusively from the HARDVA and
HARIPU files, comprised of only CPC, DEV, and LDV statements.
Any subsequent customer updates to add Data Element
Assignment are then made and RMFPHYDU is copied or renamed to
RMFPHYDE in prefix.MICS.PARMS.

Subsequent runs of the RMFPHYCP utility to discover any new
physical CPCs or devices, or logical device groups, will
create a new RMFPHYDU prefix.MICS.PARMS member.  However,
when an existing RMFPHYDE member is found in
prefix.MICS.PARMS, its information will be retained
(including any customer updates) and any new CPC, DEV, and
LDV statements for physical CPCs or devices, or logical
device groups not represented in the existing RMFPHYDE parms
member will be added to create the new RMFPHYDU
prefix.MICS.PARMS member.

Note:  Executing RMFPHYCP will overlay the existing RMFPHYDU
       member in prefix.MICS.PARMS.  Be sure to copy or
       rename RMFPHYDU to RMFPHYDE prior to re-running
       RMFPHYCP.

To execute the Physical Hardware Create Parms (RMFPHYCP)
Utility, invoke CA MICS Administrator Utilities (MWF;5;4) and
select option 9:

-------------  CA MICS Administrator Utilities  -------------
Option ===>

       1 - Compression Candidacy Report
       2 - Compression Recommendation Reports
       3 - Component ESSENTIAL and DERIVED Options Report
       4 - Database Modification Report
       5 - Database Health Check Utility
       6 - Space Utilization and Reporting
       7 - Inactive Data Elements Report
       8 - SAS Format/Informat Print Utility
       9 - Physical Hardware Parm Creation
       T - Tutorial
       X - Exit