OpenVMS CSCPAT_1101 VAX V5.2 - V5.4-3 BACKUP ECO Summary

Copyright (c) Digital Equipment Corporation 1992, 1994. All rights reserved. OP/SYS: OpenVMS VAX COMPONENT: BACKUP Utility SOURCE: Digital Equipment Corporation ECO INFORMATION: CSCPAT Kit: CSCPAT_1101 V1.8 (CSCPAT_1101018) CSCPAT Kit Approximate Size: 1800 blocks Engineering Cross Reference: BCK$IMG01_532, VAXBACK01_U3054 Kit Applies To: OpenVMS VAX V5.2, V5.2-1, V5.3, V5.3-1, V5.3-2, V5.4, V5.4-1, V5.4-2, V5.4-3 System Reboot Necessary: No ECO KIT SUMMARY: An ECO kit exists for BACKUP on OpenVMS VAX V5.2 through V5.4-3. This kit addresses the following problems: o If a file's first ACE is identical to the username of the account performing the BACKUP SAVE operation, the ACE is deleted. o BACKUP is unable to mount a continuation volume when performing a BACKUP operation in a subprocess unless the device is explicitly allocated. With this kit installed, a warning message will now be returned to the user to allow them to take corrective action. This problem is fixed in OpenVMS VAX V6.0. o With this ECO kit installed, a new BACKUP qualifier 'EXACT_ORDER' is introduced which allows enhanced volume label processing. Depending on the other qualifiers you specify on the command line, /EXACT_ORDER enables you to do the following: - Specify the exact order of tapes and labels that you want to use in a BACKUP operation. - Preserve the existing volume label on a tape. - Prevent previous volumes of a multivolume save operation from being overwritten. This new qualifier is included in this ECO and OpenVMS VAX V6.0. NOTE: For more information on this new qualifier, refer to the ECO kit release notes. o If there is a volume label problem on a continuation volume, the user is prompted for a response. If the user enters 'QUIT', BACKUP does not abort but initiates a RESTART condition and re-prompts the user for another response. If the user enters 'QUIT' a second time, the BACKUP process is aborted. This problem is fixed in OpenVMS VAX 6.0. o During an IMAGE BACKUP, files which receive a FORCEDERROR are backed up twice, once in the original directory and once in a directory named '[]'. This problem will be fixed in a future version of OpenVMS VAX. o Files which have not been completely saved may be deleted (/DELETE) or their BACKUP dates updated (/RECORD). This has occurred when the output [disk] device runs out of space during a BACKUP copy operation and either of the above qualifiers have been specified. This problem is fixed in OpenVMS VAX V6.0. o BACKUP/IMAGE saves files with alias entries (synonym files) multiple times. This problem will be fixed in a future version of OpenVMS VAX. o BACKUP runs out of channels during processing and returns a BACKUP$_NOMSG error. This problem will be fixed in a future version of OpenVMS VAX. o When highwater marking is enabled, BACKUP may report VERIFY errors on index files during either a BACKUP save or restore. This occurs when the highwater mark is less than the allocated file size. (The "used" size is less than the allocated file size.) o Use of a sequential disk saveset can cause BACKUP to abort if the output disk device is mounted foreign. This problem is fixed in OpenVMS VAX V5.5-2. o Use of the /NOINITIALIZE qualifier can incorrectly set EFBLK in INDEXF.SYS. This problem is fixed in OpenVMS VAX V5.5-2. o As a result of a change to the XQP in OpenVMS VAX V5.4-3, spurious error messages are displayed if BACKUP attempts to create directories which already exist on the disk during a restore operation. This problem is fixed in OpenVMS VAX V5.5-2. NOTE: The messages have no impact on the success of the restore operation. o If a BACKUP file specification contains a searchlist logical which was defined with 16 or more elements, some files will be backed up twice and some files will not be backed up at all. This problem is fixed in OpenVMS VAX V5.5-2. o SLS (System Storage Library) specific code was added to BACKUP and can be accessed using the new BACKUP qualifier '/STORAGE_LIBRARY_SYSTEM'. This problem is fixed in OpenVMS VAX V6.0. o After upgrading to OpenVMS VAX V5.4-3, a BACKUP incremental restore may return the following error messages for every file in the directory: %BACKUP-S-CREDIR, created directory 'disk:[directory]' %BACKUP-E-READATTR, error reading attributes for 'disk:[directory]' -SYSTEM-W-ACCONFLICT, file access conflict %BACKUP-E-INCENTERR, error creating directory entry for '[directory], file access conflict However, upon re-executing the BACKUP/INCREMENTAL command, the files DO get restored because the directory WAS created the first time the command was entered. This problem is fixed in OpenVMS VAX V6.0. o If an operator attempts to abort a BACKUP operation using the DCL command 'REPLY/ABORT=nnn', BACKUP ignores the request even though an OPCOM "REQUEST ABORTED" acknowledgment message appears. This behavior has been specifically noted on a selective BACKUP restore operation of a multi-volume saveset. This problem is fixed in OpenVMS VAX V6.0. o If the /RECORD qualifier is used and BACKUP is restarted using the 'RESTART' option, the 'Backup dates' are not updated correctly. This problem is fixed in OpenVMS VAX V6.0. o BACKUP status messages were added alphabetically and by order of severity. This caused messages already in the message file to be moved and their status code numeric values to change. With this kit installed, all new messages will be added at the end of the message file instead of alphabetically. This problem is fixed in OpenVMS VAX V6.0. o On SCSI devices (e.g., TLZ04), a blank tape can not be initialized using the BACKUP/REWIND command. The following error messages are returned: %BACKUP-F-LABELERR, Error in tape label processing -SYSTEM-F-DRVERR, fatal drive error This problem is fixed in OpenVMS VAX V6.0. o If a saveset ends exactly at the EOT (End Of Tape) and another saveset follows immediately after, BACKUP may not initiate a volume switch causing subsequent savesets to run the tape off the reel. When this occurs, savesets do not contain any data, just header information. NOTE: No error messages are returned. This problem is fixed in OpenVMS VAX V5.5-2. o When using BACKUP/IMAGE/VOLUME=n to back up one volume of a bound volume set, data corruption may occur even if the BACKUP qualifier '/VERIFY' is specified. This results in a saveset that is unusable. This problem is fixed in OpenVMS VAX V5.5-2. o During a /PHYSICAL BACKUP operation, BACKUP may hang in the LEF state at the end of the first tape volume. This problem is fixed in OpenVMS VAX V5.5-2. o Excessive null pad records may be added to BACKUP blocks when small/low process quotas are used for the account where BACKUP is run from or a large blocksize value is specified. This causes saveset sizes to be much larger. This problem is fixed in OpenVMS VAX V5.5-2. o After creating a BACKUP sequential disk saveset on a drive mounted with the /FOREIGN qualifier, the 'DISMOUNT/UNLOAD' DCL command does not dismount/unload the disk. This problem is fixed in OpenVMS VAX V5.5-2. o DFS/BACKUP process hangs when saving from a DFS served device. This problem is fixed in OpenVMS VAX V5.5-2. o The DFS/BACKUP process may hang during a BACKUP save from a DFS device when an error condition occurs. The LBN scan/sort is also disabled when the input device is a DFS served disk. This problem is fixed in OpenVMS VAX V5.5-2. o In a BACKUP restore operation, a file's ACL (Access Control List) is not restored if the user does not have the SYSPRV privilege or is not the owner of the file. This problem is fixed in OpenVMS VAX V5.5-2. NOTE: CSCPAT_1101 and CSCPAT_0153 MUST be installed in order for this problem to be fixed on systems prior to OpenVMS VAX V5.4-3. The ECO kits can be installed in any order. For more information on this problem, please refer to another database article using the following query: SYSTEM-F-NOPRIV Restore Resource Identifier o BACKUP corrupts the first two ACEs of a file's ACL if the file is opened for exclusive access after it has been saved, but before the recording pass has processed it. This problem is fixed in OpenVMS VAX V5.5-2. o If the year specified by the BACKUP '/TAPE_EXPIRATION' qualifier is greater than 2000, BACKUP will allow the tape to be overwritten. This problem is fixed in OpenVMS VAX V5.5-2. o If the BACKUP qualifier '/PROTECTION' is used, BACKUP will return a MOUNTERR and fail to mount the tape if the process does not have UIC-based access to the tape volume. This problem is fixed in OpenVMS VAX V5.5-2. o BACKUP initializes the output disk even if the BACKUP qualifier 'NOINITIALIZE is specified. This problem is fixed in OpenVMS VAX V5.5-2. o If a user mounts a tape, spawns a subprocess, then issues a BACKUP command from the subprocess, continuation tape processing fails with the OPCOM message: _MUA0 is not available for mounting This problem is fixed in OpenVMS VAX V5.5-2. o If the tape that BACKUP is going to use is mounted (using a logical name) before the BACKUP operation is initiated, and the BACKUP operation uses more than one tape volume, the logical name used in the MOUNT is no longer assigned when the BACKUP operation is done, even though the tape is still mounted. This problem is fixed in OpenVMS VAX V5.5-2. o After a BACKUP/IMAGE restore of a common system disk, VMS$COMMON.DIR becomes the synonym of SYSCOMMON.DIR. As a result, incorrect file specifications for files residing in the common root are returned when using such lexical functions as F$ENVIRONMENT or F$GETQUI. This problem is fixed in OpenVMS VAX V5.5-2. o Resetting a tape device to the original settings upon exiting may cause a SYSTEM-F-SERIOUSEXCP error to be returned. For example: $ SET VERIFY $ SET NOON $ TAPE :== $1$MUA0: $ INITIALIZE/DENSITY=6250 'TAPE' A000 $ BACKUP/VERIFY/LOG/IGNORE=LABEL XX.LIS 'TAPE'XX.BCK/SAVE $ SET MAGTAPE/REW 'TAPE' $ SET MAGTAPE/SKIP=FILE:1000 'TAPE' $ SET MAGTAPE/SKIP=FILE:-1 'TAPE' $ SET NOVERSION $ EXIT -SYSTEM-F-SERIOUSEXCP , TMSCP Controller , Serious Exception This problem is fixed in OpenVMS VAX V5.5-2. o If a wildcard file specification is used with a BACKUP/LIST command, BACKUP will display the contents of the saveset in a continuous loop. This problem is fixed in OpenVMS VAX V5.5-2. o BACKUP savesets created under VMS V5.2 through V5.5 may be much larger than those created in previous versions. Even if the same files are being saved, the savesets may grow by a factor of 4 or more. This problem is fixed in OpenVMS VAX V5.5-1. o BACKUP RESTART problems: - BACKUP hangs in a compute loop. - BACKUP restarts the save operation from the beginning of the file rather than the beginning of the tape volume. - BACKUP saves one or more files twice. When a file is saved the second time, the directory specification is null (e.g.,[]). - A SYSTEM-F-ACCVIO error occurs when attempting the RESTART. - BACKUP-E-VBNMISSING errors are generated during the VERIFY pass or when restoring a file. - A SYSTEM-F-ACCVIO error is returned when a failure occurs on the last volume of the saveset during a VERIFY pass. - A BACKUP-F-FREEBADBUF error is returned when attempting a RESTART during a BACKUP PHYSICAL save operation. All the above RESTART problems are fixed in OpenVMS VAX V5.4-3. o BACKUP/COMPARE operation hangs in LEF state. This problem is fixed in OpenVMS VAX V5.4-1. o BACKUP/JOURNAL fails with an BACKUP-F-INVBJLSIZ error if a disk saveset name is greater than 31 characters. This problem is fixed in OpenVMS VAX V5.4-1. o During a BACKUP save operation, the errors 'BACKUP-E-VBNMISSING' and 'BACKUP-E-VBNPASTEOF' are returned on files that have an EOF (end-of-file) marker much less than the number of allocated blocks. This problem is fixed in OpenVMS VAX V5.4-1. o While using the BACKUP/RECORD command, BACKUP-I-MODOUTAI and BACKUP-I-MODOUTBI messages are returned. These messages occur when a file which has been successfully backed up is deleted before the RECORD pass begins. This problem is fixed in OpenVMS VAX V5.4-1. o BACKUP/DELETE and BACKUP/RECORD do not not work if the directory file-id is larger than 65535. During the deletion or record pass, files that are contained within such a directory are not deleted. This problem with BACKUP/DELETE was fixed in OpenVMS VAX V5.4-1. This problem with BACKUP/RECORD was fixed in OpenVMS VAX V5.2. o Poor BACKUP performance after upgrading to OpenVMS VAX V5.2 or V5.3. This problem is fixed in OpenVMS VAX V5.4. o BACKUP-E-VBNMISSING errors are returned when performing a BACKUP/VERIFY save operation on an ODS-1 level disk. This problem is fixed in OpenVMS VAX V5.4. o BACKUP save operation on highly fragmented ODS-1 level disk hangs. This problem is fixed in OpenVMS VAX V5.4. o SYSTEM-F-ROPRAND error is returned from a BACKUP/NOASSIST save operation when BACKUP issues a prompt to mount the second tape volume. This problem is fixed in OpenVMS VAX V5.4. o BACKUP restore of disk multi-volume saveset loops requesting a second volume. This problem is fixed in OpenVMS VAX V5.4. o BACKUP-E-VBNMISSING and VBNERROR errors are returned on files that span tape volumes when the /VERIFY qualifier is used. This problem is fixed in OpenVMS VAX V5.4. o BACKUP is unable to change the format of the TA90 tape cartridge from non-compacted to compacted. The /MEDIA_FORMAT qualifier is ignored. This problem is fixed in OpenVMS VAX V5.4. o BACKUP operations intermittently abort with an RMS-F-USZ error at the time a volume switch occurs. This problem is fixed in OpenVMS VAX V5.4. o BACKUP hangs when attempting to save or restore a file that resides on a ODS-1 disk. ODS-1 disks are compatible with the RSX operating system. This problem is fixed in OpenVMS VAX V5.4. o BACKUP/DELETE disk-to-disk IMAGE save or copy operation deletes files that are not successfully copied. This problem is fixed in OpenVMS VAX V5.4. o SYSTEM-F-ACCVIO from BACKUP With PC of F9AE. This problem is fixed in OpenVMS VAX V5.4. o Tape saveset names greater than 17 characters are not disallowed. This causes a SYSTEM-W-NOSUCHFILE error on the verification pass or when trying to restore from the saveset. This problem is fixed in OpenVMS VAX V5.3-2. o BACKUP/RECORD and BACKUP/DELETE may not work correctly during a save operation if BACKUP-E-VERIFYERR or BACKUP-E-OPENIN errors occur. This problem is fixed in OpenVMS VAX V5.3-2. o With CSCPAT_1101 V1.0 installed, using the BACKUP command 'BACKUP/IMAGE/NOINITIALIZE' to copy or restore a disk volume may cause the resulting volume to be corrupt. This problem is fixed by CSCPAT_1101 V1.2 and later. o With CSCPAT_1101 V1.0 installed, BACKUP restore operations may not restore directory file ACLs correctly if higher level directory files also contain ACLs. This problem is fixed by CSCPAT_1101 V1.2 and later. INSTALLATION NOTES: The system/cluster does not need to be rebooted after this kit is installed. However, SYS$LIBRARY:DCLTABLES is modified to include the new BACKUP qualifiers. To take advantage of the new syntax without having to logout and then login, a process's copy of DCLTABLES can be updated by using the following command: $ SET COMMAND/TABLE=SYS$LIBRARY:DCLTABLES

This patch can be found at any of these sites:

Files on this server are as follows:

cscpat_1101018_backup.README
cscpat_1101018.CHKSUM
cscpat_1101018.a-dcx_vaxexe