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.

<strong>Software</strong> License Management <strong>and</strong> LIBSAVE/LIBLOAD<br />

3. Register System B Image Enabler key tape values MCN2 <strong>and</strong> SCN2 onto System B.<br />

Image Enabler<br />

Keys<br />

System A System B<br />

Product<br />

Key<br />

Image Enabler<br />

Keys<br />

Product<br />

Key<br />

MCN1 SCN1 SCN1 MCN2 SCN2 SCN1 No.<br />

In Compliance<br />

Product key SCN does not<br />

match Image Enabler key SCN.<br />

4. Register System B <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> software product tape with the value of<br />

SCN2.<br />

Image Enabler<br />

Keys<br />

System A System B<br />

Product<br />

Key<br />

Image Enabler<br />

Keys<br />

Product<br />

Key<br />

MCN1 SCN1 SCN1 MCN2 SCN2 SCN2 Yes.<br />

In Compliance<br />

Image Enabler key <strong>and</strong> SCN<br />

key information is in<br />

compliance on System B.<br />

5. Use SOLAR to run the PRODRT installed product report to verify the system’s<br />

software license compliance.<br />

• All products authorized with System B product keys tape have SCN2 associated<br />

with them.<br />

• If a product authorized on System A does not have a corresponding product key<br />

with SCN2 registered on System B, the product, <strong>and</strong> its key with SCN1 are not<br />

in compliance <strong>and</strong> should be removed from System B using SOLAR.<br />

3–26 7831 0349–043

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

Saved successfully!

Ooh no, something went wrong!