18.08.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Following are the recommended steps:<br />

Installing from Fast-Load Tapes<br />

1. There are three migration issues that may affect cross-booting between EXEC<br />

48R8A <strong>and</strong> older EXEC levels. These issues may require that PLEs be generated<br />

into your older EXEC level <strong>and</strong> booted before you move up to EXEC 48R8A. If you<br />

drop back from EXEC 48R8A to your older EXEC level, you must always drop back to<br />

an EXEC level that includes these PLEs. See Table 7–1 for the required migration<br />

information. A check mark in the table indicates that an action must be taken.<br />

Note: If you are migrating to this release from a release prior to 12.0 there may be<br />

other important cross-boot considerations that are no longer documented here. To<br />

perform a migration from a release prior to 12.0 you should consult the <strong>Planning</strong> <strong>and</strong><br />

Migration Overview documentation associated with release 12.0 <strong>and</strong> possibly<br />

additional prior releases to ensure that any migration issues introduced by all of the<br />

intervening releases have been identified.<br />

There are no cross-boot or migration issues between Exec 48R8 (<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong><br />

<strong>Release</strong> 13.1) <strong>and</strong> Exec 48R8A (<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> <strong>13.2</strong>). Exec 48R7 already<br />

includes all the necessary PLEs. Systems running Exec levels prior to 48R7 should<br />

add the necessary PLEs before booting Exec 48R8.<br />

a. KEYTABLE$ Migration Code<br />

The SOLAR 4R7 Dot-Format Level enhancement introduces an Exec migration<br />

consideration. You must build <strong>and</strong> boot your current Exec to integrate the<br />

changes in PLE 18756811. These fixes are required in order for the Exec to<br />

recognize the new enhanced version of the system key table written by SOLAR<br />

level 4R7 or higher. You must update <strong>and</strong> boot your current EXEC to include this<br />

KEYTABLE$ migration code before installing SOLAR level 4R7A. FURPUR level<br />

32R5B must also be installed.<br />

A SOLAR level 4R7 or higher KEYGEN-created key can only be used on an Exec<br />

that recognizes the new key table version. When SOLAR level 4R7 or higher is<br />

first used to register any key, the SYS$*DATA$.KEYTABLE$ is written in the<br />

new format which is not recognized by previous levels of SOLAR or the Exec.<br />

All previous product installation, feature, <strong>and</strong> Exec image enabler model-based,<br />

MIPS-based, <strong>and</strong> MIPS metered keys are compatible with SOLAR level 4R7 or<br />

higher.<br />

b. Cross-boot consideration for Dorado 400 <strong>and</strong> Dorado 4000<br />

systems<br />

A known problem may prevent existing Dorado 400 or Dorado 4000 systems<br />

from being able to boot <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> <strong>13.2</strong> EXEC level 48R8A.<br />

This issue can only arise if the EXEC level you are currently running is 48R4<br />

(<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.0). EXEC levels 48R5 <strong>and</strong> above already contain<br />

the necessary change. If you are a Dorado 400 or Dorado 4000 customer <strong>and</strong> are<br />

running EXEC level 48R4, you must build <strong>and</strong> boot PLE 18691159 before you<br />

make any attempt to boot EXEC level 48R8.<br />

7831 0349–043 7–7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!