1.3  Compatibility of Galaxy Computing Environment and
       Non-Galaxy Cluster Members

  V7.2-EFT3 Release Note

  OpenVMS Version 7.2 introduces new security classes that
  are used in an OpenVMS Galaxy computing environment.

  The new security classes are not valid on non-Galaxy sys-
  tems.  If your OpenVMS Galaxy is configured in an existing
  OpenVMS Cluster, you must ensure that all the nodes in the
  cluster recognize the new security classes as described in this
  release note.

  This situation applies if all of the following conditions are met:

  *   If your OpenVMS Galaxy is configured in a cluster with
      non-Galaxy systems

  *   If the non-Galaxy cluster nodes share the VMS$OBJECTS.DAT
      security database file

  *   If you use galaxywide global sections in your OpenVMS
      Galaxy

  OpenVMS VAX and Alpha systems running OpenVMS
  Version 6.2 or Version 7.1 will crash if they encounter an
  unknown security class in the VMS$OBJECTS.DAT file.

  To allow VAX and Alpha systems running older versions of
  OpenVMS to cooperate with Version 7.2 Galaxy instances in
  the same OpenVMS Cluster environment, a SECURITY.EXE
  image is provided for each of these versions.  The files are
  located on the OpenVMS Alpha Version 7.2-EFT3 CD in
  directory [VMS$COMMON.SYS$LDR]:

  OpenVMS Alpha V6.2   SECURITY.EXE_ALPHA_V62
                        SECURITY.STB_ALPHA_V62

  OpenVMS Alpha V7.1   SECURITY.EXE_ALPHA_V71
                        SECURITY.STB_ALPHA_V71

  OpenVMS VAX V6.2    SECURITY.EXE_VAX_V62
  OpenVMS VAX V7.1    SECURITY.EXE_VAX_V71

  To use the new files, you must do the following:

  For each OpenVMS Alpha Version 6.2 system disk:
  $  RENAME/LOG  target_disk:[SYS*.SYS$LDR]SECURITY.EXE  SECURITY.EXE_OLD

  $  RENAME/LOG  target_disk:[SYS*.SYS$LDR]SECURITY.STB  SECURITY.STB_OLD
  $  COPY  distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_ALPHA_V62  -

   target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;
  $  COPY  distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.STB_ALPHA_V62  -
   target_disk:[VMS$COMMON.SYS$LDR]SECURITY.STB;

  For each OpenVMS Alpha Version 7.1 system disk:

  $  RENAME/LOG  target_disk:[SYS*.SYS$LDR]SECURITY.EXE  SECURITY.EXE_OLD
  $  RENAME/LOG  target_disk:[SYS*.SYS$LDR]SECURITY.STB  SECURITY.STB_OLD

  $  COPY  distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_ALPHA_V71  -
   target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;

  $  COPY  distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.STB_ALPHA_V71  -
   target_disk:[VMS$COMMON.SYS$LDR]SECURITY.STB;

  For each OpenVMS VAX Version 6.2 system disk:
  $  RENAME/LOG  target_disk:[SYS*.SYS$LDR]SECURITY.EXE  SECURITY.EXE_OLD

  $  COPY  distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_VAX_V62  -
   target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;

  For each OpenVMS VAX Version 7.1 system disk

  $  RENAME/LOG  target_disk:[SYS*.SYS$LDR]SECURITY.EXE  SECURITY.EXE_OLD
  $  COPY  distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_VAX_V71  -
   target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;

  Before you create any galaxywide global sections, you must
  reboot all cluster members sharing one of the updated system
  disks.

  Note that the OpenVMS VAX Version 7.2-EFT3 operating
  system already contains this fix.