**************************** ECO SUMMARY INFORMATION **************************** Release Date: 17-MAY-2007 **************************** ECO SUMMARY INFORMATION **************************** Release Date: 17-MAY-2007 Kit Name: DEC-AXPVMS-VMS83A_SYS-V0100--4.PCSI$COMPRESSED;2 Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 11815 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS83A_UPDATE-V200 or later Optional Kit Dependencies: None Checksums: VMS83A_SYS-V0100.ZIPEXE Checksum: 2425213999 DEC-AXPVMS-VMS83A_SYS-V0100--4.PCSI$COMPRESSED;2 Checksum: 1430638621 VMS83A_SYS-V0100.ZIPEXE MD5 Checksum: B2DD4F70C673BA5070A5AF53B3580C60 DEC-AXPVMS-VMS83A_SYS-V0100--4.PCSI$COMPRESSED;2 MD5 Checksum: 3BA59F56266D55EB7715C710296AD406 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_SYS-V0100 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. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS ALPHA V8.3 2.4 New functionality or new hardware support provided: Yes 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS83A_UPDATE-V200 Page 2 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 VMS83A_SYS-V0100 KIT 5.1 New functionality addressed in this kit 5.1.1 Add /SUMMARY[=PROCESS] Qualifier cldnote 6016 bishop 5.1.1.1 Functionality Description: A new /SUMMARY[=PROCESS] qualifier has been added to the SDA command SHOW PFN_DATA. SHOW PFN_DATA/SUMMARY produces a single-page summary of all pages on the system. Adding the PROCESS keyword causes SDA to generate two additional lists: one of all processes in the system showing the breakdown of its active pages; and one for all processes that have non-active pages (for example, pages on the modified list). Images Affected: - [SYSLIB]SDA$SHARE.EXE 5.1.2 Add /PAGES and /TOTALS Qualifiers to SDA SHOW SUMMARY Command cldnote 6016 bishop 5.1.2.1 Functionality Description: Two new qualifiers, /PAGES and /TOTALS, have been added to the SDA SHOW SUMMARY command. SHOW SUMMARY/PAGES will cause an additional line to be output, for each process, that gives a breakdown of the process-private and global pages in the process's working set. SHOW SUMMARY/TOTALS will output a summary of process and global pages for resident and nonresident processes, followed by a summary of the processes (or threads if /THREADS was also specified) in each scheduling state. /PAGES and/TOTALS may be specified together. Page 3 Images Affected: - [SYSLIB]SDA$SHARE.EXE 5.1.3 New $GETDVI Item Codes cldnote 6170 brooks 5.1.3.1 Functionality Description: The $GETDVI system service provides an item code (DVI$_MOUNTCNT) that returns the number of times a device is mounted on a single node (the use of the the /SHARE qualifier allows more than one mounter on a single node). There has been no way to get the clusterwide mount count for a device, from $GETDVI, despite the fact that $ SHOW DEVICE does correctly display the clusterwide mount count. This patch kit addresses this by adding the DVI$_MOUNTCNT_CLUSTER item code. The DVI$_ADAPTER_IDENT item code is also being added. These codes are only available for the SYS$GETDVI system service, and the F$GETDVI lexical function. They are not available for the LIB$GETDVI runtime library routine. The numeric value of DVI$_ADAPTER_IDENT is 492 ; the numeric value of DVI$_MOUNTCNT_CLUSTER is 494. In order to use these new item codes with the SYS$GETDVI system service, you will need to update the DVIDEF module, in the STARLET libraries for the languages you use, with these values. The easiest way to do this is to extract the definitions, make the necessary changes and re-insert the definitions into the library. For example, for the C language, the DCL command to extract the definition file is: $ LIBRARY /EXTRACT=DVIDEF/OUT =DVIDEF.TXT - SYS$LIBRARY:SYS$STARLET_C.TLB Edit the TXT file to add the values for the DVI$_MOUNTCNT_CLUSTER and DVI$_ADAPTER_IDENT item codes. The modified DVIDEF.TXT file must then be inserted back into SYS$LIBRARY:SYS$STARLET_C.TLB with the command: $ LIBRARY/REPLACE SYS$LIBRARY:SYS$STARLET_C.TLB - DVIDEF.TXT Contact your HP services representative if you need assistance with these changes. Page 4 Images Affected: - [SYSEXE]DCL.EXE - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2 Problems addressed in this kit 5.2.1 $GOTO_UNWIND System Crash cldnote 5968,5984 5.2.1.1 Problem Description: Applications with multiple concurrent $GOTO_UNWINDs or $UNWINDs over multiple exceptions can lead to system crashes. The changes provided in this kit improve the behavior of $GOTO_UNWIND, $GOTO_UNWIND_64, and $UNWIND to eliminate these crashes. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) QXCM1000350985 5.2.1.2.2 QAR(s) None. Page 5 5.2.1.3 Problem Analysis: If a program unwinds from an AST routine while another AST is queued,$GOTO_UNWIND releases the second AST in the middle of the unwind. If the second AST also does a $GOTO_UNWIND to the same place, an ACCVIO can occur. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. 5.2.2 SCSI or Fibrechannel I/O Can Hang cldnote 5996 szubowicz 5.2.2.1 Problem Description: Processing of all pending I/O to a particular SCSI or Fibrechannel disk can hang if the preferred CPU of the host bus adapter used by that device is changed at an inopportune time. The DCL SET DEVICE/PREFERRED_CPU command and starting and stopping CPUs are among the ways to cause a change in the preferred CPU for "fast path" devices. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. Page 6 5.2.2.2.2 QAR(s) 75-109-1719,75-109-1767 5.2.2.3 Problem Analysis: A change of the preferred fast path CPU for a device while IOC$INITIATE_PORT_CPU processing is pending or active for that device can result in a hung I/O pending queue for that device. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.2.5 Work-arounds: None. 5.2.3 SET SECURITY /LIKE Command Does Not Set ACE cldnote 6001 harney 5.2.3.1 Problem Description: If a user performs a SET SECURITY /LIKE command where the source file has a subsystem ACE in its ACL, but the user does not possess a subsystem identifier, the operation will silently fail. The other security attributes will be set, but the subsystem ACE will be missing. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY_MON.STB 5.2.3.2 CLDs, and QARs reporting this problem: Page 7 5.2.3.2.1 CLD(s) QXCM1000324589;WFM3214257137-322 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: A check for a failed ACL status is not done before performing another ACL operation (that will overwrite the failed ACL status). This change will cause the failed ACL status check to be done. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.3.5 Work-arounds: None. 5.2.4 Several Bugcheck / SDA Problems 5.2.4.1 Problem Description: o The system may crash if, while writing a process dump, a non-existent page is chosen when collecting relevant system space pages. o The SDA SHOW CALL command will now work correctly. Images Affected: - [SYSLIB]IMGDMP.EXE - [SYSLIB]SDA$SHARE.EXE - [SYS$LDR]SYS$BASE_IMAGE.EXE Page 8 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: See problem description. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.4.5 Work-arounds: None. 5.2.5 Possible System Crash 5.2.5.1 Problem Description: The system can crash when either a tape or a disk in mount verification is dismounted. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.5.2 CLDs, and QARs reporting this problem: Page 9 5.2.5.2.1 CLD(s) None. 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: A register was not preserved. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.5.5 Work-arounds: None. 5.2.6 System Crash in NSA$SIZE_NSAB 5.2.6.1 Problem Description: The system can crash in NSA$SIZE_NSAB if certain bad data is included in the item list to $AUDIT_EVENT, or if the item list is not terminated. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY_MON.STB 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) None. Page 10 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: See problem description. 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.6.5 Work-arounds: None. 5.2.7 F$DEVICE Searches Can Take a Long Time 5.2.7.1 Problem Description: The lexical function F$DEVICE (and by extension, the system service SYS$DEVICE_SCAN) can be used with a wild card device specification to return the names of all devices on a system. The use of matching device classes and device types can be used to limit the output to those devices matching either of those criteria. In the case of a system with a large number of network or mailbox devices, a wildcard search for all disk devices can take a very long time. This change optimizes the searching logic to skip over long lists of non-matching devices. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 5.2.7.2 CLDs, and QARs reporting this problem: Page 11 5.2.7.2.1 CLD(s) QXCM1000337994;WFM3214812945-326 5.2.7.2.2 QAR(s) None. 5.2.7.3 Problem Analysis: See problem description. 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.7.5 Work-arounds: None. 5.2.8 Process Hang 5.2.8.1 Problem Description: Occasionally, a process will hang in RMS rundown at IPL 2, waiting for a blocked AST to complete. If the process also holds a lock, other processes on the system may hang waiting for the lock to be released. Images Affected: - [SYS$LDR]SYSLDR_DYN.EXE - [SYS$LDR]SYSLDR_DYN.STB 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) QXCM1000359860,WFM3215439147-323 5.2.8.2.2 QAR(s) None. Page 12 5.2.8.3 Problem Analysis: SYSDELPRC invokes the user rundown routines and expects to be returned to at IPL 0. However, at return, the IPL is 2. 5.2.8.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.8.5 Work-arounds: None. 5.2.9 MC SYSMAN IO AUTOCONFIGURE System Crash 5.2.9.1 Problem Description: When the MPDEV_POLLER and MPDEV_D3 SYSGEN parameters are set, the system can crash when an "MC SYSMAN IO AUTOCONFIGURE" command is issued. Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB 5.2.9.2 CLDs, and QARs reporting this problem: 5.2.9.2.1 CLD(s) QXCM1000369587 5.2.9.2.2 QAR(s) None. 5.2.9.3 Problem Analysis: The MPDEV_FLUSH code (mpdev$get_next_flush_candidate) looks through the IODB and selects UCB only if the UCB matches the following criteria: Page 13 o UCB must not be marked MNTVERIP o UCB must not be foreign mounted o Primary UCB must not be marked pathverip For each UCB that is selected, the MPDEV_FLUSH code (mpdev$do_next_flush_io) queues the IRP (IO$_FLUSH_ERROR) into UCB$Q_DK_IRP_LIST for error flushing. The MPDEV_FLUSH code queued the IO$_FLUSH_ERROR IRP into a UCB that was not fully configured. 5.2.9.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.9.5 Work-arounds: None. 5.2.10 Unable to Delete Global Section with Bad Page 5.2.10.1 Problem Description: Occasionally, a global section gets stuck on the delete pending list and is never deleted. This can occur if an I/O error occurs trying to write out the section and, because of this, has a page placed onto the bad page list. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.10.2 CLDs, and QARs reporting this problem: 5.2.10.2.1 CLD(s) QXCM1000192113 5.2.10.2.2 QAR(s) None. Page 14 5.2.10.3 Problem Analysis: See problem description. 5.2.10.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.10.5 Work-arounds: None. 5.2.11 Memory Does Not Get Dumped 5.2.11.1 Problem Description: When writing a full dump, if there are exactly 32 physical memory fragments, BUGCHECK zeroes the memory map at the wrong time and no memory gets dumped. If bit 1 in SYSGEN parameter DUMPSTYLE is set (verbose console output), there will be repeated messages of the form: "** Dumping unknown memory (PFN range 00000000.00000000 to FFFFFFFF.FFFFFFFF)... The resulting dump will be is unreadable; SDA reports "%SDA-F-DUMPINCOMPL, the dump file write was not completed". Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB 5.2.11.2 CLDs, and QARs reporting this problem: 5.2.11.2.1 CLD(s) None. Page 15 5.2.11.2.2 QAR(s) 75-118-64 5.2.11.3 Problem Analysis: See problem description. 5.2.11.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.11.5 Work-arounds: None. 5.2.12 Performance Improvement 5.2.12.1 Problem Description: With this change, customers running very busy systems with a high demand zero page fault rate will see improved performance. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.12.2 CLDs, and QARs reporting this problem: 5.2.12.2.1 CLD(s) None. 5.2.12.2.2 QAR(s) None. Page 16 5.2.12.3 Problem Analysis: The idle loop in the OpenVMS Scheduler performs a function known as page zeroing. When a demand zero page fault occurs, if a pre-zeroed page already exists, then the page fault can be handled much faster since the zeroing of the page does not need to occur as part of the pagefault. The idle loop had been assigning time slices to zero pages to avoid all CPUs performing this function concurrently. On a large system, without much idle CPU time, this may result in the page zeroing occurring very slowly. For non-Rad based systems, the idle loop will no longer time slice the page zeroing function. This will allow any idle CPU to perform page zeroing if idle. The goal here is to increase the rate at which pages can be zeroed. 5.2.12.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.12.5 Work-arounds: None. 5.2.13 System Crash with CLUEXIT Bugcheck 5.2.13.1 Problem Description: In an OpenVMS Cluster, there is the potential for lock manager $DEQ ALL operations to overwhelm another node in the cluster with DEQ messages. When this occurs, it is possible that either the cluster connections will break and reform or that a system crash with a CLUEXIT bugcheck. Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]SYS$CLUSTER.STB - [SYS$LDR]SYS$CLUSTER_MON.EXE Page 17 - [SYS$LDR]SYS$CLUSTER_MON.STB 5.2.13.2 CLDs, and QARs reporting this problem: 5.2.13.2.1 CLD(s) 70-3-8878,QXCM1000360250,WFM3215947250-321 5.2.13.2.2 QAR(s) None. 5.2.13.3 Problem Analysis: See problem description. 5.2.13.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.13.5 Work-arounds: None. 5.2.14 Performance Degradation 5.2.14.1 Problem Description: Heavy kernal mode alignment faulting can cause performance issues for applications. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY_MON.STB Page 18 5.2.14.2 CLDs, and QARs reporting this problem: 5.2.14.2.1 CLD(s) None. 5.2.14.2.2 QAR(s) None. 5.2.14.3 Problem Analysis: Various data structures used within the ARBS_AND_ORBS module are not aligned on a quadword. 5.2.14.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.14.5 Work-arounds: None. 5.2.15 Invalid Time Stamps 5.2.15.1 Problem Description: Errorlog entries can contain invalid time stamps. Images Affected: - [SYS$LDR]EXEC_INIT.EXE - [SYS$LDR]EXEC_INIT_MON.EXE - [SYS$LDR]EXEC_INIT.STB - [SYS$LDR]EXEC_INIT_MON.STB 5.2.15.2 CLDs, and QARs reporting this problem: Page 19 5.2.15.2.1 CLD(s) None. 5.2.15.2.2 QAR(s) 75-118-72 5.2.15.3 Problem Analysis: Error log entries can get default, stale values when an interrupt happens before the normal SYSINIT mechanism. 5.2.15.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.15.5 Work-arounds: None. 5.2.16 Application Crashes 5.2.16.1 Problem Description: Various application failures can occur with applications that use extended value blocks. RDB and SHADOWING are two such applications. Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB 5.2.16.2 CLDs, and QARs reporting this problem: 5.2.16.2.1 CLD(s) None. 5.2.16.2.2 QAR(s) None. Page 20 5.2.16.3 Problem Analysis: With the dedicated CPU lock manager enabled, extended lock value blocks were being returned incorrectly. In addition, under some conditions, the SS$_XVALNOTVALID bit was not being set correctly when the extended value block was manipulated under the dedicated CPU lock manager. 5.2.16.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.16.5 Work-arounds: None. 5.2.17 Performance Degradation 5.2.17.1 Problem Description: On large SMP systems with high image activation rates, MP Synch time can become very long, resulting in a performance degradation. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB 5.2.17.2 CLDs, and QARs reporting this problem: 5.2.17.2.1 CLD(s) None. Page 21 5.2.17.2.2 QAR(s) None. 5.2.17.3 Problem Analysis: See problem description. 5.2.17.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.17.5 Work-arounds: None. 5.2.18 System Crash with INVSECURESTATE Bugcheck 5.2.18.1 Problem Description: The system can crash with an INVSECURESTATE bugcheck. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.18.2 CLDs, and QARs reporting this problem: 5.2.18.2.1 CLD(s) QXCM1000369887 5.2.18.2.2 QAR(s) None. Page 22 5.2.18.3 Problem Analysis: Inside EXE$KTHREAD_DELETE_SELF, there was no call to synchronize the PSBs in use and operate on the correct PSB. 5.2.18.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.18.5 Work-arounds: None. 5.2.19 INVEXCEPTN SCH$POSTEF_SCHED Bugcheck 5.2.19.1 Problem Description: On multithreaded process, the system can crash with an "INVEXCEPTN SCH$POSTEF_SCHED" bugcheck. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.19.2 CLDs, and QARs reporting this problem: 5.2.19.2.1 CLD(s) QXCM1000385036,WFM1213687533-121 5.2.19.2.2 QAR(s) None. 5.2.19.3 Problem Analysis: The INVEXCEPTN bugcheck occurs when the code tries to queue PCB$L_POSTEF_ACB to a multithreaded process (with upcalls enabled) before the field has been completely set up (and is still 0). Page 23 5.2.19.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.19.5 Work-arounds: None. 5.2.20 System Crash 5.2.20.1 Problem Description: Program actions relating to exceptions can lead to a system crash rather than a reported exception. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.2.20.2 CLDs, and QARs reporting this problem: 5.2.20.2.1 CLD(s) QXCM1000394665 5.2.20.2.2 QAR(s) 75-13-1760 5.2.20.3 Problem Analysis: See problem description. 5.2.20.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 24 5.2.20.5 Work-arounds: None. 5.2.21 Wrong Value Stored in Register F1 cldnote 6284 fisher 5.2.21.1 Problem Description: Storing floating register F1 (which always contains the constant 1.0) to an unaligned address can result in the wrong value being stored. This should be an unusual condition since the constant register is not often stored, and even less often stored to an unaligned location. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB 5.2.21.2 CLDs, and QARs reporting this problem: 5.2.21.2.1 CLD(s) None. 5.2.21.2.2 QAR(s) 75-13-1870 5.2.21.3 Problem Analysis: See problem description. 5.2.21.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 25 5.2.21.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSEXE]DCL.EXE (new image) Image Identification Information image name: "DCL" image file identification: "X-50" image file build identification: "XBCA-0080070001" link date/time: 13-MAR-2007 08:26:46.40 linker identification: "A13-03" Overall Image Checksum: 3102699109 o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information image name: "EXCEPTION" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:29.82 linker identification: "A13-03" Overall Image Checksum: 3711012821 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information image name: "EXCEPTION_MON" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:33.26 linker identification: "A13-03" Overall Image Checksum: 2821184551 o [SYS$LDR]EXEC_INIT.EXE (new image) Image Identification Information image name: "EXEC_INIT" image file identification: "X-214" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:36.41 linker identification: "A13-03" Overall Image Checksum: 1678863584 o [SYSLIB]IMGDMP.EXE (new image) Image Identification Information image name: "IMGDMP" Page 26 image file identification: "X-58A2" image file build identification: "XBCA-0080070001" link date/time: 5-DEC-2006 13:00:21.55 linker identification: "A13-03" Overall Image Checksum: 4185774479 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:41.68 linker identification: "A13-03" Overall Image Checksum: 3445756102 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: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:43.44 linker identification: "A13-03" Overall Image Checksum: 1835249131 o [SYS$LDR]LOCKING.EXE (new image) Image Identification Information image name: "LOCKING" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:46.04 linker identification: "A13-03" Overall Image Checksum: 2287043661 o [SYS$LDR]MULTIPATH.EXE (new image) Image Identification Information image name: "MULTIPATH" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:47.86 linker identification: "A13-03" Overall Image Checksum: 2163081513 o [SYS$LDR]MULTIPATH_MON.EXE (new image) Image Identification Information image name: "MULTIPATH_MON" image file identification: "X-5" image file build identification: "XBCA-0080070027" Page 27 link date/time: 7-MAR-2007 14:58:48.69 linker identification: "A13-03" Overall Image Checksum: 3387159106 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:51.79 linker identification: "A13-03" Overall Image Checksum: 3046681859 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: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:52.64 linker identification: "A13-03" Overall Image Checksum: 913450867 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information image name: "SDA$SHARE" image file identification: "X-1" image file build identification: "XBCA-0080070008" link date/time: 7-MAR-2007 14:58:34.58 linker identification: "A13-03" Overall Image Checksum: 4074055844 o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information image name: "SECURITY" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:27.46 linker identification: "A13-03" Overall Image Checksum: 1791042283 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information image name: "SECURITY_MON" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:32.28 linker identification: "A13-03" Page 28 Overall Image Checksum: 2521131244 o [SYSEXE]SHOW.EXE (new image) Image Identification Information image name: "SHOW" image file identification: "X-16" image file build identification: "XBCA-0080070009" link date/time: 21-FEB-2007 15:39:06.72 linker identification: "A13-03" Overall Image Checksum: 1557858161 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information image name: "SYS$BASE_IMAGE" image file identification: "ALPHA XBCA-N2O" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:56:37.80 linker identification: "A13-03" Overall Image Checksum: 3870174631 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-5" image file build identification: "XBCA-0080070001" link date/time: 29-NOV-2006 15:43:55.96 linker identification: "A13-03" Overall Image Checksum: 675821449 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: "XBCA-0080070001" link date/time: 29-NOV-2006 15:43:58.41 linker identification: "A13-03" Overall Image Checksum: 1626884601 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:42.53 linker identification: "A13-03" Overall Image Checksum: 564285140 Page 29 o [SYS$LDR]SYSLDR_DYN.EXE (new image) Image Identification Information image name: "SYSLDR_DYN" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:46.56 linker identification: "A13-03" Overall Image Checksum: 3780411768 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:49.10 linker identification: "A13-03" Overall Image Checksum: 85166119 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: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:50.16 linker identification: "A13-03" Overall Image Checksum: 396578336 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]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]LOCKING.STB (new file) o [SYS$LDR]MULTIPATH.STB (new file) o [SYS$LDR]MULTIPATH_MON.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) Page 30 o [SYS$LDR]SECURITY_MON.STB (new file) o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) o [SYS$LDR]SYS$VM.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) 7 INSTALLATION INSTRUCTIONS 7.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. 7.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 VMS83A_SYS-V0100.ZIPEXE Page 31 7.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 VMS83A_SYS[/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. 7.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=DEC/BASE=AXPVMS/VER=V1.0 [/SOURCE=location of Kit] Page 32 o De-assign the logical names assigned For example, a sample command file to install the VMS83A_SYS-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_SYS/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 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.