OpenVMS VMS721_BACKUP-V0100 Alpha V7.2-1 BACKUP ECO Summary
TITLE: OpenVMS VMS721_BACKUP-V0100 Alpha V7.2-1 BACKUP ECO Summary
Modification Date: 16-NOV-2000
Modification Type: DOCUMENTATION: Corrected MOUNT kit name in
Kit Dependencies.
Modification Date: 14-NOV-2000
Modification Type: New Kit
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 2000. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: BACKUP
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721_BACKUP-V0100
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 1296
Kit Applies To: OpenVMS Alpha V7.2-1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
1 - To be installed on all systems running
the listed version(s) of OpenVMS.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VMS721_PCSI-V0100
VMS721_UPDATE-V0100
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
VMS721_MOUNT96-V0100
VMS721_DRIVER-V0100
VMS721_FIBRE_SCSI-V0100
ECO KIT SUMMARY:
An ECO kit exists for BACKUP on OpenVMS Alpha V7.2-1. This kit addresses
the following problems:
o Backup may abort during a /IMAGE operation of an ODS5 disk
with an RMS-F-SYN error.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o BACKUP is looping with a WAITIDLEBCB error after a fatal drive
error. See the partial error message below:
%BACKUP-E-FATALERR, fatal error on _$2$MUA561:[]DISK$REPSET2.BCK;
-SYSTEM-F-DATALOST, data lost
%SLS-E-BACKUPFAIL, backup directive failed
%BACKUP-F-ABORT, operator requested abort on fatal error
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
This may also result in an ACCVIO.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o Process quota values may cause BACKUP to ACCVIO. No quota
related messages are displayed.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o The following %BACKUP-F-PARSE error occurs when BACKUP has an
input-specifier that is somewhat lengthy and includes a
wildcard file specification with an implicit device and
directory.
%BACKUP-F-PARSE, error opening NET*.*;*
-RMS-F-SYN, file specification syntax error
where NET.*.*;* is the wildcard file specification in the
input-specifier.
The above error will occur whenever the following BACKUP
command is issued:
$ BACKUP SYS$SYSTEM:NET*.*;*,SYS$SYSTEM:SYSUAF.DAT,RIGHTSLIST.DAT -
TAPEDRIVE:SAVESET.BCK
It appears that this is a positional problem since if the
wildcard file specification appears at the beginning of the
input-specifier, the problem is avoided. For example, the
following BACKUP command will work successfully:
$ BACKUP SYS$SYSTEM:NET*.*;*,SYS$SYSTEM:SYSUAF.DAT,RIGHTSLIST.DAT -
TAPEDRIVE:SAVESET.BCK
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o When the BACKUP utility prompts for a new tape, certain
invalid replies will abort the backup with a LIB-F-INPSTRTRU
error.
For the error to occur, a blank followed by a single letter
must be entered, e.g., " y" or " r". BACKUP then repeats the
prompt. If the user types the full response, i.e., "yes" or
"restart", the following error message displays:
%BACKUP-F-ABORT, operator requested abort on fatal error
-LIB-F-INPSTRTRU, input string truncated
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o Backup cannot write journal records large enough to include
longer filenames, which are allowed with ODS5 and the extended
character set. Attempts to use long filenames results in a
'%BACKUP-F-INVBJLSIZ, invalid record size in BACKUP journal'
error.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o A /LIST/FULL operation does not include a 'seconds' output
field for file dates.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
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 A %BACKUP-W-NOFILES message may be received when backup is run
from a search list and <...> is used instead of [...] as the
syntax for a directory file specification.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o After upgrading to OpenVMS Alpha 7.2, a BACKUP command
specifying a /LABEL of more than six characters fails with:
%BACKUP-F-INVQUAVAL, value 'ISNAPBL023' invalid for /LABEL
qualifier
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 An incremental BACKUP RESTORE causes a BACKUP-E-INCDELERR
error and loops continuously when attempting to perform a
directory tree delete on a specific DIR filespec. The
following text is an example of the message syntax:
%BACKUP-E-INCDELERR, error deleting
$4$DUA1:[WINDATA.NETSCAPE.CACHE]CACHE.DIR;1
-SYSTEM-W-NOSUCHFILE, no such file
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o The loss of compaction may occur on a tape device after
upgrading to OpenVMS V7.2-1. This could happen in several
ways. Appending of savesets to a tape volume may lead to loss
of the compaction attribute for tape device or it may not be
correctly enabled at the start of a tape volume. Also, use of
generic SCSI tape devices may not honor the compaction device
attribute after a tape label overwrite or on the initialization
of continuation volumes.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o Files with an 8388698 (4 Gb.) contiguous block size could not
be copied disk to disk correctly using BACKUP. However, a
file maybe saved correctly if sent to a tape saveset,
depending upon the /blocksize value in the command line.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o A RMS-F-SYN error occurs when a UIC (user identification code)
is specified in the BACKUP command line. 'RMS-F-SYN, file
specification syntax error' is reported when the BACKUP
command line is supplied with a UIC format for a directory
filespec. For example: disk:[0,0] rather than disk:[000000].
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o Intermittent ACCVIOs occur on a tape volume switch (continuation
volumes). Depending on a number of resource issues (the number
of queued I/Os [QIOs], the number of files open, or sent but
failing QIOs) when a tape volume switch is needed, an ACCVIO may
occur just after the new tape volume is requested.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
o Compaction is not enabled, if BACKUP is called with the API.
Running BACKUP interactively or through batch jobs, however,
enables compaction and it functions acceptably with remedia
images.
Images Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, they must
also be rebooted in order to make use of the new image(s).
If it is not possible or convenient to reboot the entire cluster at
this time, a rolling re-boot may be performed.
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:
dec-axpvms-vms721_backup-v0100--4.README
dec-axpvms-vms721_backup-v0100--4.CHKSUM
dec-axpvms-vms721_backup-v0100--4.pcsi-dcx_axpexe
vms721_backup-v0100.CVRLET_TXT
|
