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.

4.1.2. <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0<br />

KEYTABLE$ Migration Code<br />

General Exec Considerations<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 changes in<br />

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

enhanced version of the system key table written by SOLAR level 4R7 or higher. You<br />

must update <strong>and</strong> boot your current EXEC to include this KEYTABLE$ migration code<br />

before installing SOLAR level 4R7. FURPUR level 32R5A or higher is also required.<br />

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

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

register any key, the SYS$*DATA$.KEYTABLE$ is written in the new format which is not<br />

recognized by previous levels of SOLAR or the Exec. All previous product installation,<br />

feature, <strong>and</strong> Exec image enabler model-based, MIPS-based, <strong>and</strong> MIPS metered keys are<br />

compatible with SOLAR level 4R7 or higher.<br />

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

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

able to boot <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0 EXEC level 48R7. This issue can only arise<br />

if the EXEC level you are currently running is 48R4 (<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.0).<br />

EXEC levels 48R5 <strong>and</strong> 48R6 already contain the necessary change. If you are a Dorado<br />

400 or Dorado 4000 customer <strong>and</strong> are running EXEC level 48R4, you must build <strong>and</strong> boot<br />

PLE 18691159 before you make any attempt to boot EXEC level 48R7.<br />

4.1.3. <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.1<br />

SIP Real Memory Utilization Statistics<br />

With the incorporation of PLE 18683962 into <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> 12.1, some of the SIP<br />

Real Memory Utilization (RMU) statistics may no longer be zero for Dorado 400 <strong>and</strong><br />

Dorado 4000 systems. Beginning with <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> 12.1, Exec maintains values<br />

for the RMU time-product that indicates the amount of memory that is in use (Active)<br />

over time. It reflects the aggregate physical memory usage on the system by both Exec<br />

<strong>and</strong> SAIL <strong>and</strong> can be used to track overall system memory usage. The existing Absolute<br />

Memory statistics remain unchanged.<br />

RUN$ Runstream Changes<br />

The following products have changed their RUN$ runstream RunIDs for this release.<br />

Product Eltname<br />

Old<br />

RunID<br />

New<br />

RunID<br />

MSCP MSCP MSCP MSCP<br />

MSCP MSCPRT (new run) MSCPRT<br />

MSCP MSCP/RT MSCPRT MSCPRT<br />

IRU IRU IRU IRUREC<br />

7831 0349–043 4–3

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

Saved successfully!

Ooh no, something went wrong!