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

Initializing an Existing System (I-Boot)
• If you are migrating a Dorado 400 system, DDP PPC 7R3A requires the following
configuration changes to run on a Dorado 400 system with CPCommOS2R2:
The CPMODE keyword in the OSITSU and TASTSU records of the DDP-PPC
configuration file must be set to CMSA (CPMODE=CMSA).
• For ClearPath OS 2200 Release 13.2 platform installation, the products on tapes
CP13, CP14, or CP16 are usually customized prior to installation. The products
on these package tapes can be installed after the platform is established.
8. Install, configure, and boot OPE. Then take one of the following steps:
• If you plan to customize the Exec, TIPUTIL, DPS, and MCB, continue with step 9
of this installation sequence.
• If you do not plan to customize the Exec, TIPUTIL, DPS, and MCB, go to step 14.
You can use the CP-OE2 tape to install DPS, TIPUTIL, and MCB in default mode.
9. 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. This file is still needed, however.
• 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.
10. Install the separately packaged Exec features that your site has ordered from the
CP-SPF tape. See Appendix C for a listing of the Exec features on the CP-SPF tape.
11. Generate Exec level 48R8A (ClearPath OS 2200 Release 13.2). During system
generation, all SGS configuration labels found in the CO$CONFIG element are
compared to a list of valid configuration SGSs. See 4.2 for a listing of any obsolete
SGS configuration labels that should be removed.
If an invalid SGS is detected, the following error occurs and the system generation
stops:
ERROR - CO$CONFIG SGS LABEL name
IS NOT VALID BECAUSE IT IS MISSPELLED, IS OBSOLETE, OR
HAS AN IMBEDDED SEMICOLON. VERIFY THE SPELLING, REMOVE
THE OBSOLETE SGS(S), OR CORRECT THE IMBEDDED SEMICOLON!
7–30 7831 0349–043