4. Operation › 4.4 Administering CA MICS › 4.4.4 CA MICS Administrator Utilities › 4.4.4.9 Physical Hardware Parameter Creation
4.4.4.9 Physical Hardware Parameter Creation
--------------- Physical Hardware Parm Creation ------- Row 1 of 3
Command ===> Scroll ===> CSR
Line Commands: S Select one of the following Unit IDs
to execute RMFPHYCP
Cmd Unit ID Description
- ------- ----------------------------------------
_ G C A
_ P CA
_ 8 C A
******************************* Bottom of data ************************
Use the Physical Hardware Create Parms (RMFPHYCP) utility to
create member RMFPHYDU in your prefix.MICS.PARMS library.
This member can then be modified to provide values to be
assigned during the creation of the Physical Hardware
(HARPHY) file. The RMFPHYCP utility can be run in any unit
that has the HARPHY file activated and where data element
assignments are required.
Member RMFPHYDU will contain CPC, DEV, and LDV key ID
statements representing hardware found in the Individual
Processor Activity (HARIPU) and Device Activity (HARDVA)
files.
Note that 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 job to
assign values to HARPHY data elements.
The first time RMFPHYCP is run in a given unit, the RMFPHYDU
PARM member is created exclusively from the HARDVA and HARIPU
files, comprised of only CPC, DEV, and LDV statements. Any
subsequent user updates to add data element assignments can
then be 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 create a
new RMFPHYDU prefix.MICS.PARMS member. If an existing
RMFPHYDE member is found in prefix.MICS.PARMS, its
information is retained (including any user updates) and any
new CPC, DEV, and LDV statements for physical CPCs or devices
or logical device groups are added to create the new RMFPHYDU
prefix.MICS.PARMS member.
Note: Executing RMFPHYCP overlays the existing RMFPHYDU
member in prefix.MICS.PARMS. Be sure to copy or rename
RMFPHYDU to RMFPHYDE before rerunning RMFPHYCP.