OpenVMS VAXBACK02_072 VAX V7.2 Backup Utility ECO Summary
TITLE: OpenVMS VAXBACK02_072 VAX V7.2 Backup Utility ECO Summary
Modification Date: 15-DEC-2000
Modification Type: Updated Kit: Supersedes VAXBACK02_072
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname-dcx_axpexe.pcsi, then it can
be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 1999, 2000. All rights reserved
OP/SYS: OpenVMS VAX
COMPONENT: Backup Utility
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXBACK02_072
ECO Kits Superseded by This ECO Kit: VAXBACK01_072
ECO Kit Approximate Size: 1098 Blocks
Kit Applies To: OpenVMS VAX V7.2
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Not Applicable
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VAXUPDATE01_072
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for the Backup Utility on OpenVMS VAX V7.2. This
kit addresses the following problems:
Problems Addressed in VAXBACK02_72:
o A CREDIRERR error status does not remove files from
post-processing when performing a BACKUP/DELETE operation.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o Provide a /NOUNLOAD qualifier fro BACKUP to carry over through
continuation volumes of a tape volume set. Before this fix,
there was no way to specify /NOUNLOAD in BACKUP, so controlling
continuation volumes was not possible.
UNLOAD/NOUNLOAD keywords have been added to the RELEASE_TAPE
qualifier, with UNLOAD as the default. On the command line,
the entry will look like the following:
$BACKUP/RELEASE_TAPE=NOUNLOAD !NOUNLOAD the volume
$BACKUP/RELEASE_TAPE=UNLOAD !UNLOAD the volume
$BACKUP/RELEASE_TAPE !UNLOAD (Default)
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o The command BACKUP/IMAGE/VERIFY DKA0: DKA1: does not do the
compare. If the /LOG qualifier is added to the command, the
message BACKUP-S-COMPARED displays for every file, but the
files are not compared.
Images Affected: [SYSEXE]STABACKUP.EXE
o The command "BACKUP/RECORD/SINCE=BACKUP Disk:[000000...] Target:"
fails to update the backup date of the MFD directory 000000.DIR.
Consequently, if the modification date of the 000000.DIR is later
than the backup date, each invocation of the above command will
result in the whole disk being backed-up.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o There are issues with BACKUP ignoring /SINCE/MODIFIED qualifiers.
For example:
Command: Behavior:
======== ==========
$BACKUP/SINCE=date/CREATED correctly selects files
$BACKUP/SINCE=date/MODIFIED incorrectly selects *ALL*
files
$BACKUP/SINCE=date/MODIFIED/NOINC correctly selects files
If the following occurs:
1. The parent directory meets the selection criteria
2. The /SINCE qualifier was entered, signifying that some
sort of incremental backup is to be performed
3. The user did not explicitly enter the MFD or the
/NOINCREMENTAL qualifier
then all files in the directory are saved and no comparison is
done between the input date specifier and the files in the
directory.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o When two ASCII files are different by one character,
BACKUP/COMPARE will complete with no error message.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o BACKUP does not preserve the File Caching attributes during
file copy operations. When a new directory or file is
created, it inherits its caching attribute from its parent
directory. When a new version of an existing file is created,
the new file inherits its caching attribute from the highest
version of the existing file.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
Problems Addressed in VAXBACK01_72:
o An %BACKUP-F-BADOPTVAL error can occur when using an
Identifier String for a BACKUP/BY_OWNER qualifier value.
For example:
$ BACKUP SOURCE:*.*/BY_OWNER=USER TAPE:A.BCK/SAV
%BACKUP-F-BADOPTVAL, invalid callable interface option value,
argument position 7, option type = 59, option value = 2147549409
Image(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
o Attempting to use BACKUP/ENCRYPT in BATCH results in the error
%BACKUP-F-ENCNOTSUP.
Images(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
o The BACKUP/DRIVE_CLASS qualifier was not processed properly.
Images(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
o BACKUP/JOURNAL fails with an ACCVIO under the following two
conditions:
- backing up a moderate number of files to tape
- backing up a file, where the combined length of the
directory specification and filename exceed 512
characters
Image(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed.
However, if the system is a member of a VMScluster, the other cluster
members should be rebooted or this kit should be installed on each
system in order to make use of the new image(s).
All trademarks are the property of their respective owners.
Copyright (c) Compaq Computer Corporation 1999. All rights reserved
Modification Date: 15-DEC-2000
Modification Type: ARCHIVED
OP/SYS: OpenVMS VAX
COMPONENT: Backup Utility
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXBACK01_072
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 504 Blocks
Kit Applies To: OpenVMS VAX V7.2
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Not Applicable
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for the Backup Utility on OpenVMS VAX V7.2. This
kit addresses the following problems:
o An %BACKUP-F-BADOPTVAL error can occur when using an
Identifier String for a BACKUP/BY_OWNER qualifier value.
For example:
$ BACKUP SOURCE:*.*/BY_OWNER=USER TAPE:A.BCK/SAV
%BACKUP-F-BADOPTVAL, invalid callable interface option value,
argument position 7, option type = 59, option value = 2147549409
Image(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
o Attempting to use BACKUP/ENCRYPT in BATCH results in the error
%BACKUP-F-ENCNOTSUP.
Images(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
o The BACKUP/DRIVE_CLASS qualifier was not processed properly.
Images(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
o BACKUP/JOURNAL fails with an ACCVIO under the following two
conditions:
- backing up a moderate number of files to tape
- backing up a file, where the combined length of the
directory specification and filename exceed 512
characters
Image(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed.
However, if the system is a member of a VMScluster, the other cluster
members should be rebooted or this kit should be installed on each
system in order to make use of the new image(s).
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxback02_072.README
vaxback02_072.CHKSUM
vaxback02_072.CVRLET_TXT
vaxback02_072.a-dcx_vaxexe
vaxback02_072.CVRLET_TXT
|
