SLS SLSE01026 V2.4A - V2.6 Saveset Overwrite Correction 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 1996.  All rights reserved.
 
PRODUCT:    Storage Library System for OpenVMS (SLS)

OP/SYS:     OpenVMS VAX
            OpenVMS Alpha

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  SLSE01026
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  Saveset A - 14796 Blocks
                             Cover Letter -     5 Blocks

                         Total of 2 files - 14801 Blocks

     Kit Applies To:  SLS V2.4A, V2.5, V2.5A, V2.5B, V2.6
                      OpenVMS VAX V5.5-2 - V6.2
                      OpenVMS Alpha V6.1 - V6.2
     System/Cluster Reboot Necessary:  No


ECO KIT SUMMARY:

An ECO kit exists for SLS V2.4A thorough V2.6 on OpenVMS VAX V5.5-2
through V6.2 and OpenVMS Alpha V6.1 through V6.2.  

Problems addressed for SLS V2.4A, V2.5, V2.5A, V2.5B, and V2.6:

  o  SLS system backups or SLS RMU backups may intermittently overwrite
     savesets on continuation volumes.  This problem occurs only for
     backup operations where the output device is within a magnetic tape
     jukebox.  This problem is timing related; not all SLS customers may
     have encountered the overwrite problem.  It does not impact HSM,
     PAB, SMF or MDMS operations.
 
     Note:  This kit contains the command procedure, 
            SLS$CHECK_SUMMARY_FILES.COM, that can be used to determine
            if you, potentially, have encountered this problem.  The
            command procedure searches the SLS summary files for
            instances of the problem.  An error message from the command
            procedure signals a probable occurrence.  For each error
            message received from this command file, closely examine the
            corresponding summary file to verify that an operator
            intervention did not cause a false warning. 
 
     Potential Impact:  

            Customers may have overwritten backup savesets 
            of their data without knowing.  The problem would be
            discovered during an attempted restoration of files in the
            saveset.  The overwritten backup saveset on that tape is
            lost. 

     Please refer to the release notes, SLSE01026.RELEASE_NOTES,
     included with this ECO for more information. 

Problems addressed for SLS V2.6 only:

  o  Shared use of JU DRIVER in a VMScluster.

     SLS V2.6 addressed the problem of concurrent access to the robotics
     control port by more than one SLS$TAPMGRRQ process.  This caused
     SLS to stall while waiting for I/O completion from the JU DRIVER. 
     
     This ECO addresses a similar issue in V2.6 where concurrent access 
     by a SLS$SYSBAK image and the SLS$TAPMGRRQ process caused SLS to
     stall. 

     Note:  If this symptom is seen in SLS V2.5(x), you must upgrade
            to SLS V2.6 before applying this ECO.
  
  o  Alpha computer system process stalls.

     On Alpha computer systems, SLS processes would stall during a
     system backup or restore operation involving DCSC-controlled and
     JCS-controlled robotic systems. 

  o  Populating a TL810 or TL820 device on an Alpha system.

     When populating a TL810 or TL820 device that was connected to an
     Alpha system, it would sometimes take more than a reasonable amount
     of time to perform the operation.  The STORAGE INVENTORY JUKEBOX
     and STORAGE IMPORT CARTRIDGE commands did not work properly in this
     case. 

  o  SLS Backup and Restore operations fail.

     SLS system backup and restore operations (including RMU backup or
     restore operations) may have failed with the following error
     status: 

        %SYSTEM-F-ACCVIO, access violation, reason mask=3C, virtual
         address=0000001B, PC=0005B13C

  o  Media robots failed to start.

     In SLS and MDMS Version 2.6 only, STORAGE commands and operations
     that required robotic control devices that were not using JU Driver
     (such direct-connect SCSI and direct-connect DSSI controlled
     devices) may have failed intermittently with following error
     message: 

        %SLS-F-MRD_START_FAIL media robot driver startup failure
     or
        %SLS-F-INVEN_ROBINFO_F, cannot get robot information

  o  STORAGE INVENTORY processed volumes loaded in drive incorrectly.

     Volume status in the database was set incorrectly for any volume
     loaded in a jukebox drive during a STORAGE INVENTORY operation. 

Please refer to the release notes, SLSE01026.RELEASE_NOTES, included
with this ECO for more information. 
  

INSTALLATION NOTES:

The system/cluster does not need to be rebooted after this kit is 
installed.  

However, when installing this ECO for SLS V2.6, it is necessary to
restart SLS in order for all of the changes to take effect. 

To correct SLS V2.4A, V2.5, V2.5A, and V2.5B, you do not need to restart
SLS.  The change will take effect for the next system backup operation.

For a mixed-architecture configuration or other heterogeneous VMScluster
configurations, the ECO must be installed on each node having its own
SLS$ROOT directory structure. 

Colorado Site
Georgia Site

slse01026.README
slse01026.CHKSUM
slse01026.CVRLET_TXT
slse01026.a-dcx_axpexe
slse01026.a-dcx_vaxexe