A

AlphaServer ES40system creating an OpenVMS Galaxy

AlphaServer ES47 system creating an OpenVMS Galaxy

AlphaServer ES80 system creating an OpenVMS Galaxy

AlphaServer GS1280 system creating an OpenVMS Galaxy

AlphaServer GS160 system creating an OpenVMS Galaxy

AlphaServer 4100 system creating an OpenVMS Galaxy

AlphaServer 8200 system creating an OpenVMS Galaxy

AlphaServer 8400 system creating an OpenVMS Galaxy

 B

Booting the OpenVMS Galaxy on an AlphaServer 8200

on an AlphaServer 8400

 C

CD drive recommendation

Child

Cluster information

becoming a Galaxy instance

SCSI consideration

Common values for memory

Communicating with sharedmemory LAN (local area network)

SMCI (Shared Memory Cluster Interconnect)

Computing models shared-everything computing model

shared-nothing computing model

shared-partial computing model

Configuration tree

Configuration requirements for an AlphaServer ES40

for an AlphaServer GS1280

for an AlphaServer GS160

for an AlphaServer 4100

for an AlphaServer 8200

for an AlphaServer 8400

CPU load balancer program example

CPU load balancer programoverview build and copy instructions

required privileges

startup options

CPU reassignment DCL

faults

GCU drag-and-drop

intermodal

sofware reassignment using Galaxy services

Creating a system disk on an AlphaServer GS160

on an AlphaServer 8200

on an AlphaServer 8400

Creating an OpenVMS Galaxy on an AlphaServer ES40

on an AlphaServer GS1280

on an AlphaServer GS160

on an AlphaServer GS320

on an AlphaServer GS80

on an AlphaServer 4100

on an AlphaServer 8200

on an AlphaServer 8400

Customizing GCU menus

 D

DCL command CONFIGURE

CONFIGURE GALAXY

INITIALIZE

INSTALL

INSTALL ADD

INSTALL/LIST

SET CPU/MIGRATE

SET CPU/OVERRIDE_CHECKS

SET CPU/POWER

SET CPU/REFRESH

SET CPU/START

SET ENTRY

SET PROCESS

SET QUEUE

SHOW CPU/ACTIVE_SET

SHOW CPU/CONFIGURE_SET

SHOW CPU/POTENTIAL_SET

SHOW CPU/STANDBY_SET

SHOW CPU/SYSTEM

SHOW MEMORY

SHOW MEMORY

SHOW PROCESS

START QUEUE

START/CPU/POWER

STOP/CPU/MIGRATE

DCLcommand STOP/CPU/POWER=OFF

DCL command SUBMIT

DCL commands useful formanaging OpenVMS Galaxy CPU commands

DCL commands useful for managingOpenVMS Galaxy CPU commands SET CPU

DCL commands useful formanaging OpenVMS Galaxy CPU commands SHOW CPU

STOP/CPU/MIGRATE

DCL lexical F$GETJPI

F$GETSYI

Direct-mapped DMA windowchanges

 E

ES45

 F

Firmware location GS1280

 G

Galaxy

Galaxy benefits

adaptability

availability

compatibility

cost of ownership

performance

scalability

Galaxy configuration considerations

EISA bus support

memory granularity restrictions

XMI bus support

Galaxy Configuration Utility See also See GCU

Galaxy configuration models active model

offline models

online versus offline models

Galaxy features

clustering

CPU reassignment

dynamic reconfiguration

SMP

Galaxyhardware and software components console

Galaxy hardware and softwarecomponents CPUs

I/O

independent instances

shared memory

Galaxy Software Architecture

Galaxy tips and techniques changing console environment variables

console hints

system auto-action

turning off Galaxy mode

Galaxy Version 7.3 features

Galaxy-wide global sections

GCM

GCU charts failover assignment chart

logical structure chart

memory assignment chart

physical structure chart

using

GCU operations creating galaxy configuration models

interaction

observation

GCU system messages

GCU (Galaxy ConfigurationUtility) definition of

 H

Hardpartition

Hardware requirements for an AlphaServer ES40

for an AlphaServer GS1280

for an AlphaServer GS160

for an AlphaServer 4100

for an AlphaServer 8200

for an AlphaServer 8400

Hardware setup installing EISA devices on an AlphaServer 8200

installing EISA devices on an AlphaServer 8400

installing the KFE72-DA module on an AlphaServer 8400

overview of KFE72-DA console subsystem on an AlphaServer 8400

High-availabilityapplications

How PCI direct-mapped DMAworks as of OpenVMS Version 7.3

prior to OpenVMS V7.3

 I

Initializing system and starting consoledevices on an AlphaServer 4100

on an AlphServer ES40

Initializing the secondaryconsoles on an AlphaServer GS160

Installing OpenVMS Alpha on an AlphaServer ES40

on an AlphaServer 4100

on an AlphaServer 8200

on an AlphaServer 8400

on an AlphaSever GS160

IOC$NODE_DATA changes

 L

LANs (local area networks)

License

Local area networks See also See LANs

 M

Managing CPU resources

Managing OpenVMS Galaxywith the GCU independent instances

isolated instances

required PROXY access

Memory common values for

Migration

Monitoring an OpenVMS Galaxywith DECamds

 N

Node definition

of tree

DCL command SET CPU/AUTO_START

 O

OpenVMS Galaxy device drivers

Ownership

 P

Parent

Partition hard

scope

setup

soft

 R

Root tree

 S

Scope of partition

SDA (System Dump Analyzer) about using

dumping shared memory

Security considerations

Setting environment variables on an AlphaServer ES40

on an AlphaServer GS160

on an AlphaServer 4100

on an AlphaServer 8200

on an AlphaServer 8400

Setup of partition

SHOW RAD command

Shared Memory Cluster Interconnect See also See SMCI

Shared memory programminginterfaces

Sibling

Single-instance Galaxy definition

using on any Alpha system

SMCI (Shared Memory Cluster Interconnect)

Soft partition

SRM

Starting the secondaryconsole devices on an AlphaServer GS160

on an AlphaServer 8200

on an AlphaServer 8400

System Dump Analyzer See also See SDA

System services enhanced services

new section flag

$ACQUIRE_GALAXY_LOCK

$CLEAR_SYSTEM_EVENT

$CREATE_GALAXY_LOCK

$CREATE_GALAXY_LOCK_TABLE

$CREATE_GDZRO

$CREPRC

$CRMPSC_GDZRO_64

$DELETE_GALAXY_LOCK

$DELETE_GALAXY_LOCK_TABLE

$GETJPI

$GETSYI

$GET_GALAXY_LOCK_INFO

$GET_GALAXY_LOCK_SIZE

$RELEASE_GALAXY_LOCK

$SET_PROCESS_PROPERTIESW

$SET_SYSTEM_EVENT

 T

Tree configuration

root

 U

Upgrading the firmware on an AlphaServer ES40

on an AlphaServer 4100

on an AlphaServer 8200

on an AlphaServer 8400

Using shared memory

 W

System services $CPU_TRANSITION