**************************** ECO SUMMARY INFORMATION **************************** Release Date: 26-JUL-2007 Kit Name: DEC-AXPVMS-VMS83A_BACKUP-V0300--4.PCSI$COMPRESSED;2 Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 1357 blocks Installation Rating: INSTALL_3 Reboot Required: No Superseded Kits: VMS83A_BACKUP-V0200 Mandatory Kit Dependencies: VMS83A_UPDATE-V0200 or later Optional Kit Dependencies: None Checksums: VMS83A_BACKUP-V0300.ZIPEXE Checksum: 3371529798 DEC-AXPVMS-VMS83A_BACKUP-V0300--4.PCSI$COMPRESSED;2 Checksum: 1898410023 VMS83A_BACKUP-V0300.ZIPEXE MD5 Checksum: 8E7BA34C0AF8738C2A1B071527FBAB99 DEC-AXPVMS-VMS83A_BACKUP-V0300--4.PCSI$COMPRESSED;2 MD5 Checksum: 79FCB0B08E9EFEF4D872AC787E833440 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_BACKUP-V0300 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 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 V8.3 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS83A_BACKUP-V0200 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS83A_UPDATE-V0200 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None Page 2 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83A_BACKUP-V0300 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Alignment Faults 5.2.1.1 Problem Description: Alignment faults, resulting in performance degradation, occur when executing BACKUP commands. Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) 75-13-1556 5.2.1.3 Problem Analysis: BACKUP reads the data from an unaligned address. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. Page 3 5.2.2 MOUNT-F-FILESTRUCT Error When Mounting Disk 5.2.2.1 Problem Description: When restoring a backup save set that was done to disk or tape without the /NOINIT qualifier, if the target disk is initialized with a different cluster factor than the source disk, the restore succeeds but mounting the disk will fail with the following error: MOUNT-F-FILESTRUCT, unsupported file structure level Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000359713 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: BACKUP was calculating a smaller size for BITMAP.SYS, which was causing the MOUNT to fail with the FILESTRUCT error message. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.2.5 Work-arounds: None. 5.2.3 BACKUP-E-INVRECTYP Error Page 4 5.2.3.1 Problem Description: When a backup is initiated with the /JOURNAL and /DATA_FORMAT=COMPRESS qualifiers, BACKUP fails, displaying the below error messages. %BACKUP-E-INVRECTYP, invalid record type in save set %BACKUP-E-INVRECSIZ, invalid record size in save set Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000371506 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: BACKUP was attempting to journal a compressed record, resulting in the failure. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.3.5 Work-arounds: None. 5.2.4 SYSTEM-F-ACCVIO Error 5.2.4.1 Problem Description: BACKUP fails with a SYSTEM-F-ACCVIO error if PGFLQUOTA is lower than WSQUOTA. Images Affected: - [SYSLIB]BACKUPSHR.EXE Page 5 - [SYSMSG]SYSMGTMSG.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000356862 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: BACKUP allocates virtual pages for internal buffers at an early stage of processing based on memory available at that time. So, at a later point, virtual pages are not available for other operations resulting in the ACCVIO. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.4.5 Work-arounds: None. 5.2.5 BACKUP Case Handling Problems 5.2.5.1 Problem Description: Restore of a saveset from tape to disk fails when the process's case is set to blind and parse style set to extended. Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.5.2 CLDs, and QARs reporting this problem: Page 6 5.2.5.2.1 CLD(s) QXCM1000369647 5.2.5.2.2 QAR(s) 75-111-91 5.2.5.3 Problem Analysis: BACKUP does a string compare of the saveset name specified in the command line with the name internally stored in the saveset. This comparison is not case sensitive. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.5.5 Work-arounds: None. 5.2.6 %BACKUP-F-ENCRYPERR Error Using AES Encryption 5.2.6.1 Problem Description: While performing an image BACKUP to a tape with the /ENCRYPT and /LIST qualifiers, if the algorithm for encryption is specified as AES, BACKUP fails with following error during span-over: %BACKUP-F-ENCRYPERR, error encountered in encryption facility while encrypting a backup record -ENCRYPT-F-CONNOTINI, context area not yet initialized Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.6.2 CLDs, and QARs reporting this problem: Page 7 5.2.6.2.1 CLD(s) QXCM1000403836 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: When span-over takes place, if the encrypted buffer is partially written to the tape, BACKUP writes the remaining encrypted buffer contents to next tape. As the /LIST qualifier is specified, BACKUP will try to decrypt the encrypted buffer before listing the contents of the buffer. During this stage the decryption context is not available, resulting in failure. 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.6.5 Work-arounds: None. 5.2.7 BACKUP Failure During Verification Pass 5.2.7.1 Problem Description: BACKUP fails with the following error during the verification pass if the /INPUT_FILE qualifier is used and the files are present on multiple disks: %BACKUP-E-OPENIN,error opening ... as input -SYSTEM-W-NOSUCHFILE, no such file Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.7.2 CLDs, and QARs reporting this problem: Page 8 5.2.7.2.1 CLD(s) QXCM1000402321 5.2.7.2.2 QAR(s) None. 5.2.7.3 Problem Analysis: BACKUP maintains a linked list to hold the list of files specified in the input file. During processing of a file, a channel is open for the device on which the file is present. This channel is closed if the next entry in the list is present on a different disk and a channel will be opened for the disk on which the next file resides. When processing the last file in the list, BACKUP deletes all the previous entries in the linked list. As a result of this, during the verification phase BACKUP will not have the complete details of the files, and will search for all the files on the channel opened for the device on which the last file was present, resulting in the failure. 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.7.5 Work-arounds: None. 5.2.8 BACKUP Fails With %BACKUP-E-CREDIRERR, Error 5.2.8.1 Problem Description: BACKUP fails with following error when the SYSGEN parameter CHANNELCNT is set to a lower value than the process quota FILLM value: %BACKUP-E-CREDIRERR, error creating directory -RMS-F-CHN, assign channel system service request failed Images Affected: - [SYSLIB]BACKUPSHR.EXE - [SYSMSG]SYSMGTMSG.EXE Page 9 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) None. 5.2.8.2.2 QAR(s) 75-109-1342 5.2.8.3 Problem Analysis: When the SYSGEN parameter CHANNELCNT value is lower than the process quota FILCNT value, BACKUP preserves the CHANNELCNT value as FILCNT. BACKUP was not subtracting the number of channels already opened by the process, and an overhead value (required for /LIST, /JOURNAL, /SAVE etc. qualifiers) during calculation of FILCNT, instead it was assigning the value of CHANNELCNT directly to FILCNT. 5.2.8.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.8.5 Work-arounds: None. 5.2.9 Network BACKUP/VERIFY Fails with %BACKUP-F-READERRS Error 5.2.9.1 Problem Description: When a network BACKUP is initiated with the /VERIFY qualifier to create a saveset on remote system, BACKUP fails with the following error message during the verification phase: %BACKUP-F-READERRS, excessive error rate reading ... -RMS-F-IOP, operation invalid for file organization or device Images Affected: - [SYSLIB]BACKUPSHR.EXE Page 10 5.2.9.2 CLDs, and QARs reporting this problem: 5.2.9.2.1 CLD(s) QXCM1000371713 5.2.9.2.2 QAR(s) None. 5.2.9.3 Problem Analysis: BACKUP was attempting to perform a block I/O (FAB$V_BIO)operation during the verification phase, resulting in the reported error. 5.2.9.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.9.5 Work-arounds: None. 5.2.10 BACKUP/DATA_FORMAT=COMPRESS Displays Wrong Informational Message 5.2.10.1 Problem Description: BACKUP/DATA_FORMAT=COMPRESS displays the wrong informational message when creating the compressed saveset when no files are selected for the BACKUP operation. For example: BACKUP *.TXT TXT.CBCK/SAVE/DATA_FORMAT=COMPRESS %BACKUP-W-NOFILES, no files selected from SYS$SYSDEVICE:[TEST]*.TXT;* %BACKUP-I-COMPRESS, data compressed by 99% Since no files were selected and no data was compressed, BACKUP should not display the "%BACKUP-I-COMPRESS, data compressed by 99%" message. Images Affected: - [SYSLIB]BACKUPSHR.EXE Page 11 5.2.10.2 CLDs, and QARs reporting this problem: 5.2.10.2.1 CLD(s) None. 5.2.10.2.2 QAR(s) 75-109-1847 5.2.10.3 Problem Analysis: BACKUP is not checking whether any files are selected for the BACKUP operation before displaying the erroneous informational message. 5.2.10.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.10.5 Work-arounds: None. 5.2.11 Incremental Restore Fails With %BACKUP-E-INCENTERR Error 5.2.11.1 Problem Description: During an incremental restore operation to a ODS5 volume, if the BACKUP saveset contains a file name in upper case and the same file name is present on the disk in lower case, the restore fails with the following error: %BACKUP-E-INCENTERR, error creating directory entry... -SYSTEM-W-DUPFILENAME, duplicate file name For example, a full (image) BACKUP contains a file for DISK:[storage]a.txt;1. In the incremental BACKUP this file has been renamed as DISK:[storage]A.TXT;1. After restoring the full BACKUP on an ODS5 volume, an incremental restore to restore the A.TXT file will fail with the above error. Images Affected: - [SYSLIB]BACKUPSHR.EXE Page 12 5.2.11.2 CLDs, and QARs reporting this problem: 5.2.11.2.1 CLD(s) QXCM1000398339 5.2.11.2.2 QAR(s) None. 5.2.11.3 Problem Analysis: BACKUP performs a directory scan during a restore operation to check for the existence of a file before restoring the file from the saveset. This directory scan is not case sensitive. Therefore, BACKUP sees no difference between lower case name of the file on the disk and the upper case file name of the file in the incremental BACKUP. 5.2.11.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.11.5 Work-arounds: None. 5.2.12 Wildcard Listing of Savesets Fails With %BACKUP-F-OPENIN error 5.2.12.1 Problem Description: A wildcard listing of the savesets on the tape fails with the following error: %BACKUP-F-OPENIN, error opening :[000000]*.*; as input, -SYSTEM-W-NOSUCHFILE, no such file Images Affected: - [SYSLIB]BACKUPSHR.EXE Page 13 5.2.12.2 CLDs, and QARs reporting this problem: 5.2.12.2.1 CLD(s) QXCM1000436960 5.2.12.2.2 QAR(s) None. 5.2.12.3 Problem Analysis: BACKUP does a string compare of the saveset name specified in the command line with the name stored in the saveset. To compare the saveset name, BACKUP calls XQP$MATCH_NAME which expects the string and pattern (may contain wildcards) to be passed as the second and fifth parameter respectively. These parameters were interchanged, resulting in the error. 5.2.12.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.12.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS83A_BACKUP ECO kits can be found in the following files: o VMS83A_BACKUP-V100.RELEASE_NOTES o VMS83A_BACKUP-V200.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS83A_BACKUP - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS83A_BACKUP - /SELECT=[SYSUPD]release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be Page 14 found with: PRODUCT LIST {PCSI Installation Name} /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSEXE]BACKUP.EXE (new image) Image Identification Information image name: "BACKUP" image file identification: "V8.3" image file build identification: "XBCA-0080070011" link date/time: 9-JUL-2007 15:57:21.48 linker identification: "A13-03" Overall Image Checksum: 3968823868 o [SYSLIB]BACKUPSHR.EXE (new image) Image Identification Information image name: "BACKUPSHR" image file identification: "V8.3" image file build identification: "XBCA-0080070011" link date/time: 9-JUL-2007 15:56:33.23 linker identification: "A13-03" Overall Image Checksum: 1014456020 o [SYSMSG]SYSMGTMSG.EXE (new image) Image Identification Information image name: "SYSMGTMSG" image file identification: "X-4" image file build identification: "XBCA-0080070010" link date/time: 29-JUN-2007 15:17:39.34 linker identification: "A13-03" Overall Image Checksum: 2186229425 o [SYSUPD]BACKUP.CLD (new file) 8 INSTALLATION INSTRUCTIONS Page 15 8.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 8.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS83A_BACKUP-V0300.ZIPEXE 8.3 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 VMS83A_BACKUP[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. 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. Page 16 Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.4 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=V3.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS83A_BACKUP-V0300 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_BACKUP/PRODUCER=DEC/BASE=AXPVMS/VER=V3.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Page 17 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.