Availability Product Authorization Keys (PAKs) are available
for the OpenVMS Alpha operating system. An OpenVMS Alpha PAK is
identified by the keyword ALPHA in the PAK's option field. Note
the following restrictions:
PAKs having the ALPHA option can be
loaded and used only on Alpha computers. However, they can safely
reside in a license database (LDB) shared by both VAX and Alpha
systems.
Because the LMF for Alpha systems is capable of
handling all types of PAKs, including those for VAX systems, HP
recommends that you perform your LDB tasks using the Alpha LMF.
Availability PAKs for VAX systems (availability
PAKs without the ALPHA option) will not load on Alpha systems. Only
those availability PAKs containing the ALPHA option will load on
Alpha systems.
Other PAK types such as activity (also known as
concurrent or n-user) and personal use (identified by the RESERVE_UNITS
option) work on both VAX and Alpha systems.
Avoid using the following LICENSE commands from
a VAX system on a PAK containing the ALPHA option:
REGISTER
DELETE/STATUS
DISABLE
ENABLE
ISSUE
MOVE
COPY
LIST
Caution: By default, all Alpha
availability PAKs look disabled to a VAX system. Never use the DELETE/STATUS=DISABLED
command from a VAX system on an LDB that contains Alpha PAKs. If you
do, all Alpha PAKs will be deleted.
With the exception of the DELETE/STATUS=DISABLED
command, if you inadvertently use one of the previously listed LICENSE
commands on an Alpha PAK while using a VAX system, the PAK and the database
will not be adversely affected. Repeat the command using LMF running
on an Alpha system, and the PAK should return to a valid state.
If you do not repeat the command using LMF on an
Alpha system, the system that you intended to disable will remain
enabled (the system is not otherwise affected). Only the Alpha LMF
can disable an Alpha PAK.
However, if you attempt to use any of the previously listed
commands on a PAK located in an LDB that is shared with a VAX system,
the following serious problems might result:
Because Alpha PAKs look disabled to
a VAX system, they are normally ignored at load time by VAX systems.
However, if one of the previously listed commands is entered from
a VAX system and the PAK information is not set to a valid state
by an Alpha system, there is a chance the VAX system will attempt
to load the Alpha PAK. Because the VAX system will be unable to
load the PAK, the VAX LMF will report an error.
Even if a valid VAX PAK for the affected product
is in the LDB, it too might not load. In this case, system users
might be denied access to the product.
If the PAK cannot be restored to a valid state because all
Alpha systems are inaccessible for any reason, use your VAX system
to disable the Alpha PAK. This prevents your VAX system from attempting
to load the Alpha PAK.