HP OpenVMS User Manual

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.4

Hewlett-Packard Company Palo Alto, California

Conﬁdential 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Intel and Itanium are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Java is a US trademark of Sun Microsystems, Inc.

Oracle is a US registered trademark of Oracle Corporation, Redwood City, California.

OSF and Motif are trademarks of The Open Group in the US and other countries, and UNIX is a registered trademark of The Open Group.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

X/Open is a registered trademark, and the X device is a trademark of X/Open Company Ltd. in the UK and other countries.

ZK6677

This document was prepared using DECdocument, Version 3.3-1b.

Contents

Preface ............................................................ xv

1 OpenVMS Software Installation and Upgrade Release Notes

1.1 HP Software Technical Support Policy ............................ 1–1

1.2 General Application Compatibility Statement ...................... 1–2

1.3 Obtaining Remedial Kits ...................................... 1–3

1.4 Networking Options . . ........................................ 1–3

1.5 Disk Incompatibility with Older Versions of OpenVMS ............... 1–3

1.6 HP DECwindows Motif for OpenVMS ............................ 1–4

1.7 OpenVMS Integrity server Users ................................ 1–4

1.7.1 Storage Controllers ....................................... 1–4

1.7.2 U160 SCSI Support for rx7620 and rx8620 ..................... 1–5

1.7.3 Clearing the System Event Log on Integrity servers ............. 1–5

1.7.4 Firmware for Integrity Servers .............................. 1–6

1.7.5 Booting from the Installation DVD ........................... 1–7

1.7.6 Booting from USB or vMedia Devices . . ....................... 1–8

1.7.7 HP DECwindows Motif Release Notes . ....................... 1–8

1.7.7.1 Keyboard Support ..................................... 1–8

1.8 OpenVMS Alpha Users ....................................... 1–8

1.8.1 Firmware for OpenVMS Alpha Version 8.4 ..................... 1–8

1.8.2 Upgrade Paths . . ........................................ 1–8

1.9 Kerberos for OpenVMS ....................................... 1–10

1.10 Modifying SYSTARTUP_VMS.COM ............................. 1–12

1.11 Encryption for OpenVMS ...................................... 1–12

1.12 Upgrading HP DECram V3.n .................................. 1–12

1.13 Converting the LANCP Device Database . . ....................... 1–13

1.14 DECnet-Plus Requires a New Version ............................ 1–13

1.15 Remove TIE Kit Before Upgrade ................................ 1–14

1.16 Installation Failure of Layered Products on Alternate Devices or

Directories ................................................ 1–14

2 OpenVMS Associated Products Release Notes

2.1 Associated Product Support .................................... 2–1

2.2 HP TCP/IP Services for OpenVMS ............................... 2–2

2.3 NetBeans Version 5.5.1 Requires Latest JDK ...................... 2–2

2.4 Problem Accessing DFS Mounted Disk ........................... 2–2

2.5 HP DCE for OpenVMS Restriction (Integrity servers Only) ............ 2–2

2.6 XML-C Product Zip File ....................................... 2–3

2.7 OpenVMS e-Business and Integration Infrastructure Package . . ....... 2–3

2.8 Updates to Freeware Readme File ............................... 2–3

2.9 CMAP Files Added . . ........................................ 2–4

iii

2.10 COBOL: Changes in I/O Run-Time Diagnostics and RMS Special

Registers .................................................. 2–4

2.11 COM for HP OpenVMS (Alpha Only) . ............................ 2–4

2.11.1 COM for OpenVMS Support ................................ 2–4

2.11.2 Registry Access Error with Heavy Load of Applications . ........... 2–4

2.12 DECdfs Version 2.4 Required for OpenVMS Version 8.3 . . . ........... 2–4

2.13 DECforms Web Connector Version 3.0 (Alpha Only) ................. 2–5

2.14 DEC PL/I: RTL Support for OpenVMS ............................ 2–5

2.15 FMS Kits ................................................. 2–5

2.16 Graphical Conﬁguration Manager (Alpha Only) . . ................... 2–6

2.17 HP DECram ................................................ 2–6

2.17.1 DECram Available with OpenVMS Version 8.2 and later ........... 2–6

2.17.2 Conﬂict with DECRYPT DCL Command ....................... 2–6

2.18 HP DECwindows Motif for OpenVMS ............................ 2–6

2.18.1 New Locales Added . . . .................................... 2–7

2.18.2 User-Written Transports not Supported ....................... 2–7

2.19 HP Secure Web Server Version Support ........................... 2–7

2.20 HP Pascal for OpenVMS Alpha Systems .......................... 2–7

2.20.1 HP Pascal: Version 5.8A (or later) Required to Create STARLET

Library (Alpha Only) . . .................................... 2–8

2.20.2 Installing HP Pascal After an Upgrade (Alpha Only) . . . ........... 2–8

2.21 WEBES and SEA Support on Integrity servers . . ................... 2–8

3 General User Release Notes

3.1 SYS$GETTIM_PREC System Service Declaration ................... 3–1

3.2 Problem With F$GETSYI("RAD_CPUS") .......................... 3–1

3.3 HP Code Signing Service for OpenVMS Support . ................... 3–1

3.4 Symbolic Links Implementation Changes ......................... 3–1

3.4.1 Logical Names ........................................... 3–1

3.4.2 Audit Alarms Fixed . . . .................................... 3–2

3.5 SHOW SYSTEM/STATE=MUTEX Does not Display the Processes . . . . . . 3–2

3.6 SWB V1.1-12 Installation Warnings . . ............................ 3–3

3.7 Ctrl/P at the Console Does not Always Work ....................... 3–3

3.8 Installing Oracle Database 10g Release 2 for OpenVMS Fails .......... 3–4

3.9 Serial Port Enumeration . . .................................... 3–4

3.10 Old Firmware Cannot Translate Messages Written to the System Event

Log....................................................... 3–6

3.11 TZ Function in C RTL ........................................ 3–7

3.12 InfoServer Utility and FDDI ................................... 3–7

3.13 New Qualiﬁer for DCL Command SET PASSWORD ................. 3–7

3.14 OpenVMS Freeware CDs . . .................................... 3–7

3.14.1 Freeware Menu Unavailable (Integrity servers Only) . . ........... 3–8

3.15 DCL Commands . ............................................ 3–8

3.15.1 SHUTDOWN.COM on OpenVMS Graphics Console (Integrity servers

only) ................................................... 3–8

3.15.2 DIAGNOSE Command No Longer Supported ................... 3–8

3.15.3 MOUNT Command Restriction . . ............................ 3–8

3.16 DECmigrate Not on Open Source Tools CD ........................ 3–9

3.17 HP Secure Web Browser . . .................................... 3–9

3.17.1 Increased Memory Required ................................ 3–9

3.17.2 Installation Error on ODS-2 Disk Volume (Integrity servers Only) . . . 3–9

3.18 Documentation Corrections .................................... 3–10

3.18.1 HP OpenVMS Linker Utility Manual Update ................... 3–10

3.18.1.1 HP C++ Examples ..................................... 3–10

3.18.2 HP PCSI Utility Online help and Manual: $PRODUCT REGISTER

VOLUME Syntax Error Correction ........................... 3–10

3.18.3 iCAP Release Notes: GiCAP Functionality not Available ........... 3–10

3.18.4 POLYCENTER Software Installation Utility Developer’s Guide:

PRODUCT Command Update ............................... 3–11

3.18.5 HP OpenVMS System Manager’s Manual Update ................ 3–11

3.18.5.1 Getting Information About Devices on the System ............ 3–11

3.18.5.2 Initializing a New Volume with ODS-5 Format ............... 3–13

3.18.5.3 Converting from ODS-2 to ODS-5 . . ....................... 3–13

3.18.5.4 New Extended File Speciﬁcations Characteristics ............. 3–14

3.18.5.5 ODS-2 and ODS-5 Used Together . . ....................... 3–14

3.18.5.6 Performing Image Backups to Disk . ....................... 3–15

3.18.5.7 Mounting a Volume With Caching Disabled . . . ............... 3–16

3.18.5.8 System-Wide Statistics . . ................................ 3–16

3.18.5.9 Disabling Caching for a Volume ........................... 3–16

3.18.5.10 Understanding File System Data Caches .................... 3–17

3.18.6 HP OpenVMS RTL Library (LIB$) Manual ..................... 3–17

3.18.7 Documentation Error: LCKMGR_CPUID System Parameter ....... 3–18

3.18.8 MMG_CTLFLAGS: Documentation Error ...................... 3–18

3.18.9 HP OpenVMS System Analysis Tools Manual ................... 3–18

3.18.10 HP OpenVMS Programming Concepts Manual .................. 3–18

3.18.10.1 Saving System Dumps . . ................................ 3–18

3.19 HP OpenVMS DELTA/XDELTA Debugger Manual Update ........... 3–18

3.19.1 HP OpenVMS Version 8.2 New Features and Documentation Overview:

Librarian Utility Corrections ................................ 3–18

3.19.1.1 /REMOVE Qualiﬁer Correction ........................... 3–19

3.19.1.2 Accessing ELF Object Libraries Correction . . . ............... 3–19

3.19.2 HP OpenVMS RTL Library (LIB$) Manual Corrections ........... 3–20

3.19.2.1 HP OpenVMS RTL Library (LIB$) Manual: Rounding Rule for

LIB$CVT_DX_DX ..................................... 3–20

3.19.3 HP OpenVMS RTL Library (LIB$) Manual: Platform Restrictions . . . 3–20

3.19.4 HP OpenVMS System Manager’s Manual: IPC Commands

Restriction .............................................. 3–21

3.20 Network Update Restrictions from Version 8.2 to Version 8.2–1 . ....... 3–21

3.21 Synchronous Data Links not Supported ........................... 3–21

3.22 Duplex-Mode Mismatch Errors . ................................ 3–22

4 System Management Release Notes

4.1 SYS$TIMEZONE_RULE Logical Replaces Hyphen (-) with Caret (^) .... 4–1

4.2 Issues with Time Zone Conﬁguration ............................. 4–1

4.3 OpenVMS as a Guest Operating System on Integrity VM ............. 4–2

4.3.1 "Guest Punishment" Scenarios ............................... 4–2

4.3.2 Increased CPU Consumption After Shutdown ................... 4–4

4.3.3 OpenVMS Guest Does not Support Attached I/O Devices . . . ....... 4–4

4.3.4 Networking or Storage Interface Support ...................... 4–4

4.4 Provisioning OpenVMS Using HP SIM ........................... 4–4

4.4.1 Provisioning OpenVMS Guest Limitation ...................... 4–4

4.4.2 System Firmware . ........................................ 4–5

4.4.3 Provisioning Multiple Servers ............................... 4–5

4.4.4 Provisioning From HP SIM Central Management Server . . . ....... 4–5

4.4.5 InfoServer Name Length . . . ................................ 4–5

4.4.6 OpenVMS InfoServer and the Integrity servers on the Same LAN . . . 4–5

4.4.7 EFI Firmware ........................................... 4–5

4.4.8 Management Processor .................................... 4–5

4.4.9 OpenVMS TCP/IP Provisioning Limitation . . ................... 4–5

4.4.10 Limitation with Deploying OpenVMS on Multiple Target Servers

Simultaneously .......................................... 4–6

4.5 Insight Dynamics - Virtual Server Environment for OpenVMS ......... 4–6

4.5.1 Utilization Data Collection Fails . ............................ 4–6

4.5.2 Problem While Creating a New or Replacement Simulated System . . . 4–7

4.5.3 Utilization Data not Available for OpenVMS Sub-OS Workloads . . . . . 4–7

4.5.4 Insight Software Features not Supported on OpenVMS . ........... 4–7

4.6 Performance Enhancements .................................... 4–8

4.6.1 Enhancements to Write Bitmaps . ............................ 4–8

4.6.1.1 WBM_MSG_INT Parameter Updates ....................... 4–8

4.6.1.2 WBM_MSG_UPPER and WBM_MSG_LOWER Parameter

Updates . ............................................ 4–8

4.6.1.3 Asynchronous SetBit Messages ........................... 4–9

4.6.1.4 Reduced SetBit Messages for Sequential I/O ................. 4–9

4.6.2 Exception Handling Performance Improvements (Integrity servers

Only) .................................................. 4–9

4.6.3 Exception Handling (Integrity servers Only) . ................... 4–9

4.6.4 Image Activation (Integrity servers Only) . . . ................... 4–10

4.6.5 Global Section Creation and Deletion ......................... 4–10

4.6.6 Dedicated CPU Lock Manager . . . ............................ 4–10

4.6.7 Ctrl/T Alignment Faults .................................... 4–10

4.7 Error and Warning Messages from ACPI During Boot ................ 4–10

4.8 Large Device Name Support for Accounting Utility .................. 4–10

4.9 PAGED_LAL_SIZE New System Parameter ....................... 4–11

4.9.1 Paged Pool Lookaside Lists ................................. 4–11

4.10 2 TiB Disk Volume Support Restrictions .......................... 4–11

4.11 Conﬁguring SAS Tape Drives ................................... 4–12

4.12 External SAS Disk Device Naming . . ............................ 4–12

4.13 External Authentication . . .................................... 4–12

4.13.1 External Authentication and Password Policy ................... 4–12

4.13.2 Integrity servers External Authentication Support ............... 4–13

4.13.3 SET PASSWORD Behavior Within a DECterm Terminal Session . . . . 4–13

4.13.4 No Password Expiration Notiﬁcation on Workstations . ........... 4–13

4.13.5 Restriction in ACME_SERVER Process (Integrity servers only) . . . . . 4–13

4.14 Itanium Primary Bootstrap (IPB) Fails to Find the Valid Dump

Devices .................................................... 4–14

4.15 SHUTDOWN.COM Changes ................................... 4–14

4.16 OpenVMS Cluster Systems .................................... 4–14

4.16.1 Cluster over IP (IP Cluster Interconnect) ....................... 4–14

4.16.1.1 Software Requirements ................................. 4–14

4.16.1.2 Integrity servers Satellite Node and Bootserver in the Same

LAN................................................ 4–14

4.16.1.3 Alpha Satellite Node Requires LAN Channels With Disk

Server . . ............................................ 4–15

4.16.1.4 IPv6 Support ......................................... 4–15

4.16.1.5 Dynamic Host Conﬁguration Protocol (DHCP) or Secondary

Address Support . . . .................................... 4–15

4.16.1.6 Multiple IP Interface Conﬁguration ........................ 4–15

4.16.1.7 ifconﬁg Command Usage ................................ 4–15

4.16.1.8 Multiple Gateway Conﬁguration .......................... 4–15

4.16.1.9 Block Transfer XMIT Chaining ........................... 4–15

4.16.1.10 LANCP for Downline Load ............................... 4–16

4.16.1.11 Duplex Mismatch ...................................... 4–16

4.16.1.12 Conﬁguring a Node During Upgrade ....................... 4–16

4.16.2 OpenVMS Cluster Support for Integrity VM .................... 4–16

4.16.2.1 Cluster Interconnect for OpenVMS Guest ................... 4–16

4.16.2.2 MSCP Support for Clusters in Integrity VM Environment ...... 4–16

4.16.2.3 Online Migration Support ............................... 4–16

4.16.3 Mixed Platform Support .................................... 4–17

4.16.4 Satellite Systems using Port Allocation Class ................... 4–17

4.17 Mixed-version Cluster Compatibility of a Six-member Shadowset ....... 4–17

4.18 Backward Compatibility of a Six-member Shadowset . ............... 4–18

4.19 WBEM Services and WBEM Providers for OpenVMS . ............... 4–18

4.19.1 Increased CPU Consumption With WBEM on OpenVMS Guest ..... 4–18

4.19.2 WBEM Providers Support for OpenVMS Guest . . . ............... 4–18

4.19.3 Based on OpenPegasus 2.9 . . ................................ 4–19

4.19.4 Supports nPartitions and iCAP .............................. 4–19

4.19.5 Restart cimserver.exe to Unload Providers on OpenVMS ........... 4–19

4.19.6 Use Quotes Around Command Line Options .................... 4–19

4.20 Writing the System Dump File to an Alternate Disk . . ............... 4–19

4.21 Monitor Utility Changes ...................................... 4–19

4.21.1 Guest Operating System on Integrity VM ...................... 4–19

4.21.2 Version-to-Version Compatibility of MONITOR Data .............. 4–21

4.21.3 Playing Back Data from a Recording File ...................... 4–21

4.22 System Parameters . . ........................................ 4–21

4.23 SYS$LDDRIVER Restriction . . . ................................ 4–22

4.24 CPU_POWER_MGMT Default Value Changed ..................... 4–22

4.25 Booting A Satellite System with Reserved Memory . . . ............... 4–22

4.26 SCACP Error Counter Reports Retransmit Errors ................... 4–22

4.27 Virtual Connect ............................................. 4–23

4.27.1 Failover and RECNXINTERVAL ............................. 4–23

4.28 INITIALIZE/ERASE=INIT Before Using Media ..................... 4–23

4.29 Performance Data Collector for OpenVMS (TDC) ................... 4–23

4.30 Recovering From System Hangs or Crashes (Integrity servers Only) ..... 4–23

4.31 DECdtm/XA with Oracle 8i and 9i (Alpha Only) .................... 4–24

4.32 Device Unit Number Increased . ................................ 4–24

4.33 EDIT/FDL: Fixing Recommended Bucket Size ...................... 4–24

4.34 Using EFI$CP Utility not Recommended . . . ....................... 4–25

4.35 Error Log Viewer (ELV) Utility: TRANSLATE/PAGE Command . ....... 4–25

4.36 Cluster Compatibility Patch Kits ................................ 4–25

4.36.1 Patch Kits Needed for Cluster Compatibility ................... 4–26

4.36.2 API to Correct Incompatibility of FC and SCSI Multipath with Some

Third-Party Products ..................................... 4–27

4.36.3 DDT Intercept Establisher Routines and Device Conﬁguration

Notiﬁcation Results ....................................... 4–28

4.36.4 Cluster Performance Reduced with CI-LAN Circuit Switching ...... 4–28

4.36.5 Multipath Tape Failover Restriction . . . ....................... 4–29

4.36.6 No Automatic Failover for SCSI Multipath Medium Changers ...... 4–29

4.37 OpenVMS Galaxy (Alpha Only) . ................................ 4–29

4.37.1 Galaxy Deﬁnitions ........................................ 4–30

4.38 Multiple nPartitions on Cell-based Systems . ....................... 4–30

4.38.1 OpenVMS Graphical Conﬁguration Manager ................... 4–30

4.38.2 Galaxy on ES40: Uncompressed Dump Limitation ............... 4–30

4.38.3 Galaxy on ES40: Turning Off Fastpath ....................... 4–31

vii

4.39 Corrupted Version 2 Format Database ........................... 4–31

4.40 System Parameters .......................................... 4–31

4.40.1 New System Parameters ................................... 4–31

4.40.2 Obsolete System Parameters ................................ 4–31

4.40.3 System Parameter Changes ................................. 4–32

4.41 Terminal Fallback Facility . .................................... 4–32

4.42 User Environment Test Package (Integrity servers Only) . . ........... 4–33

4.43 Recommended Caching Methods ................................ 4–34

4.44 Analyze Utility for OpenVMS .................................. 4–34

4.44.1 Formatted Symbol Vector Correctly Shown in Data Segment ....... 4–34

4.44.2 Transfer Array Formatted in Data Segment . ................... 4–34

4.44.3 System Version Array Formatted in Dynamic Segment . ........... 4–35

4.44.4 Enhancements for the /SEGMENT Qualiﬁer .................... 4–35

4.44.5 Support for Section Escaping Added .......................... 4–35

4.45 INSTALL Utility for OpenVMS (Installing Resident Images in S2

Space) .................................................... 4–35

5 Programming Release Notes

5.1 Symbolic Debugger ........................................... 5–1

5.2 C++ Run-Time Library ........................................ 5–1

5.3 Process/Application Hangs . .................................... 5–3

5.4 AST Delivery Clariﬁcation in Programs using POSIX Threads ......... 5–3

5.5 RMS $PARSE Validation of Directory Files ........................ 5–4

5.6 No-IOLOCK8 Fibre Channel Port Drivers ......................... 5–4

5.7 C++ Compiler . . . ............................................ 5–5

5.8 Building DCE IDL C++ Applications . ............................ 5–5

5.9 Privileged Programs may Need a Recompile (Alpha Only) . . ........... 5–6

5.10 Privileged Data Structures Updates . . ............................ 5–6

5.10.1 KPB Extensions .......................................... 5–7

5.10.2 CPU Name Space ........................................ 5–7

5.10.3 64-Bit Logical Block Number (LBN) .......................... 5–7

5.10.4 Forking to a Dynamic Spinlock . . ............................ 5–7

5.10.5 UCB/DDB Updates . . . .................................... 5–8

5.10.6 PCB$T_TERMINAL Size Increase ........................... 5–8

5.10.7 Per-Thread Security Impacts Privileged Code and Device Drivers . . . . 5–8

5.11 Applications Using Floating-Point Data .......................... 5–10

5.11.1 IEEE Floating-Point Filter (Integrity servers Only) ............... 5–10

5.11.2 Ada Event Support (Integrity servers Only) . . ................... 5–10

5.11.3 C++ Language Issues (Integrity servers Only) ................... 5–11

5.12 Ada Compiler(Integrity servers Only) ............................ 5–11

5.13 Backup API: Journaling Callback Events Restriction ................ 5–11

5.14 C Programs: Compiling with CASE_LOOKUP=SENSITIVE Settings . . . . 5–11

5.15 C Run-Time Library .......................................... 5–11

5.15.1 C RTL TCP/IP Header File Updates .......................... 5–12

5.15.2 Backport Library No Longer Shipped ......................... 5–12

5.15.3 Header File <time.h> Changes . . . ............................ 5–12

5.15.4 Header File <time.h> Makes *_r Non-ANSI Functions Visible . . . . . . 5–13

5.15.5 Header File <builtins.h> _ _CMP_SWAP* and _Interlocked* Visible to

C++ ................................................... 5–13

5.15.6 Builtin _ _fci Added for Integrity servers ....................... 5–13

5.15.7 No New Entries for DECC$*.OLB Object Libraries ............... 5–13

5.16 Calling Standard and Rotating Registers (Integrity servers Only) . . . . . . 5–13

5.17 Common Data Security Architecture (CDSA) Considerations .......... 5–14

viii

5.17.1 Secure Delivery . . ........................................ 5–14

5.17.2 Installation and Initialization Considerations ................... 5–14

5.18 Debugging Modes: Avoiding CPUSPINWAIT Bugchecks .............. 5–15

5.19 Delta/XDelta Debuggers ....................................... 5–15

5.19.1 XDELTA Register Display Consideration (Integrity servers Only) .... 5–15

5.20 File Applications: Corrections to Guide to OpenVMS File Applications

.......................................................... 5–16

5.21 HP BLISS Compiler Warnings with RMS Structures (Integrity servers

Only) ..................................................... 5–16

5.22 Potential Must-Be-Zero RMS Error: Making Room for New File Options

intheFAB................................................. 5–17

5.23 HP COBOL Run-Time Library (RTL) ............................ 5–18

5.23.1 Performance Improvement of COBOL CALL Statement ........... 5–18

5.24 HP Fortran for Integrity servers ................................ 5–18

5.25 HP MACRO for OpenVMS .................................... 5–19

5.25.1 Enhancements for the Macro-32 Compiler ...................... 5–19

5.25.2 HP MACRO for OpenVMS Integrity servers .................... 5–21

5.25.3 HP MACRO for OpenVMS Alpha Systems ...................... 5–22

5.25.4 /OPTIMIZE=VAXREGS Qualiﬁer Not Supported on Integrity

servers . ................................................ 5–22

5.25.5 Floating Divide-by-Zero Error Not Raised (Integrity servers Only) . . . 5–22

5.26 Hypersort Utility ............................................ 5–23

5.26.1 Reporting a Problem to HP . ................................ 5–23

5.26.2 Large Files Restriction ..................................... 5–23

5.26.3 Hypersort and VFC Files Restriction . . . ....................... 5–23

5.26.4 /FORMAT=RECORD_SIZE Restriction . ....................... 5–23

5.26.5 Using Hypersort with Search Lists and Other Uses of Logical Names

....................................................... 5–24

5.26.6 Lack of Free Space for Work Files ............................ 5–24

5.26.7 Input Asterisk (*) Restriction ................................ 5–24

5.26.8 Optimal Working Set Extent and Page File Quota Settings . ....... 5–24

5.27 Intel Assembler (Integrity servers Only) . . . ....................... 5–24

5.28 Librarian Utility ............................................ 5–24

5.28.1 Linking Against Data-Reduced ELF Object Libraries Not

Recommended (Integrity servers Only) . ....................... 5–24

5.28.2 Failure to Insert or Replace .STB ﬁles in an Integrity servers Library

(Integrity servers Only) .................................... 5–25

5.28.3 Librarian Fails to Report Errors When Process Quota Too Low ..... 5–25

5.29 Linker Utility for OpenVMS Alpha .............................. 5–25

5.29.1 Linker Appears to Hang When Many Files Are Speciﬁed .......... 5–26

5.29.2 Change in Linker Default Behavior with Library Check . . . ....... 5–26

5.29.3 Limit of 25 Elements on Stack .............................. 5–26

5.30 Linker Utility for OpenVMS Integrity servers ...................... 5–27

5.30.1 Linker Writes Incorrect Interimage Debug Fixups into Debug Symbol

File .................................................... 5–27

5.30.2 /SELECTIVE_SEARCH Qualiﬁer Might Incorrectly Ignore Transfer

Address ................................................ 5–27

5.30.3 Maximum Number of Sections ............................... 5–28

5.30.4 Incorrect Creation Date of Shareable Images in the Map File ....... 5–28

5.30.5 Demangler Information Look Up Results in Linker Access

Violation ................................................ 5–29

5.30.6 Incorrect Secondary Messages for the NOGLOSYM Error Message . . . 5–29

5.30.7 Incorrect Information for Undeﬁned Symbols ................... 5–29

5.30.8 Incorrect UNMAPFIL Error . ................................ 5–29

5.30.9 Max Ident Length Change for Shareable Images in Map ........... 5–29

5.30.10 Linkage Type Check for Shareable Images . . ................... 5–29

5.30.11 Program Section Attribute ABS Ignored ....................... 5–30

5.30.12 Linker ACCVIOs when FP_MODE Literal Missing From Command

Line ................................................... 5–30

5.30.13 OpenVMS Integrity servers Object Module and Image File

Information Currently Unavailable ........................... 5–30

5.30.14 Differences Between the Integrity servers Linker and the Alpha

Linker ................................................. 5–30

5.30.15 LINK_ORDER Section Header Flag Not Supported ............... 5–30

5.30.16 Linking Against Data-Reduced ELF Object Libraries Not

Recommended ........................................... 5–31

5.30.17 Error in Handling Initialized Overlaid Program Sections Fixed . . . . . 5–31

5.30.18 Removal of Linker Qualiﬁers /EXPORT_SYMBOL_VECTOR and

/PUBLISH_GLOBAL_SYMBOLS . ............................ 5–32

5.30.19 Support for Longer Symbol Names in Options ................... 5–32

5.30.20 Better Use of Memory for Linker-Created Code Stubs . . ........... 5–32

5.30.21 Compiler Support for Demangled Symbol Names ................ 5–32

5.31 LTDRIVER: CANCEL SELECTIVE Restriction . . ................... 5–32

5.32 Mail Utility: Threads Restriction for Callable Mail .................. 5–33

5.33 OpenVMS System Dump Analyzer (SDA) ......................... 5–33

5.33.1 CLUE Commands Not Ported to OpenVMS Integrity servers ....... 5–33

5.34 PL/I Libraries Not Included in OpenVMS Integrity servers Version 8.2 . . . 5–33

5.35 POSIX Threads Library . . . .................................... 5–33

5.35.1 Support for Process-shared Objects ........................... 5–34

5.35.2 New Return Status for pthread_mutex_lock . ................... 5–34

5.35.3 Support for New API pthread_mutex_tryforcedlock_np . ........... 5–34

5.35.4 Stack Overﬂows During Exception Handling (Integrity servers

Only) .................................................. 5–35

5.35.5 THREADCP Command Behavior on Integrity Servers . . ........... 5–36

5.35.6 Floating-Point Compilations and Exceptions (Integrity servers

Only) .................................................. 5–36

5.35.7 C Language Compilation Header File Changes .................. 5–36

5.35.8 New Priority Adjustment Algorithm .......................... 5–37

5.35.9 Process Dumps ........................................... 5–37

5.35.10 Dynamic CPU Conﬁguration Changes ......................... 5–37

5.35.11 Debugger Metering Function Does Not Work . ................... 5–38

5.36 RTL Library (LIB$) .......................................... 5–38

5.36.1 RTL Library (LIB$) Help Omission ........................... 5–38

5.36.2 RTL Library (LIB$): Calling Standard Routines (Integrity servers

Only) .................................................. 5–38

5.37 Screen Management (SMG$) Documentation ....................... 5–39

5.38 SORT32 Utility . ............................................ 5–40

5.38.1 CONVERT Problem With DFS-Served Disks ................... 5–40

5.38.2 Temporary Work Files Not Always Deleted . . ................... 5–40

5.38.3 SORT/SPECIFICATION With Compound Conditions: Requirement

....................................................... 5–40

5.38.4 Performance Problem with Variable Length Records . . ........... 5–40

5.38.5 Work File Directories Restriction ............................ 5–41

5.39 Timer Queue Entries (TQEs) ................................... 5–41

5.40 Watchpoint Utility (Integrity servers Only) ........................ 5–41

5.41 Whole Program Floating-Point Mode (Integrity servers Only) .......... 5–41

6 Hardware Release Notes

6.1 USB Device Support . ........................................ 6–1

6.2 MP and BMC Console Restrictions (Integrity servers Only) ........... 6–2

6.2.1 Input, Output, and Error Device Restriction .................... 6–2

6.2.2 Remapping Ctrl/H to the Delete Key . . ....................... 6–2

6.3 AlphaServer 2100 . . . ........................................ 6–2

6.3.1 Console Display . . ........................................ 6–3

6.3.2 SCSI Controller Restriction . ................................ 6–3

6.4 AlphaServer 8200/8400: FRU Table Error . ....................... 6–4

6.5 AlphaServer ES47/ES80/GS1280 Systems . . ....................... 6–4

6.5.1 INIT Console Command Usage on ES47/ES80/GS1280 Soft

Partitions ............................................... 6–4

6.5.2 RAD Support . . . ........................................ 6–4

6.5.3 License Requirements ..................................... 6–4

6.5.4 STOP/CPU and Shutdown Behavior . . . ....................... 6–4

6.5.5 Setting Time at MBM ..................................... 6–5

6.6 AlphaServer GS Series Systems . ................................ 6–5

6.6.1 AlphaServer GS80/160/320 Systems: Device Restriction ........... 6–5

6.6.2 OpenVMS Galaxy License Enforcement . ....................... 6–5

6.6.3 Installing Licenses ........................................ 6–5

6.6.4 AlphaServer GS60/GS60E/GS140 Multiple I/O Port Module

Conﬁguration Restriction . . . ................................ 6–7

6.7 AlphaStation 200/400: ISA_CONFIG.DAT Changes Required . . ....... 6–7

6.8 AlphaStation 255: PCI Conﬁguration Restriction ................... 6–8

6.9 ATI RADEON 7000 Graphics (Integrity servers Only) . ............... 6–8

6.9.1 Integrity servers Graphics Support ........................... 6–8

6.9.2 Hardware Accelerated 3D Graphics Not Supported on RADEON 7000

....................................................... 6–9

6.10 ATI RADEON 7500 Graphics . . . ................................ 6–9

6.10.1 Resource Requirements .................................... 6–9

6.10.2 DECW$OPENGLSHR_RADEON.EXE Renamed to

DECW$MESA3DSHR_RADEON.EXE . . ....................... 6–10

6.10.3 Support Limitations ....................................... 6–10

6.10.4 Video Artifacts at High Refresh Rates . . ....................... 6–10

6.10.5 OpenGL Supports IEEE Arithmetic Only ...................... 6–10

6.10.6 DECwindows Server Hangs When Output Is Written to the Graphics

Console (OPA0) . . ........................................ 6–10

6.10.7 Monitor Must Be Connected During Initialization . ............... 6–11

6.10.8 Boot Reset Recommendation (Alpha Only) ...................... 6–11

6.10.9 No Overlay Planes ........................................ 6–11

6.10.10 Single Colormap . . ........................................ 6–11

6.10.11 Single Bit Depth for All Windows ............................ 6–11

6.10.12 Pixel Depth for Read/Write Color Map . . ....................... 6–12

6.10.13 Backing Store/Save Unders Not Supported for 3D Windows . ....... 6–12

6.10.14 Threads Restriction ....................................... 6–12

6.10.15 No Support for Single Buffered Visuals ....................... 6–12

6.10.16 No 3D Support for Color Index Mode . . . ....................... 6–12

6.10.17 Timer Mechanism ........................................ 6–12

6.11 DECwindows X11 Display Server (Alpha Only) ..................... 6–13

6.11.1 S3 Multihead Graphics .................................... 6–13

6.12 DIGITAL Modular Computing Components (DMCC) . ............... 6–13

6.12.1 Alpha 5/366 and 5/433 PICMG SBC Restriction . . ............... 6–13

6.12.2 Updating the SRM Console . ................................ 6–13

6.13 Digital Personal Workstation: Booting OpenVMS V7.3-1 and Higher .... 6–14

6.14 Dual-Controller HSGnn with Many LUNs Can Fail Under Heavy I/O

Load . . .................................................... 6–14

6.15 Open3D Graphics Licensing Change . ............................ 6–15

6.16 PowerStorm 300/350 PCI Graphics Support for OpenVMS . ........... 6–15

6.17 RFnn DSSI Disk Devices and Controller Memory Errors . . . ........... 6–16

6.18 RZnn Disk Drive Considerations ................................ 6–18

6.18.1 RZ25M and RZ26N Disk Drives: Recommendations . . . ........... 6–18

6.18.2 RZ26N and RZ28M Disks: Recommended Firmware Support ....... 6–19

6.18.3 RZ26L and RZ28 Disks: Required Firmware for Multihost Use . . . . . 6–19

6.18.3.1 Firmware Revision Level 442 Requirements ................. 6–19

6.18.3.2 Firmware Revision Level 442 Installation Procedure ........... 6–19

6.19 sx1000 Integrity Superdome ................................... 6–20

6.20 ZLX Graphics Boards Support ................................. 6–20

6.21 Recompiling and Relinking OpenVMS Device Drivers ................ 6–20

6.21.1 Alpha and VAX SCSI Device Drivers .......................... 6–20

6.21.2 OpenVMS Alpha Device Drivers . ............................ 6–21

6.22 Device Driver MON Version Handling ............................ 6–21

6.23 Possible Per-Threads Security Impact on Alpha Device Drivers ........ 6–21

6.24 Device IPL Setup for OpenVMS Alpha Drivers . . ................... 6–21

6.25 CRCTX Routines Enhanced ................................... 6–22

6.26 Adapter Release Notes ........................................ 6–22

6.26.1 Fibre Channel EFI Driver and Firmware Requirements ........... 6–22

6.26.2 Booting with Multiple Fibre Channel Boot Entries ............... 6–23

A Interlocked Memory Instructions (Alpha Only)

A.1 Required Code Checks . . . .................................... A–1

A.2 Using the Code Analysis Tool (SRM_CHECK) . . . ................... A–1

A.3 Noncompliant Code Characteristics . ............................ A–2

A.4 Coding Requirements ......................................... A–3

A.5 Compiler Versions ........................................... A–5

A.6 Recompiling Code with ALONONPAGED_INLINE or

LAL_REMOVE_FIRST . . . .................................... A–6

Index

Tables

1–1 Supported Versions of DECwindows Motif . . . ................... 1–4

1–2 Firmware Versions for Entry-Class Integrity Servers . . ........... 1–6

4–2 Patch Kits Required for Cluster Compatibility ................... 4–26

4–2 Patch Kits Required for Cluster Compatibility ................... 4–27

4–3 Galaxy Deﬁnitions ........................................ 4–30

4–4 TFF Character Fallback Tables . . ............................ 4–33

5–1 Macro-32 New Built-ins .................................... 5–19

6–1 Changes to Device Description Block .......................... 6–8

6–2 Supported Microcode Revision Levels ......................... 6–17

6–3 Commands for Updating Microcode in Certain DSSI Disk Devices . . . 6–18

6–4 Revision Level 442 Firmware Compatibility . ................... 6–19

A–1 Versions of OpenVMS Compilers . ............................ A–5

xii

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.

• Chapter 2 contains installation and support information for OpenVMS associated products.

• Chapter 3 contains release notes about the general use of the OpenVMS operating system.

• Chapter 4 contains release notes speciﬁc to the OpenVMS system management.

• Chapter 5 contains release notes that relate to programming on an OpenVMS system, including notes for compilers, linkers, and run-time library routines.

Preface

• Chapter 6 contains information pertaining to hardware that runs on the OpenVMS operating system and OpenVMS device support.

• Appendix A describes the proper use of interlocked memory instructions, which is crucial for the Alpha 21264 (EV6) processor.

Notes are organized by facility or product name when applicable.

This manual contains release notes introduced in the current release and notes from previous versions that still apply to the new release. A subheading for each release note indicates either the version of origin (for example, V8.3) or the version when an old note was last updated (for example, a note from Version 8.3 that was revised for Version 8.4 will be labeled with V8.4).

Notes from previous releases are published when:

• The information in the release note has not been documented in any other printed manual in the OpenVMS documentation set, and the note is still pertinent.

• 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, 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.com

How to Order Additional Documentation

For information about how to order additional documentation, see:

http://www.hp.com/go/openvms/doc/order

Conventions

The following conventions may be used in this manual:

Ctrl/x A sequence such as Ctrl/x indicates that you must hold down

PF1 x A sequence such as PF1 x indicates that you must ﬁrst press

Return

. . . A horizontal ellipsis in examples indicates one of the following

. . .

( ) In command format descriptions, parentheses indicate that you

the key labeled Ctrl while you press another key or a pointing device button.

and release the key labeled PF1 and then press and release another key or a pointing device button.

In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)

In the HTML version of this document, this convention appears as brackets, rather than a box.

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.

must enclose choices in parentheses if you specify more than one.

xvi

[ ] In command format descriptions, brackets indicate optional

| In command format descriptions, vertical bars separate choices

{ } In command format descriptions, braces indicate required

bold type Bold type represents the introduction of a new term. It also

italic type Italic type indicates important information, complete titles

UPPERCASE TYPE Uppercase type indicates a command, the name of a routine,

Example

- A hyphen at the end of a command format description,

numbers All numbers in text are assumed to be decimal unless

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 speciﬁcations and for a substring speciﬁcation in an assignment statement.

within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.

choices; you must choose at least one of the items listed. Do not type the braces on the command line.

represents the name of an argument, an attribute, or a reason.

of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predeﬁned code for the device type).

the name of a ﬁle, or the abbreviation for a system privilege.

This typeface indicates code examples, command examples, and interactive screen displays. In text, this type also identiﬁes URLs, UNIX commands and pathnames, PC-based commands and folders, and certain elements of the C programming language.

command line, or code line indicates that the command or statement continues on the following line.

otherwise noted. Nondecimal radixes—binary, octal, or hexadecimal—are explicitly indicated.

xvii

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 ﬁrst. Later sections group notes of interest to users of speciﬁc 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.4 New Features and Documentation Overview

• HP OpenVMS Version 8.4 Upgrade and Installation Manual

For more information about associated products, see Chapter 2 and for hardware release notes, see Chapter 6.

1.1 HP Software Technical Support Policy

HP provides software technical support for OpenVMS operating system software for the latest, currently shipping version and the immediate prior version of the product. Each version is supported for 24 months from its release date, or until the release of the second subsequent version, whichever is greater. ‘‘Version’’ is deﬁned as a release containing new features and enhancements. Patch kits and maintenance-only releases do not meet the deﬁnition of ‘‘version’’ in the context of this support policy.

Current version-level support (Standard Support or SS) and Prior Version Support (PVS) for OpenVMS operating system software is provided for OpenVMS versions in accordance with these guidelines. The current level of support for recent versions of OpenVMS Integrity servers, OpenVMS Alpha, and OpenVMS VAX is kept up to date at:

http://h71000.www7.hp.com/openvms/openvms_supportchart.html

The Operating System Support Policy applies to all OpenVMS major releases, new feature releases, and enhancement releases, which are deﬁned as follows:

• Major Releases for OpenVMS contain substantial new functionality. The version number increases to the next integer (for example, from 8.3-1H1 to

8.4). Application impact: OpenVMS internal interfaces have changed. Although

binary compatibility will be maintained for the majority of applications, independent software vendors (ISVs) should test on the new version and may need to release a new application kit. Some application partners may want to release a new application kit to take advantage of new features in the operating system.

OpenVMS Software Installation and Upgrade Release Notes 1–1

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). However, OpenVMS internal interfaces may have been modiﬁed with the addition of signiﬁcant new functionality or implementation of performance improvements. It is unlikely that a new application kit will be required for 95 percent of all applications that use documented APIs. Device driver and kernel-level applications (that is, those that use nonstandard or undocumented APIs) may need qualiﬁcation testing.

• Enhancement Releases for OpenVMS contain enhancements to existing features and maintenance updates. The version number increases to show a revision by using a dash (for example, OpenVMS Version 8.2-1).

Application impact: The release may contain new hardware support, software enhancements, and maintenance, but the changes are isolated and have no impact on applications that use published APIs. There is no need for ISVs to test on the new release or to produce a new application kit.

• Hardware Releases provide current version-level support until 12 months after a subsequent release containing that particular hardware support. Hardware releases are shipped with new hardware sales only and are not distributed to existing service customers.

The following OpenVMS core products are supported at the same level (Standard Support or Prior Version Support) and duration as the operating system version on which they ship:

• HP Advanced Server for OpenVMS

• HP DECnet (Phase IV)

• HP DECnet-Plus for OpenVMS

• HP OpenVMS Cluster Client Software

• HP OpenVMS Cluster Software for OpenVMS

• HP PathWorks or HP PATHWORKS for OpenVMS

• HP RMS Journaling for OpenVMS

• HP TCP/IP Services for OpenVMS

• HP Volume Shadowing for OpenVMS

• HP DECram for OpenVMS

These products require their own individual support contracts and are not included in the operating system support contract.

1.2 General Application Compatibility Statement

OpenVMS has consistently held the policy that published APIs are supported on all subsequent releases. It is unlikely, applications that use published APIs will require changes to support a new release of OpenVMS. APIs may be "retired", and thus removed from the documentation; however, the API will continue to be available on OpenVMS as an undocumented interface.

1–2 OpenVMS Software Installation and Upgrade Release Notes

OpenVMS Software Installation and Upgrade Release Notes

1.3 Obtaining Remedial Kits

Remedial kits for OpenVMS ﬁeld test Version 8.4 will be made available in the ﬁeld test website.

1.4 Networking Options

V8.4

OpenVMS provides customers with the ﬂexibility 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 can operate with both HP and third-party networking products.

During the main installation procedure for OpenVMS Version 8.4, you have the option of installing the following supported HP networking software:

• Either HP DECnet-Plus Version 8.4 for OpenVMS or HP DECnet Phase IV Version 8.4 for OpenVMS. (Note that both DECnet products cannot run concurrently on your system.)

DECnet-Plus contains all the functionality of the DECnet Phase IV product, and the ability to run DECnet over TCP/IP or OSI protocols.

1.3 Obtaining Remedial Kits

For information about how to conﬁgure and manage your HP networking software after installation, refer to the TCP/IP, DECnet-Plus, or DECnet documentation. The manuals are available in online format on the OpenVMS Documentation website. You must use HP TCP/IP Services for OpenVMS Version 5.7 after upgrading to OpenVMS Version 8.4.

1.5 Disk Incompatibility with Older Versions of OpenVMS

V8.3

The OpenVMS Version 8.4 installation procedure initializes the target disk with volume expansion (INITIALIZE/LIMIT). This renders the disk incompatible with versions of OpenVMS prior to Version 7.2. In most cases, this does not present a problem. However, if you intend to mount this new disk on a version of OpenVMS prior to Version 7.2, you must ensure that the disk is compatible for that operating system version. For detailed instructions, see the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

Note that by taking these steps, your new system disk might include a relatively large minimum allocation size (as deﬁned by /CLUSTER_SIZE). As a result, small ﬁles will use more space than necessary. Therefore, perform these steps only for system disks that must be mounted on versions of OpenVMS prior to Version 7.2.

Note

ODS-5 disks are also incompatible with versions of OpenVMS prior to Version 7.2.

OpenVMS Software Installation and Upgrade Release Notes 1–3

OpenVMS Software Installation and Upgrade Release Notes

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

OpenVMS Alpha Version 8.4 DECwindows Motif for OpenVMS Alpha Version

The DECwindows Motif software relies on speciﬁc versions of OpenVMS server and device driver images. Ensure you install or upgrade to the version of DECwindows Motif that is appropriate to your operating system environment, as noted in Table 1–1.

For information on support for prior versions of DECwindows Motif, see the HP DECwindows Motif for OpenVMS Release Notes.

For detailed information about installing the DECwindows Motif software, see the HP DECwindows Motif for OpenVMS Installation Guide.

1.7 OpenVMS Integrity server Users

The following notes are primarily of interest to users of OpenVMS Integrity servers.

1.7.1 Storage Controllers

V8.3

The HP sx1000 chipset for HP Integrity servers provides the CPU, memory, and I/O subsystem to the HP Integrity rx7620, HP Integrity 8620, and HP Integrity Superdome servers. The cell controller is combined with four CPU chips into the computing cell in the sx1000 chipset architecture. The cell controller chip also provides paths to the I/O devices and off-cell memory.

DECwindows Motif for OpenVMS Integrity servers Version 1.7

1.7

The rx7620, rx8620, and Superdome servers provide a varying number of sx1000 chipset cells. The rx7620 provides up to 2 cells (8 CPUs), the rx8620 provides up to 4 cells (16 CPUs), and the Superdome provides up to 16 cells (64 CPUs).

OpenVMS Integrity servers Version 8.3 supports two primary storage interconnects:

• The SCSI storage type is U320, used for core I/O for certain Integrity server systems, as well as the A7173A U320 SCSI adapter. For connection to external SCSI storage, the supported storage shelves are the DS2100 or the MSA30.

• The external Fibre Channel storage connection is through the dual-port 2 GB Fibre Channel Universal PCI-X adapter (A6826A). This adapter allows connectivity to any external SAN-based Fibre Channel storage infrastructure supported by OpenVMS.

Support for SAS based storage is provided from OpenVMS Integrity servers Version 8.3-1H1 onwards.

1–4 OpenVMS Software Installation and Upgrade Release Notes

OpenVMS Software Installation and Upgrade Release Notes

1.7 OpenVMS Integrity server Users

Restrictions

Customers who used any earlier evaluation or ﬁeld test kits should note the following important considerations:

• The U160 adapter (A6829A) is not ofﬁcially 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 conﬁgurations as long as the system remains as it is currently conﬁgured. Any additional adapters, or movement to another server environment, requires you to move to U320 SCSI adapter technology.

• In the case of Fibre Channel, customers might have been running with the AB232A or KGPSA-EA FC adapters. These adapters are not supported on OpenVMS Integrity servers Version 8.3 and later, and customers using them must upgrade to the A6826A FC adapter before running production applications on Version 8.2.

1.7.2 U160 SCSI Support for rx7620 and rx8620

V8.3

The rx7620 and rx8620 systems have an internal U160 (SCSI), which is included in the system as core I/O. The internal connections to the racks of SCSI disks (which appear on the front of the system box) are supported by OpenVMS. The internal box also has two external ports. HP does not support attaching them (using cables) to a SCSI rack.

1.7.3 Clearing the System Event Log on Integrity servers

V8.3

HP Integrity servers maintain a System Event Log (SEL) within the system console storage. OpenVMS Integrity servers automatically transfers the contents of the SEL into the OpenVMS error log. If you are operating from the console during a successful boot operation, you might see a message indicating that the Baseboard Management Controller (BMC) SEL is full. You can continue when the BMC SEL is full by following the prompts; OpenVMS will process the contents of the SEL. To clear the SEL manually, enter the following command at the EFI Shell prompt:

Shell> clearlogs SEL

This command deletes the contents of the SEL. The command is available with current system ﬁrmware versions.

If your Integrity server is conﬁgured with a Management Processor (MP) and you see a BMC event log warning while connected to the MP console, you can clear the BMC event log by using MP. Press Ctrl/B to drop to the MP> prompt. At the MP> prompt, enter SL (from the main menu) and use the C option to clear the log.

HP recommends that you load and use the most current system ﬁrmware. For more information about updating the system ﬁrmware, see the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

OpenVMS Software Installation and Upgrade Release Notes 1–5

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 ﬁrmware for each of the supported Integrity servers.

For the entry-class Integrity servers, HP recommends that use the most current system ﬁrmware. For information about updating the system ﬁrmware for entry-class Integrity servers, see the HP OpenVMS Version 8.4 Upgrade and Installation Manual. (For rx7620, rx8620, and Superdome servers, call HP Customer Support to update your ﬁrmware.)

Table 1–2 lists the recommended ﬁrmware versions for entry-class Integrity servers:

Table 1–2 Firmware Versions for Entry-Class Integrity Servers

System

rx1600 4.27 4.01 E.03.30 N/A

rx1620 4.27 4.01 E.03.30 N/A

rx2600 2.31 1.53 E.03.32 N/A

rx2620 4.29 4.04 E.03.32 N/A

rx4640 4.29 4.06 E.03.32 1.10

rx2660* 4.11 5.24 F.02.23 N/A

rx3600* 4.11 5.25 F.02.23 1.23

rx6600* 4.11 5.25 F.02.23 1.23

System Firmware

BMC Firmware

MP Firmware

DHPC Firmware

*If you have Intel Itanium 9100 processors on your rx2660, rx3600, or rx660, you need ﬁrmware that is at least one version greater than the ones listed here.

For cell-based servers, you must access the MP Command Menu and issue the sysrev command to list the MP ﬁrmware revision level. The sysrev command is available on all HP Integrity servers that have an MP. Note the EFI info fw command does not display the Management Processor (MP) ﬁrmware version on cell-based Integrity servers.

To check ﬁrmware version information on an entry-class Integrity server that does not have the MP, enter the info fw command at the EFI prompt. Note the following example:

Shell> INFO FW

FIRMWARE INFORMATION

Firmware Revision: 2.13 [4412]

PAL_A Revision: 7.31/5.37 PAL_B Revision: 5.65 HI Revision: 1.02

SAL Spec Revision: 3.01 SAL_A Revision: 2.00 SAL_B Revision: 2.13

EFI Spec Revision: 1.10 EFI Intel Drop Revision: 14.61 EFI Build Revision: 2.10

POSSE Revision: 0.10

1–6 OpenVMS Software Installation and Upgrade Release Notes

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 ﬁrmware revision is 2.13.

" The BMC ﬁrmware revision is 2.35.

# The MP ﬁrmware revision is E.02.29.

The HP Integrity rx4640 server contains Dual Hot Plug Controller (DHPC) hardware with upgradeable ﬁrmware. To check the current version of your DHPC ﬁrmware, use the EFI command INFO CHIPREV, as shown in the following example. The hot-plug controller version will be displayed. A display of 0100 indicates version 1.0; a display of 0110 means version 1.1.

Shell> INFO CHIPREV

CHIP REVISION INFORMATION

Chip Logical Device Chip Type ID ID Revision

------------------- ------- ------ -------Memory Controller 0 122b 0023 Root Bridge 0 1229 0023

Host Bridge 0000 122e 0032 Host Bridge 0001 122e 0032 Host Bridge 0002 122e 0032 Host Bridge 0004 122e 0032

HotPlug Controller 0 0 0110

Host Bridge 0005 122e 0032

HotPlug Controller 0 0 0110 Host Bridge 0006 122e 0032 Other Bridge 0 0 0002

Other Bridge 0 0 0008

Baseboard MC 0 0 0235

For instructions on how to access and use EFI, see the HP OpenVMS Version 8.4 Upgrade and Installation Manual. For more information, refer to the hardware

documentation that is provided with your server.

For instructions on upgrading your ﬁrmware for your entry-class Integrity servers, see the HP OpenVMS Version 8.4 Upgrade and Installation Manual.To upgrade ﬁrmware for the rx7620, rx8620, or Superdome, contact HP Customer Support.

1.7.5 Booting from the Installation DVD

V8.2

On Integrity servers with the minimum amount of supported memory (512 MB), the following message appears when booting from the installation DVD:

********* XFC-W-MemmgtInit Misconfigure Detected ******** XFC-E-MemMisconfigure MPW_HILIM + FREEGOAL > Physical Memory and no reserved memory for XFC XFC-I-RECONFIG Setting MPW$GL_HILIM to no more than 25% of physical memory XFC-I-RECONFIG Setting FREEGOAL to no more than 10% of physical memory ********* XFC-W-MemMisconfigure AUTOGEN should be run to correct configuration ******** ********* XFC-I-MemmgtInit Bootstrap continuing ********

OpenVMS Software Installation and Upgrade Release Notes 1–7

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 Conﬁguration Manager message are new to OpenVMS Version 8.4 and are seen only when using USB or vMedia devices for booting the Integrity rx2660, rx3600, and rx6600 servers.

1.7.7 HP DECwindows Motif Release Notes

The following DECwindows Motif release notes are of interest to OpenVMS Integrity server users.

1.7.7.1 Keyboard Support

V8.2

The only model keyboard supported on HP DECwindows Motif for OpenVMS Integrity servers is the LK463 (AB552A for Integrity servers) keyboard. Although other types of keyboards may function in the OpenVMS Integrity servers environment, HP does not currently support them.

1.8 OpenVMS Alpha Users

The following notes are primarily of interest to users of OpenVMS Alpha systems.

1.8.1 Firmware for OpenVMS Alpha Version 8.4

V8.4

OpenVMS Alpha Version 8.4 was tested with the platform-speciﬁc ﬁrmware included on Alpha Systems Firmware CD Version 7.3. For older platforms no longer included on the Firmware CD, OpenVMS Alpha Version 8.4 was tested with the latest released ﬁrmware version. HP recommends upgrading to the latest ﬁrmware before upgrading OpenVMS.

Read the ﬁrmware release notes before installing the ﬁrmware. For Version 7.3 and the latest ﬁrmware information, see:

http://h18002.www1.hp.com/alphaserver/firmware/

1.8.2 Upgrade Paths

V8.4

If you are running OpenVMS Alpha or Integrity servers Version E8.4, you can upgrade directly to Version F8.4. If you are running other versions of OpenVMS, you must ﬁrst install Version E8.4 and you can upgrade to Version F8.4.

You can upgrade directly to OpenVMS Alpha Version 8.4 from only the following versions of OpenVMS Alpha.

For Alpha:

Version 7.3-2 to V8.4 Version 8.2 to V8.4

1–8 OpenVMS Software Installation and Upgrade Release Notes

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 ﬁrst 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.html

If you are running other versions of OpenVMS that are no longer supported, you must do multiple upgrades in accordance with upgrade paths that were documented for earlier versions.

Cluster Concurrent Upgrades

During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade and reboot each computer. Once you reboot, each computer will be running the upgraded version of the operating system.

Cluster Rolling Upgrades

During a cluster rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster (a mixed-version cluster). There must be more than one system disk. The systems that are not being upgraded remain available.

Only the following OpenVMS Alpha and OpenVMS VAX versions are supported in mixed-version clusters that include OpenVMS Alpha Version 8.4:

Version 7.3-2 (Alpha) Version 7.3 (VAX)

If you are upgrading in a cluster environment, rolling upgrades are supported from Version 7.3-2 of the OpenVMS Alpha operating system. If you have other versions in a cluster, you cannot do a rolling upgrade until those versions are upgraded to a supported version.

Mixed-version support for these versions require the installation of one or more remedial kits. For more information, see Section 4.36.1.

Note

HP currently supports only two versions of OpenVMS (regardless of architecture) running in a cluster at the same time. Only two architectures are supported in the same OpenVMS Cluster. Warranted support is provided for pairings with OpenVMS Integrity servers Version

8.4. For more information, refer to the HP OpenVMS Version 8.4 Upgrade and Installation Manual.

For a discussion of warranted pairs and migration pairs of OpenVMS operating systems, for complete instructions for installing or upgrading to OpenVMS Alpha Version 8.4, and for instructions on installing OpenVMS Integrity servers Version

8.4, refer to the HP OpenVMS Version 8.4 Upgrade and Installation Manual.

OpenVMS Software Installation and Upgrade Release Notes 1–9

OpenVMS Software Installation and Upgrade Release Notes

1.9 Kerberos for OpenVMS

V8.3

Before conﬁguring or starting Kerberos, check the HP TCP/IP local host database to determine whether your hostname deﬁnition is the short name (for example, node1) or the fully qualiﬁed domain name (FQDN) (for example, node1.hp.com).

If your host name deﬁnition is the short name, you must run TCPIP$CONFIG to change the deﬁnition to the fully qualiﬁed name.

The following example shows that the hostname is the short name:

$ TCPIP SHOW HOST/LOCAL NODE1

LOCAL database

Host address Host name

1.2.3.4 node1

The following log is an example of how to change the host name deﬁnition to the FQDN.

$ @SYS$STARTUP:TCPIP$CONFIG

TCP/IP Network Configuration Procedure

This procedure helps you define the parameters required to run HP TCP/IP Services for OpenVMS on this system.

Checking TCP/IP Services for OpenVMS configuration database files.

HP TCP/IP Services for OpenVMS Configuration Menu

Configuration options:

1 - Core environment 2 - Client components 3 - Server components 4 - Optional components

5 - Shutdown HP TCP/IP Services for OpenVMS 6 - Startup HP TCP/IP Services for OpenVMS 7 - Run tests

A - Configure options 1 - 4

[E] - Exit configuration procedure

Enter configuration option: 1

HP TCP/IP Services for OpenVMS Core Environment Configuration Menu

Configuration options:

1 - Domain 2 - Interfaces 3 - Routing 4 - BIND Resolver 5 - Time Zone

A - Configure options 1 - 5

[E] - Exit menu

Enter configuration option: 2

HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu

Hostname Details: Configured=node1, Active=node1

Configuration options:

1 - WE0 Menu (EWA0: TwistedPair 1000mbps) 2 - 1.2.3.4/21 node1 Configured,Active

1–10 OpenVMS Software Installation and Upgrade Release Notes

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.4/21 node1 Configured,Active WE0

Configuration options:

1 - Change address 2 - Set "node1" as the default hostname 3 - Delete from configuration database 4 - Remove from live system 5 - Add standby aliases to configuration database (for failSAFE IP)

[E] - Exit menu

Enter configuration option: 1

IPv4 Address may be entered with CIDR bits suffix. E.g. For a 16-bit netmask enter 10.0.1.1/16

Enter IPv4 Address [1.2.3.4/21]: Enter hostname [node1]: node1.hp.com

Requested configuration:

Address : 1.2.3.4/21

Netmask : 255.255.248.0 (CIDR bits: 21)

Hostname : node1.hp.com

* Is this correct [YES]:

"node1" is currently associated with address "1.2.3.4". Continuing will associate "node1.hp.com" with "1.2.3.4".

* Continue [NO]: YES Deleted host node1 from host database Added hostname node1.hp.com (1.2.3.4) to host database * Update the address in the configuration database [NO]: YES Updated address WE0:1.2.3.4 in configuration database * Update the active address [NO]: YES WE0: delete active inet address node1.hp.com Updated active address to be WE0:1.2.3.4

To exit the TCP/IP Services conﬁguration menus and return to the DCL ($) prompt, type E three times.

To verify the change, enter the following command:

$ TCPIP SHOW HOST/LOCAL NODE1

LOCAL database

Host address Host name

1.2.3.4 node1.hp.com

If you have not previously conﬁgured an earlier version of Kerberos on your system, or if you changed your TCP/IP hostname deﬁnition to the FQDN as shown in the example, you must run the Kerberos conﬁguration program before you start Kerberos.

To reconﬁgure Kerberos, enter the following command:

$ @SYS$STARTUP:KRB$CONFIGURE

OpenVMS Software Installation and Upgrade Release Notes 1–11

OpenVMS Software Installation and Upgrade Release Notes

1.9 Kerberos for OpenVMS

After you have a valid conﬁguration, 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. If you are upgrading from a previous version of OpenVMS that had Encrypt and SSL products installed, edit SYS$MANAGER:SYSTARTUP_VMS.COM to remove the calls to SYS$STARTUP:ENCRYPT_ START.COM and SYS$STARTUP:SSL$STARTUP.COM. This will prevent these command procedures from executing twice.

1.11 Encryption for OpenVMS

V8.3

When you install or upgrade OpenVMS, Encryption for OpenVMS creates its own ENCRYPT and DECRYPT commands. Encryption for OpenVMS starts automatically (after SSL for OpenVMS, which also starts automatically). For more information about Encryption for OpenVMS, see HP OpenVMS Version 8.3 New Features and Documentation Overview.

With Version 8.3 of OpenVMS, the DCL command DECRAM is removed because it conﬂicts with the new DECRYPT command (DECRYPT overwrites the default deﬁnition of DECRAM, which you might have been using to start DECram). You should update any command procedures that use the DECRAM command so that they use the foreign command style of DCL. For example:

$ DECRAM == "$MDMANAGER"

This change affects the use of the DCL command only; all other aspects of the DECram product remain the same. If you have older versions of DECram on your OpenVMS Alpha system, you must remove them before upgrading. See Section 1.12.

1.12 Upgrading HP DECram V3.n

V8.2

Starting with OpenVMS Alpha and OpenVMS Integrity servers Version 8.2, DECram ships with the OpenVMS operating system as a System Integrated Product (SIP). If you upgrade to Version 8.3 on an OpenVMS Alpha system from OpenVMS Version 7.3-2, you must remove any old versions of DECram. Refer to the HP OpenVMS Version 8.4 Upgrade and Installation Manual for details.

Note

More DECram release notes are included in Section 2.17.

1–12 OpenVMS Software Installation and Upgrade Release Notes

OpenVMS Software Installation and Upgrade Release Notes

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 ﬁrst run after the upgrade.

To convert the database, issue the following LANCP commands to convert the device database and then to stop LANACP so it can be restarted to use the new database:

$ LANCP LANCP> CONVERT DEVICE_DATABASE LANCP> SET ACP/STOP LANCP> EXIT $ @SYS$STARTUP:LAN$STARTUP

1.14 DECnet-Plus Requires a New Version

V7.3-2

When you install or upgrade to OpenVMS Alpha Version 7.3-2 or later, you must also install a new version of DECnet-Plus. One of the reasons that make this necessary is a change in AUTOGEN behavior that was introduced in Version

7.3-2.

Unlike the behavior of previous versions, DECnet-Plus for OpenVMS Version

7.3-2 and later now provides product information in NEWPARAMS.DAT records, as required by AUTOGEN. AUTOGEN anticipates this change in DECnet-Plus, so AUTOGEN does not print any warnings when it removes "bad" records from CLU$PARAMS.DAT; AUTOGEN presumes these records were made by an older DECnet-Plus kit and will be replaced by the new DECnet-Plus kit. So, under normal conditions, you will not see any striking differences in behavior during an OpenVMS Version 7.3-2 or later installation or upgrade.

However, if other products do not provide product information in NEWPARAMS.DAT records, as now required by AUTOGEN, AUTOGEN prints warning messages to both the report and the user’s SYS$OUTPUT device. The warnings state that AUTOGEN cannot accept the parameter assignment found in NEWPARAMS.DAT (because no product name is attached) and that no records will be added to CLU$PARAMS.DAT. Because no records are added, the expected additions or other alterations to SYSGEN parameters will not be made, which could lead to resource exhaustion. Developers and testers of software products should be aware of this requirement; it may also be of interest to system managers.

This new behavior is intended to protect both the users and providers of layered products.

A description of NEWPARAMS.DAT and CLU$PARAMS.DAT is included in the AUTOGEN chapter of the HP OpenVMS System Management Utilities Reference Manual.

OpenVMS Software Installation and Upgrade Release Notes 1–13

OpenVMS Software Installation and Upgrade Release Notes

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-1, you must manually remove the TIE kit before you upgrade to OpenVMS Integrity servers Version 8.3.

Use the following command to remove the TIE product kit:

$ PRODUCT REMOVE TIE

Do not install the TIE product kit, HP I64VMS TIE V1.0, on OpenVMS Integrity servers Version 8.2-1 or later.

1.16 Installation Failure of Layered Products on Alternate Devices or Directories

V8.3

By default the system device in the product to an alternate device or directory using the qualiﬁer (or by deﬁning the logical name fail with an error message stating that one of the following ﬁles cannot be found:

[SYSLIB]DCLTABLES.EXE,[SYSHLP]HELPLIB.HLB

happens, answer YES to the question, "Do you want to terminate? [YES]," and then retry the installation using the

PRODUCT INSTALL

SYS$COMMON

command installs a layered product on the

directory tree. If you choose to install a layered

/DESTINATION=dev:[dir]

PCSI$DESTINATION

,or

[SYSLIB]STARLET*.*

/NORECOVERY_MODE

), the installation may

. If this

qualiﬁer.

1–14 OpenVMS Software Installation and Upgrade Release Notes

+ 146 hidden pages