Document revision date: 30 March 2001
[Compaq] [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]
[OpenVMS documentation]

OpenVMS Alpha Partitioning and Galaxy Guide

Index


Previous Contents


Master Alphabetic Index
A B C D E G H I L M O S U

A
AlphaServer 4100 system
    creating an OpenVMS Galaxy
AlphaServer 8200 system
    creating an OpenVMS Galaxy
AlphaServer 8400 system
    creating an OpenVMS Galaxy
AlphaServer ES40 system
    creating an OpenVMS Galaxy
AlphaServer GS140 system
    creating an OpenVMS Galaxy
AlphaServer GS160 system
    creating an OpenVMS Galaxy
AlphaServer GS60 system
    creating an OpenVMS Galaxy
AlphaServer GS60E system
    creating an OpenVMS Galaxy
B
Booting the OpenVMS Galaxy
    on an AlphaServer 8200
    on an AlphaServer 8400
C
CD drive recommendation
Cluster information
    becoming a Galaxy instance
    SCSI consideration
Common values for environment variables
Communicating with shared memory
    LAN (local area network)
    SMCI (Shared Memory Cluster Interconnect)
Computing models
    shared-everything computing model
    shared-nothing computing model
    shared-partial computing model
Configuration requirements
    for an AlphaServer 4100
    for an AlphaServer 8200
    for an AlphaServer 8400
    for an AlphaServer ES40
    for an AlphaServer GS160
CPU load balancer program
    example
CPU load balancer program overview
    build and copy instructions
    required privileges
    shutdown warning
    starting the load balancer from GCU
    startup options
CPU reassignment
    DCL
    faults
    GCU drag-and-drop
    intermodal
    sofware reassignment using Galaxy services
Creating a system disk
    on an AlphaServer 8200
    on an AlphaServer 8400
    on an AlphaServer GS160
Creating an OpenVMS Galaxy
    on an AlphaServer 4100
    on an AlphaServer 8200
    on an AlphaServer 8400
    on an AlphaServer ES40
    on an AlphaServer GS140
    on an AlphaServer GS160
    on an AlphaServer GS320
    on an AlphaServer GS60
    on an AlphaServer GS60E
    on an AlphaServer GS80
Customizing GCU menus
D
DCL command
    SET PROCESS
    SHOW PROCESS
DCL commands
    CONFIGURE
    INSTALL
    SHOW MEMORY
DCL commands useful for managing OpenVMS Galaxy
    CPU commands
        SET CPU
        SHOW CPU
        STOP/CPU/MIGRATE
DCL lexical
    F$GETJPI
    F$GETSYI
Direct-mapped DMA window changes
E
Environment variables
G
Galaxy benefits
    adaptability
    availability
    compatibility
    cost of ownership
    performance
    scalability
Galaxy configuration considerations
    EISA bus support
    memory granularity restrictions
    XMI bus support
Galaxy configuration models
    active model
    offline models
    online versus offline models
Galaxy Configuration Utility
    See GCU
Galaxy features
    clustering
    CPU reassignment
    dynamic reconfiguration
    SMP
Galaxy hardware and software components
    console
    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
Galaxywide global sections
GCU charts
    failover assignment chart
    logical structure chart
    memory assignment chart
    physical structure chart
    using
GCU (Galaxy Configuration Utility)
    definition of
GCU operations
    creating galaxy configuration models
    interaction
    observation
GCU system messages
H
Hardware requirements
    for an AlphaServer 4100
    for an AlphaServer 8200
    for an AlphaServer 8400
    for an AlphaServer ES40
    for an AlphaServer GS160
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-availability applications
How PCI direct-mapped DMA works
    as of OpenVMS Version 7.3
    prior to OpenVMS V7.3
I
Initializing system and starting console devices
    on an AlphaServer 4100
    on an AlphServer ES40
Initializing the secondary consoles
    on an AlphaServer GS160
Installing OpenVMS Alpha
    on an AlphaServer 4100
    on an AlphaServer 8200
    on an AlphaServer 8400
    on an AlphaServer ES40
    on an AlphaSever GS160
IOC$NODE_DATA changes
L
LANs (local area networks)
Local area networks
    See LANs
M
Managing CPU resources
Managing OpenVMS Galaxy with the GCU
    independent instances
    isolated instances
    required PROXY access
Monitoring an OpenVMS Galaxy with DECamds
O
OpenVMS Galaxy device drivers
S
SDA (System Dump Analyzer)
    about using
    dumping shared memory
Security considerations
Setting environment variables
    on an AlphaServer 4100
    on an AlphaServer 8200
    on an AlphaServer 8400
    on an AlphaServer ES40
    on an AlphaServer GS160
Shared Memory Cluster Interconnect
    See SMCI
Shared memory programming interfaces
SHOW RAD command
Single-instance Galaxy
    definition
    using on any Alpha system
SMCI (Shared Memory Cluster Interconnect)
Starting the secondary console devices
    on an AlphaServer 8200
    on an AlphaServer 8400
    on an AlphaServer GS160
System Dump Analyzer
    See SDA
System services
    $ACQUIRE_GALAXY_LOCK
    $CLEAR_SYSTEM_EVENT
    $CPU_TRANSITION[W]
    $CREATE_GALAXY_LOCK
    $CREATE_GALAXY_LOCK_TABLE
    $CREATE_GDZRO
    $CREPRC
    $CRMPSC_GDZRO_64
    $DELETE_GALAXY_LOCK
    $DELETE_GALAXY_LOCK_TABLE
    enhanced services
    $GETJPI
    $GETSYI
    $GET_GALAXY_LOCK_INFO
    $GET_GALAXY_LOCK_SIZE
    new section flag
    $RELEASE_GALAXY_LOCK
    $SET_PROCESS_PROPERTIESW
    $SET_SYSTEM_EVENT


Previous Next Contents Index

  [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]  
  privacy and legal statement  
6512PRO_INDEX.HTML