**************************** ECO SUMMARY INFORMATION **************************** Release Date: 6-JAN-2005 Kit Name: DEC-AXPVMS-VMS731_RMS-V0600--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 3648 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS731_RMS-V0500 Mandatory Kit Dependencies: VMS731_UPDATE-V0400 VMS731_PCSI-V0200 Optional Kit Dependencies: None. VMS731_RMS-V0600.PCSI-DCX_AXPEXE Checksum: 4019625415 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_RMS-V0600 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_RMS-V0600 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 V7.3-1 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS731_RMS-V0500 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS731_PCSI-V0200 - VMS731_UPDATE-V0400 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 FILES PATCHED OR REPLACED: o [SYSEXE]ANALYZRMS.EXE (new image) Image Identification Information image name: "ANALYZRMS" image file identification: "X-10" image file build identification: "XA2Q-0060030000" link date/time: 12-MAY-2004 10:17:00.23 linker identification: "A11-50" Overall Image Checksum: 4068817476 o [SYSEXE]CONVERT.EXE (new image) Image Identification Information image name: "CONVERT" image file identification: "X-8" image file build identification: "XA2Q-0060030003" link date/time: 2-APR-2004 14:21:21.84 linker identification: "A11-50" Overall Image Checksum: 3113940153 o [SYSLIB]CONVSHR.EXE (new image) Image Identification Information image name: "CONVSHR" image file identification: "X1-012" image file build identification: "XA2Q-0060030003" link date/time: 2-APR-2004 14:21:17.23 linker identification: "A11-50" Overall Image Checksum: 2486659163 o [SYSEXE]CREATEFDL.EXE (new image) Image Identification Information image name: "CREATEFDL" image file identification: "X-5" image file build identification: "XA9J-0060030002" link date/time: 29-SEP-2004 21:40:21.51 linker identification: "A11-50" Overall Image Checksum: 1693511686 Page 3 o [SYSLIB]FDLSHR.EXE (new image) Image Identification Information image name: "FDLSHR" image file identification: "X-18" image file build identification: "XA9J-0060030002" link date/time: 29-SEP-2004 21:26:25.49 linker identification: "A11-50" Overall Image Checksum: 1590067482 o [SYS$LDR]RMS.EXE (new image) Image Identification Information image name: "RMS" image file identification: "V1.0" image file build identification: "XA9J-0060030018" link date/time: 4-OCT-2004 15:29:58.90 linker identification: "A11-50" Overall Image Checksum: 1887054084 o [SYSLIB]SDARMS$SHARE.EXE (new image) Image Identification Information image name: "SDARMS$SHARE" image file identification: "X-9" image file build identification: "XA9J-0060030018" link date/time: 4-OCT-2004 15:30:01.51 linker identification: "A11-50" Overall Image Checksum: 3030164639 o [SYS$LDR]RMSDEF.STB (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_RMS-V0600 KIT 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 Fix to prevent a SSRVEXCEPT bugcheck when accessing a file with global buffers enabled. Page 4 6.2.1.1 Problem Description: The system may experience a System Service Exception bugcheck (Reserved Operand Fault) when a global buffer that is enabled on a file has been invalidated. Images Affected: - [SYS$LDR]RMS.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) QXCM1000088294,QXCM1000189599,QXCM1000210396 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: In a rare code path taken to invalidate a Global Buffer Descriptor (GBD), a correction added to the VMS732_RMS-V0100 kit used the wrong register for accessing and decrementing the GBD's usecnt offset. This resulted in referencing a wrong cell in another structure (the Global Buffer Header), which ended up being the relative address of the start of the array of GBD's. If the decrement of the GBD start address left the relative offset value on a non-quadword aligned boundary, a system service exception would occur on a subsequent reference using this address. 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.1.5 Work-arounds: None. 6.2.2 Fix to prevent a PGFIPLHI bugcheck when RMS updates its directory path cache. Page 5 6.2.2.1 Problem Description: A PGFIPLHI system bugcheck may be signaled when RMS attempts to store a directory oriented device's directory sequence number into the RMS directory path cache. Images Affected: - [SYS$LDR]RMS.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) 75-102-1796 6.2.2.3 Problem Analysis: RMS and the file system coordinate their view of the directory structure on a device through the implementation of a directory sequence number associated with the device. An RMS Kernel mode routine that executes at elevated Interrupt Priority Level (IPL) stores the contents of the device's Unit Control Block (UCB) directory sequence number within the RMS directory path cache that is located in the process's P1 address space. Under somewhat rare conditions, there is a possibility that this location may not have been paged into memory at the time of the access resulting in a pagefault at elevated IPL. The directory sequence number is now stored on the stack until IPL is once again lowered to a level that is more tolerant of page faults. 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.2.5 Work-arounds: None. Page 6 6.2.3 Fix to prevent failures when printing or copying a file to a spooled ODS-5 device. 6.2.3.1 Problem Description: Printing or copying a file to a device that is spooled to an ODS-5 volume will fail with the following errors: -RMS-E-DAC, ACP file deaccess failed during $CLOSE -SYSTEM-E-INVFILFOROP, invalid file specification for operation Images Affected: - [SYS$LDR]RMS.EXE 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) CFS.106522 6.2.3.2.2 QAR(s) None. 6.2.3.3 Problem Analysis: These errors were the result of a change to the RMS directory path cache code in support of merging POSIX support into RMS. For spooled devices, RMS was applying defaults to missing portions of the file specification, including a defaulted directory. Prior to the V7.3-1 change, this was a harmless operation since the directory portion of the specification was ignored for spooled devices. Since spooled files are not entered into a directory, a change has been implemented to bypass the validation of the directory for a spooled device. This correction addresses an alternate code path that was overlooked in an earlier fix. 6.2.3.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 Page 7 6.2.3.5 Work-arounds: None. 6.2.4 Fix to provide compatibility with OpenVMS V8.2 generated FDL files. 6.2.4.1 Problem Description: OpenVMS V8.2 introduces a new keyword to the contents of an FDL file which is incompatible with prior versions of the FDL parser. Without this update, accessing the analysis portion of an FDL file generated on OpenVMS V8.2 from V7.3-2 will report the following fatal error condition: $EDIT/FDL FILE.FDL Parsing Definition File %FDL-E-UNPRIKW, unrecognized primary keyword in statement 89 \LONGEST\ Images Affected: - [SYSLIB]FDLSHR.EXE - [SYSEXE]CREATEFDL.EXE 6.2.4.2 CLDs, and QARs reporting this problem: 6.2.4.2.1 CLD(s) CFS.106931, CFS.106605 6.2.4.2.2 QAR(s) None. 6.2.4.3 Problem Analysis: The FDL analysis files have been enhanced in OpenVMS V8.2 to include information about the longest record length observed in a variable record length indexed file when a maximum record size has not been specified. This addition is through the introduction of a new analysis keyword, "LONGEST_RECORD_LENGTH". This update makes these new entries compatible with the FDL parser in the OpenVMS V7.3-2 version by ignoring these entries in the FDL file. Without this update, compatibility can be restored by manually editing the FDL Page 8 file with a standard text editor to remove the following line from the ANALYSIS_OF_KEY 0 section: LONGEST_RECORD_LENGTH ### 6.2.4.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.4.5 Work-arounds: Edit the FDL file using a standard text editor and remove the offending lines. 6.2.5 Fix to prevent erroneous ANALYZE/RMS errors for SIDR entries with RU deleted records. 6.2.5.1 Problem Description: Attempts to analyze a prologue 3 indexed file with a secondary key that does not allow duplicates can result in the following erroneous error being reported by ANALYZE/RMS. This can occur if an RU transaction has been aborted following a change in the key's value: *** VBN 55: SIDR entry at offset %X'003B' is invalid for a no duplicates key. Images Affected: - [SYSEXE]ANALYZRMS.EXE 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.2.1 CLD(s) CFS.107203 6.2.5.2.2 QAR(s) None. Page 9 6.2.5.3 Problem Analysis: The ANALYZE/RMS utility was reporting false errors against the SIDR entries of a key marked for no duplicates when the file had experienced an aborted RU transaction that had changed an alternate key value. This sequence of events could result in deleted and/or ru_delete entries following the valid entry in the SIDR array. This change corrects the prior assumption that the valid entry will always be the last within the SIDR array. 6.2.5.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.5.5 Work-arounds: None. 6.2.6 Fix to prevent CONVERT/PAD from failing to insert short alternate key records. 6.2.6.1 Problem Description: Attempts to convert a variable length record file to a fixed length indexed file with multiple keys using the /PAD option could result in some records becoming inaccessible through an alternate key. Images Affected: - [SYSEXE]CONVERT.EXE - [SYSLIB]CONVSHR.EXE 6.2.6.2 CLDs, and QARs reporting this problem: 6.2.6.2.1 CLD(s) CFS.106222 6.2.6.2.2 QAR(s) None. Page 10 6.2.6.3 Problem Analysis: CONVERT utilizes a common routine for reading the input file and adjusting the records for padding etc. when appropriate. Using the varying input record's short length rather than the fixed output length resulted in the wrong size being used to validate records. This could occur under somewhat rare conditions if the data records were shorter than the alternate key value. Although no user data was lost, some records became inaccessible through the alternate key. 6.2.6.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.6.5 Work-arounds: None. 6.2.7 Fix to prevent CONVERT from creating a corrupt output file when using an invalid FDL file. 6.2.7.1 Problem Description: Creation of an output file by the CONVERT utility could generate a corrupt file if an errant FDL file is utilized. No warning is issued by CONVERT; however, an ANALYZE/RMS of the file following the conversion displays errors. Images Affected: - [SYSEXE]CONVERT.EXE - [SYSLIB]CONVSHR.EXE 6.2.7.2 CLDs, and QARs reporting this problem: 6.2.7.2.1 CLD(s) CFS.106605 6.2.7.2.2 QAR(s) None. Page 11 6.2.7.3 Problem Analysis: The CONVERT utility was erroneously truncating some records without any warning when a bucket size had been specified by an FDL file that was insufficient to contain the file's longest records. If data record compression were enabled on the file, the resulting record would report compression errors if an ANALYZE/RMS were performed. 6.2.7.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.7.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed in previously released VMS731_RMS ECO kits can be found in the following files: o [SYSHLB]VMS731_RMS-V0100 o [SYSHLB]VMS731_RMS-V0200 o [SYSHLB]VMS731_RMS-V0300 o [SYSHLB]VMS731_RMS-V0400 o [SYSHLB]VMS731_RMS-V0500 8 INSTALLATION INSTRUCTIONS 8.1 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS731_RMS-V0600.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the Page 12 decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification 8.2 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 VMS731_RMS /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] 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. 8.3 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 Page 13 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=V6.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_RMS-V0600 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_RMS/PRODUCER=DEC/BASE=AXPVMS- /VER=V6.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 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 Page 14 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.