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 ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Software</strong> License Management <strong>and</strong> LIBSAVE/LIBLOAD<br />
Do <strong>Software</strong> License Management <strong>and</strong> SCNs lock software to a particular<br />
MCN?<br />
No, the SCN is not tied to a product. It is tied only to the product key. This allows<br />
software to be moved to another system provided that the target system has registered<br />
product keys containing a SCN matching the Image Enabler Key SCN. This allows you to<br />
distribute COMUS BUILD output <strong>and</strong> UNSTACK tapes, LIBSAVE/LIBLOAD, <strong>and</strong><br />
SOLAR/E created packages to other systems.<br />
For example, products on MCN1 with SCN1 can be moved to MCN2 with SCN2<br />
provided corresponding product keys with SCN2 are registered on MCN2. <strong>Software</strong> on<br />
the target system MCN2 is in compliance.<br />
Notes:<br />
• If using LIBSAVE/LIBLOAD, the software product keys containing SCN2 must be<br />
reregistered on MCN2.<br />
• <strong>Software</strong> product keys do not need to be reregistered on the MCN2 system<br />
when using COMUS BUILD output <strong>and</strong> UNSTACK tapes, or SOLAR/E created<br />
packages.<br />
3.6. <strong>Software</strong> License Management <strong>and</strong><br />
LIBSAVE/LIBLOAD<br />
LIBSAVE/LIBLOAD processes are used to save <strong>and</strong> restore an instance of the software<br />
libraries on a specific system or partition. These processes can also be used to save an<br />
instance of the software libraries <strong>and</strong> deploy it on another system or partition.<br />
LIBSAVE/LIBLOAD capabilities are available with <strong>Software</strong> License Management.<br />
However, additional steps are now required to perform these processes. To be in<br />
compliance, the <strong>Software</strong> Product key tape <strong>and</strong> the Image Enabler key tape<br />
corresponding to the LIBLOAD system must be registered on the LIBLOAD system<br />
once the LIBLOAD is complete. The following subsections identify the steps required to<br />
properly use LIBSAVE/LIBLOAD functions to save <strong>and</strong> restore the software products,<br />
software product keys, <strong>and</strong> Image Enabler keys.<br />
3.6.1. LIBSAVE/LIBLOAD Examples<br />
Examples in 3.6.2 <strong>and</strong> 3.6.3 show how <strong>Software</strong> License Management affects the<br />
LIBSAVE/LIBLOAD scenario. In the examples, a LIBSAVE is performed on System A.<br />
System A is running <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 10.0 or higher product levels. A<br />
LIBLOAD is performed on two separate systems (System B <strong>and</strong> System C).<br />
The examples show a LIBLOAD on two different systems. There is a slightly different<br />
process depending on whether the LIBLOAD system fits into the System B category or<br />
the System C category. At the end of each example, each system is running <strong>ClearPath</strong><br />
<strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 10.0 or higher products <strong>and</strong> each system complies with the software<br />
license agreement.<br />
Performing the steps in the examples ensures that the proper Image Enabler key <strong>and</strong><br />
software product keys are registered on the LIBLOAD system.<br />
7831 0349–043 3–23
Change language