4.4  OpenVMS Galaxy License PAKs and LMF

  OpenVMS Galaxy PAK names are as follows:

  *   OpenVMS Operating System Base PAK: OPENVMS-
      ALPHA (base license)

  *   OpenVMS Operating System User PAK: OPENVMS-
      ALPHA-USER

  *   OpenVMS Galaxy PAK: OPENVMS-GALAXY

  OpenVMS Galaxy customers must have at least one
  OPENVMS-ALPHA PAK, plus one additional OPENVMS-
  ALPHA PAK for each additional processor (CPU) after the
  first CPU (which is included in the Base Operating System
  License).

  The OPENVMS-ALPHA and OPENVMS-ALPHA-USER
  PAKs can now be shared by multiple Galaxy instances.  To
  implement this in the License Management Facility (LMF),
  include all OpenVMS Galaxy instance names in the PAK
  INCLUDE list.

  For example, suppose that a customer has a system named
  ANDA1A in an OpenVMS Cluster.  The OPENVMS-ALPHA
  license PAK currently has an INCLUDE list on it that has

  SCS node name ANDA1A in it.  If that system is changed
  to an OpenVMS Galaxy running three instances named
  ANDA1A, ANDA2A, and ANDA3A, the OPENVMS-ALPHA
  license PAK must be modified so that all instances can share
  the NO_SHARE OPENVMS-ALPHA license.

  The command to modify the OPENVMS-ALPHA license
  PAK is:

  $  LICENSE  MODIFY  OPENVMS-ALPHA/AUTHORIZATION=blahblah  -
  _$/INCLUDE=3D(ANDA1A,ANDA2A,ANDA3A)

  Since this example assumes that ANDA1A was already in a
  cluster, the authorization number is required to identify the
  one PAK of many OPENVMS-ALPHA license PAKs in the
  license database file (LDB).

  TBS-Modify down info