[OpenVMS documentation]
[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
Updated: 11 December 1998

OpenVMS Version 7.2
New Features Manual


Previous Contents Index

4.20.1.25 SHOW SYMBOL/ALL Command: /ALPHA and /VALUE Qualifiers

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.


Chapter 5
Compaq Galaxy Software Architecture on OpenVMS Alpha

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:

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

5.1 OpenVMS Galaxy Version 7.2 Features

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

5.2 Getting More Information

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:

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


Appendix A
New OpenVMS System Messages

This release includes new messages for the following OpenVMS facilities:

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

Facility: IOGEN
Explanation: OpenVMS was unable to activate the proper IOGEN Configuration Building Module during device autoconfiguration. Most likely, the image SYS$SHARE:SYS$ICBM.EXE is not present on your system disk or is not installed.
User Action: Check to see whether the image file exists and verify that it is installed as a known image. (For instructions on installing a known image, refer to the Install utility chapter in the OpenVMS System Management Utilities Reference Manual.) If you still have problems, reinstall OpenVMS onto your system disk or contact a Compaq support representative for assistance.
ALHOMERR, I/O error reading alternate home block on 'device-name'

Facility: MOUNT, Mount Utility
Explanation: An I/O error occurred while attempting to read the alternate home block on the volume being mounted. An accompanying message provides additional information about the error. This is a warning message; the mount is allowed to proceed.
User Action: To avoid future errors, repair the named volume using the DCL command ANALYZE/DISK_STRUCTURE/REPAIR.
ALHOMINV, invalid alternate home block on 'device-name'

Facility: MOUNT, Mount Utility
Explanation: The alternate home block on the volume being mounted does not have a valid format. This is a warning message; the mount is allowed to proceed.
User Action: To avoid future errors, repair the named volume using the DCL command ANALYZE/DISK_STRUCTURE/REPAIR.

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.

Facility: MOUNT, Mount Utility
Explanation: This message accompanies the INCONSTRUCT and INCONSET error messages to provide instructions for making the volume or volume set consistent.
User Action: If the volume or volume set is not currently mounted /NOSHARE, dismount the portion that is currently mounted and mount the volume or volume set using /NOSHARE. Then execute the DCL command SET VOLUME /STRUCTURE_LEVEL=5 on the volume or volume set. Later, you can dismount the volume or volume set and mount it as you wish.
FIBREPOLL, scanning for devices through FIBRE port 'port-device'

Facility: IOGEN
Explanation: This message is displayed while IO AUTOCONFIGURE scans a fibre channel bus to locate and configure devices on that bus.
User Action: None.
FTLIOERR, fatal I/O error while trying to access device

Facility: IOGEN
Explanation: During device configuration, OpenVMS was unable to communicate with one of the devices identified during its scan of the I/O buses.
User Action: Verify that your hardware configuration is set up properly and make any necessary corrections. If no configuration problems are noted, contact a Compaq support representative for assistance.
INCONSET, structure level on 'device-name' is inconsistent with volume set

Facility: MOUNT, Mount Utility
Explanation: The file structure level recorded on the volume is not consistent with the structure level of the volume set of which it is a part. The volume is marked as Files-11 structure level 2 while the rest of the volume set is structure level 5, or vice versa. This condition can occur if a system failure occurs during the execution of a SET VOLUME /STRUCTURE_LEVEL=5 command.

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'

Facility: MOUNT, Mount Utility
Explanation: The file structure level recorded on the volume is inconsistent. Parts of the volume are identified as Files-11 structure level 2 and other parts are identified as structure level 5. This condition can occur if a system failure occurs during the execution of a SET VOLUME /STRUCTURE_LEVEL=5 command.

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'

Facility: MOUNT, Mount Utility
Explanation: The backlink on an extension file header does not point to a valid location for a primary header.
User Action: Use the DCL command ANALYZE/DISK_STRUCTURE/REPAIR to repair the volume or volume set.
IVALOCLS, invalid HSZ allocation class, 'allocation-class'

Facility: IOGEN
Explanation: The allocation class read from a storage array exceeds the maximum allowed value of 999.
User Action: From the console of the storage array, set an allocation class for the controller that has a positive value of less than 1000.
MSCIOERR, I/O error while trying to access device

Facility: IOGEN
Explanation: During device configuration, OpenVMS was unable to communicate with one of the devices identified during its scan of the I/O buses.
User Action: Verify that your hardware configuration is set up properly and make any necessary corrections. If no configuration problems are noted, contact a Compaq support representative for assistance.
NOALOCLS, no multibus HSZ allocation class

Facility: IOGEN
Explanation: When you put a storage array into multibus failover mode, you must also assign an allocation class to the array controllers. OpenVMS has not obtained a valid allocation class from this device.
User Action: From the console of the storage array, set an allocation class for the array controller.
NODEVID, no identifier defined for device

Facility: IOGEN
Explanation: The device being configured either has been assigned an invalid device ID or it has an invalid or missing worldwide ID.
User Action: Assign a valid device ID to the failing device, following the procedure described in the documentation for the device or storage array. If you still have a problem, try replacing the drive. If the error persists, contact a Compaq support representative for assistance.
NOLUNS, no logical units found by array controller

Facility: IOGEN
Explanation: The storage array being configured by OpenVMS has reported that it contains no storage devices.
User Action: If you wish, add drives to the storage array.

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'

Facility: IOGEN
Explanation: This message is displayed while IO AUTOCONFIGURE scans a SCSI bus to locate and configure devices on that bus.
User Action: None.


Index Contents

[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
[OpenVMS documentation]

Copyright © Compaq Computer Corporation 1998. All rights reserved.

Legal
6520PRO_009.HTML