================================================================================= HP OpenVMS Enablement Kit for Integrity Servers rx2800 i2 and VMS84I_UPDATE-V0500 Release Notes ================================================================================= 1 KIT NAME: VMS84I_UPDATE-V0500 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement). This kit supports new hardware functionality, HP recommends that users review the installation instructions in section 10. 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: This update kit supports the following: * Support for Intel Itanium 9300 processor series based rack mount rx2800 i2 server. This kit includes new hardware/functionality support for the following: * 16 GB memory dual in-line memory modules (DIMMs) on BL8x0c i2 server blades. * 450 GB and 600 GB Serial Attached SCSI (SAS) disk drives on BL8x0c i2 server blades. * Dual core processor on BL870c i2 server blades and BL890c i2 server blades. * Flex10 technology For more information, see Section 5. 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_UPDATE-V0400 - VMS84I_MUP-V0100 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0200 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_UPDATE-V0500 KIT 5.1 New functionality addressed in this kit 5.1.1 New hardware support associated with the rx2800 i2 servers o IntelŪ ItaniumŪ 9300 processor series based rack mount rx2800 i2 server This kit supports the 2-socket HP Integrity rx2800 i2 server which includes the latest IntelŪ ItaniumŪ 9300 series quad-core processors and dual-core processors, with up to 192 GB double-data-rate three (DDR3) memory, and six I/O expansion slots, eight hot-plug Serial Attached SCSI (SAS) small form factor (SFF) 2.5 inch drives and 2D built-in graphics option. The rx2800 i2 server can scale to run a range of mission-critical applications. Its built-in resiliency, advanced server management features, and 2U compute density make the rx2800 i2 server an ideal choice for smaller, more remote, or legacy rack mount environments. For more information about rx2800 i2 servers and its specifications, see: http://h18004.www1.hp.com/products/quickspecs/13770_na/13770_na.html o 4 GB DIMM on rx2800 i2 server with maximum of 96 GB DDR3 memory. o Serial Advanced Technology Attachment (SATA) DVD-ROM or DVD+RW drive which ships with the rx2800 i2 servers. o HP Smart Array P411 controller (6 GB/sec SAS) Note: This release supports the HP Smart Array P411 controller only on rx2800 i2 servers with HP StorageWorks D2600/2700 disk enclosures as target. For more information, see the following websites: http://h18004.www1.hp.com/products/servers/proliantstorage/arraycontrollers/smartarrayp411/index.html?jumpid=reg_R1002_USEN http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/12169-304616-3930445-3930445-3930445-3954787.html o Minimum firmware required for rx2800 i2 servers Table 5-1 lists the minimum firmware revisions for rx2800 i2 servers. Table 5-1 Minimum firmware required for rx2800 i2 servers [ilo00237d445e76] CM:hpiLO-> sysrev SYSREV Revisions Active Pending ------------------------------------- iLO FW : 01.30.30 System FW : 01.09 MHW FPGA : 01.14 Power Mon FW : 02.09 PRS HW : 02.06 IOH HW : 02.00 The LOM and SAS firmware versions are: LOM : 3.8.18 SAS : 3.18 These pieces of firmware are part of the firmware bundle version 21.07. 5.1.2 New hardware support, associated with BL8x0c i2 server blades, for the following: o 16 GB memory dual in-line memory module (DIMMs) on BL8x0c i2 server blades. o 450 GB and 600 GB SAS disk drives on BL8x0c i2 server blades. o Dual core processor on BL870c i2 server blades and BL890c i2 server blades. Minimum firmware required for BL8x0c i2 server blades to support the above functionalities. For more details, see Table 5-2. Table 5-2 Minimum firmware required for BL8x0c i2 server blades. Onboard Administrator : 3.21 [End12b_gstl0353] CM:hpiLO-> sysrev SYSREV Revisions Active Pending ------------------------------------ iLO FW : 01.30.30 System FW : 01.24 MHW FPGA : 01.14 Power Mon FW : 03.04 Front Panel HW : 04.00 02.00 and 03.00 are also acceptable PRS HW : 02.07 02.06 is also acceptable IOH HW : 02.02 1.02, 1.03, and 02.00, are also acceptable These pieces of firmware are part of the firmware bundle version 21.08. The On-Board Administrator (OA) firmware version can be found using the SHOW OA INFO command on the Command Line Interface (CLI). On the web browser, the OA firmware version is available as a link in the left navigation pane under the "Enclosure Information" section. To obtain the Blade firmware, go to the MP Command Menu (CM) prompt and type the SR or SYSREV command. 5.1.3 New features supported o Support for Flex10 technology Flex10 technology is a hardware-based solution that enables you to partition a 10 Gigabit Ethernet (10 GbE) connection and regulate the data speed of each partition. HP Flex10 is available only with Virtual Connect (VC), and is currently available for implementation only with a few supported HP BladeSystem servers. The Flex10 technology enables VC to configure a single 10 GB network port of BladeSystem servers to represent four physical network interface card (NIC) devices, also called Flex-NICs, with a total bandwidth of 10 Gbps. These four Flex-NICs appear to the operating system as discrete NICs, each with its own driver instance. While the Flex-NICs share the same physical port, traffic flow for each one is isolated with its own MAC address and virtual local area network (VLAN) tags between the Flex-NIC and VC Flex10 interconnect module. The transmit bandwidth available to each Flex-NIC is controlled by the administrator through the VC interface. For more information on the Flex10 technology and benefits, see the following website: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf The Flex10 technology includes Flex10 capable NIC cards and Flex10 VC modules. This update kit supports the following: - Flex10 capable NICs: * LAN On Motherboard (LOMs) ports of BL8x0c i2 server blades * Mezzanine cards - HP NC532m - 467799-B21 - VC Flex10 modules: * HP BLc VC Flex10 Ethernet Module - 455880-B21 - Servers with which Flex10 is supported: * BL8x0c i2 server blades - VC/FC modules: * HP 8 Gb 24 Port Virtual Connect Fibre Channel Module (P/N 466482-B21) * 8 Gb 20 Port Virtual Connect Fibre Channel Module (P/N 572018-B21) * HP Virtual Connect 4 Gb Fibre Channel Module (P/N 409513-B22) The following device control channel (DCC) protocol events are supported as part of Flex10 feature: - Dynamic bandwidth changes reported by the Flex10 VC module - Link state changes reported by the Flex10 VC module o Support for vMedia rx2800 i2 servers features Integrity Integrated Lights-Out 3 (iLO3) Management Processor and vMedia is part of the iLO3 feature set. OpenVMS supports the use of vMedia for optical devices and for ISO images on rx2800 i2 servers. vMedia can also be used to install OpenVMS from a remote DVD or for read-only postinstallation DVD related tasks such as application installation. o Support for vKVM Support for integrated remote console (vKVM) on BL8x0c i2 server blades and rx2800 i2 servers. o System management, including provisioning, providers, and WBEM infrastructure HP Systems Insight Manager (HP SIM) runs as a management server on ProLiant servers running Windows. OpenVMS can be managed from HP SIM on any of the supported management servers. OpenVMS provides software support in the following management areas so that OpenVMS is similar to server blades running on HP-UX: - Provisioning Version 4.1 Provisioning is the automatic configuration (or reconfiguration) of BladeSystems. Using HP SIM with the network services provided by the InfoServer utility and TCP/IP Services for OpenVMS (BOOTP), you can install or upgrade up to eight servers simultaneously. You can also use HP SIM with the vMedia feature provided with your Integrity server firmware, in which case you can install or upgrade OpenVMS on one server at a time. - WBEM Infrastructure This release supports Web Based Enterprise Management (WBEM Services V2.9-9), whose infrastructure is currently based on OpenPegasus Version 2.9. For more information on WBEM Services, see the WBEM Services Release Notes at http://h71000.www7.hp.com/doc/wbem.html. - WBEM Providers (Instance and Method) WBEM Services V2.9-9 and WBEM Providers V2.2 add support for the HP Integrity rx2800 i2 servers, in addition to the existing server models. The OpenVMS update kit VMS84I_UPDATE-V0500 or later must be installed and running before installing the WBEM Services and WBEM Providers kit. The WBEM Providers kit includes the operating system, computer system, processor, memory, fan, and power supply, as well as management processor and enclosure. To be managed by HP SIM, your Integrity server requires HP WBEM (Web-Based Enterprise Management) Services for OpenVMS and the HP WBEM Providers for OpenVMS. For more information, see section 7.9.5 in the HP OpenVMS Version 8.4 for Integrity Servers Upgrade and Installation Manual. o HP StorageWorks LTO-5 Ultrium Tape Drives. For more information, see the following website: http://h18006.www1.hp.com/storage/tapestorage/index.html?psn=storage o Performance improvement while handling "%RMS-E-EOF, end of file detected" errors The GET and FIND statements in HP BASIC RTL for OpenVMS use a signaled exception to indicate a condition other than a successful record retrieval. Because the current exception delivery code on OpenVMS Integrity servers is not fully optimized, this can slow down programs that generate a set of such events. The DBASIC$IO_NO_SIGNAL routine in the new version of DEC$BASRTL.EXE is enhanced to support the commonly experienced RMS$_EOF condition. This improves the performance of applications written in BASIC while porting to the Integrity platform. The DBASIC$IO_NO_SIGNAL routine takes two input parameters, the channel number (integer) and the vector (integer), containing the condition, for which signaling and exception are to be avoided. The DBASIC$IO_NO_SIGNAL routine call must be placed immediately before the GET or FIND statement, because the effect lasts only until the next I/O operation on the indicated channel. The GET or FIND statement must be immediately followed by a call to RMSSTATUS for the channel to test whether an exception occurred, and then conditionally transact with the RMS$_EOF condition instead of the exception handler routine. Images Affected: - [SYSLIB]DEC$BASRTL.EXE o Performance improvement of the OTS$STRCMP routines The LIBOTS Run-Time Library (RTL) has nine variants of the OTS$STRCMP routines. These routines are written in BLISS programming language. They perform a byte-to-byte comparison, which leads to poor performance. In this release of the update kit, the OTS$STRCMP routines are rewritten in Itanium assembly, thereby improving the performance significantly. Images affected: - [SYSLIB]LIBOTS.EXE - [SYSLIB]LIBOTS.OLB o Addition of the OpenVMS C RTL decc$get_channel() API function The OpenVMS C RTL decc$get_channel() API function is introduced to obtain the channel number for sockets and mailbox that are opened by the fopen() call. The decc$get_channel() API function verifies the following: i) The fab$l_dev of the fab structure has the flag DEV$M_MBX set and returns fab$l_stv, which includes the mailbox channel number. ii) The issocket of the FCB structure is set and returns the fcb->channel, which includes the socket channel number. The syntax for the decc$get_channel() API function is: unsigned short int decc$get_channel(__FILE *fp) Arguments: FILE * Returns : unsigned short int The decc$get_channel () API returns the channel number: 1) (fab$l_stv) for mailbox if the fab$l_dev has DEV$M_MBX set. 2) (fcb->channel) for socket if fcb->issocket is set. On failure, the decc$get_channel() API returns 0 with errno set to EINVAL. To use decc$get_channel() function, declare the following in your application: extern unsigned short int decc$get_channel(__FILE *fp); Images Affected: - [SYSLIB]DECC$SHR.EXE o ACME LDAP - multiple redundant directory servers support The Authentication Credentials Management Extensions (ACME) Lightweight Directory Access Protocol (LDAP) can now be configured to search multiple redundant directory servers for user authentication. ACME LDAP tries to connect to a set of directory servers, in a sequence, until it receives a successful connection. This is useful when the first directory server is not reachable or inactive. The LDAP user's login into the OpenVMS system is not blocked and users are authenticated against the next directory server that is active. The "bind_timeout" directive is a new directive included in this release. To provide multiple redundant servers, the "server", "bind_timeout", and "ca_file" (optional) directive must be updated in the LDAP configuration file. For more information, see Section "Editing LDAP Configuration file" in the SYS$HELP:ACMELDAP_STD_CONFIG_INSTALL.PDF. Images Affected: - [SYSLIB]SYS$STARLET_C.TLB - [SYSLIB]LDAP$SHR.EXE - [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE - [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF - [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT - [SYS$STARTUP]LDAPACME$CONFIG-STD.INI_TEMPLATE o New triple DES example added in ENCRYPT$EXAMPLES A new example file ENCRYPT$EXAMPLES:ENCRYPT_3DES.C is provided. The example file uses the Data Encryption Standard (DES) APIs to encrypt and decrypt data in 3DES by using 64-bits of data at a time. For more information, see the comments in the ENCRYPT$EXAMPLES:ENCRYPT_3DES.C file. Images Affected: - [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT_3DES.C - [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT$EXAMPLES.TXT o Improvements to cluster communication * PEdriver VC Flex10 support - With VC Flex10, the speed of the network interface card (NIC) interfaces can be changed dynamically in the server profiles. The PEdriver is enhanced to detect any changes in speed of the interfaces because the channel load class is calculated based on the speed of the interface. As a result, when you execute the $ MCR SCACP SHOW CHANNEL command, the PEdriver queries the LAN driver to identify any speed changes and updates the load class of the channel between the nodes. The channel load class has an internal effect on the RECEIVE CACHE SIZE and XMT window size. Note: To change the speed of VC Flex10 vNICs interfaces using the virtual connection manager, execute the $ MCR SCACP SHOW CHANNEL command on all the nodes where the port speed is updated to reflect in PEdriver. - The jumbo frame size of Flex10 vNICs is 15 bytes lesser than the normal 1 Gigabit Mezzanine cards. Based on the buffer size of the channel, PEdriver marks the channel as either inferior or superior. Because the buffer size of VC Flex10 vNICs is 15 bytes less than the traditional 1 Gigabit Mezzanine cards, they are marked as inferior and hence cannot be used for system communication services (SCS) traffic. The PEdriver now allows a variance of 16 bytes in the buffer size when jumbo frames are enabled. - The RECEIVE CACHE SIZE of the VC is set based on the VC LOAD CLASS in PEdriver. As a result, if the VC LOAD CLASS is greater than 2 Gigabits, the RECEIVE CACHE SIZE is set to 128. Note: HP recommends that all the interfaces used for cluster communication must have the same port speed. If you need to tune the port speed to less than 1 Gigabit for any Flex NICs, decrease the priority of the interface using the MC SCACP command. The interface with the greater speed is given preference than an interface with lesser speed. This improves the performance of cluster communication. For example, if there is a requirement to tune the Flex NICs of one interface to 9.9 Gigabits and another to 100 MB, and if both are used for cluster communication, decrease the priority of the 100 MB interface by executing the following command: $ MCR SCACP SET LAN_DEVICE/priority=-1 EIB Alternatively, you can also increase the priority of VC Flex10 vNICS by executing the following command: $ MCR SCACP SET LAN_DEVICE/priority=2 EWA * Cluster over IP (IPCI) improvements - Transmit window The default transmit window for an IP channel has been increased from 8 to 128. This results in better throughput using an IP channel. - Line speed for IP interface In the Cluster over IP environment, the MCR SCACP SHOW IP_INTERFACE command now displays the correct line speed value for the IP interface. - Load class for IP interface The MCR SCACP SHOW CHANNEL command now displays the proper load class for IP channels with 10 Gigabit interfaces. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER_MON.STB 5.2 Problems addressed in this kit 5.2.1 EFI network utilities result in an ASSERT on BL8x0c i2 server blades and rx2800 i2 servers 5.2.1.1 Problem Description: Usage of Extensible Firmware Interface (EFI) network utilities FTP.EFI, TCPIPV4.EFI, ROUTE.EFI, IFCONFIG.EFI and PING.EFI on BL8x0c i2 server blades and rx2800 i2 servers could result in ASSERT (firmware crash). This problem has been fixed. HP recommends that the following commands be used instead of the above utilities: ifconfig - Modifies the default IP address of UEFI network stack ftp - Performs an FTP operation ping - Pings the target machine with UEFI network stack Images Affected: - [SYSEXE]TCPIPV4.EFI - [SYSEXE]FTP.EFI - [SYSEXE]IFCONFIG.EFI - [SYSEXE]PING.EFI - [SYSEXE]ROUTE.EFI Quix cases reporting this problem: None. 5.2.1.2 Work-arounds: None. 5.2.2 On an rx2800 i2 series server, creating more than two LUNs from the P410i controller fails 5.2.2.1 Problem Description: Creating more than 2 units on a P410i RAID controller without a cache/battery using MSA$UTIL fails with an incomprehensible error message. Now the utility is modified to provide meaningful error message. In order to create more than 2 units on a P410i controller, a cache/battery is required. Images Affected: - [SYSEXE]MSA$UTIL.EXE Quix cases reporting this problem: None. 5.2.2.2 Work-arounds: None. 5.2.3 The MOVAQ instruction fails to handle negative numbers 5.2.3.1 Problem Description: The MOVAQ instruction cannot handle negative integers specified in decimal format. The MOVAQ instruction considers negative integers as large positive integers. For example, $ type movaq.mar neg = -8 xneg = ^xfffffff8 .psect data,rd,wrt z: .blkl 10 .psect code,rd,nowrt .entry start,0 MOVAQ xneg+z,r16 MOVAQ neg+z,r18 ret .end start The MOVAQ instruction treats '-8' as a large 64-bit constant value, though it handles ^xfffffff8 correctly. This problem has been fixed. Images Affected: - [SYSEXE]MACRO.EXE Quix cases reporting this problem: None. 5.2.3.2 Work-arounds: None. 5.2.4 MACRO compiler generates incorrect debugging information 5.2.4.1 Problem Description: MACRO compiler generates incorrect debugging information for certain variables. When you try to access these variables, the debugger displays an error message. This problem has been fixed. Images Affected: - [SYSEXE]MACRO.EXE Quix cases reporting this problem: None. 5.2.4.2 Work-arounds: None. 5.2.5 MACRO INDEX instruction incorrectly generates a trap 5.2.5.1 Problem Description: The MACRO INDEX instruction incorrectly generates a trap when the application code uses the same register as both input and output register. This problem has been fixed. Images Affected: - [SYSEXE]MACRO.EXE Quix cases reporting this problem: QXCM1000976996 5.2.5.2 Work-arounds: None. 5.2.6 Difference in behavior between C and C++ while casting 128-floating point data to 64-bit integer data 5.2.6.1 Problem Description: When a 128-bit floating point data is cast to a 64-bit integer data, the HP C Compiler for OpenVMS Integrity truncates the value to the largest signed 64-bit integer (7FFFFFFFFFFFFFFF) in case of an overflow. The HP C++ Compiler for OpenVMS Integrity and the HP C Compiler for OpenVMS Alpha truncates it to the largest unsigned 64-bit integer (FFFFFFFFFFFFFFFF). With this fix, the HP C Compiler for OpenVMS Integrity works similar to the HP C++ Compiler for OpenVMS Integrity. This problem has been fixed. Images Affected: - [SYSLIB]LIBOTS.EXE Quix cases reporting this problem: QXCM1000995804 5.2.6.2 Work-arounds: None. 5.2.7 DEBUG EXAMINE displays incorrect results for PASCAL Boolean variables 5.2.7.1 Problem Description: The Debugger fails to handle Boolean variables correctly, such as, addressing and displaying the correct value. This happens for certain PASCAL test programs, as shown in the following examples: Example 1: ---------- $ TYPE DEBUG1.PAS Program Debug_test1 (Input, Output); TYPE yBYTE_BOOL = [BYTE] BOOLEAN; Const cMax_Orders = 2; Type yOrder = RECORD InUse : yBYTE_BOOL; END; yOrder_ARRAY = ARRAY [1..cMAX_Orders] OF yOrder; Var mOrder : yOrder_ARRAY := Zero; xI : Integer := 0; Begin For xI := 1 To cMax_Orders Do With mOrder[xI] Do Begin InUse := true; End; Writeln ('Value mOrder[1].InUse',mOrder[1].InUse); Writeln ('Value mOrder[2].InUse',mOrder[1].InUse); End. In example 1, the value of 'InUse' is set to TRUE but the debugger displays it as FALSE while examining the value. Example 2: ---------- $ TYPE DEBUG2.PAS program x(output); var r : packed record f1 : boolean; f2 : integer; end; begin r.f1 := true; r.f2 := 12; writeln(r.f1,r.f2); end. In example 2, while examining the value of "r", the debugger displays incorrect values. This problem has been fixed. Images Affected: - [SYSLIB]DEBUGSHR.EXE Quix cases reporting this problem: QXCM1000945306 5.2.7.2 Work-arounds: None. 5.2.8 Maximum limit for the IMGREG_PAGES SYSGEN parameter is modified 5.2.8.1 Problem Description: Currently, the maximum permissible value for the IMGREG_PAGES SYSGEN parameter is set to 131072 pages. Setting the IMGREG_PAGES SYSGEN parameter to 131072 pages occupies all of the P1 space and denies memory required for other structures. This renders the system unbootable. This problem has been fixed. The maximum limit for the IMGREG_PAGES SYSGEN parameter is now modified to 80000 pages. Images Affected: - [SYS$LDR]SYS$BASE_IMAGE.EXE - [SYSLIB]SDA$SHARE.EXE - [SYSEXE]SYSGEN.EXE - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSMAN.EXE - [SYSEXE]SMISERVER.EXE Quix cases reporting this problem: QXCM1000943395 5.2.8.2 Work-arounds: None. 5.2.9 Occasional system crashes during USB operations 5.2.9.1 Problem Description: In the event of the exhaustion of bus addressable pool (BAP) on a system, I/O operations associated with USB devices might result in a system crash. This problem has been fixed. The behavior of the USB drivers is now modified as follows: - fails an I/O if system_check is OFF - crashes the system if system_check is ON Images Affected: - [SYS$LDR]SYS$EHCIDRIVER.EXE - [SYS$LDR]SYS$OHCIDRIVER.EXE - [SYS$LDR]SYS$UHCIDRIVER.EXE - [SYSLIB]USB$SDA.EXE Quix cases reporting this problem: None. 5.2.9.2 Work-arounds: None. 5.2.10 OpenVMS crashes during boot due to a mouse event 5.2.13.1 Problem Description: An event generated by the mouse such as scrolling the mouse wheel while a USB mouse is being plugged-in or while DECwindows is starting up, might cause a system crash. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$IKUDRIVER.EXE - [SYS$LDR]SYS$IMUDRIVER.EXE - [SYS$LDR]SYS$IKXDRIVER.EXE Quix cases reporting this problem: QXCM1000898776 5.2.13.2 Work-arounds: None. 5.2.11 AUTOGEN changes to handle a target disk of size in the range of 1 TiB to 2 TiB 5.2.11.1 Problem Description: DCL supports 32-bit operations. However, the 32nd bit is a sign extension bit. On a disk with size greater than 1 TiB, the number of free blocks on the disk is represented as a negative value by DCL. This results in many of the checks in AUTOGEN to fail and print invalid error messages with respect to available free space on the disk even when there is sufficient free space available on the disk. AUTOGEN has been modified to handle this situation as a part of the update to support 2 TiB volumes. Images Affected: - [SYSUPD]AUTOGEN.COM Quix cases reporting this problem: None. 5.2.11.2 Work-arounds: None. 5.2.12 Unable to access a directory with Unicode characters in the directory name 5.2.12.1 Problem Description: An attempt to access a directory with Unicode characters in the directory name, fails with the following error message: $ dir [.^U3042] %DIRECT-E-OPENIN, error opening SYS$SPECIFIC:[SYSMGR.TMP.KANJIDIR.^U3042]*.*;* as input RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE Quix cases reporting this problem: None. 5.2.12.2 Work-arounds: None. 5.2.13 SEARCH/NOWARN is unable to suppress unresolved symbolic link errors 5.2.13.1 Problem Description: When the DCL command SEARCH with /NOWARN qualifier is issued on a symbolic link pointing to a non-existing file, the SEARCH/NOWARN command is unable to suppress the "RMS-E-FNF, file not found" error message. For example, $DIR/LINK LINK.DAT Directory SYS$SYSDEVICE:[DOC] LINK.DAT;1 -> file.txt 0 Total of 1 file. $ SEARCH/NOWARN LINK.DAT "HELLO WORLD" %SEARCH-W-OPENIN, error opening SYS$SYSDEVICE:[DOC]LINK.DAT;1 as input -RMS-E-FNF, file not found This problem has been fixed. Images Affected: - [SYSEXE]SEARCH.EXE Quix cases reporting this problem: None. 5.2.13.2 Work-arounds: None. 5.2.14 FLT SHOW TRACE/SUMMARY report is misleading for process space PC value(s) 5.2.14.1 Problem Description: The FLT SHOW TRACE/SUMMARY report is misleading for process space PC value(s) because the symbolization of the PC value(s) reflects the current System Dump Analyzer (SDA) process context. Two new qualifiers, /INDEX and /IDENT, are now added to summarize the fault trace information for a particular process: FLT SHOW TRACE/SUMMARY/INDEX= FLT SHOW TRACE/SUMMARY/IDENT= With these new features, FLT SHOW TRACE/SUMMARY can summarize the FLT trace information specific to a process based on PID or index. This problem has been fixed. Images Affected: - [SYS$LDR]FLT$DEBUG.EXE - [SYSLIB]FLT$SDA.EXE Quix cases reporting this problem: QXCM1000858646, QXCM1000952887 5.2.14.2 Work-arounds: None. 5.2.15 Image Activation fails with insufficient privilege or object protection violation 5.2.15.1 Problem Description: When multiple jobs are running in parallel, image activation fails with insufficient privilege or object protection violation for the installed image as follows: %DCL-W-ACTIMAGE,error activating image XXX -CLI-E-IMGNAME, image file DEV:[XXX.][SYSLIB]XXX.EXE -SYSTEM-F-NOPRIV, insufficient privilege or object protection violation This problem has been fixed. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB Quix cases reporting this problem: QXCM1001050875 5.2.15.2 Work-arounds: None. 5.2.16 The SMISERVER process crashes when it invokes a request on a remote node 5.2.16.1 Problem Description: In a cluster environment, account errors such as "%LOGIN-F-DISUSER, account is disabled" are displayed and the SMISERVER aborts with a process dump. This occurs when there are different User Authorization Files (UAFs) in a cluster and if the currently used account is set to DISUSER. $ MCR SYSMAN SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SAHOO will be used on nonlocal nodes SYSMAN> DO SHOW TIME %SYSMAN-I-OUTPUT, command execution on node NODE1 17-SEP-2010 19:29:32.19 %SYSMAN-I-OUTPUT, command execution on node NODE2 %SYSMAN-I-NODERR, error returned from node NODE2 -SMI-E-ABORT, SMI Server has aborted This problem has been fixed. Images Affected: - [SYSEXE]SMISERVER.EXE Quix cases reporting this problem: QXCM1000999438 5.2.16.2 Work-arounds: None. 5.2.17 Problem opening an RMS indexed file with a large number of global buffers 5.2.17.1 Problem Description: When a large number of global buffers are specified on a Record Management Services (RMS) indexed file, the RMS system service SYS$CONNECT fails with the error codes -RMS-F-CRMP and RMS-F-DME as primary and secondary status respectively. For example, $ SET FILE/GLOBAL_BUFFER=COUNT=1270400 TEST$DISK:[FOO]SYSUAF.DAT $ TYPE TEST$DISK:[FOO]SYSUAF.DAT %TYPE-W-OPENIN, error opening TEST$DISK:[FOO]SYSUAF.DAT;1 as input -RMS-F-CRMP, CRMPSC system service failed to map global buffers -RMS-F-DME, dynamic memory exhausted A high-level language file open request, such as OPEN in FORTRAN, also exhibits this problem, as the operation internally includes a call to SYS$CONNECT, on a file with the same RMS global buffer attributes. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE Quix cases reporting this problem: QXCM1001062201 5.2.17.2 Work-arounds: None. 5.2.18 Use of DCL commands or RTL routines that SPAWN sub-processes might experience an infinite loop or process hang 5.2.18.1 Problem Description: A parent process can spawn sub-processes with either the WAIT or NOWAIT option. If the sub-process is spawned with the WAIT option, the parent process waits for the completion of the sub-process. Sometimes a sub-process can terminate normally or abnormally even before the parent process gets into the WAIT state. This condition leads to the parent process waiting for the sub-process indefinitely. This might be seen when using DCL commands such as SPAWN and PIPE, or programs that use the LIB$SPAWN RTL routine. For more information, see the customer advisory at: http://h41302.www4.hp.com/km/saw/view.do?docId=emr_na-c02584511 This problem has been fixed. Images Affected: - [SYSEXE]DCL.EXE Quix cases reporting this problem: QXCM1001056367, QXCM1001078968 5.2.18.2 Work-arounds: None. 5.2.19 The COPY command might display an incorrect progress report 5.2.19.1 Problem Description: Pressing CTRL/T when using the COPY command to append a large number of input files to an output file, displays an incorrect progress report (0% completed). For example, $ COPY TEST.LOG;* TEST.NEW DRWHO::SYSTEM 14:54:47 COPY CPU=00:04:29.78 PF=1431975 IO=806207 MEM=170 Copying: DSA15:[CARRD]TEST.LOG;18033 (0% completed) 0 blocks copied of 4294447434 This problem has been fixed. Images Affected: - [SYSEXE]COPY.EXE Quix cases reporting this problem: QXCM1000975987 5.2.19.2 Work-arounds: None. 5.2.20 Alignment fault in RMS 5.2.20.1 Problem Description: With OpenVMS V8.4, various alignment faults are seen when the SYS$CONNECT operation is being performed on a file with global buffers enabled or when SYS$PARSE is attempted on a file that includes a wildcard specification. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE Quix cases reporting this problem: QXCM1001078833 5.2.20.2 Work-arounds: None. 5.2.21 After executing STOP/QUEUE/RESET, the queue manager crashes 5.2.21.1 Problem Description: Attempting to delete a non-existing job entry after executing STOP/QUEUE/RESET causes the queue manager to crash with the following messages that are reported to the operator console and log: %%%%%%%%%%% OPCOM 22-OCT-2010 13:51:32.06 %%%%%%%%%%% Message from user SYSTEM on CLT94C %QMAN-F-BADLOGIC, internal logic error detected at PC 00111070 %%%%%%%%%%% OPCOM 22-OCT-2010 13:51:32.74 %%%%%%%%%%% Message from user SYSTEM on CLT94C %JBC-E-QMANDEL, unexpected queue manager process termination This problem has been fixed. Images Affected: - [SYSEXE]QMAN$QUEUE_MANAGER.EXE Quix cases reporting this problem: QXCM1001079988 5.2.21.2 Work-arounds: None. 5.2.22 The "Default" value for the SYSTEM_CHECK system parameter is set to 1 after installing the VMS84I_UPDATE-V0400 kit 5.2.22.1 Problem Description: After installing the VMS84I_UPDATE-V0400 kit on OpenVMS Integrity servers Version 8.4, the "Default" value of the SYSTEM_CHECK system parameter is set to 1. However, certain operations (such as running AUTOGEN) cause the SYSTEM_CHECK "Default" value to be moved to the "Current" value. If this occurs, the system will run using a value of 1. For most installations, this is not the desired value and can cause performance slowdowns. This problem has been fixed. Images Affected: - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSGEN.EXE Quix cases reporting this problem: QXCM1001082915 5.2.22.2 Work-arounds: None. 5.2.23 AUTOGEN prints an UNDSYM warning message 5.2.23.1 Problem Description While running AUTOGEN, the following warning message might be displayed: "%DCL-W-UNDSYM, undefined symbol - check validity and spelling" This problem has been fixed. Images Affected: - [SYSUPD]AUTOGEN.COM Quix cases reporting this problem: QXCM1001084583 5.2.23.2 Work-arounds: None. 5.2.24 SHADOWSET in endless mount verification 5.2.24.1 Problem Description: Certain unhandled errors on IO operations on SHADOWSET members during mount verification could result in the SHADOWSET not getting successfully mounted but remaining in mount verification state. This problem has been fixed. The SHADOWSET member on which these errors are reported would be removed from SHADOWSET and the mount verification would successfully complete. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE - [SYS$LDR]SYS$SHDRIVER.STB Quix cases reporting this problem: None. 5.2.24.2 Work-arounds: None. 5.2.25 System crash with SHADDETINCON, SHADOWING detects inconsistent state 5.2.25.1 Problem Description: 1) A cluster node member may occasionally crash with the SHADDETINCON error condition, when multiple mount or dismount commands are applied simultaneously on the same SHADOWSET, from other cluster members while another cluster member is leaving the cluster. 2) During the calibration cycle, initiated during the copy/merge of a SHADOWSET, a cluster node could crash in rare circumstances with a deadlock detected error. The calibration process now avoids the deadlock. These problems have been fixed. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE - [SYS$LDR]SYS$SHDRIVER.STB - [SYSEXE]SHADOW_SERVER.EXE - [SYSEXE]SHADOW_SERVER.STB Quix cases reporting this problem: None. 5.2.25.2 Work-arounds: None. 5.2.26 Fix for security vulnerability 5.2.26.1 Problem Description: Potential security vulnerability with HP OpenVMS resulted in local non-privileged users to gain access to privileged resources and/or system crash. This problem has been fixed. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB Quix cases reporting this problem: None. 5.2.26.2 Work-arounds: None. 5.2.27 AUTOGEN changes to handle physical memory of size in the range of 1 TiB to 2 TiB 5.2.27.1 Problem Description: BL890c i2 server blades support physical memory greater than 1 TiB (for example, 96 slots each with 16 GB = 1536 GB of physical memory). On such a system, the memory size in terms of pagelets overflows the DCL limit of 2^31. AUTOGEN has been modified to handle the physical memory greater than 1 TiB. A new file named AUTOGEN_LM.COM has been provided to handle this configuration. A run of AUTOGEN automatically decides if it needs to use the AUTOGEN_LM.COM on the system. This is transparent to users of AUTOGEN. Images Affected: - [SYSUPD]AUTOGEN.COM - [SYSUPD]AUTOGEN_LM.COM Quix cases reporting this problem: None. 5.2.27.2 Work-arounds: None. 5.2.28 Memory leak in the LDAP API library 5.2.28.1 Problem Description: While testing the ACME LDAP external authentication under stressed condition, memory leaks were identified to be originating from LDAP$SHR.EXE. This problem has been fixed. Images Affected: - [SYSLIB]LDAP$SHR.EXE Quix cases reporting this problem: None. 5.2.28.2 Work-arounds: None. 5.2.29 Performance issues during login of users using ACME LDAP 5.2.29.1 Problem Description: When a large number of users try to login at the same time, the users who try to login after a few minutes see a blank screen and timeout messages. If an LDAP connection to the directory server is slow, the users will get blank screen and timeout messages. These problems have been fixed. Images Affected: - [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE Quix cases reporting this problem: QXCM1001020715, QXCM1000904720 5.2.29.2 Work-arounds: None. 5.2.30 Autostarting ACME_SERVER does not load the LDAP ACME Agent 5.2.30.1 Problem Description: Even after defining the LDAPACME$INIT logical in the ACME$START.COM with a "/SYSTEM/EXECUTIVE" qualifier, on autostart of the ACME_SERVER process, the logical is defined with only a /SUPERVISOR_MODE access. The LDAP ACME agent will not load if the LDAPACME$INIT logical is not defined with a /SYSTEM/EXECUTIVE. This problem has been fixed. Images Affected: - [SYSEXE]ACME_SERVER.EXE Quix cases reporting this problem: None. 5.2.30.2 Work-arounds: None. 5.2.31 Unable to capture enough diagnostic using the existing SYS$EXAMPLES:LDAP_EXAMPLE.C 5.2.31.1 Problem Description: The SYS$EXAMPLES:LDAP_EXAMPLE.C file currently do not support passing bind_dn, bind_password, port_security and ca_file parameters, thus limiting the amount of diagnostic that can be captured. The new LDAP_EXAMPLE.C is modified to accept new parameters specific to bind_dn, bind_password, port_security and ca_file. For more information, see the comments in the SYS$EXAMPLES:LDAP_EXAMPLE.C file. This problem has been fixed. Images Affected: - [SYSHLP.EXAMPLES]LDAP_EXAMPLE.C Quix cases reporting this problem: QXCM1001019671 5.2.31.2 Work-arounds: None. 5.2.32 ACME LDAP local user mapping fails 5.2.32.1 Problem Description: The LDAP local mapping does not work on some systems and user login fails due to search logic failures. This problem has been fixed. Images Affected: - [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE Quix cases reporting this problem: None. 5.2.32.2 Work-arounds: None. 5.2.33 BL8x0c i2 server blades hang if the vMedia device is connected and the network link is lost 5.2.33.1 Problem Description: When a vMedia device is connected and if the network link is lost, BL8x0c i2 server blades hang. This problem has been fixed as part of the BL8x0c i2 server blades firmware bundle version 21.08. Images Affected: None. Quix cases reporting this problem: None. 5.2.33.2 Work-arounds: None. 5.2.34 Infoserver boot/installation process hangs if the specified service is unavailable or inaccessible 5.2.34.1 Problem Description: If the specified service is unavailable or inaccessible, the Infoserver boot/installation process hangs without displaying any error message. This has been fixed and now the Infoserver boot/installation process displays the following error message on the console: - If the service is unavailable, it displays the following message: "Unable to proceed further. Specified service is not available." - If the service is available, but connection to the service encountered a failure, it displays the following message: "Connection to the specified service is failed. Unable to continue." This problem has been fixed. Images Affected: - [SYS$LDR]SYS$DADDRIVER.EXE Quix cases reporting this problem: None. 5.2.34.2 Work-arounds: None. 5.2.35 MONITOR SET DEFAULT/NODE command can lead to an ACCVIO 5.2.35.1 Problem Description: When the MONITOR SET DEFAULT command is used with the /NODE qualifier to specify the default node and further monitoring is initiated, it ACCVIOs with the following footprint: $ MONITOR MONITOR> SET DEF/NODE=XYZ MONITOR> MONITOR PROC %NONAME-W-NOMSG, Message number 00000000 %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000049414D, PC=FFFFFFFF84B8E070, PS=0000001B This problem has been fixed. Images Affected: - [SYSEXE]MONITOR.EXE Quix cases reporting this problem: QXCM1000750590 5.2.35.2 Work-arounds: None. 5.2.36 Exception loop in threads library 5.2.36.1 Problem Description: When an unhandled exception causes a threaded application to run down, if the exit handler encounters a wait, the threads library could cause the application to hang. Images Affected: - [SYSLIB]PTHREAD$RTL.EXE - [SYSLIB]PTHREAD$DBGSHR.EXE Quix cases reporting this problem: QXCM1001078843 5.2.36.2 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_UPDATE patch kits can be found in the following files: o VMS84I_UPDATE-V0100.RELEASE_NOTES o VMS84I_UPDATE-V0200.RELEASE_NOTES o VMS84I_UPDATE-V0300.RELEASE_NOTES o VMS84I_UPDATE-V0400.RELEASE_NOTES o VMS84I_MUP-V0100.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS84I_UPDATE /VERSION=V5.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_UPDATE /VERSION=V5.0 - /SELECT=release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST VMS84I_UPDATE /VERSION=V5.0 /SELECT = *.RELEASE_NOTES 7 KNOWN PROBLEMS AND LIMITATIONS 7.1 Known problems and limitations in this patch kit This section describes the known problems and limitations in this patch kit. 0 On rx2800 i2 servers, BOOT_OPTIONS.COM cannot be used to add boot options to any device on the PCIe Emulex 2-port 4 GB Fibre Channel/2-port Ethernet HBA combo cards. Boot options for devices on this card must be configured from EFI using the EFI boot manager. 0 Inability to boot using the "Internal Bootable DVD" EFI boot option on rx2800 i2 servers On rx2800 i2 servers, an attempt to boot the system using the internal DVD boot option from the boot manager, fails to boot with the following error message: Booting Internal Bootable DVD Boot Failed Press any key to continue... Boot using the internal DVD drive can be done by creating a boot option entry manually using one of the following: Boot Maintenance Manager BCFG utility VMS_BCFG EFI utility BOOT_OPTIONS.COM This issue will be addressed in a future release. 0 On rx2800 i2 servers, the serial console runs in 'POLLED' mode The serial console on rx2800 i2 servers running OpenVMS works in the 'POLLED' mode and not the 'INTERRUPT' mode, resulting in: - Slow rate of output being displayed on the console. - Copying huge data on the console might result in the following error message: %RMS-F-RER, file read error -SYSTEM-W-DATAOVERUN, data overrun 0 Booting OpenVMS from an SAS disk with a vMedia device connected may result in a crash While booting OpenVMS Integrity servers Version 8.4 from an SAS disk on BL8x0c i2 server blades or rx2800 i2 servers, the system might crash if a vMedia device is connected. HP recommends you to disconnect the vMedia device while booting OpenVMS from an SAS disk. 0 Uncore fatal errors cause a system reset without generating OpenVMS dumps On BL8x0c i2 server blades and rx2800 i2 servers, an uncore fatal error must result in a Machine Check Abort (MCA). Eventually, a system reset occurs after a valid dump is generated. It is observed that on BL8x0c i2 server blades and rx2800 i2 servers, uncore fatal errors reset the system without generating the OpenVMS dump. If such a reset occurs, firmware logs can be collected using the efi command, ERRDUMP MCA. 0 On a BL870c i2 server blades in the "MostlyUMA" configuration might hang during boot if reserved memory is configured on the system The workaround for this issue is to reserve the memory size in multiples of 1024 MB (1 GB). For example, a 90 GB reserved memory can be reserved as 92160 MB from SYSMAN. However, this workaround might not work in all the situations. In such cases, contact your HP support representative for a point fix image. 0 Possible system hang while running AUTOGEN on a 8S BL890c i2 server with physical memory greater than 1 TiB AUTOGEN computes incorrect values of system parameters and file sizes on a BL890c i2 server with more than 1 TiB physical memory if the installation is performed from OpenVMS V8.4 source media that does not contain VMS84I_UPDATE-V0500 images. As a result, you might observe warning such as, Computed size: -715914400; current size: 0 %SYSGEN-I-CREATED, DKA0:[SYS0.SYSEXE]SYSDUMP.DMP;1 created %SYSTEM-W-DEVICEFULL, device full; allocation failure If this warning is ignored and VMS84I_UPDATE-V0500 is installed from the DCL prompt ($), on execution of AUTOGEN on such a system might result in a system hang. To overcome this problem, HP recommends you to follow these steps: 1) Perform the installation of VMS84I_UPDATE-V0500 before the first boot. The steps are described in section 1.4.7 in the HP OpenVMS Version 8.4 Upgrade and Installation Manual. 2) Limit the physical memory available to OpenVMS during the first boot to less than 1 TiB. This can be achieved by performing a conversational boot (VMS_FLAGS n,1 - where 'n' is the root number of the node you are booting) and setting the PHYSICAL_MEMORY parameter to less than 1048576 MB. For example, At the SYSBOOT> prompt, enter the following command: SYSBOOT> SET PHYSICAL_MEMORY 1024000 SYSBOOT> CONTINUE After the system boots and VMS84I_UPDATE-V0500 is installed, reset the PHYSICAL_MEMORY SYSGEN parameter to the default value of -1 to have the complete memory available to OpenVMS. 3) If the system boots without performing step 1 and 2, take a backup of the existing SYSDUMP.DMP and delete the original SYSDUMP.DMP. After taking the backup, run AUTOGEN from VMS84I_UPDATE-V0500. IMPORTANT NOTE: Do not perform these steps if you are installing directly from the OpenVMS V8.4 media that includes the VMS84I_UPDATE-V0500 images. 0 Number of LAN devices of the same type will be limited to 26 LAN devices are named as xyn where, x is the LAN type, and can be E, F, V, or L. E for Ethernet, F for FDDI, V for VLAN, L for Logical LAN. y is usually the bus type, where, y can be W, R, X, or I. W for PCI, PCI-X, and PCIe, R for EISA, and ISA, X for XMI. R has been reused for PCIe mezzanine devices. W for PCI convention is not followed for Gigabit devices exactly. I stands for Intel Gigabit and W stands for Broadcom Gigabit and 10 Gigabit and Neterion 10 Gigabit devices. n is the device letter A-Z. For example, EIA device where, E - Ethernet, I - Intel Gigabit, A - device letter. Device names are assigned as they are discovered. When 26 LAN devices of a certain type are discovered, for example, EWA through EWZ, you cannot configure any more EW series devices. When systems are configured with many devices, it might reach the limit of 26. This is especially true with Flex10-enabled devices in Blade configurations that are configured as 8 EW devices for each Broadcom 57711E LOM device and 8 ER devices for each Broadcom 57711E mezzanine card. Note: - When designing system configurations, plan your network configuration. - VLAN and Logical LAN devices are named differently, as VLn and LLn devices. These devices are configured through LANCP and are limited to 26 for each type. 0 LAN failover feature is not supported when Flex-NICs are part a failover group Hardware Configuration: Server: BL8x0c i2 LAN devices: BL8x0c i2 LOM (LAN On Motherboard) ports or Mezzanine card (467799-B21) ports VC module: VC Flex-10 module (455880-B21) 0 EFI VMS_SHOW Utility will not display SAS devices connected via LSI Logic 1068 SAS Core I/O Controller On Integrity servers VMS_SHOW EFI utility will not show SAS devices connected through LSI Logic 1068 SAS Controller as a Core I/O. Workaround: The customers may use BOOT_OPTIONS.COM to view and set the boot and dump device. This issue will be addressed in a future release. 0 Installing OpenVMS from InfoServer with duplicate services may fail with a crash Installing OpenVMS from InfoServer crashes intermittently with the "PROCGONE" bugcheck, if the requested service is hosted by multiple servers in the same LAN. Workaround: Delete or rename the duplicate service name from one of the servers. 0 The P410i controller supports the following RAID levels: 0, 0 + 1 (1 in general), 5, 6 or ADG, 10, 50 and 60 Using MSA$UTIL the following RAID levels can be created on the P410i controller: 0, 1, 5, ADG, 50, and 60 Note: - Creating RAID 5 requires cache. - Creating ADG RAID 50 and RAID 60 requires Battery Backed-up Write Cache (BBWC). 0 Firmware updates of P410i, P411, and P812 controllers using MSA$UTIL is currently not supported. 0 The account records for batch jobs, terminated through $ STOP/QUEUE/RESET command on a batch queue, show identical values for start and finish times and show zero values for Elapsed and Processor times. The accounting records also show zero values in the PID and Resource fields such as Page Faults, Direct IO, and so on. These accounting records are followed by complete and correct records for the same jobs. However, these records do not show the batch queue or entry number for those jobs. A footprint of the possible accounting record is as follows: Username: ALEX UIC: [ALEX] Account: APC Finish time: 28-OCT-2010 17:55:54.99 Process ID: 00000000 Start time: 28-OCT-2010 17:55:54.99 . . . . . . . . . . Posix UID: Posix GID: Queue entry: 12 Final status code: 000480EC Queue name: FDAY Job name: LOOP Final status text: %JBC-F-QUERESET, job aborted during execution because queue was reset . . . . . . . . . . BATCH Process Termination ------------------------- Username: ALEX UIC: [ALEX] Account: APC Finish time: 28-OCT-2010 17:56:00.03 Process ID: 2021CD29 Start time: 28-OCT-2010 17:55:42.14 . . . . . . . . . Posix UID: -2 Posix GID: -2 (%XFFFFFFFE) Queue entry: Final status code: 000480EC Queue name: Job name: Final status text: %JBC-F-QUERESET, job aborted during execution because queue was reset 0 Dedicated CPU Lock Manager cannot be scheduled on CPUs with CPUID greater than 31 If the dedicated CPU Lock Manager is enabled on a system, the LCKMGR_CPUID SYSGEN parameter value must be less than 32. 0 Calls to LIB$FIND_IMAGE_SYMBOL sometimes fail with an ACCVIO while replacing shareable images installed with shared address data This problem can be found in applications where the shareable images are activated using LIB$FIND_IMAGE_SYMBOL while the shareable images are being replaced with modified images or identical images using the following commands: a. INSTALL/REMOVE - deletes the KFE b. INSTALL/ADD - allocates a KFE, which can be the same KFE 0 SHOW DEVICE command displays asterisks for the FREEBLOCKS field The SHOW DEVICE command displays asterisks for the FREEBLOCKS field when the freeblocks count is a number greater than 9 digits (approximately greater than 476 GB). The field that displays the freeblocks count is limited to 9 characters long so that the output of the SHOW DEVICE command does not wrap around the last character to the next line if the terminal display width is set to 80. In such cases, the freeblocks count can be obtained in blocks using the SHOW DEVICE/FULL command or in bytes using 'SHOW DEVICE/UNIT=BYTES'. Alternatively, you can use the lexicals as shown in the examples. Example-1: $ FREEBLOCKS = F$GETDVI("$1$DKB200:","FREEBLOCKS") $ STR_FREEBLOCKS = F$FAO("!ZL",FREEBLOCKS) $ SHOW SYMBOL FREEBLOCKS FREEBLOCKS = -1187997808 Hex = B9309790 Octal = 27114113620 $ SHOW SYMBOL STR_FREEBLOCKS STR_FREEBLOCKS = "3106969488" Example-2: $ STR_FREEBLOCKS = F$CUNITS(F$GETDVI("$1$DKB200:","FREEBLOCKS")) $ SHOW SYMBOL STR_FREEBLOCKS STR_FREEBLOCKS = "1.44TB" 0 Issues with RMS Multi Block Count (MBC) value greater than 127 Some issues have been observed with some MBC values greater than 127, a feature that was introduced in VMS84I_UPDATE-V0400. In such cases, contact your HP support representative for the V8.4 patch kit. 0 An OpenVMS disk larger than 1 TB, when connected with a QLogic Dual Port 8 Gb Fibre Channel HBA (firmware version 2.15 and 2.20), does not show up as an EFI boot partition. As a result, it is not possible to boot from this disk in such cases. OpenVMS engineering is investigating this problem. For an update, contact your HP support representative. 0 BOOT_OPTIONS.COM fails while adding boot option with specific 'VMS_FLAGS' The default value of "position number" does not work while adding a boot option using BOOT_OPTIONS.COM when 'VMS_FLAGS' are explicitly specified overriding the default for 'VMS_FLAGS'. Workaround: Provide an input value for the "Position number" option instead of selecting the default value. For example, Enter the desired position number (1,2,3,,,) of the entry. To display the Boot Options list, type "?" and press Enter. Position [1]:1 0 UETP load phase fails for high memory systems On systems with greater than 1TiB memory, running the UETP test can fail in the load phase as follows: %DCL-W-NUMBER, invalid numeric value - supply an integer \****\ %APPEND-E-OPENIN, error opening SYS$COMMON:[SYSTEST]UETLOAD00.LOG; as input -RMS-E-FNF, file not found %DELETE-W-SEARCHFAIL, error searching for SYS$COMMON:[SYSTEST]UETLO*.LOG;* -RMS-E-FNF, file not found In such a case the number of processes in the load phase must be restricted to no more than 1000 or the value of the MAXPROCESSCNT SYSGEN parameter, whichever is lower). Enter this value as a response to the question "How many simulated user loads do you want [4294966140]?" during UETP test configuration. For example, How many simulated user loads do you want [4294966140]? 1000 7.2 Known problems with OpenVMS running as a Guest Operating System on Integrity VM This section describes the known problems in the OpenVMS guest on HP Integrity Virtual Machines (Integrity VM). For more information, see the Integrity VM Release 4.2.5 release notes. 0 Considerations for license sharing in clusters with OpenVMS guests and native systems In a cluster that includes both native systems and OpenVMS guests, a single license cannot be used to share license units between a guest and a native system. The guest system requires a separate license with the appropriate number of units. For example, a license with 6 units cannot be used to share units between a native system which requires 4 units and a guest which requires 2 units. This is because Per Core License (PCL) licenses are modified using the /VIRTUAL qualifier for guests in a cluster. A license modified this way cannot be loaded on native systems. For more information about licensing OpenVMS guests, see the "HP OpenVMS License Management Utility Manual". 0 System Dump Analyzer (SDA) displays the following errors: SDA> CLUE CONFIG System Configuration: --------------------- System Information: System Type _HP_ VMM (1.67GHz/9.0MB) Primary CPU ID 0. Cycle Time 0.60 nsec (1666 MHz) Pagesize 8192 Byte %CLUE-W-NOSYMBIOS, cannot access SYMBIOS table ... Rest of data is displayed ... SDA> EXAMINE/PHYSICAL 0FE000;20 ! FEOOO is SMBIOS table physical address on guest Physical locations 00000000.000FE000 through 00000000.000FE01F are not accessible Workaround: Use the F$GETSYI("SYSTEM_UUID") lexical or the $GETSYI system service to get the system Universal Unique Identifier (UUID). 0 Starting TCP/IP on a guest with no associated Virtual Network Interface Cards (vNICs) leads to a crash. After disassociating a vNIC from a guest, an attempt to start TCP/IP on the guest after DECnet is started leads to a system crash. HP recommends that you use the OpenVMS guest with at least one vNIC configured. 0 OpenVMS guest crashes occasionally a) OpenVMS guest crashes occasionally with one of the following error messages: - CPUSPINWAIT, CPU spinwait timer expired - CPUSANITY, CPU sanity timer expired This issue is under investigation and will be fixed in a future release of Integrity VM. b) OpenVMS guest crashes occasionally during a reboot with any one of the following message: "?SYSLDR-F-NOTFOUNTD, needed image not found SYS$PUBLIC_VECTORS -> SYS$BASE_IMAGE" or %SYSBOOT-F-LDFAIL, unable to load SYS$PUBLIC_VECTORS.EXE, status = 00000044 The hpvm_mon_log, available at /var/opt/hpvm/common, indicates memory related errors during the time of crash as shown below: # WARNING: Host memory is fragmented. # Reducing VHPT preferred page size from #K to #K. # This may result in degraded performance for this virtual machine. Workaround: 1) Set the tunable ptsz by entering the following command: hpvmmodify -P -q ptsz=13 2) Restart the Integrity VM guest for the changes to take effect. 8 DOCUMENTATION ERRATA This section describes corrections and additions to the online help and various manuals in the OpenVMS documentation set. 0 In the HP OpenVMS System Management Utilities Reference Manual: M-Z and online help, the RAD_SUPPORT system parameter must be read as: RAD_SUPPORT enables RAD-aware code to be executed on systems that support Resource Affinity Domains (RADs). For example, AlphaServer GS160 systems and Integrity cell-based servers, BL8x0c i2 server blades, or rx2800 i2 servers. An RAD is a set of hardware components (CPUs, memory, and I/O) with common access characteristics. Bits are defined in the RAD_SUPPORT parameter as follows: RAD_SUPPORT (default is 207 for Alpha and 109446674473 for Integrity servers) 9 FILES PATCHED OR REPLACED: o [SYSEXE]ACC.EXE (new image) Image Identification Information Image name: "ACC" image file identification: "X-25" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:11.00 Overall Image Checksum: 9182007A o [SYSEXE]AGEN$FEEDBACK.EXE (new image) Image Identification Information Image name: "AGEN$FEEDBACK" image file identification: "X-32" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:46.56 Overall Image Checksum: 3371A610 o [SYSEXE]AUDIT_SERVER.EXE (new image) Image Identification Information Image name: "AUDIT_SERVER" image file identification: "X-13" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:17.11 Overall Image Checksum: F21A75BC o [SYSEXE]BACKUP.EXE (new image) Image Identification Information Image name: "BACKUP" image file identification: "V8.4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 30-SEP-2010 11:00:46.82 Overall Image Checksum: EA94BE55 o [SYSLIB]BACKUPSHR.EXE (new image) Image Identification Information Image name: "BACKUPSHR" image file identification: "V8.4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 30-SEP-2010 10:59:57.65 Overall Image Checksum: 55DBAB39 o [SYSEXE]CDU.EXE (new image) Image Identification Information Image name: "CDU" image file identification: "I01-11" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:17.42 Overall Image Checksum: 397B73B2 o [SYSMSG]CLIUTLMSG.EXE (new image) Image Identification Information Image name: "CLIUTLMSG" image file identification: "X-3" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:16.51 Overall Image Checksum: 34EA5BEA o [SYSLIB]CLUE$SDA.EXE (new image) Image Identification Information Image name: "CLUE$SDA" image file identification: "X-69" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:53.92 Overall Image Checksum: 2433EAD7 o [SYSEXE]COPY.EXE (new image) Image Identification Information Image name: "COPY" image file identification: "X02-01" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:17.09 Overall Image Checksum: E3650C99 o [SYSEXE]DBGHK$HOST_KERNEL.EXE (new image) Image Identification Information Image name: "DBGHK$HOST_KERNEL" image file identification: "V8.4-000" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:59:12.51 Overall Image Checksum: E58D00ED o [SYSEXE]DBGHK$PRCDUMP_KERNEL.EXE (new image) Image Identification Information Image name: "DBGHK$PRCDUMP_KERNEL" image file identification: "V8.4-000" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:59:15.06 Overall Image Checksum: 20F2A7EC o [SYSEXE]DBGHK$SYSDUMP_KERNEL.EXE (new image) Image Identification Information Image name: "DBGHK$SYSDUMP_KERNEL" image file identification: "V8.4-000" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:59:16.92 Overall Image Checksum: B549FCE7 o [SYSEXE]DCL.EXE (new image) Image Identification Information Image name: "DCL" image file identification: "X-54" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:13.59 Overall Image Checksum: DA113FDB o [SYSLIB]DEBUG.EXE (new image) Image Identification Information Image name: "DEBUG" image file identification: "V8.4-000" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:38.97 Overall Image Checksum: B513386A o [SYSLIB]DEBUGSHR.EXE (new image) Image Identification Information Image name: "DEBUGSHR" image file identification: "V8.4-000" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:55.93 Overall Image Checksum:98AF1A7B o [SYS$LDR]FLT$DEBUG.EXE (new image) Image Identification Information Image name: "FLT$DEBUG" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:51.71 Overall Image Checksum: 4462BC30 o [SYSLIB]DEC$BASRTL.EXE (new image) Image Identification Information Image name: "DEC$BASRTL" image file identification: "V01-036" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:15:26.59 Overall Image Checksum: 81B96312 o [SYSLIB]DEC$FORRTL.EXE (new image) Image Identification Information Image name: "DEC$FORRTL" image file identification: "V01-07.004" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:57:36.98 Overall Image Checksum: AD966D52 o [SYSLIB]DECC$SHR.EXE (new image) Image Identification Information Image name: "DECC$SHR" image file identification: "V8.4-00" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 9-DEC-2010 11:59:37.71 Overall Image Checksum: 917CA9B o [SYSLIB]DECC$SHRP.EXE (new image) Image Identification Information Image name: "DECC$SHRP" image file identification: "V8.4-00" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:56:24.10 Overall Image Checksum: C4694AC7 o [SYSEXE]DIRECTORY.EXE (new image) Image Identification Information Image name: "DIRECTORY" image file identification: "X02-01" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:17.61 Overall Image Checksum: 840A08AB o [SYSLIB]EDTSHR.EXE (new image) Image Identification Information Image name: "EDTSHR" image file identification: "1-050" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:15:26.98 Overall Image Checksum: 28651612 o [SYSEXE]EFI$BCFG.EXE (new image) Image Identification Information Image name: "EFI$BCFG" image file identification: "X-40" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:10:33.87 Overall Image Checksum: B6A0A868 o [SYSEXE]ERRFMT.EXE (new image) Image Identification Information Image name: "ERRFMT" image file identification: "X-22" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:10:08.63 Overall Image Checksum: 4CFCCB81 o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information Image name: "EXCEPTION" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:53.98 Overall Image Checksum: 7D0B2152 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information Image name: "EXCEPTION_MON" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:59.58 Overall Image Checksum: 7D0B2152 o [SYS$LDR]EXEC_INIT.EXE (new image) Image Identification Information Image name: "EXEC_INIT" image file identification: "X-217" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:04.85 Overall Image Checksum: BE91A673 o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information Image name: "F11BXQP" image file identification: "XQP V84R_10 CB4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:00.81 Overall Image Checksum: 2767F0D4 o [SYSEXE]F11CACP.EXE (new image) Image Identification Information Image name: "F11CACP" image file identification: "X-13" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:16.63 Overall Image Checksum: 858832A3 o [SYSEXE]F11DACP.EXE (new image) Image Identification Information Image name: "F11DACP" image file identification: "X-13" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:17.63 Overall Image Checksum: 12EC70DC o [SYSLIB]DCE$LIB_SHR.EXE (new image) Image Identification Information Image name: "DCE$LIB_SHR" image file identification: "DCE V3.2-100509" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 10-MAY-2010 02:54:11.62 Overall Image Checksum: 1E7AB502 o [SYSEXE]ICAPINIT.EXE (new image) Image Identification Information Image name: "ICAPINIT" image file identification: "X-20" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:11.55 Overall Image Checksum: AACCEF10 o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) Image Identification Information Image name: "IMAGE_MANAGEMENT" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:12.68 Overall Image Checksum: 102AE8D0 o [SYSLIB]IMGDMP.EXE (new image) Image Identification Information Image name: "IMGDMP" image file identification: "X-71" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:21.00 Overall Image Checksum: DF125D99 o [SYSEXE]INDICTMENT_SERVER.EXE (new image) Image Identification Information Image name: "INDICTMENT_SERVER" image file identification: "X-9" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:16.86 Overall Image Checksum: 3DA25BA o [SYSEXE]INSTALL.EXE (new image) Image Identification Information Image name: "INSTALL" image file identification: "X-34" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:25.51 Overall Image Checksum: E5727767 o [SYSLIB]IOGEN$FIBRE_CONFIG.EXE (new image) Image Identification Information Image name: "IOGEN$FIBRE_CONFIG" image file identification: "X-39" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 15-SEP-2010 15:49:45.45 Overall Image Checksum: DDEB4425 o [SYSLIB]IOGEN$ISA_CONFIG.EXE (new image) Image Identification Information Image name: "IOGEN$ISA_CONFIG" image file identification: "X-21" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:07:19.51 Overall Image Checksum: A82BC75 o [SYSLIB]IOGEN$SCSI_CONFIG.EXE (new image) Image Identification Information Image name: "IOGEN$SCSI_CONFIG" image file identification: "X-14" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:57:20.56 Overall Image Checksum: 58D28E83 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information Image name: "IO_ROUTINES" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:20.05 Overall Image Checksum: C3DB7896 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information Image name: "IO_ROUTINES_MON" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:28.37 Overall Image Checksum: 20CE81A4 o [SYSEXE]IPB.EXE (new image) Image Identification Information Image name: "IPB" image file identification: "X-4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:33.14 Overall Image Checksum: 41A7E2A0 o [SYSEXE]LANCP.EXE (new image) Image Identification Information Image name: "LANCP" image file identification: "X-92" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:06.62 Overall Image Checksum: E17E8D49 o [SYSLIB]LBRSHR.EXE (new image) Image Identification Information Image name: "LBRSHR" image file identification: "I01-42" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:15:14.21 Overall Image Checksum: 32B5E0D4 o [SYSLIB]LCK$SDA.EXE (new image) Image Identification Information Image name: "LCK$SDA" image file identification: "X-28" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:37.95 Overall Image Checksum: E9B49F54 o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information Image name: "LIBRTL" image file identification: "X01-001" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:44:50.65 Overall Image Checksum: 95A58DB9 o [SYS$LDR]LOCKING.EXE (new image) Image Identification Information Image name: "LOCKING" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:31.71 Overall Image Checksum: 5E5183A9 o [SYS$LDR]LOGICAL_NAMES.EXE (new image) Image Identification Information Image name: "LOGICAL_NAMES" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:36.98 Overall Image Checksum: D7B2293F o [SYSEXE]MACRO.EXE (new image) Image Identification Information Image name: "MACRO" image file identification: "50-120-5-50F9M" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:05.08 Overall Image Checksum: E70FCB13 o [SYSEXE]MSA$UTIL.EXE (new image) Image Identification Information Image name: "MSA$UTIL" image file identification: "X-28" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:12:35.55 Overall Image Checksum: 6E7E4C05 o [SYS$LDR]MSCP.EXE (new image) Image Identification Information Image name: "MSCP" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:11.87 Overall Image Checksum: AD2C6C8E o [SYSLIB]PKM$SDA.EXE (new image) Image Identification Information Image name: "PKM$SDA" image file identification: "X-29" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 6-JUL-2010 19:03:08.50 Overall Image Checksum: 7C814B0B o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information Image name: "PROCESS_MANAGEMENT" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 9-DEC-2010 12:21:06.22 Overall Image Checksum: E50840A o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information Image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 9-DEC-2010 12:21:14.71 Overall Image Checksum: 1AE64345 o [SYS$LDR]RMS.EXE (new image) Image Identification Information Image name: "RMS" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 9-DEC-2010 12:19:29.09 Overall Image Checksum: FFE756FF o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information Image name: "SDA$SHARE" image file identification: "X-2" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:42.91 Overall Image Checksum: 3744C1E o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information Image name: "SECURITY" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:51.96 Overall Image Checksum: B8E7C7A0 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information Image name: "SECURITY_MON" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:54.50 Overall Image Checksum: 8EDF3190 o [SYSEXE]SET.EXE (new image) Image Identification Information Image name: "SET" image file identification: "X02-00" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:59:12.16 Overall Image Checksum: DBEDB1F0 o [SYSEXE]SETSHOSHADOW.EXE (new image) Image Identification Information Image name: "SETSHOSHADOW" image file identification: "X-02" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:39.16 Overall Image Checksum: AF44C07F o [SYSEXE]SHADOW_SERVER.EXE (new image) Image Identification Information Image name: "SHADOW_SERVER" image file identification: "X-27" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:24.05 Overall Image Checksum: 6E254E42 o [SYS$LDR]SHELL16K.EXE (new image) Image Identification Information Image name: "SHELL16K" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:10.39 Overall Image Checksum: B1DC91B0 o [SYS$LDR]SHELL32K.EXE (new image) Image Identification Information Image name: "SHELL32K" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:13.44 Overall Image Checksum: 73F34B95 o [SYS$LDR]SHELL64K.EXE (new image) Image Identification Information Image name: "SHELL64K" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:15.75 Overall Image Checksum: E62635F8 o [SYS$LDR]SHELL8K.EXE (new image) Image Identification Information Image name: "SHELL8K" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:05.90 Overall Image Checksum: 5C0A23FF o [SYSEXE]SHOW.EXE (new image) Image Identification Information Image name: "SHOW" image file identification: "X-8" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:19:28.98 Overall Image Checksum: 20FA83BE o [SYSEXE]SHWCLSTR.EXE (new image) Image Identification Information Image name: "SHWCLSTR" image file identification: "X-27" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:59:12.78 Overall Image Checksum: 3A7043B9 o [SYSLIB]SMGSHR.EXE (new image) Image Identification Information Image name: "SMGSHR" image file identification: "SMG$ X1.0-001" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:56:20.10 Overall Image Checksum: 2DD21893 o [SYSEXE]SMPUTIL.EXE (new image) Image Identification Information Image name: "SMPUTIL" image file identification: "X-30" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:10:06.48 Overall Image Checksum: 4ECACE4 o [SYSEXE]SORTMERGE.EXE (new image) Image Identification Information Image name: "SORTMERGE" image file identification: "V08-013" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:30.86 Overall Image Checksum: AC317224 o [SYSLIB]SORTSHR.EXE (new image) Image Identification Information Image name: "SORTSHR" image file identification: "V08-013" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:57:19.11 Overall Image Checksum: 560F33AB o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information Image name: "SYS$BASE_IMAGE" image file identification: "IA64 XCB8-J2I" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 17:52:25.04 Overall Image Checksum: 9AFC672B o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information Image name: "SYS$CLUSTER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:14.54 Overall Image Checksum: D22FDAE0 o [SYS$LDR]SYS$CLUSTER_MON.EXE (new image) Image Identification Information Image name: "SYS$CLUSTER_MON" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:20.12 Overall Image Checksum: CFA8EBA7 o [SYS$LDR]SYS$CMDRIVER.EXE (new image) Image Identification Information Image name: "SYS$CMDRIVER" image file identification: "X-5" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:55.59 Overall Image Checksum: C96897F o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information Image name: "SYS$DKDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:14.05 Overall Image Checksum: E78E73E3 o [SYS$LDR]SYS$DNDRIVER.EXE (new image) Image Identification Information Image name: "SYS$DNDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:36.74 Overall Image Checksum: DEE5F0A5 o [SYS$LDR]SYS$DZCDRIVER.EXE (new image) Image Identification Information Image name: "SYS$DZCDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:46.35 Overall Image Checksum: ECE337BB o [SYS$LDR]SYS$EIGBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$EIGBTDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 15-SEP-2010 15:50:51.03 Overall Image Checksum: B66A8957 o [SYS$LDR]SYS$GHDRIVER.EXE (new image) Image Identification Information Image name: "SYS$GHDRIVER" image file identification: "DW V8.4-100903" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:59:16.70 Overall Image Checksum: 9D71158B o [SYS$LDR]SYS$HWP0001.EXE (new image) Image Identification Information Image name: "SYS$HWP0001" image file identification: "X-35" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:10:27.37 Overall Image Checksum: 3083FF7 o [SYS$LDR]SYS$HWP0004.EXE (new image) Image Identification Information Image name: "SYS$HWP0004" image file identification: "X-35" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:10:30.81 Overall Image Checksum: BEFFC254 o [SYS$LDR]SYS$IPC_SERVICES.EXE (new image) Image Identification Information Image name: "SYS$IPC_SERVICES" image file identification: "V1.3-X03E-XCB4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:02.58 Overall Image Checksum: 99C7C4A9 o [SYS$LDR]SYS$LASTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$LASTDRIVER" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 6-JUL-2010 19:02:07.00 Overall Image Checksum: EE4DD88B o [SYS$LDR]SYS$PCIE_SUPPORT.EXE (new image) Image Identification Information Image name: "SYS$PCIE_SUPPORT" image file identification: "X-35" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:10:53.70 Overall Image Checksum: BFFB6434 o [SYS$LDR]SYS$PCI_SUPPORT.EXE (new image) Image Identification Information Image name: "SYS$PCI_SUPPORT" image file identification: "X-35" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:10:20.78 Overall Image Checksum: DF096D31 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PEDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:28.47 Overall Image Checksum: 2A596F18 o [SYS$LDR]SYS$PEDRIVER_MON.EXE (new image) Image Identification Information Image name: "SYS$PEDRIVER_MON" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:40.06 Overall Image Checksum: 4D1729E0 o [SYS$LDR]SYS$PGQBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PGQBTDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 15-SEP-2010 15:50:48.88 Overall Image Checksum: 53FE7201 o [SYS$LDR]SYS$PKMDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKMDRIVER" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:32.10 Overall Image Checksum: E3F97B77 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKRDRIVER" image file identification: "X-5" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:28.04 Overall Image Checksum: FC17D8E2 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKWDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 15-SEP-2010 15:51:10.63 Overall Image Checksum: D54F31DE o [SYS$LDR]SYS$PLATFORM_SUPPORT.EXE (new image) Image Identification Information Image name: "SYS$PLATFORM_SUPPORT" image file identification: "X-35" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:38.51 Overall Image Checksum: DE87A1AA o [SYSLIB]SYS$SETBOOTSHR.EXE (new image) Image Identification Information Image name: "SYS$SETBOOTSHR" image file identification: "SB V6.0-1" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:57:19.00 Overall Image Checksum: 53D38BCD o [SYS$LDR]SYS$SHDRIVER.EXE (new image) Image Identification Information Image name: "SYS$SHDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:44.65 Overall Image Checksum: 4CFE4783 o [SYS$LDR]SYS$SRDRIVER.EXE (new image) Image Identification Information Image name: "SYS$SRDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 9-DEC-2010 12:19:39.20 Overall Image Checksum: 66FF03A2 o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) Image Identification Information Image name: "SYS$TRANSACTION_SERVICES" image file identification: "V2.1-X035-XCAU" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 30-SEP-2010 11:00:42.87 Overall Image Checksum: E27F8FDA o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information Image name: "SYS$VM" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:30.58 Overall Image Checksum: 105F76DC o [SYS$LDR]SYS$XFCACHE.EXE (new image) Image Identification Information Image name: "SYS$XFCACHE" image file identification: "V1.0" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 30-SEP-2010 11:01:06.16 Overall Image Checksum: DB1ED9EF o [SYS$LDR]SYS$XFCACHE_MON.EXE (new image) Image Identification Information Image name: "SYS$XFCACHE_MON" image file identification: "V1.0" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 30-SEP-2010 11:01:10.54 Overall Image Checksum: C0156AD4 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information Image name: "SYSBOOT" image file identification: "X-154" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:18.04 Overall Image Checksum: 74F07D60 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information Image name: "SYSGEN" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:02.20 Overall Image Checksum: F8361FE8 o [SYS$LDR]SYSGETSYI.EXE (new image) Image Identification Information Image name: "SYSGETSYI" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:29.79 Overall Image Checksum: 73E9C6B1 o [SYSEXE]SYSINIT.EXE (new image) Image Identification Information Image name: "SYSINIT" image file identification: "X-124" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:11:15.33 Overall Image Checksum: FD907C7E o [SYS$LDR]SYSLDR_DYN.EXE (new image) Image Identification Information Image name: "SYSLDR_DYN" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:31.51 Overall Image Checksum: 7DCF2B47 o [SYSMSG]SYSMGTMSG.EXE (new image) Image Identification Information Image name: "SYSMGTMSG" image file identification: "X-4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:21.43 Overall Image Checksum: 7A235E5D o [SYS$LDR]SYSTEM_DEBUG.EXE (new image) Image Identification Information Image name: "SYSTEM_DEBUG" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:51.90 Overall Image Checksum: 2CB6F89A o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:12:04.03 Overall Image Checksum: 28B112C6 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information Image name: "SYSTEM_PRIMITIVES_MIN" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:12:15.31 Overall Image Checksum: BE8CBAE1 o [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE (new image) Image Identification Information Image name: "SYSTEM_SYNCHRONIZATION" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:52.40 Overall Image Checksum: 161C2D6A o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE (new image) Image Identification Information Image name: "SYSTEM_SYNCHRONIZATION_MIN" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:50.40 Overall Image Checksum: D14A8BAA o [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE (new image) Image Identification Information Image name: "SYSTEM_SYNCHRONIZATION_UNI" image file identification: "X-5" image file build identification: "0100000001" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:53.59 Overall Image Checksum: D6B3BD38 o [SYSLIB]USB$SDA.EXE (new image) Image Identification Information Image name: "USB$SDA" image file identification: "X-32" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:19:06.01 Overall Image Checksum: 9B207014 o [SYSLIB]VMS$FORMAT_AUDIT_SYSTEM.EXE (new image) Image Identification Information Image name: "VMS$FORMAT_AUDIT_SYSTEM" image file identification: "X-19" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:18.38 Overall Image Checksum: 229A268A o [SYSLIB]VMS$VMS_ACMESHR.EXE (new image) Image Identification Information Image name: "VMS$VMS_ACMESHR" image file identification: "V1.0" image file build identification: "0100000002" linker identification: "Linker I02-38" Link Date/Time: 5-APR-2010 13:08:39.83 Overall Image Checksum: AED4791A o [SYSEXE]VMSHELP.EXE (new image) Image Identification Information Image name: "VMSHELP" image file identification: "X-4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:20.35 Overall Image Checksum: E616A288 o [SYSLIB]I64_CLUE$SDA.EXE (new image) Image Identification Information Image name: "I64_CLUE$SDA" image file identification: "X-69" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:46:54.95 Overall Image Checksum: 8972E72D o [SYSEXE]I64_DBGHK$HOST_KERNEL.EXE (new image) Image Identification Information Image name: "I64_DBGHK$HOST_KERNEL" image file identification: "V8.4-000" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:59:13.42 Overall Image Checksum: D4EC58D6 o [SYSLIB]IOGEN$AVIO_CONFIG.EXE (new image) Image Identification Information Image name: "IOGEN$AVIO_CONFIG" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:57:20.35 Overall Image Checksum: 983985BC o [SYSEXE]IPB_NOXDELTA.EXE (new image) Image Identification Information Image name: "IPB_NOXDELTA" image file identification: "X-4" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 21-AUG-2010 14:16:38.89 Overall Image Checksum: DBCE41AC o [SYS$LDR]LNM$DEBUG.EXE (new image) Image Identification Information Image name: "LNM$DEBUG" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:01.15 Overall Image Checksum: 5978A650 o [SYSLIB]LNM$SDA.EXE (new image) Image Identification Information Image name: "LNM$SDA" image file identification: "X-13" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:40.53 Overall Image Checksum: 75237EAD o [SYS$LDR]PRF$DEBUG.EXE (new image) Image Identification Information Image name: "PRF$DEBUG" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:14.50 Overall Image Checksum: B95D9D6F o [SYSLIB]PRF$SDA.EXE (new image) Image Identification Information Image name: "PRF$SDA" image file identification: "X-27" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:12:03.64 Overall Image Checksum: 5A37FC1 o [SYSLIB]SPL$SDA.EXE (new image) Image Identification Information Image name: "SPL$SDA" image file identification: "X-43" image file build identification: "0100000000" linker identification: "Linker I02-37" Link Date/Time: 14-MAY-2010 23:11:24.22 Overall Image Checksum: 1E5B7D4B o [SYS$LDR]SYS$ER57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:18.90 Overall Image Checksum: C9174816 o [SYS$LDR]SYS$ER57711_MON.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER_MON" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:19.24 Overall Image Checksum: B9AED804 o [SYS$LDR]SYS$EW57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:18.90 Overall Image Checksum: C9174816 o [SYS$LDR]SYS$EW57711_MON.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER_MON" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:19.24 Overall Image Checksum: B9AED804 o [SYS$LDR]SYS$GSPBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$GSPBTDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 12-AUG-2010 14:58:27.30 Overall Image Checksum: 8D292EB3 o [SYS$LDR]SYS$GSPDRIVER.EXE (new image) Image Identification Information Image name: "SYS$GSPDRIVER" image file identification: "X-5" image file build identification: "0100000002" linker identification: "Linker I02-37" Link Date/Time: 3-SEP-2010 12:47:50.38 Overall Image Checksum: 8819DE61 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information Image name: "SYS$LAN_CSMACD" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 7-SEP-2010 16:28:09.83 Overall Image Checksum: F6E16CBA o [SYSEXE]ACME_SERVER.EXE (new image) Image Identification Information Image name: "ACME_SERVER" image file identification: "X-42" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 7-SEP-2010 16:27:39.76 Overall Image Checksum: 20E2F175 o [SYSLIB]LDAP$SHR.EXE (new image) Image Identification Information Image name: "LDAP$SHR" image file identification: "LDAP V2.0-05000" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 22-SEP-2010 17:49:36.81 Overall Image Checksum: A9793D82 o [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE (new image) Image Identification Information Image name: "LDAPACME$LDAP-STD_ACMESHR" image file identification: "LDAP-STD V01.05" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:12.06 Overall Image Checksum: B23C2FC5 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information Image name: "SYS$EIDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 7-SEP-2010 16:28:07.44 Overall Image Checksum: 3EE9231A o [SYSEXE]LANACP.EXE (new image) Image Identification Information Image name: "LANACP" image file identification: "X-29" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:09.46 Overall Image Checksum: 981E18DE o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information Image name: "SYS$EW5700DRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:13.36 Overall Image Checksum: 6885F7F6 o [SYS$LDR]SYS$EWXFRAME.EXE (new image) Image Identification Information Image name: "SYS$EWXFRAMEDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:17.81 Overall Image Checksum: 23C180CD o [SYSLIB]LIBOTS.EXE (new image) Image Identification Information Image name: "LIBOTS" image file identification: "V1.0-1" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 17:52:53.62 Overall Image Checksum: 6CBFA382 o [SYSEXE]LMF.EXE (new image) Image Identification Information Image name: "LMF" image file identification: "X-26" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:11.29 Overall Image Checksum: 405DCFD o [SYS$LDR]NET$CSMACD.EXE (new image) Image Identification Information Image name: "CSMACD - NETWORK MANAGEMENT" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:12.34 Overall Image Checksum: AEBE3327 o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information Image name: "SMI$OBJSHR" image file identification: "X40-A9" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:40:54.16 Overall Image Checksum: 4C3AC1BA o [SYS$LDR]SWIS$DEBUG.EXE (new image) Image Identification Information Image name: "SWIS$DEBUG" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:29.86 Overall Image Checksum: E4C99ED7 o [SYSLIB]SWIS$SDA.EXE (new image) Image Identification Information Image name: "SWIS$SDA" image file identification: "X-6" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:31.90 Overall Image Checksum: 524C27CD o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information Image name: "SYS$FGEDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:12:03.75 Overall Image Checksum: 6D5842A9 o [SYS$LDR]TR$DEBUG.EXE (new image) Image Identification Information Image name: "TR$DEBUG" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:28.03 Overall Image Checksum: 52C5C475 o [SYSLIB]TR$SDA.EXE (new image) Image Identification Information Image name: "TR$SDA" image file identification: "X-18" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 11-OCT-2010 15:18:28.48 Overall Image Checksum: 581D8D55 o [SYSLIB]FLT$SDA.EXE (new image) Image Identification Information Image name: "FLT$SDA" image file identification: "X-8" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:57.09 Overall Image Checksum: 24AA59C6 o [SYSEXE]MONITOR.EXE (new image) Image Identification Information Image name: "MONITOR" image file identification: "X-26" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:37.24 Overall Image Checksum: D0AA273E o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information Image name: "SYSMAN" image file identification:"X01-22" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:40:58.11 Overall Image Checksum: A6131565 o [SYSLIB]SMI$SHR.EXE (new image) Image Identification Information Image name: "SMI$SHR" image file identification:"X01-04" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:40:52.44 Overall Image Checksum: 2754B038 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information Image name: "SMISERVER" image file identification: "X01-15" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:02.41 Overall Image Checksum: 50FFCED0 o [SYS$LDR]SYS$EHCIDRIVER.EXE (new image) Image Identification Information Image name: "SYS$EHCIDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:18:08.54 Overall Image Checksum: BB806079 o [SYS$LDR]SYS$OHCIDRIVER.EXE (new image) Image Identification Information Image name: "SYS$OHCIDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:18:02.22 Overall Image Checksum: 51D6991A o [SYS$LDR]SYS$UHCIDRIVER.EXE (new image) Image Identification Information Image name: "SYS$UHCIDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:18:14.85 Overall Image Checksum: 4C0FBA17 o [SYSLIB]ICC$SDA.EXE (new image) Image Identification Information Image name: "ICC$SDA" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:47.51 Overall Image Checksum: 945326A5 o [SYS$LDR]SYS$GLDRIVER.EXE (new image) Image Identification Information Image name: "SYS$GLDRIVERDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:18:47.42 Overall Image Checksum: E58D5824 o [SYS$LDR]SYS$GLDRIVER_MON.EXE (new image) Image Identification Information Image name: "SYS$GLDRIVERDRIVER_MON" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:18:50.51 Overall Image Checksum: DC02EB42 o [SYSEXE]SEARCH.EXE (new image) Image Identification Information Image name: "SEARCH" image file identification: "X02-09" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 20-OCT-2010 18:17:55.08 Overall Image Checksum: B6C7EED9 o [SYSLIB]PE$SDA.EXE (new image) Image Identification Information Image name: "PE$SDA" image file identification: "X-23" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:40.77 Overall Image Checksum: AF74A4AB o [SYS$LDR]SYS$IKUDRIVER.EXE (new image) Image Identification Information Image name: "SYS$IKUDRIVER" image file identification: "DW V8.4-101104" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 18:16:07.43 Overall Image Checksum: 3D49C68C o [SYS$LDR]SYS$IMUDRIVER.EXE (new image) Image Identification Information Image name: "SYS$IMUDRIVER" image file identification: "DW V8.4-101104" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 18:16:13.84 Overall Image Checksum: 9FF28778 o [SYS$LDR]SYS$IKXDRIVER.EXE (new image) Image Identification Information Image name: "SYS$IMUDRIVER" image file identification: "DW V8.4-101104" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 18:15:47.02 Overall Image Checksum: 8C69C757 o [SYS$LDR]SYS$MKDRIVER.EXE (new image) Image Identification Information Image name: "SYS$IMUDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:21.87 Overall Image Checksum: D9C627F8 o [SYSEXE]QMAN$QUEUE_MANAGER.EXE (new image) Image Identification Information Image name: "QMAN$QUEUE_MANAGER" image file identification: "X-3" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:09.01 Overall Image Checksum: DDA8CCED o [SYS$LDR]SYS$DADDRIVER.EXE (new image) Image Identification Information Image name: "SYS$DADDRIVER" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:41:29.03 Overall Image Checksum: 9A2553B8 o [SYSLIB]PTHREAD$RTL.EXE (new image) Image Identification Information Image name: "PTHREAD$RTL" image file identification: "V3.22-094" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:37:16.46 Overall Image Checksum: 8D7D8695 o [SYSLIB]PTHREAD$DBGSHR.EXE (new image) Image Identification Information Image name: "PTHREAD$DBGSHR" image file identification: "V3.22-094" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 4-NOV-2010 17:37:21.09 Overall Image Checksum: 8BC3E6CA o [SYSHLP.UNSUPPORTED]CDDVD$COPY.EXE (new image) Image Identification Information Image name: "CDDVD$COPY" image file identification: "CDDVD V1.0-1" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:09:39.02 Overall Image Checksum: 7C0C5E6 o [SYSHLP.UNSUPPORTED]CDDVD$COMPARE.EXE (new image) Image Identification Information Image name: "CDDVD$COMPARE" image file identification: "CDDVD V1.0-1" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:09:59.35 Overall Image Checksum: 1CCCCAC3 o [SYSMSG]CDDVD$MSG.EXE (new image) Image Identification Information Image name: "CDDVD$MSG" image file identification: "CDDVD V1.0-1" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 17:24:33.20 Overall Image Checksum: 33F0FBC8 o [SYSEXE]CDDVD$CP.EXE (new image) Image Identification Information Image name: "CDDVD$CP" image file identification: "CDDVD V1.0-1" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 28-NOV-2010 19:10:22.25 Overall Image Checksum: D101AA6C o [SYSUPD]AUTOGEN.COM (new file) o [SYSUPD]AUTOGEN_LM.COM (new file) o [SYSLIB]BACKUP.CLD (new file) o [SYSMGR]CLUSTER_CONFIG.COM (new file) o [SYSMGR]CLUSTER_CONFIG_LAN.COM (new file) o [SYS$LDR]COPY.CLD (new file) o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]EXEC_INIT.STB (new file) o [SYS$LDR]F11BXQP.STB (new file) o [SYS$LDR]IMAGE_MANAGEMENT.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYSLIB]IO_ROUTINES_MON.STB (new file) o [SYSLIB]LIB.MLB (new file) o [SYSLIB]LIBRTL.DSF (new file) o [SYS$LDR]LIBRTL.STB (new file) o [SYS$LDR]LOCKING.STB (new file) o [SYS$LDR]LOGICAL_NAMES.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYSEXE]SHELL8K.STB (new file) o [SYSLIB]SHUTDOWN.COM (new file) o [SYS$LDR]STARLET.MLB (new file) o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) o [SYS$LDR]SYS$LIB_C.TLB (new file) o [SYS$LDR]SYS$PEDRIVER.STB (new file) o [SYS$LDR]SYS$PEDRIVER_MON.STB (new file) o [SYS$LDR]SYS$STARLET_C.TLB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYS$XFCACHE.STB (new file) o [SYS$LDR]SYS$XFCACHE_MON.STB (new file) o [SYS$LDR]SYSGETSYI.STB (new file) o [SYS$LDR]SYSLDR_DYN.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB (new file) o [SYSLIB]SYSTEM_SYNCHRONIZATION_UNI.STB (new file) o [SYS$STARTUP]VMS$CONFIG-050_SHADOW_SERVER.COM (new file) o [SYSEXE]VMS$DEVICE_STARTUP.COM (new file) o [SYSUPD]VMSINSTAL.COM (new file) o [SYSEXE]VMS_BCFG.EFI (new file) o [SYSEXE]VMS_SET.EFI (new file) o [SYSEXE]VMS_SHOW.EFI (new file) o [SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA (new file) o [SYSLIB]BASIC$STARLET.TLB (new file) o [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM (new file) o [SYSEXE]INS_STARTUP.COM (new file) o [SYS$LDR]LNM$DEBUG.STB (new file) o [SYS$LDR]MSCP.STB (new file) o [SYSUPD]NPAR.MOF (new file) o [SYSUPD]NPARREG.MOF (new file) o [SYS$LDR]PRF$DEBUG.STB (new file) o [SYS$LDR]RMS.STB (new file) o [SYS$LDR]SHELL16K.STB (new file) o [SYS$LDR]SHELL32K.STB (new file) o [SYS$LDR]SHELL64K.STB (new file) o [SYSLIB]STARLET.R64 (new file) o [SYSLIB]STARLET.REQ (new file) o [SYSLIB]STARLETPAS.TLB (new file) o [SYSLIB]STARLETSD.TLB (new file) o [SYS$LDR]SYS$CMDRIVER.STB (new file) o [SYS$LDR]SYS$DKDRIVER.STB (new file) o [SYS$LDR]SYS$DNDRIVER.STB (new file) o [SYS$LDR]SYS$GHDRIVER.STB (new file) o [SYS$LDR]SYS$GSPDRIVER.STB (new file) o [SYS$LDR]SYS$IPC_SERVICES.STB (new file) o [SYS$LDR]SYS$LASTDRIVER.STB (new file) o [SYS$LDR]SYS$PKMDRIVER.STB (new file) o [SYS$LDR]SYS$PKRDRIVER.STB (new file) o [SYS$LDR]SYS$PKWDRIVER.STB (new file) o [SYS$LDR]SYS$SRDRIVER.STB (new file) o [SYS$LDR]SYSTEM_DEBUG.STB (new file) o [SYSHLP]UAFHELP.HLB (new file) o [SYSMSG]VMSINSTAL_LANGUAGE.COM (new file) o [SYSEXE]VMS_LOADER.EFI (new file) o [SYS$LDR]SYS$LAN_CSMACD.STB (new file) o [SYS$LDR]SYS$EIDRIVER.STB (new file) o [SYSHLP.EXAMPLES]LDAP_EXAMPLE.C (new file) o [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF (new file) o [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT (new file) o [SYS$STARTUP]LDAPACME$CONFIG-STD.INI_TEMPLATE (new file) o [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT_3DES.C (new file) o [SYS$LDR]SYS$EW5700.STB (new file) o [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT$EXAMPLES.TXT (new file) o [SYS$LDR]SYS$FGEDRIVER.STB (new file) o [SYS$LDR]NET$CSMACD.STB (new file) o [SYSEXE]TCPIPV4.EFI (new file) o [SYSEXE]FTP.EFI (new file) o [SYSEXE]IFCONFIG.EFI (new file) o [SYSEXE]PING.EFI (new file) o [SYSEXE]ROUTE.EFI (new file) o [SYS$LDR]TR$DEBUG.STB (new file) o [SYS$LDR]SWIS$DEBUG.STB (new file) o [SYSLIB]DECC$RTLDEF.TLB (new file) o [SYS$LDR]SYS$EHCIDRIVER.STB (new file) o [SYS$LDR]SYS$UHCIDRIVER.STB (new file) o [SYS$LDR]SYS$SHDRIVER.STB (new file) o [SYS$LDR]FLT$DEBUG.STB (new file) o [SYS$LDR]SYS$OHCIDRIVER.STB (new file) o [SYSHLP]MAILHELP.HLB (new file) o [SYSEXE]SHADOW_SERVER.STB (new file) o [SYSLIB]DECC$RTLDEF.TLB (new file) o [SYS$LDR]SYS$IKUDRIVER.STB (new file) o [SYS$LDR]SYS$IMUDRIVER.STB (new file) o [SYS$LDR]SYS$IKXDRIVER.STB (new file) o [SYS$LDR]SYS$MKDRIVER.STB (new file) o [SYS$LDR]SYS$DADDRIVER.STB (new file) o [SYSHLP]MSA_UTIL_HELP.HLB (new file) o [SYSUPD]ANALYZE.hlp (new file) o [SYSUPD]BACKUP.hlp (new file) o [SYSUPD]CRTL.hlp (new file) o [SYSUPD]DCLDICT.hlp (new file) o [SYSUPD]LIBRARY.hlp (new file) o [SYSUPD]SYSTEM.hlp (new file) o [SYSUPD]UTIL_ROUTINES.hlp (new file) 10 INSTALLATION INSTRUCTIONS 10.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 10.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_UPDATE-V0500.ZIPEXE 10.3 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS84I_UPDATE[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 10.4 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=HP/BASE=I64VMS/VER=V5.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_UPDATE-V0500 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_UPDATE/PRODUCER=HP/BASE=I64VMS/VER=V5.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 10.5 Upgrading from the Existing OpenVMS Version 8.4 Update Patch If you are running OpenVMS on BL8x0c i2 server blades with patch level VMS84I_UPDATE-V0400 or VMS84I_UPDATE-V0300 or VMS84I_UPDATE-V0200, and upgrading to VMS84I_UPDATE-V0500, HP recommends that you upgrade the system firmware to version 21.08 once you have installed VMS84I_UPDATE-V0500. 10.6 Installing OpenVMS Version 8.4 on BL8x0c i2 Server Blades or rx2800 i2 Servers with the Latest Firmware If you are installing OpenVMS using an OpenVMS version 8.4 kit that does not include the update 500 kit on any of the following servers: - BL8x0c i2 server blades running with firmware bundle version 21.08 or later (or) - rx2800 i2 servers running with firmware bundle version 21.07 or later Perform the following steps: 1. Install OpenVMS version 8.4, licenses, and configure TCPIP (DO NOT REBOOT after this step). 2. Copy the necessary patch kits from ITRC. 3. Install VMS84I_PCSI-V0200. 4. Logoff and login again or open a new session. 5. Install VMS84I_UPDATE-V0500. 6. Reboot the system. Failure to follow the above procedure might result in a system reset during boot. In the event that you are faced with this situation, you can work around it by booting with minimum startup followed by an exclusion of the graphics cards (GH* devices) from being configured. Complete the following the steps: Shell> vms_loader -fl ,1 SYSBOOT> set startup_p1 "MIN" SYSBOOT> continue $ MCR SYSMAN IO SHOW EXCLUDE $ MCR SYSMAN IO SET EXCLUDE=(GHA0,) $ REBOOT Perform the Normal boot (clear the startup_p1 parameter) Shell> vms_loader -fl ,1 SYSBOOT> set startup_p1 " " SYSBOOT> continue After installing update 500 remove the graphics device (GHA0) from the exclusion list and reboot the system. The GHA0 device can be removed from the exclusion list by following the steps below: $ MCR SYSMAN IO SHOW EXCLUDE $ MCR SYSMAN IO SET EXCLUDE=("other devices to be excluded") Retain other devices and remove only GHA0 device from the exclusion list. NOTE: To remove all the devices from the exclusion list execute the following command: $ MCR SYSMAN IO SET EXCLUDE=(" ") $ REBOOT 10.7 Considerations for RAD Configuration during installation on BL8x0c i2 server blades Until the VMS84I_UPDATE-V0500 kit has been successfully installed, a system running OpenVMS V8.4 on BL8x0c i2 server blades in a large memory configuration (1 TB and above **) must use the "MostlyNUMA" (default) or "MaxNUMA" memory interleaving option. Otherwise, it might fail to boot with the following message: %SYSBOOT-F-PFNMEMMAP, failed to allocate pool for PFN memory map, status = 00000014 For example, a BL890c i2 server blades with all 96 memory slots populated with 16 GB DIMMs (96 * 16 GB = 1.5 TB) might fail to boot with the above message. This includes attempts to install from the OpenVMS source media that do not contain VMS84I_UPDATE-V0500 images. After VMS84I_UPDATE-V0500 has been installed, all memory interleaving options will be available. ** Currently this amount of memory can be realized with 16 GB DIMMs or a combination of 8 GB and 16 GB DIMMs. NOTE: The memory interleaving configuration can be modified at the EFI shell by invoking the "memconfig -mi