OpenVMS__ABS ABSE01022 Archive/Backup System for OpenVMS ECO Summary
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Digital Equipment Corporation 1998. All rights reserved.
Modification Date: 05-Jun-1998
Modification Type: New ECO kit.
PRODUCT: Archive/Backup System
OP/SYS: OpenVMS VAX
OpenVMS Alpha
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ABSE01022
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 74258 Blocks
Saveset A - 702 Blocks
Saveset B - 16938 Blocks
Saveset C - 4518 Blocks
Saveset D - 22338 Blocks
Saveset E - 14490 Blocks
Saveset F - 15246 Blocks
Kit Applies To: Archive/Backup System v2.1 through V2.2
Archive/Backup System - OMT V2.1
OpenVMS VAX V6.1 through V7.1
OpenVMS Alpha V6.1 through V7.1-1H2
NOTE: This kit automatically installs the correct images for your
type of system (VAX or Alpha).
System/Cluster Reboot Necessary: No (See Installation Notes)
ECO KIT SUMMARY:
An ECO kit exists for Archive/Backup System V2.2 on OpenVMS VAX V6.1
through V7.1 and OpenVMS Alpha V6.1 through V7.1-1H2. This kit
addresses the following problems:
Problems Addressed in ABSE01022:
o The NT Client was not Y2K compliant. The Gtar image used for the
NT client has been fixed to support Y2K.
o ABS SHOW RESTORE was displaying destination twice. The extra display
of destination was removed from ABS SHOW RESTORE.
o ABS SHOW <object> was displaying EXECUTE access in the access control
fields. This field can not be set using ABS. ABS SHOW <object> no
longer displays EXECUTE access.
o %ABS-E-SETRESTOREERR, error setting restore request error received
when attempting to set a restore request after updating to ABS V2.2.
This occured if the ABS SET RESTORE command did not specify the
/STORAGE_CLASS qualifier.
In V2.1, ABS startup defined the logical name ABS_DEF_ARCH_CLASS to
SYSTEM_BACKUPS. The DCL code was referencing this logical to determine
the default storage class for the restore. This has been fixed in
ABSE01022.
o The template file
VMS_BACKUP-2.INCREMENTAL_ARCHIVE_TEMPLATE
incorrectly placed the /NOPRESHELVED/NOSHELVED qualifiers after
the AGENT_OPTIONS field. This prevented you from overriding these
qualifiers on a save request.
The /NOPRESHELVED/NOSHELVED qualifiers have been placed before the
AGENT_OPTIONS field so that you may specify agent_options to override
the qualifiers on a save request.
o When an error occurred in a save request (either in the save request
itself or in an epilogue file), ABS would fail to unlock the volume set
and would loop forever waiting for the volume to become available.
This would only happen if the retry option was set and the retry interval
was approximately 15 minutes.
o The ABS GUI did not allow you to enter a catalog name which was not
listed in the CREATE/MODIFY STORAGE POLICY window. This prevented you
from entering a catalog from a VMS client.
This was changed. There is now an OTHER selection which then allows you
to enter a catalog name which is not listed.
o In the ABS GUI, there were some fields in the storage class tape options
screen which should be uppercased. If you entered a media type in lower
case, then your save would fail to find the media type.
o Setting /LATEST_COPY on a RESTORE request using ABS RESTORE or ABS SET
RESTORE, failed to set that option.
o The ABS GUI would receive an ACCVIO if you attempted to add more than
8 objects to a save request.
The ABS GUI now prevents you from entering more than 8 objects to the
save request. ABS does not allow more than 8 objects in a save request.
o The ABS GUI was not correctly setting the high and low limit dates on
a restore.
o The ABS GUI was missing a window where you could set an EXPLICIT INTERVAL.
This window has been added to the GUI.
o When restoring a disk or files from a multiple tape saveset, ABS would
hang. The data had been completely restored, but the Coordinator process
would never exit.
o When a storage class was created or set using the ABS GUI, and you listed
multiple drives in the tape options window, the save requests would only
use the first drive in the list. The save would never attempt to use
another drive if the first one was unavailable.
o If you set a save request to /SCHEDULE=MONTHLY using the ABS SET SAVE
command, the scheduler job was incorrectly set to "F Q M" for the
schedule interval.This has been corrected in ABSE01022. It now sets the
scheduler job to "M 1".
o ABS SET SAVE/START_TIME was not updating the scheduler job.
The format of the date/time string was constructed incorrectly.
This is fixed in ABSE01022.
o The ABS GUI was returning an ACCVIO if you attempted to delete a storage
class which has catalog references.
An error message which says that you may not delete the storage class with
catalog references is now displayed.
o ABS had hardcoded process quotas for the backup agent subprocess and the
staging catalog unpack process. This prevented the user from changing the
quotas if desired.
We now retrieve the quotas from the ABS account. If you raise the quotas
for the ABS account, ABS will now use those for the subprocesses.
o ABS SET ENVIRONMENT/DATA_SAFETY=CRC was failing to set CRC.
o When updating from ABS V2.1n to V2.2, if you were using a tape written by
V2.1n, if you did a UNIX or NT backup to that same tape with V2.2, ABS
wrote to the beginning of the tape, overwriting previously saved data.
INSTALLATION NOTES:
After installing this kit, it is necessary to restart ABS for all of
the changes to take effect.
For a mixed-architecture configuration or other heterogeneous
VMScluster configurations, the kit must be installed on each node
having its own SLS$ROOT directory structure.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
abse01022.README
abse01022.CHKSUM
abse01022.a-dcx_axpexe
abse01022.a-dcx_vaxexe
abse01022.b-dcx_axpexe
abse01022.b-dcx_vaxexe
abse01022.c-dcx_axpexe
abse01022.c-dcx_vaxexe
abse01022.d-dcx_axpexe
abse01022.d-dcx_vaxexe
abse01022.e-dcx_axpexe
abse01022.e-dcx_vaxexe
abse01022.f-dcx_axpexe
abse01022.f-dcx_vaxexe
|