Document revision date: 19 July 1999

The Alpha SDA command SHOW SYMBOL /ALL has two new qualifiers. The /ALPHA qualifier causes SDA to display the symbols sorted only in alphabetical order. The /VALUE qualifier causes SDA to display the symbols sorted only in value order. The default is to display the symbols twice, sorted alphabetically and then by value.

4.20.1.26 SHOW SYMBOL Command: Enhanced to Allow Wildcards

The Alpha SDA command SHOW SYMBOL without the /ALL qualifier now causes SDA to allow standard wildcards in the symbol-name parameter. By default, matching symbols are displayed only in alphabetical order. If SHOW SYMBOL /VALUE is specified, then matching symbols are output sorted by value. If both /ALPHA and /VALUE are specified, matching symbols are displayed twice, sorted alphabetically and then by value.

The benefit of this new functionality is increasing the flexibility of the SHOW SYMBOL command for locating symbols whose name is only partially known.

4.20.1.27 VALIDATE PFN_LIST Command: /UNTESTED and /PRIVATE Qualifiers

The Alpha SDA command VALIDATE PFN_LIST has two new qualifiers: /PRIVATE and /UNTESTED. The /PRIVATE qualifier causes SDA to validate all private PFN lists. The /UNTESTED qualifier causes SDA to validate the state of the untested PFN list that was set up for deferred memory testing.

4.20.1.28 VALIDATE QUEUE Command: /PHYSICAL and /BACKLINK Qualifiers

The Alpha SDA command VALIDATE QUEUE has two new qualifiers: /PHYSICAL and /BACKLINK. The /PHYSICAL qualifier causes SDA to allow validation of queues whose header and links are physical addresses. The /BACKLINK qualifier causes SDA to allow doubly linked lists to be validated from the tail of the queue.

The benefit of the /BACKLINK qualifier is that if the queue is found to be broken when validated from the head of the queue, this qualifier can be used to narrow the list of corrupted entries.

4.20.2 SDA CLUE: DOSD File Analysis Capability

OpenVMS Alpha Version 7.2 allows you to write the system dump file to a device other than the system disk. With this enhancement, CLUE HISTORY information can be collected even when dump off system disk (DOSD) is in use. For SDA CLUE to locate the dump file to be analyzed, you need to perform the following steps:

1. Modify the command procedure SYS$MANAGER:SYLOGICALS.COM to add the system logical name CLUE$DOSD_DEVICE to point to the device where the dump file resides. You need to supply only the physical or logical device name without a file specification.
2. Modify the command procedure SYS$MANAGER:SYLOGICALS.COM to mount systemwide the device where the dump file resides. Otherwise, SDA CLUE cannot access and analyze the dump file.

In the following example, the dump file has been placed on device $3$DUA25, which has the label DMP$DEV. You need to add the following commands to SYS$MANAGER:SYLOGICALS.COM:

$ MOUNT/SYSTEM/NOASSIST $3$DUA25: DMP$DEV DMP$DEV $ DEFINE/SYSTEM CLUE$DOSD_DEVICE DMP$DEV

4.20.3 SDA Extensions

OpenVMS Alpha Version 7.2 includes extension routines that allow you to create additional System Dump Analyzer (SDA) commands for interpreting system dumps. You can now use a documented and supported interface to write custom SDA extensions tailored to your business needs. For a description of the the SDA extension routines, as well as how to create and debug an extension, see the OpenVMS Alpha System Analysis Tools Manual.

4.21 System Services

Several new system services have been added, and several existing services have been modified for OpenVMS Version 7.2. This section contains the new and changed services.

4.21.1 Support for New Service, $GETENV

The new system service, $GETENV, returns the value(s) of the specified console environment variable(s).

4.21.2 Support for Intra-Cluster Communication

New services have been created to support Intra-Cluster Communication, an applications programming interface (API) for local and clusterwide interprocess communications.

For more information about these services and their application, see Section 4.11 in this manual.

4.21.3 Support for Clusterwide Logicals

This section contains information about services that have been modified to support clusterwide logical names. The following table details the changes.

System Service	New Features
$CRELNM	Support added for clusterwide logicals. Modified item, TABNAM Modified item code, LNM$_STRING Added condition value, SS$_INSFMEM
$CRELNT	Support added for clusterwide logicals. Modified attribute, LNM$M_CREATE_IF Modified arguments, PARTAB and TABNAM Added condition value, SS$_INSFMEM Modified condition value, SS$_IVLOGTAB Modified Required Access or Privileges section
$DELLNM	Support added for clusterwide logicals. Added condition value, SS$_INSFMEM Modified Required Access or Privileges section
$GETSYI	Support added for clusterwide logicals. Modified 64-bit descriptor field, BUFFER LENGTH Added item codes, SYI$_CWLOGICALS and SYI$_SYSTYPE All item codes work for clusterwide logicals
$TRNLNM	Support added for clusterwide logicals. Modified arguments, ATTR and TABNAM Added item code attributes, LNM$M_CLUSTERWIDE and LNM$M_INTERLOCKED Modified Description section

For more information about these services, refer to the OpenVMS System Services Reference Manual.

4.21.4 Support for Extended File Specifications

This section contains information about services that have been modified to support Extended File Specifications. The following table details the changes.

System Service	New Features
$CREPRC	Support added for Extended File Specifications. Modified service to include new symbolic name for the stsflg parameter.
$CVT_FILENAME	Support added for Extended File Specifications. New service that converts a string from RMS format to file-system (ACP/QIO) format, or from file-system (ACP/QIO) format to RMS format.
$GETJPI	Support added for Extended File Specifications. Modified service to include new item codes, JPI$_PARSE_STYLE_PERM, and JPI$_PARSE_STYLE_IMAGE.
$SETDDIR	Support added for Extended File Specifications. Modified the Description section
$SET_PROCESS_PROPERTIESW	Support added for Extended File Specifications. New service that sets a simple value associated with a process

For more information about these services, refer to the OpenVMS System Services Reference Manual.

4.21.5 Support for Fast Path

Two new services have been created to support Fast Path, $IO_FASTPATH and $IO_FASTPATHW.

For more information about Fast Path, refer to the OpenVMS System Services Reference Manual: GETQUI--Z, to the OpenVMS I/O User's Reference Manual, and see Table 2-1 in this manual.

4.21.6 Support for Personas

Previous versions of OpenVMS included system services that allowed a privileged OpenVMS process to create and use personae. Beginning with OpenVMS Version 7.2, several new system services are available to support persona lookup and retrieval and persona extensions.

For more information about these services and their application, see Section 4.18.2 in this manual and refer to the OpenVMS System Services Reference Manual.

OpenVMS Alpha Version 7.2 introduces a model of computing that allows multiple instances of OpenVMS to execute cooperatively in a single computer. With Adaptive Partitioned Multiprocessing (APMP), many processors (and other physical resources) are partitioned in order to run multiple instances of operating systems. Each instance has assigned CPUs, memory, and I/O. The instances share a part of memory, and CPUs can be reassigned from one instance to another while the system runs. This computing environment can be dynamically adapted to changing application needs and workload demands.

Compaq's first implementation of the APMP model of computing is the Galaxy Software Architecture on OpenVMS Alpha. An evolution in OpenVMS functionality, OpenVMS Galaxy leverages proven OpenVMS cluster, symmetric multiprocessing, memory management, memory channel community management, and performance features to provide extremely flexible operational computing capabilities.

For companies looking to improve their ability to manage unpredictable, variable, or growing IT workloads, OpenVMS Galaxy technology provides a flexible way to dynamically reconfigure and manage system resources.

By running multiple instances of OpenVMS in a single computer, an OpenVMS Galaxy computing environment gives you quantum improvements in:

• Compatibility---Existing applications run without changes.
• Availability---Presents opportunities to upgrade software and expand system capacity without downtime.
• Scalability---Offers scaling alternatives that improve performance of SMP and cluster environments.
• Adaptability---Physical resources can be dynamically reassigned to meet changing workload demands.
• Cost of ownership---Fewer computer systems reduce system management requirements, floor space, and more.

An OpenVMS Galaxy computing environment is ideal for high-availability applications, such as:

• Database servers
• Transaction processing systems
• Data Warehousing
• Data Mining
• Internet servers

With OpenVMS Alpha Version 7.2, you can create an OpenVMS Galaxy computing environment that allows you to:

• Run three instances of OpenVMS on an AlphaServer 8400
• Run two instances of OpenVMS on an AlphaServer 8200
• Run two instances of OpenVMS on an AlphaServer 4100
• Reassign CPUs between instances
• Perform independent booting and shutdown of instances
• Use shared memory for inter-instance communication
• Cluster instances within an OpenVMS Galaxy using the shared memory cluster interconnect
• Cluster instances with non-Galaxy systems
• Create applications using OpenVMS Galaxy APIs for resource management, event notification, locking for synchronization, and shared memory for global sections
• Use the Galaxy Configuration Utility to view and control the OpenVMS Galaxy environment
• Run a single-instance OpenVMS Galaxy on any Alpha system for application development

For more information about how to create, manage, and use an OpenVMS Galaxy computing environment, refer to the OpenVMS Alpha Galaxy Guide. This book includes:

• OpenVMS Galaxy licensing, hardware, and configuration requirements
• Procedures for creating OpenVMS Galaxy computing environments on OpenVMS Alpha Server 8400, 8200, and 4100 systems
• Complete details about how to use all of the OpenVMS Galaxy features and capabilities available in OpenVMS Alpha Version 7.2

Note that release notes about the Galaxy Software Architecture on OpenVMS are included in the OpenVMS Alpha Galaxy Guide.

This release includes new messages for the following OpenVMS facilities:

• ACME, Authentication and Credential Management
• ANALDISK, Analyze/Disk_Structure Utility
• BACKUP, Backup Utility
• Cluster Port Driver
• INSTALL, Install Utility
• IOGEN
• MOUNT, Mount Utility
• OPCOM, Operator Communication Process
• PCSI, POLYCENTER Software Installation Utility
• PCSIUI, POLYCENTER Software Installation Utility
• POWER, AlphaServer 8200 Series Power Monitoring
• RMS, OpenVMS Record Management Services
• SDA, System Dump Analyzer
• SET, SET Command and SET Utility
• SET, SET PASSWORD Command
• SYSINIT, System Initialization
• SYSTEM, System Services
• UAF, Authorize Utility

The Help Message database has been updated with all the new messages. This appendix alphabetically lists and describes only those messages that might occur before the system is fully functional; that is, when the Help Message database is not accessible.

For information about the HELP/MESSAGE command and qualifiers, see DCL help (type HELP HELP/MESSAGE at the DCL prompt) or refer to OpenVMS System Messages: Companion Guide for Help Message Users.

ACTERR, error activating ICBM

ALHOMERR, I/O error reading alternate home block on 'device-name'

ALHOMINV, invalid alternate home block on 'device-name'

CI port Virtual Circuit SETCKT OPEN timeout: Restart Port
Facility: Cluster Port Driver
Explanation: When the CI port found a new, remote CI node, the CI port did not complete the processing of a "virtual-circuit-open" command within the permitted virtual-circuit timeout period. The local CI port is either hung, offline, or saturated with activity, or the CI response queue processing CPU remained at or above IPL-8 for an extended period.
User Action: The port restarts automatically. If this error recurs, it indicates problems with port load balancing, system tuning, or faulty hardware or firmware on the CI port.

DOSETVOL, Use SET VOLUME/STRUCTURE_LEVEL and remount.

FIBREPOLL, scanning for devices through FIBRE port 'port-device'

FTLIOERR, fatal I/O error while trying to access device

INCONSET, structure level on 'device-name' is inconsistent with volume set

This error is fatal for all shareable mounts (for example, MOUNT/SYSTEM and MOUNT/SHARE). It is a warning for /NOSHARE mounts; however, the volume set is locked against modification. That is, existing files can be accessed and updated, but they cannot be extended or deleted.
User Action: If the volume set is not currently mounted /NOSHARE, dismount the portion that is currently mounted and mount the entire set using /NOSHARE. Then execute the DCL command SET VOLUME /STRUCTURE_LEVEL=5 on the volume set. Later, you can dismount the volume set and mount it as you wish.

INCONSTRUCT, inconsistent file structure level on 'device-name'

This error is fatal for all shareable mounts (for example, MOUNT/SYSTEM and MOUNT/SHARE). It is a warning for /NOSHARE mounts; however, the volume is locked against modification. That is, existing files can be accessed and updated, but they cannot be extended or deleted.
User Action: Mount the volume using /NOSHARE if it is not currently mounted as such. Then execute the DCL command SET VOLUME /STRUCTURE_LEVEL=5 on it. Later, you can dismount the volume and mount it as you wish.

Insuff. Bus Addr. Pool for Init.: Use AUTOGEN W/FEEDBACK (NPAG_BAP_*)
Facility: Cluster Port Driver
Explanation: The device driver failed to initialize because of a failure to allocate bus addressable pool (BAP). Either BAP was not created or it was insufficient.
User Action: To correctly size and position BAP in physical memory, manually invoke @SYS$UPDATE:AUTOGEN using FEEDBACK mode and reboot. For more information, consult the OpenVMS System Management Utilities Reference Manual: A--L or AUTOGEN help.

INVBACKLINK, invalid backlink in extension header 'file-number' on relative volume 'volume-number'

IVALOCLS, invalid HSZ allocation class, 'allocation-class'

MSCIOERR, I/O error while trying to access device

NOALOCLS, no multibus HSZ allocation class

NODEVID, no identifier defined for device

NOLUNS, no logical units found by array controller

Port incompatible with nonzero system base PA.
Facility: Cluster Port Driver
Explanation: You attempted to use an older non-PCI device, such as an XMI-based CIXCD or KFMSB, on an Alpha system whose main memory does not begin at physical address zero (PA0).
User Action: Use CIXCD or KFMSB adapters only in systems with system memory based at physical address zero (0). Use adapters such as CIPCA or KFPSA in systems with system memory based above physical address zero.

SCSIPOLL, scanning for devices through SCSI port 'port-device'

	privacy and legal statement
6520PRO_009.HTML