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

OpenVMS Associated Products Release Notes

This chapter contains information about OpenVMS associated products. Notes speciﬁcally 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.1 Associated Product Support

The Software Public Rollout Reports for OpenVMS lists the availability of HP software products shipping on the Software Products Library kits (CD–ROM consolidations) for OpenVMS Alpha and OpenVMS VAX and on the Layered Product Library kits (DVD consolidation) for OpenVMS Integrity servers.

The reports contain the product name and version, the operating system version required to support the product, and the volume ship date for the product. The information in these tables is continually evolving and is subject to change. The reports are intended for public distribution and are updated monthly. The information is not provided in these release notes because of the changing nature of the information.

The Software Public Rollout Reports for OpenVMS is available at:

http://h71000.www7.hp.com/openvms/os/swroll/

If you do not have Internet access, you can ﬁnd the operating system support information on any of the quarterly Software Products Libraries in the following ﬁles:

[README]SW_COMPAT_MATRIX.PS [README]SW_COMPAT_MATRIX.TXT

The Software Public Rollout Reports are also available from your HP support representative.

Because of a change in OpenVMS Version 7.3-2 and later, BASIC versions prior to V1.5A cannot create the BASIC$STARLET library ﬁle during installation.

Earlier versions of BASIC can install on OpenVMS Version 7.3-2 and later, provided you do not request the option to build the STARLET library ﬁle. Also, previously installed BASIC compilers and previously created STARLET library ﬁles will continue to function after upgrading an older OpenVMS system to Version 7.3-2 and later.

It is only the BASIC$STARLET library ﬁle creation that does not work on OpenVMS Version 7.3-2 and later. The BASIC V1.5A kit contains an enhanced installation procedure that correctly builds the STARLET library ﬁle on OpenVMS Version 7.3-2 and later.

BASIC V1.6 is available on the latest consolidated layered product CD.

OpenVMS Associated Products Release Notes 2–1

OpenVMS Associated Products Release Notes

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.4 Problem Accessing DFS Mounted Disk

V8.4

When accessing an ODS-5 disk over DFS, if the path speciﬁcation from the client includes the MFD, the access fails with the following error message as shown in the example. If the path speciﬁcation does not include the MFD, the access succeeds.

Example:

Let the access point be DKA100:[USERS] and the client DFS disk be DFSC1001.

$ DIR DFSC1001:[000000] ! fails with the following error message:

%DIRECT-E-OPENIN, error opening DFSC1001:[000000]*.*;* as input -RMS-E-DNF, directory not found

-SYSTEM-W-NOSUCHFILE, no such file

$ TYPE DFSC1001:[000000]file.dat ! fails with the following error message: where: file.dat is a file under USERS.DIR.

%TYPE-W-SEARCHFAIL, error searching for DFSC1001:[000000]file.dat

-RMS-E-DNF, directory not found

-SYSTEM-W-NOSUCHFILE, no such file

$ DIR DFSC1001:[SUBDIR] ! works as expected where: SUBDIR is a subdirectory under USERS.DIR.

2.5 HP DCE for OpenVMS Restriction (Integrity servers Only)

V8.4

On OpenVMS Version 8.4, if you install HP DCE for OpenVMS Version 3.2 by selecting Install or Upgrade Layered Products from the Install menu, it fails with the following error message:

%PCSI-E-ERROWNER, error in owner specification ’DCE$SERVER’

-SYSTEM-E-NORIGHTSDB, rights database file not found %PCSI-E-OPFAILED, operation failed

2–2 OpenVMS Associated Products Release Notes

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 ﬁle that contains a self-extracting executable ﬁle. The XML-C installation documentation describes how to install the product by using this executable ﬁle. To obtain the executable ﬁle, extract it from the ZIP ﬁle.

2.7 OpenVMS e-Business and Integration Infrastructure Package

V8.3-1H1

The OpenVMS e-Business and Integration Infrastructure Package for OpenVMS is contained on two CDs that are formatted so that they appear as a Files-11 ﬁle structure to an OpenVMS system and an ISO 9660 ﬁle structure to a Windows, Linux, or UNIX system.

Installation

The component installation kits and documentation are split across the two CDs. Component installation can be done only on an OpenVMS Alpha system from the speciﬁc CD designated in the top-level

Documentation

For OpenVMS systems, partial component documentation is viewable based on which CD is mounted for use. Component documentation is available only for the components present on the speciﬁc CD.

For Windows, Linux, or UNIX systems, complete component documentation is viewable on both CDs.

2.8 Updates to Freeware Readme File

V8.3-1H1

An update to the [FREEWARE]FREEWARE_README.TXT, included on each OpenVMS Freeware CD, is available for download from the OpenVMS Freeware website at:

http://h71000.www7.hp.com/openvms/freeware/index.html

This updated ﬁle includes the correction to the displayed version number from V7.0 to the intended and expected V8.0, as well as additional updates and corrections.

index.html

ﬁle.

As is traditional with the OpenVMS Freeware, all updates to existing ﬁles and new packages are available at the OpenVMS Freeware website.

OpenVMS Associated Products Release Notes 2–3

OpenVMS Associated Products Release Notes

2.9 CMAP Files Added

V8.2

The following new CMAP ﬁles 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.2, you may notice changes in the handling of I/O run-time diagnostics and RMS special registers on OpenVMS Alpha Version 7.2 and higher. In particular, a long ﬁle name that produced RMS$_FNM under versions of OpenVMS Alpha prior to Version 7.2 now produces RMS$_CRE on OpenVMS Alpha Version 7.2 and higher. You do not need to use the new ODS-5 support to see the RMS differences.

2.11 COM for HP OpenVMS (Alpha Only)

The following release notes pertain to HP COM for OpenVMS.

2.11.1 COM for OpenVMS Support

V8.2

HP COM Version 1.4 for OpenVMS is currently supported on OpenVMS Alpha Version 7.3-2 and 8.2. For the latest information about COM for OpenVMS, refer to the following website:

http://h71000.www7.hp.com/openvms/products/dcom/

2.11.2 Registry Access Error with Heavy Load of Applications

V7.3-2

You might get an ‘‘Error accessing registry database, contact system manager (0x000025fc)’’ message if you run a heavy load of COM for OpenVMS applications with the CTLPAGES value set to 256 or less. Set the CTLPAGES value to 512 to avoid this problem.

2.12 DECdfs Version 2.4 Required for OpenVMS Version 8.3

V8.3

DECdfs Version 2.4 is required for OpenVMS Version 8.3. If you try to use an older version of DECdfs, you will get an error message.

2–4 OpenVMS Associated Products Release Notes

OpenVMS Associated Products Release Notes

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

• FORMS_WEB$STARTUP.COM

• FORMS_WEB_CONFIG.COM

2. Ensure that the Java environment is set up systemwide for all processes. HP recommends adding the Java environment setup to the system’s SYSLOGIN.COM ﬁle.

3. Ensure that the browser clients use the Sun Java Plugin Version 1.2.2, as stated in the SPD and the Administrative guide.

2.14 DEC PL/I: RTL Support for OpenVMS

V7.3

There is a known incompatibility between the PL/I RTL distributed with the OpenVMS operating system and the more recent PL/I RTL owned and distributed by Kednos Corporation. The older version shipped with the OpenVMS operating system may overwrite a newer version. The image effected is SYS$LIBRARY:DPLI$RTLSHR.EXE.

OpenVMS distributes the following version of the ﬁle, which can be identiﬁed by using the DCL command ANALYZE/IMAGE:

Image Identification Information

image name: "DPLI$RTLSHR" image file identification: "V4.0-6"

If you execute an ANALYZE/IMAGE command before upgrading to OpenVMS Version 7.3 or higher and ﬁnd a newer version of DPLI$RTLSHR.EXE, you can either copy it and restore it after the upgrade or reinstall the PL/I kit.

Any questions about DEC PL/I and VAX PL/I should be directed to Kednos Corporation:

Phone: (831) 373-7003 Email: tom@kednos.com

See a related note in Section 5.34.

2.15 FMS Kits

V8.3

You can install either of the following FMS kits (or later versions) on both OpenVMS Alpha and OpenVMS Integrity servers:

Full kit: HPFMS025

OpenVMS Associated Products Release Notes 2–5

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 Conﬁguration Manager (Alpha Only)

The Graphical Conﬁguration 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.17 HP DECram

This section contains release notes pertaining to DECram.

Note

Refer to Section 1.12 for more information on HP DECram.

2.17.1 DECram Available with OpenVMS Version 8.2 and later

V8.2

Starting with OpenVMS Alpha and Integrity servers Version 8.2, DECram ships with the OpenVMS operating system as a System Integrated Product (SIP). Users are still required to have a DECram license. The DECram driver is located in SYS$COMMON:[SYS$LDR]. Alpha users should remove any remaining SYS$MDDRIVER images in the system-speciﬁc directories ([SYSx.SYS$LDR]). For details about removing old versions of DECram before you upgrade to Version

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

If you try to load any old versions of DECram, you will get the following error message:

SYSTEM-W-SYSVERDIF, system version mismatch; please relink No older versions of DECram are supported on OpenVMS Version 8.2. DECram Version 2.5 will continue to be supported on VAX systems only.

2.17.2 Conﬂict with DECRYPT DCL Command

V8.2

The Encryption for OpenVMS Alpha layered product creates its own DCL command DECRYPT at installation time. DECRYPT then overwrites the default deﬁnition of DECR, which users might have been using to invoke DECram.

If both products are installed, you can access the DECram interface by deﬁning a DCL foreign command symbol such as the following:

$ DECRAM == "$MDMANAGER"

2.18 HP DECwindows Motif for OpenVMS

This section contains release notes pertaining to the HP DECwindows Motif for OpenVMS product.

2–6 OpenVMS Associated Products Release Notes

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.3-2

In DECwindows Motif Version 1.3 for OpenVMS Alpha, signiﬁcant changes were made to the DECwindows Motif transport library to accommodate multithreading and the communication needs of the Inter-Client Exchange (ICE) protocol, LowBandwidth X (LBX) proxy server, and Input Method servers. As a result, HP has discontinued support for user-written network transports on systems running DECwindows Motif Version 1.3 or later.

All existing transports (DECnet, TCP/IP, LAT, and LOCAL) remain available and function as expected. However, HP no longer provides support for designing and implementing user-written transports based on the updated transport interface. The VMS DECwindows Transport Manual has been archived, and the new libraries are not publicly available.

If you have implemented a custom transport and want to migrate that transport to the DECwindows Motif Version 1.5 or greater environment, contact your HP support representative to develop a migration strategy.

2.19 HP Secure Web Server Version Support

V8.2

OpenVMS Alpha Version 7.3-2 and OpenVMS Version 8.2 (Alpha and Integrity servers) are the last releases on which the Secure Web Server (SWS) Version

1.3-* is supported. OpenVMS Alpha Version 7.3-2 is the last release on which

SWS Version 2.0 is supported.

The functional replacement for SWS Version 1.3-* and SWS Version 2.0 is SWS Version 2.1. All future new features and enhancements to SWS will be provided beginning with SWS Version 2.1, which is based on the Apache 2.0.* open source code base.

SWS Version 1.3-* and SWS Version 2.0 will be supported while OpenVMS Alpha Version 7.3-2 is in Prior Version Support (PVS) status, and SWS Version 1.3-* will be supported as long as OpenVMS Version 8.2 is supported. Support for these SWS versions will include remedial ﬁxes and security ﬁxes as deemed appropriate.

2.20 HP Pascal for OpenVMS Alpha Systems

The following release notes pertain to HP Pascal for OpenVMS Alpha systems.

OpenVMS Associated Products Release Notes 2–7

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 ﬁles 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 ﬁles. Also, previously installed Pascal compilers and previously created STARLET library ﬁles will continue to function after upgrading an older OpenVMS system to Version 7.3-2 or later.

It is only the STARLET library creation portion of the Pascal installation that does not work on OpenVMS Version 7.3-2 or later. The Pascal V5.8A kit contains an enhanced installation procedure to correctly build the STARLET library ﬁles on OpenVMS Version 7.3-2 or later.

Pascal V5.8A is available on the latest consolidated layered product CD.

2.20.2 Installing HP Pascal After an Upgrade (Alpha Only)

V7.3

This note applies to any version of HP Pascal and any version of the OpenVMS Alpha operating system.

After upgrading OpenVMS, you should reinstall HP Pascal to produce new versions of STARLET.PAS and other deﬁnition ﬁles to match the upgraded system.

If you do not reinstall HP Pascal after upgrading OpenVMS, the compiler on your system will still work correctly. However, STARLET.PAS and the other deﬁnition ﬁles will not contain any new or corrected deﬁnitions supplied by the OpenVMS upgrade.

2.21 WEBES and SEA Support on Integrity servers

V8.3

The latest version of WEBES (WEBased Enterprise Services) can be obtained from the WEBES homepage at:

http://h18000.www1.hp.com/support/svctools/

2–8 OpenVMS Associated Products Release Notes

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. Unlike other languages, FORSYSDEF.TLB ships with the FORTRAN compiler and is built against the lowest OS supported. In a future release, we will be providing OpenVMS V8.4 based FORSYSDEF library which contains the SYS$GETTIM_PREC system service declarartion along with the usual library built against the lowest OS.

3.2 Problem With F$GETSYI("RAD_CPUS")

V8.4

On a cell-based Integrity server system containing 64 CPUs, with both cell local memory (CLM) and interleaved memory (ILM) conﬁgured, the output of F$GETSYI("RAD_CPUS") does not include the 64th CPU as a member of the base RAD.

3.3 HP Code Signing Service for OpenVMS Support

V8.4

HP Code Signing Service (HPCSS) for OpenVMS supports PCSI and VMSINSTAL based kits.

3.4 Symbolic Links Implementation Changes

V8.4

Symbolic links (Symlinks) was ﬁrst introduced with OpenVMS Version 8.3. The internal implementation of Symlinks has been improved in OpenVMS Version

8.4.

3.4.1 Logical Names

V8.4

The new symlinks implementation allows the use of logical names as the ﬁrst element of a target pathname.

General User Release Notes 3–1

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 ﬁle. DIRECTORY command must read the

ﬁle header (that is, perform a ﬁle access operation) in order to determine if the ﬁle was a symlink. This access will trigger the audit alarm if the user issuing

DIRECTORY command does not have read permissions on the target ﬁle. This problem has been corrected with the new symlink design on OpenVMS Version

8.4, where a directory entry indicating a symlink is ﬂagged as such, with DIR$V_ SPECIAL set to 1 (overlaid with DIR$V_NEXTREC).

Note

• Compatibility with symbolic links created by OpenVMS Version 8.3 Symlinks created by OpenVMS Version 8.4 will work on OpenVMS

Version 8.3. However, symlinks created by OpenVMS Version 8.3 will not work on OpenVMS Version 8.4.

To convert symlinks created by OpenVMS Version 8.3 to the format required on OpenVMS Version 8.4, you must run the ANALYZE/DISK_STRUCTURE (VERIFY) utility with the /REPAIR qualiﬁer.

3.5 SHOW SYSTEM/STATE=MUTEX Does not Display the Processes

V8.4

$ SHOW SYSTEM/STATE=MUTEX

state.

However, you can display the processes in MUTEX state by entering the following command:

$ SHOW SYSTEM

command does not display the processes in MUTEX

3–2 General User Release Notes

General User Release Notes

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.1-12

-PCSI-W-VERREM, will remove current product HP I64VMS CSWB V1.7-13

This is because PCSI always considers a higher number for a new version and in this case the latest SWB’s version number is lower than it’s predecessor. You can ignore this warning.

Do you want to continue? [YES]

3.7 Ctrl/P at the Console Does not Always Work

Permanent Restriction

On certain Integrity server conﬁgurations, pressing Ctrl/P at the console does not cause OpenVMS to display the Interrupt Priority C (IPC) menu. If you plan to use Ctrl/P, you should test it to ensure that it works.

If necessary, you can restore Ctrl/P functionality by performing the following steps:

1. Invoke SDA to analyze the running system:

$ ANALYZE/SYSTEM

2. Use the CLUE CONFIG command to display the adapters on the system:

SDA> CLUE CONFIG/ADAPTER

3. Locate the "Console Serial Line Driver" adapter (SRA:) in the display:

System Adapter Configuration:

----------------------------TR Adapter ADP Hose Bus BusArrayEntry Node GSIN iVec SCB Port Slot Device Name/HW-Id

-- ----------- ----------------- ---- ----------------------- ---- ---------------- ---- ---- ----------------------...

5 ACPI_IA64_I FFFFFFFF.8832E0C0 0 00 IA64_BUS 6 PCI FFFFFFFF.88342A80 9 00 PCI

...

4. Identify the controller that shares the same Global System Interrupt Number (GSIN) as SRA:. In this example, it is EWA:.

5. Exit from SDA and enter the following command (substituting EWA with the correct controller):

$ SET DEVICE EWA0/PREFERRED_CPUS=’F$GETSYI("PRIMARY_CPUID")’

FFFFFFFF.88342E58 0 0018 00DF 15F0 SRA: 0 Console Serial Line Driver FFFFFFFF.88342F68 8 0018 00DF 15F0 EWA: 1 A6865A (Fast Ethernet)

When you complete these steps, Ctrl/P should now function correctly. HP recommends that you edit SYS$MANAGER:SYLOGICALS.COM to include the SET DEVICE command to ensure correct behavior when the system reboots. Note that Ctrl/P might stop working again if you add or remove I/O adapters. If this happens, redo the steps listed above.

General User Release Notes 3–3

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

Due to intermittent problems during the installation of Oracle Database 10g Release 2 for OpenVMS on ﬁeld test Version 8.4, the Oracle 10g Release 2 installation fails. HP is analyzing and will ﬁx this problem in a future release.

If you are already using Oracle Database 10g Release 2 on prior versions of OpenVMS, you can upgrade the OpenVMS operating system to Version 8.4 and continue to use Oracle on OpenVMS Version 8.4.

3.9 Serial Port Enumeration

V8.3-1H1

On OpenVMS systems, enumeration is the process by which devices are assigned a letter and number following the OpenVMS generic device-type nomenclature. In the case of serial ports, enumeration is expressed as TTA0, TTB0, and so on, for generic serial port devices, and as OPA0 for a serial port device that has been selected as the system’s primary console at the EFI Boot Manager or the EFI Shell> prompt.

OpenVMS Version 8.2 consistently enumerated system serial ports according to the rules and precedents established by OpenVMS Alpha systems. With OpenVMS Version 8.3, those rules were violated and users experienced inconsistent port naming, particularly on systems migrating from Version

8.2 to Version 8.3.

OpenVMS Version 8.3-1H1 returns to the consistent serial-port naming conventions established for HP Integrity in OpenVMS Version 8.2, with the goal of not changing serial port names more than necessary, and for consistency with the policy on OpenVMS Alpha systems. The names of the serial ports can change, because at least one serial port can serve more than one function.

The serial port selected as primary console is always OPA0. If the graphics console has been selected as primary, the keyboard and graphics head constitute OPA0, and the serial ports will be named TTA0, TTB0, and so on.

Unless the serial port of the Integrated Lights Out (iLO) Management Processer (MP) is selected as the primary console, it is not connected as a serial port and is not exposed by the operating system. It is not suitable for general-purpose use because it cannot support the data rates a general-purpose serial port needs to support. This is an optional component in most systems. Check the options list shipped with your system and your system’s documentation at the HP documentation website:

http://docs.hp.com

3–4 General User Release Notes

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 deﬁnitions.

Abbreviation Deﬁnition

MP Serial port of the iLO MP. This component is

optional on some systems.

BMC Serial port of the BMC. This component is not

available on all systems.

AP Auxiliary Port. This auxiliary 16550-compatible

serial port is not available on all systems.

VGA Graphics Console. This is an optional component of

the iLO MP. If your system was not shipped with the VGA option, you can install a graphics option in one of the PCI slots to obtain this functionality.

NA Not Available.

NC Not Conﬁgured as a Serial Port by OpenVMS.

NS Not Supported.

The following table displays the sources for backpanel drawings:

Platform Backpanel Drawing

rx1600, rx1620 http://docs.hp.com/en/AB430-

rx2600, rx2620 http://docs.hp.com/en/AD117-9003A/ch02s02.html

rx4640 http://docs.hp.com/en/A9950-96009/A9950-96009.pdf

rx3600, rx6600 http://docs.hp.com/en/AD217-9001A/ch02s03.html

rx2660 http://docs.hp.com/en/AD217-9001A/ch02s02.html

rx8620 http://docs.hp.com/en/A7026-96033/ch04s05.html

bl860c http://docs.hp.com/en/AD217-9001A/ch02s01.html

96004/ch03s03.html#i1021437

The following table provides serial-port naming for the HP Integrity platforms listed. The device selected as primary console is always named OPA0.

OpenVMS Serial Port Name

Platform

rx1600 rx1620

rx2600 rx2620

rx4640 MP

Primary Console Port MP BMC AP VGA

MP (optional) BMC VGA (optional)

VGA (optional)

OPA0 NC NC

OPA0 NC

TTA0 OPA0 TTA0

TTB0 OPA0 TTB0

NA NA OPA0

NA OPA0

TTA0 TTA0 TTA0

General User Release Notes 3–5

OPA0

General User Release Notes

3.9 Serial Port Enumeration

OpenVMS Serial Port Name

Platform

rx3600 rx6600

rx2660 MP

rx8620 MP

BL860c MP

Primary Console Port MP BMC AP VGA

MP (optional) BMC VGA (optional)

VGA (optional)

VGA

OPA0 NC NC

OPA0 NC

TTA0 OPA0 TTA0

NA TTA0

NA NA OPA0

OPA0

TTA0

3.10 Old Firmware Cannot Translate Messages Written to the System Event Log

8.3-1H1

Upon installation, OpenVMS Version 8.3-1H1 begins writing new messages to the system event log. To see the SEL, select it (on most systems) from the main MP menu (SL: Show Event Logs).

Older ﬁrmware translates the messages as "IPMI Type-E0 Event," instead of the correct OS_OPENVMS_BUGCHECK and OS_OPENVMS_SHUTDOWN.

The following shows the OS_OPENVMS_BUGCHECK message (alert level *5 critical) on a system running older ﬁrmware:

OPA0

291 0 *5 0xB4801C9700E01B50 000000000019000C IPMI Type-E0 Event

30 Jul 2007 14:03:41

The following is an example of OS_OPENVMS_SHUTDOWN message (alert level 2 - informational) on a system running older ﬁrmware:

296 0 2 0x54801C9900E01BD0 00000000001A000C IPMI Type-E0 Event

30 Jul 2007 14:22:06

The new ﬁrmware uses the phrase "OS_OPENVMS_BUGCHECK" or "OS_ OPENVMS_SHUTDOWN" in place of "IPMI Type-E0 Event".

A third message, OS_BOOT_COMPLETE, has a different alert level on a system running new ﬁrmware. It has been changed by OpenVMS to informational, or level 2:

301 OS 0 2 0x548016E100E01B80 0000000000000001 OS_BOOT_COMPLETE

23 Aug 2007 14:25:44

New ﬁrmware displays the following message when "T - View Mode Conﬁguration Text" is selected:

MP:SL (+,-,CR,D, F, L, J, H, K, T, A, U, ? for Help, Q or Ctrl-B to Quit) >t . . .

Log Entry 301: 23 Aug 2007 14:25:44 Alert Level 2: Informational Keyword: OS_BOOT_COMPLETE OS Boot Complete Logged by: O/S Kernel (Generic) 0 Data: Major change in system state - Boot Complete 0x548016E100E01B80 0000000000000001

3–6 General User Release Notes

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 deﬁne the time zone to be used in certain C program time-related functions. (For more information about TZ, its use, and speciﬁc 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.

Prior to Version 8.3, deﬁning TZ to something other than a valid time zone caused the time zone to default to local time (that is, the current time zone of your system). With OpenVMS Version 8.3, deﬁning TZ to an invalid time zone causes the C RTL functions to resort to Coordinated Universal Time (UTC) time.

Note that if you deﬁne the logical name or DCL symbol TZ to a non-standard deﬁnition, it might cause undesirable side-effects in some C programs.

3.12 InfoServer Utility and FDDI

V8.3-1H1

General User Release Notes

3.11 TZ Function in C RTL

Using the InfoServer utility on OpenVMS to boot a client over an FDDI network adapter is not supported.

3.13 New Qualiﬁer for DCL Command SET PASSWORD

V8.3-1H1

The DCL command SET PASSWORD now accepts the /PROMPT qualiﬁer with two permitted values: /PROMPT=FIXED and /PROMPT=VARIABLE. If you use the SET PASSWORD command in a DCL command procedure, do not specify the /PROMPT=VARIABLE qualiﬁer. If you do, it works as expected, but any failing status is only displayed and not returned to DCL.

3.14 OpenVMS Freeware CDs

V8.3

Included in the OpenVMS Version 8.3 media kit are the OpenVMS Freeware Version 8.0 CDs. The Freeware CDs contain free software tools and utilities for creating applications and for using and managing OpenVMS systems.

To mount the Freeware CDs, insert one of the CD volumes into the CD drive and enter the following command to mount and display the contents of the Freeware volume.

$ MOUNT/OVERRIDE=IDENTIFICATION ddcu:

In this command, the or DVD device on your OpenVMS system. This device name is speciﬁc to each OpenVMS system.

ddcu:

speciﬁcation represents the device name of the CD

$ TYPE ddcu:[FREEWARE]FREEWARE_README.TXT

Duplicate copies of this ﬁle are found on each volume of the Freeware 8.0 distribution, and you can view its contents by using the preferred text editor.

TYPE

command or your

General User Release Notes 3–7

General User Release Notes

3.14 OpenVMS Freeware CDs

For additional information about the Freeware, refer to the ﬁles.

After the appropriate device is mounted, you can access the kit directories directly using standard DCL commands, such as text ﬁles 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.0 distribution.

DIRECTORY

3.14.1 Freeware Menu Unavailable (Integrity servers Only)

V8.2

The [FREEWARE]FREEWARE.COM Freeware menu system interface on the OpenVMS Freeware V7.0 distribution does not operate on OpenVMS Integrity servers.

The menu system interface is expected to function on OpenVMS Alpha and on OpenVMS VAX systems.

You can directly access the contents of the Freeware V7.0 distribution media by using DCL commands such as DIRECTORY and COPY from an OpenVMS Integrity servers, OpenVMS Alpha, or OpenVMS VAX system. This is the preferred way to access the contents of the Freeware V7.0 distribution.

Information about submissions and the Freeware distribution is contained in the ﬁle [FREEWARE]FREEWARE_README.TXT. This ﬁle is on each volume of the Freeware V7.0 distribution, and you can view its contents by using the TYPE command or a text editor.

FREEWARE_README.TXT

and

COPY

. Omnibus

3.15 DCL Commands

The following release notes pertain to DCL commands.

3.15.1 SHUTDOWN.COM on OpenVMS Graphics Console (Integrity servers

only)

Permanent Restriction

On an OpenVMS Integrity server system with a graphics console, use of SYS$SYSTEM:SHUTDOWN.COM to stop the system may not work as expected. The system will not stop after the "SYSTEM SHUTDOWN COMPLETE" message and wait for a key to be typed at the console keyboard. However, it will continue to reset as though a reboot had been requested. If the ﬁrst option in the list of boot options is a valid boot device, the OpenVMS system will reboot.

3.15.2 DIAGNOSE Command No Longer Supported

V8.2

The DIAGNOSE command is not supported on OpenVMS Version 8.2.

3.15.3 MOUNT Command Restriction

V8.4

In a mixed-version OpenVMS cluster, an attempt to mount a volume with /CLUSTER and /CACHE=[NO]DATA from a OpenVMS Version 8.4 system will fail on the earlier versions of OpenVMS (%MOUNT-W-RMTMNTFAIL) with the error condition as MOUNT-F-BADPARAM.

3–8 General User Release Notes

General User Release Notes

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. The software will continue to be available on the following website for earlier versions of OpenVMS:

http://h71000.www7.hp.com/openvms/products/omsva/omsva.html

3.17 HP Secure Web Browser

The following notes pertain to the HP Secure Web Browser.

3.17.1 Increased Memory Required

V7.3-1

If you have an OpenVMS workstation and you are using the HP Secure Web Browser (SWB), based on Mozilla, the minimum memory requirement is 256 MB; however, 512 MB is highly recommended for more robust performance.

3.15 DCL Commands

3.17.2 Installation Error on ODS-2 Disk Volume (Integrity servers Only)

V8.2

Installing the HP Secure Web Browser (CSWB) Version 1.4 for OpenVMS Integrity servers on an ODS-2 disk volume fails with a PCSI error, as follows:

%PCSI-E-OPENIN, error opening ODS2$DISK:[SYS0.SYSCOMMON.][CSWB.RES]SAMPLE^.UNIXPSFONTS.PROPERTIES;* as input

-RMS-E-FND, ACP file or directory lookup failed

-SYSTEM-W-BADFILEVER, bad file version number %PCSI-E-OPFAILED, operation failed

You can continue with the installation by answering "NO" to the "Do you want to terminate?" prompt. The installation will continue successfully.

As an alternative, you can install the HP Secure Web Browser on an ODS-5 disk volume.

General User Release Notes 3–9

General User Release Notes

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. On OpenVMS Alpha, you must use the CXXLINK utility to link the object modules into one executable image. On Integrity server systems, the only beneﬁt of using CXXLINK is that CXXLINK reports non-mangled names of undeﬁned multiply-deﬁned. It does this by intercepting Linker diagnostics and converting mangled names reported by the Linker to their original names, using the information in the demangler database.

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

VOLUME Syntax Error Correction

V8.4

The HP PCSI utility online help deﬁnes incorrect syntax of the $PRODUCT REGISTER VOLUME command as follows:

$PRODUCT REGISTER VOLUME old-volume-label device-name

The correct syntax is as follows:

$PRODUCT REGISTER VOLUME old-logvolnam device-name

3.18.3 iCAP Release Notes: GiCAP Functionality not Available

V8.3-1H1

While running SYS$MANAGER:ICAP$CONFIG.COM, if you respond "Y" to the "Enter (Y)es to conﬁgure this system with GiCAP support (N):" prompt, the following message is displayed:

HP OpenVMS Industry Standard 64

Global Instant Capacity on Demand (GiCAP) configuration utility

*** GiCAP functionality is not currently available ***

***GiCAP will be enabled at a later date via an ECO kit ***

HP OpenVMS Industry Standard 64 Global Instant Capacity on Demand (GiCAP) configuration utility *** GiCAP functionality is not currently available ***

***GiCAP will be enabled at a later date via an ECO kit ***

Also, note that in the release notes for Instant Capacity (iCAP), Chapter 2 speciﬁes GiCAP support for OpenVMS Version 8.3-1H1. This support is not available currently, but will be available in a future update kit. For more information, see the OpenVMS website.

3–10 General User Release Notes

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.1 Getting Information About Devices on the System

In section 8.3, the following examples should be replaced as follows:

The following command requests a full listing of the status of the DAD42: RRD40 device. The device is located on node IRIS in an OpenVMS Cluster environment.

$ SHOW DEVICES/FULL DAD42:

Disk DAD42: (IRIS), device type RRD40, is online, mounted, software write-locked, file-oriented device, shareable, error logging is enabled.

Error count 0 Operations completed 146 Owner process "" Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL Reference count 1 Default buffer size 512 Total blocks 1218000 Sectors per track 4 Total cylinders 50750 Tracks per cylinder 6 Allocation class 11

Volume label "CDBIN06JUL21" Relative volume number 0 Cluster size 3 Transaction count 1 Free blocks 15153 Maximum files allowed 152083 Extend quantity 5 Mount count 1 Mount status System Cache name "_$11$DUA21:XQPCACHE" Extent cache size 64 Maximum blocks in extent cache 1515 File ID cache size 64 Blocks currently in extent cache 0 Quota cache size 0 Maximum buffers in FCP cache 1330

Volume status: ODS-2, subject to mount verification, file high-water marking,

write-through XQP caching enabled, write-through XFC caching enabled.

The following command requests a full informational display about each DG device. This display shows only the ﬁrst two devices: the mounted $1$DGA5001: device and the unmounted $1$DGA5004: device.

General User Release Notes 3–11

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.

Error count 0 Operations completed 5773 Owner process "" Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 1 Default buffer size 512 Current preferred CPU Id 0 Fastpath 1 WWID 01000010:6005-08B4-0001-42DC-0001-F000-0111-0000 Total blocks 20971520 Sectors per track 128 Total cylinders 1280 Tracks per cylinder 128 Host name "CEAGLE" Host type, avail AlphaServer ES40, yes Alternate host name "CLETA" Alt. type, avail AlphaServer ES40, yes Allocation class 1

Volume label "5001" Relative volume number 0 Cluster size 21 Transaction count 1 Free blocks 19598208 Maximum files allowed 476625 Extend quantity 5 Mount count 9 Mount status System Cache name "_$1$DGA3105:XQPCACHE" Extent cache size 64 Maximum blocks in extent cache 1959820 File ID cache size 64 Blocks in extent cache 0 Quota cache size 0 Maximum buffers in FCP cache 3444 Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-2, subject to mount verification, file high-water marking,

write-back XQP caching enabled, write-through XFC caching enabled.

Volume is also mounted on VMSROC, PAVER, VMSROL, CLETA, VMSJO, VMSMO, NOME,

FARKLE.

I/O paths to device 5 Path PGA0.5000-1FE1-0015-22AC (CEAGLE), primary path.

Error count 0 Operations completed 0

Path PGA0.5000-1FE1-0015-22A9 (CEAGLE).

Error count 0 Operations completed 0

Path PGB0.5000-1FE1-0015-22A8 (CEAGLE).

Error count 0 Operations completed 0

Path PGB0.5000-1FE1-0015-22AD (CEAGLE), current path.

Error count 0 Operations completed 5773

Path MSCP (CLETA).

Error count 0 Operations completed 0

Disk $1$DGA5004: (CEAGLE), device type HSV110, is online, file-oriented device, shareable, device has multiple I/O paths, served to cluster via MSCP Server, error logging is enabled.

Error count 0 Operations completed 0 Owner process Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 0 Default buffer size 512 Current preferred CPU Id 0 Fastpath 1 WWID 01000010:6005-08B4-0001-42DC-0001-F000-0120-0000 Host name CEAGLE Host type, avail AlphaServer ES40, yes Alternate host name CLETA Alt. type, avail AlphaServer ES40, yes Allocation class 1

3–12 General User Release Notes

General User Release Notes

3.18 Documentation Corrections

I/O paths to device 5 Path PGA0.5000-1FE1-0015-22AC (CEAGLE), primary path. Error count 0 Operations completed 0 Path PGA0.5000-1FE1-0015-22A9 (CEAGLE). Error count 0 Operations completed 0 Path PGB0.5000-1FE1-0015-22A8 (CEAGLE), current path. Error count 0 Operations completed 0 Path PGB0.5000-1FE1-0015-22AD (CEAGLE). Error count 0 Operations completed 0 Path MSCP (CLETA). Error count 0 Operations completed 0

3.18.5.2 Initializing a New Volume with ODS-5 Format

In Section 9.3.3, the SHOW/DEVICE DKA200:/FULL command displays the messages similar to the following:

$ SHOW DEVICE DKA200:/FULL

Disk $10$DKA200:, device type RZ74, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable.

Error count 0 Operations completed 155 . .

. Volume Status: ODS-5, subject to mount verification, file high-water marking, write-back XQP caching enabled, write-through XFC caching enabled.

3.18.5.3 Converting from ODS-2 to ODS-5

In section 9.5.5.1, the SHOW DEVICE DKA200:/FULL command in the instruction 2 should display the message similar to the following:

$ SHOW DEVICE DKA200:/FULL

Disk $10$DKA200:, device type RZ47, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable.

Error count 0 Operations completed 232

. Volume Status: ODS-2, subject to mount verification, file high-water marking, write-back XQP caching enabled, write-through XFC caching enabled.

In section 9.5.5.1, the SHOW DEVICE DKA300:/FULL command in the instruction 5 displays the message similar to the following:

$ SHOW DEVICE DKA300:/FULL

Disk $10$DKA300:, device type RX74, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable.

Error count 0 Operations completed 155

. Volume Status: ODS-5, subject to mount verification, file high-water marking, write-back XQP caching enabled, write-through XFC caching enabled.

General User Release Notes 3–13

General User Release Notes

3.18 Documentation Corrections

3.18.5.4 New Extended File Speciﬁcations 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 . .

. Volume Status: ODS-5, subject to mount verification, file high-water marking, write-back XQP caching enabled, write-through XFC caching enabled.

$ SHOW DEVICE DKA200:/FULL

Disk AABOUT$DSA200:, 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, subject to mount verification, file high-water marking, write-back XQP caching enabled, write-through XFC caching enabled.

3.18.5.5 ODS-2 and ODS-5 Used Together

In section 10.1.2.2, the SHOW DEVICE command example in the "Error Messages Can Vary Depending on Parse Style" notes should display the message similar to the following:

Examples of TRADITIONAL and EXTENDED styles on an ODS-5 volume:

$ SHOW DEVICE DKA500:/FULL

Disk AABOUT$DKA500:, device type RZ25 Disk, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable.

Error count 0 Operations completed 155

. Volume Status: ODS-5, [1] subject to mount verification, file high-water marking, write-back XQP caching enabled, write-through XFC caching enabled.

$ SET PROCESS /PARSE_STYLE=TRADITIONAL [2] $ OPEN /WRITE FILE z.z.z.z %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters \.Z\ [3] $ SET PROCESS /PARSE_STYLE=EXTENDED [4] $ OPEN /WRITE FILE z.z.z.z $ [5]

1. The volume is ODS-5.

2. The parse style is set to TRADITIONAL.

3. DCL returns an error on some ODS-5 file names such as this one.

4. The parse style is set to EXTENDED.

5. DCL creates the file.

3–14 General User Release Notes

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.

-RMS-E-CRE, ACP file create failed [5]

-SYSTEM-W-BADFILEVER, bad file version number

1. The volume is ODS-2.

2. The parse style is set to TRADITIONAL.

3. DCL returns an error message.

4. The parse style is set to EXTENDED.

5. DCL allows the file name, but XQP returns an error.

Examples of different error messages for the same syntax error:

$ SHOW DEVICE DKA500:/FULL Disk AABOUT$DKA500:, device type RZ25 Disk, is online, allocated, deallocate on dismount, mounted, file-oriented device, shareable.

Error count 0 Operations completed 155 . .

. Volume Status: ODS-5, [1] subject to mount verification, file high-water marking, write-back XQP caching enabled, write-through XFC caching enabled.

$ SET PROCESS /PARSE_STYLE=TRADITIONAL [2] $ CREATE a^<b.c %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters \^\ [3] $ SET PROCESS /PARSE_STYLE=EXTENDED [4] $ CREATE a^<b.c %CREATE-E-OPENOUT, error opening a^<b.c as output

-RMS-F-SYN, file specification syntax error [5]

1. The volume is ODS-5.

2. The parse style is set to TRADITIONAL.

3. DCL returns an error message for a syntax error.

4. The parse style is set to EXTENDED.

5. RMS returns a different error message for the same syntax error.

3.18.5.6 Performing Image Backups to Disk

In section 11.15.3, the following note should be appended to the end of the section:

BACKUP does not preserve GUID signature during image restore operation of the system disk on Integrity server systems. During restore, BACKUP calls SETBOOT to create a new GUID signature. Hence, during image restore operation BACKUP does not restore the original GUID signature, rather it creates a new GUID signature. As a result of this, Integrity servers system does not boot automatically from a disk created through an image restore operation.

General User Release Notes 3–15

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 <destination_disk>:[VMS$COMMON.SYS$LDR]SYS$EFI.SYS

The following corrections pertain to the HP OpenVMS System Manager’s Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

3.18.5.7 Mounting a Volume With Caching Disabled

The following paragraphs should be appended to Section 4.4.

To disable XFC, enter the following command:

MOUNT/CACHE=NODATA

This command disables only data cache (XFC) while metadata cache (XQP) is enabled.

This example mounts a database volume labeled ORACLE_VOL1 with data cache (XFC) disabled:

$ MOUNT DUA100: ORACLE_VOL1 /CACHE = NODATA /SYSTEM

3.18.5.8 System-Wide Statistics

In section 4.5.6.1, the following changes should be made to the foot note:

[7] Reads bypassing cache — The total number of read I/Os since system startup that were seen by the cache but were not cached, for example, because they were too big, or they were for volumes mounted /NOCACHE or /CACHE=NODATA, or they speciﬁed one of the following QIO modiﬁers: IO$M_DATACHECK, IO$M_ INHRETRY, or IO$M_NOVCACHE.

[17] Write bypassing cache — The total number of write I/Os since system startup that were seen by the cache but were not cached, for example, because they were too big, or they were for volumes mounted /NOCACHE or/CACHE=NODATA, or they speciﬁed one of the following QIO modiﬁers: IO$M_DATACHECK, IO$M_ ERASE, IO$M_INHRETRY, or IO$M_NOVCACHE.

3.18.5.9 Disabling Caching for a Volume

In Chapter 4, a new section "Disabling Caching for a Volume" has to be added before Section 4.5.4, "Disabling Caching for a File".

The following text should be added to the "Disabling Caching for a Volume":

From OpenVMS Version 8.4 onwards, XFC can be dynamically enabled or disabled or cleared for a volume using the DCL "SET VOLUME" command. In the earlier versions, XFC caching attributes of the volume were speciﬁed when the volume was mounted. Once the volume is mounted there is no way to dynamically modify the XFC caching attributes. Therefore, to modify the XFC caching attributes, the volume had to be dismounted and mounted again with the appropriate XFC caching attributes.

3–16 General User Release Notes

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

SET VOLUME V1/CACHE=DATA To Enable XFC caching for the volume V1

SET VOLUME V1/CACHE=NODATA To Disable XFC caching for the volume V1

SET VOLUME V1/CACHE=CLEAR_ DATA

SET VOLUME V1/CACHE=(DATA,CLEAR_DATA)

SET VOLUME V1/CACHE=(NODATA,CLEAR_DATA)

SHOW MEM/CACHE=(VOL=V1) To display the current XFC caching status of

Examples

$ SET VOLUME $DKA100/CACHE=CLEAR_DATA

To Clear the contents of the volume V1 from cache

To Enable XFC caching for the volume V1 and Clear the contents of volume V1 from the cache

To Disable XFC caching for the volume V1 and Clear the contents of volume V1 from the cache

the volume V1

This example clears the contents of the volume $DKA100 already present in the XFC cache. The caching attributes of the volume $DKA100 is not altered.

$ SET VOLUME $DKA100/CACHE=DATA

This example enables XFC caching for the volume $DKA100. The contents of volume $DKA100 already present in the XFC cache is not affected.

$ SET VOLUME $DKA100/CACHE=(DATA,CLEAR_DATA)

This example enables XFC caching for the volume $DKA100 and clears contents of the volume $DKA100 already present in the XFC cache.

3.18.5.10 Understanding File System Data Caches

In Section 4.2, add the following bullet after the following paragraph:

XFC improves I/O performance and contains the following features that are not available with VIOC:

• Dynamically enabling or disabling caching for mounted volumes

3.18.6 HP OpenVMS RTL Library (LIB$) Manual

V8.3

The LIB$SET_SYMBOL value-string is incorrectly documented in Version 8.2 of the HP OpenVMS RTL Library (LIB$) Manual. The correct value-string is as follows:

Trailing blanks are not removed from the value string before use. The maximum length of value-string is 4096 characters. Integer values are not allowed; LIB$SET_SYMBOL is intended to set string CLI symbols, not integer CLI symbols.

General User Release Notes 3–17

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

There is an error in the description of Bit 1 of the MMG_CTLFLAGS system parameter in the OpenVMS Performance Management manual. That description should be corrected to read as follows:

"Reclamation enabled by out swapping processes that have been idle for longer than LONGWAIT seconds. This occurs when the size of the free list drops below the value of FREEGOAL."

3.18.9 HP OpenVMS System Analysis Tools Manual

For changes and updates to the HP OpenVMS System Analysis Tools Manual, see Chapter 4.

3.18.10 HP OpenVMS Programming Concepts Manual

The following corrections pertain to the HP OpenVMS Programming Concepts Manual:

3.18.10.1 Saving System Dumps

V8.3

The following changes should be made to the paragraph in Section 31.2, "Writing a Privileged Routine (User-Written System Service)":

"As a protected image, your program does not have the entire operating system programming environment at its disposal. Unless a module has the preﬁx SYS$ or EXE$, you must avoid calling it from an inner mode. In particular, do not call LIB$GET_VM or LIB$RET_VM from an inner mode. You can call OpenVMS RMS routines from executive mode but not from kernel mode."

LIB$GET_VM should be LIB$FREE_VM. You cannot call these LIBRTL routines directly, and you cannot call any routines that might now or in the future call these routines indirectly. This includes other routines within LIBRTL and the user-mode C library, among other libraries.

3.19 HP OpenVMS DELTA/XDELTA Debugger Manual Update

V8.3

The HP DELTA debugger was made available on OpenVMS Integrity servers Version 8.2-1. The HP OpenVMS DELTA/XDELTA Debugger Manual has been revised in this release to include information about using DELTA on OpenVMS Integrity servers.

3.19.1 HP OpenVMS Version 8.2 New Features and Documentation Overview: Librarian Utility Corrections

The following release notes provide corrected information about the OpenVMS Integrity servers Librarian utility.

3–18 General User Release Notes

3.19 HP OpenVMS DELTA/XDELTA Debugger Manual Update

3.19.1.1 /REMOVE Qualiﬁer 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

qualiﬁer is incorrect. The correct information is as follows:

The /REMOVE qualiﬁer 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. The enhanced /REMOVE qualiﬁer requests that the LIBRARY command delete one or more entries from the global symbol table of an object library.

3.19.1.2 Accessing ELF Object Libraries Correction

Section 4.8.3.2 of the HP OpenVMS Version 8.2 New Features and Documentation Overview contains incorrect information. The following text replaces information

in that section:

Accessing ELF Object Libraries

ELF object modules are inherently random access modules, whereas OpenVMS Alpha objects, text modules, and so on, are sequential. To allow random access, a new library routine was created to map the ELF object modules into process P2 space so that applications can make random access queries. To recover virtual address space from this mapping, another library routine was created to remove this mapping. These new routines (LBR$MAP_MODULE and LBR$UNMAP_ MODULE) work only with ELF object libraries. These entry points are 64-bit interfaces because they refer to P2 space.

General User Release Notes

Because of the random-access nature of ELF object ﬁles, the following operations are not allowed on ELF object libraries:

LBR$GET_RECORD LBR$SET_LOCATE LBR$SET_MOVE

Because inserting modules into the library is a sequential operation, LBR$PUT_ RECORD is allowed on ELF object libraries. Because the ELF object modules are not segmented into records, you need to provide the module’s on-disk size when calling LBR$PUT_MODULE or upon the ﬁrst call to LBR$PUT_RECORD when writing a module into the library.

The C code fragment in the following example illustrates how to use LBR$PUT_ RECORD to insert an object module:

bufdesc->dsc$a_pointer = &p0_buffer ; bytes_to_transfer = module_size ;

while ( bytes_to_transfer ) {

transfer = MIN ( bytes_to_transfer ,

bufdesc->dsc$w_length = transfer ;

status = lbr$put_record ( library_index ,

if ( (status & 1) == 0 )

break ;

bytes_to_transfer -= transfer ; bufdesc->dsc$a_pointer += transfer ; };

ELBR$C_MAXRECSIZ ) ;

& bufdesc , & txtrfa ,

module_size ) ;

General User Release Notes 3–19

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.1 HP OpenVMS RTL Library (LIB$) Manual: Rounding Rule for LIB$CVT_DX_DX

V8.2-1

In the description of the LIB$CVT_DX_DX routine in the HP OpenVMS RTL Library (LIB$) Manual, the following paragraph under ‘‘Guidelines for Using

LIB$CVT_DX_DX’’ should contain speciﬁc information about the rounding rule that is used:

Results are always rounded instead of truncated, except for the case described below. Note that loss of precision or range may be inherent in the destination data type or in the NBDS destination size. No errors are reported if there is a loss of precision or range as a result of destination data type.

This paragraph should be modiﬁed as follows:

Results are always rounded instead of truncated, except for when the source and destination are both NBDS and no scaling is requested. That case is described more fully in a later rule. LIB$CVT_DX_DX uses the VAX_ROUNDING rule. Note that loss of precision or range may be inherent in the destination data type or in the NBDS destination size. No errors are reported if there is a loss of precision or range as a result of destination data type. For details about the VAX_ROUNDING rule, refer to the description of CVT$CONVERT_FLOAT.

3.19.3 HP OpenVMS RTL Library (LIB$) Manual: Platform Restrictions

V8.2–1

The HP OpenVMS RTL Library (LIB$) Manual incorrectly identiﬁes the following routines as being available on both Alpha and Integrity servers. These routines are available only on Alpha:

• LIB$GET_CURR_INVO_CONTEXT

• LIB$GET_INVO_CONTEXT

• LIB$GET_INVO_HANDLE

• LIB$GET_PREV_INVO_CONTEXT

• LIB$GET_PREV_INVO_HANDLE

• LIB$PUT_INVO_REGISTERS

The HP OpenVMS RTL Library (LIB$) Manual also should specify that the LIB$GET_UIB_INFO routine is available only on Integrity servers.

The routines relating to invocation contexts and invocation handles that are Integrity servers only include the following:

• LIB$I64_CREATE_INVO_CONTEXT

• LIB$I64_FREE_INVO_CONTEXT

3–20 General User Release Notes

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.15, Using Interrupt Priority Level C (IPC), in the HP OpenVMS System Manager’s Manual, Volume 1: Essentials incorrectly states that you can use

IPC commands on all Alpha and Integrity servers. This is not correct. The documentation has been changed to include the following statement:

For OpenVMS Versions 8.2 and 8.2--1, you cannot use IPC commands on Integrity servers or on ES47 or GS1280 Alpha systems if you booted from a Graphic console.

C Prototype

int sys$putmsg (void *msgvec, int (*actrtn)(__unknown_params), void *facnam, unsigned __int64 actprm);

Note that the return value from *actrtn is indeed checked to determine whether or not the message is input.

The documentation source ﬁle has been corrected, and the correction will appear in the next version of the HP OpenVMS System Services Reference Manual and in online help.

3.20 Network Update Restrictions from Version 8.2 to Version 8.2–1

V8.2–1

OpenVMS Version 8.2–1 supports network update of the operating system from Version 8.2 to Version 8.2–1. Network update is supported only over the core I/O LAN cards on systems supported by OpenVMS Version 8.2. Refer to the HP

OpenVMS Version 8.2–1 for Integrity Servers Upgrade and Installation Manual

for more information.

In addition, there is also a hardware conﬁguration restriction for network booting. Unlike Alpha consoles, where the speed and duplex setting for the network adapter can be selected at the console, the Integrity servers console and network boot drivers perform autonegotiation only. The network switch nearest to the Integrity servers boot client must be set to autonegotiate for a successful network boot. Failure to set the switch to autonegotiate may not complete the network boot process.

3.21 Synchronous Data Links not Supported

OpenVMS does not support any synchronous data link hardware on Integrity servers.

General User Release Notes 3–21

General User Release Notes

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. A common network conﬁguration error that results in a duplex mode mismatch condition occurs when the switch port is set to autonegotiate the speed and duplex settings, and the LAN device is set to a ﬁxed setting of full duplex. In this conﬁguration, autonegotiation by the switch results in the selection of half-duplex mode and the LAN device is set to full-duplex mode, and a duplex-mode mismatch occurs.

The consequence of a duplex-mode mismatch is typically a performance degradation. In addition, the IEEE 802.3 speciﬁcation that describes the autonegotiation process suggests that a duplex-mode mismatch can result in data corruption. For most LAN devices, the only consequence of a duplex mode mismatch is the performance degradation. For some LAN devices, packet data is corrupted with good CRC, resulting in packet corruption undetected by the LAN subsystem. These devices include all Broadcom-based NICs and embedded LOM chips. On Alpha systems, these include the DEGPA, DEGXA, BCM5703 LOM on the AlphaServer DS25, and any implementations using the dual-port BCM5704 chip. On Integrity systems, these include the A6847A, A6725A, A9782A, A9784A, AB465A, and BCM5701 LOM on the rx2600; BCM5703 LOM on other systems; and the A6794A.

In prior versions of OpenVMS, the LAN drivers attempt to detect the duplexmode mismatch condition. Once an hour while the condition exists, they issue a console message and error log message warning of the condition.

In OpenVMS Version 8.3, the frequency of the messages is increased from once per hour to once every 36 seconds for any Broadcom-based LAN devices. The frequency remains at once per hour for non-Broadcom-based LAN devices. In addition, to increase the visibility of these messages, the console messages are sent to OPCOM and to the LANACP log ﬁle (SYS$MANAGER:LAN$ACP.LOG).

The purpose of this note is to underscore the importance of avoiding duplexmode mismatches, particularly when this condition results in undetected data corruption for Broadcom-based devices.

Note that the LAN drivers detect a duplex mode mismatch condition by monitoring device errors. The detection is not perfect, so the LAN drivers refer to the condition as a "potential duplex-mode mismatch." Upon noticing these messages, a system or network manager should inspect the LAN counters and LAN device settings to ensure a duplex-mode mismatch condition does not exist.

3–22 General User Release Notes

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 modiﬁed to replace the ’-’ character with the ’^’ character. This change is done in TDF to support DTSS. DTSS cannot handle the commonly used UNIX ’GMT-X’ timezone rules and does not support timezone rule strings that are identical to the timezone name.

For example, the ’GMT-1’ timezone rule generates a SYS$TIMEZONE_RULE string of ’GMT-1’. Due to the matching rule ﬁle name of ’GMT-1’ and rule string of ’GMT-1’ caused DTSS not to function properly.

The CRTL and DTSS components are also modiﬁed to support this change.

For example, Timezone logical before this change:

"SYS$TIMEZONE_RULE" = "CET-1CEST-2,M3.5.0/02,M10.4.0/03"

Timezone logical after this change:

"SYS$TIMEZONE_RULE" = "CET^1CEST^2,M3.5.0/02,M10.4.0/03"

4.2 Issues with Time Zone Conﬁguration

V8.4

On OpenVMS Version 8.4, if you conﬁgure time zone to a zone that does not get affected by the daylight saving time (DST) changes, it results in the following error message on the operator’s terminal at a very high frequency:

%TDF-F-SMNSUBFAIL, Attempt to compute delta in Smithsonian time failed, status = 001583EC, terminating.

Note

OpenVMS Version 8.4 upgrade kit is recommended only to those customers who will be conﬁguring their time zone to a zone that gets affected by the DST changes.

System Management Release Notes 4–1

System Management Release Notes

4.2 Issues with Time Zone Conﬁguration

Workaround

Deassign the the system.

$ DEASSIGN/EXECUTIVE_MODE/SYSTEM SYS$DST_DELTA_TIME

SYS$DST_DELTA_TIME

logical, when the error message appears on

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). For more information about product speciﬁc limitations, see the respective product documentation.

This section describes known problems and restrictions in OpenVMS guest on Integrity VM.

4.3.1 "Guest Punishment" Scenarios

V8.4

Scenario 1

A problem in Integrity VM Version 4.1 Field Test Evaluation Kit for OpenVMS Version 8.4 causes OpenVMS guests to fail with the following message displayed on the guest’s MP console:

*** A fatal error has occurred -- VM terminated ***

**** Dumping Guest Image ****

**** Done with dump (nnnnnKbytes) ****

At the same time, the Integrity VM monitor log (found on the VM Host in /var/opt/hpvm/common/hpvm_mon_log) must include guest punishment information as follows:

Assertion failed mmxlate.c:nnn: PTE_TYPE(pte) == PTE_TYPE_TRPT || PTE_TYPE(pte) == PTE_TYPE_SPPT scopeDeact EA0C000000000000

===============================================================================

Guest punishment: Virtual Machine Monitor Assertion Failed (CPUnnnnnnn)

===============================================================================

This problem occurs when a privileged hardware instruction (for example, mov r1 = psr) is executed in process space, rather than in system space (that is, in the VMS executive).

When an application uses the $CMKRNL system service to enter kernel mode, it can execute privileged hardware instructions in process space. The kernel mode routines may be within the main image of the application, or within a shareable image. To run such an application, the user must have CMKRNL privilege, or the image must be installed: a main image with privileges, and a shareable image as a protected shareable image.

The application may be part of OpenVMS, a local customer application, or may be from a third-party.

If the problem occurs, a possible workaround is to install the image that performs the privileged hardware instructions using /RESIDENT. This ensures that the code of the image is in the system space.

4–2 System Management Release Notes

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. The protected shareable image is installed without /RESIDENT:

$ set process/privilege=cmkrnl $ install add sys$disk:[]punish_shr.exe/protect/share $ set process/privilege=nocmkrnl $ define/user punish_shr sys$disk:[]punish_shr.exe $ run punish_main Changing mode to kernel to read PSR

*** A fatal error has occurred -- VM terminated ***

**** Dumping Guest Image ****

**** Done with dump (22864Kbytes) ****

This is the VM Host view of the guest punishment in the Integrity VM monitor log at the same instant:

Assertion failed mmxlate.c:430: PTE_TYPE(pte) == PTE_TYPE_TRPT || PTE_TYPE(pte) == PTE_TYPE_SPPT scopeDeact EA0C000000000000 ============================================================================

Guest punishment: Virtual Machine Monitor Assertion Failed (CPU2000000)

============================================================================

b. The protected shareable image is installed with /RESIDENT:

$ set process/privilege=cmkrnl $ install add sys$disk:[]punish_shr.exe/protect/share/resident $ set process/privilege=nocmkrnl $ define/user punish_shr sys$disk:[]punish_shr.exe $ run punish_main Changing mode to kernel to read PSR PSR = 000000100a0ae010

This problem will be ﬁxed in a future version of Integrity VM.

Scenario 2

OpenVMS guests will fail with the following message displayed on the guest’s MP console:

*** A fatal error has occurred -- VM terminated ***

**** Dumping Guest Image ****

**** Done with dump (nnnnnKbytes) ****

The Integrity VM monitor log (found on the VM Host in /var/opt/hpvm/common/hpvm_mon_log) must include guest punishment information as follows:

ERROR: Could not allocate pinned memory (256 bytes) Pinned pool: MaxChunk: 0x0000000000000000 Free: 0x0000000000000000 Pinned pool chunks: Resource map: PinnedMemAlloc limit=0xea0a0000025e0870 Assertion failed firmware.c:94: argArray

=============================================================================

Guest punishment: Virtual Machine Monitor Assertion Failed (CPUc000000)

System Management Release Notes 4–3

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 ﬁxed in a future version of Integrity VM.

4.3.2 Increased CPU Consumption After Shutdown

V8.4

OpenVMS guest has a known issue where the CPU consumption of the Host increases, in case the guest is shutdown using the SYS$SYSTEM:SHUTDOWN.COM command procedure using "NONE" as the shutdown options. The CPU consumption on the Host remains high as long as the VMS guest stays in the "P000>>>" ﬁrmware prompt. After the guest is rebooted the Host CPU consumption returns back to normal.

The suggested workaround for this problem is to shutdown VMS guest using "POWER_DOWN" as the shutdown options.

A known consequence of using this option is that, the virtual machine is shutdown and has to be restarted by the MP command "pc -on" in the virtual console or alternately enter the following command on the Host:

# hpvmstart -P <<OpenVMS guest name>>

This will be ﬁxed in a future release.

4.3.3 OpenVMS Guest Does not Support Attached I/O Devices

V8.4

The OpenVMS guest does not support attached devices such as CD/DVD burners, media changers and tape devices. If you want to use tape devices, you can connect them to a physical system that is in a cluster with OpenVMS guest and TMSCP serves the tape devices.

4.3.4 Networking or Storage Interface Support

V8.4

The OpenVMS guest supports only Accelerated Virtual I/O (AVIO) interface.

Integrity VM commands allows you to conﬁgure VIO devices to a guest and these devices may not give any apparent errors during the startup. However, VIO devices are not part of the supported conﬁguration of a guest running OpenVMS Operating System.

4.4 Provisioning OpenVMS Using HP SIM

The following release notes pertain to provisioning on OpenVMS.

4.4.1 Provisioning OpenVMS Guest Limitation

V8.4

Provisioning OpenVMS using HP SIM, Version 4.0 is not supported with OpenVMS as a Guest Operating System on Integrity VM.

4–4 System Management Release Notes

System Management Release Notes

4.4 Provisioning OpenVMS Using HP SIM

4.4.2 System Firmware

V8.4

The system ﬁrmware version of BL860c and BL870c servers must be at 4.21. The system ﬁrmware 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.4 Provisioning From HP SIM Central Management Server

V8.4

OpenVMS can be provisioned from an HP SIM Central Management Station, an HP ProLiant server running Microsoft Windows.

4.4.5 InfoServer Name Length

V8.3-1H1

The InfoServer name must be less than 12 characters long for provisioning to work. This is a temporary restriction.

4.4.6 OpenVMS InfoServer and the Integrity servers on the Same LAN

V8.3-1H1

The OpenVMS InfoServer and the Integrity servers must be on the same Local Area Network (LAN) to provision the server blade.

4.4.7 EFI Firmware

V8.3-1H1

The EFI ﬁrmware for the BladeSystem must be at version 5.0 or later.

4.4.8 Management Processor

V8.4

The Management Processor must be running the Advanced iLO2 ﬁrmware.

4.4.9 OpenVMS TCP/IP Provisioning Limitation

V8.4

The TCP/IP server components BIND, LPD, LBROKER, and SMTP, if selected to be enabled on the target server, do not start up when OpenVMS TCP/IP is conﬁgured through Provisioning.

The workaround for this problem is to conﬁgure and restart these services manually after conﬁguring TCP/IP with Provisioning.

System Management Release Notes 4–5

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. These errors may prevent booting the target server successfully from InfoServer.

Shell> lanboot -dn sysmg3

Client MAC Address: 00 11 22 33 44 55 Client IP Address: 1.2.3.4 Subnet Mask: 255.255.254.0 BOOTP Server IP Address: 1.2.3.5 DHCP Server IP Address: 0.0.0.0 Boot file name: LDA30:[VMS$COMMON.SYSEXE]VMS_LOADER.EFI

Retrieving File Size.

Retrieving File (TFTP).Loading memory disk from IP 1.2.3.5 . Warning - Unable to open SYS$LOADABLE_IMAGES:SYS$PLATFORM_SUPPORT.EXE, status = 0x54

*** SYSTEM MAY NOT BE BOOTABLE. Continuing...

...........

Warning - Unable to open SYS$SYSTEM:SYSBOOT.EXE, status = 0x54

*** SYSTEM MAY NOT BE BOOTABLE. Continuing...

...

Warning - Unable to open SYS$LOADABLE_IMAGES:EXCEPTION.EXE, status = 0x54

*** SYSTEM MAY NOT BE BOOTABLE. Continuing... .

TFTP error, status = 8000000000000012, attempting retry

To workaround this issue, when deploying OpenVMS Version 8.4 simultaneously on two or more target servers with Provisioning, avoid using InfoServer boot with memory disk option as follows: In Step 2 of Provisioning in HPSIM GUI, under the "LAN Boot Settings" section of all target servers, select the setting for OpenVMS Version combo box as "V8.3-1H1 or below".

4.5 Insight Dynamics - Virtual Server Environment for OpenVMS

This section describes the known issues and limitations in Insight Dynamics Virtual Server Environment (ID-VSE) Version 4.1 for OpenVMS.

4.5.1 Utilization Data Collection Fails

V8.4

When an attempt is made to collect utilization data in Capacity Advisor for an OpenVMS guest on Integrity VM, the operation fails and the following error message is displayed:

The system has no workload defined. Make sure to select Tools->VSE Management...in HP-SIM before running this command for the first time. For HPVM Guests, please be sure that the HPVM wbem provider is properly configured.

4–6 System Management Release Notes

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. In the Product Description section, select the Operating System for Tool Filtering property. Click the drop-down menu and select HP OpenVMS and click OK to apply the changes.

After making these changes, you can return to Capacity Advisor to collect and view utilization data proﬁle for the OpenVMS guest.

4.5.2 Problem While Creating a New or Replacement Simulated System

V8.4

When trying to create a new or replacement simulated OpenVMS system in a Capacity Advisor Scenario, the Select OS Type in the "System Type and Size" section does not list "OpenVMS".

Workaround

For a new or replacement OpenVMS system, select the different operating system. To do so, follow these steps:

1. In the "System Type and Size" section, select the Select OS Type property.

2. Click the drop-down menu and select HP-UX.

3. Click OK to apply the changes.

4.5.3 Utilization Data not Available for OpenVMS Sub-OS Workloads

V8.4

The OpenVMS Utilization WBEM provider supports collecting utilization data only for OpenVMS whole-OS workloads. It does not support sub-OS (monitored and managed) workloads under OpenVMS. This has the following impact on ID-VSE:

• Virtualization Manager and Capacity Advisor display utilization data for whole-OS workloads only.

• Utilization data from sub-OS workloads running under OpenVMS cannot be used for capacity planning in Capacity Advisor.

4.5.4 Insight Software Features not Supported on OpenVMS

V8.4

The following Insight software features are not supported on OpenVMS:

• Application Discovery

• iCAP Manager

• Process Resource Manager (PRM)

• Logical Server Management

System Management Release Notes 4–7

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 Conﬁguration...’ options under ’Diagnose’ menu -> ’Troubleshoot VSE

Management....’

• Conﬁgure VSE agents for OpenVMS - This refers to all options under the ’Conﬁgure’ menu -> ’Conﬁgure VSE agents...

• VSE Agentless data collection - This refers to all options under the ’Conﬁgure’ menu -> ’Conﬁgure VSE Agentless agents...

• Import of Capacity Advisor Data from OVPA and PMP - This refers to all options under Optimize menu -> Capacity Advisor -> Import Capacity Advisor Data

4.6 Performance Enhancements

V8.4

The following performance enhancements have been made to the OpenVMS Version 8.4 release.

4.6.1 Enhancements to Write Bitmaps

V8.4

Write Bitmaps (WBM) is a feature used by OpenVMS during minimerge and minicopy operations of Shadowing minimerge and minicopy. Information, about which blocks on a disk are written, is transmitted to other nodes within the cluster. The following updates have been made in this release.

4.6.1.1 WBM_MSG_INT Parameter Updates

V8.4

The WBM_MSG_INT parameter indicates the time by which a SetBit message can be delayed when it is in buffered mode. If the SetBit buffer does not ﬁll with SetBit messages by this time interval, then the message is sent. The parameter is in milliseconds, however, the conversion factor used for this timer was off by a factor of 10. Earlier, a WBM_MSG_INT value of 10 was resulting in a 100 millisecond delay when in buffered mode. This problem is corrected so that a value of 10 now indicates only a 10 millisecond delay.

4.6.1.2 WBM_MSG_UPPER and WBM_MSG_LOWER Parameter Updates

V8.4

WBM_MSG_UPPER is the threshold used to determine if a switch should occur to buffered message mode, when operating in single message mode. If WBM_ MSG_UPPER or more SetBit operations are done in a 100 millisecond window, the messaging mode will be switched to buffered mode. The default value is 80.

4–8 System Management Release Notes

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. Currently, SetBit messages are sent to the multiple master bitmap nodes synchronously. Only when the response for the SetBit message is received from the ﬁrst remote master bitmap node, is the message sent to the next master bitmap node. When done with all of the remote master bitmap nodes, the I/O is resumed.

SetBit messages are now sent to all multiple master bitmap nodes asynchronously. I/O operation is resumed when the responses from all the master bitmap nodes are received. This reduces the stall time of the I/O operation by the write bitmap code.

4.6.1.4 Reduced SetBit Messages for Sequential I/O

V8.4

If sequential writes occur to a disk, it results in sending Setbit messages that set sequential bits in the remote bitmap. The WBM code will now recognize where a number of prior bits in the bitmap have already been set. In this scenario, the WBM code will set additional bits so that if sequential writes should continue, fewer Setbit messages are required. Assuming the sequential I/O continues, the number of Setbit messages will be reduced by about a factor of 10 and thus improve the I/O rate for sequential writes.

System Management Release Notes

4.6 Performance Enhancements

4.6.2 Exception Handling Performance Improvements (Integrity servers Only)

V8.4

The OpenVMS Version 8.4 caches the decoded unwind data. The cache is used in the user-callable calling standard routines, during the exception handling. These calling standard routines are also used in the RTLs, to implement programming language constructs like the try/throw/catch constructs in C++ and the setjmp/longjmp constructs in C programming language.

In case of unexpected errors, the cache can be disabled temporarily using the VMS system parameter, KTK_D3. Its default value of zero enables the cache. A value of one disables the cache. The special parameter, KTK_D3 may have been used by HP supplied debug/test images. If you had such test images on your system, make sure that it is reset to its default value zero. The ability to disable the cache will be removed in the OpenVMS Version 8.4 main release.

4.6.3 Exception Handling (Integrity servers Only)

Some performance improvements have been made to exception handling for OpenVMS Integrity server systems. The change will reduce the overhead of exception handling in some, but not all cases of exception handling.

System Management Release Notes 4–9

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 ﬂush need to be performed on these pages in case the page has code that is executed. This resulted on the I-cache ﬂush occurring on many pages that would never be executed. To avoid the I-cache ﬂush on pages that are never executed, the I-cache is now only done on pages when an instruction is ﬁrst executed on the page. This avoids the I-cache ﬂush on the pages that are never executed and provides an overall system performance beneﬁt.

4.6.5 Global Section Creation and Deletion

Performance improvements have been made to areas of the operating system that create and delete various types of global sections. The beneﬁts of the changes will only be seen on large SMP systems as a reduction in MP Synch.

4.6.6 Dedicated CPU Lock Manager

The Dedicated CPU Lock Manager is a feature typically only turned used on systems with 16 or more CPUs and very high locking rates. Improvements have been made to the Dedicated CPU Lock Manager that results in an increase in the rate at which locking operations can be performed.

4.6.7 Ctrl/T Alignment Faults

A Ctrl/T operation at a terminal resulted in a number of alignment faults. These have been corrected for OpenVMS Version 8.4.

4.7 Error and Warning Messages from ACPI During Boot

V8.4

The following message may be displayed by VMS during boot on cell-based machines (for example, rx8640 or rx7640):

ACPI Error (utmutex-0430): Mutex [1] is not acquired, cannot release [20071219]

The following message may be displayed by VMS during boot on certain systems that have power management enabled (for example, an rx2660 with the latest processors):

ACPI Warning (nseval-0250): Excess arguments - method [_OST] needs 3, found 7 [20080701]

These messages can be ignored. They will be ﬁxed in a future release.

4.8 Large Device Name Support for Accounting Utility

V8.4

The accounting utility is modiﬁed to handle long device names. It can now display device names having seven characters or more, for example, Terminal (TNA) of unit number >9999, MBA device of unit number >999, and other large device names such as TNA10000:, MBA1000:, and so on.

Earlier, the utility displayed arbitrary characters if a device name exceeded seven characters. A new accounting record version (version4) is used to write new records into the accounting.dat ﬁle and the utility is modiﬁed appropriately to read and display these new records.

4–10 System Management Release Notes

System Management Release Notes

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.

If the variable paged pool freelist becomes fragmented, you might beneﬁtby enabling the use of these lookaside lists. The SYSGEN parameter PAGED_LAL_ SIZE sets the maximum size, in bytes, to use for these lookaside lists. Packets larger than this size will still be allocated from the variable paged pool freelist. A modest value, 512 bytes, has been found to help systems doing intensive logical name creation and deletion operations.

Since the parameter is dynamic it can be enabled, adjusted, or disabled as needed. If it was enabled and then lowered there might be some packets on the paged pool lookaside lists that are no longer actively in use. These show up as "Over-limit Lookaside Blocks" in DCL’s and SDA’s command. These packets were used before but are now larger than the new PAGED_LAL_SIZE. These packets will be used again if the SYSGEN parameter is increased to include them, or if there is a paged pool shortage and the packets are reclaimed from the lookaside lists.

SHOW MEMORY/POOL/FULL

To help prevent a runaway condition where packets on a lookaside list starts to consume most or all of paged pool, the paged pool lookaside lists will not be used for packets in the last quarter of paged dynamic pool. If there is a paged pool memory shortage packets on the lookaside lists will be reclaimed as well.

If disabled, at the default value of 0, paged pool behaves as it did in previous versions of OpenVMS, allocating and deallocating packets from the paged pool variable freelist.

4.10 2 TiB Disk Volume Support Restrictions

V8.4

OpenVMS Version 8.4 supports disk volumes up to 2 TiB in size with the following restrictions:

• With OpenVMS versions prior to version 8.4, there is no support for volumes larger than 1 TiB in size or for mounting of volumes larger than 1 TiB. To prevent accidental mounts on earlier versions of OpenVMS, the latest patches for MOUNT will explicitly disallow mounting of volumes larger than 1 TiB on such systems.

• The lexical function F$GETDVI( ) with items codes MAXBLOCK, FREEBLOCKS, EXPSIZE, and VOLSIZE will return a negative number if the value is larger than 1 TiB. This is due to the fact that DCL does 32-bit signed integer arithmetic and comparisons. Command procedures that use F$GETDVI( ) with these item codes may need to be modiﬁed to work with volumes larger than 1 TiB. For more information about handling numeric values outside the range of DCL integer representation using DCL, see the HP OpenVMS DCL Dictionary.

System Management Release Notes 4–11

System Management Release Notes

4.11 Conﬁguring SAS Tape Drives

V8.4

SAS tape drives must be named and conﬁgured using the same commands that are used to conﬁgure Fibre Channel tape drives. For more information, see the section 7.5 "Fibre Channel Tape Support" in the Guidelines for OpenVMS Cluster Conﬁgurations.

4.12 External SAS Disk Device Naming

V8.4

The external SAS drives that are served by non-Smart array controllers can be conﬁgured as $3$DGA<UDID>, where UDID is unique device ID for the LUN. Note that Fibre Channel disk device names use an allocation class value of 1 whereas external SAS disk device names use an allocation class value of 3 to differentiate a SAS device from an Fibre Channel device.

4.13 External Authentication

This section contains release notes pertaining to external authentication. External authentication is an optional feature introduced in OpenVMS Version

7.1 that enables OpenVMS systems to authenticate designated users with their external user IDs and passwords. For detailed information about using external authentication, see the HP OpenVMS Guide to System Security.

Note

A special note for external authentication users. If you are using the SYS$ACM-enabled LOGINOUT.EXE and SETP0.EXE

(SET PASSWORD) images that supports external authentication, an upgrade to higher version of OpenVMS will restore the setup.

If you are using the password policy for customized password processing, it is necessary to restart the ACME Server after the Password Policy shareable image is installed, and the LOAD_PWD_POLICY system parameter is enabled.

Please see the SYS$HELP:ACME_DEV_README.TXT on how to install the ACMELOGIN kit.

4.13.1 External Authentication and Password Policy

V8.4

If you are using external authentication to authenticate users against a source other than the SYSUAF.DAT, and using the password policy for customized password processing, it is necessary to restart the ACME Server after the Password Policy shareable image is installed, and the LOAD_PWD_POLICY system parameter is enabled.

Use the following command to restart the ACME Server:

$ SET SERVER ACME_SERVER /RESTART

4–12 System Management Release Notes

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.

If you want to enable NT LAN Manager external authentication on OpenVMS Cluster member nodes running Integrity servers, you must copy the Integrity servers standalone external authentication images from an Alpha system on which the Advanced Server is installed to the Integrity servers member node, and complete the setup as described in the Advanced Server kit release notes.

4.13.3 SET PASSWORD Behavior Within a DECterm Terminal Session

V7.2

A DECterm terminal session does not have access to the external user name used for login and must prompt for one during SET PASSWORD operations. The external user name defaults to the process’s OpenVMS user name. If the default is not appropriate (that is, if the external user name and mapped OpenVMS user name are different), you must enter the correct external user name.

The following example shows a SET PASSWORD operation initiated by a user with the external user name JOHN_DOE. The mapped OpenVMS user name is JOHNDOE and is the default used by the SET PASSWORD operation. In this case, the default is incorrect and the actual external user name was speciﬁed by the user.

$ set password External user name not known; Specify one (Y/N)[Y]? Y External user name [JOHNDOE]: JOHN_DOE Old password: New password: Verification: %SET-I-SNDEXTAUTH, Sending password request to external authenticator %SET-I-TRYPWDSYNCH, Attempting password synchronization $

4.13.4 No Password Expiration Notiﬁcation on Workstations

V7.1

In the LAN Manager domain, a user cannot log in once a password expires.

PC users receive notiﬁcation of impending external user password expiration and can change passwords before they expire. However, when a user logs in from an OpenVMS workstation using external authentication, the login process cannot determine whether the external password is about to expire. Therefore, sites that enforce password expiration and whose users do not primarily use PCs can choose not to use external authentication for workstation users.

4.13.5 Restriction in ACME_SERVER Process (Integrity servers only)

The SET SERVER ACME/CONFIG=THREAD_MAX command is ignored on Integrity servers for this release because only one worker thread is active.

System Management Release Notes 4–13

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

Connecting a bridged device such as, AD221, HP PCIe combo Card on the PCI bus, where dump devices (DOSD) are conﬁgured on another HBA that is already connected may cause the PCI bus numbering of the dump devices to be renumbered and making it difﬁcult to ﬁnd the valid dump devices.

Workaround

After connecting a new I/O card, validate the boot/dump option. Then, refresh the DUMP_DEV and boot device list.

4.15 SHUTDOWN.COM Changes

V8.4

SHUTDOWN.COM

SYSHUTDWN_0010.COM if it is present. The template contains three sample routines that can help force the queue system to shutdown and restart or failover faster.

is modiﬁed to execute a pre-queue system shutdown procedure

4.16 OpenVMS Cluster Systems

The release notes in this section pertain to OpenVMS Cluster systems.

4.16.1 Cluster over IP (IP Cluster Interconnect)

HP OpenVMS Version 8.4 is enhanced with the Cluster over IP feature. This feature provides the ability to form clusters beyond a single LAN or VLAN segment using industry standard Internet protocol. It also provides improved disaster tolerant capability to OpenVMS clusters.

This section describes known problems and restrictions in Cluster over IP.

4.16.1.1 Software Requirements

V8.4

Cluster over IP is available only on OpenVMS Version 8.4 Alpha and Integrity servers. Cluster over IP also requires HP TCP/IP services for OpenVMS, Version

5.7.

4.16.1.2 Integrity servers Satellite Node and Bootserver in the Same LAN

V8.4

An Integrity server satellite node must be in the same LAN as its boot server for the satellite node to initialize cluster over IP successfully and to join the cluster successfully.

It is also necessary to have LAN cluster communication between Integrity servers satellite node and the boot server for the satellite node to be able to initialize cluster over IP during the satellite bootup.

4–14 System Management Release Notes

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.16.1.4 IPv6 Support

V8.4

Cluster over IP does not support IPv6 type address for cluster communication interface.

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

V8.4

Cluster over IP requires the addresses that are used for cluster communication, which are static, primary address on that interface. Furthermore, IP address used for cluster communication must not be used for Failsafe conﬁguration.

4.16.1.6 Multiple IP Interface Conﬁguration

V8.4

If you conﬁgure multiple IP interface with the same default gateway, loss of communication on any interface may result in disrupted cluster communication with CLUEXITS.

4.16.1.7 ifconﬁg Command Usage

V8.4

If the interface used for cluster communication is reactivated by ifconﬁg, it results in losing cluster communication to other nodes and also results in cluexit of nodes.

4.16.1.8 Multiple Gateway Conﬁguration

V8.4

Cluster over IP conﬁguration information is stored in the conﬁguration ﬁles, which are loaded early in the boot time. This conﬁguration information also includes the default route or gateway that is used by TCP/IP. Currently, only one default route can be entered in the conﬁguration ﬁle and used during the node bootup.

4.16.1.9 Block Transfer XMIT Chaining

V8.4

PEdriver emulates each IP interface used for cluster communication similar to lan interface (BUS). An IP bus will have the characteristics of Xchain_Disabled status as shown. This means that the block transfer packets transmitted through TCP/IP are copied from the PEdriver to the TCP/IP buffers.

System Management Release Notes 4–15

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 Type Events Status Priority Size BufSiz Speed Pkts(S+R) IP Address

------ ---- ------ ------ -------- ----- ------ ----- --------- -----------

4.16.1.10 LANCP for Downline Load

4.16.1.11 Duplex Mismatch

Device Errors + Mgt Buffer MgtMax Line Total Current

IE0 184 Run Online 0 1394 0 N/A 1419711 15.146.235.222

XChain_Disabled

V8.4

Cluster over IP requires LANCP, instead of DECnet for downline load since the changes related to conﬁguring cluster over IP and enabling cluster over IP is available only with CLUSTER_CONFIG_LAN.COM. This restriction will be ﬁxed in the future release of HP Clusters.

V8.4

A duplex mode mismatch or a change in duplex mode from half to full on the host duplex can result in CLUEXIT when IP is used for cluster communication. It is recommended to check for the duplex mismatch issues to avoid cluexit.

4.16.1.12 Conﬁguring a Node During Upgrade

V8.4

If you are upgrading from prior versions to Version 8.4, you cannot enable Cluster over IP. When upgrading it does not call CLUSTER_CONFIG[_LAN] procedure, which is required for enabling Cluster over IP. Hence, the node joins the existing cluster in which it is the member before upgrading.

For enabling Cluster over IP, you must call CLUSTER_CONFIG_LAN procedure explicitly after upgrading.

This restriction will be removed in a future release.

4.16.2 OpenVMS Cluster Support for Integrity VM

V8.4

OpenVMS for Integrity servers Version 8.4 is supported as a guest operating system on Integrity VM. OpenVMS guest can be conﬁgured in a cluster.

4.16.2.1 Cluster Interconnect for OpenVMS Guest

V8.4

OpenVMS guest can use both LAN or Cluster over IP (IPCI) to communicate with other nodes in the cluster.

4.16.2.2 MSCP Support for Clusters in Integrity VM Environment

V8.4

MSCP is used to provide shared storage capability in cluster consisting of OpenVMS guest systems.

4.16.2.3 Online Migration Support

V8.4

Online migration of OpenVMS guest that are part of cluster is not supported.

4–16 System Management Release Notes

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. See the OpenVMS Cluster Software SPD for more information.

• Currently, only two architectures are allowed for supported production environments in an OpenVMS Cluster system. Refer to the HP OpenVMS Version 8.2 Upgrade and Installation Manual for a list of supported cluster conﬁgurations.

4.16.4 Satellite Systems using Port Allocation Class

V8.2

Integrity server Satellite systems that use device naming (also known as port allocation classes) require an additional step to operate correctly in this release. On the satellite boot server node, edit the ﬁle device:

[SYSn.SYSCOMMON.SYS$LDR]SYS$MEMORYDISK.DAT

where device is the disk that contains the satellite’s root and where n is the root of the satellite system) and add the following line to the ﬁle:

SYS$SYSTEM:SYS$DEVICES.DAT, text

You can safely ignore the "Do Not Edit" comment at the top of the ﬁle in this case. The list of ﬁles in SYS$MEMORYDISK.DAT is not order-dependent. This problem is expected to be resolved for the ﬁnal release.

4.17 Mixed-version Cluster Compatibility of a Six-member Shadowset

V8.4

OpenVMS Version 8.4 supports "Extended Membership" volume shadowing feature. This feature allows shadowsets to have more than three and up to six-members. This feature is enabled when a fourth member is added to the shadowset. Following are some of the important points in a mixed-version OpenVMS cluster:

• To use the "Extended Membership" shadowing feature, all the systems that mount the shadowset must be running OpenVMS Version 8.4.

• If you attempt to mount a shadowset on an OpenVMS Version 8.4 system using "Extended Memberships" shadowing feature, the mount fails if the shadowset is already mounted on systems with prior versions of OpenVMS in the cluster.

• If you attempt to mount a shadowset on a system that is not capable of "Extended Memberships" shadowing feature on prior versions of OpenVMS, the mount fails if shadowset is already mounted on an OpenVMS Version 8.4 system in the cluster using the "Extended Memberships" shadowing feature.

System Management Release Notes 4–17

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. If a shadowset is mounted on OpenVMS Alpha or OpenVMS Integrity servers without enabling this feature, the shadowset will mount on the OpenVMS VAX systems. The Virtual Unit characteristic voting ensures compatibility.

4.18 Backward Compatibility of a Six-member Shadowset

V8.4

A new area of the Storage Control Block (SCB) of disk stores the extended membership arrays required to support the "Extended Membership" shadowing feature. Therefore, an attempt to mount a six-member shadowset on prior versions of OpenVMS works only if the members are speciﬁed in the command line.

In OpenVMS prior versions, the $MOUNT/INCLUDE qualiﬁer which is used for reconstructing the shadowset, can ﬁnd only the existing membership list and not the new membership area in the SCB. Hence, it does not mount any members from the new extended membership area in the SCB.

This problem has been ﬁxed in OpenVMS Version 8.4 upgrade kit.

4.19 WBEM Services and WBEM Providers for OpenVMS

This section describes known problems and restrictions in WBEM.

4.19.1 Increased CPU Consumption With WBEM on OpenVMS Guest

V8.4

OpenVMS Guest has a known issue where the CPU consumption of the host gradually increases with the time when WBEM is conﬁgured and running on the guest. Due to this issue, the guest responsiveness gradually decreases with the time, although there is no workload on the guest.

The workaround for this problem is to stop and restart WBEM on the guest when responsiveness is slow by entering the following command:

$ @SYS$STARTUP:WBEM_SERVICES$SHUTDOWN ! Shutdown WBEM on the guest $ @SYS$STARTUP:WBEM_SERVICES$STARTUP ! Startup WBEM on the guest

Alternately, you can reboot the OpenVMS guest when the responsiveness is slow.

4.19.2 WBEM Providers Support for OpenVMS Guest

V8.4

WBEM Providers running on OpenVMS guest does not support WBEM instance data and event indications for CPU, Memory, Enclosure, Chassis, Fan, Power Supply, and Management Processor, since the guest is running in a virtual machine. This will be supported by WBEM providers running on the underlying VM Host operating system.

4–18 System Management Release Notes

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.exe to Unload Providers on OpenVMS

After entering the cimprovider -r command, you must stop and restart the cimserver to complete the process of replacing a provider. (OpenVMS does not support unloading a dynamically loaded image.)

4.19.6 Use Quotes Around Command Line Options

Ensure that you use quotes around a command line option to preserve its case. For example, Correct:

$ cimmofl "-E" "--xml"

Incorrect:

$ cimmof -E -xml

4.20 Writing the System Dump File to an Alternate Disk

V8.4

On Superdome class of servers, writing the system dump ﬁle to an alternate disk (DOSD) does not work and the following message is displayed:

**** Unable to locate SYSDUMP.DMP on any valid DUMP_DEV device **** Attempting to write the crash dump to the system disk

4.21 Monitor Utility Changes

The Monitor utility (MONITOR) has undergone several changes since OpenVMS Version 7.3-2. Most of these changes are related to providing improved formatting of the recording ﬁle and including additional class data. These changes have introduced some compatibility issues between data collected by one version of MONITOR that is subsequently processed by another version. This section discusses these issues.

4.21.1 Guest Operating System on Integrity VM

V8.4

OpenVMS Integrity servers Version 8.4 supports Guest Operating System on HP Integrity Virtual Machines (Integrity VM). When the OpenVMS Integrity servers is running as a guest on an Integrity VM system, the monitor utility indicates the amount of CPU time used by the guest. The Monitor also indicates the amount of CPU time allocated to the guest by Integrity VM.

MONITOR MODES

The When the system is running as a guest, the above commands display "In use by Host" instead of "Compatibility Mode". This ﬁeld is to be interpreted as the amount of CPU time that was unavailable to the current guest and that is being used by the other guests or Integrity VM. The display is scaled based on the number of vCPUs (Virtual CPUs) conﬁgured for the guest irrespective of the actual number of physical CPUs in the host.

and

MONITOR SYSTEM /ALL

commands provide this information.

System Management Release Notes 4–19

System Management Release Notes

4.21 Monitor Utility Changes

$ MONITOR MODES

+-----+ TIME IN PROCESSOR MODES | CUR | on node VMSG7 +-----+ 5-FEB-2009 12:35:39.74

Interrupt State |

MP Synchronization |

Kernel Mode |

Executive Mode |

Supervisor Mode |

User Mode 99 |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦

In use By Host 1 |

Idle Time |

$ MONITOR SYSTEM/ALL

Interrupt State 0.00 0.12 0.00 0.33 MP Synchronization 0.00 0.00 0.00 0.00 Kernel Mode 0.00 0.06 0.00 0.50 Executive Mode 0.00 0.00 0.00 0.00 Supervisor Mode 0.00 0.00 0.00 0.00 User Mode 98.33 98.03 96.50 98.50 In use By Host 1.66 1.77 1.33 3.33 Idle Time 0.00 0.00 0.00 0.00 Process Count 25.00 24.72 24.00 25.00 Page Fault Rate 0.00 10.96 0.00 47.50 Page Read I/O Rate 0.00 0.96 0.00 3.16 Free List Size 46851.00 46945.54 46850.00 47105.00 Modified List Size 317.00 316.90 316.00 317.00 Direct I/O Rate 0.00 1.37 0.00 5.50 Buffered I/O Rate 1.00 2.68 0.66 9.83

OpenVMS Monitor Utility

0 25 50 75 100 +----+----+----+----+

|||||

+----+----+----+----+

OpenVMS Monitor Utility

SYSTEM STATISTICS

on node VMSG9

5-FEB-2009 12:36:44.88

CUR AVE MIN MAX

The data that is displayed when commands are executed on a guest is the time that the guest spends on the virtual CPUs.

4–20 System Management Release Notes

Note

MONITOR MODES

and

MONITOR SYSTEM /ALL

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 ﬁle (that is, playback) or live data from another cluster node. In general, playing back recorded data provides more compatibility than monitoring live remote data.

4.21.3 Playing Back Data from a Recording File

Each ﬁle of recorded MONITOR binary data is identiﬁed by a MONITOR recording ﬁle-structure level ID. You can see this ID by entering the DCL command DUMP /HEADER /PAGE on the ﬁle. The following table lists some recent MONITOR versions and their associated structure level IDs:

Operating System Version

OpenVMS Version 7.3-2 with remedial kit

OpenVMS Versions 8.2, 8.2-1 with remedial kit

OpenVMS Versions 8.3, 8.3-1H1, 8.4 MON01060

These remedial kits are proposed kits that might be issued for the sole purpose of providing improved

compatibility.

MONITOR Recording File Structure ID

MON31050

MON01060

Usually, for you to be able to play back a single MONITOR recording ﬁle, the last two digits of the structure level ID must match those of the running MONITOR version. For example, if you are running OpenVMS Version 7.3-2, you can play back a ﬁle from Version 7.3-2 but not one from Version 8.2.

However, MONITOR Versions 8.2 and higher are specially coded to read recording ﬁles with structure level IDs ending in "50." In addition, a utility in SYS$EXAMPLES, called MONITOR_CONVERT.C, converts a MONxx060 ﬁle to a MON31050 ﬁle. This allows the resulting ﬁle to be read by versions prior to Version 8.2. See MONITOR_CONVERT.C for instructions for building and running the program.

Note that, even though you are allowed to play back a ﬁle, certain MONITOR data classes within the ﬁle might not be available. This can happen if you are using an older MONITOR version to play back a ﬁle created by a newer MONITOR version.

Finally, note that, when you produce a multiﬁle summary from several recording ﬁles, all 8 characters of the structure level ID from all the ﬁles must match.

4.22 System Parameters

V8.3-1H1

This release also contains the new GH_RES_CODE_S2 parameter, which speciﬁes the size in pages of the resident 64-bit S2 space resident image code granularity hint region.

Only images linked with the /SEGMENT=CODE=P2 qualiﬁer can have code placed in this region. See the HP OpenVMS Linker Utility Manual and the INSTALL utility in the HP OpenVMS System Manager’s Manual for more information.

System Management Release Notes 4–21

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. This is the only supported use of this freeware driver. All other uses of this driver continue to be subject to the following documented freeware usage restrictions:

OpenVMS Freeware is provided as is without a warranty. HP imposes no restrictions on its distribution or redistribution. HP does not support services for this software, ﬁx the software, or guarantee that it works correctly.

4.24 CPU_POWER_MGMT Default Value Changed

V8.3-1H1

The default value for the sysgen parameter CPU_POWER_MGMT has been restored to 1 (that is to on). An improved idle power saving algorithm reduces interrupt latency while CPU_POWER_MGMT is on.

4.25 Booting A Satellite System with Reserved Memory

V8.3-1H1

To use the SYSMAN reserved memory feature on an Integrity server satellite system the ﬁle SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA must allow world READ+EXECUTE access. Failure to set this access protection results in the warning when booting the satellite:

%VMS_LOADER-W-Warning: Unable to load file SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA

After running SYSMAN to add memory reservations to a satellite, execute SYS$MANAGER:CLUSTER_CONFIG_LAN.COM to set the correct protection on the VMS$RESERVED_MEMORY.DATA ﬁle. To set the protection, from the cluster conﬁguration procedure "Main Menu" select:

3. CHANGE a cluster member’s characteristics.

From the "CHANGE Menu" select the following:

13. Reset an IA64 satellite node’s boot environment file protections.

What is the satellite name (leave blank to use a specific device and root)?

Enter the satellite name or satellite boot device and root for the system where you added the memory reservation. SYSMAN will be ﬁxed in a later release to eliminate this condition.

4.26 SCACP Error Counter Reports Retransmit Errors

V8.3-1H1

If the PEA0: device on the system shows a number of errors, these errors might be retransmit errors and not actual errors. To verify actual errors, use the SCACP utility to conﬁrm whether there are a number of retransmits on the PEA0 channels and use the LANCP utility to identify whether any actual devices errors

4–22 System Management Release Notes

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. This is especially true in larger clusters.

4.28 INITIALIZE/ERASE=INIT Before Using Media

V8.3-1H1

HP recommends that you issue the DCL command INITIALIZE/ERASE=INIT on storage media prior to using them for the ﬁrst time. This eliminates any stale data that was left from previous use by another operating system or diagnostics.

An indication of such stale data is three questions marks (???) in the console command output, as shown in the following example:

Shell> ls fs1:\

Directory of: fs1:\

00/00/07 19:16p 1,788,984,016 ???

00/00/80 12:00a 0 ???

2 File(s) 1,788,984,016 bytes

0 Dir(s)

The problem will be corrected in a future release.

4.29 Performance Data Collector for OpenVMS (TDC)

V8.3-1H1

TDC_RT Version 2.2-107 is included in the OpenVMS Version 8.3–1H1 installation. An update to TDC Version 2.2-108 is now available from the TDC Web site at:

http://www.hp.com/products/openvms/tdc/

TDC Version 2.2-108 corrects several issues discovered in TDC_RT Version

2.2-107. It also enables collection of internet metrics in TCPware and MultiNet environments, adds additional metrics to several data records, and provides new programming features and sample code in the TDC Software Developers Kit.

4.30 Recovering From System Hangs or Crashes (Integrity servers Only)

V8.2

If your system hangs and you want to force a crash, press Ctrl/P from the console. The method of forcing a crash dump varies depending on whether XDELTA is loaded.

System Management Release Notes 4–23

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. You can force a crash from XDELTA by entering ;C, as shown in the following example:

Console Brk at 8068AD40

8068AD40! add r16 = r24, r16 ;; (New IPL = 3)

If XDELTA is not loaded, pressing Ctrl/P a second time causes the system to respond with the prompt ‘‘Crash? (Y/N)’’. Entering Y causes the system to crash. Entering any other character has no effect on the system.

4.31 DECdtm/XA with Oracle 8i and 9i (Alpha Only)

V7.3-2

When you are using DECdtm/XA to coordinate transactions with the Oracle 8i/9i XA Compliant Resource Manager (RM), do not use the dynamic registration XA switch (xaoswd). Version 9.0.1.0.0 of the Oracle shareable library that supports dynamic registration does not work. Always use the static registration XA switch (xaosw) to bind the Oracle RM to the DECdtm/XA Veneer.

The DECdtm/XA V2.1 Gateway now has clusterwide transaction recovery support. Transactions from applications that use a clusterwide DECdtm Gateway Domain Log can now be recovered from any single-node failure. Gateway servers running on the remaining cluster nodes can initiate the transaction recovery process on behalf of the failed node.

4.32 Device Unit Number Increased

V8.2

In the past, OpenVMS would never create more than 10,000 cloned device units, and unit numbers would wrap after 9999. This had become a limitation for some devices, such as mailboxes or TCP/IP sockets.

Starting with OpenVMS Version 7.3-2, OpenVMS will create up to 32,767 devices if the DEV$V_NNM bit is clear in UCB$L_DEVCHAR2 and if bit 2 is clear in the DEVICE_NAMING system parameter. This does not require any device driver change.

However, programs and command procedures that are coded to assume a maximum device number of 9999 may need to be modiﬁed.

4.33 EDIT/FDL: Fixing Recommended Bucket Size

V7.3

Prior to OpenVMS Version 7.3, when running EDIT/FDL, the calculated bucket sizes were always rounded up to the closest disk-cluster boundary, with a maximum bucket size of 63. This could cause problems when the disk-cluster size was large, but the ‘‘natural’’ bucket size for the ﬁle was small, because the bucket size was rounded up to a much larger value than required. Larger bucket sizes increase record and bucket lock contention, and can seriously impact performance.

4–24 System Management Release Notes

System Management Release Notes

4.33 EDIT/FDL: Fixing Recommended Bucket Size

OpenVMS Version 7.3 or higher modiﬁes 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. Certain privileged operations within this utility could render OpenVMS Integrity servers unbootable.

4.35 Error Log Viewer (ELV) Utility: TRANSLATE/PAGE Command

V7.3-2

If a message is signaled while you are viewing a report using the /PAGE qualiﬁer with the TRANSLATE command, the display might become corrupted. The workaround for this problem is to refresh the display using Ctrl/W.

If you press Ctrl/Z immediately after a message is signaled, the program abruptly terminates. The workaround for this problem is to scroll past the signaled message before pressing Ctrl/Z.

4.36 Cluster Compatibility Patch Kits

V8.3

Before introducing an OpenVMS Version 8.2–1 system into an existing OpenVMS Cluster system, you must apply certain patch kits (also known as remedial kits) to your systems running earlier versions of OpenVMS. Note that these kits are version speciﬁc.

The versions listed in Table 4–2 are supported in a warranted conﬁguration. For more information about these conﬁgurations, see the HP OpenVMS Version 8.2–1 for Integrity Servers Upgrade and Installation Manual.

Table 4–2 lists the facilities that require patch kits and the patch kit ﬁle names. Each patch kit has a corresponding readme ﬁle by the same name with a .README ﬁle extension.

You can either download the patch kits from the following Web site or contact your HP Support representative to receive the patch kits on media appropriate for your system:

http://www2.itrc.hp.com/service/patch/mainPage.do

Patch kits are periodically updated on an as-needed basis. Always use the most recent patch kit for the facility, as indicated by the version number in the kit’s readme ﬁle. The most recent version of each kit is the version posted on the Web site.

Note

System Management Release Notes 4–25

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

C RTL VMS732_ACRTL-V0100

Drivers VMS732_DRIVER-V0200

PCSI VMS732_PCSI-V0100

OpenVMS Alpha Version 8.2

DECnet-Plus for OpenVMS Alpha ECO1

OpenVMS Integrity servers Version 8.2

This kit is required if you are running this software in your conﬁguration.

VMS732_UPDATE-V0600.

VMS82A_UPDATE-V0200

DNVOSIECO01_V82

VMS82I_UPDATE-V0200

4.36.1 Patch Kits Needed for Cluster Compatibility

V8.2

Before introducing an OpenVMS Version 8.2 (or higher) system into an existing OpenVMS Cluster system, you must apply certain patch kits (also known as remedial kits) to your systems running earlier versions of OpenVMS. If you are using Fibre Channel, XFC, or Volume Shadowing, additional patch kits are required. Note that these kits are version speciﬁc.

The versions listed in Table 4–2 are supported in either a warranted conﬁguration or a migration pair conﬁguration. For more information about these conﬁgurations, refer to either HP OpenVMS Cluster Systems or the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

Table 4–2 lists the facilities that require patch kits and the patch ID names. Each patch kit has a corresponding readme ﬁle with the same name (ﬁle extension is .README).

You can either download the patch kits from the following web site (select the OpenVMS Software Patches option), or contact your HP support representative to receive the patch kits on media appropriate for your system:

http://www2.itrc.hp.com/service/patch/mainPage.do

Note

4–26 System Management Release Notes

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

Audit Server VAXAUDS01_073

Cluster VAXSYSL01_073

DECnet-Plus VAX_DNVOSIECO04-V73

DECwindows Motif VAXDWMOTMUP01_073

DTS VAXDTSS01_073

Files 11 VAXF11X02_073

MAIL VAXMAIL01_073

MIME VAXMIME01_073

MOUNT VAXMOUN01_073

RMS VAXRMS01_073

RPC VAXRPC02_073

Volume Shadowing VAXSHAD01_073

System VAXSYS01_073

For operating guidelines when using VAX systems in a cluster, refer to Section 4.16.3.

VMS732_UPDATE-V0600

Note that VAX systems cannot be in a cluster with Integrity servers. For a complete list of warranted groupings within a cluster, refer to the HP OpenVMS Version 8.3 Upgrade and Installation Manual.

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

Third-Party Products

V7.3-2

OpenVMS Alpha Version 7.2-1 introduced the multipath feature, which provides support for failover between the multiple paths that can exist between a system and a SCSI or Fibre Channel device. OpenVMS Alpha Version 7.3-1 introduced support for failover between Fibre Channel multipath tape devices.

This multipath feature can be incompatible with some third-party disk-caching, disk-shadowing, or similar products. HP advises that you do not use such software on SCSI or Fibre Channel devices that are conﬁgured for multipath failover until this feature is supported by the producer of the software.

Third-party products that rely on altering the Driver Dispatch Table (DDT) of either the OpenVMS Alpha SCSI disk class driver (SYS$DKDRIVER.EXE), the OpenVMS Alpha SCSI tape class driver (SYS$MKDRIVER.EXE), or the SCSI generic class driver (SYS$GKDRIVER) may need to be modiﬁed in order to function correctly with the SCSI multipath feature.

System Management Release Notes 4–27

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.

Note

If you are using a third-party disk-caching product or disk shadowing application, refrain from using it in an OpenVMS SCSI or Fibre Channel multipath conﬁguration until you conﬁrm that the application has been revised using these new routines.

For more information about OpenVMS Alpha SCSI and Fibre Channel multipath features, refer to Guidelines for OpenVMS Cluster Conﬁgurations.

4.36.3 DDT Intercept Establisher Routines and Device Conﬁguration Notiﬁcation Results

V8.3

To ensure proper behavior of certain routines, a patch kit is required. Using those routines without the required patch kit can result in system hangs, crashes, or data corruption, and is not supported by HP.

For more information about these routines, see the HP OpenVMS Alpha Version

7.3–2 New Features and Documentation Overview manual.

4.36.4 Cluster Performance Reduced with CI-LAN Circuit Switching

V7.3-1

In rare cases, in an OpenVMS Cluster conﬁguration with both CI and multiple FDDI, 100 Mb/s or Gb/s Ethernet-based circuits, you might observe that SCS connections are moving between CI and LAN circuits at intervals of approximately 1 minute. This frequent circuit switching can result in reduced cluster performance and may trigger mount veriﬁcation of shadow set members.

PEdriver can detect and respond to LAN congestion that persists for a few seconds. When it detects a signiﬁcant delay increase or packet losses on a LAN path, the PEdriver removes the path from use. When it detects that the path has improved, it begins using it again.

Under marginal conditions, the additional load on a LAN path resulting from its use for cluster trafﬁc may cause its delay or packet losses to increase beyond acceptable limits. When the cluster load is removed, the path might appear to be sufﬁciently improved so that it will again come into use.

If a marginal LAN path’s contribution to the LAN circuit’s load class increases the circuit’s load class above the CI’s load class value of 140 when the marginal path is included (and, conversely, decreases the LAN circuit’s load class below 140 when the path is excluded), SCS connections will move between CI and LAN circuits.

You can observe connections moving between LAN and CI circuits by using SHOW CLUSTER with the CONNECTION and CIRCUITS classes added.

4–28 System Management Release Notes

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.

Examples of SCACP commands are:

$ MC SCACP SCACP> SET PORT PNA0 /PRIORITY=2 ! This will cause circuits from local

! CI port PNA0 to be chosen over ! lower priority circuits.

SCACP> SET PORT PEA0 /PRIORITY=2 ! This will cause LAN circuits to be

• You can use the SCACP SHOW CHANNEL commands to determine which channels are being switched into or out of use. Then you can use SCACP to explicitly exclude a speciﬁc channel by assigning it a lower priority value than the desired channels. For example:

SCACP> SET CHANNEL LARRY /LOCAL=EWB/REMOTE=EWB /PRIORITY=-2

Note that CHANNEL and LAN device priority values in the range of max, max-1 are considered equivalent; that is, they are treated as if they both had

the maximum priority value. A difference of 2 or more in priority values is necessary to exclude a channel or LAN device from use.

! chosen over lower priority circuits.

4.36.5 Multipath Tape Failover Restriction

V7.3-1

While the INITIALIZE command is in progress on a device in a Fibre Channel multipath tape set, multipath failover to another member of the set is not supported. If the current path fails while another multipath tape device is being initialized, retry the INITIALIZE command after the tape device fails over to a functioning path.

This restriction will be removed in a future release.

4.36.6 No Automatic Failover for SCSI Multipath Medium Changers

V7.3-1

Automatic path switching is not implemented in OpenVMS Alpha Version 7.3-1 or higher for SCSI medium changers (tape robots) attached to Fibre Channel using a Fibre-to-SCSI tape bridge. Multiple paths can be conﬁgured for such devices, but the only way to switch from one path to another is to use manual path switching with the SET DEVICE/SWITCH command.

This restriction will be removed in a future release.

4.37 OpenVMS Galaxy (Alpha Only)

The following sections contain notes pertaining to OpenVMS Galaxy systems.

Note that OpenVMS Galaxy is supported on OpenVMS Alpha systems only.

System Management Release Notes 4–29

System Management Release Notes

4.37 OpenVMS Galaxy (Alpha Only)

4.37.1 Galaxy Deﬁnitions

V8.2

Because the HP OpenVMS Alpha Partitioning and Galaxy Guide is not being updated for this release, this note provides improved deﬁnitions of the word Galaxy, which depends on context.

Table 4–3 Galaxy Deﬁnitions

Galaxy as a: Functions this way:

License Is required to create and run multiple instances of OpenVMS in a

System parameter

Soft partition Provides the capability of several OpenVMS instances to execute

single computer. Without this license, only one instance of OpenVMS can be run in a single computer.

Sets memory sharing. GALAXY set to 1 speciﬁes that OpenVMS instances with the parameter set in a hard partition will share memory between soft partitions within that hard partition. (You can run more than two soft partitions in a hard partition, and you may not want to share memory among all of them.) Note that this parameter only speciﬁes whether a node uses shared memory. There is no need to use this parameter to run multiple, cooperative instances of OpenVMS; this is achieved by console setup of the desired conﬁguration tree. GALAXY set to 0 means that memory is not shared (the default).

cooperatively in a single computer so as to be able to migrate CPUs, use APIs, share memory, and so on. Platform partitioning makes possible the separation of resources into multiple soft partitions, each of which can run an OS instance. A soft partition is that subset of resources that the OS instance running in it can see and use.

4.38 Multiple nPartitions on Cell-based Systems

V8.2-1

If you have multiple nPartitions on your HP Integrity rx7620, HP Integrity rx8620, or HP Integrity Superdome servers, and you are running a multioperating system environment with OpenVMS on one of the nPartitions, one of the other operating systems might register an error or event on the System Event Log (SEL) while OpenVMS is booting. OpenVMS holds the SEL until it has produced a table of Field Replaceable Units (FRU), which might cause other operating systems to register an error or an event.

4.38.1 OpenVMS Graphical Conﬁguration Manager

V8.2

The OpenVMS Graphical Conﬁguration Manager (GCM) is now supported for AlphaServer ES47/ES80/GS1280 Galaxy conﬁgurations. Previously, only the Graphical Conﬁguration Utility (GCU) was supported.

4.38.2 Galaxy on ES40: Uncompressed Dump Limitation

Permanent Restriction

On AlphaServer ES40 Galaxy systems, you cannot write a raw (uncompressed) dump from instance 1 if instance 1’s memory starts at or above 4 GB (physical). Instead, you must write a compressed dump.

4–30 System Management Release Notes

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. If there is shared SCSI or Fibre Channel, I/O will hang on the sharing nodes and all paths to those devices will be disabled.

4.39 Corrupted Version 2 Format Database

V7.3-2

If you create eight or more volatile subkeys in a key tree and then reboot a standalone system or a cluster, the OpenVMS Registry server can corrupt a Version 2 format Registry database when the server starts up after the reboot.

To avoid this problem, do one of the following:

• Do not use volatile keys.

• Use a Version 1 format database.

Note that Advanced Server for OpenVMS and COM for OpenVMS do not create volatile keys.

4.40 System Parameters

The following sections contain notes related to system parameters.

4.40.1 New System Parameters

V8.3

To learn about new system parameters, see the HP OpenVMS Version 8.3 New Features and Documentation Overview.

4.40.2 Obsolete System Parameters

V8.3

The following system parameters are marked as obsolete in OpenVMS Version

8.3:

• SMP_CPUS

• SMP_CPUSH

• IO_PREFER_CPU

• IO_PREFER_CPUS

• NPAG_AGGRESSIVE

• NPAG_GENTLE

• SCH_CTLFLAGS

• TTY_SILOTIME

• BALSETCNT

• BREAKPOINTS

System Management Release Notes 4–31

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. For more information, see the HP OpenVMS System Management Utilities Reference Manual.

• BALSETCNT - wording changes

• BREAKPOINTS - now dynamic

• MMG_CTLFLAGS - additional bits deﬁned; wording changes

• MULTITHREAD - Integrity servers support added

• NISCS_MAX_PKTSZ - wording changes

• NISCS_PORT_SERV - bit deﬁnition changes

• SECURITY POLICY - Bits 13 and 14 deﬁned

• SHADOW_SYS_DISK - wording changes

• WBM_MSG_UPPER - default changed

For detailed descriptions of these parameters see the online help or the HP OpenVMS System Management Utilities Reference Manual.

4.41 Terminal Fallback Facility

V8.2

On OpenVMS Alpha systems, the Terminal Fallback Facility (TFF) includes a fallback driver (SYS$FBDRIVER.EXE), a shareable image (TFFSHR.EXE), a terminal fallback utility (TFU.EXE), and a fallback table library (TFF$MASTER.DAT).

TFFSHR has been removed from IMAGELIB because it is not a documented, user-callable interface. The image is still available in the SYS$LIBRARY: directory.

4–32 System Management Release Notes

Note

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

To enable fallback or to change fallback characteristics, invoke the Terminal Fallback Utility (TFU), as follows:

$ RUN SYS$SYSTEM:TFU TFU>

To enable default fallback to the terminal, enter the following DCL command:

$ SET TERMINAL/FALLBACK

OpenVMS Alpha TFF differs from OpenVMS VAX TFF in the following ways:

• On Alpha systems, the TFF fallback driver is named SYS$FBDRIVER.EXE. On VAX systems, the TFF fallback driver is named FBDRIVER.EXE.

• On Alpha systems, TFF is capable of handling 16-bit character fallback. The OpenVMS Alpha fallback table library (TFF$MASTER.DAT) contains four more 16-bit character tables than the VAX library. Table 4–4 describes these additional tables.

Table 4–4 TFF Character Fallback Tables

Table Name Base Description

BIG5_HANYU BIG5 BIG5 for CNS 11643 (SICGCC) terminal/printer

HANYU_BIG5 CNS CNS 11643 (SICGCC) for BIG5 terminal/printer

HANYU_TELEX CNS CNS 11643 for MITAC TELEX-CODE terminal

HANGUL_DS KS KS for DOOSAN 200 terminal

These tables are used mainly by the Asian region. Also, the table format was changed due to the support of 16-bit character fallback.

• On Alpha systems, the TFU command SHOW STATISTICS does not display the size of the fallback driver (SYS$FBDRIVER.EXE).

RT terminals are not supported by TFF.

For more information about the Terminal Fallback Facility, refer to the now archived OpenVMS Terminal Fallback Utility Manual on the OpenVMS documentation website:

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

Click on ‘‘Archived documents’’ in the left sidebar to link to this manual.

4.42 User Environment Test Package (Integrity servers Only)

V8.2

The User Environment Test Package (UETP) can be used with the following cautions:

• During the load phase, there are sporadic access violations in UETMEMY01. This does not terminate execution or really affect the validity of the run. UETP is still useable and produces valid results.

System Management Release Notes 4–33

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 ﬁne. 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.43 Recommended Caching Methods

Permanent Restriction

Virtual I/O Cache (VIOC) — also known as VAX Cluster Cache (VCC) — is not available on OpenVMS Integrity servers. On Integrity servers, setting the SYSGEN parameter VCC_FLAGS to 1 is equivalent to setting VCC_FLAGS to 0 or not loading caching at all.

HP recommends Extended File Cache (XFC) as the preferred method for caching on both Alpha and Integrity servers. For more information about XFC, refer to the HP OpenVMS System Manager’s Manual.

In a future release of OpenVMS Alpha, support for VIOC will be removed.

4.44 Analyze Utility for OpenVMS

The following sections describe corrected problems in the Analyze Utility for OpenVMS.

4.44.1 Formatted Symbol Vector Correctly Shown in Data Segment

Previously, the symbol vector summary information did not indicate the segment in which the symbol vector resided. The symbol vector was formatted only in the dynamic segment.

This problem is ﬁxed in OpenVMS Version 8.3-1H1. The formatted symbol vector now appears with the data segment in which it is contained. The formatted symbol vector is embedded in data and visible in a dump of the data.

To avoid formatting the same data twice, the symbol vector is no longer shown with the dynamic segment. To make formatting of the symbol vector easy, the SYMBOL_VECTOR keyword is allowed for the /SEGMENT qualiﬁer. When you specify this keyword, the resulting output is only the formatted symbol vector. The surrounding data are not shown. To show and format all of the data, select the segment by number.

To get equivalent output for the former command /SEGMENT=DYNAMIC for symbol vectors, use the /SEGMENT=(DYNAMIC,SYMBOL_VECTOR) qualiﬁer.

The summary information shows the name of the data segment that contains the symbol vector.

4.44.2 Transfer Array Formatted in Data Segment

Previously, if you selected the data segment that contained the transfer array (either by segment number or with the ALL keyword), the transfer array was not formatted. Information about the transfer array was shown only in the summary.

This problem is corrected in OpenVMS Version 8.3-1H1. The formatted tranfer array now appears in the data segment.

4–34 System Management Release Notes

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. The formatted system version array now appears in the dynamic segment.

4.44.4 Enhancements for the /SEGMENT Qualiﬁer

Enhancements have been made to the /SEGMENT qualiﬁer for dynamic segments. Analyze has been enhanced to accept keywords for the /SEGMENT=DYNAMIC qualiﬁer to provide customized information. The keywords for selectable information are:

ALL—(Default) Formats all parts of the dynamic segment

TAGS—Formats the tag array

IMAGE_STRINGS—Formats strings of the speciﬁed image

RELOCATIONS—Formats the image relocations

FIXUPS—Formats the image ﬁxups

SYSTEM_VERSION_ARRAY—Formats the system version array

The default, /SEGMENT=ALL, formats all of the image information.

Note that formatting using the TAGS keyword includes the names of the needed images, so you do not have to add IMAGE_STRINGS to print the names.

4.44.5 Support for Section Escaping Added

On OpenVMS V8.3, the Analyze utility did not complete when analyzing an object module with more than 65,280 sections. Instead, it looped when attempting to print the section header table.

This problem has been ﬁxed in OpenVMS V8.3-1H1.

4.45 INSTALL Utility for OpenVMS (Installing Resident Images in S2 Space)

The INSTALL utility now supports installing code segments of resident images into 64-bit S2 address space. Not all code can run in a full 64-bit address space (P2 or S2). For example, the code must be prepared for 64-bit PCs when handling exceptions. Also, some compilers require the /POINTER_SIZE=64 command qualiﬁer, when generating code, suitable for a 64-bit address space.

To avoid mapping unprepared code in S2 space, the INSTALL utility by default will continue to map the code segments in S0/S1 space. The INSTALL utility will map code segments of resident images to S2 if two conditions are met:

• The developer explicitly conﬁrmed that the code is 64-bit ready by using the /SEGMENT_ATTRIBUTE=CODE=P2 qualiﬁer when linking the image.

• There is sufﬁcient pre-allocated space in the resident code region in the S2 space to map the code segments. The size of the region is determined by the system parameter GH_RES_CODE_S2 (number of pages). The default value is set to 0. That means that by default even 64-bit ready resident images have their code mapped in S0/S1 space.

System Management Release Notes 4–35

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.3-1H1 include the following:

• The run-time library had faulty code that accessed memory just freed to advance a pointer. In multithreaded code, another thread could reuse that memory before the original thread could advance its pointer. This has been ﬁxed by updating accesses prior to freeing pointers.

Programming Release Notes

• A new processwide exception processing mode— introduced. In this mode, non-C++ exceptions, also known as OpenVMS conditions, cannot be caught in a C++ catch-all handler. This mode can be requested by calling

pure_unix

cxxl$set_condition(pure_unix);

condition_behavior enum declared in <cxx_exception.h> header has been extended to include pure_unix member.

To demonstrate how sample. As it is written, the program crashes with ACCVIO. If the call to

cxxl$set_condition( )

exits:

#include <stdio.h> #include <cxx_exception.h>

void generateACCVIO() { *((int*)0) = 0; }

argument:

cxxl$set_condition(condition_behavior)

pure_unix

is commented out, the program outputs "caught" and

mode works, consider the following program

pure_unix

— has been

with a

Programming Release Notes 5–1

Programming Release Notes

5.2 C++ Run-Time Library

int main() { cxxl$set_condition(pure_unix); try { generateACCVIO();

} catch(...) { puts("caught");

To use this new functionality you must have a new version of

cxx_exception.h

ﬁle provided with the Version 7.3 compiler (or higher).

• The run-time library sometimes failed to destruct objects of automatic storage duration deﬁned in a function, if such a function exited via an exception that could be caught. This problem has been ﬁxed.

• The run-time library now allows the thread cancel signal (CMA$_ALERTED) and the thread exit signal (CMA$_EXIT_THREAD) to be caught in a catch handler with a pointer or a reference to type CXXL$PTHREAD_ CANCEL (or CX6L$PTHREAD_CANCEL) and CXXL$PTHREAD_EXIT (or CX6L$PTHREAD_EXIT), respectively, if catching the signals are enabled. The new types catch these signals exclusively.

}

Note

, which is included in the CXXL$ANSI_DEF.TLB

Note

To use this new functionality, you must have a new version of

cxx_exception.h

provided with the V7.3 compiler (or higher).

• The C++ RTL has changed its internal mapping of SIGTRAP from SS$_ BREAK to SS$_TBIT, to match a recent C RTL change.

• The C++ RTL used to call exception during stack unwinding, even if that destructor did not exit via the exception. This problem has been ﬁxed.

• The C++ RTL used to call a non-C++ OpenVMS condition) was raised while a C++ exception was being processed. This behavior has been reﬁned to calling if the raised OpenVMS condition also leads to unwinding the stack.

• Because OpenVMS conditions can be caught in C++ catch handlers, the C++ RTL converts the conditions to an internal format that matches the representation of C++ exceptions. This conversion would sometimes lead to incorrect information being shown in the traceback. This problem has been ﬁxed.

The following problems are ﬁxed in this version of the C++ Library (Version 7.3 and higher compiler):

, which is included in the CXXL$ANSI_DEF.TLB

std::terminate( )

when a destructor raised an

, if a foreign exception (such as

std::terminate( )

only

• As described in Apache Software Foundation Issues website), the function in <algorithm.cc> header has a problem which, for some input sequences, can adversely affect performance of

5–2 Programming Release Notes

http://issues.apache.org/jira/browse/STDCXX-397

(the

_ _introsort_loop( )

std::sort

. For more

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 ﬁxed. However, for some input sequences, the ﬁx can change the behavior of which elements that have equivalent ordering are placed into the sorted sequence. Though this change in behavior is permissible because,

std::stable_sort

order of elements having equivalent ordering, to avoid breaking applications that rely on existing behaviour of _ _RW_ FIX_APACHE_STDCXX_397 macro. The ﬁx is in effect only when the program is compiled with this macro deﬁned.

• When compiled in standard GNU mode, the library now deﬁnes the _RWSTD_ NO_IMPLICIT_INCLUSION macro, which causes library headers to include their respective template deﬁnition ﬁles. This is necessary because in standard GNU mode, implicit inclusion is disabled.

Before this change, the program below would link with undeﬁned symbol when compiled in standard GNU mode:

std::sort

#include <vector>

int main() {

std::vector<int> v; v.push_back(0);

}

std::sort

does not guarantee any particular relative

with regard to the relative order in

std::sort

, the ﬁx is conditionalized with

unlike

• According to section 27.6.1.3 Standard, the following class should call is the case for an empty line. While on Integrity servers the functions set failbit, on Alpha systems they do not, for example:

setstate(failbit)

istream_type& get(char_type *s, streamsize n, char_type delim); istream_type& get(char_type *s, streamsize n);

[lib.istream.unformatted]

get member

functions of the

if no characters have been stored, as

std::basic_istream

of the C++

5.3 Process/Application Hangs

The following restriction applies to the LIBRTL documentation for the

lib$find_image_symbol

If your application might dynamically activate shareable images that use pthreads (or the older CMA thread interface), the main image must be linked with the

pthread$rtl

run-time library routine:

image.

5.4 AST Delivery Clariﬁcation in Programs using POSIX Threads

V8.3-1H1

It is possible to utilize ASTs in threaded programs. Section B.12.5 in the Guide to the POSIX Threads Library describes some general usage notes and cautions. However, that section does not make clear how AST delivery behaves in programs with upcalls disabled (which is the default conﬁguration).

In a program with upcalls disabled, user-mode ASTs will interrupt whatever thread happens to be executing at the moment that the AST is delivered. Therefore the AST service routine cannot make any assumptions about the context in which it executes (with respect to thread ID, stack space available, and so on.)

Programming Release Notes 5–3

Programming Release Notes

5.4 AST Delivery Clariﬁcation 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.3-1H1

Starting with OpenVMS Version 8.3, the $PARSE service further validates all directories named in a directory speciﬁcation to ensure that the directory characteristic is set. In previous OpenVMS versions, attempting to use a ﬁle with a .DIR extension that was not a directory resulted in a SS$_BADIRECTORY error from the $OPEN service, but not necessarily from the $PARSE service. As of Version 8.3, the error is consistently returned by the $PARSE service as long as it is not a syntax-only $PARSE.

5.6 No-IOLOCK8 Fibre Channel Port Drivers

V8.3-1H1

Many I/O subsystem components synchronize their operations across CPUs by using the IOLOCK8 spinlock, which has made acquiring the spinlock a performance bottleneck. As of Version 8.3-1H1, each Fibre Channel port driver (SYS$PGQDRIVER, SYS$PGADRIVER and SYS$FGEDRIVER) device uses its own port-speciﬁc spinlock instead of IOLOCK8 to synchronize its internal operations. In most conﬁgurations, this results in a signiﬁcant decrease in the amount of time each CPU spends waiting for the IOLOCK8 spinlock as well as some increase in the Fibre Channel I/O rate.

Some minor changes are required to any class driver that connects to one of these new port drivers, so customers must determine whether they are running any non-HP class drivers that will not work with them. The simplest way to do this is to examine the output of the SDA command the name of any third-party class driver device appears in the device hierarchy for an FGx0 or PGx0 port device in the "Device" column.

For more information, refer to the notes following this sample SDA session.

$ ANALYZE/SYSTEM

OpenVMS system analyzer

SDA> CLUE SCSI /SUMMARY

CLUE SCSI/SUMMARY

and see whether

5–4 Programming Release Notes

HP OpenVMS User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual