Document revision date: 24 June 2002
[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
AA-REZQD-TE
This manual supersedes the OpenVMS Alpha Version 7.3 manual.
OpenVMS Alpha Version 7.3–1
OpenVMS Alpha Versions 7.3–1
June 2002
Compaq Computer Corporation
Houston Texas 
© 2002 Compaq Information Technologies Group, L.P.
This guide describes how to use hard partitions, soft partitions (OpenVMS Galaxy), and resource affinity domains (RADs) with OpenVMS Alpha on AlphaServer systems that support these features. In addition, it describes how to create, manage, and use an OpenVMS Galaxy computing environment.
Compaq, the Compaq logo, Alpha, DECnet, DECwindows, OpenVMS, VAX, and VMS are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.
Microsoft, Windows, Windows NT, and Windows 2000 are trademarks of Microsoft Corporation in the U.S. and other countries.
Motif, OSF/1, and UNIX are trademarks of The Open Group in the U.S. and/or other countries.
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.
All other product names mentioned herein may be trademarks of their respective companies.
Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
ZK6512
The Compaq OpenVMS documentation set is available on CD-ROM.
Contents
OpenVMS Alpha Partitioning and Galaxy Guide
Preface
Intended Audience
Document Structure
Related Documents
Reader’s Comments
How to Order Additional Documentation
For Additional Information
Conventions
Chapter 1 Managing Workloads With Partitions and Resource Managemement
1.1 Using Hard and Soft Partitions on OpenVMS Systems
1.2 OpenVMS Partitioning Guidelines
1.3 Hard Partition Requirements and Configuration
 

 

 

 

1.4 OpenVMS Galaxy Support
1.5 OpenVMS Application Support for Resource Affinity Domains (RADs)
Chapter 2 OpenVMS Galaxy Concepts
2.1 OpenVMS Galaxy Concepts and Components
2.2 OpenVMS Galaxy Features
2.3 OpenVMS Galaxy Benefits
2.4 OpenVMS Galaxy Version 7.3 Features
2.5 OpenVMS Galaxy Advantages
2.6 When OpenVMS Galaxy Is Not the Best Choice
2.7 Possible OpenVMS Galaxy Configurations
 

 

 

2.8 What Is a Single-Instance Galaxy?
2.9 OpenVMS Galaxy Configuration Considerations
 

 

 

2.10 CD Drive Recommendation
2.11 Important Cluster Information
 

 

2.12 Security Considerations in an OpenVMS Galaxy Computing Environment
2.13 Configuring OpenVMS Galaxy Instances in Time Zones
2.14 Developing OpenVMS Galaxy Programs
 

 

 

 

 

Chapter 3 NUMA Implications on OpenVMS Applications
3.1 OpenVMS NUMA Awareness
 

 

 

3.2 Application Resource Considerations
 

 

 

 

3.3 Batch Job Support for NUMA Resource Affinity Domains
 

 

 

 

 

 

 

3.4 RAD Application Programming Interfaces
3.5 RAD System Services Summary Table
3.6 RAD DCL Command Summary Table
3.7 System Dump Analyzer (SDA) Support for RADs
 

 

 

 

Chapter 4 Creating an OpenVMS Galaxy on AlphaServer GS140/GS60/GS60E Systems
Chapter 5 Creating an OpenVMS Galaxy on an AlphaServer 8400 System
5.1 Step 1: Choose a Configuration and Determine Hardware Requirements
5.2 Step 2: Set Up Hardware
 

 

 

 

 

 

 

 

5.3 Step 3: Create a System Disk
5.4 Step 4: Install OpenVMS Alpha Version 7.3
 

5.5 Step 5: Upgrade the Firmware
5.6 Step 6: Set the Environment Variables
5.7 Step 7: Start the Secondary Console Devices
5.8 Step 8: Boot the OpenVMS Galaxy
Chapter 6 Creating an OpenVMS Galaxy on an AlphaServer 8200 System
6.1 Step 1: Choose a Configuration and Determine Hardware Requirements
6.2 Step 2: Set Up Galaxy Hardware
 

6.3 Step 3: Create a System Disk
6.4 Step 4: Install OpenVMS Alpha Version 7.3
6.5 Step 5: Upgrade the Firmware
6.6 Step 6: Set the Environment Variables
6.7 Step 7: Start the Secondary Console Device
6.8 Step 8: Boot the OpenVMS Galaxy
Chapter 7 Creating an OpenVMS Galaxy on an AlphaServer 4100 System
7.1 Before You Start
7.2 Step 1: Confirm the AlphaServer 4100 Configuration
7.3 Step 2: Install OpenVMS Alpha Version 7.3
7.4 Step 3: Upgrade the Firmware
7.5 Step 4: Set the Environment Variables
7.6 Step 5: Initialize the System and Start the Console Devices
Chapter 8 Creating an OpenVMS Galaxy on an AlphaServer ES40 System
8.1 Before You Start
8.2 Step 1: Confirm the AlphaServer ES40 Configuration
8.3 Step 2: Install OpenVMS Alpha Version 7.31
8.4 Step 3: Upgrade the Firmware
8.5 Step 4: Set the Environment Variables
8.6 Step 5: Initialize the System and Start the Console Devices
Chapter 9 Creating an OpenVMS Galaxy on AlphaServer GS80/160/320 Systems
9.1 Step 1: Choose a Configuration and Determine Hardware Requirements
9.2 Step 2: Set Up the Hardware
9.3 Step 3: Create a System Disk
9.4 Step 4: Install OpenVMS Alpha Version 7.3
 

9.5 Step 5: Set the Environment Variables
 

 

 

9.6 Step 6: Start the Secondary Console Devices
9.7 Step 7: Initialize the Secondary Consoles
9.8 Step 8: Boot the OpenVMS Galaxy
Chapter 10 Using a Single-Instance Galaxy on Any Alpha System
Chapter 11 OpenVMS Galaxy Tips and Techniques
11.1 System Auto-Action
11.2 Changing Console Environment variables
11.3 Console Hints
11.4 Turning Off Galaxy Mode
Chapter 12 OpenVMS Galaxy Configuration Utility
12.1 GCU Tour
 

 

 

 

 

12.2 Managing an OpenVMS Galaxy with the GCU
 

 

 

12.3 Galaxy Configuration Models
 

 

 

12.4 Using the GCU Charts
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

12.5 Viewing Component Parameters
12.6 Executing Component Commands
12.7 Customizing GCU Menus
12.8 Monitoring an OpenVMS Galaxy with DECamds
12.9 Running the CPU Load Balancer Program
12.10 Creating an Instance
12.11 Dissolving an Instance
12.12 Shutdown and Reboot Cycles
12.13 Online Versus Offline Models
12.14 GCU System Messages
Chapter 13 Installing the Graphical Configuration Manager (GCM)
13.1 Overview
13.2 Installation Prerequisites
 

 

13.3 Installation Procedure
 

 

 

 

 

 

13.4 Starting the GCM Server
 

 

13.5 Postinstallation Administrative Tasks
 

 

 

 

 

13.6 Configuring the Association
 

 

13.7 Customizing GCM
 

13.8 GCM Server Log Files
13.9 Troubleshooting the GCM Server
 

 

 

13.10 Performance
13.11 Maintaining the GCM Server
13.12 Sample Verbose GCM Server Setup
Chapter 14 CPU Reassignment
14.1 DCL Reassignment
14.2 GCU Drag-and-Drop Reassignment
14.3 Intermodal Reassignment
14.4 Software Reassignment Using Galaxy Services
14.5 Reassignment Faults
Chapter 15 DCL Commands and Lexical Functions
15.1 DCL Commands
15.2 DCL Lexical Functions
15.3 DCL Command Examples
 

 

 

 

 

 

 

 

 

Chapter 16 Communicating With Shared Memory
16.1 Shared Memory Cluster Interconnect (SMCI)
 

 

 

 

 

16.2 LAN Shared Memory Device Driver
Chapter 17 Shared Memory Programming Interfaces
17.1 Using Shared Memory
17.2 System Services
 

 

17.3 Galaxywide Global Sections
Chapter 18 OpenVMS Galaxy Device Drivers
18.1 Direct-Mapped DMA Window Changes
18.2 How PCI Direct-Mapped DMA Works Prior to OpenVMS Version 7.2
18.3 How PCI Direct-Mapped DMA Works in Current Versions of OpenVMS
18.4 IOC$NODE_DATA Changes to Support Nonzero Direct-Mapped DMA Windows
Appendix A OpenVMS Galaxy CPU Load Balancer Program
 

 

 

 

 

 

 

Appendix B Common Values for Environment Variables






























Preface

The OpenV MS Alpha Partitioning and Galaxy Guide describes how customers can take advantage of the partitioning and OpenVMS Galaxy capabilities available in OpenVMS Alpha Version 7.3–1.
The information in this document applies to OpenVMS Alpha systems only; it does not apply ro OpenVMS VAX systems.

Intended Audience

This guide is intended for system managers, application programmers, technical consultants, data center managers, and anyone else who wants to learn about OpenVMS Galaxy and the partitioning capabilities of OpenVMS Alpha.

Document Structure

This guide introduces OpenVMS partitioning concepts and features on the hardware platforms that support them. It also explains how to use the OpenVMS Galaxy capabilities available in OpenVMS Alpha Version 7.3–1.
This guide contains the following chapters and appendixes:
Chapter 1 describes how to use hard and soft partitions and the OpenVMS support for resource affinity domains (RADs).
Chapter 2 describes the OpenVMS Galaxy concepts and highlights the features available in OpenVMS Version 7.3–1.
Chapter 3 discusses the nonuniform memory access (NUMA) implications on OpenVMS applications.
Chapter 4 describes how to create an OpenVMS Galaxy on AlphaServer GS140/GS60/GS60E systems.
Chapter 5 describes how to create an OpenVMS Galaxy on an AlphaServer 8400 system.
Chapter 6 describes how to create an OpenVMS Galaxy on an AlphaServer 8200 system.
Chapter 7 describes how to create an OpenVMS Galaxy on an AlphaServer 4100 system.
Chapter 8 describes how to create an OpenVMS Galaxy on an AlphaServer ES40 system.
Chapter 9 describes how to create an OpenVMS Galaxy on AlphaServer GS80/160/320 systems.
Chapter 10 discusses how to use a single-instance Galaxy on any Alpha system.
Chapter 11 discusses OpenVMS Galaxy tips and techniques.
Chapter 12 describes the OpenVMS Galaxy configuration utility.
Chapter 13 describes the OpenVMS Graphical Configuration Manager.
Chapter 14 discusses CPU reassignment.
Chapter 15 describes the DCL commands that are useful for managing an OpenVMS Galaxy.
Chapter 16 describes how to communicate with shared memory.
Chapter 17 discusses the shared memory programming interfaces.
Chapter 18 describes the OpenVMS Galaxy device drivers.
Appendix A contains an OpenVMS Galaxy load balancer program example.
Appendix B lists the common values for environment variables.
The OpenVMS Alpha Partitioning and Galaxy Guide assumes that readers are familiar with OpenVMS concepts and operation, and it does not cover basic OpenVMS information.

Related Documents

The following manuals contains OpenVMS information that might be useful for partitioned computing environments:
• OpenVMS Alpha Upgrade and Installation
• OpenVMS Cluster Systems
• OpenVMS Alpha System Analysis Tools Manual
• OpenVMS License Management Utility Manual
For additional information about Compaq OpenVMS products and services, see the Compaq web site at the following URL:
http://www.openvms.compaq.com

Reader’s Comments

Compaq welcomes your comments on this manual. Please send comments to either of the following addresses:
Internet
openvmsdoc@compaq.com
Mail
Compaq Computer Corporation
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How to Order Additional Documentation

Visit the following World Wide Web address for information about how to order additional documentation:
http://www.openvms.compaq.com/

For Additional Information

For additional information about Compaq OpenVMS products and services, access the Compaq website at the following location:
http://www.openvms.compaq.com/

Conventions

In this manual:
• Instance refers to a copy of the OenVMS Alpha operating system.
• OpenVMS Galaxy and Galaxy refer to the Compaq OpenVMS Galaxy Software Architecture on OpenVMS.
• DECwindows and DECwindows Motif refer to DECwindows Motif for OpenVMS software.
The following conventions are used in this manual:
Ctrl/ x
Indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1x
A sequence such as PF1x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.
[Return]
In an example, a key name enclosed in a box indicates that you press that key.
A horizontal ellipsis in examples indicates one of the following possibilities:
• Additional optional arguments in a statement have been omitted.
• The preceding item or items can be repeated one or more times.
• Additional parameters, values, or other information can be entered.
A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( )
In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.
[ ]
In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
|
In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
{ }
In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.
Type
This typeface represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.
italics
Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where (dd) represents the predefined par code for the device type).
UPPERCASE TEXT
Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace text
Monospace type indicates code examples and interactive screen displays.
In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.
A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers
All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes—binary, octal, or hexadecimal—are explicitly indicated.

1    Managing Workloads With Partitions and Resource Managemement

OpenVMS customers use systems that support hard and soft partitions in many different ways. To most effectively use these systems, customers can decide which configuration options best meet their computing and application needs.
This chapter describes how to use hard and soft partitions and the new OpenVMS support for resource affinity domains (RADs) to ensure that applications run as efficiently as possible on the new AlphaServer systems.

1.1  Using Hard and Soft Partitions on OpenVMS Systems

Hard partitioning is a physical separation of computing resources by hardware-enforced access barriers. It is impossible to read or write across a hard partition boundary. There is no resource sharing between hard partitions.
Soft partitioning is a separation of computing resources by software-controlled access barriers. Read and write access across a soft partition boundary is controlled by the operating system. OpenVMS Galaxy is an implementation of soft partitioning.
The way that customers choose to partition their new AlphaServer GS series systems depends on their computing environments and application requirements. When deciding how to configure an OpenVMS system that supports partitioning, customers need to consider the following questions:
• How many hard partitions do I need?
• How many soft partitions do I need?
• How small can I make the partitions?