**************************** ECO SUMMARY INFORMATION **************************** Release Date: 1-AUG-2007 Kit Name: DEC-AXPVMS-VMS82A_CLIUTL-V0100--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 1199 blocks Installation Rating: INSTALL_3 Reboot Required: No Superseded Kits: None Mandatory Kit Dependencies: VMS82A_UPDATE-V0600 or later VMS82A_PCSI-V0100 or later Optional Kit Dependencies: None Checksums: VMS82A_CLIUTL-V0100.ZIPEXE Checksum: 1647051693 DEC-AXPVMS-VMS82A_CLIUTL-V0100--4.PCSI$COMPRESSED Checksum: 1056650025 VMS82A_CLIUTL-V0100.ZIPEXE MD5 Checksum: 422C5F3D5C221993A548C0C1E19C6A3E DEC-AXPVMS-VMS82A_CLIUTL-V0100--4.PCSI$COMPRESSED MD5 Checksum: 8E4051160CCD46882259EFA8BE6AA0DB ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_CLIUTL-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 2.2 Reboot Requirement: No reboot is necessary after installation of this kit. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V8.2 2.4 New functionality or new hardware support provided: No 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: - VMS82A_PCSI-V0100 - VMS82A_UPDATE-V0600 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None Page 2 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS82A_CLIUTL-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 SHOW SYSTEM/IMAGE Problems 5.2.1.1 Problem Description: o A SHOW SYSTEM/IMAGE command aborts with a SYSTEM-F-SUSPENDED error when encountering a process in SUSP state" o A SHOW SYSTEM/IMAGE command on an outswapped process will trigger an inswap (example output truncated to fit): $ SHOW SYSTEM/STATE=HIBO Pid Process Name State Pri I/O CPU 20800410 CACHE_SERVER HIBO 16 -- swapped out 2080041B REMACP HIBO 9 -- swapped out 2080041F SMTP_IPL31_01 HIBO 4 -- swapped out $ SHOW SYSTEM/STATE=HIBO/IMAGE Pid Process Name State Pri I/O CPU 20800410 CACHE_SERVER HIBO 16 -- swapped out DSA5:[SYS0.SYSCOMMON.][SYSEXE]FILESERV.EXE 2080041B REMACP HIBO 9 -- swapped out DSA5:[SYS0.SYSCOMMON.][SYSEXE]REMACP.EXE;1 2080041F SMTP_IPL31_01 HIBO 4 -- swapped out DSA5:[SYS0.SYSCOMMON.][SYSEXE]TCPIP$SMTP_SYMBIONT.EXE;1 $ SHOW SYSTEM/STATE=HIBO $ ! no outswapped processes o A SHOW SYSTEM/IMAGE/STATE=RMBX command aborts with SYSTEM-F-SUSPENDED when encountering a process in one of the MWAIT states (example output truncated to fit): $ SHOW SYSTEM/IMAGE/STATE=RWMBX Pid Process Name State Pri I/O CPU 20800498 _TNA11: RWMBX 6 582 0 00:00:00.29 %SYSTEM-F-SUSPENDED, process is suspended Images Affected: Page 3 - [SYSEXE]SHOW.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) 75-109-105 5.2.1.3 Problem Analysis: o A $GETJPI call on a suspended process fails with SYSTEM-F-SUSPENDED. The bad status was being signaled causing SHOW SYSTEM to abort due to unsuccessful operation. o JPI$_IMAGNAME is looking at CTL$GL_IMGHDRBUF of the target process which forces an inswap. 5.2.1.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.1.5 Work-arounds: None. 5.2.2 SHOW MEMORY /SLOT Does Not Display Adjusted Balance Set slots Value 5.2.2.1 Problem Description: If the balance set slots are dynamically adjusted, a SHOW MEMORY /SLOT command does not display the adjusted value. The change contained in this patch kit will update the SHOW MEMORY /SLOT command to display the total slots allocated and the adjusted swapper maximum value. SYSGEN> SHOW BAL Parameter Current Default Min. Max. Unit Name ---------- ------- ------- ---- ---- ---- BALSETCNT 484 30 8 16384 Processes MAXPROCESSCNT 520 32 12 16384 Processes Page 4 New Display: TEST> SHOW MEMORY/SLOT Slot Usage (slots): Total Free Resident Swapped Process Entry Slots 520 488 26 6 Balance Set Slots(484) 518 488 24 6 Old Display: TEST> SHOW MEMORY/SLOT Slot Usage (slots): Total Free Resident Swapped Process Entry Slots 520 488 26 6 Balance Set Slots 484 489 29 0 Images Affected: - [SYSEXE]SHOW.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000218851 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: The SHOW MEMORY display does not use the dynamically adjustable balance set cell. 5.2.2.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.2.5 Work-arounds: None. 5.2.3 SHOW SYSTEM/STATE Command Misses Processes Page 5 5.2.3.1 Problem Description: The output of a SHOW SYSTEM/STATE command does not show all processes when more than one state is specified, and the second state is one of the resource wait states. For example, a SHOW SYSTEM/STATE=(RWMBX,LEF) command will show processes that are in RWMBX state while a SHOW SYSTEM/STATE=(LEF,RWMBX) command will not. Images Affected: - [SYSEXE]SHOW.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000218969 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: A flag is not initialized. 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 SET PASSWORD/GENERATE Can Cause Errors 5.2.4.1 Problem Description: Customers with a SET PASSWORD/GENERATE in a command procedure can sometimes see a %RMS-W-RTB error, for example: Choose a password from this list, or press RETURN to get a new list %RMS-W-RTB, 226532 byte record too large for user's buffer this occurs when the DCL command following the SET PASSWORD /GENERATE is longer than 32 characters. Page 6 Users that use SET PASSWORD/GENERATE interactively will see the same RMS-W-RTB, 226532 byte error message if the password they enter is greater than 32 characters. Images Affected: - [SYSEXE]SETP0.EXE 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) 75-109-279 5.2.4.3 Problem Analysis: The buffer for the input is only 32 bytes. 5.2.4.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.4.5 Work-arounds: None. 5.2.5 SET PASSWORD/GENERATE Does Not Accept Some Passwords 5.2.5.1 Problem Description: Users may encounter passwords on the generated password list that are not recognized as being on that list: $ SET PASSWORD/GENERATE Old password: rettivifts multroment hablechey binglics mandaily %SET-S-PICKLIST, Choose a password from this list, or press RETURN to get a new list Page 7 New password: %SET-S-NOTONLIS, That word is not on this list: rettivifts multroment hablechey binglics mandaily %SET-S-PICKLIST, Choose a password from this list, or press RETURN to get a new list New password: Images Affected: - [SYSEXE]SETP0.EXE 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) None. 5.2.5.2.2 QAR(s) 75-109-298 5.2.5.3 Problem Analysis: A $GET sometimes leaves the terminator in user's buffer, 5.2.5.4 Release Version of OpenVMS that will contain this change: OpenVMS V8.3 5.2.5.5 Work-arounds: None. 5.2.6 SHOW SYSTEM/IMAGE May Fail With SYSTEM-F-SUSPENDED. Page 8 5.2.6.1 Problem Description: A SYSTEM/IMAGE command may fail with a SYSTEM-F-SUSPENDED error Images Affected: - [SYSEXE]SHOW.EXE 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) None. 5.2.6.2.2 QAR(s) 75-112-256 5.2.6.3 Problem Analysis: The code does not take into consideration that a process in LEF state may be suspended. 5.2.6.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.6.5 Work-arounds: None. 5.2.7 Z During SHOW CPU/FULL/PAGE Causes Process Termination 5.2.7.1 Problem Description: Entering a Z when a SHOW CPU/FULL/PAGE command is displaying certain CPU information results in the process being terminated. Images Affected: - [SYSLIB]UTIL$SHARE.EXE Page 9 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) None. 5.2.7.2.2 QAR(s) 75-13-1562 5.2.7.3 Problem Analysis: SHOW CPU uses the generic utilities /PAGE handling routines. When Z is entered the generic routine issues a $EXIT. SHOWCPU is displaying some information, fastpath, CPU binding, from exec mode and $EXIT causes the process to exit. 5.2.7.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.7.5 Work-arounds: None. 5.2.8 SHOW LOGICAL Generates Alignment Faults 5.2.8.1 Problem Description: Issuing the SHOW LOGICAL command generates numerous alignment faults. Images Affected: - [SYSEXE]SHOW.EXE 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) None. Page 10 5.2.8.2.2 QAR(s) 75-13-1655 5.2.8.3 Problem Analysis: SHOW LOGICAL allocates a large chunk of virtual memory for various structures and packets it uses. o The large chunk of memory did not end on a quadword boundary. Any structure allocated after the large VM chunk started on an unaligned address and referencing it resulted in an alignment fault. o SHOW LOGICAL was allocating small pieces of the big VM chunk for various structures without regard to the size of memory being consumed. Some packets/structures started on an unaligned address which resulted in an alignment faults. 5.2.8.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.8.5 Work-arounds: None. 5.2.9 SHOW DEVICE Problems 5.2.9.1 Problem Description: o A SHOW DEVICE/FILE command does not show some files that are open on the volume when that file is opened by BACKUP /IGNORE=INTERLOCK. o If a volume is in mount verification, the SHOW DEVICE/FILE command will hang. Images Affected: - [SYSEXE]SHOW.EXE Page 11 5.2.9.2 CLDs, and QARs reporting this problem: 5.2.9.2.1 CLD(s) None. 5.2.9.2.2 QAR(s) 75-13-1392 5.2.9.3 Problem Analysis: SHOW was looking at only one criteria for determining an open file. 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 SHOW PROCESS/CONTINUOUS Command Results in PGFIPLHI Crash 5.2.10.1 Problem Description: A SHOW PROCESS/CONTINUOUS command can result in a PGFIPLHI crash on memory constrained systems. Images Affected: - [SYSEXE]SHOW.EXE 5.2.10.2 CLDs, and QARs reporting this problem: 5.2.10.2.1 CLD(s) QXCM1000373738 5.2.10.2.2 QAR(s) None. Page 12 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 .hl 3 SHOW CLUSTER Command Can Crash System 5.2.11.1 Problem Description: Errors such as mis-configuration of NPAG_BAP_* parameters, insufficient non-paged pool and a missing CLUSTER_AUTHORIZE.DAT can cause a SHOW CLUSTER command to crash the system when the PEdriver is partially initialized. Images Affected: - [SYSEXE]SHWCLSTR.EXE 5.2.11.2 CLDs, and QARs reporting this problem: 5.2.11.2.1 CLD(s) None. 5.2.11.2.2 QAR(s) 75-45-1447 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 Page 13 5.2.11.5 Work-arounds: None. 5.2.12 SHOW SYSTEM/STATE=COM/CLUSTER Command Fails with ACCVIO 5.2.12.1 Problem Description: A SHOW SYSTEM/STATE=COM/CLUSTER command in the cluster environment leads to an ACCVIO. Images Affected: - [SYSEXE]SHOW.EXE 5.2.12.2 CLDs, and QARs reporting this problem: 5.2.12.2.1 CLD(s) QXCM1000407175 5.2.12.2.2 QAR(s) None. 5.2.12.3 Problem Analysis: The order of comparison with respect to the Event flag wait mask of the RSN table and data block was incorrect in the output_data MACRO when displaying information on a particular process. 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. 6 FILES PATCHED OR REPLACED: o [SYSMSG]CLIUTLMSG.EXE (new image) Image Identification Information Page 14 image name: "CLIUTLMSG" image file identification: "X-3" image file build identification: "XAJT-0070050004" link date/time: 15-FEB-2007 10:47:40.75 linker identification: "A11-50" Overall Image Checksum: 411804719 o [SYSEXE]SETP0.EXE (new image) Image Identification Information image name: "SETP0" image file identification: "X-3K2" image file build identification: "XAJT-0070050019" link date/time: 27-JUN-2007 16:16:34.07 linker identification: "A11-50" Overall Image Checksum: 1348720116 o [SYSEXE]SHOW.EXE (new image) Image Identification Information image name: "SHOW" image file identification: "X-15" image file build identification: "XAJT-0070050019" link date/time: 27-JUN-2007 16:16:31.07 linker identification: "A11-50" Overall Image Checksum: 43681440 o [SYSEXE]SHWCLSTR.EXE (new image) Image Identification Information image name: "SHWCLSTR" image file identification: "X-26" image file build identification: "XAJT-0070050019" link date/time: 27-JUN-2007 16:16:31.79 linker identification: "A11-50" Overall Image Checksum: 2968154956 o [SYSLIB]UTIL$SHARE.EXE (new image) Image Identification Information image name: "UTIL$SHARE" image file identification: "A01-14" image file build identification: "XAJT-0070050019" link date/time: 27-JUN-2007 16:16:29.27 linker identification: "A11-50" Overall Image Checksum: 1025610945 Page 15 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 VMS82A_CLIUTL-V0100.ZIPEXE 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 VMS82A_CLIUTL[/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 Page 16 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 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] o De-assign the logical names assigned For example, a sample command file to install the VMS82A_CLIUTL-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_CLIUTL/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! {Special Installation Instructions} Page 17 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.