ECO NUMBER: AXPSYS13_061 ----------- PRODUCT: OPENVMS AXP OPERATING SYSTEM 6.1 -------- UPDATED PRODUCT: OPENVMS AXP OPERATING SYSTEM 6.1 ---------------- APPRX BLCK SIZE: 1280 ---------------- COVER LETTER 1 KIT NAME: AXPSYS13_061 2 KIT DESCRIPTION: 2.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS AXP V6.1, V6.1-1H1, V6.1-1H2 2.2 Kits superseded by this kit: AXPSYS05_061 2.3 Files patched or replaced: o [SYS$LDR]LOCKING.EXE (new image) o [SYS$LDR]SYS$VCC.EXE (new image) o [SYS$LDR]SYS$VCC_MON.EXE (new image) o [SYS$LDR]SYS$CLUSTER.EXE (new image) 3 PROBLEMS ADDRESSED IN AXPSYS13_061 KIT o There is a race condition possible when a CFCB (Cache File Control Block) is being deleted due to XQP action and cache space is being reclaimed from a LIMBO file. o Under certain conditions, a fork lock used by the virtual I/O cache may be created with an incorrect length. This results in unsynchronized data access which can cause corruption. 4 PROBLEMS ADDRESSED IN AXPSYS05_061 KIT o If a multi-programming application uses a non-homogenous access pattern to a file which is resident in Virtual I/O cache, there is a possibility that the size returned in the I/O status block from a READ operation will be truncated. -- COVER LETTER -- Page 2 30 May 1995 If a clustered application consisting of a large number of concurrent processes which perform file operations consisting of an OPEN, WRITE , CLOSE sequence on the same data file repetitively , a possibility of data corruption exists. In a multi-programming environment, where a significant amount of NEW data from a file is being loaded into the cache concurrently by multiple processes, the possibility of a HANG exists. o In a VMS cluster, if VCC_MAXSIZE is set to a value which is too low the user may see the following console message during boot of one of the cluster members: "Insufficient system page table space for VIOC cache." This will permit the Virtual I/O Cache function to run on other members of the cluster even though it is not running on this member. This can lead to data corruption. 5 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 AXPSYS13_061 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. System should be rebooted after successful installation of the kit. If you have other nodes in your VMScluster, they should also be rebooted in order to make use of the new image(s). *************************** NOTE ********************************** If the AXPSHAD06_061 kit is applied after this kit has been installed, during the AXPSHAD06_061 installation you will receive messages stating that the images LOCKING .EXE, SYS$VCC.EXE and SYS$VCC_MON.EXE will not be installed. This is because the images in AXPSYS13_061 are newer images than what are in AXPSHAD06_061 and installing the images from AXPSHAD06_061 would result in regression. Other AXPSHAD06_061 images will install normally. ******************************************************************** -- COVER LETTER -- Page 3 30 May 1995 Copyright Digital Equipment Corporation 1995. All Rights reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Digital makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.