ECO NUMBER: ALPSYS23_061 ----------- PRODUCT: OpenVMS Alpha Operating System -------- UPDATED PRODUCT: OpenVMS Alpha Operating System 6.1 ---------------- APPRX BLCK SIZE: 1908 ---------------- COVER LETTER 1 KIT NAME: ALPSYS23_061 2 KITS SUPERSEDED BY THIS KIT: ALPSYS22_061, ALPSYS19_061, ALPSYS17_061 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this kit: ALPSHAD09_061 3.2 In order to receive the all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2 4.2 Files patched or replaced: o [SYS$LDR]IO_ROUTINES.EXE (new image) o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) o [SYSLIB]SYS$SSISHR.EXE (new image) o [SYSLIB]SYS$PUBLIC_VECTORS.EXE (new image) -- COVER LETTER -- Page 2 4 March 1998 5 PROBLEMS ADDRESSED IN ALPSYS23_061 KIT o OpenVMS Alpha V6.1 - V7.0 systems using the SYS$SET_SECURITY or the SYS$CHANGE_ACL system service to protect File Objects are inconsistent. o OpenVMS Alpha systems could crash when cleaning up pending ASTs during rundown, with the address of the next packet pointing to an incorrect value. o OpenVMS could create processes in the same group UIC with the same process name. On OpenVMS VAX systems, SS$_NOSLOT could be returned when one process entry slot is left, the last one used. o A potential problem exists when a batch job process termination message is sent to the JOB_CONTROL process. If the Job Controller's mailbox is full at the time, the message is sent, so the message could be dropped and lost. The result could be that SHOW QUEUE shows "executing" jobs with no associated process on the system. 6 PROBLEMS ADDRESSED IN ALPSYS22_061 KIT o The ALPSYS03_062 kit, which applied to V6.2 and V7.1, is being re-issued as separate version kits. There are no new fixes in this kit. If you have installed the ALPSYS03_062 remedial kit, you do not need to install this kit. 7 PROBLEMS ADDRESSED IN ALPSYS03_062 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2 o SHOW SECURITY/CLASS=DEVICE generates an ACCVIO and crashes the system. This problem is corrected in OpenVMS Alpha V6.2 o Occasional crashes in IOC$DISMOUNT with INCONSTATE or SSRVEXCEPT. This problem is corrected in OpenVMS Alpha V7.0. -- COVER LETTER -- Page 3 4 March 1998 8 PROBLEMS ADDRESSED IN AXPSYS03_061 KIT o Process loops in kernel mode, holding IO database mutex. The problem can be reproduced by sending mail to yourself on a workstation after creating and deleting the message window. This problem is corrected in OpenVMS Alpha V6.2. 9 PROBLEMS ADDRESSED IN ALPSYS19_061 KIT o Remove previous fix for Spurious SS$_SUBTRACED errors with protected subsystems. Images linked with DEBUG cannot be run using this modification. The problem is fixed in V6.2 OpenVMS Alpha. 10 PROBLEMS ADDRESSED IN ALPSYS15_061 KIT o Spurious SS$_SUBTRACED errors with protected subsystems, if the image was installed with an INSTALL/HEADER_RESIDENT command. This problem is corrected in OpenVMS Alpha V6.2. 11 PROBLEMS ADDRESSED IN ALPSYS17_061 KIT o Although the ALPSYS11_061 documentation states that the system must be rebooted, some customers are not doing so immediately. This causes a problem when using DEBUG. A BADVECTOR error is issued and the system crashes. The problem does not occur if the system is rebooted. The crash occurs because the kit does an INSTALL/REPLACE on the SYS$SSISHR.EXE image which results in image mismatch problems if the system is not re-booted. Re-issue the kit with a stronger warning. 12 PROBLEMS ADDRESSED IN ALPSYS11_061 KIT o The common idle loop counters have a severe performance degradation on Alpha 4000 SMP configurations. -- COVER LETTER -- Page 4 4 March 1998 13 PROBLEMS ADDRESSED IN AXPSYS10_061 KIT o Process hangs and is often impossible to kill or stop. 14 PROBLEMS ADDRESSED IN AXPSYS09_061 KIT o Because installation of the AXPSYS06_061 ECO kit will exacerbate problems corrected by the AXPRMS02_061 ECO kit, after installation of the AXPSYS06_061 kit users should also install the AXPRMS02_061 kit. 15 PROBLEMS ADDRESSED IN AXPSYS06_061 KIT o The PROCESS_MANAGEMENT.EXE image included in remedial kit AXPSYS04_061 did not fix the problems listed. 16 PROBLEMS ADDRESSED IN AXPSYS04_061 KIT o A process is hung in LEF state, with an outstanding I/O operation and a kernel mode AST queued to the process. Kernel mode ASTs are disabled. 17 PROBLEMS ADDRESSED IN AXPSYS02_061 KIT o Applications that call the wait form of system services cause a hang. The cause is that the service has finished asynchronously but the application is still waiting in LEF. The problem has been found to be generally applicable to all system services that have a wait form counterpart. 18 PROBLEMS ADDRESSED IN AXPSYS01_061 KIT o On systems running OpenVMS Alpha V6.1, when a process with a non-zero CPU limit SPAWNs one or more subprocesses, each SPAWN halves the CPU limit (as expected), but on returning from the SPAWN the unused CPU time isn't credited back to the parent process. After some number of successful SPAWNs the process will receive a %SYSTEM-F-EXCPUTIME error and will not allow the user to continue. The user will have to log out and log back -- COVER LETTER -- Page 5 4 March 1998 in to start another process. 19 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: 3 : To be installed by customers experiencing the problems corrected. 20 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPSYS23_061 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. If you have other nodes in your VMS 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. Copyright (c) Digital Equipment Corporation, 1998 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. 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 DIGITAL BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND -- COVER LETTER -- Page 6 4 March 1998 REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.