======================================================================= HP OpenVMS Update Kit for Integrity Servers VMS84I_UPDATE-V0600 Release Notes ======================================================================= 1 KIT NAME: VMS84I_UPDATE-V0600 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). 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. Refer to section 10.5 "Special Installation Instructions" for any such requirements BEFORE attempting to install the VMS84I_UPDATE-V0600 patch kit. 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 HP Smart Array P812 controller (AM312A). * Support for Dual-port 10GbE PCIe Ethernet Controller (AM225A, AM232A, and AM233A). For more information, see Section 5.1. The following I/O options which were supported with rx2800 i2 servers and BL8x0c i2 server blades, are now supported with legacy Itanium servers: * HP Smart Array P411 controller (AM311A) with legacy PCIe based Itanium rack servers. * HP NC532m Dual-port 10 GbE BL-c Adapter (467799-B21) with BL860c server blades or BL870c server blades. 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_UPDATE-V0500 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-V0300 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-V0600 KIT 5.1 New functionality addressed in this kit 5.1.1 New hardware support associated with the rx2800 i2 servers and other legacy PCIe based Itanium rack mounted servers o Support for HP Smart Array P812 controller (AM312A) The HP Smart Array P812 is the first 24 port serial attached SCSI (SAS) RAID controller from HP. It is the highest performing, highest capacity controller in the HP Smart Array SAS controller portfolio and provides new levels of storage connectivity for HP servers. o Support for Dual-port 10 GbE PCIe Ethernet Controller (AM225A, AM232A, and AM233A) The HP Integrity PCIe 2-port 10 GbE adapter is an eight lane (x8) PCI Express (PCIe) 10 Gigabit network solution offering optimal throughput. This update kit supports the following models: - AM225A HP 10GbE-SR PCIe 2-port NC532SFP adapter - AM232A HP 10GbE-LR PCIe 2-port NC532SFP adapter - AM233A HP 10GbE-CR PCIe 2-port NC532SFP adapter Note: For SR card, use SR SFP+ modules. For LR card, use LR SFP+ modules. Minimum required firmware version for these cards is: - Firmware: 5.2.70 - EFI: 5.2.53 5.1.2 New features supported in this kit 0 LBR$OPEN continues to retry for two minutes (or more) on a file which is held exclusively LBR$OPEN continues to retry for a duration of two minutes (or more) when the same file is held exclusively by another process. A new logical LBR$OPEN_RETRYCNT is introduced. To control the duration while LBR$OPEN accesses the library if it is already opened by another process in exclusive mode. Images Affected: - [SYSLIB]LBRSHR.EXE 5.2 Problems addressed in this kit 5.2.1 System crash with INVEXCEPTN in SYS$HUBDRIVER 5.2.1.1 Problem Description: A system crash might occur, if a faulty USB DVD drive is connected to the system. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$HUBDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001111743 5.2.1.2 Workaround: None. 5.2.2 USB mass storage device fails to mount 5.2.2.1 Problem Description: If the USB mass storage device is not deconfigured properly during the previous disconnection, it might fail to mount. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$DNDRIVER.EXE - [SYSLIB]USB$SDA.EXE - [SYSEXE]EFI$BCFG.EXE - [SYSEXE]ERRFMT.EXE QuIX case(s) reporting this problem: None. 5.2.2.2 Workaround: None. 5.2.3 USB serial multiplexer devices fails to configure on BL8x0c i2 server blades and rx2800 i2 servers 5.2.3.1 Problem Description: USB serial multiplexer devices fail to configure on BL8x0c i2 server blades and rx2800 i2 servers. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$UHCIDRIVER.EXE - [SYSLIB]USB$SDA.EXE QuIX case(s) reporting this problem: None. 5.2.3.2 Workaround: None. 5.2.4 MSA$UTIL does not display the correct cache low battery status message 5.2.4.1 Problem Description: In MSA$UTIL, the SHOW CONTROLLER command does not display the correct battery status message. Now MSA$UTIL displays the correct cache low battery status message. This problem has been fixed. Images Affected: - [SYSEXE]MSA$UTIL.EXE QuIX case(s) reporting this problem: None. 5.2.4.2 Workaround: None. 5.2.5 Unable to update SAS controller firmware using MSA$UTIL 5.2.5.1 Problem Description: MSA$UTIL does not support update to firmware image size greater than 2 MB. Now MSA$UTIL can update SAS controller firmware image size greater than 2 MB. This problem has been fixed. Images Affected: - [SYSEXE]MSA$UTIL.EXE QuIX case(s) reporting this problem: None. 5.2.5.2 Workaround: None. 5.2.6 LUNs are created when invalid spare disk is specified 5.2.6.1 Problem Description: The MSA$UTIL ADD UNIT command succeeds and LUNs are created even if the specified spare disk is invalid (that is, number greater than 10 digits). Now the MSA$UTIL command prevents the creation of LUNs when an invalid spare disk is specified. This problem has been fixed. Images Affected: - [SYSEXE]MSA$UTIL.EXE QuIX case(s) reporting this problem: None. 5.2.6.2 Workaround: None. 5.2.7 MSA$UTIL SHOW CONTROLLER/FULL command displays error messages 5.2.7.1 Problem Description: If the default controller is not set in MSA$UTIL, SHOW CONTROLLER/FULL command displays an error message. This problem has been fixed. Images Affected: - [SYSEXE]MSA$UTIL.EXE QuIX case(s) reporting this problem: None. 5.2.7.2 Workaround: None. 5.2.8 MSA$UTIL fails to create a RAID 50 or RAID 60 LUN 5.2.8.1 Problem Description: MSA$UTIL fails to create a RAID 50 or RAID 60 LUN. An attempt to create a RAID 50 or RAID 60 LUN using the ADD UNIT command in MSA$UTIL, RAID 5 or RAID 6 (ADG) LUNs are created. MSA$UTIL displays the wrong Raid level for the created Logical Volume Raid as RAID 50 or RAID 60. This problem has been fixed. Images Affected: - [SYSEXE]MSA$UTIL.EXE QuIX case(s) reporting this problem: None. 5.2.8.2 Workaround: None. 5.2.9 MSA$UTIL fails to create a LUN greater than 1 TB 5.2.9.1 Problem Description: MSA$UTIL ADD UNIT command fails to create a LUN if the size of the logical unit exceeds 1 TB. Now MSA$UTIL creates a logical unit greater than 1 TB. This problem has been fixed. Images Affected: - [SYSEXE]MSA$UTIL.EXE QuIX case(s) reporting this problem: None. 5.2.9.2 Workaround: None. 5.2.10 A warning message while executing CLUSTER_CONFIG[_LAN].COM 5.2.10.1 Problem Description: An undefined symbol warning message is displayed when you run the CLUSTER_CONFIG[_LAN].COM command procedure for non-lan cluster configuration. This problem has been fixed. Images Affected: - [SYSMGR]CLUSTER_CONFIG.COM - [SYSMGR]CLUSTER_CONFIG_LAN.COM QuIX case(s) reporting this problem: None. 5.2.10.2 Workaround: None. 5.2.11 Incorrect load class displayed for IP interface 5.2.11.1 Problem Description: An incorrect bus load class is displayed by SCACP, if the IP interface is restarted in Cluster over IP (IPCI) environment. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.STB QuIX case(s) reporting this problem: None. 5.2.11.2 Workaround: None. 5.2.12 WEBES cannot translate PEDriver event messages 5.2.12.1 Problem Description: WEBES cannot translate PEDriver event messages. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.STB QuIX case(s) reporting this problem: QXCM1001079619 5.2.12.2 Workaround: None. 5.2.13 SHOW PORT/VC command displays incorrect hardware type 5.2.13.1 Problem Description: SHOW PORT/VC command in SDA displays incorrect hardware type. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.STB QuIX case(s) reporting this problem: None. 5.2.13.2 Workaround: None. 5.2.14 PEDriver crashes with INVEXCEPTN during excessive packet loss 5.2.14.1 Problem Description: The PEDriver crashes during excessive packet loss with the following crash dump summary information. This crash occurs in an environment where channel bandwidth is greater than 1 GB. Failing PC: FFFFFFFF.81429FD0 TR.RCV_ACK_C+005C0 Failing PS: 00000000.00000800 Module: SYS$PEDRIVER Offset: 0002EBD0 This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.STB QuIX case(s) reporting this problem: QXCM1001150138 5.2.14.2 Workaround: None. 5.2.15 Added new event type for PEDriver error logs 5.2.15.1 Problem Description: PEDriver packet error events which are reported under entry type 100 in ERRLOG.SYS are changed to entry type 127 for better readability. Images Affected: - [SYS$LDR]ERRORLOG.EXE - [SYS$LDR]ERRORLOG.STB QuIX case(s) reporting this problem: QXCM1001079606 5.2.15.2 Workaround: None. 5.2.16 LOCKMGRERR crash while creating a large lock tree 5.2.16.1 Problem Description: System crashes with LOCKMGRERR bugcheck if the lock manager reaches the architectural limit of lock IDs. Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB QuIX case(s) reporting this problem: QXCM1001070677 5.2.16.2 Workaround: None. 5.2.17 Problems with deadlock detection results in an application hang 5.2.17.1 Problem Description: Under certain conditions, a deadlock search might fail to detect and resolve the deadlock for a waiting lock. The applications that depend on the lock manager to find and resolve deadlocks might result in an application hang. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]SYS$CLUSTER.STB - [SYS$LDR]SYS$CLUSTER_MON.EXE - [SYS$LDR]SYS$CLUSTER_MON.STB QuIX case(s) reporting this problem: QXCM1001140177 5.2.17.2 Workaround: None. 5.2.18 Inappropriate message displayed when BOOT_OPTIONS.COM is run on an Alpha system 5.2.18.1 Problem Description: BOOT_OPTIONS.COM utility is intended to run only on an Integrity server systems. If it is run on an Alpha system, it displays the following warning message: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling \SAY\ This problem has been fixed. Images Affected: - [SYSMGR]BOOT_OPTIONS.COM QuIX case(s) reporting this problem: QXCM1001098021 5.2.18.2 Workaround: None. 5.2.19 OpenVMS installation procedure ignores typed in answer, while adding boot options 5.2.19.1 Problem Description: During the installation of OpenVMS from an installation media, any typed in answer is treated as "NO" by the command procedure for the following question: Do you want to create or validate boot options? (Yes/No) [Yes] This problem has been fixed. Images Affected: - [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM - [SYSEXE]I64VMS$PCSI_INSTALL.COM QuIX case(s) reporting this problem: QXCM1001111653 5.2.19.2 Workaround: To create or validate boot options, select the default option and press 'Enter', instead of explicitly typing 'Yes' for the following question: Do you want to create or validate boot options? (Yes/No) [Yes] 5.2.20 BOOT_OPTIONS.COM fails to add a valid boot option, for a device name that does not begin with 'd' or '$' 5.2.20.1 Problem Description: While adding a boot option using BOOT_OPTIONS.COM utility, if the device name does not begin with 'd' or '$' and the default option is selected for the position of the boot option, it displays the following error message: efi$bcfg: Device is not found or not local. Status = 3 efi$bcfg: Unable to execute the Add Option. Status = 3 This problem has been fixed. Images Affected: - [SYSMGR]BOOT_OPTIONS.COM QuIX case(s) reporting this problem: QXCM1001104146 5.2.19.2 Workaround: Instead of pressing ENTER key to select the default option, explicitly type in the position number as below: Enter the desired position number (1,2,3,,,) of the entry. To display the Boot Options list, enter "?" and press Return. Position [1]: 1 5.2.21 The BOOT_OPTIONS.COM command procedure allows addition of a Boot Option from a non-privileged account without any warnings 5.2.21.1 Problem Description: BOOT_OPTIONS.COM utility allows a non-privileged user to add a boot option. But, booting from such a boot option, results in a failure with the following error message: Load of device failed: Not Found An appropriate message is displayed when the boot option is added from a non-privileged account. This problem has been fixed. Images Affected: - [SYSEXE]EFI$BCFG.EXE - [SYSEXE]ERRFMT.EXE QuIX case(s) reporting this problem: QXCM1001097546, QXCM1000921798 5.2.21.2 Workaround: None. 5.2.22 Boot options added by BOOT_OPTIONS.COM for certain devices on rx2800 i2 servers and BL8x0c i2 server blades fails to boot 5.2.22.1 Problem Description: A boot failure occurs because incorrect boot options are added by BOOT_OPTIONS.COM for certain devices on rx2800 i2 servers and BL8x0c i2 sever blades. For example, in the following cases an invalid boot option is added: - A satellite boot option added for an onboard ethernet card - Boot option for a device connected to "HP 4GB FC and 1 Gigabit Ethernet combo card" This problem has been fixed. Images Affected: - [SYSEXE]EFI$BCFG.EXE - [SYSEXE]ERRFMT.EXE QuIX case(s) reporting this problem: None. 5.2.22.2 Workaround: None. 5.2.23 Correct error status reported by SYSINIT 5.2.23.1 Problem Description: If SYSINIT encounters an unexpected error a bad status could be reported. This problem has been fixed. Images Affected: - [SYSEXE]SYSINIT.EXE QuIX case(s) reporting this problem: None. 5.2.23.2 Workaround: None. 5.2.24 System crash with INVEXCEPTN bugcheck when DECnet is disabled 5.2.24.1 Problem Description: When the DECnet is disabled on a LAN port using MCR NCL DISABLE CSMA STATION command, the corresponding LAN port is reset instead of disabling DECnet alone. Due to this LAN port reset there is an impact on the other applications running on the same port, which results in a system crash. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EI1000.EXE - [SYS$LDR]SYS$EI1000_MON.EXE QuIX case(s) reporting this problem: QXCM1001098728 5.2.24.2 Workaround: To disable the DECnet on the network, run the following commands: $ MCR NCL DISABLE ROUTING CIRCUIT $ MCR NCL DELETE ROUTING CIRCUIT 5.2.25 Application using OpenVMS CRTL fcntl() byte range locking feature might result in a hang 5.2.25.1 Problem Description: When a process tries to acquire the fcntl() lock on a byte range, it might result in a hang, when the same range has already been acquired by another process. The application using OpenVMS CRTL fcntl() will not respond. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHRP.EXE QuIX case(s) reporting this problem: QXCM1001108650 5.2.25.2 Workaround: None. 5.2.26 System crash with SHADDETINCON or INVEXCEPTN bugcheck 5.2.26.1 Problem Description: When multiple members are added or removed from the SHADOWSETS from different member nodes on the cluster, one or more system crashes resulted with one or more nodes having a different crash footprint than the other node(s). This problem has been fixed. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE QuIX case(s) reporting this problem: None. 5.2.26.2 Workaround: None. 5.2.27 System crash with CPUSPINWAIT bugcheck 5.2.27.1 Problem Description: While adding a member to a SHADOWSET in the cluster, a node that does not have a path to the new member online, the system crashes with CPUSPINWAIT bugcheck. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001065099 5.2.27.2 Workaround: Before adding a new member to the SHADOWSET ensure that the new member is visible to all the systems in a cluster. 5.2.28 System or cluster hang occurs during a shadow "write bitmap" reset 5.2.28.1 Problem Description: A small window exists where write IOs to a SHADOWSET can cause a deadlock between the SHADOW_SERVER process and a process on the system which is attempting to write to a SHADOWSET. Depending on the affected disk, this deadlock might cause a system or cluster hang. This hang occurs during a shadow "write bitmap" reset - the occasional clearing of a bitmap. This problem has been fixed. Images Affected: - [SYSEXE]SHADOW_SERVER.EXE - [SYSEXE]SHADOW_SERVER.STB QuIX case(s) reporting this problem: QXCM1001131786 5.2.28.2 Workaround: To minimize this problem, the shadow "write bitmap" reset threshold can be increased from the default value. 5.2.29 Shadow driver displays redundant mountverification messages 5.2.29.1 Problem Description After any storage firmware upgrade or switch reset, if the MPDEV_POLLER SYSGEN parameter is set, the Shadow driver displays redundant mountverification messages in console for every shadow devices once in every hour and takes nearly half a second to complete mountverification. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001128435, QXCM1001139179, QXCM1001144610 5.2.29.2 Workaround: None. 5.2.30 System crashes with INVEXCEPTN bugcheck 5.2.30.1 Problem Description: The uninitialized memory allocation for receive buffers by LAN driver from a nonpaged pool causes the system crash. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$LAN.EXE QuIX case(s) reporting this problem: QXCM1001105653 5.2.30.2 Workaround: None. 5.2.31 FORTRAN program fails after creating an indexed remote file 5.2.31.1 Problem Description: A FORTRAN program that uses a USEROPEN routine to create an indexed file on a remote system fails with an access violation after successfully creating the file and connecting to it. This problem has been fixed. Images Affected: - [SYSLIB]DEC$FORRTL.EXE QuIX case(s) reporting this problem: QXCM1001107379 5.2.31.2 Workaround: None. 5.2.32 LAN failover takes more than three seconds to failover from a 10 Gb (BCM57711) port to another port 5.2.32.1 Problem Description: When 10 Gb (BCM57711) LAN ports are involved in the failover group, LAN failover takes more than three seconds to switch to another active device in the failover group. This problem occurred because of the 10 Gb (BCM57711) device behavior. The driver is modified to address this problem. The problem has been fixed. Images Affected: - [SYS$LDR]SYS$EW57711.EXE - [SYS$LDR]SYS$ER57711.EXE - [SYS$LDR]SYS$EW57711_MON.EXE - [SYS$LDR]SYS$ER57711_MON.EXE QuIX case(s) reporting this problem: None. 5.2.32.2 Workaround: None. 5.2.33 A LAN link flap is observed on LAN card A6825 copper module 5.2.33.1 Problem Description A LAN link flap is observed on A6825A (copper module) when long unshielded twisted pair (UTP) cables are attached to NIC. The link might bounce excessively rendering the device unusable, accompanied by cyclic redundancy check (CRC) and other errors. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EW5700.EXE - [SYS$LDR]SYS$EW5700_MON.EXE QuIX case(s) reporting this problem: QXCM1000905461 5.2.33.2 Workaround: None. 5.2.34 BACKUP does not preserve the directory structure at the destination 5.2.34.1 Problem Description: BACKUP does not preserve the directory structure at the destination. This occurs when MFD [000000] is used to specify the path for the copy or restore operation. This problem has been fixed. Images Affected: - [SYSLIB]BACKUPSHR.EXE QuIX case(s) reporting this problem: QXCM1001093529 5.2.34.2 Workaround: None. 5.2.35 Processes hang in RWMPB state 5.2.35.1 Problem Description: If a system is not rebooted for 897 days or more, processes might hang in RWMPB state and a reboot might be required. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB QuIX case(s) reporting this problem: QXCM1001061198 5.2.35.2 Workaround: Reboot the system on or before 897 days of continuous uptime. 5.2.36 COPY/SYMLINK copies the target file 5.2.36.1 Problem Description: COPY/SYMLINK does not copy the symlink file; instead it copies the target file. This problem has been fixed. Images Affected: - [SYSEXE]COPY.EXE QuIX case(s) reporting this problem: None. 5.2.36.2 Workaround: None. 5.2.37 Possible boot hang while using reserved memory on Integrity systems with large memory sizes and RAD enabled 5.2.37.1 Problem Description: A boot hang might occur when reserved memory is used on Integrity systems with large memory sizes and RAD enabled. The following conditions might cause the system to hang: - When the memory is reserved for sizes such as 33 GB, 52 GB, and 62 GB from base RADs. - Memory configuration is set through EFI MEM manager because of MostlyUMA and the system has a 8 GB XFC reservation and 8 GB of custom reservations. If the memory configuration is then changed from MostlyUMA to BALANCED and the XFC reservation is increased to 16 GB, the system hangs. This problem has been fixed. Images Affected: - [SYS$LDR]EXEC_INIT.EXE - [SYS$LDR]EXEC_INIT.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB QuIX case(s) reporting this problem: QXCM1001078997, QXCM1001108693, QXCM1001108403 5.2.37.2 Workaround: Reserve the memory size in multiples of 1024 MB (that is, 1 GB). For example, a 90 GB reserved memory can be reserved as 92160 MB from SYSMAN. Note: Workaround might not work in all situations. 5.2.38 Possible SECREFNEG bugcheck while deleting process address space 5.2.38.1 Problem Description: Under some specific circumstances, a SECREFNEG bugcheck might occur when a process is deleted. The system might crash with the following footprint: Crash dump Summary Information: Crash Time: 26-APR-2010 11:17:42.00 Bugcheck Type: SECREFNEG, Section reference count went negative Node: (Cluster) CPU Type: HP rx8640 (1.60GHz/12.0MB) VMS Version: V8.3 Current Process: Current Image: Failing PC: FFFFFFFF.802B8D00 MMG_STD$SUBSECREF_C+001F0 Failing PS: 00000000.00000800 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 22-JUL-2009 10:42:27.06) Offset: 00158D00 ... Failing Instruction: MMG_STD$SUBSECREF_C+001F0: break.m 100002 This problem has been fixed. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB QuIX case(s) reporting this problem: QXCM1001037359 5.2.38.2 Workaround: None. 5.2.39 COPY/OVERLAY extends the size of the resultant file 5.2.39.1 Problem Description: COPY/OVERLAY extends the size of the output file even if no records are present in the input file. This problem has been fixed. Images Affected: - [SYSEXE]COPY.EXE QuIX case(s) reporting this problem: QXCM1001101770 5.2.39.2 Workaround: None. 5.2.40 Recursive DIRECTORY command fails with "SYSTEM-W-BADFILEVER" error message 5.2.40.1 Problem Description: On an ODS-2 disk, recursive DIRECTORY command fails and displays the error message "SYSTEM-W-BADFILEVER", when process SYMLINK attribute is set to WILDCARD or ELLIPSIS. Example: MDA0 is an ODS-2 disk and the process SYMLINK attribute is set to WILDCARD. $ DIR MDA0:[000000.TEST...] Directory MDA0:[000000.TEST] %DIRECT-E-OPENIN, error opening MDA0:[000000.TEST.A^.TXT]*.*;* as input -RMS-E-DNF, directory not found -SYSTEM-W-BADFILEVER, bad file version number A.TXT;1 Total of 1 file. $ This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE QuIX case(s) reporting this problem: None. 5.2.40.2 Workaround: None. 5.2.41 BACKUP does not follow the SYMLINK file 5.2.41.1 Problem Description: BACKUP does not follow SYMLINKs in its search of a directory path. SYMLINK files are saved and restored as is but they are not followed. This problem has been fixed and BACKUP has been modified to display the following informational message to the user. This message indicates that the link file is not followed: %BACKUP-I-SYMNOTFLW, KU2S4$LDA200:[000000]NEW.LINK;1 is a SYMLINK and BACKUP will not follow the link Images Affected: - [SYSLIB]BACKUPSHR.EXE - [SYSMSG]SYSMGTMSG.EXE QuIX case(s) reporting this problem: None. 5.2.41.2 Workaround: None. 5.2.42 Analyzing the AES encrypted saveset fails 5.2.42.1 Problem Description: Analyzing the Advanced Encryption Standard (AES) encrypted saveset fails and displays the following error message: %BACKUP-F-ENCINIERR, an error was encountered initializing an encryption stream -ENCRYPT-F-ILLALGSEL, algorithm selection unknown, unavailable, or unsupported This problem has been fixed. Images Affected: - [SYSLIB]BACKUPSHR.EXE QuIX case(s) reporting this problem: None. 5.2.42.2 Workaround: None. 5.2.43 DIRECTORY command issued on a directory file having special character dot(.) fails with an error message 5.2.43.1 Problem Description: When a directory file is created with a special character dot(.) as the last character of the directory file name, the look up for the directory contents fail with the following error message: -RMS-E-DNF, directory not found Example: $ SET PROCESS/PARSE_STYLE=EXTENDED $ CREATE/DIR [.DIR_WITH_DOT_AT_END^.]/LOG %CREATE-I-CREATED, $10$DKA0:[TEST.DIR_WITH_DOT_AT_END^.] created $ DIR [.DIR_WITH_DOT_AT_END^.] %DIRECT-E-OPENIN, error opening $10$DKA0:[TEST.DIR_WITH_DOT_AT_END^.]*.*;* as input -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ This problem has been fixed. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB QuIX case(s) reporting this problem: None. 5.2.43.2 Workaround: None. 5.2.44 ACCOUNTING /REJECTED command fails with an error message 5.2.44.1 Problem Description: ACCOUNTING utility fails with "OTS-F-OUTCONERR" error message when it operates on a binary accounting file created by using /REJECTED qualifier. Example: $ ACCOUNTING /TYPE=(IMAGE)/REJECTED=ACC.REST $ ACCOUNTING ACC.REST %OTS-F-OUTCONERR, output conversion error This problem has been fixed. Images Affected: - [SYSEXE]ACC.EXE QuIX case(s) reporting this problem: QXCM1001084494 5.2.44.2 Workaround: None. 5.2.45 The ACCOUNTING utility fails with an error "OTS-F-OUTCONERR", while reading accounting records written using SYS$SNDJBC system service 5.2.45.1 Problem Description: In OpenVMS V8.4 systems, the format of the terminal name in ACCOUNTING record is modified to support long device name. The $SNDJBC system service does not handle this new format. This problem has been fixed. Images Affected: - [SYS$LDR]MESSAGE_ROUTINES.EXE - [SYS$LDR]MESSAGE_ROUTINES.STB - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB QuIX case(s) reporting this problem: QXCM1001121400 5.2.45.2 Workaround: None. 5.2.46 SUBMIT command fails with "RMS-F-SYN" error 5.2.46.1 Problem Description: If the NAME contains special characters and the log file is in a root directory, SUBMIT/NAME="xxxx" command fails with the following error message: $ REPLY/ENABLE $SUBMIT/LOG=xyz.log/NAME=" SHOW LOCK 22A000 Lock Database Lock id: 0122A000 PID: 0001013C Flags: Par. id: 00000000 SUBLCKs: 0| LKB: FFFFFFFD.D6413080 BLKAST: 00000000 Priority: 0000 Granted at NL 00000000-FFFFFFFF RSB: FFFFFFFF.7FEBB980 Resource: 00000000 00006963 ci...... Status: VALBLKR VALBLKW Length 03 00000000 00000000 ........ User mode 00000000 00000000 ........ Group 00001 00000000 00000000 ........ Local copy SDA> SHOW LOCK A2A000 Lock Database Lock id: 0122A000 PID: 0001013C Flags: Par. id: 00000000 SUBLCKs: 0 LKB: FFFFFFFD.D6413080 BLKAST: 00000000 Priority: 0000 Granted at NL 00000000-FFFFFFFF RSB: FFFFFFFF.7FEBB980 Resource: 00000000 00006963 ci...... Status: VALBLKR VALBLKW Length 03 00000000 00000000 ........ User mode 00000000 00000000 ........ Group 00001 00000000 00000000 ........ In this example, the Lock Id A2A000 is greater than 7FFFFF. The lock information of 22A000 is displayed in this example because the upper bit of A2A000 is masked. This problem has been fixed. Images Affected: - [SYSLIB]SDA$SHARE.EXE QuIX case(s) reporting this problem: QXCM1001074108 5.2.56.2 Workaround: None. 5.2.57 F$FILE_ATTRIBUTES lexical function returns FALSE 5.2.57.1 Problem Description: The F$FILE_ATTRIBUTES lexical function returns FALSE if filespec argument contains installed image name along with the version. File version cannot be specified to this lexical as only one version of the image can be installed at a time. Example: $ WRITE SYS$OUTPUT F$FILE_ATTRIBUTES("SYS$SYSTEM:DCL.EXE;1", "KNOWN") FALSE $ This problem has been fixed and the lexical function F$FILE_ATTRIBUTES has been modified. It now returns a DCL-E-ILLFILEVER message when an installed image is specified with file version as shown in the following: $ WRITE SYS$OUTPUT F$FILE_ATTRIBUTES("SYS$SYSTEM:DCL.EXE;1", "KNOWN") %DCL-E-ILLFILEVER, file version numbers not permitted $ Images Affected: - [SYSEXE]DCL.EXE - [SYSMSG]SYSMSG.EXE QuIX case(s) reporting this problem: QXCM1001100895 5.2.57.2 Workaround: None. 5.2.58 Process hangs when two or more MTAACP requests are run simultaneously 5.2.58.1 Problem Description: When two or more MTAACP requests are run simultaneously, there is a possibility that these MTAACP requests may hang and the corresponding OPCOM messages are displayed on the console. Example: When two SAVESET COPY commands are run simultaneously from two different telnet sessions. In telnet session A, enter the following command: $ SAVESET COPY/IDENTICAL/SYNCH_READ mkb600:2010071512072159. mkb300:2010071512072159 Switch to telnet session B immediately and enter the following command: $ SAVESET COPY/IDENTICAL/SYNCH_READ mka600:2010071512155341. mkb100:2010071512155341 In telnet session C, the following console requests and messages are displayed: %%%%%%%%%%% OPCOM 3-AUG-2010 11:31:07.16 %%%%%%%%%%% Message from user SYSTEM on NODEA VOL004 not on _NODEA$MKB600: %%%%%%%%%%% OPCOM 3-AUG-2010 11:34:08.03 %%%%%%%%%%% Message from user SYSTEM on NODEA I/O error initializing volume on _NODEA$MKB100: This problem has been fixed. Images Affected: - [SYSEXE]MTAAACP.EXE QuIX case(s) reporting this problem: QXCM1001058067 5.2.58.2 Workaround: Provide a /PROCESSOR=UNIQUE qualifier while mounting the disk. This creates a separate MTAACP process for each device. 5.2.59 SHOW ERROR/FULL command exits with "%SYSTEM-F-VASFULL" error message 5.2.59.1 Problem Description: The SHOW ERROR/FULL command exits with "%SYSTEM-F-VASFULL, virtual address space is full" error message. This occurs when the system has more than 700 devices. This problem has been fixed. Images Affected: - [SYSEXE]SHOW.EXE QuIX case(s) reporting this problem: QXCM1001003793, QXCM1001117298 5.2.59.2 Workaround: None. 5.2.60 CONVERT/FDL command fails with an error message 5.2.60.1 Problem Description: If CONVERT/FDL command is used to convert an indexed file using the /SECONDARY=n qualifier, where n is greater than 1, the conversion might fail, even though the disk has sufficient free blocks. %CONVERT-F-CREA_ERR, error creating work file :CONVWORK.TMP;1 -RMS-F-FUL, device full (insufficient space for allocation) Example: $ COPY SYS$SYSTEM:SYSUAF.DAT []*/LOG %COPY-S-COPIED, SYS$COMMON:[SYSEXE]SYSUAF.DAT;1 copied to SYS$SYSDEVICE:[TEST]SYSUAF.DAT;1 (80 blocks) $ $ ANALYZE /RMS/FDL SYSUAF.DAT $ $ CONVERT/FDL=sysuaf.fdl sysuaf.dat sysuaf_new.dat/SECONDARY=2 %CONVERT-F-CREA_ERR, error creating work file SYS$SYSROOT:[SYSMGR]CONVWORK.TMP;3 -RMS-F-FUL, device full (insufficient space for allocation) $ This problem has been fixed. Images Affected: - [SYSLIB]CONVSHR.EXE QuIX case(s) reporting this problem: QXCM1001127682 5.2.60.2 Workaround: None. 5.2.61 Alignment faults in LIB$FIND_CVT_PATH routine 5.2.61.1 Problem Description: Alignment faults are reported while running the application which calls LIB$FIND_CVT_PATH routine. Exception PC Rate Exception PC Module Offset ----------------- ------------- -------------------------------------- ----------------------------------- Trace summary output: FFFFFFFF.85E4C441 31133.77 LIBRTL+0018A441 LIBRTL 0018A441 LIB$$FIND_CVT_PATH + 00001471 / LIB$$FIND_CVT_PATH + 00001471 FFFFFFFF.85E4C0D0 3534.39 LIBRTL+0018A0D0 LIBRTL 0018A0D0 LIB$$FIND_CVT_PATH + 00001100 / LIB$$FIND_CVT_PATH + 00001100 FFFFFFFF.841A3341 28332.90 LIBRTL+00187341 LIBRTL 00187341 LIB$$FIND_CVT_PATH + 000011E1 / LIB$$FIND_CVT_PATH + 000011E1 FFFFFFFF.841A3050 3219.12 LIBRTL+00187050 LIBRTL 00187050 LIB$$FIND_CVT_PATH + 00000EF0 / LIB$$FIND_CVT_PATH + 00000EF0 These alignment faults are fixed. Images Affected: - [SYSLIB]LIBRTL.EXE - [SYSLIB]LIBRTL.DSF - [SYSLIB]LIBRTL.STB QuIX case(s) reporting this problem: QXCM1001124869 5.2.61.2 Workaround: None. 5.2.62 TYPE/TAIL=n command fails with an error message 5.2.62.1 Problem Description: On OpenVMS V8.4 systems, TYPE/TAIL=n command (where n is the number of lines), fails with the following error message: -SYSTEM-E-UNSUPPORTED, unsupported operation or function Example: $ TYPE/TAIL=10 TMP_SORT_PID_MEM_20200CFE.TXT; %TYPE-W-READERR, error reading TEST$DKA0:[TEST.QXCM1001128688]TMP_SORT_PID_MEM_20200CFE.TXT;3 -SYSTEM-E-UNSUPPORTED, unsupported operation or function $ This problem has been fixed. Images Affected: - [SYSEXE]TYPE.EXE QuIX case(s) reporting this problem: QXCM1001128688 5.2.62.2 Workaround: None. 5.2.63 CPU time consumed by the DELETE command is higher on OpenVMS V8.4 than it is on previous versions 5.2.63.1 Problem Description: The DELETE command on OpenVMS V8.4 consumes more CPU time due to the activation of additional RTL images. This problem has been fixed. Images Affected: - [SYSEXE]DELETE.EXE QuIX case(s) reporting this problem: QXCM1001118197 5.2.63.2 Workaround: None. 5.2.64 DIFFERENCES command reports differences with undefined record format file 5.2.64.1 Problem Description: DIFFERENCES command executed on files with record format as "Undefined record format", report differences though there were none. This occurs only when the node name is part of the second input-file's file specification. Example: $ DIFF HELLO.OBJ;1 0.0"user pass"::SYS$SYSDEVICE:[TEMP]HELLO.OBJ;1 This problem has been fixed. Images Affected: - [SYSEXE]DIFF.EXE QuIX case(s) reporting this problem: QXCM1001103924 5.2.64.2 Workaround: Include the node specification in the first file and not in the second file as shown in the following example: DIFF 0"user pass"::SYS$SYSDEVICE:[TEMP]HELLO.OBJ;1 HELLO.OBJ;1 5.2.65 Setting the default value for SCH_SOFT_OFFLD and SCH_HARD_OFFLD parameter from SYSMAN sets the default value for the PAGED_LAL_SIZE parameter 5.2.65.1 Problem Description: Setting the SCH_SOFT_OFFLD parameter to default value from SYSMAN, sets the SCH_HARD_OFFLD parameter to its default value. Similarly, setting the SCH_HARD_OFFLD parameter to default value, sets the PAGED_LAL_SIZE parameter to its default value. Example: $ MC SYSMAN SYSMAN> PARAM USE CURRENT SYSMAN> PARAM SHOW SCH_SOFT_OFFLD Node USITY: Parameters in use: CURRENT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCH_SOFT_OFFLD 1-3 (none set) 0 1023 CPU bitmap D SYSMAN> SYSMAN> PARAM SHOW SCH_HARD_OFFLD Node USITY: Parameters in use: CURRENT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCH_HARD_OFFLD 1-2 (none set) 0 1023 CPU bitmap D SYSMAN> SYSMAN> PARAM SHOW PAGED_LAL_SIZE Node VIOLET: Parameters in use: CURRENT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- PAGED_LAL_SIZE 256 0 0 2560 Bytes D SYSMAN> SYSMAN> PARAM SET SCH_SOFT_OFFLD DEFAULT SYSMAN> PARAM WRITE CURRENT SYSMAN> SYSMAN> PARAM SHOW SCH_SOFT_OFFLD Node USITY: Parameters in use: CURRENT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCH_SOFT_OFFLD (none set) (none set) 0 1023 CPU bitmap D SYSMAN> SYSMAN> PARAM SHOW SCH_HARD_OFFLD Node USITY: Parameters in use: CURRENT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCH_HARD_OFFLD (none set) (none set) 0 1023 CPU bitmap D SYSMAN> SYSMAN> PARAM SET SCH_HARD_OFFLD default SYSMAN> PARAM WRITE CURRENT SYSMAN> SYSMAN> PARAM SHOW SCH_HARD_OFFLD Node USITY: Parameters in use: CURRENT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCH_HARD_OFFLD (none set) (none set) 0 1023 CPU bitmap D SYSMAN> SYSMAN> PARAM SHOW PAGED_LAL_SIZE Node USITY: Parameters in use: CURRENT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- PAGED_LAL_SIZE 0 0 0 2560 Bytes D SYSMAN> SYSMAN> EXIT $ This problem has been fixed. Images Affected: - [SYSEXE]SYSMAN.EXE - [SYSEXE]SMISERVER.EXE - [SYSLIB]SMI$OBJSHR.EXE - [SYSLIB]SMI$SHR.EXE QuIX case(s) reporting this problem: QXCM1001129074 5.2.65.2 Workaround: Set the default value for SCH_SOFT_OFFLD and SCH_HARD_OFFLD parameter from SYSGEN. 5.2.66 LBR$OPEN leaves the channel open when invoked with non-library file format 5.2.66.1 Problem Description: When LBR$OPEN is invoked with a non-library file format, it fails with "%LBR-E-ILLCTL - illegal control index" error message. In this case, LBR$OPEN leaves the channel open, which can lead to system hang if LBR$OPEN is called in a loop. This problem has been fixed. Images Affected: - [SYSLIB]LBRSHR.EXE QuIX case(s) reporting this problem: QXCM1001122623, QXCM1001126264, QXCM1001126255 5.2.66.2 Workaround: None. 5.2.67 XFC does not support GH regions greater than 4 MB 5.2.67.1 Problem Description: XFC does not support Granularity Hint (GH) regions greater than 4 MB. This leads to a maximum GH region size of 4 MB while reserving permanent memory for XFC on Integrity servers, which is capable of supporting GH region of size scaling up to 4 GB. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$XFCACHE.EXE - [SYS$LDR]SYS$XFCACHE_MON.EXE - [SYS$LDR]SYS$XFCACHE.STB - [SYS$LDR]SYS$XFCACHE_MON.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB QuIX case(s) reporting this problem: QXCM1001013838 5.2.67.2 Workaround: None. 5.2.68 SET PROCESS/AFFINITY command displays %CLI-W-CONFLICT warning message 5.2.68.1 Problem Description: The SET PROCESS/AFFINITY command displays %CLI-W-CONFLICT warning message when it is used with the /SET and /CLEAR qualifiers in the same command. This occurs even when different CPU IDs are specified, as shown in the following example: $ SET PROCESS/AFFINITY/SET=0/CLEAR=1 %CLI-W-CONFLICT, illegal combination of command elements - check documentation This problem has been fixed. Images Affected: - [SYSEXE]SET.EXE QuIX case(s) reporting this problem: None. 5.2.68.2 Workaround: None. 5.2.69 CREATE/SYMLINK command does not display any error message when the target disk is ODS-2 5.2.69.1 Problem Description: SYMLINKs are not supported on an ODS-2 disk but an attempt to create a SYMLINK on an ODS-2 disk succeeds. Example: $ INIT/STRUCTURE= 2 DKA100: test $ MOUNT/SYSTEM DKA100: test %MOUNT-I-MOUNTED, TEST mounted on _$5$DKA100: (ITAN) $ CREATE/SYMLINK="/DKA100/FOO.TXT" LINK2FOO.LNK/LOG %CREATE-I-CREATED, LINK2FOO.LNK created This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE QuIX case(s) reporting this problem: None. 5.2.69.2 Workaround: None. 5.2.70 EDIT/TPU command fails to open a file with error BADIRECTORY 5.2.70.1 Problem Description: This problem may also be observed if an application calls RMS $PARSE and then calls $SEARCH in loop until "no-more-files" condition is detected. For this error scenario RMS $SEARCH service returns RMS$_FND and SS$_BADDIRECTORY, as primary and secondary messages respectively, instead of RMS$_NMF (no-more-files) return value. This problem has been fixed. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB QuIX case(s) reporting this problem: QXCM1000855075 5.2.70.2 Workaround: Copy the file that EDIT/TPU failed to open using the DCL command COPY in the same location or at another location, and then open it. 5.2.71 ANALYZE/DISK_STRUCTURE/REPAIR DCL command fails with an error message 5.2.71.1 Problem Description: On OpenVMS V8.4 systems, ANALYZE/DISK_STRUCTURE/REPAIR DCL command fails with "ANALDISK-F-ALLOCMEM" error message, while repairing a large number of SYMLINK files on a disk. Example: Assume Disk DKA0: has 2200 SYMLINK files created from OpenVMS V8.3. The SYMLINK file names are from ACDC_1.LNK to ACDC_2200.LNK. When the VERIFY command on V8.4 is run on the disk, it successfully repairs 320 SYMLINK files starting from ACDC_1.LNK to ACDC_1286.LNK but fails when it tries to repair the 321st file named ACDC_1287.LNK. Note that files are stored in the directory and sorted in alphanumeric order. Therefore, the number of files in sorted order from ACDC_1.LNK to ACDC_1286.LNK would be 320. $ ANALYZE/DISK_STRUCTURE/REPAIR DKA0: ANALYZE/DISK_STRUCTURE/REPAIR for _DKA0: started on 23-JUN-2011 00:42:34.43 ... %ANALDISK-W-BADSYMENTRY, directory entry for ACDC_1287.LNK in directory (55771,51,0) TEST does not match symlink attribute in file header %ANALDISK-F-ALLOCMEM, error allocating virtual memory -LIB-F-BADBLOSIZ, bad block size $ This problem has been fixed. Images Affected: - [SYSEXE]VERIFY.EXE QuIX case(s) reporting this problem: None. 5.2.71.2 Workaround: None. 5.2.72 Debugger is unable to examine certain complex data structures 5.2.72.1 Problem Description: Debugger is unable to expand complex unions or data structures while examining them. An example of the problem is given below: $ TYPE TEST.C #include typedef struct _A{ int i; struct { int j; int k; struct _A *p; } ST; }A; void main() { A a1,a2; a1.i = 10; a1.ST.j=11; a1.ST.k=12; a1.ST.p=0; a2.i = 210; a2.ST.j=211; a2.ST.k=212; a2.ST.p=&a1; } While debugging this program, the following result is displayed: DBG> EX A2 TEST\main\a2 i: 210 ST j: 211 k: 212 p: 2060327712 DBG> ex *a2.ST.p *TEST\main\a2.ST.p i: 10 ST: 51539607563 [cycle found in type definitions] Here, the debugger does not expand ST when it examines by dereferencing a pointer. A similar behavior occurs for unions also. This is a limitation in the current debugger implementation of EXAMINE command. It has been overcome by providing an additional option to examine, EXAMINE/EXPAND. The EXAMINE/EXPAND works in the following way: DBG> EXAMINE/EXPAND *a2.ST.p %DEBUG-I-EXAMEXPAND, Use EXAMINE/EXPAND with caution *TEST\main\a2.ST.p i: 10 ST j: 11 k: 12 p: 0 DBG> Note that in case of genuine loops in the structure, such as the one below, the EXAMINE/EXPAND behavior is undefined. If the debugger goes into an infinite loop, avoid using EXAMINE/EXPAND. $ type a.cxx struct B; struct A { B &x; A( B &x ); }; struct B { A y; B(); }; A::A( B &xx ) : x(xx) {} B::B( ) : y( *this ) {} B b; //A a(b); void main() { B b1; A a1(b1); } Images Affected: - [SYSLIB]DBG$HA_KERNEL.EXE - [SYSLIB]DBG$HA_MAIN.EXE - [SYSMSG]DBGTBKMSG.EXE - [SYSLIB]DEBUG.EXE - [SYSLIB]DEBUGSHR.EXE - [SYSLIB]DEBUGSRVSHR.EXE - [SYSLIB]DEBUGUISHR.EXE - [SYSLIB]TRACE.EXE - [SYSHLP]DBG$HELP.HLB QuIX case(s) reporting this problem: QXCM1001066530 5.2.72.2 Workaround: None. 5.2.73 Debugger displays all components within a record as having the same offset 5.2.73.1 Problem Description: Debugger displays all components within a record as having the same offset. This happens in case of Ada programs compiled with the latest GNATADA compiler wavefront from Adacore. Example: procedure Record2 is type T_Rec is record Int1 : Integer; Int2 : Integer; Int3 : Integer; Int4 : Integer; end record; C : T_Rec := (others => 0); X : Integer; begin C.Int1 := 5000; end Record2; In this example, while debugging the program, the following problem is observed: record type (T_REC, 4 components), size: 16 bytes contains the following components: unallocatedINT1 : longword integer, size: 4 bytes, offset: 0 bytes INT2 : longword integer, size: 4 bytes, offset: 0 bytes INT3 : longword integer, size: 4 bytes, offset: 0 bytes INT4 : longword integer, size: 4 bytes, offset: 0 bytes structure has been padded, size: 12 bytes, offset: 4 bytes Note: All record components have offset of 0 bytes. This problem has been fixed. Images Affected: - [SYSLIB]DEBUGSHR.EXE QuIX case(s) reporting this problem: QXCM1001106222 5.2.73.2 Workaround: None. 5.2.74 System crashes due to non-synchronization between SYS$MKDRIVER and AUDIT server 5.2.74.1 Problem Description: If a tape drive is connected to a running system and the SYSMAN IO AUTO command is executed, a system crash might occur. This is due to a synchronization issue between SYS$MKDRIVER and AUDIT server. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE - [SYS$LDR]SYS$MKDRIVER.STB QuIX case(s) reporting this problem: QXCM1001060534, QXCM1001084216 5.2.74.2 Workaround: None. 5.2.75 IPC trace buffer overflow results in INCONSTATE crash 5.2.75.1 Problem Description: The Interprocess Communication (IPC) tracing mechanism is synchronized using IPC MEGA spinlock. In a particular trace event, if the tracing happens without holding IPC MEGA spinlock, it results in a wrong index calculation and overflows the IPC trace buffer. This overflow results in INCONSTATE crash. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE - [SYS$LDR]SYS$IPC_SERVICES.STB QuIX case(s) reporting this problem: QXCM1001073961 5.2.75.2 Workaround: None. 5.2.76 Application hangs in SYS$ICC_TRANSCEIVEW system service 5.2.76.1 Problem Description: When an application calls SYS$ICC_TRANSCEIVEW system service, it results in application hang. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE - [SYS$LDR]SYS$IPC_SERVICES.STB QuIX case(s) reporting this problem: QXCM1001097224 5.2.76.2 Workaround: None. 5.2.77 LAN failover does not work when the link status is down 5.2.77.1 Problem Description: When 10 Gb (BCM57711) LAN ports are involved in a failover group, LAN failover does not work if the link status for the current physical port is changed to down. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EW57711.EXE - [SYS$LDR]SYS$EW57711_MON.EXE - [SYS$LDR]SYS$ER57711.EXE - [SYS$LDR]SYS$ER57711_MON.EXE QuIX case(s) reporting this problem: QXCM1001098333, QXCM1001092127 5.2.77.2 Workaround: None. 5.2.78 Unable to access a directory containing unicode characters 5.2.78.1 Problem Description: An attempt to access a directory with unicode characters in the directory name fails with an error message. Example: $ DIR [.^U3042] %DIRECT-E-OPENIN, error opening SYS$SPECIFIC:[SYSMGR.TMP.TEST.^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 case(s) reporting this problem: None. 5.2.78.2 Workaround: None. 5.2.79 Generic USB driver(UG) may leave AST outstanding 5.2.79.1 Problem Description: The Asynchronous System Trap (AST) quota continues to be charged to the process, if the application runs down without deassigning the associated channels. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$UGDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001077934 5.2.79.2 Workaround: None. 5.2.80 Duplicate boot path is displayed for fibre channel system disk 5.2.80.1 Problem Description: Incorrect number of FC paths are displayed (that is, duplicate entry for the boot path), when the LUN number of the boot device is greater than 255(d). This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PGQDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001064459, QXCM1001101468 5.2.80.2 Workaround: None. 5.2.81 Multithreaded applications intermittently hangs 5.2.81.1 Problem Description: This update kit fixes an intermittent hang in a multithread application with upcalls enabled when performing I/O operations. This problem has been fixed. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB - [SYSLIB]PTHREAD$DBGSHR.EXE - [SYSLIB]PTHREAD$RTL.EXE QuIX case(s) reporting this problem: QXCM1001103965, QXCM1001110712, QXCM1001112125 5.2.81.2 Workaround: Disable the Inner Mode Semaphore (IMS) upcalls. To disable IMS upcalls, set the value of DISABLE_UPCALLS SYSGEN parameter to 768 decimal and restart the application: SYSGEN> SET DISABLE_UPCALLS 768 SYSGEN> WRITE ACTIVE SYSGEN> WRITE CURRENT SYSGEN> EXIT Note: Reboot is not required and the system should not have any noticeable performance impact. Disabling IMS upcalls does not affect processes already hung in this state. 5.2.82 Bootable physical devices not displayed in EFI prompt 5.2.82.1 Problem Description: Bootable physical disks are not displayed when the VMS_SHOW DEVICE command is executed from EFI in BL8x0c server blades and rx2660 Integrity servers. Bootable disks which are logical units have no problems. This problem has been fixed. Images Affected: - [SYSEXE]VMS_SHOW.EFI - [SYSEXE]VMS_BCFG.EFI - [SYSEXE]VMS_SET.EFI QuIX case(s) reporting this problem: None. 5.2.82.2 Workaround: None. 5.2.83 On rx2800 i2 servers, the console runs in 'POLLED' mode 5.2.83.1 Problem Description: The console on rx2800 i2 servers running OpenVMS works in the 'POLLED' mode instead of the 'INTERRUPT' mode. The following might be observed: 1. Sluggishness on the console. 2. Copying huge data on the console results in the following error message: %RMS-F-RER, file read error -SYSTEM-W-DATAOVERUN, data overrun This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PLATFORM_SUPPORT.EXE - [SYS$LDR]SYS$SRDRIVER.EXE QuIX case(s) reporting this problem: None. 5.2.83.2 Workaround: None. 5.2.84 Control characters or keyboard interrupts are not accepted on an RTA terminal device 5.2.84.1 Problem Description: Keyboard inputs such as CTRL/Y are not accepted on an RTA terminal device, if a detached process is spawned from this terminal. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$CTDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001108566, QXCM1001050322, QXCM1000953283 5.2.84.2 Workaround: None. 5.2.85 Multiple problems with AUTHORIZE utility 5.2.85.1 Problem Description: The following problems are observed in the AUTHORIZE utility: 1) When all the login flags for the user are specified in SYSUAF, subsequent "SHOW USER" command output gets truncated. Example: $ UAF MOD XYZ/flags=(AUDIT,AUTOLOGIN,CAPTIVE,DEFCLI,DISCTLY,- DISFORCE_PWD_CHANGE,DISIMAGE,DISMAIL,DISNEWMAIL,DISPWDDIC,DISPWDHIS,- DISPWDSYNCH,DISRECONNECT,DISREPORT,DISUSER,DISWELCOME,EXTAUTH,GENPWD,- LOCKPWD,PWD_EXPIRED,PWD2_EXPIRED,PWDMIX,RESTRICTED,VMSAUTH) $ UAF SHOW XYZ Username: XYZ Owner: SYSTEM_MANAGER Account: SYSTEM UIC: [10,11] ([XYZ]) CLI: DCL Tables: DCLTABLES Default: SYS$COMMON:[MD] LGICMD: LOGIN Flags: DisCtlY DefCLI LockPwd Restricted DisUser DisWelcome DisNewMail DisMail GenPwd Audit DisReport DisReconnect AutoLogin DisForce_Pwd_Change Captive DisImage DisPwdDic DisPwdHis ExtAuth MigratePwd VMSAuth D <-- The output stops here and gets truncated Primary days: Mon Tue Wed Thu Fri Secondary days: Sat Sun No access restrictions Expiration: (none) Pwdminimum: 10 Login Fails: 0 Pwdlifetime: 30 00:00 Pwdchange: (pre-expired) Last Login: (none) (interactive), (none) (non-interactive) Maxjobs: 0 Fillm: 128 Bytlm: 128000 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 150 JTquota: 4096 Prclm: 8 DIOlm: 150 WSdef: 4096 Prio: 4 ASTlm: 300 WSquo: 8192 Queprio: 4 TQElm: 100 WSextent: 16384 CPU: (none) Enqlm: 4000 Pgflquo: 256000 Authorized Privileges: ACNT BYPASS CMEXEC CMKRNL GRPNAM IMPERSONATE LOG_IO NETMBX OPER READALL SECURITY SETPRV SYSLCK SYSNAM SYSPRV TMPMBX VOLPRO WORLD Default Privileges: ACNT BYPASS CMEXEC CMKRNL GRPNAM IMPERSONATE LOG_IO NETMBX OPER READALL SECURITY SETPRV SYSLCK SYSNAM SYSPRV TMPMBX VOLPRO WORLD 2) AUTHORIZE utility does not limit page file quota (PGFLQUO) to less than 2,147,483,632. If a value greater than 2,147,483,632 is specified for a user in the SYSUAF, the user's login session hangs. 3) AUTHORIZE utility does not correctly display the UAF records with a large PGFLQUO specified. UAF> MODIFY TEST /PGFLQUO=2147483632 %UAF-I-MDFYMSG, user record(s) updated UAF> SHOW TEST . . CPU: (none) Enqlm: 25000 Pgflquo: ********* . . These problems have been fixed. Images Affected: - [SYSEXE]AUTHORIZE.EXE QuIX case(s) reporting this problem: QXCM1001108425, QXCM1001105197 5.2.85.2 Workaround: None. 5.2.86 The LOG10 C run-time library function returns a value of HUGE_VAL 5.2.86.1 Problem Description: The LOG10 C run-time library function returns a value of HUGE_VAL when an input value near zero is passed. As per standard, it must return a value of -HUGE_VAL in this situation. The problem occurs only when the code that calls LOG10 is compiled with the /float=g_float qualifier. When compiled with the default floating point format, it returns -HUGE_VAL as expected. This problem has been fixed. Images Affected: - [SYSLIB]DPML$SHR.EXE QuIX case(s) reporting this problem: QXCM1001119014 5.2.86.2 Workaround: None. 5.2.87 System crash occurs while processing I/Os due to a faulty Emulex FC HBA 5.2.87.1 Problem Description: A system crash is observed while processing I/Os due to a faulty Emulex Fibre Channel (FC) Host Bus Adapter (HBA). This occurs because FC HBA sends the corrupt information to SYS$FGEDRIVER. While trying to process this corrupt data the driver BUGCHECKs. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001114729 5.2.87.2 Workaround: None. 5.2.88 System shutdown/reboot takes longer time when VMS_DUMP_DEV EFI parameter has invalid entries 5.2.88.1 Problem Description: Longer shutdown/reboot time observed if the VMS_DUMP_DEV contains invalid or non-existent entries with a lot of PGQBT-W-LINK_WAIT messages displayed. During shutdown OpenVMS flushes the error log buffers to the system disk through the initial boot path. If the system disk is unavailable due to a path failure then the system tries the flush operation via alternate paths/devices mentioned in the VMS_DUMP_DEV list. In each failure the boot driver waits for up to 60 seconds for each path to respond (link up). This is retried three times. If there are many invalid entries in the VMS_DUMP_DEV list, considerable delay is seen. The fix provided reduces this delay. Images Affected: - [SYS$LDR]SYS$PGQBTDRIVER.EXE - [SYSEXE]IPB.EXE QuIX case(s) reporting this problem: QXCM1001070615 5.2.88.2 Workaround: None. 5.2.89 Compiling application or programs written in C which call decc$get_channel() API function reports an informational message 5.2.89.1 Problem Description: The declaration for decc$get_channel() API function is not included in the DECC$RTLDEF.TLB file. Due to this, the compiler reports the following informational message: %CC-I-IMPLICITFUNC, In this statement, the identifier "decc$get_channel" is implicitly declared as a function. This problem has been fixed. Images Affected: - [SYSLIB]DECC$RTLDEF.TLB QuIX case(s) reporting this problem: None. 5.2.89.2 Workaround: None. 5.2.90 Creating more than 32 K global sections returns SECTBLFUL error message 5.2.90.1 Problem Description: Creating more than 32 K global section descriptors results in the following error message, though the GBLSECTIONS SYSGEN parameter is set to a higher value: -SYSTEM-F-SECTBLFUL, process or global section table is full This problem has been fixed. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB QuIX case(s) reporting this problem: QXCM1001121692 5.2.90.2 Workaround: None. 5.2.91 Unable to set Jumbo frames for Broadcom 10 Gigabit devices through LANCP utility 5.2.91.1 Problem Description: Failed to allocate Jumbo frame buffers on Broadcom 10 Gigabit devices through LANCP utility. Example: LANCP> set dev /JUMBO This problem has been fixed. Images Affected: - [SYS$LDR]SYS$ER57711.EXE - [SYS$LDR]SYS$ER57711_MON.EXE - [SYS$LDR]SYS$EW57711.EXE - [SYS$LDR]SYS$Ew57711_MON.EXE QuIX case(s) reporting this problem None. 5.2.91.2 Workaround: Jumbo frame buffers can be enabled system wide by setting LAN_FLAGS SYSGEN parameter. Example: SYSGEN> SET LAN_FLAGS 64 SYSGEN> WRITE CURRENT SYSGEN> WRITE ACTIVE 5.2.92 System hangs during boot while joining the cluster 5.2.92.1 Problem Description: Under rare situations, during boot, the quorum file on a cluster is unreachable. Due to this, a system hang is observed after the following messages: %VMScluster-I-LOADSECDB, loading the cluster security database %SYSINIT-I- waiting to form or join an OpenVMS Cluster %MSCPLOAD-I-CONFIGSCAN, enabled automatic disk serving This problem has been fixed. Images Affected: - [SYSEXE]IPB.EXE - [SYSEXE]IPB_NOXDELTA.EXE - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSINIT.EXE - [SYS$LDR]EXEC_INIT.STB - [SYS$LDR]EXEC_INIT.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB QuIX case(s) reporting this problem: QXCM1000909763, QXCM1000985853, QXCM1001131653 5.2.92.2 Workaround: None. 5.2.93 Unable to create logical LANs with Jumbo frames when 10 Gigabit Broadcom devices are involved 5.2.93.1 Problem Description: The Broadcom 10 Gigabit devices support different Jumbo frame buffer size compared to other drivers. Due to this discrepancy, it fails to create logical LANs with Jumbo frames when Broadcom 10 Gigabit devices are part of the fail set devices (physical devices). This problem has been fixed. Images Affected: - [SYS$LDR]SYS$LLDRIVER.EXE QuIX case(s) reporting this problem: None. 5.2.93.2 Workaround: None. 5.2.94 System crash with PROCGONE bugcheck during boot 5.2.94.1 Problem Description: During the boot, absence of SYS$ERRLOG.DMP file results in a system crash with PROCGONE bugcheck after the following messages: "%SYSINIT-W- SYS$ERRLOG.DMP not found - system initialization continuing... %SYSINIT-W- error log buffers not saved" This problem has been fixed. Images Affected: - [SYSEXE]SYSINIT.EXE QuIX case(s) reporting this problem: QXCM1001083437 5.2.94.2 Workaround: None. 5.2.95 Incorrect sign extension of negative literals 5.2.95.1 Problem Description: The sign extension of 32-bits negative literals are incorrectly performed by the MACRO compiler. Due to this, a 32-bit negative literal is treated as a large positive value by the compiler. This problem has been fixed. Images Affected: - [SYSEXE]MACRO.EXE QuIX case(s) reporting this problem: None. 5.2.95.2 Workaround: None. 5.2.96 OpenVMS CRTL setitimer() API function incorrect behavior 5.2.96.1 Problem Description: The following problems are observed: 1) The OpenVMS C RTL setitimer() API function does not clear the values returned in the third argument (ovalue), when the values passed in the second argument are all zeros. 2) setitimer() API function does not disable a timer after next expiration, when the value of it_interval is set to ZERO. These problems have been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE QuIX case(s) reporting this problem: QXCM1001115136 5.2.96.2 Workaround: None. 5.2.97 The OpenVMS C RTL setenv() API function causes memory leak when called frequently to set the same environment variable 5.2.97.1 Problem Description: The OpenVMS C RTL setenv() API function allocates memory instead of reallocating for an existing environment variable. Due to this, setenv() API function causes a memory leak. Images Affected: - [SYSLIB]DECC$SHR.EXE QuIX case(s) reporting this problem: QXCM1001106354 5.2.97.2 Workaround: None. 5.2.98 The SORT command does not display the status of intermediate warning messages 5.2.98.1 Problem Description: In certain scenarios, the return status of the SORT command does not display the status of intermediate warning messages, if the SORT command is successful. This problem has been fixed. With this fix, by default the return status of SORT command reflects the status of warning messages even if the SORT command is successful. If the $STATUS variable must reflect the status of SORT on completion of the operation irrespective of intermediate warning messages, you must define a system wide logical SORT_RETURN_FINAL_STATUS as shown in the following: $ DEFINE/SYSTEM SORT_RETURN_FINAL_STATUS 1 Images Affected: - [SYSEXE]SORTMERGE.EXE QuIX case(s) reporting this problem: QXCM1001107781 5.2.98.2 Workaround: None. 5.2.99 The PRINT USING routine does not print or display the correct QUAD value 5.2.99.1 Problem Description: The QUAD variable value is not displayed correctly when used with PRINT USING routine. This problem has been fixed. Images Affected: - [SYSLIB]DEC$BASRTL.EXE QuIX case(s) reporting this problem: QXCM1001086149 5.2.99.2 Workaround: None. 5.2.100 UETP miscalculates load on large memory systems 5.2.100.1 Problem Description: The User Environment Test Package (UETP) command procedure accepts "number of simulated user loads" as the input from the user. On large memory systems the default value for the "number of simulated user loads" can be miscalculated. This problem has been fixed. Images Affected: - [SYSTEST]UETINIT00.EXE QuIX case(s) reporting this problem: None. 5.2.100.2 Workaround: None. 5.2.101 Multiple mount verification messages on SATA DVD 5.2.101.1 Problem Description: Multiple mount verification are seen on SATA DVD drive connected to a rx2800 i2 server. This causes slow boot and takes long time to install. Also can cause failures when burning media. This is due to a race condition in driver ISR, thereby interrupts goes unnoticed causing I/O to timeout. This fix also includes some performance improvements. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PKDDRIVER.EXE QuIX case(s) reporting this problem: None. 5.2.101.2 Workaround: Decrease the number of active threads (CPUs) in the server to less than or equal to eight. 5.2.102 The creation of process dumps gives additional WARNING messages 5.2.102.1 Problem Description: While creating the process dump an additional warning message may be seen with the VMS84I_UPDATE-V0500 kit installed. However, the process dump gets created. Example: $ SET PROCESS/DUMP $ LIBRARIAN/EXTRACT=$PCBDEF/OUTPUT=nl: SYS$LIBRARY:LIM.MLB %LIBRAR-F-OPENIN, error opening SYS$COMMON:[SYSLIB]LIM.MLB; as input -RMS-E-FNF, file not found %PROCDUMP-W-BADLOGIC, internal logic error detected at PC 00000000.7B5E2DF0 -PROCDUMP-E-NOREAD, no access to location 00000000.7B5061C8, length 00000000.00000008 -PROCDUMP-E-REQUESTED, requested from PC 00000000.7B5E0FC0 This problem has been fixed. Images Affected: - [SYSLIB]IMGDMP.EXE QuIX case(s) reporting this problem: None. 5.2.102.2 Workaround: None. 5.2.103 Multiple problems in ACME VMS agent 5.2.103.1 Problem Description: The following problems are observed with ACME VMS agent: 1) Unable to use PointSecure system detective product, as ACME_SERVER process crashes and restarts occasionally with the following error message: CONSTRAINT_ERROR : acmevacmevrequeprivifromwqerequesprofil.adb:293 range check failed 2) When an image installed with all privilege calls SYS$ACM() system service, the ACME_SERVER process crashes and restarts. 3) The following ACME-LDAP error message is displayed for every 30 seconds: -LOGIN-F-TEXT, FINISH_PROCESSING_AUDIT ACMEVMS_SECURITY_AUDIT discarded physical terminal information This was increasing the size of the log file though not impacting the successful execution of the ACME-LDAP service. These problems have been fixed. Images Affected: - [SYSLIB]VMS$VMS_ACMESHR.EXE QuIX case(s) reporting this problem: QXCM1001038077, QXCM1001080138, QXCM1001065868 5.2.103.2 Workaround: None. 5.2.104 Login terminal name field width is only seven characters 5.2.104.1 Problem Description: If the associated cloned device names (or terminal device names) are more than seven bytes long, new login sessions are not allocated with license units. This problem has been fixed. Images Affected: - [SYSEXE]LOGINOUT.EXE (ACMELOGIN,LOGIN) - [SYSEXE]SETP0.EXE (ACMELOGIN,LOGIN) QuIX case(s) reporting this problem: None. 5.2.104.2 Workaround: None. 5.2.105 Potential loop while doing floating point software assist 5.2.105.1 Problem Description: The code handling floating point software assist can potentially loop longer than expected when attempting to load the required page into memory. This problem has been fixed. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB QuIX case(s) reporting this problem: None. 5.2.105.2 Workaround: None. 5.2.106 Improper handling of case-sensitive logicals in logical name cache 5.2.106.1 Problem Description: There is a limitation in the way case-sensitive logicals are cached and searched in the logical name cache. This update kit fixes this issue of handling case-sensitive logicals. This problem has been fixed. Images Affected: - [SYS$LDR]LOGICAL_NAMES.EXE - [SYS$LDR]LOGICAL_NAMES.STB QuIX case(s) reporting this problem: QXCM1001046367, QXCM1001123051 5.2.106.2 Workaround: None. 5.2.107 Process crash while executing the LNM UNLOAD SDA command 5.2.107.1 Problem Description: A process crash occurs while executing a logical name tracing unload command on SDA using LNM UNLOAD. This crash occurs only if the LNM tracing collection is started through LNM START COLLECT command and LNM UNLOAD command is executed before LNM STOP COLLECT. This problem has been fixed. Images Affected: - [SYSLIB]LNM$SDA.EXE QuIX case(s) reporting this problem: QXCM1001094420 5.2.107.2 Workaround: None. 5.2.108 Intermittent process crashes in applications that use KP services in a threaded application 5.2.108.1 Problem Description: When KP services are used in an threaded application, Thread Pointer(R13) register gets corrupted which results in an ACCVIO while trying to access Thread Environment Block (TEB). This problem has been fixed. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB QuIX case(s) reporting this problem: QXCM1001038522, QXCM1001069944, QXCM1001106858, QXCM1001125907 5.2.108.2 Workaround: None. 5.2.109 INVEXCEPTN in EXE$PAL_IMB_PHYS trying to flush the cache 5.2.109.1 Problem Description: Possible INVEXCEPTN in EXE$PAL_IMB_PHYS trying to flush the cache while setting page protection. Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL CPU Type: HP rx8640 (1.60GHz/12.0MB) VMS Version: V8.3-1H1 Current Process: _RTA1: Current Image: Failing PC: FFFFFFFF.8011A161 EXE$PAL_IMB_PHYS_C+00151 Failing PS: 00000000.00000809 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 24-NOV-2010 15:25:51.74) Offset: 0009A161 This problem has been fixed. Images Affected: - [SYSEXE]IPB.EXE - [SYSEXE]SYSBOOT.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB QuIX case(s) reporting this problem: QXCM1001120757 5.2.109.2 Workaround: None. 5.2.110 Avoid prompt to enter system time during reboot 5.2.110.1 Problem Description: If an OpenVMS Integrity server system is booted and the time stored in one of its data cells is five years or more in the past, the system prompts the operator to enter the correct date and time. This can delay boots and reboots since operator intervention is required. This update kit avoids the operator intervention to enter the system time during reboot. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB QuIX case(s) reporting this problem: None. 5.2.110.2 Workaround: None. 5.2.111 ACME_SERVER process locks OPA0: console 5.2.111.1 Problem Description: With the SYS$ACM enabled LOGINOUT.EXE, messages written from a VMS$PASSWORD policy to SYS$OUTPUT redirects to OPA0:console. As a result, ACME_SERVER process takes ownership of the console and the user is unable to type information on the console. This results in a console hang. Now ACME_SERVER process is created with output directed to a file and not to OPA0:console. As a result, the output messages are now logged into SYS$MANAGER:ACME_SERVER_CONSOLE_OUTPUT.LOG. This problem has been fixed. Images Affected: - [SYSEXE]SETSHOSERVER.EXE - [SYSEXE]ACME_SERVER.EXE QuIX case(s) reporting this problem: QXCM1001062894 5.2.111.2 Workaround: None. 5.2.112 Audit records differ from DIR/FILE_ID command 5.2.112.1 Problem Description: File ID display in Audit records does not match the DIR/FILE_ID command. Example: $ DIR AB20000.TXT/FILE_ID AB20000.TXT;1 (116471,36,0) >> Hexa (1C6F7,24,0) However, the OPCOM/AUDIT record shows a different File ID: Auditable event: Object deletion Image name: $10$DKB200:[SYS0.SYSCOMMON.][SYSEXE]DELETE.EXE Object class name: FILE File name: _$10$DKA0:[000000]AB20000.TXT;1 File ID: (50935,36,256) >> (C6F7,24,100) This problem has been fixed. Images Affected: - [SYSLIB]VMS$FORMAT_AUDIT_SYSTEM.EXE QuIX case(s) reporting this problem: QXCM1001100900 5.2.112.2 Workaround: None. 5.2.113 Link state change issue with the LOM on BL860c server blades and BL870c server blades 5.2.113.1 Problem Description: Driver unable to determine the correct link state for LOM devices of BL860c server blades and BL870c server blades when working with pass through interconnect modules. Now, driver identifies the link state change correctly for LOM devices. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EW5700.EXE - [SYS$LDR]SYS$EW5700_MON.EXE QuIX case(s) reporting this problem: QXCM1000996763, QXCM1000980925, QXCM1001083017 5.2.113.2 Workaround: None. 5.2.114 SHOW PROCESS/CONTINUOUS command can cause unexpected behavior 5.2.114.1 Problem Description: Under rare circumstances, SHOW PROCESS/CONTINUOUS command can cause unexpected behavior on OpenVMS Integrity server systems. This problem has been fixed. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB QuIX case(s) reporting this problem: QXCM1001078269, QXCM1001080391 5.2.114.2 Workaround: None. 5.3 Problems addressed in Firmware releases 5.3.1 Inability to boot using the "Internal Bootable DVD" EFI boot option on rx2800 i2 servers 5.3.1.1 Problem Description: On rx2800 i2 servers, an attempt to boot the system using the internal DVD boot option from the boot manager fails. The following error message is displayed: Booting Internal Bootable DVD Boot Failed Press any key to continue... This problem has been fixed in the firmware version S26.06, for rx2800 i2 servers. QuIX case(s) reporting this problem: None. 5.3.1.2 Workaround: None. 5.3.2 Tape drive connected to the HP Smart Array P812 controller hangs on rx2800 i2 servers 5.3.2.1 Problem Description: If a tape drive is connected to HP Smart Array P812 controller, rx2800 i2 server hangs in EFI shell. This problem has been fixed in P812 firmware version 5.06. QuIX case(s) reporting this problem: None. 5.3.2.2 Workaround: None. 6 CONSOLIDATION OF PREVIOUSLY RELEASED PATCH KITS FOR OPENVMS FOR INTEGRITY SERVERS V8.4 - The VMS84I_LOGINPLUS patch kit is consolidated in this update Kit. The update kit will automatically detect and replace the sys$acm / non-sys$acm images of LOGINOUT.EXE and SETP0.EXE based on the existing configuration. No manual intervention is required. - The VMS84I_UPDATE-V0600 kit is a consolidation of previously released patch kits for OpenVMS for Integrity Servers V8.4. The kits included in the VMS84I_UPDATE-V0600 kit are: o VMS84I_DEBUG-V0100 o VMS84I_FIBRE_SCSI-V0100 o VMS84I_FIBRE_SCSI-V0200 o VMS84I_IPC-V0100 o VMS84I_LAN-V0100 o VMS84I_RMS-V0200 o VMS84I_LOGINPLUS-V0100 o VMS84I_SYSLOA-V0100 o VMS84I_DRIVER-V0100 o VMS84I_UPDATE-V0100 o VMS84I_UPDATE-V0200 o VMS84I_UPDATE-V0300 o VMS84I_UPDATE-V0500 Note that OpenVMS Patch kits are cumulative and that they contain all changes that have been released in earlier versions of the kit. The issues addressed by these kits can be found in the following Release Notes files after the kit is installed: o VMS84I_MUP-V0100.RELEASE_NOTES o VMS84I_MUP-V0200.RELEASE_NOTES o VMS84I_DEBUG-V0100.RELEASE_NOTES o VMS84I_DRIVER-V0100.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0100.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0200.RELEASE_NOTES o VMS84I_IPC-V0100.RELEASE_NOTES o VMS84I_LAN-V0100.RELEASE_NOTES o VMS84I_LOGINPLUS-V0100.RELEASE_NOTES o VMS84I_RMS-V0100.RELEASE_NOTES o VMS84I_RMS-V0200.RELEASE_NOTES o VMS84I_SYS-V0100.RELEASE_NOTES o VMS84I_SYSLOA-V0100.RELEASE_NOTES o VMS84I_UPDATE-V0100.RELEASE_NOTES o VMS84I_UPDATE-V0200.RELEASE_NOTES o VMS84I_UPDATE-V0300.RELEASE_NOTES o VMS84I_UPDATE-V0500.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=V6.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_UPDATE /VERSION=V6.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=V6.0 /SELECT = *.RELEASE_NOTES 7 KNOWN PROBLEMS AND LIMITATIONS This section describes the known problems and limitations in this patch kit. 0 On P812 SAS controller, when SAS cable is unplugged or plugged in to a running system, path failover or device discovery does not happen. The SAS controller hangs and a system reboot is required. 0 LAN boot driver support is not available for 82575EB and 57711E based I/O cards LAN boot driver support is not available for IO cards based on 82575E and 57711 chipsets. "InfoServer booting" and "Cluster satellite booting" can be performed only through "Memory disk boot method." 0 LUN migration or expansion using MSA$UTIL might fail when a smaller capacity disk is added to a disk group. This may be because free space is not available in the newly added disk. Workaround: Use same or higher capacity disk for LUN migration or expansion. 0 MSA$UTIL fails to expand or extend a LUN to a size greater than 1 TB. 0 LUN migration and expansion of RAID 50 or RAID 60 unit is not supported by MSA$UTIL. 0 When RAID 50 unit with spare disk is created on top of an RAID 60 unit, an unused partition is created between these two units. 0 On BL860c server blades or BL870c server blades, VC Flex10 module (455880-B21) is not supported with the LAN-on-motherboard (LOM) ports. 0 OpenVMS supports boot devices up to 2 TB in size. However, ensure that the storage device is supported with OpenVMS and that the storage and associated HBA is installed with the latest firmware versions. 0 RMS $PARSE service with wildcards and ellipsis fails with an error message RMS $PARSE service with wildcards and ellipsis on a directory name having the format ^..DIR, fails with the following error message: -RMS-E-DNF, directory not found Where, name1 and name2 are part of the directory name before and after the special character dot (.) which is preceded by the escape character (^). This problem is observed on other utilities, such as DIR, TYPE, and so on, or applications that internally call SYS$PARSE system service. In this scenario, where the directory is in the ^..DIR format, RMS $PARSE fails only if it is called with a directory file specification that has one or more characters of between the two wildcards. This problem is not observed when the directory file specification passed to $PARSE, containing one or more characters of name1 between the two wildcards. If the directory name is of the format "^.^..DIR", the problem is observed only for one or more characters of and not for or . Example: "DIR_TEST^.WITH_DOT.DIR" is the directory name created under SYS$SYSDEVICE:[TEST]. Where, name1 is "DIR_TEST" and name2 is "WITH_DOT". $ SET PROCESS/PARSE_STYLE=EXTENDED $ CREATE/DIR [.DIR_TEST^.WITH_DOT]/LOG %CREATE-I-CREATED, SYS$SYSDEVICE:[TEST.DIR_TEST^.WITH_DOT] created $ 1) Using DIRECTORY command: $ DIR [.*TEST*...] %DIRECT-W-NOFILES, no files found $ $ DIR [.*W*...] %DIRECT-E-OPENIN, error opening SYS$SYSDEVICE:[TEST.*W*...]*.*;* as input -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ 2) Using DELETE command: $ CREATE [.DIR_TEST^.WITH_DOT]A.TXT Hello Exit $ $ DELETE [.*W*...]A.TXT;* %DELETE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[TEST.*W*...]A.TXT;* -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ 3) Using COPY command: $ CREATE/DIR [.TARGET] $ COPY [.*W*...]A.TXT [.TARGET] %COPY-E-OPENIN, error opening SYS$SYSDEVICE:[TEST.*W*...]A.TXT; as input -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ 4) Using TYPE command: $ TYPE [.*W*...]A.TXT %TYPE-W-SEARCHFAIL, error searching for SYS$SYSDEVICE:[TEST.*W*...]A.TXT; -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ 0 XFC may not cache some files in cluster environment, this results in performance degradation. Under some circumstances, the XFC might stop caching some files, such that all the I/O's are performed directly with the file on the disk instead of using the memory cache for that file. When these files are used, the performance is lower than expected. It has been observed that the following two scenarios might trigger this behavior: 1) One cluster node performs frequent reads and writes on a file. A second node opens the same file and performs a write operation but no further read or write operations, and leaves the file open. 2) One cluster node performs frequent reads and writes on a file. A second node opens the file and does only infrequent read operations, leaving the file open. Workaround: If required, close the file and reopen it periodically, or perform more frequent read operations on the file from the less active nodes. The XFC needs at least two read I/Os from that node to modify its locks and start caching the file again. 0 Unable to create a directory ^.DIR.DIR when another directory .DIR already exists If there is a directory .DIR in a user directory, and if you try to create another directory ^.DIR.DIR in the same user directory, it fails with the following error message: %CREATE-I-EXISTS This problem is observed only on ODS-5 disk. Example: $! On an ODS-5 disk $ SET PROCESS/PARSE_STYLE=EXTENDED $ CREATE/DIR [.FOO]/LOG %CREATE-I-CREATED, $10$DKA0:[TEST.FOO] created $! Now let’s try to create another directory $ CREATE/DIR [.FOO^.DIR]/LOG %CREATE-I-EXISTS, [.FOO^.DIR] already exists Workaround: Create a temporary directory and rename the directory with the desired name. Example: $! On an ODS-5 disk $ SET PROC/PARSE_STYLE=EXTENDED $ CREATE/DIR [.FOO]/LOG %CREATE-I-CREATED, $10$DKA0:[TEST.FOO] created $! Now create a temporary directory $ CREATE/DIR [.TEMP]/LOG %CREATE-I-CREATED, $10$DKA0:[TEST.TEMP] created $! Now rename it $ RENAME $10$DKA0:[TEST]TEMP.DIR $10$DKA0:[TEST]FOO^.DIR.DIR/LOG %RENAME-I-RENAMED, $10$DKA0:[TEST]TEMP.DIR;1 renamed to $10$DKA0:[TEST]FOO^.DIR.DIR;1 0 To set or modify the security profile of the SYMLINK file, use the SET SECURITY/SYMLINK DCL command. If the file named in the SET SECURITY command is a symlink file, this command operates on the symlink file itself. To set or modify the security profile of the target file, use the SET SECURITY/SYMLINK DCL command on the target file. Example: $ CREATE MDA500:[TEST1]A.TXT HELLO WORLD Exit $ DIR MDA500:[TEST1]A.TXT Directory MDA500:[TEST1] A.TXT;1 Total of 1 file. $ $ CREATE/SYMLINK="/MDA500/TEST1/A.TXT" MDA600:[TEST1]N.LNK $ $ SHOW SEC MDA600:[TEST1]N.LNK MDA600:[TEST1]N.LNK;1 object of class FILE Owner: [SYSTEM] Protection: (System: RWED, Owner: RWED, Group: RE, World) Access Control List: $ $ SHOW SEC MDA500:[TEST1]A.TXT MDA500:[TEST1]A.TXT;1 object of class FILE Owner: [SYSTEM] Protection: (System: RWED, Owner: RWED, Group: RE, World) Access Control List: $ $ !The following command sets the security profile of the SYMLINK file $ SET SECU/PROT=(G:R,W:R) MDA600:[TEST1]N.LNK $ SHOW SEC MDA500:[TEST1]A.TXT MDA500:[TEST1]A.TXT;1 object of class FILE Owner: [SYSTEM] Protection: (System: RWED, Owner: RWED, Group: RE, World) Access Control List: $ $ SHOW SEC MDA600:[TEST1]N.LNK MDA600:[TEST1]N.LNK;1 object of class FILE Owner: [SYSTEM] Protection: (System: RWED, Owner: RWED, Group: R, World: R) Access Control List: $ $ !The following command sets the security profile of the target file $ SET SECU/PROT=(G:RW,W:R) MDA500:[TEST1]A.TXT;1 MDA500:[TEST1]A.TXT;1 object of class FILE Owner: [SYSTEM] Protection: (System: RWED, Owner: RWED, Group: RW, World: R) Access Control List: $ 0 Unable to create a SYMLINK even after the SYMLINK is deleted After a SYMLINK is deleted from a directory, an attempt to create a SYMLINK with the same name in that directory, by that same process, within a time period set by RMS_PATH_TMO SYSGEN parameter, fails with "-RMS-E-FEX" error. Example: $ SET PROCESS/PARSE_STYLE=EXTENDED/CASE=BLIND $ CREATE/SYMLINK="/DKA0/TEST/FOO.DAT" Link.lnk $ DIR [.Link^.lnk] ! During this SYMLINK access, it is added to RMS path cache. $ DELETE Link.lnk;* $ CREATE/SYMLINK="/ DKA0/TEST/FOO.DAT" Link.lnk ! This creation attempt fails with "-RMS-E-FEX, file already exists, not superseded" as SYMLINK is found in the path cache $ WAIT 00:00:10 ! In this case the RMS_PATH_TMO = 10 seconds. After waiting for 10 seconds, you will be able to create SYMLINKS. $ CREATE/SYMLINK="/ DKA0/TEST/FOO.DAT" Link.lnk ! It works $ The following section describes how to set RMS path cache timeout value. How to set RMS path cache timeout value: ---------------------------------------- You can modify the RMS path cache timeout value by using the $ SET RMS/PATH_TIMEOUT= DCL command or by changing the RMS_PATH_TMO SYSGEN dynamic parameter. Some special values of RMS_PATH_TMO SYSGEN parameter: 1 = do not keep cache entries at all; it is equivalent of setting a time out value of 0 seconds. -1 = keep cache entries forever, so the time out value is infinity. Workaround: Disable RMS path cache for SYMLINKS. To disable, run the one of the following commands: $ SET RMS/PATH_TIMEOUT = 1 ! Use this to change timeout value only for the process Or $ SET RMS/PATH_TIMEOUT = 1/SYSTEM ! Use this to change timeout value for the system Or $ MCR SYSGEN SYSGEN> SET RMS_PATH_TMO 1 SYSGEN> WRITE CURRENT SYSGEN> WRITE ACTIVE SYSGEN>EXIT 0 On large memory systems, while executing some DCL commands and SDA commands, memory related statistics displays "*******" instead of actual values. Example: The MONITOR PAGE command displays "*******" on large memory system, when its value exceeds the permissible column width as below: $ MONITOR PAGE/RECORD=MONITOR_PAGE.DAT/NODISPLAY/END="+00:01:00" $ MONITOR PAGE /INPUT=MONITOR_PAGE.DAT /SUMMARY OpenVMS Monitor Utility PAGE MANAGEMENT STATISTICS on node NODE8S 8-SEP-2011 15:55:21.17 CUR AVE MIN MAX Page Fault Rate 0.00 0.01 0.00 0.33 Page Read Rate 0.00 0.00 0.00 0.00 Page Read I/O Rate 0.00 0.00 0.00 0.00 Page Write Rate 0.00 0.00 0.00 0.00 Page Write I/O Rate 0.00 0.00 0.00 0.00 Free List Fault Rate 0.00 0.01 0.00 0.33 Modified List Fault Rate 0.00 0.00 0.00 0.00 Demand Zero Fault Rate 0.00 0.00 0.00 0.00 Global Valid Fault Rate 0.00 0.00 0.00 0.00 Wrt In Progress Fault Rate 0.00 0.00 0.00 0.00 System Fault Rate 0.00 0.00 0.00 0.00 Free List Size *******.00 *******.40 *******.00 *******.00 Modified List Size 304.00 304.00 304.00 304.00 PLAYBACK SUMMARIZING $ 0 SYMLINK files with file name extension ".DIR" (or ".dir") are not supported by the OpenVMS file system and utilities In OpenVMS, the target of a SYMLINK can be an ordinary file or a directory file. However, the name of the SYMLINK itself should not have ".DIR" as the extension. Examples: 1) SYMLINK name with ".DIR" extension not supported $ CREATE NOT_SUPPORTED_SYMLINK.DIR /SYMLINK="TARGET_DIRECTORY/" In this example, the command creates a symbolic link named "NOT_SUPPORTED_SYMLINK.DIR", pointing to a directory named "TARGET_DIRECTORY". The name of the symbolic link "NOT_SUPPORTED_SYMLINK.DIR" has the extension ".DIR". Therefore, it is not supported. While the user cannot see any error message upon attempting to create such a SYMLINK, subsequent directory operations may give inconsistent results. 2) SYMLILNK created from bash shell with .DIR in its name Note: A SYMLINK with .DIR in its name, created in bash shell, displays the ^.DIR in its name when listed in DCL. $ DEFINE DECC$POSIX_COMPLIANT_PATHNAMES 1 GNV_bash$ ln -s e.dir LINK.DIR GNV_bash$ exit $ DIR LINK^.DIR/LINK LINK^.DIR.;1 -> e.dir 1 $ In this example, the symbolic file named "LINK.DIR" is created. However, this file name is created from the GNV shell. The actual file name created in the OpenVMS file system is a non-directory file named "LINK.DIR.;1". Upon listing this file in DCL, the name of the symbolic link shows up as ^.DIR As the SYMLINK file created does not have a ".DIR" extension, the symbolic link "LINK.DIR.;1" is supported. 3) SYMLINK with ".DIR" in its file name component is supported as long as the file name extension is not ".DIR" $ CREATE LINK^.DIR /SYMLINK="FOO.DAT" $ DIR/LINK Directory SYS$SYSDEVICE:[EXAMPLES] FOO.DAT;1 LINK^.DIR.;1 -> FOO.DAT;1 Total of 2 files. 8 DOCUMENTATION ERRATA This section describes corrections to the various manuals in the OpenVMS documentation set. 0 In VMS84I_UPDATE-V0200 release notes, section 5.3, Hardware support: 1) Table 5-2 Hardware supported on the BL8x0c i2 server blades, the following row has to be ignored: Table 5-2 Hardware supported on the BL8x0c i2 server blades =========================================================================== Adapter Adapter Description Suggested Suggested Compatible FW EFI Servers =========================================================================== Fibre Channel --------------------------------------------------------------------------- 456972-B21 8 Gb FC Mezz Emulex 1.11x7 4.00a8 BL8x0c i2 server blades --------------------------------------------------------------------------- 2) The below note should follow the "Table 5-2 Hardware supported on the BL8x0c i2 server blades": Note: 8 Gb FC Mezz Emulex (456972-B21) is not supported on OpenVMS. 0 In VMS84I_UPDATE-V0300 release notes, section 5.1.2, Broadcom 57711E support, must read: It is mandatory to install the VMS84I_UPDATE-V0300 update kit to support the Broadcom 57711E based dual-port LAN device (LOM or NC532m mezzanine card). 0 In VMS84I_RMS-V0200 release notes, add the following note in section 5.2, Problem Description: Note: Usage of Multi-Block Count (MBC) value greater than 127 is supported only in OpenVMS V8.4 with this patch onwards. If you intend to use a MBC value of more than 127 blocks to open a file in shared mode in a VMS cluster, you must apply this patch on all nodes in the cluster where these files are shared. For OpenVMS versions prior to V8.4, MBC value greater than 127 is not supported. In mixed version clusters install the following RMS/SYS TIMAs which ensure that attempts to access a file opened on a V8.4 node, from a non-v8.4 node, returns an error without corrupting the file. - VMS732_RMS-V0600 - VMS82A_RMS-V0400 - VMS821I_RMS-V0500 - VMS83A_RMS-V1200 and VMS83A_SYS-V2000 - VMS83I_RMS-V1000 and VMS83I_SYS-V1700 - VMS831H1I_RMS-V0400 and VMS831H1I_SYS-V1400 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 23-MAY-2011 12:08:23.55 Overall Image Checksum: 28484EA0 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 5-MAY-2011 18:00:24.32 Overall Image Checksum: 3AF272ED 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:46.21 Overall Image Checksum: AC6651C3 o [SYSLIB]CONVSHR.EXE (new image) Image Identification Information Image name: "CONVSHR" image file identification: "X1-012" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:48:56.29 Overall Image Checksum: 1C0A6E6F 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:03.31 Overall Image Checksum: 46E9F9D 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 24-JUN-2011 13:57:01.98 Overall Image Checksum: DEEBD9DD o [SYSMSG]SYSMSG.EXE (new image) Image Identification Information Image name: "SYSMSG" image file identification: "X-9" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:39.02 Overall Image Checksum: ACCFED0D o [SYSLIB]DEBUGSHR.EXE (new image) Image Identification Information Image name: "DEBUGSHR" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:39.26 Overall Image Checksum: F52B8527 o [SYS$LDR]FLT$DEBUG.EXE (new image) Image Identification Information Image name: "FLT$DEBUG" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:25.81 Overall Image Checksum: F5FA9A1B o [SYSLIB]DEC$BASRTL.EXE (new image) Image Identification Information Image name: "DEC$BASRTL" image file identification: "V01-036" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:33:18.80 Overall Image Checksum: 75945AF4 o [SYSLIB]DEC$FORRTL.EXE (new image) Image Identification Information Image name: "DEC$FORRTL" image file identification: "V01-07.004" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:33:18.95 Overall Image Checksum: 2CD9D20A o [SYSLIB]DECC$SHR.EXE (new image) Image Identification Information Image name: "DECC$SHR" image file identification: "V8.4-00" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:31:10.95 Overall Image Checksum: 23C90C04 o [SYSLIB]DECC$SHRP.EXE (new image) Image Identification Information Image name: "DECC$SHRP" image file identification: "V8.4-00" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:31:09.83 Overall Image Checksum: DC2B36B2 o [SYSEXE]DIRECTORY.EXE (new image) Image Identification Information Image name: "DIRECTORY" image file identification: "X02-01" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:40.48 Overall Image Checksum: 4AE1F8CB 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-43" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:17:59.85 Overall Image Checksum: D895B3D8 o [SYSEXE]ERRFMT.EXE (new image) Image Identification Information Image name: "ERRFMT" image file identification: "X-22" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:17:48.49 Overall Image Checksum: 187A3735 o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information Image name: "EXCEPTION" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:19.89 Overall Image Checksum: 1C36B945 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information Image name: "EXCEPTION_MON" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:32.90 Overall Image Checksum: 1C36B945 o [SYS$LDR]EXEC_INIT.EXE (new image) Image Identification Information Image name: "EXEC_INIT" image file identification: "X-217" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:46.38 Overall Image Checksum: 84BCDED7 o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information Image name: "F11BXQP" image file identification: "XQP V84R_RE CD8" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:44.82 Overall Image Checksum: C14B3541 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 [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 [SYS$LDR]SYS$PGQDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PGQDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 24-JUN-2011 13:57:35.66 Overall Image Checksum: A54DB5B5 o [SYSLIB]IMGDMP.EXE (new image) Image Identification Information Image name: "IMGDMP" image file identification: "X-72" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:09.05 Overall Image Checksum: C088596 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:43.97 Overall Image Checksum: B788DDDA 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:03:54.62 Overall Image Checksum: FCC80C2A 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:46:29.49 Overall Image Checksum: BF0B22F7 o [SYS$LDR]LOCKING.EXE (new image) Image Identification Information Image name: "LOCKING" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:38.85 Overall Image Checksum: 7606F20E o [SYS$LDR]LOGICAL_NAMES.EXE (new image) Image Identification Information Image name: "LOGICAL_NAMES" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:08:43.01 Overall Image Checksum: 727B846C o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) Image Identification Information Image name: "MESSAGE_ROUTINES" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:08:58.31 Overall Image Checksum: 97EC7EFE o [SYSEXE]MACRO.EXE (new image) Image Identification Information Image name: "MACRO" image file identification: "50-120-5-50F9M" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:12.29 Overall Image Checksum: 85290640 o [SYSEXE]MSA$UTIL.EXE (new image) Image Identification Information Image name: "MSA$UTIL" image file identification: "X-29" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:09:33.66 Overall Image Checksum: FA109004 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:09:05.78 Overall Image Checksum: E73EB8B4 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:09:16.31 Overall Image Checksum: 19017B6 o [SYS$LDR]RMS.EXE (new image) Image Identification Information Image name: "RMS" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 10-JUN-2011 15:42:26.76 Overall Image Checksum: 299CADD7 o [SYS$LDR]SYS$HUBDRIVER.EXE (new image) Image Identification Information Image name: "SYS$HUBDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 5-MAY-2011 18:01:31.50 Overall Image Checksum: 195A57D o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information Image name: "SDA$SHARE" image file identification: "X-2" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 24-JUN-2011 13:57:24.77 Overall Image Checksum: 6A7E3671 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:19:11.04 Overall Image Checksum: 5E203817 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-28" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:58.79 Overall Image Checksum: 725C6BD1 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:22.07 Overall Image Checksum: 25CCC85E o [SYS$LDR]SYS$CTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$CTDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:18:12.31 Overall Image Checksum: 53813CDB 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 XCD0-J2I" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 24-JUN-2011 13:54:01.09 Overall Image Checksum: D69A04B4 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information Image name: "SYS$CLUSTER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:05.01 Overall Image Checksum: 66CA2B53 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:24.22 Overall Image Checksum: 234332F7 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:36.29 Overall Image Checksum: 644C8CD6 o [SYS$LDR]SYS$EI1000.EXE (new image) Image Identification Information Image name: "SYS$EI1000DRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 23-MAY-2011 12:08:36.08 Overall Image Checksum: 8171AD55 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-XCD8" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:45.47 Overall Image Checksum: E771736A 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:38.63 Overall Image Checksum: 7FDB1932 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:48.04 Overall Image Checksum: A1FCBA0E o [SYS$LDR]SYS$PGQBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PGQBTDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:48.71 Overall Image Checksum: A295000C 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:17:48.80 Overall Image Checksum: 4C36B79A 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:09.82 Overall Image Checksum: 1E291A07 o [SYS$LDR]SYS$UGDRIVER.EXE (new image) Image Identification Information Image name: "SYS$UGDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 23-MAY-2011 12:09:08.68 Overall Image Checksum: A71A64C6 o [SYS$LDR]SYS$SRDRIVER.EXE (new image) Image Identification Information Image name: "SYS$SRDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:18:12.96 Overall Image Checksum: 51BE4C5 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:04.98 Overall Image Checksum: 75138888 o [SYS$LDR]SYS$XFCACHE.EXE (new image) Image Identification Information Image name: "SYS$XFCACHE" image file identification: "V1.0" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:18:12.01 Overall Image Checksum: D551A831 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:18:13.80 Overall Image Checksum: 718A5C48 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information Image name: "SYSBOOT" image file identification: "X-154" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:05.02 Overall Image Checksum: AD982FD8 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-128" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:00.32 Overall Image Checksum: 2527AE0E 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 7-APR-2011 16:30:10.88 Overall Image Checksum: CA34AE4E 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:08:38.76 Overall Image Checksum: C6DB5732 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:08:53.36 Overall Image Checksum: 20CDC6DE 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-34" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:18:27.10 Overall Image Checksum: BDAC4346 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:08.44 Overall Image Checksum: 2F17FA11 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: "0100000004" linker identification: "Linker I02-38" Link Date/Time: 13-APR-2011 22:20:34.93 Overall Image Checksum: CE956F72 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:45.29 Overall Image Checksum: 1A8A0AFD 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 23-MAY-2011 12:08:52.91 Overall Image Checksum: 677D3AF6 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$EW57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:07.52 Overall Image Checksum: DA5F9B26 o [SYS$LDR]SYS$EW57711_MON.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:08.02 Overall Image Checksum: 739E1099 o [SYS$LDR]SYS$ER57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:07.52 Overall Image Checksum: DA5F9B26 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:08.02 Overall Image Checksum: 739E1099 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:03.58 Overall Image Checksum: 65AB664B o [SYSEXE]SETSHOSERVER.EXE (new image) Image Identification Information Image name: "SETSHOSERVER" image file identification: "X-2" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:35:25.04 Overall Image Checksum: FCB8703F 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:00.01 Overall Image Checksum: 5F828251 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:41.28 Overall Image Checksum: D889DCB5 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:22.48 Overall Image Checksum: 43731648 o [SYSLIB]DEBUG.EXE (new image) Image Identification Information Image name: "DEBUG" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-MAR-2011 12:19:07.10 Overall Image Checksum: 243C847E 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:26.42 Overall Image Checksum: 56EAC3D7 o [SYSEXE]MONITOR.EXE (new image) Image Identification Information Image name: "MONITOR" image file identification: "X-26" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:23.93 Overall Image Checksum: AD6E966A o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information Image name: "SYSMAN" image file identification:"X01-22" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:44.40 Overall Image Checksum: B1C5F015 o [SYSLIB]SMI$SHR.EXE (new image) Image Identification Information Image name: "SMI$SHR" image file identification:"X01-04" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:37.75 Overall Image Checksum: 2689105E o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information Image name: "SMISERVER" image file identification: "X01-15" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:46.89 Overall Image Checksum: 5EFEDD90 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: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:18:19.30 Overall Image Checksum: 20467B2F 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$MKDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:07.12 Overall Image Checksum: 178ABECA 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-095" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:16:47.68 Overall Image Checksum: FCE15062 o [SYSLIB]PTHREAD$DBGSHR.EXE (new image) Image Identification Information Image name: "PTHREAD$DBGSHR" image file identification: "V3.22-095" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:16:48.07 Overall Image Checksum: 7F892FAD 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 [SYSLIB]SDARMS$SHARE.EXE (new image) Image Identification Information Image name: "SDARMS$SHARE" image file identification: "X-7" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:23.59 Overall Image Checksum: 386DE222 o [SYSLIB]DBG$HA_KERNEL.EXE (new image) Image Identification Information Image name: "DBG$HA_KERNEL" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-MAR-2011 12:19:31.81 Overall Image Checksum: F15DFC01 o [SYSLIB]DBG$HA_MAIN.EXE (new image) Image Identification Information Image name: "DBG$HA_MAIN" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-MAR-2011 12:19:27.88 Overall Image Checksum: 26E710E6 o [SYSMSG]DBGTBKMSG.EXE (new image) Image Identification Information Image name: "DBGTBKMSG" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-MAR-2011 12:19:16.10 Overall Image Checksum: 18D626C7 o [SYSLIB]DEBUGSRVSHR.EXE (new image) Image Identification Information Image name: "DEBUGSRVSHR" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-MAR-2011 12:19:01.54 Overall Image Checksum: E8516CBD o [SYSLIB]DEBUGUISHR.EXE (new image) Image Identification Information Image name: "DEBUGUISHR" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-MAR-2011 12:19:16.02 Overall Image Checksum: A088619A o [SYSLIB]TRACE.EXE (new image) Image Identification Information Image name: "TRACE" image file identification: "V8.4-001" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-MAR-2011 12:16:03.43 Overall Image Checksum: C71D9CD2 o [SYS$LDR]SYS$EWXFRAME_MON.EXE (new image) Image Identification Information Image name: "SYS$EWXFRAMEDRIVER_MON" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 16:33:18.20 Overall Image Checksum: B64AAFCD o [SYS$LDR]SYS$EIDRIVER_MON.EXE (new image) Image Identification Information Image name: "SYS$EIDRIVER_MON" image file identification: "X-5" image file build identification: "0100000003" linker identification: "Linker I02-37" Link Date/Time: 7-SEP-2010 16:28:07.87 Overall Image Checksum: 86A65966 o [SYS$LDR]SYS$EW5700_MON.EXE (new image) Image Identification Information Image name: "SYS$EW5700DRIVER_MON" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:01.25 Overall Image Checksum: DFF14EE9 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 [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information Image name: "SYS$LAN" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time:3-JUN-2011 13:34:42.86 Overall Image Checksum: C7EEB01 o [SYSEXE]VERIFY.EXE (new image) Image Identification Information Image name: "VERIFY" image file identification: "X-28" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:02.44 Overall Image Checksum: 351D0CC5 o [SYSTEST]UETINIT00.EXE (new image) Image Identification Information Image name: "UETINIT00" image file identification: "X-48" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:24.84 Overall Image Checksum: 87C4672D o [SYSEXE]RECOVER.EXE (new image) Image Identification Information Image name: "RECOVER" image file identification: "X01-03" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:22.15 Overall Image Checksum: 39332EE o [SYSEXE]RMSREC$SERVER.EXE (new image) Image Identification Information Image name: "RMSREC$SERVER" image file identification: "X-13" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:24.38 Overall Image Checksum: F221F272 o [SYS$LDR]ERRORLOG.EXE (new image) Image Identification Information Image name: "ERRORLOG" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 3-JUN-2011 13:34:03.30 Overall Image Checksum: 4696DD8F o [SYS$LDR]SYS$EI1000_MON.EXE (new image) Image Identification Information Image name: "SYS$EI1000DRIVER_MON" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 23-MAY-2011 12:08:36.44 Overall Image Checksum: 8179D7D6 o [SYSEXE]AUTHORIZE.EXE(new image) Image Identification Information Image name: "AUTHORIZE" image file identification: "X-31" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:18:12.67 Overall Image Checksum: EC0031F o [SYSEXE]DELETE.EXE (new image) Image Identification Information Image name: "DELETE" image file identification: "X-05" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:40.37 Overall Image Checksum: 101CEC7D o [SYSEXE]DIFF.EXE (new image) Image Identification Information Image name: "DIFF" image file identification: "X-12" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:40.22 Overall Image Checksum: 2D361DA1 o [SYSEXE]MAIL.EXE (new image) Image Identification Information Image name: "MAIL" image file identification: "V1.06" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:53.38 Overall Image Checksum: 7A9C36D0 o [SYSEXE]MTAAACP.EXE (new image) Image Identification Information Image name: "MTAAACP" image file identification: "X-12" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:49:58.55 Overall Image Checksum: 97B1EE3E o [SYS$LDR]SYS$LLDRIVER.EXE (new image) Image Identification Information Image name: "SYS$LLDRIVER" image file identification: "X-5" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:08.84 Overall Image Checksum: 2F9ACFD8 o [SYSEXE]TYPE.EXE (new image) Image Identification Information Image name: "TYPE" image file identification: "X-28" image file build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 19-JUL-2011 16:50:54.13 Overall Image Checksum: 33BD59CC o [SYSLIB]DPML$SHR.EXE (new image) Image Identification Information Image name: "DPML$SHR" Image file identification: "T01-018" Image build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 1-JUL-2011 15:15:22.89 Overall Image Checksum: B2865D89 o [SYS$LDR]CNX$DEBUG.EXE (new image) Image Identification Information Image name: "CNX$DEBUG" Image file identification: "X-5" Image build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 8-AUG-2011 13:07:47.78 Overall Image Checksum: 7323B449 o [SYS$LDR]SYS$PKDDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKDDRIVER" Image file identification: "X-5" Image build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 9-SEP-2011 13:36:15.09 Overall Image Checksum: B514E52C o [SYSEXE]LOGINOUT.EXE - ACMELOGIN (new image) Image Identification Information Image name: "LOGINOUT" Image file identification: "LOGIN98 X-1" Image build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 17-MAY-2011 12:22:40.97 Overall Image Checksum: B3107B9C o [SYSEXE]SETP0.EXE - ACMELOGIN (new image) Image Identification Information Image name: "SETP0" Image file identification: "LOGIN98 X-1" Image build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 17-MAY-2011 12:24:10.26 Overall Image Checksum: FE72F890 o [SYSEXE]LOGINOUT.EXE - LOGIN (new image) Image Identification Information Image name: "LOGINOUT" Image file identification: "X-54" Image build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 17-MAY-2011 12:22:41.68 Overall Image Checksum: 6E9560D2 o [SYSEXE]SETP0.EXE - LOGIN (new image) Image Identification Information Image name: "SETP0" Image file identification: "X-3K2" Image build identification: "0100000004" linker identification: "Linker I02-37" Link Date/Time: 17-MAY-2011 12:24:10.47 Overall Image Checksum: 531E9801 o [SYS$LDR]SYS$PKDDRIVER.STB (new file) o [SYS$LDR]CNX$DEBUG.STB (new file) o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) o [SYS$LDR]SYS$LLDRIVER.STB (new file) o [SYSMSG]SYSMSG.STB (new file) o [SYSUPD]ACCOUNTIN.HLP (new file) o [SYS$LDR]SYS$UGDRIVER.STB (new file) o [SYS$LDR]SYS$LAN.STB (new file) o [SYS$LDR]SYS$EI1000.STB (new file) o [SYS$LDR]SYS$EW5700_MON.STB (new file) o [SYS$LDR]SYS$EIDRIVER_MON.STB (new file) 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 [SYSLIB]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 [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 [SYSHLP]ACME_DEV_README.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 (updated by DECC$RTLDEF.FOR_RELEASE) 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 [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) o [SYSHLP]LANCP$HELP.HLB (new file) o [SYS$LDR]RMSDEF.STB (new file) o [SYSHLP]DBG$HELP.HLB (new file) o [SYS$LDR]SYS$HUBDRIVER.STB (new file) o [SYSMGR]BOOT_OPTIONS.COM (new file) o [SYSEXE]I64VMS$PCSI_INSTALL.COM (new file) o [SYS$LDR]SYS$CTDRIVER.STB (new file) o [SYS$LDR]ERRORLOG.STB (new file) o [SYSHLP]SYSMANHELP.HLB (new file) o [SYS$LDR]SYS$EI1000_MON.STB (new file) o [SYS$LDR]LIBOTS.STB (new file) o [SYS$LDR]SMGSHR.STB (new file) o [SYS$LDR]SYS$PGQDRIVER.STB (new file) o [SYSHLP]SDA.HLB (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-V0600.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 avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT 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=V6.0 [/SOURCE=location of Kit] o De-assign the logical names assigned Example: A sample command file to install the VMS84I_UPDATE-V0600 kit: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_UPDATE/PRODUCER=HP/BASE=I64VMS/VER=V6.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 10.5 Special Installation Instructions In order to Install or perform any PRODUCT commands on the VMS84I_UPDATE-V0600 patch kit, you must have the VMS84I_PCSI-V0300 or later kit installed on your system. If you attempt to install from another OpenVMS system disk by using /REMOTE qualifier, you must have the latest PCSI kit installed on the source system disk. 11 COPYRIGHT AND DISCLAIMER: (C) Copyright 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.