RELEASE NOTES Year 2000 Kits for OpenVMS VAX and OpenVMS Alpha Version 6.2 This document contains release notes for the VAX and Alpha Year 2000 enhancements that ship in kits VAXY2K02_062 and ALPY2K02_062, respectively. NOTE Kits VAXY2K02_062 and ALPY2K02_062 supersede kits VAXY2K01_062 and ALPY2K01_062. The new kits are identical to the superseded kits except that kits VAXY2K02_062 and ALPY2K02_062 also correctly replace image LBRSHR.EXE in SYS$COMMON:[SYSLIB]IMAGELIB.OLB. Kit VAXY2K02_062 also contains a fix that correctly installs F11BXQP.EXE in [SYSEXE]. Even though DIGITAL believes that few customer sites will need these enhancements, which affect only a few areas of the operat- ing system, all customer sites should install the Year 2000 kit. The few Year 2000 enhancements in this kit result from a rigor- ous and comprehensive analysis of the entire OpenVMS operating system, including extensive OpenVMS testing. For more information on the OpenVMS Year 2000 Initiative, please visit the OpenVMS Year 2000 web page: http://www.openvms.digital.com/openvms/products/year-2000 NOTE DIGITAL expects that most year 2000-related problems will occur primarily in locally developed layered applications. Therefore, it is important to start evaluating your applications and environments as soon as possible. Even if DIGITAL's products are ready for the year 2000, you must ensure that the environments in which these products operate are also ready. The OpenVMS Year 2000 web page includes a link to testing instructions, including how to set the system clock ahead to simulate the transition to the year 2000 or other future dates. If you need additional help, contact your DIGITAL support representative to learn what information and tools are available to get you started. 1 Kit Information Kit names: VAXY2K02_062 (VAX) and ALPY2K02_062 (Alpha) 1 Kits superseded by these kits: VAXY2K01_062 and ALPY2K01_062 (Year 2000 enhancement kits) VAXF11X03_062 and ALPF11X02_062 (Files-11 XQP file system) VAXVERI02_062 and ALPVERI02_062 (Analyze/Disk_Structure Utility) VAXLIBR06_070 and ALPLIBR06_062 (LIB$ Run-Time Library) ALPMTAA01_070 (Magnetic tape ACP) For kits VAXLIBR06_070 and ALPMTAA01_070, which contain fixes for several versions of the OpenVMS operating system, only the Version 6.2 fixes are included in VAXY2K02_062 and ALPY2K02_062. Kit description: Versions of OpenVMS to which these kits may be applied: OpenVMS VAX Version 6.2 OpenVMS/Japanese VAX Version 6.2 OpenVMS Alpha Versions 6.2, 6.2-1H1, 6.2-1H2, 6.2-1H3 OpenVMS/Japanese Alpha Versions 6.2, 6.2-1H1, 6.2-1H2, 6.2-1H3 Files modified, replaced, or added: o [SYS$LDR]F11BXQP.EXE (Alpha only; new image) o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) o [SYSEXE]BACKUP.EXE (VAX only; new image) o [SYSEXE]DUMP.EXE (new image) o [SYSEXE]EXCHANGE.EXE (new image) o [SYSEXE]F11AACP.EXE (VAX only; new image) o [SYSEXE]F11BXQP.EXE (VAX only; new image) o [SYSEXE]MTAAACP.EXE (new image) o [SYSEXE]STABACKUP.EXE (VAX only; new image) o [SYSEXE]VERIFY.EXE (new image) o [SYSLIB]CLUE$SDA.EXE (Alpha only; new image) o [SYSLIB]LBRSHR.EXE (new image) o [SYSLIB]LIBRTL.EXE (new image) o [SYSLIB]LIBRTL2.EXE (VAX only; new image) o [SYSLIB]LIBRTL_INSTRUMENTED.EXE (VAX only; new image) o [SYSLIB]STARLET.OLB (updated with LIB$DATE_ARITHMETIC and LIB$DATE_CVT) 2 o [SYSLIB]TECOSHR.EXE (VAX only; new image) o [SYSLIB]TECOSHR_TV.EXE (Alpha only; new image) o [SYSUPD]VMS$REMEDIAL_ID.EXE (new image) This new image is provided for installing any future remedial kits that contain one or more images from the ALPY2K02_062 or VAXY2K02_062 kit. 2 Conditions Addressed in This Kit These release notes identify certain conditions you should be aware of when preparing your OpenVMS environment for the year 2000. This kit contains minor modifications to several older components of the operating system; other conditions are simply noted here, but need no changes. Release notes are included for the following facilities that run on the OpenVMS platform: o Crash Log Utility Extractor (CLUE) (Alpha only; see Section 2.1) o EXCHANGE (See Section 2.2) o RSX-11 backwards compatible code: - File system $QIO interface (See Section 2.3.1) - ODS-1 file format (See Section 2.3.2) o LIB$ run-time library (See Section 2.4) o TECO editor (See Section 2.5) The TECO problem actually does not occur until 2028, but Andy figured he'd just go right ahead and fix it for you now because he expects to be retired by then! This kit also includes fixes unrelated to the year 2000 for the Analyze/Disk_Structure utility, the Files-11 XQP file system, magnetic tape ACP (Alpha only), and the LIB$ Run-Time Library. These fixes were released earlier in separate kits, but now have been incorporated into this kit. Release notes from those kits are included in Appendix A (VAX kits) and Appendix B (Alpha kits). 2.1 Crash Log Utility Extractor (CLUE) (Alpha Only) The CLUE history listing file contains a 2-digit year format in its file name, which has this format: CLUE$node_ddmmyy_hhmm.LIS This file format poses no year 2000 problem in itself, but the code that generates this date has been changed from using a subtract operation to using a modulo function so that the correct date will still be calculated in the year 2000. This change has no visible effect on the file name format. 3 2.2 EXCHANGE Utility When the EXCHANGE utility is used to transfer files between OpenVMS and RT-11 or DOS-11 systems, date problems could occur starting in the year 2004 for RT-11 and in the year 2036 for DOS-11. NOTE RT-11 volumes are also used as console storage media on certain older VAX systems. This kit contains an enhancement to EXCHANGE that makes the RT-11 date format continue to function correctly until the year 2099. NOTE DIGITAL transferred the RT-11 operating system, along with other PDP-11 software, to Mentec in 1994. 2.3 RSX-11 Backwards Compatible Code The following sections describe conditions you should be aware of if you interoperate with RSX-11 or if you use RSX-11 software on your OpenVMS system. 2.3.1 File System $QIO Interface The file system $QIO interface supports several attributes for RSX-11 compatibility. Of these, ATR$C_EXPDAT and ATR$C_ASCDATES return the file creation date, revision date, and expiration date using 2-digit years. These attributes are not normally used by native code and can be replaced with the following documented, compliant interfaces: ATR$C_CREDATE ATR$C_EXPDATE ATR$C_REVDATE The file system $QIO interface is provided by the following file systems: DIGITAL TCP/IP Network File System (NFS) client Distributed File System (DECdfs) Magnetic tape ACP OpenVMS ODS-1 file system (see Section 2.3.2) OpenVMS ODS-2 file system 4 2.3.2 ODS-1 File Header Format and Utility Support For RSX-11 compatibility, OpenVMS VAX supports ODS-1 file format disk volumes. The ODS-1 file system uses a 2-digit year format internally, and current implementations have limitations for the year 2000. The magnetic tape ACP also returns an ODS-1 format file header in response to an application request for the ATR$C_HEADER attribute. This feature is supported on both VAX and Alpha. ODS-1 data structures use a 2-digit year (ddmmmyy) in the following items: o ODS-1 file header: FI1$T_CREDATE FI1$T_CRETIME FI1$T_EXPDATE FI1$T_REVDATE FI1$T_REVTIME o ODS-1 home block: HM1$T_CREDATE The OpenVMS VAX file system and the following OpenVMS utilities that support the ODS-1 file system format have been modified to correctly interpret these 2-digit years until the year 2057: Analyze/Disk_Structure Utility Backup Utility Dump Utility Librarian (LBR) routines NOTE Even though we are updating the ODS-1 code for the year 2000, DIGITAL strongly recommends that users of ODS-1 formatted media move to a newer file format by the year 2000. 2.4 LIB$ Run-Time Library In the run-time library, the LIB$CONVERT_DATE_STRING routine allows the user to select a 2-digit year format (as well as many others). This routine interprets 2-digit years as belonging to the century in which the system is currently running (according to the system clock). For example, in the 1900s, 61 is interpreted as 1961, and starting January 1, 2000, 61 will be interpreted as 2061. If this behavior could produce unexpected results on your system, select one of the alternatives to the 2-digit year format. NOTE This behavior has been documented in the OpenVMS RTL Library (LIB$) Manual since Version 6.0, so we will not change the code. No customer should be penalized for reading the documentation and complying with our stated intentions! 5 2.5 TECO Editor This kit includes two minor changes to the TECO editor. (Who says you can't teach an old dog new tricks!) o The date value in the TECO editor has been extended to a longword so that the year value returned by the Ctrl/B function will not overflow on 01-JAN-2028. o This kit also fixes a TECO problem that is unrelated to dates. The UIC value returned by the 2EJ function was incor- rect if the process UIC had a group or member number greater than 377. For compatibility reasons, the 2EJ value cannot be changed. However, the problem has been fixed by the following changes: - All group and member numbers that exceed a byte are now mapped to 377 (octal). - A 3EJ function has been implemented to return the longword UIC. The following TECO example demonstrates the change. NOTE: The ESCAPE () sequence can be entered on most keyboards by typing Ctrl/[. $ SET UIC [1234,567] $ TECO *3EJ/65536== 1234 *3EJ&65535== 567 3 Kit Installation Kit Installation Rating The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which cus- tomers should apply this remedial kit. (Refer to the attached Disclaimer of Warranty and Limitation of Liability Statement.) Installation Rating: INSTALL_1 - To be installed by all customers. Kit Installation Instructions Before you install this kit, you must first install kit VAXCLUSIO01_062 (for VAX) or ALPCLUSIO01_062 (for Alpha). 6 Then, install kit VAXY2K02_062 (for VAX) or ALPY2K02_062 (for Alpha) using the VMSINSTAL utility. Simply log in to the SYSTEM account and enter the following command at the DCL prompt: For VAX: @SYS$UPDATE:VMSINSTAL VAXY2K02_062 [save-set location] OPTIONS N For Alpha: @SYS$UPDATE:VMSINSTAL ALPY2K02_062 [save-set location] OPTIONS N The save-set location can be a tape drive or a disk directory that contains the kit save set. During the kit installation you will be prompted with options to print and/or display the release notes. Reboot the system after the kit has been successfully installed. If you have other nodes in your OpenVMS Cluster system, they should also be rebooted to make use of the new images. Copyright Information 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 em- bodies the confidential technology of Digital Equipment Corpo- ration. 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 Statement With the exception of the Year 2000 DIGITAL Product Warranty, this patch is provided as is, without warranty of any kind. All expressed or implied conditions, representations, and war- ranties, including any implied warranty of merchantability, fitness for particular purpose, or noninfringement, 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 dam- ages, however caused and regardless of the theory of liability, with respect to any patch made available here or to the use of such patch. 7 APPENDIX A RELEASE NOTES FOR SUPERSEDED VAX KITS This appendix contains release notes that were published with the following VAX kits: o VAXVERI02_062 (Analyze/Disk_Structure Utility) See Section A.1. o VAXF11X02_062 (Files-11 XQP file system) See Section A.2. o VAXLIBR06_070 (LIB$ Run-Time Library) See Section A.3. These kits have been superseded and their contents are now included in this kit. EXCEPTION The VAXLIBR06_070 kit also includes fixes for versions of OpenVMS other than Version 6.2. Only the fixes in that kit that apply to Version 6.2 are included in the VAXY2K02_062 kit. A.1 Analyze/Disk_Structure Utility: Release Notes for Superseded Kits Kit VAXY2K02_062 supersedes kit VAXVERI02_062. This section itemizes the problems that were solved in VAXVERI02_062 and the kits that it superseded. PROBLEMS ADDRESSED IN VAXVERI02_062 KIT: o VERIFY does not flag files, which are directly back linked to themselves, as having invalid backlinks. o VERIFY hangs in an infinite loop during its scan of the directory structure. PROBLEMS ADDRESSED IN VAXVERI01_071 KIT: o Verify has incorrectly 'fixed' the backlink of a lost directory to point to itself. The next time verify is run, it encounters the lost directory and goes into a tight loop following the directory's backlink. PROBLEMS ADDRESSED IN VAXVERI01_062 KIT: o Analyze/disk gives multiple errors of the form, or similar to: %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 3, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 4, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 5, RVN 1 Release Notes for Superseded VAX Kits 9 NOTE: In order to receive this full fix, in addition to this kit, the VAXCLIU04_062 kit or any kits that supersede it, must also be installed. A.2 Files-11 XQP: Release Notes for Superseded Kits Kit VAXY2K02_062 supersedes kit VAXF11X03_062. This section itemizes the problems that were solved in VAXF11X03_062 and the kits that it superseded. PROBLEMS ADDRESSED IN VAXF11X03_062 KIT: o An XQPERR bugcheck occurs when trying to create a file. o A bad FID bugcheck occurs when trying to mark a file header free in the index file bitmap. o There are multiply allocated blocks and file headers on the disk. o Processes hang in an RWAST state while trying to deaccess a file during channel deassignment. o The system hangs during cluster wide cache flushes. o The contents of a header or bitmap block could be corrupted within the block buffer cache. o Failure to take an allocation lock could be ignored. o If a DEACCESS request failed with a SS$_DEADLOCK error, a process could be left in an RWAST state indefinitely. o If a large file is created on a fragmented disk that has quotas enabled and the user needs to use EXQUOTA privilege to allocate the necessary disk space, an internal XQP table can become corrupted. This leads to the following bugcheck: SECAUDERR, Fatal error attempting to perform a security audit o Attempting to queue a maximal length (39.39;5) filename to the XQP for spooling to a symbiont would cause either an infinite CPU loop or the following bugcheck: FILCNTNONZ, Open file count nonzero after process rundown PROBLEMS ADDRESSED IN VAXF11X01_071 KIT: o The problem occurs when a file is deleted while still being accessed by someone. This produces an XQPERR bugcheck when an attempt is made to access the deleted file. o The problem may result in an XQPERR bugcheck which claims that: "all the index buffers are active" during the processing of a directory file. o System Hang. Processes are stalled waiting to perform I/O operations, despite buffer credits being available for use. 10 Release Notes for Superseded VAX Kits PROBLEMS ADDRESSED IN VAXF11X03_070 KIT: o A system could crash with a SECAUD bugcheck whenever ANALYZE/DISK is run on a corrupted disk with auditing turned on. o The XQP bugchecks when a file is accessed for the first time, with cathedral windows, and the accessing process runs out of BYTLM quota. o Window mapping code could incorrectly concatenate extents which ran from one volume to another in a volume set. o XQPERR bugcheck in [F11X]DIRSCNuPDATE_INDEX() when trying to insert index entry into directory index block with DIR$W_TOTALCELLS equal to zero. o Directory FCBs can become stale but invisible to the XQP. The File IDs can then be reused, and if the FCB in question was an extension FCB, the next time the new file is accessed on that node, the XQP bugchecks with the fatal XQPERR 'wrong lockbasis with FCB present'. o If a file is opened for exclusive access on one node in a cluster and a BACKUP/IGNORE=INTERLOCK command is issued to backup the file on that node, after the BACKUP completes the file can be successfully accessed from the other node(s) of the cluster. The BACKUP destroys the exclusive access. o BACKUP and SLS can cause WCBFCBMNG bugchecks when operating on some files. These files are legal, uncorrupted files so they should not repeatedly cause a crash whenever BACKUP or SLS tries to back them up. PROBLEMS ADDRESSED IN VAXF11X02_062 KIT: o The system crashes with a BADFID bugcheck. o File name appears twice in a directory block. o System crashes with a BADDALRQSZ bugcheck. o Multiple allocated blocks being reported after the defragger has been run. o UNXSIGNAL crash due to a corrupt Window Control Block. o File Access Control Lists are corrupted after a failure to allocated an extension File Control Block due to disk quota being exceeded. PROBLEMS ADDRESSED IN VAXF11X01_062 KIT: o On a large, very fragmented disk with little free space and heavy usage, an XQP lock ranking violation can occur on a regular basis. Release Notes for Superseded VAX Kits 11 o Lock Ranking Violation (with EDIT/EDT usage). The problem is caused under the following circumstances: o User B does not have an entry in the quota file. o User A has CONTROL access to user B's files. CONTROL access grants the accessor all the privileges of the objects actual owner. User A can have this access by either: - being a member of the SYSTEM group - having the necessary entry in an ACL. o User A edits one of user B's files using EDIT/EDT. o On a disk with highwater marking enabled, a file is created with several extents, of which any extent, except the last one, exceeds 2 Gb in size. When a write operation is performed on a block in the last extent of the file, the user may see blocks of a different file erased incorrectly. o The user sees an XQPERR bugcheck, with a message in the code 'FCBs must be in ascending order', although with XQP+ there can be an unexpected lock manager error on a DEQ (where the DIRLCKID and PRIMFCB fields of an FCB overlap and we try to DEQ an FCB address). The broken FCB chain in question is invariably for a multi-header directory (produced by PATHWORKS V5 putting lots of ACLs on the directory). o When issuing a set security/volume command from the command line, it is possible to make the XQP crash. o Due to INDEXF.SYS resizing the system may cash with the following errors: o BADFID, ACP file number out of range for this volume o Failed to allocate FID when expected A.3 LIB$ Run-Time Library: Release Notes for Superseded Kits Kit VAXY2K02_062 supersedes kit VAXLIBR06_070, which superseded kit VAXLIBR05_070. However, kit VAXLIBR06_070 included fixes for OpenVMS Version 5.5-2* only, so OpenVMS users did not need to apply VAXLIBR06_070 to Version 6.2 operating systems. Therefore, this section itemizes the OpenVMS Version 6.2 problems that were addressed in kit VAXLIBR05_070 and the kits that it superseded. PROBLEMS ADDRESSED IN VAXLIBR05_070 KIT. o The OpenVMS operating system has a documented delta-time restriction that may cause a serious error in some applications and OpenVMS components beginning on or around 19-MAY-1997. DIGITAL has corrected this potential problem and has provided ECOs (Engineering Change Orders) that remove the delta-time limit. 12 Release Notes for Superseded VAX Kits Applications and OpenVMS components most likely to experience errors are those that pass delta-time arguments with values exceeding 9999 days on system-supplied date routines. The most likely date that these errors will occur is 19-MAY-1997:00:00, which is 10,000 days after the common UNIX time origin of 1-JAN-1970. 5.0.1 Fixed in: V7.1 PROBLEMS ADDRESSED IN VAXLIBR02_070 KIT: o Heaps that are removed from the heap pending list are only merged with the most recently returned heap. This can lead to heap fragmentation. PROBLEMS ADDRESSED IN VAXLIBR01_070 KIT: o LIB$FID_TO_NAME has been modified to ensure that the use of very deep directory trees do not result in the call stack being corrupted. o The 10,000 day limit in LIB$CVT_TO_INTERNAL_TIME causes problems for DECthreads since it is using this routine to convert UNIX times to VAX time. It will fail to work on 19-May-1997. PROBLEMS ADDRESSED IN VAXLIBR02_062 KIT: o When the code was originally written there was no support for node synonyms. Now that the support is there, people are using it The code doesn't get the right value from the network call. PROBLEMS ADDRESSED IN VAXLIBR01_062 KIT: o LIB$CVT_DX_DX returns a status of 00158334 (LIB$_INTOVF) when converting '-2147483648' to quadword. Release Notes for Superseded VAX Kits 13 APPENDIX B RELEASE NOTES FOR SUPERSEDED ALPHA KITS This appendix contains release notes that were published with the following Alpha kits: o ALPVERI02_062 (Analyze/Disk_Structure Utility) See Section B.1. o ALPF11X02_062 (Files-11 XQP file system) See Section B.2. o ALPLIBR06_062 (LIB$ Run-Time Library) See Section B.3. o ALPMTAA01_070 (Magnetic tape ACP) See Section B.4. These kits have been superseded and their contents are now included in this kit. EXCEPTION The ALPMTAA01_070 kit also includes fixes for versions of OpenVMS other than Version 6.2. Only the fixes in that kit that apply to Version 6.2 are included in the ALPY2K02_062 kit. B.1 Analyze/Disk_Structure Utility: Release Notes for Superseded Kits Kit ALPY2K02_062 supersedes kit ALPVERI02_062. This section itemizes the problems that were solved in ALPVERI02_062 and the kits that it superseded. PROBLEMS ADDRESSED IN ALPVERI02_062 KIT: o VERIFY does not flag files, which are directly back linked to themselves, as having invalid backlinks. o VERIFY hangs in an infinite loop during its scan of the directory structure. PROBLEMS ADDRESSED IN ALPVERI01_071 KIT: o Verify has incorrectly 'fixed' the backlink of a lost directory to point to itself. The next time verify is run, it encounters the lost directory and goes into a tight loop following the directory's backlink. Release Notes for Superseded Alpha Kits 15 PROBLEMS ADDRESSED IN ALPVERI01_062 KIT: o ANALYZE/DISK gives multiple errors of the form (or similar to): %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 3, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 4, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 5, RVN 1 In order to receive this full fix, in addition to this kit you must also install the ALPCLIU01_062 kit. B.2 Files-11 XQP: Release Notes for Superseded Kits Kit ALPY2K02_062 supersedes kit ALPF11X02_062. This section itemizes the problems that were solved in ALPF11X02_062 and the kits that it superseded. PROBLEMS ADDRESSED IN ALPF11X02_062 KIT: o An XQPERR bugcheck occurs when trying to create a file. o A bad FID (File ID) bugcheck occurs when trying to mark a file header free in the index file bitmap. o There are multiply allocated blocks and file headers on the disk. o Processes hang in an RWAST state while trying to deaccess a file during channel deassignment. o The system hangs during cluster wide cache flushes. o The contents of a header or bitmap block could be corrupted within the block buffer cache. o Failure to take an allocation lock could be ignored. o If a DEACCESS request failed with a SS$_DEADLOCK error, a process could be left in an RWAST state indefinitely. o If a large file is created on a fragmented disk that has quotas enabled and the user needs to use EXQUOTA privilege to allocate the necessary disk space, an internal XQP table can become corrupted. This leads to the following bugcheck: SECAUDERR, Fatal error attempting to perform a security audit o Attempting to queue a maximal length (39.39;5) filename to the XQP for spooling to a symbiont would cause either an infinite CPU loop or the following bugcheck: FILCNTNONZ, Open file count nonzero after process rundown 16 Release Notes for Superseded Alpha Kits PROBLEMS ADDRESSED IN ALPF11X01_071 KIT: o The problem occurs when a file is deleted while still being accessed by someone. This produces an XQPERR bugcheck when an attempt is made to access the deleted file. o The problem may result in an XQPERR bugcheck which claims that: "all the index buffers are active" during the processing of a directory file. The problem occurs when no free directory index BFRD's are found on the first pass through MAKE_DIRINDX. The thread then stalls to allow some of the BFRD's to be freed, but doesn't release the cache lock which would allow others to do this. This means that if no free BFRD was found on the first try then none will be found on subsequent tries either, and the bugcheck will occur. PROBLEMS ADDRESSED IN ALPF11X03_070 KIT: o BACKUP and SLS can cause WCBFCBMNG bugchecks when operating on some files. These files are legal, uncorrupted files so they should not repeatedly cause a crash whenever BACKUP or SLS tries to back them up. o A system could crash with a SECAUD bugcheck whenever ANALYZE/DISK is run on a corrupted disk with auditing turned on. o The XQP bugchecks when a file is accessed for the first time, with cathedral windows, and the accessing process runs out of BYTLM quota. o Window mapping code could incorrectly concatenate extents which ran from one volume to another in a volume set. o XQPERR bugcheck in [F11X]DIRSCNuPDATE_INDEX() when trying to insert index entry into directory index block with DIR$W_TOTALCELLS equal to zero. o Directory FCBs can become stale but invisible to the XQP. The File IDs can then be reused, and if the FCB in question was an extension FCB, the next time the new file is accessed on that node, the XQP bugchecks with the fatal XQPERR 'wrong lockbasis with FCB present'. o If a file is opened for exclusive access on one node in a cluster and a BACKUP/IGNORE=INTERLOCK command is issued to backup the file on that node, after the BACKUP completes the file can be successfully accessed from the other node(s) of the cluster. The BACKUP destroys the exclusive access. PROBLEMS ADDRESSED IN ALPF11X02_070 KIT: o The ALPF11X01_070 remedial kit did not install on systems running OpenVMS Alpha V6.2-1H1, as it should have. Release Notes for Superseded Alpha Kits 17 PROBLEMS ADDRESSED IN ALPF11X01_062 KIT: o The system crashes with a BADFID bugcheck. o File name appears twice in a directory block. o System crashes with a BADDALRQSZ bugcheck. o Multiple allocated blocks being reported after the defragger has been run. o UNXSIGNAL crash due to a corrupt Window Control Block. o File Access Control Lists are corrupted after a failure to allocated an extension File Control Block due to disk quota being exceeded. o The system crashes with 'BADFID, ACP file number out of range for this volume'. The system crashes with 'Failed to allocate FID when expected'. This problem is fixed in OpenVMS Alpha V7.0. o On a disk with highwater marking enabled, a file is created with several extents, of which any extent, except the last one, exceeds 2 Gb in size. When a write operation is performed on a block in the last extent of the file, the user may see blocks of a different file erased incorrectly. This problem is fixed in OpenVMS Alpha V7.0. o Lock Ranking Violation when using EDIT/EDT. The problem is caused under the following circumstances: - User B does not have an entry in the quota file. - User A has CONTROL access to user B's files. CONTROL access grants the accessor all the privileges of the objects actual owner. User A can have this access by either: - being a member of the SYSTEM group - having the necessary entry in an ACL. - User A edits one of user B's files using edit/EDT. This problem is fixed in OpenVMS Alpha V7.0. o On a large, very fragmented disk with little free space and heavy usage, an XQP lock ranking violation can occur on a regular basis. This problem is fixed in OpenVMS Alpha V7.0. 18 Release Notes for Superseded Alpha Kits B.3 LIB$ Run-Time Library: Release Notes for Superseded Kits Kit ALPY2K02_062 supersedes kit ALPLIBR06_062. This section itemizes the problems that were solved in ALPLIBR06_062 and the kits that it superseded. PROBLEMS ADDRESSED IN ALPLIBR06_062 KIT: o DEBUG links LIBRTL.OLB into its DEBUG.EXE image. The LIB$CALLING_STANDARD routines included can ACCVIO when trying to walk the call chain or write to a call's invocaition context block on a corrupt stack. These ACCVIOs have now been observed from DEBUG CALL commands from certain register frames. In order to receive this full fix, the ALPDEBU02_062 (or supersedant) remedial kit must also be installed. PROBLEMS ADDRESSED IN ALPLIBR05_062 KIT: o Because we are no longer issuing multi-version kits, the kit ALPLIBR05_070, which was for OpenVMS Alpha versions V6.1 through V7.0, has been broken down such that there is a kit for each version. ALPLIBR05_062 is the V6.2 portion of ALPLIBR05_070. There are no new fixes in this kit. PROBLEMS ADDRESSED IN ALPLIBR05_070 KIT: o The OpenVMS operating system has a documented delta-time restriction that may cause a serious error in some applications and OpenVMS components beginning on or around 19-MAY-1997. DIGITAL has corrected this potential problem and has provided ECOs (Engineering Change Orders) that remove the delta-time limit. Applications and OpenVMS components most likely to experience errors are those that pass delta-time arguments with values exceeding 9999 days on system-supplied date routines. The most likely date that these errors will occur is 19-MAY-1997:00:00, which is 10,000 days after the common UNIX time origin of 1-JAN-1970. PROBLEMS ADDRESSED IN ALPLIBR04_070 KIT: o Heaps that are removed from the heap pending list are only merged with the most recently returned heap. This can lead to heap fragmentation. PROBLEMS ADDRESSED IN ALPLIBR03_070 KIT: o LIBRTL.EXE was not replaced in IMAGELIB.OLB. Release Notes for Superseded Alpha Kits 19 PROBLEMS ADDRESSED IN ALPLIBR02_070 KIT: o The OpenVMS operating system has a documented delta-time restriction that may cause a serious error in some applications and OpenVMS components beginning on or around 19-MAY-1997. DIGITAL has corrected this potential problem and has provided ECOs (Engineering Change Orders) that remove the delta-time limit. Applications and OpenVMS components most likely to experience errors are those that pass delta-time arguments with values exceeding 9999 days on system-supplied date routines. The most likely date that these errors will occur is 19-MAY-1997:00:00, which is 10,000 days after the common UNIX time origin of 1-JAN-1970. o LIB$STAT_TIMER produces incorrect results. Elapsed time jumps significantly from the initial value to the next returned value. o Problem noticed using OTS$DIV_PK_LONG or OTS$DIV_PK_SHORT LIBRTL routine. Packed value 11259 divided by 1, yielded 1125.90083841. Only a handful of numbers cause bad results. PROBLEMS ADDRESSED IN ALPLIBR03_062 KIT: o When setting host into a DECnet PhaseV system, the logical name SYS$REM_NODE is incorrectly set. When the code was originally written, there was no support for node synonyms. The code doesn't get the right values from the system call. B.4 Magnetic Tape ACP Release Notes Kit ALPY2K02_062 supersedes kit ALPMTAA01_070. This section itemizes the OpenVMS Version 6.2 problems that were solved in ALPMTAA01_070 and the kits that it superseded. PROBLEMS ADDRESSED IN ALPMTAA01_070 KIT: o MTAACP can hang during multivolume copy operations. PROBLEMS ADDRESSED IN ALPMTAA01_062 KIT o The system crashes with NOBVPVCB. o The system crashes with an XQPERR while dismounting a MAD drive. 20 Release Notes for Superseded Alpha Kits