SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping 

*OpenVMS, ABS] ABSE02022 Archive/Backup System for OpenVMS ECO Summary 


TITLE: *OpenVMS, ABS] ABSE02022 Archive/Backup System for OpenVMS ECO Summary 
 
ON HOLD:  Engineering is currently researching a problem with this
          ECO and has requested that it be placed on Engineering Hold.

Modification Date:  08-JAN-99
Modification Type:  Updated Kit:  Put on HOLD 

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) Compaq Computer Corporation 1998.  All rights reserved.

PRODUCT:    Archive/Backup System 
            Archive/Backup System - OMT (OpenVMS Managment Tools)

OP/SYS:     OpenVMS VAX
            OpenVMS Alpha

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  ABSE02022
     ECO Kits Superseded by This ECO Kit:  ABSE01022
     ECO Kit Approximate Size:  76563 Blocks
                    Saveset A -   567 Blocks
                    Saveset B - 18000 Blocks
                    Saveset C -  4536 Blocks
                    Saveset D - 23634 Blocks
                    Saveset E - 14580 Blocks
                    Saveset F - 15246 Blocks

     Kit Applies To:  Archive/Backup System V2.1 through V2.2-eco1
                      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)
     Rolling Re-boot Supported:  Information Not Available
     Installation Rating:  INSTALL_UNKNOWN

     Kit Dependencies:

          None


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 ABSE02022:

  o  If an NT or UNIX save request using a stacker device required a
     volume continuation, the save request would fail and the following
     error was displayed: 

          %SLS-E-PARTOFSET

  o  If ABS restored a file from a save set that spanned multiple volumes
     of a volume set, and the last volume in the volume set was involved,
     ABS left the volume set locked. If an ABS save or restore attempted
     to use that volume set, ABS would wait for the volume to become
     unlocked. A message similar to following would be repeated in the
     save or restore request log file:

          COORDINATOR: Attempting to allocate volume set ABS102...

  o  When performing a UNIX or an NT incremental save operation using
     ABS, if the path name specified in the save request was the same as
     the path name specified on a save request for a different UNIX or NT
     system, the backup dates selected for the incremental save operation
     may not have been correct. Because ABS did not include the node name
     of the UNIX or NT system, ABS selected the most recent backup dates
     for the incremental save operation, regardless of which system the
     file was backed up from. 

  o  During a multi-volume restore operation, ABS would not deallocate
     the drives completely. ABS would allocate additional drives to
     continue the restore operation. If there were not enough drives
     available, the restore operation would wait for a drive and never
     complete. 

  o  If a save request for a UNIX or NT system continued onto a new
     volume, ABS would not update the volume set record to reflect the
     correct length of the volume set. This would cause the next save
     request to load the previous volume rather than the correct volume
     with the end-of-volume indicator. 

  o  ABS save or restore requests with the file type of VMS Files may fail
     while attempting to load the continuation volume of a multi-volume
     set. This applies only to magazine loaders (Tx8nn DLT, TLZnL and 4mm
     DAT loaders) that automatically eject the current volume and load
     the next following a DISMOUNT/UNLOAD function. The problem involves
     a hardware feature of magazines loaders where cartridges
     automatically eject and load (from the next sequential slot)
     following a software DISMOUNT/UNLOAD command. ABS must then eject
     the auto-loaded volume and replace it with a volume from the
     magazine meeting volume selection criteria. The problem symptoms
     occur when ABS fails to wait for completion of the auto-eject-load
     before sending commands to load the selected volume. 

     Symptoms of the problem vary depending on system configuration:

       o  The device type and controller interface (HSJ controllers
          produce different symptoms than directly-connected SCSI
          controllers). Device timing of the auto-eject-load also effects
          symptoms. 

       o  The sequence of volume selection from the magazine (selection
          in the reverse direction may succeed whereas selection in the
          forward direction may fail). 

     Depending on the system configuration, one or more of the following
     symptoms may occur: 

       o  Error message %SLS-F-MRD_SLOT_FULL appearing in the log file of
          the Save/Restore. 
       o  Error message %SLS-F-MRD_UNLOAD_FAIL.
       o  One or more entries in the system hardware error log file.
       o  Device/controller timeout resulting in HSJ controllers setting
          the tape device misconfigured and unavailable as
          shown by the HSJ command SHOW Unit. 

  o  ABS save and restore requests fail when the output drive is located
     in a DCSC-controlled jukebox. The log file of the save or restore
     request shows the following failure status message, regardless of
     whether there are free volumes in the database: 

          %SLS-E-NOVOLUME, %SLS-E-NOVOLUME, the volume does not exist in
                                            the SLS database 

  o  The ABS coordinator fails with ACCVIO termination after encountering
     end-of-tape during a multi-volume save or restore operation. This
     problem occurs on Alpha systems only. The PC of the ACCVIO varies
     from system to system, but a consistent footprint is shown in the
     following instruction stream at the PC of the ACCVIO (as shown by
     ANALYZE/SYSTEM while an ABS process running the file COORDINATOR.EXE
     is active): 

          SDA> SET PROCESS/INDEX= ! Process index
          SDA> EXAMINE/INSTRUCTION @422E04-4;10 ! PC=422E04 as an example

               00000000.00422DFC: RET R31,(R26)
               00000000.00422E00: LDA SP,#xxxxx(SP)
               00000000.00422E04: STQ R27,(SP) ! Loc of ACCVIO
               00000000.00422E08: STQ R26,#xxxxx(SP)

  o  Minor Error Messages Removed

       o  In previous versions of ABS, the following message would be
          recorded in the ABS$LOG:POLICY_ENGINE_T.LOG file: 

               -E- LOG FILE OPEN FAILED

       o  Minor error messages were displayed during the unpacking of
          staging catalogs.


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  was displaying EXECUTE access in the access control 
     fields. This field can not be set using ABS. ABS SHOW  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:


abse02022.README
.CHKSUM
abse02022.a-dcx_axpexe
abse02022.a-dcx_vaxexe
abse02022.b-dcx_axpexe
abse02022.b-dcx_vaxexe
abse02022.c-dcx_axpexe
abse02022.c-dcx_vaxexe
abse02022.d-dcx_axpexe
abse02022.d-dcx_vaxexe
abse02022.e-dcx_axpexe
abse02022.e-dcx_vaxexe
abse02022.f-dcx_axpexe
abse02022.f-dcx_vaxexe
abse02022.CVRLET_

privacy and legal statement