OpenVMS Alpha Galaxy Guide

Document revision date: 19 July 1999

Order Number: AA--REZQB--TE

July 8, 1999

This guide introduces the Compaq Galaxy Software Architecture on OpenVMS Alpha and describes how to create, manage, and use an OpenVMS Galaxy computing environment.

The latest version of this guide is always available at:
http://www.openvms.digital.com:8000/

Please send ALL corrections, comments, issues, questions, and concerns about this guide to margie.sherlock@compaq.com

Revision/Update Information: This is a new manual.

Software Version: OpenVMS Alpha Version 7.2--1
OpenVMS Galaxy Version 1.0--1

Compaq Computer Corporation
Houston, Texas

July 8, 1999

Digital Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital Equipment Corporation or an authorized sublicensor.

Compaq, the Compaq logo, and the DIGITAL logo are registered in the U.S. Patent and Trademark Office.

Alpha, AlphaServer, AlphaStation, DEC, DECnet, DECserver, DECterm, DIGITAL, DIGITAL UNIX, MSCP, OpenVMS, Tru64, VAX, VAXcluster, VMS, VMScluster are trademarks of Compaq Computer Corporation.

The following are third-party trademarks:

POSTSCRIPT is a registered trademark of Adobe Systems Incorporated.

Motif, OSF, OSF/1, OSF/Motif, and The Open Group are registered trademarks of The Open Group.

MEMORY CHANNEL is a trademark of Encore Computer Corporation.

NonStop is a trademark of Tandem Computer, Inc.

Windows NT is a registered trademark of Microsoft Corporation.

All other trademarks and registered trademarks are the property of their respective holders.

ZK6512

The OpenVMS documentation set is available on CD-ROM.

This document was prepared using VAX DOCUMENT, Version V3.2n.

Contents Index

Preface

The OpenVMS Alpha Galaxy Guide describes how customers can take advantage of the OpenVMS Galaxy capabilities available in OpenVMS Alpha Version 7.2--1.

The information in this document applies to OpenVMS Alpha systems only; it does not apply to 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 the Galaxy Software Architecture on OpenVMS Alpha.

Document Structure

The OpenVMS Alpha Galaxy Guide introduces OpenVMS Galaxy concepts and features, and it explains how to use the OpenVMS Galaxy capabilities available in OpenVMS Alpha Version 7.2--1.

This guide is designed to include all of the Galaxy-specific information you need to create, manage, use, and develop programs for an OpenVMS Galaxy computing environment. Specifically, this guide covers the following OpenVMS Galaxy topics:

Basic concepts
Hardware and software requirements
Configuration alternatives
Licensing information
Installation procedures
System management options
Descriptions of the application programming interfaces (APIs) available to develop programs that take advantage of OpenVMS Galaxy features

The OpenVMS Alpha Galaxy Guide assumes that readers are familiar with OpenVMS concepts and operation, and it does not cover basic OpenVMS information.

How to Use this Book

The OpenVMS Alpha Galaxy Guide contains the following four parts:

Part 1---Introduction to the Galaxy Software Architecture
Part 2---Creating an OpenVMS Galaxy Environment
Part 3---Managing an OpenVMS Galaxy
Part 4---Developing OpenVMS Galaxy Programs

Compaq recommends that you read Part I to learn about OpenVMS Galaxy concepts, features, benefits, configuration alternatives, and licensing information.

When you are ready to set up an OpenVMS Galaxy computing environment, read the chapter in Part II that is appropriate to your system. Be sure to refer to Chapter 10 to learn additional information that might be useful for your environment.

When your OpenVMS Galaxy system is running, see Part III for information about how to manage and use it.

If you want to develop applications that take full advantage of OpenVMS technology, see Part IV. Note that Appendix A is an example program that demonstrates many of the programming interfaces referenced in Part IV.

We Want to Hear From You!

OpenVMS Galaxy is a new product, and we welcome your feedback. Let us know about any problems, issues, questions you encounter. We are especially interested in hearing about:

OpenVMS problems
Console issues
Documentation errors and suggestions

Print or edit the online form SYS$HELP:OPENVMSDOC_COMMENTS.TXT and send us your comments by:

e-mailInternet margie.sherlock@compaq.com

Fax 603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08

Mail Compaq Computer Corporation
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How To Order Additional Documentation

Use the following World Wide Web address for information about how to order additional documentation:

http://www.compaq.com/openvms

To reach the OpenVMS documentation website, click the Documentation link.

If you need help deciding which documentation best meets your needs, call 1--800--ATCOMPA.

Conventions

In this manual:

Instance refers to a copy of the OpenVMS Alpha operating system.
OpenVMS Galaxy and Galaxy refer to the Compaq 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 A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.

PF1 x A sequence such as PF1 x 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 examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)
In the HTML version of this document, this convention appears as brackets, rather than a box.

... 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 the options in parentheses if you choose more than one.

[ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.)

[|] In command format descriptions, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options.

{ } In command format descriptions, braces indicate required elements; you must choose one of the options listed.

bold text This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason.

italic text 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 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 text 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.

Chapter 1
OpenVMS Galaxy Version 7.2--1 Release Notes

This chapter contains OpenVMS Galaxy release notes for OpenVMS Version 7.2--1 and notes from OpenVMS Version 7.2 that still apply to this release.

1.1 OpenVMS Galaxy Support on AlphaServer GS60/GS60E/GS140 Systems

V7.2--1 Release Note

OpenVMS Alpha Version 7.2--1 provides support for OpenVMS Galaxy configurations on AlphaServer GS60, GS60E, and GS140 systems.

For information about creating OpenVMS Galaxy computing environments on GS60, GS60E, and GS140 systems, see Chapter 5. Note that console firmware requirements for these systems is also included in this chapter.

1.2 AlphaServer GS60/GS60E/GS140 Multiple I/O Port Module Configuration Restriction

V7.2--1 Release Note

AlphaServer GS60/GS60E/GS140 configurations with more than a single I/O Port Module, KFTHA-AA or KFTIA-AA, might experience system crashes.

When upgrading OpenVMS Galaxy and non-Galaxy AlphaServer 8200/8400 configurations with multiple I/O Port Modules to GS60/GS60E/GS140 systems, customers must install one minimum revision B02 KN7CG-AB EV6 CPU (E2063-DA/DB rev D01) module as described in Compaq Action Blitz # TD 2632.

For complete details about this restriction and its solution, refer to Compaq Action Blitz # TD 2632.

1.3 OpenVMS Galaxy Console Firmware for AlphaServer 8400, 8200, and 4100 Systems

V7.2--1 Release Note

OpenVMS Galaxy console firmware for AlphaServer 8400, 8200, and 4100 systems is located on the Alpha Systems Firmware Update Version 5.4 CD-ROM that is included with the OpenVMS Alpha Version 7.2--1 CD-ROM package.

For OpenVMS Alpha Version 7.2, OpenVMS Galaxy firmware files were included on the OpenVMS Alpha Version 7.2 kit.

1.4 OpenVMS Galaxy Operating Hints

V7.2--1 Release Note

Chapter 10 contains operating hints that OpenVMS Engineering has found useful in creating and supporting OpenVMS Galaxy environments.

1.5 Changes to the OpenVMS Alpha Galaxy Guide

V7.2--1 Release Note

This section describes OpenVMS Galaxy documentation changes and enhancements since OpenVMS Version 7.2.

1.5.1 KFE72-DA Installation Procedures Added

The procedures that describe how to install KFE72-DA modules in OpenVMS Galaxy systems have been expanded. For the correct procedures, see Chapter 6.

1.5.2 Additional SDA Information Published

The System Dump Analyzer (SDA) Galaxy-specific documentation in this book has been enhanced to include:

Information about how to dump shared memory when a system crash occurs in a Galaxy instance.
Complete descriptions of Galaxy-specific SDA commands.

1.5.3 Running the CPU Load Balancer Program

Instructions for running the CPU load balancer program from the Galaxy Configuration Utility have been made more visible in Appendix A, and a new section about running the load balancer has been added to Chapter 10.

1.5.4 Enhancements to Galaxy-specific System Services Documentation

As of OpenVMS Version 7.2--1, documentation for the following Galaxy-specific systems services is included in DCL online help:

$ACQUIRE_GALAXY_LOCK
$CLEAR_SYSTEM_EVENT
$CREATE_GALAXY_LOCK
$CREATE_GALAXY_LOCK_TABLE
DELETE_GALAXY_LOCK
$DELETE_GALAXY_LOCK_TABLE
$GET_GALAXY_LOCK_INFO
$GET_GALAXY_LOCK_SIZE
$RELEASE_GALAXY_LOCK
$SET_SYSTEM_EVENT

1.6 MOP Booting Restrictions

V7.2 Release Note

In an OpenVMS Galaxy computing environment, MOP Booting is only supported on Instance 0. This restriction will be removed in a future release.

1.7 Restriction on KFMSB and CIXCD Adapters in Galaxy Configurations

Permanent Restriction

Due to firmware addressing limitations on driver-adapter control data structures, KFMSB and CIXCD adapters can only be used on hardware partitions based at physical address (PA) = 0. In OpenVMS Galaxy configurations, this restricts their use to instance 0.

1.8 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster Members

V7.2 Release Note

OpenVMS Version 7.2 introduces new security classes that are used in an OpenVMS Galaxy computing environment. The new security classes are not valid on non-Galaxy systems. If your OpenVMS Galaxy is configured in an existing OpenVMS Cluster, you must ensure that all the nodes in the cluster recognize the new security classes as described in this release note.

This situation applies if all of the following conditions are met:

If your OpenVMS Galaxy is configured in a cluster with non-Galaxy systems
If the non-Galaxy cluster nodes share the VMS$OBJECTS.DAT security database file
If you use Galaxywide global sections in your OpenVMS Galaxy
If versions of OpenVMS prior to OpenVMS Version 7.1-2 are in use

OpenVMS VAX and Alpha systems running OpenVMS Version 6.2 or Version 7.1 will crash if they encounter an unknown security class in the VMS$OBJECTS.DAT file.

To allow VAX and Alpha systems running older versions of OpenVMS to cooperate with Version 7.2 Galaxy instances in the same OpenVMS Cluster environment, a SECURITY.EXE image is provided for each of these versions. The appropriate remedial kit from the following list must be installed on all system disks used by these systems. (Later versions of these remedial kits may be used if available.)

Alpha V7.1 and V7.1-1xx ALPSYSB02_071

Alpha V6.2 and V6.2-1xx ALPSYSB02_062

VAX V7.1 VAXSYSB01_071

VAX V6.2 VAXSYSB01_062

Before you create any galaxywide global sections, you must reboot all cluster members sharing one of the updated system disks.

See Section 3.7.1 the installation questions that relate to this topic.

Part I
Introduction to the Galaxy Software Architecture on OpenVMS

Contents

Index

privacy and legal statement

6512PRO.HTML

e-mailInternet	margie.sherlock@compaq.com
Fax	603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08
Mail	Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698

Ctrl/ x	A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1 x	A sequence such as PF1 x 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 examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box.
...	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 the options in parentheses if you choose more than one.
[ ]	In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.)
[\|]	In command format descriptions, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options.
{ }	In command format descriptions, braces indicate required elements; you must choose one of the options listed.
bold text	This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason.
italic text	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 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 text 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.

Alpha V7.1 and V7.1-1xx	ALPSYSB02_071
Alpha V6.2 and V6.2-1xx	ALPSYSB02_062
VAX V7.1	VAXSYSB01_071
VAX V6.2	VAXSYSB01_062