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

Installing from Package Tapes
4. Start the REGISTERPKG runstream to register the ClearPath OS 2200 Release 13.2
product key tape using the SOLAR level received with this release. 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.
Note: When SOLAR 4R7 or above is first used and any key is registered (software
product key or Exec key), the SYS$*DATA$ KEYTABLE$ format is extended to
version 8 and is not recognized by previous levels of SOLAR or Exec levels that do
not have PLE 18756811 applied. The ability to use SOLAR 4R7A on previous Exec
levels is required for crossbooting.
Use of a SOLAR 4R7 or above KEYGEN created Exec key can only be used on an
Exec which recognizes the new SOLAR keytable version 8 expanded definitions.
5. For metering-based systems
First install the Windows component of URU-OS2200. This installation converts the
URU database to the new format. When the Windows installation is complete, install
the OS 2200 component of URU-OS2200 (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.
6. Prepare the ClearPath OS 2200 Release 13.2 versions of these library files:
MCODE$, LIB$, RUN$, RLIB$, and PRINTER$. All five files are required for system
generation, regardless of system type. Either copy the files from the release master
tape to another tape or catalog five mass storage files and copy the library files into
them (one library file per mass storage file). Refer to the Exec System Software
Installation and Configuration Guide for the specific runstreams to use.
Notes:
• You can use the POSTOEXMSTR utility to position the package tape to the first
file of the Exec Release Master files.
• The MCODE$ file is empty; however, this file is still needed.
• The Exec level 48.0 base symbolic tape has three files: Utility, Base Symbolics,
and the last 47-level PCF file. The PCF file on the base symbolic tape is needed
to upgrade 47-level local code. The file name EXEC48-PCF47*PCF$.
distinguishes the 48R1 PCF file from the 47-level PCF file.
7. Install the separately packaged Exec features that your site has ordered from the
CP-SPF tape. Refer Appendix C for a listing of the Exec features on the CP-SPF tape.
Caution
Unisys recommends that you perform an INSPECT generation before a FULL
or CONFIGURATION generation. The INSPECT generation allows you to
simulate an actual system generation to ensure that there are no syntactical
errors. The INSPECT generation checks all the skeletons for errors without
stopping in a skeleton that contains a fatal error. This process detects more
errors using fewer trial-and-error passes.
7831 0349–043 7–19