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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SOLAR <strong>and</strong> SOLAR/E<br />

Note: FURPUR is not required when you use SOLAR to install software from a<br />

keyed software package.<br />

• After you use SOLAR level 4R7 to register a key, if you need to revert to a level of<br />

SOLAR or FURPUR prior to <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0, Unisys recommends<br />

that you perform a LIBLOAD or LIBLOAD/FAS from the library save created before<br />

you started migration.<br />

• If you have not registered a key tape, using SOLAR level 4R7<br />

− You can revert to previous level of SOLAR simply by installing that level.<br />

− You can revert to a previous level of FURPUR by installing that level along with<br />

the corresponding level of SOLAR.<br />

Migration<br />

To migrate to <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0, perform the following steps:<br />

1. Apply the changes in PLE 18756811 to your existing Exec level <strong>and</strong> boot. See a<br />

description of Exec key migration <strong>and</strong> crossboot requirements in Section 7.<br />

2. Install SOLAR level 4R7 <strong>and</strong> FURPUR level 32R5A from the CP-FLD tape. See<br />

Section 7 for the procedure to install the first install tape (CP-FLD).<br />

3. Register the <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0 product key tape. See Section 7 for<br />

the procedure to register the key tape.<br />

The new format for the software product keys includes the release level.<br />

A registered product/feature key <strong>and</strong> its corresponding installed products are in<br />

compliance with the software license only when the <strong>Software</strong> Control Number (SCN)<br />

attached to the key matches the registered Exec image enabler key SCN or active<br />

Primary SCN.<br />

SOLAR level 4R7 does not prevent product key registration or corresponding software<br />

installation if the registered Exec image enabler key already contains a different SCN.<br />

Instead, SOLAR writes a warning message to the diagnostic file <strong>and</strong>, if executed in<br />

batch, displays a console message indicating that a noncompliance has occurred.<br />

Verify that the SCN listed on the product key tape label corresponds to the<br />

system/partition workload before registering it. If necessary, take corrective action to<br />

comply with your software license agreement, as follows:<br />

• If the Exec image enabler key contains the correct SCN, simply locate the correct<br />

product key tape <strong>and</strong> register it.<br />

• If the Exec image enabler key was populated with an incorrect SCN while migrating<br />

to <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0, use LIBLOAD to go back to the system state<br />

that existed prior to registering the incorrect product key tape <strong>and</strong> register the<br />

correct product key tape.<br />

• If the Exec image enabler key was populated with an incorrect SCN while migrating<br />

to <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0 or earlier, contact your Unisys Support Center for<br />

assistance.<br />

5–48 7831 0349–043

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

Saved successfully!

Ooh no, something went wrong!