OpenVMS Version 7.3 Release Notes Order Number: AA–QSBTD–TE June 2001 This manual describes changes to the software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections. Note This online version of the release notes manual has the most current information compared to the printed version of this manual. Revision/Update Information: This is a new manual. Software Version: OpenVMS Alpha Version 7.
© 2001 Compaq Computer Corporation Compaq, AlphaServer, POLYCENTER, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. Motif, OSF1, and UNIX are trademarks of The Open Group in the United States and other countries. PostScript is a trademark of Adobe Systems, Inc. All other product names mentioned herein may be trademarks of their respective companies.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii 1 Introduction 1.1 1.1.1 1.1.2 1.1.3 1.1.4 1.2 1.3 1.4 OpenVMS Releases . . . . . . . . . . . . . . . . . . . . . . . . . . OpenVMS Major Release . . . . . . . . . . . . . . . . . . . OpenVMS New Feature Release . . . . . . . . . . . . . OpenVMS Minor Release . . . . . . . . . . . . . . . . . . . OpenVMS Limited Hardware Release . . . . . . . . . Upgrade Paths . .
2.3.2 Error at Shutdown After Booting CD–ROM for Full Environment Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12 3 OpenVMS Associated Products Release Notes Layered Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compaq Advanced Server Version 7.3 for OpenVMS (Alpha Only) . . . . . . PATHWORKS for OpenVMS (Alpha and VAX) . . . . . . . . . . . . . . . . . . . . . . PATHWORKS for OpenVMS Support . . . .
4.3 4.4 4.5 4.6 COM for OpenVMS (Alpha Only) Not Supported in a Mixed-Version Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Help New and Changed Topics . . . . . . . . . . . . . . . . . . . . . . . . OpenVMS Alpha Firmware for OpenVMS Alpha Version 7.3 . . . . . . . OpenVMS Freeware CD–ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3 4–3 4–4 4–5 . . . . . . . . . . . . . .
5.9.3 5.9.4 5.9.5 5.9.6 5.9.7 5.9.8 5.9.9 5.9.10 5.9.11 5.9.12 5.9.13 5.9.14 5.9.15 5.9.16 5.9.17 5.9.18 5.9.19 5.9.20 5.9.21 5.9.22 5.9.23 5.9.24 5.9.25 5.9.26 5.9.27 5.9.28 5.9.29 5.10 5.10.1 5.10.2 5.11 5.12 5.13 5.14 5.14.1 5.14.2 5.14.3 5.14.4 5.14.5 5.15 5.16 5.16.1 vi Remedial Kits Required for Extended File Cache (XFC) Used in Mixed Version OpenVMS Cluster Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre Channel Remedial Kits Support for SANWorks DRM . . . . . . . . .
5.16.2 VCC_MAXSIZE System Parameter Definition Corrected . . . . . . . . . . . 5.16.3 NISCS_MAX_PKTSZ System Parameter Definition Corrected . . . . . . . 5.16.4 Parameter Description Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.16.5 Obsolete System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.17 Terminal Fallback Facility (TFF) (Alpha Only) . . . . . . . . . . . . . . . . . . . . . 5.18 Volume Shadowing for OpenVMS . . . . . . . . . . . . . . . . . . .
6.9 Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9.1 ANALYZE/PROCESS_DUMP Command (Alpha Only) . . . . . . . . . . . . . 6.9.2 SET MODULE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9.3 SET EVENT Ada Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9.4 Enumerated Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9.
6.20 POSIX Threads Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20.1 Process Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20.2 Dynamic CPU Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . 6.20.3 Enhanced Debugging of Threaded Programs . . . . . . . . . . . . . . . . . . . . 6.20.4 POSIX 1003.4a Draft 4 Interface Retirement . . . . . . . . . . . . . . . . . . . . 6.20.
7.9 7.10 7.11 7.12 7.13 7.14 7.15 7.16 7.17 7.17.1 7.17.2 7.17.3 7.17.4 7.18 7.18.1 7.18.2 7.19 7.20 ISA_CONFIG.DAT Unsupported in Future Release (Alpha Only) . . . . . . . Required Change in ISA_CONFIG.DAT on AlphaStation 200/400 . . . . . . . Memory Holes on AlphaServer 4100 Systems . . . . . . . . . . . . . . . . . . . . . . SYS$MSBDRIVER Removed from OpenVMS Alpha Distribution . . . . . . . Device IPL Setup for OpenVMS Alpha Drivers . . . . . . . . . . . . . . . . . . . . .
B.1.7 B.1.8 B.2 B.2.1 B.2.2 B.3 B.3.1 B.3.2 B.4 B.5 B.5.1 B.5.2 B.6 B.7 B.7.1 B.8 B.8.1 B.8.2 B.8.3 B.9 B.9.1 B.9.2 B.10 B.10.1 B.10.2 B.11 B.11.1 Keyboard Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OpenVMS Cluster Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . AlphaServer 1000A (Alpha Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bus Probe Algorithm Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A–1 B–1 B–2 xii OpenVMS VAX SPL Subscription Services . . . . . . . . . . . . . . . . . . . . . . Supported Microcode Revision Levels . . . . . . . . . . . . . . . . . . . . . . . . . Commands for Updating Microcode in Certain DSSI Disk Devices . . .
Preface Intended Audience This manual is intended for all OpenVMS operating system users. Read this manual before you install, upgrade, or use Version 7.3 of the operating system. Document Structure This manual contains the following chapters and appendixes: • Chapter 1 contains information describing the type of OpenVMS releases, upgrade paths, and support policy. • Chapter 2 contains release notes that pertain to installing the OpenVMS operating system.
• The release note may be pertinent in multiple-version OpenVMS Cluster systems. Related Documents For a list of additional documents that are available in support of this version of the OpenVMS operating system, refer to the OpenVMS Version 7.3 New Features and Documentation Overview. For additional information about OpenVMS products and services, access the following Compaq web site: http://www.compaq.com/openvms Reader’s Comments Compaq welcomes your comments on this manual.
... 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.
1 Introduction This chapter contains information about the following topics: • OpenVMS releases • Upgrade paths • Support policy 1.1 OpenVMS Releases The following sections describe the differences in OpenVMS releases. Full upward compatibility of user-mode code is part of any OpenVMS release. 1.1.
Introduction 1.1 OpenVMS Releases Minor releases are shipped to all customers with the appropriate software service contracts. 1.1.4 OpenVMS Limited Hardware Release Limited hardware releases are specific to, tested for, and targeted at new systems, new option support, and new hardware configurations. These releases may include specific remedial fixes that are required to support the new hardware, but they do not include enhancements or general maintenance. No application impact is expected.
Introduction 1.2 Upgrade Paths OpenVMS Alpha Figure 1–1 illustrates the OpenVMS Alpha upgrade paths. The bold lines indicate the direct upgrade paths to Version 7.3. Figure 1–1 OpenVMS Alpha Upgrade Paths OpenVMS Alpha V6.2-1Hx OpenVMS Alpha V7.0 OpenVMS Alpha V7.1-2 OpenVMS Alpha V7.2x OpenVMS Alpha V7.3 VM-0572A-AI For OpenVMS Alpha, you can upgrade directly to Version 7.3 from Version 6.2x, Version 7.0, Version 7.1x, and 7.2x. Cluster rolling upgrades are supported from Version 7.
Introduction 1.2 Upgrade Paths If you are running Version 5.5-2, you can upgrade to Version 6.1 and then to Version 7.3. Caution Install the following remedial kit before upgrading from Version 6.1 to Version 7.3. VAXBACK04_061 Remedial kits can be accessed at the following World Wide Web (WWW) address: http://www.compaq.
Introduction 1.4 Compaq’s Support Policy A software release is considered a current version when it is the most recent release and for the twelve months following the release of a subsequent version. A subsequent version is defined as a Major or New Feature release. Major releases contain substantial new functionality. The version number increases to the next integer (for example, 6.2 to 7.0). New Feature releases contain some additional functionality.
2 OpenVMS Software Installation Release Notes This chapter contains information that applies to installations and upgrades of the OpenVMS Alpha and OpenVMS VAX operating systems. The installation and upgrade notes in this chapter are organized into the following categories: • Installation and upgrade notes common to both Alpha and VAX systems (see Section 2.1) • Alpha specific installation and upgrade notes (see Section 2.2) • VAX specific installation and upgrade notes (see Section 2.
OpenVMS Software Installation Release Notes 2.1 Installation and Upgrade Information Common to Alpha and VAX During the main installation procedure for OpenVMS Version 7.3, you have the option of installing the following Compaq networking software: • Compaq TCP/IP Services for OpenVMS TCP/IP Services and DECnet can run concurrently on your system.
OpenVMS Software Installation Release Notes 2.1 Installation and Upgrade Information Common to Alpha and VAX Table 2–1 (Cont.
OpenVMS Software Installation Release Notes 2.1 Installation and Upgrade Information Common to Alpha and VAX For information on PATHWORKS (LAN Manager) servers, see Section 3.3.2. For more information about the Advanced Server for OpenVMS product, see Section 3.2. 2.1.5 Upgrading Advanced Server for OpenVMS V7.2 or V7.2A V7.3 If you you want to upgrade your Advanced Server for OpenVMS server, follow these steps: 1. Upgrade your Advanced Server V7.2/7.2A for OpenVMS server to Advanced Server V7.
OpenVMS Software Installation Release Notes 2.1 Installation and Upgrade Information Common to Alpha and VAX For example: %PCSI-I-RETAIN, file [SYSEXE]DTSS$SET_TIMEZONE.EXE was not replaced because file from kit has a lower generation number You can ignore these messages. The DECnet-Plus kit has been properly installed. 2.1.8 Installing DECwindows with Some Layered Products May Cause Insufficient Global Sections V7.
OpenVMS Software Installation Release Notes 2.1 Installation and Upgrade Information Common to Alpha and VAX This is correct and normal information to ensure awareness of a possible effect on the system time during the minimum startup procedure. It can safely be ignored if it does not affect your own requirements for the startup of the system (such as, during an upgrade or installation). 2.
OpenVMS Software Installation Release Notes 2.2 Installation and Upgrade Information Specific to Alpha Corrected lines [SYSLIB]SYS$ICBM.EXE_OLD VMS721_DRIVER-V0200 [SYSLIB]SMI$SHR.EXE_OLD VMS721_MANAGEV0100 [SYS$LDR]SYS$GFDRIVER.EXE_OLD VMS721_VX1-V0200 [SYSEXE]SYS$CONFIG.DAT_OLD VMS721_VX1-V0200 [SYSLIB]DECC$SHR.EXE_OLD VMS721H1_ACRTLV0200 [SYS$LDR]SYS$CPU_ROUTINES_2308.EXE_OLD VMS721H1_CPU2308V0100 [SYSEXE]SYS$SMHANDLER_SLAVE_2308.
OpenVMS Software Installation Release Notes 2.2 Installation and Upgrade Information Specific to Alpha • The Registry • Advanced Server • COM layered products • Any other applications using Registry At some point, you will have to shutdown all remaining Registry-based activity in the cluster just before you start up Registry and applications using Registry services on the V7.3 nodes. Note If you are running Compaq Advanced Server for OpenVMS on OpenVMS V7.
OpenVMS Software Installation Release Notes 2.2 Installation and Upgrade Information Specific to Alpha 6. Ensure that the Registry server does not restart on the node or nodes you are upgrading until the upgrade is complete, or, if you are selectively upgrading nodes, until you determine that you wish to switch over to the new server. To prevent Registry startup on reboot, you need to check two things on each node: a. In the file SYS$MANAGER:SYLOGICALS.
OpenVMS Software Installation Release Notes 2.2 Installation and Upgrade Information Specific to Alpha If you are selectively upgrading nodes, you should comment out the "TO_BE_STARTED" logical name definitions in the SYS$MANAGER:SYLOGICALS.COM file and the invocation of Advanced Server startup in the SYS$MANAGER:SYSTARTUP_VMS.COM file on any remaining OpenVMS V7.2-1 nodes in the cluster, as described in step 6. 12.
OpenVMS Software Installation Release Notes 2.2 Installation and Upgrade Information Specific to Alpha This error can occur either when you are upgrading Compaq TCP/IP Services as part of an OpenVMS upgrade, or during a separate TCP/IP Services upgrade. When the old version of TCP/IP Services is removed, it attempts to remove the module UCX from the SDA Help library.
OpenVMS Software Installation Release Notes 2.3 Installation and Upgrade Information Specific to VAX 2.3.1 Magnetic Tape Media for OpenVMS VAX to Be Retired V7.3 OpenVMS VAX Version 7.3 is the last OpenVMS release for which TK50 and magnetic tape media will be distributed. All future OpenVMS VAX releases will be available on CD–ROM media only. For more information, see Appendix A. 2.3.2 Error at Shutdown After Booting CD–ROM for Full Environment Installation V7.
3 OpenVMS Associated Products Release Notes This chapter contains installation and support information about a broad range of OpenVMS associated products. For notes about using compilers, linkers, and run-time library routines, see Chapter 6. 3.1 Layered Product Support The Software Public Rollout Reports for OpenVMS list the availability of Compaq’s software products shipping on the Software Products Library kits (CD–ROM consolidations) for OpenVMS Alpha and OpenVMS VAX.
OpenVMS Associated Products Release Notes 3.2 Compaq Advanced Server Version 7.
OpenVMS Associated Products Release Notes 3.3 PATHWORKS for OpenVMS (Alpha and VAX) You can run PATHWORKS V6.0D for OpenVMS (Advanced Server) on either OpenVMS Alpha Versions 7.3, 7.2-1, or 6.2, or on OpenVMS VAX Versions 7.3, 7.2, or 6.2. To access PATHWORKS V6.0D for OpenVMS (Advanced Server) on OpenVMS Version 7.3, clients must be licensed using the license PAK PWLMXXXCA06.00, PWLMXXXCA07.02, or PWLMXXXCA07.03.
OpenVMS Associated Products Release Notes 3.4 C and C++ • In the Australia timezone file, the rules for the following time zones have been updated: Time Zone Name Territory or State ACT Australia Capital Territory NSW New South Wales NT Northern Territory QLD Queensland SA South Australia TAS Tasmania VIC Victoria WA Western Australia 3.4.2 STARLET Header Files Now Ship with OpenVMS VAX V7.1 Starting with Version 7.
OpenVMS Associated Products Release Notes 3.5 COBOL (Alpha Only)—RMS Special Registers and RMS$_FNM Compared to RMS$CRE reflected in I/O runtime diagnostics and RMS special registers. You do not need to use the new ODS-5 support to see these RMS differences. 3.6 DECdfs This section contains release notes pertaining to Compaq DECdfs for OpenVMS (formerly named DECdfs). 3.6.1 Version 2.3-1 Required for OpenVMS Alpha and VAX V7.3 If you want to run Compaq DECdfs for OpenVMS on OpenVMS Alpha Version 7.
OpenVMS Associated Products Release Notes 3.7 DECram Version Support from the S1 address into the S2 address space. This change allows for the creation and addressing of devices larger than 2 gigabytes (GBs). Any Alpha-based system can be easily upgraded to DECram Version 3.0. With Version 3.0 you can use the new DECRAM command interface or continue using the same familiar commands from SYSMAN for creating, initializing, and mounting DECram disks. DECRAM Version 3.
OpenVMS Associated Products Release Notes 3.8 Lightweight Directory Access Protocol (LDAP) API 3.8.2 The Routine ber_flatten( ) Does Not Detect Mismatched Braces V7.3 The routine ber_flatten( ) does not correctly detect the situation where ’{’ and ’}’ format modifiers in a BerElement are incorrectly matched. 3.9 DECwindows Motif This section contains release notes pertaining to the Compaq DECwindows Motif for OpenVMS layered product. 3.9.1 System Parameter Values Required for Installation V7.
OpenVMS Associated Products Release Notes 3.11 Installing Compaq Open3D on OpenVMS Alpha Version 7.3 3.11 Installing Compaq Open3D on OpenVMS Alpha Version 7.3 V7.3 During installation of Open3D on OpenVMS Alpha Version 7.3, an older version of the SYS$LOADABLE_IMAGES:SYS$GYCDRIVER.EXE image is installed. Before you install Open3D on OpenVMS Alpha Version 7.3 perform one of the following tasks: • Create a backup copy of the SYS$LOADABLE_ IMAGES:SYS$GYCDRIVER.EXE image.
OpenVMS Associated Products Release Notes 3.13 DEC PL/I—RTL Support for OpenVMS Any questions about DEC PL/I and VAX PL/I should be directed to Kednos Corporation at the following address: Kednos Corporation 2857 Sloat Rd. Pebble Beach, CA. 93953 Phone: (831) 373-7003 3.14 Compaq Reliable Transaction Router (RTR) License V7.3 Reliable Transaction Router (RTR) is fault tolerant transactional messaging middleware used to implement large, distributed applications using client/server technology.
OpenVMS Associated Products Release Notes 3.15 Compaq TCP/IP Services for OpenVMS For information about upgrading to TCP/IP Services for OpenVMS Version 5.1, see the Compaq TCP/IP Services for OpenVMS Release Notes. 3.15.2 DIGITAL TCP/IP Services for OpenVMS Version 4.2 (UCX) Not Supported V7.3 DIGITAL TCP/IP Services for OpenVMS Version 4.2 (UCX) is not supported on OpenVMS Version 7.0 and later releases.
4 General User Release Notes This chapter provides information for all users of the OpenVMS operating system. It includes information about commonly used commands and utilities. For information about new features included in this version of the software, refer to the OpenVMS Version 7.3 New Features and Documentation Overview. 4.1 AlphaServer GS Series Systems This section contains release notes of general interest to most users of the AlphaServer GS Series Systems. 4.1.
General User Release Notes 4.1 AlphaServer GS Series Systems 4.1.3 V5.9B Console Firmware Required for OpenVMS on AlphaServer GS80/160/320 Systems V7.3 If you are running OpenVMS Alpha Version 7.3 on AlphaServer GS80/160/320 systems, you must download console firmware V5.9B or later from the following location: http://ftp.digital.com/pub/DEC/Alpha/firmware/ Note that you need the V5.9B console firmware to use the new CPU online replace feature. 4.1.
General User Release Notes 4.2 Booting OpenVMS Version 7.3 on a Personal Workstation with IDE Controllers To determine which IDE chip you have in your configuration, enter the following SRM console command: SHOW CONFIGURATION If you see Cypress PCI Peripheral Controller, you can boot OpenVMS. If you see Intel SIO 82378, you will need to use and boot from a SCSI CD–ROM. 4.3 COM for OpenVMS (Alpha Only) Not Supported in a Mixed-Version Cluster V7.
General User Release Notes 4.
General User Release Notes 4.6 OpenVMS Freeware CD–ROMs 4.6 OpenVMS Freeware CD–ROMs V7.3 Included in the OpenVMS Version 7.3 CD–ROM kit are the OpenVMS Freeware Version 5.0 CD–ROMs. The Freeware CD–ROMs contain free software tools and utilities for creating applications and managing OpenVMS systems. To mount the Freeware CD–ROMs, insert a CD–ROM into the CD–ROM drive and enter the following commands appropriate to the freeware volume being mounted.
5 System Management Release Notes This chapter contains information that applies to system maintenance and management, performance management, and networking. For information about new features included in this version of the software, refer to the OpenVMS Version 7.3 New Features and Documentation Overview. V7.
System Management Release Notes 5.1 ECP Data Collector and ECP Performance Analyzer V5.4 Available with V7.3 5.1 ECP Data Collector and ECP Performance Analyzer V5.4 Available with V7.3 V7.3 Starting with the shipment of OpenVMS Version 7.3, the Enterprise Capacity and Performance (ECP) Data Collector Version 5.4 for OpenVMS and the Enterprise Capacity and Performance (ECP) Analyzer Version 5.4 for OpenVMS will be provided to users with a valid operating system license at no additional cost.
System Management Release Notes 5.2 Extended File Specifications Because mixed UNIX and OpenVMS style extended file names are not yet supported by the Compaq C RTL, you may be required to use UNIX style syntax when interacting with Java applications or FastTrack or Apache Server. For example, you may want to modify a root to which you append additional directories or a file name.
System Management Release Notes 5.3 External Authentication Installation and Configuration Guide. See this manual and the OpenVMS Guide to System Security for detailed information about using external authentication. 5.3.1 FTP Server Uses External Authentication V7.2 With the release of Compaq TCP/IP Services for OpenVMS Version 5.0, the File Transfer Protocol (FTP) server uses external authentication to authenticate connections on the OpenVMS system. 5.3.
System Management Release Notes 5.3 External Authentication 5.3.5 Compaq DECnet-Plus Requirement V7.2-1 Users with the EXTAUTH bit set in their SYSUAF account record cannot use explicit access control strings with systems running Compaq DECnet-Plus unless their externally authenticated password is all uppercase characters.
System Management Release Notes 5.3 External Authentication For externally authenticated users, the normal system authorization database (SYSUAF.DAT) is used to construct the OpenVMS process profile (UIC, privileges, quotas, and so on) and to apply specific login restrictions. However, there are two key differences between externally authenticated users and normal OpenVMS users.
System Management Release Notes 5.3 External Authentication 5.3.11 No Password Expiration Notification on Workstations V7.1 In the LAN Manager domain, a user cannot log in once a password expires. Users on personal computers (PCs) receive notification of impending external user password expiration and can change passwords before they expire. However, when a user logs in from an OpenVMS workstation using external authentication, the login process cannot determine if the external password is about to expire.
System Management Release Notes 5.5 OpenVMS Galaxy Version 7.3 5.5.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster Members V7.2 OpenVMS Version 7.2 introduced 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.
System Management Release Notes 5.5 OpenVMS Galaxy Version 7.3 5.5.5 MOP Booting Restrictions V7.2 In an OpenVMS Galaxy computing environment, MOP (Maintenance Operations Protocol) Booting is only supported on Instance 0. This restriction will be removed in a future release. 5.5.
System Management Release Notes 5.7 Lock Manager 5.7.2 Instituting the Dedicated CPU Lock Manager Functionality (Alpha Only) V7.3 With OpenVMS Version 7.3, Compaq introduces an alternative locking mode that allows a CPU to be dedicated to the lock manager. The dedicated CPU lock manager can perform better than the traditional lock manager under heavy locking loads.
System Management Release Notes 5.7 Lock Manager Because of this change to nonpaged pool, Compaq recommends the following steps: • Use AUTOGEN with feedback information to tune the size of nonpaged pool. • Inspect MODPARAMS.DAT to check for any NPAGEDYN or NPAGEVIR settings previously made to increase the size of nonpaged pool due to the lock manager’s usage. You may find that these parameters can be either trimmed back or removed due to changes to the lock manager.
System Management Release Notes 5.8 OPCOM CLUSTER DEVICES DISKS LICENSE NETWORK OPER1 through OPER12 PRINTER SECURITY TAPES When you specify an invalid class, all classes are enabled. This change causes the error messages listed to reach as many operators as possible. 5.8.3 Handling OPC$ALLOW_INBOUND and OPC$ALLOW_OUTBOUND V7.3 The algorithm formerly used by OPCOM when OPC$ALLOW_INBOUND and OPC$ALLOW_OUTBOUND were set to FALSE was found to be too restrictive.
System Management Release Notes 5.9 OpenVMS Cluster Systems 5.9 OpenVMS Cluster Systems The release notes in this section pertain to OpenVMS Cluster systems. 5.9.1 New Error Message About Packet Loss V7.3 Prior to OpenVMS Version 7.3, an SCS virtual circuit closure was the first indication that a LAN path had become unusable. In OpenVMS Version 7.
System Management Release Notes 5.9 OpenVMS Cluster Systems A remedial kit will be available from the following web site to correct this problem: http://www.support.compaq.com/patches/ This problem exists only on Alpha platforms running OpenVMS Alpha Version 7.2x. 5.9.3 Remedial Kits Required for Extended File Cache (XFC) Used in Mixed Version OpenVMS Cluster Systems V7.
System Management Release Notes 5.9 OpenVMS Cluster Systems You can either download the remedial kits from the following web site, or contact your Compaq support representative to receive the remedial kits on http://www.compaq.com/support Note Remedial kits are periodically updated on an as-needed basis. Always use the most recent remedial kit for the facility, as indicated by the version number in the kit’s ReadMe file. The most recent version of each kit is the version posted to the WWW site.
System Management Release Notes 5.9 OpenVMS Cluster Systems 5.9.6 OpenVMS Version 7.2-1 Installation Restrictions for Fibre Channel V7.2-1 Note that the OpenVMS Alpha Version 7.2-1 CD–ROM does not support the KGPSA-BC or KGPSA-CA. You must install the operating system to a disk that is not accessed through the KGPSA-BC or KGPSA-CA, then apply the latest FIBRECHAN kit, and reboot to use the KGPSA-BC or KGPSA-CA. This restriction applies only to OpenVMS Alpha Version 7.2-1.
System Management Release Notes 5.9 OpenVMS Cluster Systems 5.9.8 KGPSA NVRAM Error with Console V5.6 and Later V7.2-1 When you use V5.6 or later versions of the console, you will see the error message kgpsaa0.0.0.2.4 - Nvram read failed, when the console KGPSA driver starts. This error indicates that NVRAM on the KGPSA is unformatted or not working properly. The more likely reason is that the NVRAM is unformatted. The NVRAM was always unformatted prior to V5.6. As of V5.
System Management Release Notes 5.9 OpenVMS Cluster Systems 5.9.9 Selective Autoconfiguration Not Supported in Some Fibre Channel and SCSI Configurations V7.2-1 OpenVMS Alpha provides SYSMAN commands that enable system managers to specify which devices will be autoconfigured.
System Management Release Notes 5.9 OpenVMS Cluster Systems To avoid this problem when upgrading, use one of the following procedures: • Upgrade all systems before adding the CCMAA-xx MEMORY CHANNEL adapters. • If you have MEMORY CHANNEL hubs, power them off before upgrading each system. After all systems have been upgraded, power on the MEMORY CHANNEL hubs. • If the nodes are connected directly in a virtual hub configuration, disconnect the MEMORY CHANNEL cables before upgrading each system.
System Management Release Notes 5.9 OpenVMS Cluster Systems Table 5–2 System Parameter Settings for Multipath Shadow Sets System Parameter Recommended Setting MSCP_CMD_TMO 60 as a minimum. The value of 60 is appropriate for most configurations. Some configurations may require a higher setting.
System Management Release Notes 5.9 OpenVMS Cluster Systems 5.9.17 Multipath Failover Fails Infrequently on HSZ70/HSZ80 Controllers V7.2-1 Under heavy load, a host-initiated manual or automatic path switch from one controller to another may fail on an HSZ70 or HSZ80 controller. Testing has shown this to occur infrequently. Note This problem has been corrected for the HSZ70 in the firmware revision HSOF V7.7 (and later versions) and will be corrected for the HSZ80 in a future release.
System Management Release Notes 5.9 OpenVMS Cluster Systems To avoid this problem, disable autonegotiation on the new node’s DEGPA, as follows: • Perform a conversational boot when first booting the node into the cluster. • Set the new node’s system parameter LAN_FLAGS to a value of 32 to disable autonegotiation on the DEGPA. 5.9.20 DQDRIVER Namespace Collision Workaround V7.
System Management Release Notes 5.9 OpenVMS Cluster Systems Restriction: If you attempt to use the DCL command $INITIALIZE to initialize an IDC hard drive on a remote system using the mass storage control protocol (MSCP) server, you may receive a warning message about the lack of a bad block file on the volume. You can safely ignore this warning message. Additionally, previously unused drives from certain vendors contain factorywritten data that mimics the data pattern used on a head alignment test disk.
System Management Release Notes 5.9 OpenVMS Cluster Systems 5.9.24 SHOW DEVICE Might Fail in Large Fibre Channel Configurations V7.2-1 The problem of SHOW DEVICE failing in large Fibre Channel configurations has been corrected in the following versions: • OpenVMS Alpha Version 7.2-1 with the remedial kit DEC-AXPVMS-VMS721_ UPDATE-V0100-4.PCSI • OpenVMS Alpha Version 7.2-1H1 • OpenVMS Alpha Version 7.
System Management Release Notes 5.9 OpenVMS Cluster Systems 5.9.26 Fibre Channel Path Name Syntax Permits Quotation Marks V7.2 Enclosing a Fibre Channel path name in quotation marks is valid, starting in OpenVMS Alpha Version 7.3. Prior to OpenVMS Version 7.3, the documentation and help text indicated that a path name could be enclosed in quotation marks, for example: $ SET DEVICE $1$dga166:/PATH="PGA0.5000-1FE1-0000-1501"/SWITCH In versions of the system prior to OpenVMS Version 7.
System Management Release Notes 5.9 OpenVMS Cluster Systems did not test the current path first, and did not stay on that path if the error condition had cleared. 5.10 OpenVMS Registry The release notes in this section pertain to the OpenVMS Registry. 5.10.1 Registry Services in a Mixed OpenVMS V7.3/V7.2-1 Cluster V7.3 Removing the data transfer size restrictions on the OpenVMS NT Registry required a change in the communication protocol used by the Registry.
System Management Release Notes 5.10 OpenVMS Registry the snapshot files which may be difficult to repair. Third, by periodically exporting the database, creating a new database, and importing the saved export file; you are effectively compacting the database and thereby keeping it smaller and more efficient. It should also be noted that in previous versions of OpenVMS, the EXPORT command may have failed to complete the operation under some conditions.
System Management Release Notes 5.13 Queue Manager—Long Boot Times OPERATOR.LOG. The long boot time is caused by the queue manager needing a large space to accommodate the queue journal file. The following example shows the error messages displayed in the operator.log: %%%%%%%%%%% OPCOM 2-MAR-2000 23:05:31.24 %%%%%%%%%%% Message from user QUEUE_MANAGE on PNSFAB %QMAN-E-OPENERR, error opening $1$DUA0:[SYS3.SYSCOMMON.][SYSEXE] SYS$QUEUE_MANAGER.QMAN$JOURNAL;1 %%%%%%%%%%% OPCOM 2-MAR-2000 23:05:32.
System Management Release Notes 5.14 RMS Journaling Previous versions: [SYSJNL]RMS$214003BC.RMS$JOURNAL;1 Current version: [SYSJNL.NODE1]CB300412.;1 If RMS does not find either the [SYSJNL] directory or the node-specific directory, RMS creates them automatically. 5.14.2 Recovery Unit Journaling Incompatible with Kernel Threads (Alpha Only) V7.
System Management Release Notes 5.14 RMS Journaling only to recovery unit journaled files accessed across the network in an OSI or mixed OSI and non-OSI environment. 5.14.5 VFC Format Sequential Files VAX V5.0 Alpha V1.0 You cannot update variable fixed-length control (VFC) sequential files when using before-image or recovery unit journaling. The VFC sequential file format is indicated by the symbolic value FAB$C_VFC in the FAB$B_RFM field of the FAB. 5.
System Management Release Notes 5.16 System Parameters 5.16.3 NISCS_MAX_PKTSZ System Parameter Definition Corrected V7.3 PEDRIVER uses NISCS_MAX_PKTSZ to compute the maximum amount of data to transmit in any LAN packet: LAN packet size <= LAN header (padded Ethernet format) + NISCS_MAX_PKTSZ + NISCS checksum (only if data checking is enabled) + LAN CRC or FCS The following table shows the minimum NISCS_MAX_PKTSZ value required to use the maximum packet size supported by specified LAN types.
System Management Release Notes 5.16 System Parameters • VCC_FLAGS (Alpha only) • VCC_MAX_CACHE (Alpha only) • VCC_MAX_LOCKS (Alpha only) • VCC_WRITEBEHIND (Alpha only) • VCC_WRITE_DELAY (Alpha only) • VIRTUALPAGECNT • XQPCTL2 • XQPCTLD1 You can read the new descriptions of these system parameters in online help. For example: $ HELP SYS_PARAMETERS FAST_PATH 5.16.5 Obsolete System Parameters V7.3 Starting with OpenVMS Version 7.
System Management Release Notes 5.17 Terminal Fallback Facility (TFF) (Alpha Only) Note TFFSHR has been removed from IMAGELIB because it is not a documented, user-callable interface. The image is still available in the SYS$LIBRARY: directory. To start TFF, invoke the TFF startup command procedure located in SYS$MANAGER, as follows: $ @SYS$MANAGER:TFF$SYSTARTUP.
System Management Release Notes 5.18 Volume Shadowing for OpenVMS 5.18 Volume Shadowing for OpenVMS The following release notes pertain to Volume Shadowing for OpenVMS. 5.18.1 Minicopy Version Required on All Nodes 7.3 OpenVMS Alpha Version 7.3 introduces minicopy support in Compaq Volume Shadowing for OpenVMS. To use this new feature of volume shadowing in an OpenVMS Cluster system, OpenVMS Version 7.3, or an upgrade to OpenVMS Version 7.
System Management Release Notes 5.18 Volume Shadowing for OpenVMS $DISMOUNT/POLICY=MINICOPY $80$DKA302: %DISM-W-CANNOTDMT, $80$DKA302: cannot be dismounted %DISM-F-SRCMEM, only source member of shadow set cannot be dismounted $ $ $DISMOUNT/POLICY=MINICOPY $80$DKA302: $ This problem will be corrected in a future release. 5.18.4 SHADOW_MAX_UNIT Settings V7.3 OpenVMS Alpha Version 7.3 introduces minicopy support in Volume Shadowing for OpenVMS.
6 Programming Release Notes This chapter provides release notes about both application and system programming on OpenVMS systems. For information about new programming features included in OpenVMS Version 7.3, refer to the OpenVMS Version 7.3 New Features and Documentation Overview. 6.1 Backup API This section contains release notes pertaining to the Backup application programming interface (API). 6.1.1 Unexpected Informational Message V7.
Programming Release Notes 6.1 Backup API 6.1.3 Repetitive Calls to BACKUP$START Can Cause an Error V7.1 Repetitive calls to BACKUP$START can cause the following error: %BACKUP-F-INSBUFSPACE, insufficient buffer space The number of repetitive calls completed before receiving this error varies, depending on the previous backup operations performed. The workaround for an application that receives this error is to exit the operation and restart. 6.2 Batch and Print Queues—Terminating Executing Batch Jobs V6.
Programming Release Notes 6.3 COM for OpenVMS (Alpha Only) 6.3 COM for OpenVMS (Alpha Only) V7.3 For release notes about COM for OpenVMS, see the OpenVMS Connectivity Developer Guide, which is installed as part of the COM for OpenVMS installation process. That document is available in PostScript, HTML, and PDF formats. The OpenVMS Connectivity Developer Guide is also available from the OpenVMS website at the following location: http://www.openvms.compaq.com/openvms/products/dcom/ 6.
Programming Release Notes 6.5 Compaq C Run-Time Library 6.5.1 The strptime Function Is Now XPG5 Compliant V7.3 The strptime function has been modified to be compliant with X/Open CAE Specification System Interfaces and Headers Issue 5 (commonly known as XPG5). The change for XPG5 is in how the strptime function processes the "%y" directive for a two-digit year within the century if no century is specified.
Programming Release Notes 6.5 Compaq C Run-Time Library 6.5.5 Case Preservation Supported in File Names (Alpha Only) V7.3 The Compaq C RTL is enhanced to support case preservation in file names for an ODS-5 device. This feature must be explicitly enabled by the user. See the OpenVMS Version 7.3 New Features and Documentation Overview for more details. 6.5.6 Exact Case argv Arguments Supported (Alpha Only) V7.
Programming Release Notes 6.5 Compaq C Run-Time Library 6.5.11 New LINK Command for Linking /NOSYSSHR (VAX Only) V7.3 The LINK command for linking /NOSYSSHR on OpenVMS VAX systems is now: $ LINK/NOSYSSHR PROG, SYS$LIBRARY:DECCRTL.OLB/INCLUDE=(CMA$TIS,CMA$TIS_VEC)/LIB Previously, the LINK command was: $ LINK/NOSYSSHR PROG, SYS$LIBRARY:DECCRTL.OLB/INCLUDE=CMA$TIS/LIB 6.5.12 The select Socket Function Returns Failure for Invalid File Descriptor V7.
Programming Release Notes 6.6 Compaq COBOL Run-Time Library (Alpha Only) 6.6.3 RTL Compatibility with Programs Linked Against Older Version V7.3 RTL compatibility with programs linked against the V2.4 TIMA RTL and V2.5 RTL has been restored in these areas: ACCEPT FROM DATE YYYYMMDD ACCEPT FROM DAY YYYYDDD /MATH=CIT3 (/SWITCH=DC_USE_CIT3 with V2.4 TIMA) Any program that uses any of these features and has been linked against the older V2.6 RTLs (DEC$COBRTL V2.6-467 or V2.
Programming Release Notes 6.8 Compaq Distributed Computing Environment (DCE) for OpenVMS 6.8 Compaq Distributed Computing Environment (DCE) for OpenVMS This section contains important release notes for existing users of Compaq Distributed Computing Environment (DCE) for OpenVMS VAX and OpenVMS Alpha. Remote procedure call (RPC) functionality was integrated into the operating system beginning with OpenVMS Version 7.2. As of OpenVMS Version 7.
Programming Release Notes 6.9 Debugger 6.9 Debugger This section contains release notes pertaining to the OpenVMS Debugger. 6.9.1 ANALYZE/PROCESS_DUMP Command (Alpha Only) V7.3 The documentation for the OpenVMS debugger command ANALYZE/PROCESS_DUMP states that if you do not include the /IMAGE_PATH=directory-spec qualifier, the debugger looks for the debugger symbol table (.DSF or .EXE) file in the following directories: 1. In the directory that contains the dump file 2. Directory SYS$SHARE 3.
Programming Release Notes 6.9 Debugger 6.9.5 Enumeration Literals as Class Members V7.3 Previous versions of the debugger did not treat C++ enumeration literals as class members. This problem has been corrected. For example, given the following declaration, the debugger will match ’B::red’ and ’b.red’, and ’p->red’: struct B { enum colors { yellow, red, green, purple }; } b, *p; 6.9.6 Global Symbol Table Search V7.
Programming Release Notes 6.9 Debugger 6.9.11 Interrupting Program Execution in Compaq DECwindows Motif Interface V7.3 In Version 7.2 of the debugger, the STOP button in the DECwindows Motif interface and Ctrl/C in screen mode sometimes do not return control to the user. This problem has been corrected. 6.9.12 Nested Anonymous Unions V7.3 In previous versions of the debugger, nested anonymous unions in C++ led to incorrect symbolizations. For example, the following definition symbolized u.s as ’u.
Programming Release Notes 6.9 Debugger led to the following error: DBG> show SYMBOL/FULL C_Outer type C_Outer struct (C_Outer, 1 component), size: 1 byte contains the following members: %DEBUG-E-INTERR, debugger error in DBGDUMP\DBG$GET_SYMBOL_OFFSET or session corruption This problem has been corrected. 6.9.16 Inline Code V7.3 Previous versions of the debugger could fail when trying to set a breakpoint within a routine that is inlined within a program that is compiled with the /OPTIMIZED switch.
Programming Release Notes 6.9 Debugger 6.9.20 Nonunique COBOL Symbol Lookups (VAX Only) V7.3 In previous versions of the debugger, lookups of certain COBOL record components resulted in nonunique symbol errors. For example: DBG> SET MODULE B_COB DBG> EXAMINE D00_DIALLING_NO %DEBUG-I-NOUNIQ, symbol ’D00_DIALLING_NO’ is not unique record component A_COB\COMMON_DATA_FORMAT_WKSP.D00_CDF.CDF_WKSP.D00_DIALLING_NO record component B_COB\COMMON_DATA_FORMAT_WKSP.D00_CDF.CDF_WKSP.
Programming Release Notes 6.9 Debugger 6.9.23 Source View Update V7.3 In previous versions, the DECwindows Motif interface to the debugger did not correctly update the source view on a return step command from a subroutine call when the calling routine was in a different source module. This problem has been corrected. 6.9.24 SHOW SYMBOL IN Clause V7.3 The ability of the debugger to set modules dynamically has been improved. 6.9.25 Corrupted Stack Errors (Alpha Only) V7.
Programming Release Notes 6.10 Debugging Modes—Avoiding CPUSPINWAIT Bugchecks 6.10 Debugging Modes—Avoiding CPUSPINWAIT Bugchecks V7.1 The OpenVMS operating system has a number of special modes of operation designed to help you debug complex hardware and software problems. In general terms, these special modes enable an extra level of tracing, data recording, and consistency checking that is useful in identifying a failing hardware or software component.
Programming Release Notes 6.11 Hypersort (SORT/MERGE/CONVERT)—Alpha Only 6.11.5 Hypersort and VFC Files—Known Problem V7.3 Hypersort does not correctly calculate the byte offset for keys for VFC Format files. 6.11.6 Hypersort and /STATISTICS Working-Set Display—Known Problem V7.3 Hypersort overflows the working-set display in the /STATISTICS output for any working set that is 1,000,000 pages or larger. This is also a known problem with SORT32. 6.11.7 Hypersort and INSVIRMEM—Restriction V7.
Programming Release Notes 6.13 Librarian Utility—PGFLQUOTA Should Exceed 23000 (Alpha Only) To work around this problem, run the compression, data reduction, or data expansion operation in an account with a PGFLQUOTA process quota greater than 23000. In addition, ensure that your command procedures check the return status from the LIBRARY command. 6.14 Linker Utility The following sections describes release notes pertaining to the Linker Utility. 6.14.
Programming Release Notes 6.17 Mail Utility—Threads Restriction for Callable Mail Because callable mail context information is maintained on a per-process (rather than a per-thread) basis, multiple threads performing context-based processing must be synchronized so that only one mail context of a given type is active at once. Otherwise, one thread could corrupt another thread’s mail operations.
Programming Release Notes 6.19 OpenVMS Registry (Alpha Only) only the REG$M_CHANGENAME, REG$M_CHANGELASTSET, and REG$M_ CHANGESECURITY mask bits have any effect on which notifications are passed or filtered. The REG$M_CHANGEATTRIBUTES mask bit is currently not supported. For the most part, specifying the REG$M_CHANGENAME, REG$M_ CHANGELASTSET, and REG$M_CHANGESECURITY mask bits is equivalent to specifying the REG$M_CHANGEATTRIBUTES mask bit.
Programming Release Notes 6.20 POSIX Threads Library 6.20.2 Dynamic CPU Configuration Changes V7.3 Starting in OpenVMS Version 7.3, the POSIX Threads Library is sensitive to dynamic changes in the number of CPUs that are configured for a running multiprocessor Alpha system.
Programming Release Notes 6.20 POSIX Threads Library 6.20.5 Setting of the MULTITHREAD SYSGEN Parameter on NUMA Systems V7.3 When use of multiple kernel threads is enabled (by way of the LINK/THREADS_ ENABLE qualifier or the THREADCP command verb) for an image, the POSIX Threads Library monitors the apparent parallelism of an application and creates multiple kernel threads up to the number of CPUs available.
Programming Release Notes 6.21 Privileged Interfaces and Data Structures (Alpha Only) 6.21 Privileged Interfaces and Data Structures (Alpha Only) This section contains release notes concerning privileged code and data structures. 6.21.1 Per-Thread Security and Backward Compatibility V7.2 The security information previously stored in several data structures has moved to a new Persona Security Block (PSB) data structure, making the relevant fields in those structures obsolete in OpenVMS Version 7.2.
Programming Release Notes 6.
Programming Release Notes 6.21 Privileged Interfaces and Data Structures (Alpha Only) 6.21.3 Per-Thread Security Impacts Privileged Code and Device Drivers V7.2 The method used for attaching a security profile to the I/O Request Packet (IRP) has changed. In previous versions of OpenVMS, the address of the processwide Access Rights Block (ARB) security structure was copied directly into the IRP. Beginning with OpenVMS Alpha Version 7.
Programming Release Notes 6.22 Record Management Services (RMS) 6.22 Record Management Services (RMS) This section contains release notes pertaining to RMS. 6.22.1 Potential CONVERT-I-SEQ Error on CONVERT/NOSORT with Collated Key V7.3 This potential change in behavior is restricted to a CONVERT command that specifies both the /NOSORT qualifier and a collated key type on one of the keys in the output file.
Programming Release Notes 6.23 Run-Time Library (LIB$)—LIB$FIND_IMAGE_SYMBOL Signals Warning for Modules with Co 6.23 Run-Time Library (LIB$)—LIB$FIND_IMAGE_SYMBOL Signals Warning for Modules with Compilation Errors V7.1 LIB$FIND_IMAGE_SYMBOL may signal a warning (LIB$_EOMWARN) to indicate that the image being activated contains modules that had compilation warnings. A condition handler used with LIB$FIND_IMAGE_SYMBOL should probably handle this as a special case.
Programming Release Notes 6.24 Screen Management (SMG$) Facility Documentation • The description of routine SMG$SET_KEYPAD_MODE should contain this note: Note Changing the keypad mode changes the physical terminal setting. This is a global change for all virtual keyboards, not just the virtual keyboard specified by the keyboard-id argument. 6.25 Soft Affinity—Soft Affinity Disabled (Alpha Only) V7.3 In OpenVMS Version 7.
Programming Release Notes 6.26 SORT32 (SORT/MERGE/CONVERT) 6.26.4 SORT32 and /STATISTICS Working-Set Display V7.3 SORT32 overflows the working-set display in the /STATISTICS output for any working set that is 1,000,000 pages or larger. This is also a known problem with Hypersort. 6.27 System Services The following sections contain release notes pertaining to system services. All system services are documented in the OpenVMS System Services Reference Manual. 6.27.1 Performance API - $GETRMI V7.
Programming Release Notes 6.27 System Services 6.27.3 $PERSONA System Services: Default Privilege Change (Alpha Only) V7.2 The default behavior in assigning persona privileges has changed in OpenVMS Alpha Version 7.2. Prior to this release, a persona was created with the authorized privileges from the specified user’s UAF record as the default privileges. The user’s default privileges would be used only if the IMP$V_ ASSUME_DEFPRIV flag was set in the call to $PERSONA_CREATE.
Programming Release Notes 6.27 System Services 6.27.6 $SUSPND Behaves Incorrectly in a Cluster Environment VAX V6.0 Alpha V1.5 When the $SUSPND system service is called and the target process is on a different cluster node than that of the process calling the $SUSPND service, the kernel mode suspend flag (bit 0) is ignored. As a result, any suspend is treated as a supervisor-mode suspend. 6.27.7 $PERSONA Restrictions Removed (Alpha Only) V7.
7 Device Support on OpenVMS Systems This chapter contains release notes pertaining to OpenVMS device support on Alpha and VAX systems. Where appropriate, section headings indicate whether specific notes contain Alpha-specific or VAX-specific information. 7.1 Recompiling and Relinking OpenVMS Device Drivers The following sections contain release notes pertaining to recompiling and relinking OpenVMS device drivers. 7.1.1 Possible Per-Threads Security Impacts Alpha Device Drivers V7.2 Refer to Section 6.21.
Device Support on OpenVMS Systems 7.1 Recompiling and Relinking OpenVMS Device Drivers source changes to customer-written drivers, see the OpenVMS Alpha Guide to Upgrading Privileged-Code Applications. 7.2 Restriction: Parallel SCSI Support for Logical Unit Numbers V7.2 OpenVMS supports up to eight Logical Unit Numbers (LUNs) per target ID on a parallel SCSI bus. The SCSI-2 standard is limited to eight LUNs, but the SCSI-3 standard recently increased to 64 LUNs.
Device Support on OpenVMS Systems 7.4 Changes to the IO$_DIAGNOSE Function S2DGV$L_32DSCTMO S2DGV$L_64DSCTMO S2DGB$L_DISCPRIV Although not documented at the time, the PAD counts, S2DGV$L_32PADCNT and S2DGV$L_64PADCNT were included in this group. The implementation inadvertently conditionalized on the port’s ability to handle command queuing instead of S2DGB$V_TAGGED_REQ. The code has now been changed to conditionalize on S2DGB$V_TAGGED_REQ. The PAD counts are still included in this group.
Device Support on OpenVMS Systems 7.6 CRCTX Routines Enhanced (Alpha Only) • IOC$DEALLOC_CNT_RES • IOC$LOAD_MAP These routines have changed as follows: If you call IOC$DEALLOC_CRCTX with a valid CRCTX status (CRCTX$V_ ITEM_VALID set to 1), the service returns a bad status. If the SYSBOOT parameter SYSTEM_CHECK is set, the system will crash. This prevents users from deallocating a CRCTX when they have valid resources that have not been deallocated.
Device Support on OpenVMS Systems 7.8 New Values for Length Parameter in System Routines (Alpha Only) The two new length values (IOC$K_BYTE and IOC$K_WORD) allow byte and word data to be passed in right-aligned fashion. Table 7–1 shows the accepted values for the length parameter.
Device Support on OpenVMS Systems 7.8 New Values for Length Parameter in System Routines (Alpha Only) IOC$K_BYTE (hex 100) Right-Aligned Byte The byte is always in the right-most lane: +---+---+---+---+ | | | | X | +---+---+---+---+ bits <1:0> = 0,1,2,3 Note that the high-order byte contains unpredictable data and must be masked to operate correctly.
Device Support on OpenVMS Systems 7.10 Required Change in ISA_CONFIG.DAT on AlphaStation 200/400 The following table shows the changes to the device description block. Table 7–2 Changes to Device Description Block Before Version 7.1 After Version 7.1 [AUA0] NAME=AU NODE=3 DRIVER=SYS$MSBDRIVER IRQ=9 DMA=(0,1) PORT=(388:4.530:8) [AUA0] NAME=AU DRIVE=SYS$MSBDRIVER IRQ=9 DMA=(0,1) PORT=(388:4,530:8) NODE=3 Customers using SYS$MANAGER:ISA_CONFIG.DAT files should read Section 7.9. 7.
Device Support on OpenVMS Systems 7.11 Memory Holes on AlphaServer 4100 Systems Figure 7–1 Example Memory Diagram 0 512 MB memory daughter card pair 1fff.ffff 2000.0000 256 MB memory daughter card pair 2fff.ffff 3000.0000 256 MB hole 3fff.ffff 1GB=4000.0000 128 MB memory daughter card pair 47ff.ffff 4800.
Device Support on OpenVMS Systems 7.11 Memory Holes on AlphaServer 4100 Systems int dma_size; int pages; status = IOC$NODE_DATA (crb, IOC$K_DIRECT_DMA_SIZE, &dma_size); /* dma_size contains the number of megabytes. * convert number of megabytes to bytes. */ dma_size = dma_size * (1024 * 1024); /* Convert number of bytes to number of pages by * dividing by number of bytes per page. */ pages = dma_size / MMG$GL_PAGE_SIZE; 3. Compare the resulting number of pages with mmg$gl_maxpfn + 1. 4.
Device Support on OpenVMS Systems 7.14 AlphaStation 255: PCI Configuration Restriction 7.14 AlphaStation 255: PCI Configuration Restriction V7.1 The OpenVMS Alpha operating system does not support PCI option cards configured in PCI slot 0 on any AlphaStation 255 series systems. PCI slot 0 is the lowest physical PCI option slot on AlphaStation 255 series systems. The interrupt signal for this slot is shared with the built-in Ethernet port.
Device Support on OpenVMS Systems 7.17 OpenVMS Alpha SCSI Firmware Support 7.17.2 Required Firmware for Multihost Use of RZ26L and RZ28 Disks V6.2 If you install RZ26L or RZ28 disks on a multihost SCSI bus in an OpenVMS Cluster, the disk’s minimum firmware revision is 442. The following sections describe a procedure that can be used to update the firmware on some RZ26L and RZ28 drives. This procedure can only be used with drives that are directly connected to a SCSI adapter on a host system.
Device Support on OpenVMS Systems 7.18 OpenVMS Alpha SCSI Port and Class Drivers 7.18 OpenVMS Alpha SCSI Port and Class Drivers V6.2 The following sections describe OpenVMS Alpha SCSI class and port device driver restrictions. 7.18.1 Add-On SCSI Adapters V6.2 Version 6.2 and later of OpenVMS Alpha supports various add-on SCSI adapters. Compaq’s AlphaGeneration platforms typically support one or more integral SCSI adapters, with the option of installing additional add-on SCSI adapters.
Device Support on OpenVMS Systems 7.20 Stricter Requirement for Mode Page 01h on SCSI Tape Drives 7.20 Stricter Requirement for Mode Page 01h on SCSI Tape Drives V7.3 OpenVMS Alpha Version 7.3 has implemented stricter requirements for SCSI Mode Page 01h (the Read Write Error Recovery Page) for SCSI tape drives. These requirements help guard against possible data loss during write operations to SCSI tape, by defining the recovery actions to be taken in the event of deferred recoverable errors.
8 Interlocked Memory Instructions (Alpha Only) The Alpha Architecture Reference Manual, Third Edition (AARM) describes strict rules for using interlocked memory instructions. The Alpha 21264 (EV6) processor and all future Alpha processors are more stringent than their predecessors in their requirement that these rules be followed. As a result, code that has worked in the past, despite noncompliance, could fail when executed on systems featuring the 21264 processor and its successors.
Interlocked Memory Instructions (Alpha Only) 8.2 Using the Code Analysis Tool $ define DCL$PATH [] $ srm_check myimage.exe The tool supports wildcard searches. Use the following command line to initiate a wildcard search: $ srm_check [*...]* -log Use the -log qualifier to generate a list of images that have been checked. You can use the -output qualifier to write the output to a data file. For example, the following command directs output to a file named CHECK.DAT: $ srm_check ’file’ -output check.
Interlocked Memory Instructions (Alpha Only) 8.3 Characteristics of Noncompliant Code only in C or C++ programs that use LDx_L/STx_C instructions in assembly language code that is embedded in the C/C++ source using the ASM function, or in assembly language written in MACRO–32 or MACRO–64. In some cases, a branch was introduced between the LDx_L and STx_C instructions. This can be addressed by recompiling.
Interlocked Memory Instructions (Alpha Only) 8.4 Coding Requirements • Any branch that has a destination between an LDx_L and an STx_C • STx_C instructions that do not have a preceding LDx_L instruction This typically indicates that a backward branch is taken from an LDx_L to the STx_C Note that hardware device drivers that do device mailbox writes are an exception. These drivers use the STx_C to write the mailbox. This condition is found only on early Alpha systems and not on PCI-based systems.
Interlocked Memory Instructions (Alpha Only) 8.4 Coding Requirements To correct this code, the memory access to read the value of INDEX must first be moved outside the LDQ_L/STQ_C sequence. Next, the branch between the LDQ_L and STQ_C, to the label IS_CLEAR, must be eliminated. In this case, it could be done using a CMOVEQ instruction. The CMOVxx instructions are frequently useful for eliminating branches around simple value moves.
Interlocked Memory Instructions (Alpha Only) 8.6 Recompiling Code with ALONONPAGED_INLINE or LAL_REMOVE_FIRST Macros Note Source modules that call the EXE$ALONONPAGED routine (or any of its variants) do not need to be recompiled. These modules transparently use the correct version of the routine that is included in this release.
A Product Retirement Notices This appendix contains notifications about OpenVMS products that are no longer supported as of this release or that are slated for retirement. It also lists manuals that have been archived with this release. Freeware Once a product is retired, Compaq does not accept or act on problem reports posted against the product.
Product Retirement Notices A.3 Adobe Display PostScript Extension Support No Longer Available A.3 Adobe Display PostScript Extension Support No Longer Available V7.3 Support for the Display PostScript extension (XDPS) has been removed from DECwindows Motif Version 1.2-6. The XDPS extension and its associated files are no longer supplied by Compaq and are removed from the system during an upgrade.
Product Retirement Notices A.
Product Retirement Notices A.9 POLYCENTER Software Installation Utility: DECwindows Motif Interface Retired A.9 POLYCENTER Software Installation Utility: DECwindows Motif Interface Retired V7.2 The DECwindows Motif interface for the POLYCENTER Software Installation utility has been retired. All functions of the POLYCENTER Software Installation utility are still available from the DCL interface using the PRODUCT command. A.10 X.25 Client for OpenVMS Alpha Retirement (Alpha Only) V7.3 The X.
B Hardware Release Notes This appendix contains information specific to certain hardware products: • ALPHAbook 1 • AlphaServer 1000A • AlphaServer 2100 • AlphaServer 4100 • AlphaServer 8200 • AlphaServer 8400 • AlphaServer GS Series • AlphaStation 255 • DEC 7000 • DECwindows X11 Display Server • DIGITAL Modular Computing Components • RF73 and other RFnn DSSI Disk Devices B.1 ALPHAbook 1 (Alpha Only) V7.
Hardware Release Notes B.
Hardware Release Notes B.1 ALPHAbook 1 (Alpha Only) Note the following conventions: • – The default is either 3 (if a monitor is available) or 1 (if no monitor is available. – If you have not explicitly selected the display or the resolution, then 1024 x 768 CRT-only is the default when a monitor is detected. If no monitor is detected, then 800 x 600 LCD-only is selected. – If you explicitly select the display, then that selection takes precedence over any other size requests.
Hardware Release Notes B.1 ALPHAbook 1 (Alpha Only) B.1.5 PCMCIA Bus Support The following notes apply to the PCMCIA bus. Supported PCMCIA Cards OpenVMS support for the PCMCIA bus on the ALPHAbook 1 system is limited to the following cards: • 3Com EtherLink III (3C589C) • Megahertz 28.8 FAX/Modem (XJ2288) • Apex Data ClipperCom V.34 International Data/FAX Modem (011–20811) The OpenVMS operating system can configure a maximum of one Ethernet card and one FAX/Modem card.
Hardware Release Notes B.1 ALPHAbook 1 (Alpha Only) B.1.6 Audio Support The DECsound utility included with DECwindows Motif Version 1.2-3 does not support the sound processor on the ALPHAbook 1 system. Audio support is available on the OpenVMS Multimedia services kit, a separately licensed layered product available from Compaq. B.1.7 Keyboard Mapping The ALPHAbook 1 keyboard is an 88-key, PC layout keyboard. The following notes describe how to set up the keyboard and enable particular key functions.
Hardware Release Notes B.1 ALPHAbook 1 (Alpha Only) • Two keys are mislabeled. The KP_Subtract and KP_Add are engraved in grey on the minus ( - ) and plus ( + ) keys. However, the 0 (zero) and P keys actually provide the function for KP- and KP+, respectively. • NUMLOCK is generated by SHIFT-NUMLOCK, and KP_ENTER is generated by RIGHT-ALT-ENTER. • There is no way to generate directly RIGHT-ALT, RIGHT-COMPOSE, or LEFT-COMPOSE. You can provide the function of the compose key by pressing LEFT ALT-SPACE.
Hardware Release Notes B.1 ALPHAbook 1 (Alpha Only) B.1.8 OpenVMS Cluster Restrictions Due to controller limitations of the PCMCIA Ethernet card, Compaq recommends that you use the ALPHAbook 1 computer only as a satellite node in a cluster environment rather than as a cluster boot node. B.2 AlphaServer 1000A (Alpha Only) The following sections contain release notes pertaining to the AlphaServer 1000A computer. B.2.1 Bus Probe Algorithm Default V7.
Hardware Release Notes B.
Hardware Release Notes B.4 AlphaServer 4100 (Alpha Only)—EISA Configuration Utility (ECU) 3. Use the down arrow key to select Utilities. Then use either the right arrow or Enter key to highlight the first submenu entry, "Run ECU From Floppy..." The display is as follows: AlphaBIOS Setup Display System Configuration... Upgrade AlphaBIOS Hard Disk Setup... CMOS Setup... Install Windows NT >> Utilities About AlphaBIOS... F1=Help Run ECU From Floppy... OS Selection Setup... Run Maintenance Program...
Hardware Release Notes B.5 AlphaServer 8200 and AlphaServer 8400 (Alpha Only) B.5.2 Environmental Data Restrictions V7.1-1H1 On AlphaServer 8200 systems, the power regulators do not contain sensors for environmental conditions. Therefore, data cannot be reported in the thermal and power supply MIB groups of the DSM System subagent.
Hardware Release Notes B.8 DECwindows X11 Display Server (Alpha Only) B.8.3 Integrated Graphics Boards Supported V7.3 Under V7.3, support for graphics boards is fully integrated with the OpenVMS operating system. The following new boards are now supported: • Elsa GLoria (PowerStorm 4D10T) • OXYGEN VX1 • PowerStorm 300 • PowerStorm 350 B.9 DIGITAL Modular Computing Components (DMCC) (Alpha Only) This section contains release notes pertaining to DMCC. B.9.
Hardware Release Notes B.10 PowerStorm 300/350 PCI Graphics Controller Directory File Name [73.DOCUMENTATION.PS_TXT] P300_350_REL_NOTES.PS,TXT These documents, release notes, and installation guides are shipped with the Graphics cards. Starting with OpenVMS V7.3, the following parameter settings are not relevant for PowerStorm 300 and 350 graphics cards: MAXBOBMEM, MAXBOBS0S1, and MAXBOBS2. B.10.2 AlphaStation 255 PowerStorm Graphics Cards V7.
Hardware Release Notes B.11 RF73 and Other RFnn DSSI Disk Devices Table B–1 Supported Microcode Revision Levels Device Type Minimum Level with Supported Microcode RF31T T387E RF31T+ T387E RF35 T392D RF35+ T392D RF36 V427P RF73 T392D RF74 V427P To display the microcode revision level of your DSSI disk devices, perform the following steps: 1. Log in to the SYSTEM account or another account that has the CMKRNL, DIAGNOSE, and SYSPRV privileges. 2.
Hardware Release Notes B.11 RF73 and Other RFnn DSSI Disk Devices To update the microcode in your device, use the appropriate command for your device and platform from Table B–2. Caution Back up the disk before updating the microcode. Table B–2 Commands for Updating Microcode in Certain DSSI Disk Devices Device Type Platform Command RF35 Alpha $RUN SYS$ETC:RF35_T392F_DEC_ALPHA.EXE RF35 VAX $RUN SYS$ETC:RF35_T392F_DEC.EXE RF36 Alpha $RUN SYS$ETC:RF36_V427P_DEC_ALPHA.
Index A ACMS IPC-E-BCKTRNSFAIL error message, 5–1 Ada Run-Time Library AST procedure workarounds no longer needed, 6–3 text libraries with Ada declarations, 6–3 unexpected storage errors, 6–3 Adobe Display PostScript Extension support no longer available, A–2 Adobe Display PostScript not supported for DECwindows Motif, A–1 Advanced Server for OpenVMS, 3–1 upgrade path, 2–4 upgrade path for PATHWORKS users, 2–3 After-image journaling, 5–29 ALPHAbook 1, B–1 to B–7 Alpha Firmware, 4–2, 4–4 AlphaServer 1000A BU
Class Scheduler, 5–13 CLISYMTBL system parameter, 3–7 clock function, 6–4 Cluster compatibility kits, 2–1, 5–14 Cluster interconnects LANs as cluster interconects, 5–13 Clusters See OpenVMS Cluster systems COM for OpenVMS, 6–3 cluster restriction, 4–3 Compaq C++ compiler, consequences of noncompliant code, 8–1 Compaq C compiler, consequences of noncompliant code, 8–1 Compaq C RTL time zone rules, 3–3 Compaq C Run-Time Library See Compaq C RTL Compaq DCE for OpenVMS notes for existing users, 6–8 Compaq Open3
DECnet-Plus for OpenVMS, 2–1 external authentication requirement, 5–5 NET_CALLOUTS parameter, 5–5 DEC PL/I, 3–8 DECram version support, 3–5 DECwindows, 2–5 DECwindows Motif changes and enhancements Adobe Display PostScript not supported, A–1 problems and restrictions language variant availability, 3–7 system parameter values required for installation, 3–7 DECwindows pause screen unlock mechanism password validation, 5–5 DECwindows X11 display server graphics boards support, B–10 DEFPA adapter on AlphaServer
FREE_GBLPAGES system parameter, 3–7 FTP server, external authentication support, 5–4 G Galaxy, 5–7 Galaxy license enforcement, 4–1 GBLPAGES system parameter, 3–7 $GETRMI system service, 6–28 Gigabit Ethernet switch restriction, 5–21 Global section watchpoints, 6–10 symbol table search, 6–10 Graphics boards support, B–10 H HSD10 virtual disks, 5–35 HSZ70/HSZ80 multipath failover problem, 5–21 HSZ allocation class, multipath device naming, 5–19 Hypersort, 6–15 I IDE CD–ROM, 4–2 Installation and upgrade inf
MMOV$MSBDRIVER, 7–9 Monitor utility, compatibility kits, 5–14 MOP booting restriction, 5–9 Mount utility, compatibility kits, 5–14 MTH$ RTL executable image restrictions, 6–18 MultiNet, 3–7 Multipath devices volume rebuild problem, 5–20 failover HSZ70/HSZ80 problem, 5–21 Multipath HSG/HSZ disk partition restriction with volume shadowing, 5–34 MULTIPROCESSING system parameter, 6–15 N Name change BACKUP Help topic, 4–4 FDL Help topic, 4–4 MAIL Help topic, 4–4 NCS Help topic, 4–4 NCS Help topic name change, 4
POSIX for OpenVMS 1003.4a Draft 4 interface retirement, 6–20 POSIX Threads Library changes and enhancements application coding errors, 6–20 Dynamic CPU configuration, 6–20 POSIX 1003.
SYS$STARLET_C.TLB on VAX deleted by pre-Version 5.
