**************************** ECO SUMMARY INFORMATION **************************** Release Date: 28-OCT-2004 Kit Name: DEC-AXPVMS-VMS731_VERIFY-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 640 blocks Installation Rating: INSTALL_3 Superseded Kits: None. Mandatory Kit Dependencies: VMS731_UPDATE-VO400 VMS731_PCSI-V0200 Optional Kit Dependencies: None. VMS731_VERIFY-V0100.PCSI-DCX_AXPEXE Checksum: 2569766523 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_VERIFY-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_VERIFY-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 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: No reboot is necessary after installation of this kit. 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: None. 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: - VMS731_PCSI-V0200 - VMS731_UPDATE-VO400 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]VERIFY.EXE (new image) Image Identification Information image name: "VERIFY" image file identification: "X-30" image file build identification: "XA9J-0060030001" link date/time: 4-OCT-2004 15:30:01.74 linker identification: "A11-50" Overall Image Checksum: 2194372859 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS31_VERIFY-V0100 KIT None. 6.1 Problems addressed in this kit 6.1.1 ANALYZE/DISK/READ_CHECK does not read cached files 6.1.1.1 Problem Description: When performing an ANALYZE /DISK /READ_CHECK, the utility can read data from cache instead of verifying that the on disk content is readable. Also, as all the files are read, the caches (VIOC or XFC) are filled with data of not often read files, possibly forcing out data of more recently accessed files. Images Affected: - [SYSEXE]VERIFY.EXE 6.1.1.2 CLDs, and QARs reporting this problem: Page 3 6.1.1.2.1 CLD(s) None. 6.1.1.2.2 QAR(s) None. 6.1.1.3 Problem Analysis: In order to prevent the thrashing of the VIOC or XFC cache and to force the reading of the data that is on disk. With this change, VERIFY will now uses IO$M_NOVCACHE when reading data from files during ANALYZE/DISK/READ. This also prevents ANALYZE/DISK/READ from filling the VIOC or XFC caches with data not normally read. 6.1.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.1.1.5 Work-arounds: None. 6.1.2 ANALYZE/DISK gives %ANALDISK-W-CHKSCB error 6.1.2.1 Problem Description: An ANALYZE/DISK disk_name command can return the following error during processing: %ANALDISK-W-CHKSCB, invalid storage control block, RVN 1 Images Affected: - [SYSEXE]VERIFY.EXE 6.1.2.2 CLDs, and QARs reporting this problem: Page 4 6.1.2.2.1 CLD(s) None. 6.1.2.2.2 QAR(s) None. 6.1.2.3 Problem Analysis: The volume Storage Control Block has different geometry information (Sectors, Tracks, Cylinders) than that of the current volume. There are circumstances where the controller or shadowing software can change the S/C/T values for the device. The actual values only need to add up to a correct maxblock value. 6.1.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.1.2.5 Work-arounds: None. 6.1.3 ANALYZE /DISK fails with ANALDISK-F-BADBITMAP error 6.1.3.1 Problem Description: If a volume is initialized on OpenVMS V7.3-2 using the /LIMIT qualifier, or changed with a SET VOLUME/LIMIT command, an ANALYZE/DISK of the volume on a node running OpenVMS V7.3-1 will fail with the following error: $ ANALYZE/DISK disk_name ANALDISK-F-BADBITMAP, BITMAP.SYS is wrong size or not contiguous, RVN 1 The volume is still usable on OpenVMS V7.3-1, but VERIFY cannot analyze it. Images Affected: - [SYSEXE]VERIFY.EXE Page 5 6.1.3.2 CLDs, and QARs reporting this problem: 6.1.3.2.1 CLD(s) 70-3-8179,QXCM1000198395 6.1.3.2.2 QAR(s) None. 6.1.3.3 Problem Analysis: Dynamic Volume Expansion (DVE) sets the size of BITMAP.SYS to accommodate a much larger disk than the physical disk. The calculation for sizing BITMAP.SYS did no accommodate this for V7.3-1. 6.1.3.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.1.3.5 Work-arounds: None. 7 INSTALLATION INSTRUCTIONS 7.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_VERIFY-V0100.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 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, Page 6 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 7.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_VERIFY /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. 7.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 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/SAVE_RECOVERY_DATA Page 7 o De-assign the logical names assigned For example, a sample command file to install the VMS731_VERIFY kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_VERIFY/PRODUCER=DEC/BASE=AXPVMS- /VER=V1.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit 8 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 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.