
System Management Release Notes
4.37 OpenVMS Galaxy (Alpha Only)
4.37.1 Galaxy Definitions
V8.2
Because the HP OpenVMS Alpha Partitioning and Galaxy Guide is not being
updated for this release, this note provides improved definitions of the word
Galaxy, which depends on context.
Table 4–3 Galaxy Definitions
Galaxy as a: Functions this way:
License Is required to create and run multiple instances of OpenVMS in a
single computer. Without this license, only one instance of OpenVMS
can be run in a single computer.
System
parameter
Sets memory sharing. GALAXY set to 1 specifies that OpenVMS
instances with the parameter set in a hard partition will share
memory between soft partitions within that hard partition. (You
can run more than two soft partitions in a hard partition, and
you may not want to share memory among all of them.) Note that
this parameter only specifies whether a node uses shared memory.
There is no need to use this parameter to run multiple, cooperative
instances of OpenVMS; this is achieved by console setup of the
desired configuration tree. GALAXY set to 0 means that memory is
not shared (the default).
Soft partition Provides the capability of several OpenVMS instances to execute
cooperatively in a single computer so as to be able to migrate CPUs,
use APIs, share memory, and so on. Platform partitioning makes
possible the separation of resources into multiple soft partitions, each
of which can run an OS instance. A soft partition is that subset of
resources that the OS instance running in it can see and use.
4.38 Multiple nPartitions on Cell-based Systems
V8.2-1
If you have multiple nPartitions on your HP Integrity rx7620, HP Integrity
rx8620, or HP Integrity Superdome servers, and you are running a multi-
operating system environment with OpenVMS on one of the nPartitions, one
of the other operating systems might register an error or event on the System
Event Log (SEL) while OpenVMS is booting. OpenVMS holds the SEL until it
has produced a table of Field Replaceable Units (FRU), which might cause other
operating systems to register an error or an event.
4.38.1 OpenVMS Graphical Configuration Manager
V8.2
The OpenVMS Graphical Configuration Manager (GCM) is now supported for
AlphaServer ES47/ES80/GS1280 Galaxy configurations. Previously, only the
Graphical Configuration Utility (GCU) was supported.
4.38.2 Galaxy on ES40: Uncompressed Dump Limitation
Permanent Restriction
On AlphaServer ES40 Galaxy systems, you cannot write a raw (uncompressed)
dump from instance 1 if instance 1’s memory starts at or above 4 GB (physical).
Instead, you must write a compressed dump.
4–30 System Management Release Notes