**************************** ECO SUMMARY INFORMATION **************************** Release Date: 6-DEC-2006 Kit Name: DEC-AXPVMS-VMS732_BACKUP-V0700--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 2825 blocks Installation Rating: INSTALL_3 Reboot Required: No Superseded Kits: VMS732_BACKUP-V0600 Mandatory Kit Dependencies: VMS732_UPDATE-V0700 or later VMS732_PCSI-V0300 or later Optional Kit Dependencies: None Checksums: VMS732_BACKUP-V0700.ZIPEXE Checksum: 3317233743 DEC-AXPVMS-VMS732_BACKUP-V0700--4.PCSI$COMPRESSED Checksum: 2768237440 VMS732_BACKUP-V0700.ZIPEXE MD5 Checksum: 3322D472BF59E564EBFFEE46840A33ED DEC-AXPVMS-VMS732_BACKUP-V0700--4.PCSI$COMPRESSED MD5 Checksum: 81D330DB36037CA926190BA733450544 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_BACKUP-V0700 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, however, this kit provides an update to DCLTABLES.EXE. If this kit is being installed in a clustered environment with a shared system disk, in order for all members of the cluster that share the system disk to make use of the new images, you must INSTALL/REPLACE DCLTABLES.EXE on each node of the cluster. Users must log out and log back in to use the newly installed DCLTABLES.EXE. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS ALPHA V7.3-2 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS732_BACKUP-V0600 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0300 - VMS732_UPDATE-V0700 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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS732_BACKUP-V0700 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Misleading Error Message From BACKUP/PHYSICAL Operation 5.2.1.1 Problem Description: If a physical backup is initiated from a non-privileged account, BACKUP does not notify the user of the privilege problem but displays an incorrect, misleading error message instead. $ BACKUP/PHYSICAL $2$DKA100: NLA0:X.X/SAVE %BACKUP-F-MOUNTFOR, $2$DKA100:[TEST]*.*;* must be mounted /FOREIGN Images Affected: - [SYSLIB]BACKUPSHR.EXE - [SYSMSG]SYSMGTMSG.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-1634 Page 3 5.2.1.3 Problem Analysis: During physical BACKUP operations, the process is expected to have LOG_IO privileges. 5.2.1.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.1.5 Work-arounds: None. 5.2.2 BACKUP-E-INCDELERR Error During Incremental Restore Operation. 5.2.2.1 Problem Description: Under the following conditions, an incremental RESTORE operation will report a "no such file" error: o The file version limit is set to two o One version of the file is already on disk o There are two versions of the file in the incremental BACKUP that is being restored. The error seen is: %BACKUP-E-INCDELERR error deleting ...filename... SYSTEM-W-NOSUCHFILE, no such file Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000290064 5.2.2.2.2 QAR(s) None. Page 4 5.2.2.3 Problem Analysis: During the incremental restore operation, if the version of the file on disk is not part of the incremental BACKUP, the file on disk is marked for deletion. BACKUP then restores the two versions of the file from the BACKUP and tries to delete the file marked for deletion. However, since the version limit is set to two, the file has already been deleted by the file system before BACKUP attempts to delete it, prompting the error. 5.2.2.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.2.5 Work-arounds: None. 5.2.3 BACKUP/IMAGE Fails With %BACKUP-E-CLOSEOUT Error 5.2.3.1 Problem Description: A BACKUP/IMAGE command fails with a %BACKUP-E-CLOSEOUT error when the file name length is greater than 91 characters and security ACEs are of size 252. Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000328584 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: When the file name length is greater than 91 characters and ACEs are of size 252, the ACLs are too large for the access control area of the primary header. Normally, when this occurs, an extension (secondary) header will is created and the ACL entry written into it. However, BACKUP does not create an extension header, therefore the Page 5 ACL does not get written into a secondary header. 5.2.3.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.3.5 Work-arounds: None. 5.2.4 BACKUP/ENCRYPT/LIST Error 5.2.4.1 Problem Description: When making a tape backup with the /ENCRYPT and /LIST qualifiers, if the backup spans more than one tape, BACKUP fails with following error: %BACKUP-E-INVATTSTR, invalid attribute record structure level in save set %BACKUP-E-INVATTSIZ, invalid attribute record size in save set Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM100333849 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: When span-over takes place, the buffer is partially written to the first tape with the remaining buffer content written to the next tape. Before writing the remaining buffer contents, BACKUP first creates and writes a summary record to next tape. Because the /LIST qualifier is specified, BACKUP lists the summary record correctly. However, since buffer contents are encrypted before span-over, when listing the remaining buffer contents, BACKUP displays the error. This change Page 6 modifies BACKUP so that after span-over, BACKUP will decrypt the remaining buffer contents before listing them. 5.2.4.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.4.5 Work-arounds: None. 5.2.5 SUBSYSTEM ACE Not Propagated From Source File To Target File 5.2.5.1 Problem Description: When a BACKUP copy operation is performed from a fully privileged account, if the account does not have the SUBSYSTEM identifier, BACKUP does not propagate the SUBSYSTEM ACE of the source file to the target file. Images Affected: - [SYSLIB]BACKUPSHR.EXE - [SYSMSG]SYSMGTMSG.EXE 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) QXCM1000324592 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: During a BACKUP copy, the status of the ACL operation is not checked while restoring the target file. Page 7 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 ODS-5 File Names Incorrectly converted to ODS-2 5.2.6.1 Problem Description: When BACKUP is initiated with /INTERCHANGE, the /CONVERT qualifier is implicitly considered, forcing the conversion of ODS-5 file names to the ODS-2 file name format. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE - [SYSUPD]BACKUP.CLD 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) QXCM1000324895 5.2.6.2.2 QAR(s) 75-109-360 5.2.6.3 Problem Analysis: The /CONVERT qualifier is implicit with the /INTERCHANGE qualifier and BACKUP does not provide a /NOCONVERT option. This change modifies BACKUP code to allow, and check for, a /NOCONVERT qualifier. If /NOCONVERT is used the ODS-5 to ODS-2 file name conversion routine is not called and the volume structure level (ODS-5 or ODS-2) is set appropriately. Page 8 5.2.6.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.6.5 Work-arounds: None. 5.2.7 BACKUP/IMAGE/CONVERT Operation Fails 5.2.7.1 Problem Description: A BACKUP/IMAGE/CONVERT operation fails with a "%BACKUP-E-OPENIN" error. Images Affected: - [SYSLIB]BACKUPSHR.EXE 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) None. 5.2.7.2.2 QAR(s) 75-109-360 5.2.7.3 Problem Analysis: BACKUP/IMAGE/CONVERT fails to retain the file attributes on the destination disk. 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. Page 9 5.2.8 Network BACKUP Error 5.2.8.1 Problem Description: When BACKUP is initiated across the network to create a save set on the remote system, BACKUP fails with the following error message when the target device is specified as a logical. %SYSTEM-F-IVDEVNAM, invalid device name -RUF-W-NORMAL, normal successful completion Images Affected: - [SYSLIB]BACKUPSHR.EXE 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-13-1736, 75-115-158 5.2.8.3 Problem Analysis: This problem may occur in any network save set specification, regardless of whether a logical or physical device name is given. BACKUP attempts a lookup on the local system of a device (or logical name) that belongs to the remote system. 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. Page 10 5.2.9 MOUNT-F-FILESTRUCT Error When Mounting Disk 5.2.9.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.9.2 CLDs, and QARs reporting this problem: 5.2.9.2.1 CLD(s) QXCM1000359713 5.2.9.2.2 QAR(s) None. 5.2.9.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.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-W-LOWPGFLQUOTA Page 11 5.2.10.1 Problem Description: When PGFLQUOTA is less than WSQUOTA + 25000 pagelets, the BACKUP process will exit and display a "%BACKUP-W-LOWPGFLQUOTA" warning Images Affected: - [SYSLIB]BACKUPSHR.EXE - [SYSMSG]SYSMGTMSG.EXE 5.2.10.2 CLDs, and QARs reporting this problem: 5.2.10.2.1 CLD(s) QXCM1000356862 5.2.10.2.2 QAR(s) None. 5.2.10.3 Problem Analysis: See problem description 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. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS732_BACKUP ECO kits can be found in the following files: o VMS732_BACKUP-V100.RELEASE_NOTES o VMS732_BACKUP-V200.RELEASE_NOTES o VMS732_BACKUP-V300.RELEASE_NOTES o VMS732_BACKUP-V400.RELEASE_NOTES Page 12 o VMS732_BACKUP-V500.RELEASE_NOTES o VMS732_BACKUP-V600.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 VMS732_BACKUP/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS732_BACKUP/VERSION= V7.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYSEXE]BACKUP.EXE (new image) Image Identification Information image name: "BACKUP" image file identification: "AXP72R001" image file build identification: "XBCV-0060110040" link date/time: 25-OCT-2006 11:56:28.32 linker identification: "A11-50" Overall Image Checksum: 233991657 o [SYSLIB]BACKUPSHR.EXE (new image) Image Identification Information image name: "BACKUPSHR" image file identification: "AXP72R001" image file build identification: "XBCV-0060110040" link date/time: 25-OCT-2006 11:55:26.66 linker identification: "A11-50" Overall Image Checksum: 3020860672 o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information image name: "LIBRTL" image file identification: "X01-001" image file build identification: "XA99-0060111007" link date/time: 28-MAR-2006 09:19:38.64 linker identification: "A11-50" Overall Image Checksum: 2944424280 Page 13 o [SYSMSG]SYSMGTMSG.EXE (new image) Image Identification Information image name: "SYSMGTMSG" image file identification: "X-4" image file build identification: "XBCV-0060111009" link date/time: 15-NOV-2006 11:27:36.59 linker identification: "A11-50" Overall Image Checksum: 1179440411 o [SYSUPD]BACKUP.CLD (new file) 8 INSTALLATION INSTRUCTIONS 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 VMS732_BACKUP-V0700.ZIPEXE Page 14 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 VMS732_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. 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=V7.0 [/SOURCE=location of Kit] Page 15 o De-assign the logical names assigned For example, a sample command file to install the VMS732_BACKUP-V0700 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_BACKUP/PRODUCER=DEC/BASE=AXPVMS/VER=V7.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 8.5 Special Installation Instructions: This kit provides an update to DCLTABLES.EXE. If this kit is being installed in a clustered environment with a shared system disk, in order for all members of the cluster that share the system disk to make use of the new images, you must INSTALL/REPLACE DCLTABLES.EXE on each node of the cluster. Users must log out and log back in to use the newly installed DCLTABLES.EXE. 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2006 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 Page 16 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.