HP OpenVMS Version 8.4 Release Notes June 2010 This manual describes changes to the software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections. Revision/Update Information: This is a new manual. Software Version: OpenVMS Version 8.4 for Integrity servers OpenVMS Alpha Version 8.
© Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv 1 OpenVMS Software Installation and Upgrade Release Notes 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.7.1 1.7.2 1.7.3 1.7.4 1.7.5 1.7.6 1.7.7 1.7.7.1 1.8 1.8.1 1.8.2 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 HP Software Technical Support Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Application Compatibility Statement . . . . . . . . . . . . . . . . . . . . .
2.10 2.11 2.11.1 2.11.2 2.12 2.13 2.14 2.15 2.16 2.17 2.17.1 2.17.2 2.18 2.18.1 2.18.2 2.19 2.20 2.20.1 2.20.2 2.21 COBOL: Changes in I/O Run-Time Diagnostics and RMS Special Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . COM for HP OpenVMS (Alpha Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . COM for OpenVMS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP OpenVMS Linker Utility Manual Update . . . . . . . . . . . . . . . . . . . HP C++ Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP PCSI Utility Online help and Manual: $PRODUCT REGISTER VOLUME Syntax Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.18.3 iCAP Release Notes: GiCAP Functionality not Available . . . . . . . . . . . 3.18.4 POLYCENTER Software Installation Utility Developer’s Guide: PRODUCT Command Update . . . . . . . . . . . . . .
OpenVMS InfoServer and the Integrity servers on the Same LAN . . . EFI Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OpenVMS TCP/IP Provisioning Limitation . . . . . . . . . . . . . . . . . . . . . Limitation with Deploying OpenVMS on Multiple Target Servers Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.
4.16.1.9 Block Transfer XMIT Chaining . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16.1.10 LANCP for Downline Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16.1.11 Duplex Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16.1.12 Configuring a Node During Upgrade . . . . . . . . . . . . . . . . . . . . . . . 4.16.2 OpenVMS Cluster Support for Integrity VM . . . . . . . . . . . . . . . . . . . . 4.16.2.
. . . . . . . . . . . . . . 4–31 4–31 4–31 4–31 4–32 4–32 4–33 4–34 4–34 4–34 4–34 4–35 4–35 4–35 ...... 4–35 Symbolic Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C++ Run-Time Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process/Application Hangs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AST Delivery Clarification in Programs using POSIX Threads . . . . . . . . .
5.17.1 Secure Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.17.2 Installation and Initialization Considerations . . . . . . . . . . . . . . . . . . . 5.18 Debugging Modes: Avoiding CPUSPINWAIT Bugchecks . . . . . . . . . . . . . . 5.19 Delta/XDelta Debuggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.19.1 XDELTA Register Display Consideration (Integrity servers Only) . . . . 5.
Max Ident Length Change for Shareable Images in Map . . . . . . . . . . . Linkage Type Check for Shareable Images . . . . . . . . . . . . . . . . . . . . . Program Section Attribute ABS Ignored . . . . . . . . . . . . . . . . . . . . . . . Linker ACCVIOs when FP_MODE Literal Missing From Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.30.13 OpenVMS Integrity servers Object Module and Image File Information Currently Unavailable . . . . . .
6 Hardware Release Notes USB Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MP and BMC Console Restrictions (Integrity servers Only) . . . . . . . . . . . Input, Output, and Error Device Restriction . . . . . . . . . . . . . . . . . . . . Remapping Ctrl/H to the Delete Key . . . . . . . . . . . . . . . . . . . . . . . . . AlphaServer 2100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console Display . . . . . . . . . .
Dual-Controller HSGnn with Many LUNs Can Fail Under Heavy I/O Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.15 Open3D Graphics Licensing Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.16 PowerStorm 300/350 PCI Graphics Support for OpenVMS . . . . . . . . . . . . 6.17 RFnn DSSI Disk Devices and Controller Memory Errors . . . . . . . . . . . . . . 6.18 RZnn Disk Drive Considerations . . . . . . . . . . . . . . . . . . . .
Preface Intended Audience This manual is intended for all users of the HP OpenVMS for Integrity servers or HP OpenVMS Alpha Version 8.4 operating system. Read this manual before you install, upgrade, or use OpenVMS Version 8.4. Document Structure This manual contains the following chapters and appendix: • Chapter 1 contains release notes that pertain to upgrading or installing the OpenVMS Alpha operating system or installing the OpenVMS Integrity servers.
Related Documents For a list of additional documents that are available in support of this version of the OpenVMS operating system, see the HP OpenVMS Version 8.4 New Features and Documentation Overview manual. For additional information about HP OpenVMS products and services, see: http://www.hp.com/go/openvms Reader’s Comments HP welcomes your comments on this manual. Please send your comments or suggestions to: openvmsdoc@hp.
[] In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement. | In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required.
1 OpenVMS Software Installation and Upgrade Release Notes This chapter contains information that you must know before installing or upgrading to OpenVMS Version 8.4. Topics of interest to both Alpha and Integrity server users are covered first. Later sections group notes of interest to users of specific platforms. HP recommends that you read the following manuals before installing or upgrading OpenVMS Version 8.4: • HP OpenVMS Version 8.4 Release Notes (this manual) • HP OpenVMS Version 8.
OpenVMS Software Installation and Upgrade Release Notes 1.1 HP Software Technical Support Policy • New Feature Releases for OpenVMS contain new features, enhancements, and maintenance updates. The version number increases to the next decimal number (for example, from 8.2 to 8.3). Application impact: The release has not retired any published application programming interfaces (APIs).
OpenVMS Software Installation and Upgrade Release Notes 1.3 Obtaining Remedial Kits 1.3 Obtaining Remedial Kits Remedial kits for OpenVMS field test Version 8.4 will be made available in the field test website. 1.4 Networking Options V8.4 OpenVMS provides customers with the flexibility to choose the network protocol of their choice. Whether you require DECnet or TCP/IP, OpenVMS allows you to choose the protocol or combination of protocols that works best for your network.
OpenVMS Software Installation and Upgrade Release Notes 1.6 HP DECwindows Motif for OpenVMS 1.6 HP DECwindows Motif for OpenVMS V8.4 The following table lists the versions of DECwindows Motif supported on various platforms of the OpenVMS Version 8.4 operating system. Table 1–1 Supported Versions of DECwindows Motif OpenVMS Version DECwindows Motif Version OpenVMS Integrity servers Versions 8.3, 8.3-1H1, and 8.4 DECwindows Motif for OpenVMS Integrity servers Version 1.7 OpenVMS Alpha Version 8.
OpenVMS Software Installation and Upgrade Release Notes 1.7 OpenVMS Integrity server Users Restrictions Customers who used any earlier evaluation or field test kits should note the following important considerations: • The U160 adapter (A6829A) is not officially supported on OpenVMS Integrity servers Version 8.3 and later, and reached end-of-life in 2005. However, you can use this adapter for existing hardware configurations as long as the system remains as it is currently configured.
OpenVMS Software Installation and Upgrade Release Notes 1.7 OpenVMS Integrity server Users 1.7.4 Firmware for Integrity Servers V8.4 OpenVMS Integrity servers Version 8.4 was tested with the latest firmware for each of the supported Integrity servers. For the entry-class Integrity servers, HP recommends that use the most current system firmware. For information about updating the system firmware for entry-class Integrity servers, see the HP OpenVMS Version 8.4 Upgrade and Installation Manual.
OpenVMS Software Installation and Upgrade Release Notes 1.7 OpenVMS Integrity server Users ACPI Revision: 7.00 BMC Revision: 2.35 IPMI Revision: 1.00 SMBIOS Revision: 2.3.2a Management Processor Revision: E.02.29 " # ! The system firmware revision is 2.13. " The BMC firmware revision is 2.35. # The MP firmware revision is E.02.29. The HP Integrity rx4640 server contains Dual Hot Plug Controller (DHPC) hardware with upgradeable firmware.
OpenVMS Software Installation and Upgrade Release Notes 1.7 OpenVMS Integrity server Users The message means that the system cache (XFC) initialization has successfully adjusted the SYSGEN parameters MPW_HILIM and FREEGOAL to allow caching to be effective during the installation. You can continue with the installation. 1.7.6 Booting from USB or vMedia Devices V8.4 The %SYSTEM-I-MOUNTVER messages and the Universal Serial Bus Configuration Manager message are new to OpenVMS Version 8.
OpenVMS Software Installation and Upgrade Release Notes 1.8 OpenVMS Alpha Users Version 8.3 to V8.4 For Integrity servers: Version 8.2-1 to V8.3 Version 8.3 to V8.4 Version 8.3-1H1 to V8.4 If you are currently running OpenVMS Alpha Version 6.2x through 7.3, inclusive, you must first upgrade to Version 7.3-2, and then to Version 8.4. For details about OpenVMS operating system support, see the chart on the following website: http://h71000.www7.hp.com/openvms/openvms_supportchart.
OpenVMS Software Installation and Upgrade Release Notes 1.9 Kerberos for OpenVMS 1.9 Kerberos for OpenVMS V8.3 Before configuring or starting Kerberos, check the HP TCP/IP local host database to determine whether your hostname definition is the short name (for example, node1) or the fully qualified domain name (FQDN) (for example, node1.hp.com). If your host name definition is the short name, you must run TCPIP$CONFIG to change the definition to the fully qualified name.
OpenVMS Software Installation and Upgrade Release Notes 1.9 Kerberos for OpenVMS 3 - IE0 Menu (EIA0: TwistedPair 100mbps) I - Information about your configuration [E] - Exit menu Enter configuration option: 2 HP TCP/IP Services for OpenVMS Address Configuration Menu WE0 1.2.3.
OpenVMS Software Installation and Upgrade Release Notes 1.9 Kerberos for OpenVMS After you have a valid configuration, start Kerberos with the following command: $ @SYS$STARTUP:KRB$STARTUP.COM For more information, see the Kerberos for OpenVMS Installation Guide and Release Notes. 1.10 Modifying SYSTARTUP_VMS.COM V8.4 The startup command procedures for Encrypt and SSL are now called from the VMS$LPBEGIN-050_STARTUP.COM procedure.
OpenVMS Software Installation and Upgrade Release Notes 1.13 Converting the LANCP Device Database 1.13 Converting the LANCP Device Database V8.3 When you upgrade to OpenVMS Alpha Version 8.3 from OpenVMS Version 7.3-2, you might also need to convert the LAN device database to the Version 8.3 format if this is not automatically done by LANACP when LANACP is first run after the upgrade.
OpenVMS Software Installation and Upgrade Release Notes 1.15 Remove TIE Kit Before Upgrade 1.15 Remove TIE Kit Before Upgrade V8.2-1 The Translated Image Environment (TIE) has been integrated into OpenVMS Integrity servers Version 8.2–1. Refer to the HP OpenVMS Systems Migration Software web site for further information. http://www.hp.com/go/openvms/products/omsais If you have installed any version of the TIE PCSI kit (HP-I64VMS-TIE) on OpenVMS Integrity servers Version 8.2 or Version 8.
2 OpenVMS Associated Products Release Notes This chapter contains information about OpenVMS associated products. Notes specifically related to installation or upgrade issues of associated products are in Chapter 1. For notes about using compilers, linkers, and run-time library routines, see Chapter 5. 2.
OpenVMS Associated Products Release Notes 2.2 HP TCP/IP Services for OpenVMS 2.2 HP TCP/IP Services for OpenVMS V8.4 You must use HP TCP/IP Services for OpenVMS Version 5.7 after upgrading to OpenVMS Version 8.4. 2.3 NetBeans Version 5.5.1 Requires Latest JDK V8.4 NetBeans Version 5.5.1 for OpenVMS Alpha and OpenVMS Integrity servers is supported only on Java Platform, Standard Edition, Development Kit (JDK) v 1.4.2-7 or higher. Note JDK Version 6.0-1 for Integrity servers is not supported. 2.
OpenVMS Associated Products Release Notes 2.5 HP DCE for OpenVMS Restriction (Integrity servers Only) Workaround To install DCE, mount the OE DVD installation disk on the OpenVMS system and execute the DCE$INSTALL.COM procedure which is present under DCE_ I64032 folder. 2.6 XML-C Product Zip File V8.3-1H1 The XML-C product for OpenVMS for Integrity servers is delivered as a ZIP file that contains a self-extracting executable file.
OpenVMS Associated Products Release Notes 2.9 CMAP Files Added 2.9 CMAP Files Added V8.2 The following new CMAP files are provided in the OpenVMS Version 8.2 internationalization data kit. DECKANJI2000 GB18030 ISO8859-1-EURO UTF8-20 UTF8-30 2.10 COBOL: Changes in I/O Run-Time Diagnostics and RMS Special Registers V7.3 Because of the addition of Extended File Support in OpenVMS Alpha Version 7.
OpenVMS Associated Products Release Notes 2.13 DECforms Web Connector Version 3.0 (Alpha Only) 2.13 DECforms Web Connector Version 3.0 (Alpha Only) V7.3-1 If you already have DECforms installed, perform the following tasks to enable DECforms Web Connector V3.0 to run on OpenVMS Version 7.3-1 and higher: 1. Remove or comment out the following line: $ @SYS$COMMON:[JAVA$122.COM]JAVA$122_SETUP.COM from these command procedures in the FORMS$INSTALL_AREA directory: • FORMS_SMGR_STARTUP.
OpenVMS Associated Products Release Notes 2.15 FMS Kits Run-time kit: HPFMSRT025 FMS V2.5 is supported on OpenVMS V8.2 and later systems (Alpha and Integrity servers). 2.16 Graphical Configuration Manager (Alpha Only) The Graphical Configuration Manager (GCM) is included on the Layered Products CD that ships with the operating system. However, GCM is frequently updated. Check regularly for new versions of the software on the following web page: http://h71000.www7.hp.com/openvms/products/gcm/ 2.
OpenVMS Associated Products Release Notes 2.18 HP DECwindows Motif for OpenVMS 2.18.1 New Locales Added V8.2 The following new locales, which are used by localized DECwindows Motif software, have been added to the OpenVMS Version 8.2 internationalization data kit. iw_IL.utf-8 (Hebrew, Israel, UTF-8) ko_KR.utf-8 (Korean, UTF-8) zh_CN.utf-8 (Chinese, PRC, UTF-8) zh_HK.utf-8 (Chinese, Hong Kong, UTF-8) zh_TW.utf-8 (Chinese, Taiwan, UTF-8) 2.18.2 User-Written Transports not Supported V7.
OpenVMS Associated Products Release Notes 2.20 HP Pascal for OpenVMS Alpha Systems 2.20.1 HP Pascal: Version 5.8A (or later) Required to Create STARLET Library (Alpha Only) V7.3-2 Because of a change in OpenVMS Version 7.3-2, Pascal versions prior to V5.8A cannot create the STARLET library files during installation. Earlier versions of Pascal can install on OpenVMS Version 7.3-2 or later, if you answer "NO" to the option to create and install the STARLET library files.
3 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 HP OpenVMS Version 8.4 New Features and Documentation Overview. 3.1 SYS$GETTIM_PREC System Service Declaration V8.4 The SYS$GETTIM_PREC system service declaration is not present in the FORTRAN library FORSYSDEF.TLB.
General User Release Notes 3.4 Symbolic Links Implementation Changes For example, $ CREATE /SYMLINK="/SYS$HELP/CC_RELEASE_NOTES.PS" RELNOTES.PS $ DIR /SIZE /NOSYMLINK RELNOTES.PS Directory SYS$SYSROOT:[SYSMGR] RELNOTES.PS;1 209 Total of 1 file, 209 blocks. 3.4.2 Audit Alarms Fixed V8.4 With the previous implementation of symlinks, when commands such as $DIR attempted to list a directory, it resulted in audit alarms if the user did not have permissions on the target of a given file.
General User Release Notes 3.6 SWB V1.1-12 Installation Warnings 3.6 SWB V1.1-12 Installation Warnings V8.4 SeaMonkey Version 1.0 is built based on the Mozilla Version 1.8b1 code. When you install SWB Version 1.1-12 on an OpenVMS server that already has SWB Version 1.7-13 installed, you will see the following warning message: %PCSI-W-VERLOW, you have selected a lower version of an installed product -PCSI-W-VERINS, the installation of product HP I64VMS CSWB V1.
General User Release Notes 3.7 Ctrl/P at the Console Does not Always Work Also, note that if XDELTA or the System Code Debugger has been loaded when the system was booted, Ctrl/P is not affected. Entering Ctrl/P will cause the XDELTA prompt to be displayed, for example: Console Brk at 807CF3D2 on CPU 0 807CF3D2! cmp4.lt p0, p6 = 3F, r4 (New IPL = 3) 3.8 Installing Oracle Database 10g Release 2 for OpenVMS Fails V8.
General User Release Notes 3.9 Serial Port Enumeration There are two possible serial ports that can be selected as the primary console, the iLO and the Baseboard Management Console (BMC). Whichever is selected as primary console will be expressed as OPA0 by OpenVMS; the other will be either TTA0 or TTB0 if the system has an additional serial port. The following list describes these abbreviations and their definitions. Abbreviation Definition MP Serial port of the iLO MP.
General User Release Notes 3.9 Serial Port Enumeration OpenVMS Serial Port Name Primary Console Port MP BMC AP rx3600 rx6600 MP (optional) BMC VGA (optional) OPA0 NC NC TTA0 OPA0 TTA0 OPA0 rx2660 MP VGA (optional) OPA0 NC NA TTA0 TTA0 OPA0 rx8620 MP VGA OPA0 NC NA NA OPA0 BL860c MP VGA OPA0 NC NA NA OPA0 Platform VGA 3.10 Old Firmware Cannot Translate Messages Written to the System Event Log 8.3-1H1 Upon installation, OpenVMS Version 8.
General User Release Notes 3.11 TZ Function in C RTL 3.11 TZ Function in C RTL V8.3-1H1 The TZ logical name or DCL symbol is used by the C Run-Time Library (C RTL) to define the time zone to be used in certain C program time-related functions. (For more information about TZ, its use, and specific functions, see the C Run-Time Library documentation.) The TZ logical name or DCL symbol has been used by the C Run-Time Library since Version 7.3 of OpenVMS. However, with Version 8.3, there has been a change.
General User Release Notes 3.14 OpenVMS Freeware CDs For additional information about the Freeware, refer to the FREEWARE_README.TXT files. After the appropriate device is mounted, you can access the kit directories directly using standard DCL commands, such as DIRECTORY and COPY. Omnibus text files containing submission abstracts and other materials are available in the [FREEWARE] directory on each disk. The [FREEWARE]FREEWARE.COM Freeware menu system interface has been removed from Freeware 8.
General User Release Notes 3.15 DCL Commands For more information about enabling or disabling XFC while mounting a volume, see the HP OpenVMS Version 8.4 New Features and Documentation Overview. 3.16 DECmigrate Not on Open Source Tools CD V8.2 The OpenVMS Migration Software for VAX to Alpha (DECmigrate) is not included on the Open Source Tools CD shipped with the OpenVMS Version 8.2 distribution media. The software kit was included on the media for OpenVMS Version 7.3-2.
General User Release Notes 3.18 Documentation Corrections 3.18 Documentation Corrections The following sections describe corrections and additions to various manuals in the OpenVMS documentation set. 3.18.1 HP OpenVMS Linker Utility Manual Update V8.4 3.18.1.1 HP C++ Examples In section 2.6.2, the following should be appended to point 7: Note that on Integrity servers, you can use either the CXXLINK command or invoke the OpenVMS Linker to combine your object modules into one executable image.
General User Release Notes 3.18 Documentation Corrections 3.18.4 POLYCENTER Software Installation Utility Developer’s Guide: PRODUCT Command Update V8.4 In the parameters section, the producer description should be as follows: Indicates the legal owner of the software product. This parameter must be either a double quoted or an unquoted string. 3.18.5 HP OpenVMS System Manager’s Manual Update V8.4 The following corrections pertain to the HP OpenVMS System Manager’s Manual, Volume 1: Essentials. 3.18.5.
General User Release Notes 3.18 Documentation Corrections $ SHOW DEVICES/FULL DG Disk $1$DGA5001: (CEAGLE), device type HSV110, is online, mounted, file-oriented device, shareable, device has multiple I/O paths, served to cluster via MSCP Server, error logging is enabled.
General User Release Notes 3.18 Documentation Corrections I/O paths to device 5 Path PGA0.5000-1FE1-0015-22AC Error count Path PGA0.5000-1FE1-0015-22A9 Error count Path PGB0.5000-1FE1-0015-22A8 Error count Path PGB0.5000-1FE1-0015-22AD Error count Path MSCP (CLETA). Error count (CEAGLE), primary path. 0 Operations completed (CEAGLE). 0 Operations completed (CEAGLE), current path. 0 Operations completed (CEAGLE). 0 Operations completed 0 Operations completed 0 0 0 0 0 3.18.5.
General User Release Notes 3.18 Documentation Corrections 3.18.5.4 New Extended File Specifications Characteristics In section 10.1.2.1, the SHOW DEVICE command in the "Be Aware of Volume Structure" notes displays the message similar to the following: $ SHOW DEVICE DKA500:/FULL Disk AABOUT$DKA500:, device type DZ25 Disk, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable. Error count 0 Operations completed 155 . . .
General User Release Notes 3.18 Documentation Corrections Examples of TRADITIONAL and EXTENDED styles on an ODS-2 volume: Disk AABOUT$DKA200:, device type RZ25 Disk, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable. Error count 0 Operations completed 232 . . . Volume Status: ODS-2, [1] subject to mount verification, file high-water marking, write-back caching XQP enabled, write-through XFC caching enabled. $ SET PROCESS /PARSE_STYLE=TRADITIONAL [2] $ OPEN /WRITE FILE z.
General User Release Notes 3.18 Documentation Corrections If required to boot an Integrity servers system from a disk created through an image restore operation, you need to follow one of the method described below to update the GUID signature of the disk: • Use the following procedure to add or validate the boot options: $ @SYS$MANAGER:BOOT_OPTIONS.COM • Use the following command to update the boot block: $ SET BOOTBLOCK /INTEGRITY :[VMS$COMMON.SYS$LDR]SYS$EFI.
General User Release Notes 3.18 Documentation Corrections With this feature, after the volume is mounted, you can modify the XFC caching attributes dynamically without dismounting and mounting the volume again. Use... To...
General User Release Notes 3.18 Documentation Corrections 3.18.7 Documentation Error: LCKMGR_CPUID System Parameter V8.3 The OpenVMS Performance Management manual contains several references to the system parameter LCKMGR_CPUID as LOCKMGR_CPU. This latter reference is incorrect and will be corrected the next time the manual is updated. 3.18.8 MMG_CTLFLAGS: Documentation Error V8.
General User Release Notes 3.19 HP OpenVMS DELTA/XDELTA Debugger Manual Update 3.19.1.1 /REMOVE Qualifier Correction In Section 4.8.2.3 of the HP OpenVMS Version 8.2 New Features and Documentation Overview, the description of the enhanced library /REMOVE qualifier is incorrect. The correct information is as follows: The /REMOVE qualifier has been enhanced for the Integrity servers Librarian utility. The format now allows you to specify the module instance of the symbol to be removed.
General User Release Notes 3.19 HP OpenVMS DELTA/XDELTA Debugger Manual Update if ( (status & 1) == 1 ) status = lbr$put_end ( library_index ) ; To avoid making several calls to LBR$PUT_RECORD, a new library routine, LBR$PUT_MODULE, has been created. 3.19.2 HP OpenVMS RTL Library (LIB$) Manual Corrections V8.2-1 The following sections provide additions and corrections to Version 8.2 of the HP OpenVMS RTL Library (LIB$) Manual. 3.19.2.
General User Release Notes 3.19 HP OpenVMS DELTA/XDELTA Debugger Manual Update • LIB$I64_GET_CURR_INVO_CONTEXT • LIB$I64_GET_CURR_INVO_HANDLE • LIB$I64_GET_INVO_CONTEXT • LIB$I64_GET_INVO_HANDLE • LIB$I64_GET_PREV_INVO_CONTEXT • LIB$I64_GET_PREV_INVO_HANDLE For additional information about these routines, refer to the HP OpenVMS Calling Standard. 3.19.4 HP OpenVMS System Manager’s Manual: IPC Commands Restriction V8.2-1 Section 9.
General User Release Notes 3.22 Duplex-Mode Mismatch Errors 3.22 Duplex-Mode Mismatch Errors V8.3 A duplex-mode mismatch condition occurs when a LAN device is operating in fullduplex mode and the other end of the cable, typically a switch port, is operating in half-duplex mode. The reverse is also true.
4 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 HP OpenVMS Version 8.4 New Features and Documentation Overview. 4.1 SYS$TIMEZONE_RULE Logical Replaces Hyphen (-) with Caret (^) V8.4 Starting from Version 8.2 onwards, SYS$TIMEZONE_RULE logical is modified to replace the ’-’ character with the ’^’ character.
System Management Release Notes 4.2 Issues with Time Zone Configuration Workaround Deassign the SYS$DST_DELTA_TIME logical, when the error message appears on the system. $ DEASSIGN/EXECUTIVE_MODE/SYSTEM SYS$DST_DELTA_TIME 4.3 OpenVMS as a Guest Operating System on Integrity VM OpenVMS Version 8.4 now supports HP Virtualization and can be installed as a guest operating system on HP Integrity Virtual Machines (Integrity VM).
System Management Release Notes 4.3 OpenVMS as a Guest Operating System on Integrity VM Examples In the following examples, the image PUNISH_SHR.EXE is a protected shareable image that uses $CMKRNL to execute privileged hardware instructions. The image PUNISH_MAIN.EXE is an executable image that calls routines in PUNISH_SHR.EXE. The output is as seen at the guests MP console in each case. a.
System Management Release Notes 4.3 OpenVMS as a Guest Operating System on Integrity VM ============================================================================= This problem occurs when VM Monitor runs out of memory to allocate for guests. The workaround for this problem is to restart VM Monitor by entering the following commands on the Host: # /sbin/init.d/hpvm stop # /sbin/init.d/hpvm start This problem will be fixed in a future version of Integrity VM. 4.3.
System Management Release Notes 4.4 Provisioning OpenVMS Using HP SIM 4.4.2 System Firmware V8.4 The system firmware version of BL860c and BL870c servers must be at 4.21. The system firmware version of rx3600 and rx6600 servers must be at 4.11. 4.4.3 Provisioning Multiple Servers V8.4 • HP SIM provisioning using InfoServer can provision up to eight servers simultaneously. • HP SIM provisioning using vMedia can provision only one server at a time. 4.4.
System Management Release Notes 4.4 Provisioning OpenVMS Using HP SIM 4.4.10 Limitation with Deploying OpenVMS on Multiple Target Servers Simultaneously V8.4 There is a known issue with the TFTP server on Infoserver, which may prevent deploying OpenVMS Version 8.4 simultaneously on two or more target servers when using InfoServer booting with memory disk. In this scenario, InfoServer booting on the target server reports network errors when loading the memory disk similar to the below trace.
System Management Release Notes 4.5 Insight Dynamics - Virtual Server Environment for OpenVMS Workaround 1. Click Tools –> VSE Management.... The Virtualization Manager page appears. 2. Select OpenVMS guest. 3. Select Tools –> System Information –> System Page. The System Page... appears. 4. Select the Tools & Links tab on the System Page, and then select Edit System Properties. The Edit System Properties page appears. 5.
System Management Release Notes 4.5 Insight Dynamics - Virtual Server Environment for OpenVMS • Virtual Connect Enterprise Manager (VCEM) • Partition Manager • BladeSystem Integrated Manager • GiCAP Group Manager • Virtual Machines Manager • Insight Power Manager (IPM) • VSE troubleshooting for OpenVMS Managed Nodes - This refers to ’Check VSE CMS to Managed Node Communication...’ and ’Check VSE Managed Node Configuration...’ options under ’Diagnose’ menu -> ’Troubleshoot VSE Management....
System Management Release Notes 4.6 Performance Enhancements WBM_MSG_LOWER is the threshold used to determine if a switch should occur to single message mode, when operating in buffered message mode. If WBM_ MSG_LOWER or fewer SetBit operations are done in a 100 millisecond window, the messaging mode will be switched to single mode. The default value is 20. 4.6.1.3 Asynchronous SetBit Messages V8.4 There can be multiple master bitmap nodes for a shadow set.
System Management Release Notes 4.6 Performance Enhancements 4.6.4 Image Activation (Integrity servers Only) During image activation and over the life of the image, paging IO brings pages of the image into memory. On Integrity server systems, an I-cache flush need to be performed on these pages in case the page has code that is executed. This resulted on the I-cache flush occurring on many pages that would never be executed.
System Management Release Notes 4.9 PAGED_LAL_SIZE New System Parameter 4.9 PAGED_LAL_SIZE New System Parameter PAGED_LAL_SIZE sets the maximum size, in bytes, to use the page dynamic pool lookaside lists. 4.9.1 Paged Pool Lookaside Lists V8.4 Paged dynamic pool now allows the use of lookaside lists to increase system performance in some cases. It is controlled by SYSGEN parameter PAGED_LAL_ SIZE and is off (0) by default.
System Management Release Notes 4.11 Configuring SAS Tape Drives 4.11 Configuring SAS Tape Drives V8.4 SAS tape drives must be named and configured using the same commands that are used to configure Fibre Channel tape drives. For more information, see the section 7.5 "Fibre Channel Tape Support" in the Guidelines for OpenVMS Cluster Configurations. 4.12 External SAS Disk Device Naming V8.
System Management Release Notes 4.13 External Authentication 4.13.2 Integrity servers External Authentication Support V8.2 The Advanced Server for OpenVMS V7.3A ECO4 (and later) product kit contains standalone external authentication software for Integrity servers in an OpenVMS cluster.
System Management Release Notes 4.13 External Authentication Note Do not increase the number of threads on Integrity servers. Increasing the number of threads on Integrity servers might lead to ACME_SERVER process crash and login failures. 4.14 Itanium Primary Bootstrap (IPB) Fails to Find the Valid Dump Devices V8.
System Management Release Notes 4.16 OpenVMS Cluster Systems 4.16.1.3 Alpha Satellite Node Requires LAN Channels With Disk Server V8.4 Alpha satellite boot fails in an IP only environment. That is, while booting an Alpha satellite, if all the nodes, including the boot servers, are using only IP channels for cluster communication, the satellite boot fails with the following message: cluster-W-PROTOCOL_TIMEOUT, NISCA protocol timeout %VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server 4.
System Management Release Notes 4.16 OpenVMS Cluster Systems $ mc scacp show ip NODEG PEA0 Device Summary 16-FEB-2009 12:29:15.92: Device Errors + Mgt Buffer MgtMax Line Total Current Device Type Events Status Priority Size BufSiz Speed Pkts(S+R) IP Address ------ --------- ------------- ----- ------ ----- --------- ----------IE0 184 Run Online 0 1394 0 N/A 1419711 15.146.235.222 XChain_Disabled 4.16.1.10 LANCP for Downline Load V8.
System Management Release Notes 4.16 OpenVMS Cluster Systems 4.16.3 Mixed Platform Support V8.2 • A supported production cluster containing an Integrity servers cannot include a VAX system. VAX systems can be included in these clusters for the purposes of development and migration with the understanding that any problems arising from the existence of VAX systems in these clusters will result in the need for either the VAX or Integrity servers to be removed.
System Management Release Notes 4.17 Mixed-version Cluster Compatibility of a Six-member Shadowset • Once the shadowset has been enabled to use "Extended Memberships" shadowing feature, the characteristic is maintained even if the membership is reduced to less than four members. The characteristic is retained until the shadowset is dismounted clusterwide. • This shadowing feature is not ported onto OpenVMS VAX.
System Management Release Notes 4.19 WBEM Services and WBEM Providers for OpenVMS 4.19.3 Based on OpenPegasus 2.9 WBEM Services for OpenVMS Version 2.9 is based on the OpenPegasus 2.9 code stream of The Open Group’s Pegasus open source project. 4.19.4 Supports nPartitions and iCAP On cell-based systems, Version 2.0 supports local nPartitions and iCAP providers. Only the functions and capabilities needed by these providers are supported. 4.19.5 Restart cimserver.
System Management Release Notes 4.
System Management Release Notes 4.21 Monitor Utility Changes 4.21.2 Version-to-Version Compatibility of MONITOR Data Because the body of data MONITOR collects can change at each release, it is not always possible to view MONITOR data collected in one version on a different version. The level of compatibility between releases depends on whether you examine recorded binary data from a file (that is, playback) or live data from another cluster node.
System Management Release Notes 4.22 System Parameters GH_RES_CODE has the AUTOGEN and FEEDBACK attributes. 4.23 SYS$LDDRIVER Restriction V8.3-1H1 SYS$LDDRIVER.EXE is a freeware pseudo device driver that allows OpenVMS operating system to create virtual disks. For OpenVMS Version 7.3-1 and succeeding versions, this driver was placed in SYS$COMMON:[SYS$LDR] to support the creation of the source virtual disk for mastering a CD or DVD using CDRECORD or COPY/RECORDABLE_MEDIA.
System Management Release Notes 4.26 SCACP Error Counter Reports Retransmit Errors exist on the LAN devices that the PEdriver uses. If there are retransmits and no devices errors, then the PEA0: device errors are likely retransmits and not actual errors. 4.27 Virtual Connect The following section pertain to Virtual Connect. 4.27.1 Failover and RECNXINTERVAL V8.3-1H1 RECNXINTERVAL may have to be increased above the default of 20 to allow time for Virtual Connect Manager failovers.
System Management Release Notes 4.30 Recovering From System Hangs or Crashes (Integrity servers Only) If XDELTA is loaded, pressing Ctrl/P causes the system to enter XDELTA. The system displays the instruction pointer and the current instruction.
System Management Release Notes 4.33 EDIT/FDL: Fixing Recommended Bucket Size OpenVMS Version 7.3 or higher modifies the algorithms for calculating the recommended bucket size to suggest a more reasonable size when the disk cluster is large. 4.34 Using EFI$CP Utility not Recommended V8.2 The OpenVMS EFI$CP utility is presently considered undocumented and unsupported. HP recommends against using this utility.
System Management Release Notes 4.36 Cluster Compatibility Patch Kits Table 4–2 Patch Kits Required for Cluster Compatibility Facility Patch Kit File Name OpenVMS Alpha Version 7.3-2 Update kit with most patch kits except those listed in this section VMS732_UPDATE-V0600. C RTL VMS732_ACRTL-V0100 Drivers VMS732_DRIVER-V0200 PCSI VMS732_PCSI-V0100 OpenVMS Alpha Version 8.2 VMS82A_UPDATE-V0200 DECnet-Plus for OpenVMS Alpha ECO1 DNVOSIECO01_V821 OpenVMS Integrity servers Version 8.
System Management Release Notes 4.36 Cluster Compatibility Patch Kits Table 4–2 Patch Kits Required for Cluster Compatibility Facility Patch ID OpenVMS Alpha Version 7.3-2 Update kit with most patch kits except those also listed in this section OpenVMS VAX Version 7.
System Management Release Notes 4.36 Cluster Compatibility Patch Kits Producers of such software can now modify their software using DDT Intercept Establisher routines introduced in OpenVMS Alpha Version 7.3-2. For more information about these routines, refer to the HP OpenVMS Alpha Version 7.3–2 New Features and Documentation Overview manual.
System Management Release Notes 4.36 Cluster Compatibility Patch Kits Workarounds If excessively frequent connection moves are observed, you can use one of the following workarounds: • You can use SCACP or Availability Manager to assign a higher priority to the circuit, or the port you wish to be used, thus overriding automatic connection assignment and moving.
System Management Release Notes 4.37 OpenVMS Galaxy (Alpha Only) 4.37.1 Galaxy Definitions V8.2 Because the HP OpenVMS Alpha Partitioning and Galaxy Guide is not being updated for this release, this note provides improved definitions of the word Galaxy, which depends on context. Table 4–3 Galaxy Definitions Galaxy as a: Functions this way: License Is required to create and run multiple instances of OpenVMS in a single computer.
System Management Release Notes 4.38 Multiple nPartitions on Cell-based Systems 4.38.3 Galaxy on ES40: Turning Off Fastpath Permanent Restriction When you implement Galaxy on an AlphaServer ES40 system, you must turn off Fast Path on instance 1. Do this by setting the SYSGEN parameter FAST_PATH to 0 on that instance. If you do not turn off Fastpath on instance 1, I/O on instance 1 will hang when instance 0 is rebooted. This hang will continue until the PCI bus is reset and instance 1 rebooted.
System Management Release Notes 4.40 System Parameters • MMG_CTLFLAGS • MULTITHREAD • NISCS_MAX_PKTSZ • NISCS_PORT_SERV • SECURITY POLICY The following new parameters replace the preceding ones: • SMP_CPU_BITMAP • IO_PRCPU_BITMAP For more information about these new system parameters, see the HP OpenVMS System Management Utilities Reference Manual or online help. 4.40.3 System Parameter Changes V8.3 The following system parameters are changed in OpenVMS Version 8.3.
System Management Release Notes 4.41 Terminal Fallback Facility To start TFF, invoke the TFF startup command procedure located in SYS$MANAGER, as follows: $ @SYS$MANAGER:TFF$SYSTARTUP.
System Management Release Notes 4.42 User Environment Test Package (Integrity servers Only) • The device phase currently does not complete execution due to an access violation. • The DECnet phase runs fine. The cluster phase is still being tested. It appears to execute properly, but there are some concerns, and the output does not show other system names properly. 4.
System Management Release Notes 4.44 Analyze Utility for OpenVMS 4.44.3 System Version Array Formatted in Dynamic Segment System version data is in the dynamic segment. Previously, if you selected the dynamic segment (either by segment number, or with the ALL or DYNAMIC keyword), the system version array was not shown. Information about the system version array was only shown in the summary. This problem is corrected in OpenVMS Version 8.3-1H1.
5 Programming Release Notes This chapter provides release notes about application and system programming on OpenVMS systems. 5.1 Symbolic Debugger V8.4 On OpenVMS Alpha Version 8.4, when you set breakpoints the debugger will not be able to differentiate between FORTRAN functions and declared variables of the same name in different compilation unit. 5.2 C++ Run-Time Library V8.3-1H1 Problems corrected in OpenVMS Version 8.
Programming Release Notes 5.2 C++ Run-Time Library int main() { cxxl$set_condition(pure_unix); try { generateACCVIO(); } catch(...) { puts("caught"); } } Note To use this new functionality you must have a new version of cxx_exception.h, which is included in the CXXL$ANSI_DEF.TLB file provided with the Version 7.3 compiler (or higher).
Programming Release Notes 5.2 C++ Run-Time Library information, see the Apache tracker for the issue STDCXX-397 at http://issues.apache.org/jira/browse/STDCXX-397 The problem has been fixed. However, for some input sequences, the fix can change the behavior of std::sort with regard to the relative order in which elements that have equivalent ordering are placed into the sorted sequence.
Programming Release Notes 5.4 AST Delivery Clarification in Programs using POSIX Threads Also, note that much of the material in Section B.12.5 of the Guide describes a possible future version of OpenVMS. The description of generalized "per-thread" or thread-targeted ASTs represents possible future enhancements to the operating system. In all OpenVMS releases to date, however, user-mode ASTs are treated as if they are directed to the process as a whole. 5.5 RMS $PARSE Validation of Directory Files V8.
Programming Release Notes 5.
Programming Release Notes 5.9 Privileged Programs may Need a Recompile (Alpha Only) 5.9 Privileged Programs may Need a Recompile (Alpha Only) V8.2 OpenVMS Alpha Version 8.2 is a major version release in which a number of privileged data structures have changed. It may be necessary to recompile and relink privileged applications linked with /SYSEXE that refer to internal OpenVMS data structures or routines.
Programming Release Notes 5.10 Privileged Data Structures Updates 5.10.1 KPB Extensions V8.2 Prior versions of OpenVMS supported the use of KPBs for kernel mode above IPL 2. To make the transition to Integrity servers easier, usage of KPBs has been expanded for use in outer modes and all IPLs. This Alpha and Integrity servers change allows certain code that previously had private threading packages to make use of KPBs on both Alpha and Integrity servers.
Programming Release Notes 5.10 Privileged Data Structures Updates 5.10.5 UCB/DDB Updates V8.2 A number of updates have been made to the UCB and DDB structures. The list of UCBs associated with a DDB is currently a singularly linked list. When creating and deleting a UCB, this list must be walked until the appropriate location is found. For OpenVMS Version 8.2, UCBs are now linked to the DDB with a double linked list.
Programming Release Notes 5.10 Privileged Data Structures Updates Device drivers that create or clone copies of IRPs to facilitate multiple I/O operations per request, and subsequently pass the copies to the I/O subsystem for postprocessing, must make code changes to account for the extra references to the PSB in these additional IRPs. This is done by passing the PSB address located in the copied IRP to the NSA_STD$REFERENCE_PSB routine.
Programming Release Notes 5.10 Privileged Data Structures Updates For performance reasons, the IPL is not verified if SYSTEM_CHECK is set to zero (the default). Incorrect code may cause the system to hang if a reschedule to another CPU occurs during execution of these routines from process context (for example, below IPL$_RESCHED). 5.11 Applications Using Floating-Point Data V8.
Programming Release Notes 5.11 Applications Using Floating-Point Data If you encounter problems with event breakpoints, switch to pthread events (SET EVENT_FACILITY pthread) as a workaround. Note that not all Ada events have an equivalent in the pthreads facility. 5.11.3 C++ Language Issues (Integrity servers Only) V8.3 Condition: The debugger does note support debugging C++ programs compiled with /OPTIMIZE. Workaround: Compile C++ programs with /NOOPTIMIZE. 5.12 Ada Compiler(Integrity servers Only) V8.
Programming Release Notes 5.15 C Run-Time Library 5.15.1 C RTL TCP/IP Header File Updates V8.4 The C RTL ships header files for users to call TCP/IP. C RTL places the headers into the C RTL header library (DECC$RTLDEF.TLB). New header files are added, as appropriate for new features in TCP/IP. SCTP.H SCTP_UIO.H These header files provide Stream Control Transmission Protocol (SCTP) support. For more information on SCTP, see the HP TCP/IP Services for OpenVMS Version 5.7 Release Notes. 5.15.
Programming Release Notes 5.15 C Run-Time Library In OpenVMS Version 8.3, changes are made to to make sure the C RTL selects the appropriate prefixing for the listed functions. 5.15.4 Header File Makes *_r Non-ANSI Functions Visible V8.3 The C RTL functions ctime_r, gmtime_r, and localtime_r defined in the X/Open specification are not in the ISO/ANSI C standard and should not be visible when compiling only for ANSI compliance. Previously in the C RTL, they were visible.
Programming Release Notes 5.16 Calling Standard and Rotating Registers (Integrity servers Only) Previously, the supplemental access routines LIB$I64_GET_FR, LIB$I64_SET_ FR, LIB$I64_GET_GR and LIB$I64_SET_GR (see Section 4.8.4 in the HP OpenVMS Calling Standard) improperly interpreted their register number parameters without applying an adjustment for the effects of the register rename base and rotating size registers. This error is corrected. 5.
Programming Release Notes 5.17 Common Data Security Architecture (CDSA) Considerations cleanly and could create other undesirable effects. An attempt to remove CDSA will result in a message similar to the following: The following product has been selected: HP I64VMS CDSA T2.4-315 Layered Product Do you want to continue? [YES] %PCSI-E-HRDREF, product HP I64VMS CDSA T2.4-315 is referenced by HP I64VMS OPENV MS X8.4-C42 The two products listed above are tightly bound by a software dependency.
Programming Release Notes 5.20 File Applications: Corrections to Guide to OpenVMS File Applications 5.20 File Applications: Corrections to Guide to OpenVMS File Applications Permanent Correction The following corrections will be made to the Guide to OpenVMS File Applications if this manual is revised in the future. • Table 1-4 is potentially confusing. In the comparison of file formats, directory limitations are listed as 256 for ODS-2 and ODS-5 file formats.
Programming Release Notes 5.21 HP BLISS Compiler Warnings with RMS Structures (Integrity servers Only) In addition, if any of these allocations is included in a PSECT that contains an explicit alignment that is in conflict with ALIGN(3) (that is, is lower than ALIGN(3)), the BLISS compiler issues an ‘‘align request negative or exceeds that of psect’’ warning. For example, the warning would be issued for the following declaration: PSECT OWN = $OWN$ (..., ALIGN(2), ...) OWN FAB = $FAB_DECL, ...
Programming Release Notes 5.23 HP COBOL Run-Time Library (RTL) 5.23 HP COBOL Run-Time Library (RTL) V8.4 For OpenVMS Alpha and OpenVMS Integrity servers Version 8.4, the HP COBOL RTL (DEC$COBRTL) has been updated to V2.9-785. 5.23.1 Performance Improvement of COBOL CALL Statement V8.4 Performance degradation was observed on OpenVMS Integrity servers while calling subroutines, using the COBOL CALL statement. The time taken was much longer on OpenVMS Integrity servers than on OpenVMS Alpha.
Programming Release Notes 5.24 HP Fortran for Integrity servers For more information about this release, including installation instructions, read the Fortran V8.0 or V8.1 product release notes. To extract the release notes, set your default to the directory that contains the Fortran PCSI kit and enter one of the following commands: $ PRODUCT EXTRACT RELEASE_NOTES FORTRAN ! For TXT file $ PRODUCT EXTRACT FILE FORTRAN/SELECT=FORTRAN_RELEASE_NOTES.PS ! For PS file 5.
Programming Release Notes 5.25 HP MACRO for OpenVMS Table 5–1 (Cont.) Macro-32 New Built-ins Supported on Built-in Operands1 Description IA64_PADD2 Generate Parallel Add instruction, two byte form, with the first argument as the destination and the next two arguments as the source operands. Integrity servers IA64_PADD2_SSS Generate Parallel Add instruction, two byte form, with the first argument as the destination and the next two arguments as the source operands.
Programming Release Notes 5.25 HP MACRO for OpenVMS Table 5–1 (Cont.) Macro-32 New Built-ins Operands1 Built-in All the _FAULT_variants of the LFETCH built-in 1 The Supported on Description Generates ’lfetch’ instructions with the ’fault’ completer. For example, IA64_ LFETCH_FAULT_EXCL_NT1 Integrity servers built-in requires the operands, where WQ - Write Quadword, PQ - Read Quadword, AB - Address of Byte.
Programming Release Notes 5.25 HP MACRO for OpenVMS require any additional changes. For unused memory loads that must remain in final object file, change them from: MOVL (Rn),Rn into IA64_LD8_A Rn,(Rn),#0 HP will add new syntax to the compiler in a future release to designate instructions that must survive to the final object file. For systems prior to Version 8.3, there is no IA64_LD8_A built-in. The only workaround is to use /NOOPTIMIZE. 5.25.3 HP MACRO for OpenVMS Alpha Systems V8.
Programming Release Notes 5.26 Hypersort Utility 5.26 Hypersort Utility The following notes pertain to Hypersort V08-006 for OpenVMS Alpha and OpenVMS Integrity servers Version 8.2. As always, continue to use SORT32 as a workaround for any unresolved problems with Hypersort or any functionality not implemented in Hypersort. Release notes for SORT32 are in Section 5.38. 5.26.
Programming Release Notes 5.26 Hypersort Utility 5.26.5 Using Hypersort with Search Lists and Other Uses of Logical Names Permanent Restriction Hypersort does not fully support search lists and logical names used for input files and work files. If you encounter this problem, use SORT32. 5.26.6 Lack of Free Space for Work Files Permanent Restriction Hypersort does not properly terminate if free space is exhausted in all available sort work files.
Programming Release Notes 5.28 Librarian Utility The LBR$UNMAP_MODULE library service recovers those pages, but the pages remain in a heap storage free list and continue to be counted against process quota. For this reason, HP strongly recommends that DCX data-reduced ELF object libraries first be expanded before performing Linker operations. 5.28.2 Failure to Insert or Replace .STB files in an Integrity servers Library (Integrity servers Only) V8.2 On OpenVMS VAX and Alpha, .
Programming Release Notes 5.29 Linker Utility for OpenVMS Alpha 5.29.1 Linker Appears to Hang When Many Files Are Specified V8.3 When the RMS_RELATED_CONTEXT linker option is on (the default is RMS_ RELATED_CONTEXT=YES) and a nonexistent file is specified in a list of files for the LINK command, the linker’s call to LIB$FIND_FILE may take a long time to complete and the linker may appear to hang.
Programming Release Notes 5.30 Linker Utility for OpenVMS Integrity servers 5.30 Linker Utility for OpenVMS Integrity servers The following release notes pertain to the Integrity servers Linker utility. For Alpha Linker release notes, see Section 5.29. 5.30.1 Linker Writes Incorrect Interimage Debug Fixups into Debug Symbol File V8.3-1H1 In some situations, the linker creates interimage fixups for the OpenVMS debugger.
Programming Release Notes 5.30 Linker Utility for OpenVMS Integrity servers This condition happens only when Integrity server object modules, meant to provide the program’s transfer address, are included in the link operation with the SELECTIVE_SEARCH attribute. The SELECTIVE_SEARCH attribute is given to an object module when you specify the /SELECTIVE_SEARCH qualifier to the object module in the LINK command or in a LIBRARY command. For example: $ LINK MAIN/SELECTIVE_SEARCH or $ LIBRARY/INSERT LIB.
Programming Release Notes 5.30 Linker Utility for OpenVMS Integrity servers 5.30.5 Demangler Information Look Up Results in Linker Access Violation V8.3-1H1 In some cases, when the linker tried to look up demangler information in a shareable image that did not contain such information, the linker aborted with an access violation. This problem is corrected in the OpenVMS V8.3-1H1 Linker. 5.30.6 Incorrect Secondary Messages for the NOGLOSYM Error Message V8.
Programming Release Notes 5.30 Linker Utility for OpenVMS Integrity servers 5.30.11 Program Section Attribute ABS Ignored V8.3-1H1 On Integrity servers, you cannot set the ABS attribute to a program section that contains labels to convert its offsets to constants. The linker prints the error message: %ILINK-E-ILLABSPSC, absolute psect has non-zero length (not allowed) The OpenVMS 8.
Programming Release Notes 5.30 Linker Utility for OpenVMS Integrity servers The following figure illustrates this concept. Unwind Sections Code Sections (LINK_ORDER bit set) 1 2 3 refers to A B Combined Code Sections Resulting Combined Unwind Sections B 2 A 1 C 3 C VM-1134A-AI 5.30.16 Linking Against Data-Reduced ELF Object Libraries Not Recommended V8.2 DCX data-reduced ELF object libraries are not stored in contiguous space in the library.
Programming Release Notes 5.30 Linker Utility for OpenVMS Integrity servers 5.30.18 Removal of Linker Qualifiers /EXPORT_SYMBOL_VECTOR and /PUBLISH_GLOBAL_SYMBOLS V8.3 Creating a shareable image by simply exporting all global symbols does not work. Previous Integrity servers Linker versions provide the /EXPORT_SYMBOL_ VECTOR and /PUBLISH_ GLOBAL_ SYMBOLS qualifiers to assist in creating symbol vector options for all global symbols on a per-module basis.
Programming Release Notes 5.32 Mail Utility: Threads Restriction for Callable Mail 5.32 Mail Utility: Threads Restriction for Callable Mail V7.1 OpenVMS callable mail routines are not thread-safe. Refer to the Guide to the POSIX Threads Library for more information about calling non-thread-safe routines within a threaded application.
Programming Release Notes 5.35 POSIX Threads Library 5.35.1 Support for Process-shared Objects V8.2 The POSIX Threads Library on OpenVMS Alpha and Integrity servers supports process-shared mutexes and condition variables. Note The process-shared read-write locks for mutexes and condition variables are supported only on Tru64 systems.
Programming Release Notes 5.35 POSIX Threads Library With process-shared objects, the objects such as mutexes and condition variables can be shared among multiple processes. If a process terminates while owning a mutex, the mutex will stay as owned by the terminated process. Hence none of the other threads or processes can own that mutex. However, there is an optional system service sys$pshared_register.
Programming Release Notes 5.35 POSIX Threads Library 5.35.5 THREADCP Command Behavior on Integrity Servers V8.2 The DCL command THREADCP cannot be used on OpenVMS Integrity servers to query and change the two threads-related main image header flags, UPCALLS and MULTIPLE_KERNEL_THREADS. Instead, you must use the DCL commands SET IMAGE and SHOW IMAGE to set and show threads header flags on Integrity servers. Alpha users should continue to use the THREADCP command. 5.35.
Programming Release Notes 5.35 POSIX Threads Library compliance of the C RTL and threads header files has been improved. As a result, PTHREAD.H no longer provides the timespec_t typedef. There may be some applications whose compilations require the timespec_t typedef, and which erroneously rely on PTHREAD.H to provide it—either directly or indirectly (for example, by using TIS.H). If such an application source module is recompiled on an OpenVMS Version 7.
Programming Release Notes 5.35 POSIX Threads Library While an application is running, an operator can stop or start a CPU. Such a dynamic change affects the allowable number of kernel threads that future image activations can create. It also will now affect images that are currently executing. When a CPU is added or removed, the threads library will query for the new number of active CPUs, and compare this to the number of kernel threads that the process is currently using.
Programming Release Notes 5.36 RTL Library (LIB$) Currently, the supplemental access routines LIB$I64_GET_FR, LIB$I64_SET_ FR, LIB$I64_GET_GR, and LIB$I64_SET_GR improperly interpret their register number parameters without applying an adjustment for the effects of the register rename base and rotating size registers. This is an error and will be corrected in a future release.
Programming Release Notes 5.38 SORT32 Utility 5.38 SORT32 Utility The following release notes pertain to SORT32 V08-010 for OpenVMS Alpha and OpenVMS Integrity servers Version 8.2. For additional notes, refer to Section 5.26.8 and Section 5.26.1. SORT32 is recommended as a workaround for unresolved problems with Hypersort and for functionality not implemented in Hypersort. Release notes for Hypersort are in Section 5.26. 5.38.1 CONVERT Problem With DFS-Served Disks V8.
Programming Release Notes 5.38 SORT32 Utility 5.38.5 Work File Directories Restriction V7.3 SORT32 work files must be redirected to directories that allow multiple file versions that can handle the number of requested work files. 5.39 Timer Queue Entries (TQEs) Permanent Restriction Management of Timer Queue Entries was redesigned for OpenVMS Alpha Version 7.3-1 to provide significantly higher performance for systems using many TQEs. This change is transparent to nonprivileged applications.
6 Hardware Release Notes This chapter contains information about the following hardware products: • USB Device Support (Section 6.1) • MP and BMC Console (Section 6.2) • AlphaServer 2100 (Section 6.3) • AlphaServer 8200/8400 (Section 6.4) • AlphaServer ES47/ES80/GS1280 Systems (Section 6.5) • AlphaServer GS Series (Section 6.6) • AlphaStation 200/400 (Section 6.7) • AlphaStation 255 (Section 6.8) • ATI RADEON 7000 Graphics (Section 6.9) • ATI RADEON 7500 Graphics (Section 6.
Hardware Release Notes 6.1 USB Device Support The nature of USB is such that in many cases broad categories of devices can be supported by a single generic device driver. OpenVMS does not attempt to prevent such unknown third-party devices from configuring and operating. However, we cannot guarantee correct operation of such untested devices.
Hardware Release Notes 6.3 AlphaServer 2100 6.3.1 Console Display V7.2 On AlphaServer 2100 and 2100A systems, a console display similar to the following is normal and does not represent system errors: P00>>>SET CONSOLE SERIAL P00>>>INIT VMS PALcode X5.48-112, OSF PALcode X1.35-81 starting console on CPU 0 initialized idle PCB initializing semaphores initializing heap initial heap 1c0c0 memory low limit = 132000 heap = 1c0c0, 13fc0 . . .
Hardware Release Notes 6.4 AlphaServer 8200/8400: FRU Table Error 6.4 AlphaServer 8200/8400: FRU Table Error V7.2 The error log buffer size is controlled by the system parameter ERLBUFFERPAGES, which has a maximum value of 32 pagelets. If the Field Replaceable Unit (FRU) table exceeds this limit during a boot of the OpenVMS Alpha operating system on an AlphaServer 8200/8400 or 4100 system, an entry will not be written to the error log file. 6.
Hardware Release Notes 6.5 AlphaServer ES47/ES80/GS1280 Systems When the shutdown procedure is invoked on an ES47/ES80/GS1280 system with an attached I/O drawer, an error message such as the following might be displayed: %SYSTEM-W-WRONGSTATE, CPU 5 is in the wrong state for the requested operation You can ignore such messages. The shutdown will complete correctly. 6.5.5 Setting Time at MBM V7.3-2 You must set the correct time and date on the MBM of an AlphaServer ES47/ES80/GS1280 system.
Hardware Release Notes 6.6 AlphaServer GS Series Systems • Load the SMP licenses. • Use the following command to verify that you have the correct number of license units: $ SHOW LICENSE /UNIT_REQUIREMENTS /CLUSTER Note The base OpenVMS license allows you to have only one interactive user login per physical system (not per partition). (However, you can always log in from OPA0: in each partition.) For additional interactive users, you will require additional license units.
Hardware Release Notes 6.6 AlphaServer GS Series Systems b. Once you have determined the system serial number, use the SET SYS_ SERIAL_NUM command from the master console of each partition to change SYS_SERIAL_NUM to the correct value. For example: P00>>> P00>>>SET SYS_SERIAL_NUM G2A105 You must do this in every hard partition and in every soft partition. 5.
Hardware Release Notes 6.7 AlphaStation 200/400: ISA_CONFIG.DAT Changes Required Warning For upgrades from OpenVMS Version 6.2 or 7.0 systems, this change must be made before starting the upgrade procedure. Table 6–1 shows the changes to the device description block. Table 6–1 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.
Hardware Release Notes 6.9 ATI RADEON 7000 Graphics (Integrity servers Only) 6.9.2 Hardware Accelerated 3D Graphics Not Supported on RADEON 7000 V8.2 Hardware accelerated 3D (OpenGL) rendering is not supported on the embedded Radeon 7000 PCI adapter. 6.10 ATI RADEON 7500 Graphics V7.3-2 The following notes describe resource requirements, enhancements, fixes, and a few restrictions for ATI RADEON 7500 graphics.
Hardware Release Notes 6.10 ATI RADEON 7500 Graphics GBLPAGFIL 8233 (GBLPAGFIL is in units of 8192-byte Alpha pages.) 6.10.2 DECW$OPENGLSHR_RADEON.EXE Renamed to DECW$MESA3DSHR_RADEON.EXE V8.2 The shareable library SYS$LIBRARY:DECW$OPENGLSHR_RADEON.EXE has been renamed to SYS$LIBRARY:DECW$MESA3DSHR_RADEON.EXE to reflect that this library was built from the Mesa 3D code base. The API and functionality remain the same as in previous releases.
Hardware Release Notes 6.10 ATI RADEON 7500 Graphics If you do not have SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM, you can create this command procedure from SYS$MANAGER:DECW$PRIVATE_ APPS_SETUP.TEMPLATE. After editing SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM, restart DECwindows with the following command: $ @SYS$MANAGER:DECW$STARTUP RESTART 6.10.7 Monitor Must Be Connected During Initialization The RADEON 7500 graphics card has two video output ports: one for digital and one for analog.
Hardware Release Notes 6.10 ATI RADEON 7500 Graphics 6.10.12 Pixel Depth for Read/Write Color Map By default, the RADEON 7500 provides a pixel depth of 24 planes with a readonly, TrueColor color map. Some applications, such as DECwindows Paint, require a read/write color map.
Hardware Release Notes 6.10 ATI RADEON 7500 Graphics Specifies the number of clock ticks that are allowed to elapse before a timeout occurs and the DECwindows server seizes control of the RADEON card. The default values are chosen to minimize the impact of the timer on the performance of graphics applications. If you want to reduce the length of time before the DECwindows server begins responding again, you can do so by decreasing the value of DECW$DRM_TIMER_PERIOD.
Hardware Release Notes 6.12 DIGITAL Modular Computing Components (DMCC) • If you are running Windows NT on these systems, update only the AlphaBIOS setup. If you accidentally update both the SRM and the AlphaBIOS consoles, you will enter the AlphaBIOS Setup menu, and you will not have the option to return to the SRM console. The only way to exit the AlphaBIOS Setup menu and return to the SRM console is to use a Firmware Update Utility located at the following Internet site: ftp://ftp.digital.
Hardware Release Notes 6.15 Open3D Graphics Licensing Change 6.15 Open3D Graphics Licensing Change V8.2 The 3D graphics display capability has traditionally been licensed separately from the OpenVMS operating system. Since its initial offering, the Open3D layered product has required a separately orderable license. When Open3D software began shipping as part of the OpenVMS operating system, the 3D graphics display feature continued to be a separately licensed capability.
Hardware Release Notes 6.
Hardware Release Notes 6.17 RFnn DSSI Disk Devices and Controller Memory Errors Table 6–2 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 6.17 RFnn DSSI Disk Devices and Controller Memory Errors To update the microcode in your device, use the appropriate command for your device and platform from Table 6–3. Caution Back up the disk before updating the microcode. Table 6–3 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.
Hardware Release Notes 6.18 RZnn Disk Drive Considerations 6.18.2 RZ26N and RZ28M Disks: Recommended Firmware Support V6.2-1H3 The minimum firmware revision level recommended for RZ26N and RZ28M disks is Revision 0568. If the latest firmware revision level is not used with these disks, multiple problems can occur. 6.18.3 RZ26L and RZ28 Disks: Required Firmware for Multihost Use V6.
Hardware Release Notes 6.18 RZnn Disk Drive Considerations $ RZTOOLS_ALPHA :== $SYS$ETC:RZTOOLS_ALPHA $ RZTOOLS_ALPHA DKB500 /LOAD=SYS$ETC:filename.FUP Read in 262144 bytes. Current FW version - X440C Upgrading to - DEC0 Loading code ...... New code has been sent to the drive. 6.19 sx1000 Integrity Superdome V8.3 The HP Integrity Superdome cannot boot as a satellite over the Core I/O LAN card. When you specify the LAN card as a boot option to BOOT_OPTION.
Hardware Release Notes 6.21 Recompiling and Relinking OpenVMS Device Drivers Note that for OpenVMS Version 7.1 all OpenVMS VAX SCSI device drivers required recompiling and relinking. OpenVMS VAX device drivers that were recompiled and relinked to run on OpenVMS Version 7.1 will run correctly on OpenVMS Version 7.3 or higher. 6.21.2 OpenVMS Alpha Device Drivers V7.1 Device drivers that were recompiled and relinked to run on OpenVMS Alpha Version 7.
Hardware Release Notes 6.25 CRCTX Routines Enhanced 6.25 CRCTX Routines Enhanced V7.1-2 The system routines that you can use to manage the Counted Resource Context Block (CRCTX) data structure have been improved.
Hardware Release Notes 6.26 Adapter Release Notes To determine the latest, currently supported versions of the RISC firmware and EFI driver, see the README text file provided on the HP IPF Offline Diagnostics and Utilities CD. To locate this file, navigate to the (\efi\hp\tools\io_ cards\fc2) directory for the 2 GB Fibre Channel HBA or \efi\hp\tools\io_ cards\fc4 for the 4 GB HBA. To update the driver and firmware, execute the fcd_update2.nsh or the fcd_update4.nsh, depending on your HBA type.
A 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) A.2 Using the Code Analysis Tool (SRM_CHECK) 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) A.3 Noncompliant Code Characteristics 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. • Some code compiled with very old BLISS, MACRO–32, DEC Pascal, or DEC COBOL compilers may contain noncompliant sequences. Early versions of these compilers contained a code scheduling bug where a load was incorrectly scheduled after a load_locked.
Interlocked Memory Instructions (Alpha Only) A.4 Coding Requirements • 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) A.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) A.5 Compiler Versions The MACRO–32 Compiler for OpenVMS Alpha Version 4.1 now performs additional code checking and displays warning messages for noncompliant code sequences. A.6 Recompiling Code with ALONONPAGED_INLINE or LAL_REMOVE_FIRST Any MACRO–32 code on OpenVMS Alpha that invokes either the ALONONPAGED_INLINE or the LAL_REMOVE_FIRST macro from the SYS$LIBRARY:LIB.MLB macro library must be recompiled on OpenVMS Version 7.
Index A Ada compiler, 5–11 adapter release notes, 6–22 AlphaServer 2100 console display, 6–3 SCSI controller restriction, 6–3 AlphaServer 4100 FRU table restriction, 6–4 AlphaServer 8200 systems FRU table restriction, 6–4 AlphaServer 8400 systems FRU table restriction, 6–4 AlphaServer ES47/ES80/GS1280 systems INIT console command usage on soft partitions, 6–4 license requirement, 6–4 RAD support, 6–4 setting time at MBM, 6–5 STOP/CPU and shutdown behavior, 6–4 AlphaServer GS Series systems device restrictio
Configuring SAS tape drives, 4–12 C programs compiling and case sensitivity, 5–11 CPUSPINWAIT bugcheck, 5–15 CPU_POWER_MGMT default, 4–22 CRCTX routines enhanced, 6–22 C RTL, 5–11 to 5–13 backport library, 5–12 changes, 5–13 DECC$*.OLB libraries frozen, 5–13 _ _fci built-in added, 5–13
F$GETSYI("RAD_CPUS"), 3–1 Fast Path turning off, for Galaxy on ES40, 4–31 _ _fci built-in added, 5–13 Fibre Channel, 5–4, 6–23 compatibility kits, 4–26 multipath failover restriction for tape devices, 4–29 Firmware for Alpha servers, 1–8 for Integrity servers, 1–6 firmware, EFI, 4–5 Floating-point data considerations for applications, 5–10 FMS kits, 2–5 Fortran See HP Fortran Freeware, 3–7 menu unavailable on OpenVMS Integrity servers, 3–8 HP DECwindows Motif (cont’d) version support, 1–4 HP Fortran for In
K Kerberos Kerberos for OpenVMS, 1–10 KPB extensions, 5–7 L LANCP converting device database after upgrading (Alpha only), 1–13 LAN Drivers duplex mode mismatch errors, 3–22 Large device name support, 4–10 Layered product fails to install, 1–14 LIB$GET_CURR_INVO_CONTEXT documentation correction, 3–20 LIB$GET_INVO_CONTEXT documentation correction, 3–20 LIB$GET_INVO_HANDLE documentation correction, 3–20 LIB$GET_PREV_INVO_CONTEXT documentation correction, 3–20 LIB$GET_PREV_INVO_HANDLE documentation correction
Network update restrictions, 3–21 Network options, 1–3 New Return Status pthread_mutex_lock, 5–34 Noncompliant code, A–1, A–2 O Open3D graphics controller boards support, 6–20 licensing change, 6–15 OpenVMS ENCRYPT and DECRYPT commands, 1–12 OpenVMS Calling Standard rotating registers, 5–13 OpenVMS Cluster systems, 4–14 to 4–29 compatibility kits, 4–26 compatibility kits for mixed versions, 4–26 patch kits, 4–25 performance reduced with CI-LAN switching, 4–28 rolling upgrades, 1–9 SCSI multipath failover,
R Recompiling programs for Alpha, 5–6 Remedial kits obtaining, 1–3 required for mixed-version OpenVMS Cluster system, 4–26 restriction SYS$LDDRIVER, 4–22 RF73 and RFnn disks, controller memory errors, 6–16 RMS FAB, 5–17 Rotating registers, 5–38 Run-time library routines, 3–20 rx7620 server, 1–4 rx8620 server, 1–4 RZnn disk drives, 6–18 to 6–20 S satellite system, 4–22 SCSI controllers restrictions on AlphaServer 2100 systems, 6–3 SCSI device drivers, 6–20 SCSI multipath incompatibility, 4–27 SDA See OpenVM
UCB structure updates, 5–8 Upgrade paths, 1–8 USB device support, 6–1 V validation, 5–4 VAX Cluster Cache See Virtual I/O Cache VCC See Virtual I/O Cache VIOC See Virtual I/O Cache virtual connect, 4–23 failover, 4–23 Virtual I/O Cache not available on Integrity servers, 4–34 superseded by XFC, 4–34 Volume Shadowing for OpenVMS compatibility kits, 4–26 W Watchpoint utility, 5–41 WEBES support on Integrity servers, 2–8 Whole-program floating-point mode (Integrity servers only), 5–41 Write Bitmaps, 4–8 wri
