3.6  Important Info That Needs to be Located in the
       Appropriate Chapters

  3.6.1  New SYSGEN parameter

  The GLX_INST_TMO SYSGEN parameter:

  Each SHARING member ticks a heartbeat cell in shared
  memory which the other instances watch.  If an instance's
  heartbeat stops ticking for GLX_INST_TMO milliseconds,
  that instance will be assumed to be dead and removed as a
  sharing member.

  If for example, you CTRL-P a sharing member for longer
  that GLX_INST_TMO milliseconds, upon issuing a Continue
  command from the console, the instance will immediatly
  bugcheck with a GLXEXIT bugcheck.  This is very similar
  to the behavior of an OpenVMScluster that would result in a
  CLUEXIT bugcheck if a cluster member was in a CTRL-P
  state for longer than RECNXINTERVAL seconds.

  The sharing members all use the same value of GLX_INST_
  TMO. The value used is the smallest value of any node that
  has EVER booted into the Galaxy

  3.6.2  System Auto-Action
  Upon system power-up, if the AUTO_ACTION console envi-
  ronment variable is set to BOOT or RESTART for instance 0,
  then the GALAXY command will automatically be issued and
  instance 0 will attempt to boot.

  The setting of AUTO_ACTION in the console environment
  variables for the other instances will dictate their behavior
  upon the issuing of the GALAXY comamnd (whether it is
  issued automatically or by the user from the console).

  To setup your system for this feature, you must set the con-
  sole environment variable "AUTO_ACTION" to "RESTART"
  or "BOOT" on each instance, and be sure to specify appro-
  priate values for the BOOT_OSFLAGS and BOOTDEF_DEV
  environment variables for each instance.

  3.6.3  Changing console environment variables

  Once you have established the initial set of LP_  * environ-
  ment variables for OpenVMS Galaxy operation and booted
  your system, changing environment variable values requires
  that you first re-initialize the system, change the values,
  and re-initialize again.  Wrapping the changes between
  INITs is required to properly propagate the new values to all
  partitions.
                                Note

      For the 4100, no INIT is needed to start but you must
      change these variables on both instances.

  3.6.4  CONFIGURE GALAXY

  The GCU can now be invoked via DCL commands:
  CONFIGURE GALAXY.