ClearPath OS 2200 Series Release 13.2 Software Planning and ...

Initializing an Existing System (I-Boot)
4. Start the REGISTERPKG runstream to register the supplied Exec key tape (labeled
“Software Controlled Performance Key Tape”) to establish the contracted
performance level for the system. For more information about Software Controlled
Performance (SCP), see 4.8.
5. Start the REGISTERPKG runstream to register the ClearPath OS 2200 Release 13.2
product key tape. A key tape is registered using the same steps as registration for a
package tape. The registration summary report will display all new product
authorizations added to the system. See the file SOLAR*DIAGNOSTIC.
6. For metering-based systems
First install the client component of URU-OS2200. This installation converts the URU
database to the new format. When the client installation is complete, install the
ClearPath OS 2200 component of URU-OS2200 level 5.1 from package tape CP05.
After URU-OS2200 level 5.1 is installed, you cannot revert back to a pre-URU-2200
4.0 level. URU-OS2200 level 5.1 can collect previous COD log data entries created
by previous levels of the Exec, if it is necessary to revert back to a previous Exec.
7. Install the products on fast-load tape CP-OE1A using the INSTALLPKG runstream
and CP-OE1B using the INSTALLIOE runstream. See Appendix C for the contents of
those tapes.
You can selectively install products (in default mode) from either tape using SOLAR.
If you choose to do so, you should follow the order of installation as described in 7.7.
Notes:
• Do not install LINK until URTS, SLIB, and SYSLIB have been installed. If you are
installing the products from the CP-OE1B tape, the INSTALLIOE runstream does
this for you.
• The CP-OE1B tape includes LINK. It is important that you deactivate all active
subsystems that require ongoing LINK services whenever LINK is replaced. To
do this, you can either explicitly deactivate the subsystems, or you can do an
autorecovery through a $! keyin after installing the new level of LINK. See 5.27
for more information.
• When you install a new level of LINK, ELMS must be installed at the same time
to ensure that the ELMS subsystem is loaded by the new LINK.
• The INSTALLPKG runstream for CP-OE1A and the INSTALLIOE runstream for
CP-OE1B will present warning messages because ELMS has not been installed
on the system. These warnings can be ignored, as they will be resolved when
ELMS is installed during the installation of the CP-OE1B Fast Load tape.
**WARNING* PRODLD 23015:
The location of ELMSs processor, MDBREG, could not be ascertained
because ELMS was not installed. The Extended Language Message
System’s search chain could not be updated.
• Check the IPF 1100 Administration Guide for configuration considerations when
installing IPF-compatible products (for example, DDP-FJT or TAS).
• DDP-PPC must be properly conditioned for the system security environment.
See 5.14.
7831 0349–043 7–29