Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp

more options
hp.com home
End of Jump to page title
HP Services software patches
Jump to content

» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

patches by topic
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

connection tools
» nameserver lookup
» traceroute
» ping

Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_BACKUP-V0200 Alpha V7.3 BACKUP ECO Summary
TITLE: OpenVMS VMS73_BACKUP-V0200 Alpha V7.3 BACKUP ECO Summary
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.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
New Kit Date:       05-MAR-2003
Modification Date:  Not Applicable
Modification Type:  NEW KIT

Copyright (c) Compaq Computer Corporation 2003.  All rights reserved.

OP/SYS:     OpenVMS Alpha 


SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  VMS73_BACKUP-V0200
     ECO Kits Superseded by This ECO Kit:  VMS73_BACKUP-V0100
     ECO Kit Approximate Size:  1344
     Kit Applies To:  OpenVMS Alpha V7.3 
     System/Cluster Reboot Necessary:  No
     Rolling Re-boot Supported:  N/A
     Installation Rating:  INSTALL_1
                           1 - To be installed by all customers

     Kit Dependencies:

       The following remedial kit(s), or later, must be installed BEFORE
       installation of this, or any required kit:

       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:




An ECO kit exists for BACKUP on OpenVMS Alpha V7.3.  This kit addresses 
the following problems: 


      o  After a BACKUP/LIST of a save-set on a disk mounted /FOREIGN,
         further access to the disk fails with a %SYSTEM-F-VOLINV error.
         The disk is inaccessible until it is dismounted, or until
         BACKUP is used to create another save-set on it.

         Images Affected:[SYSLIB]BACKUPSHR.EXE

      o  When using BACKUP to copy a directory tree, if the first file
         copied into the destination parent directory is a directory
         file which has a directory limit, then a directory version
         limit is improperly placed on the destination parent directory.

         Images Affected:[SYSLIB]BACKUPSHR.EXE

      o  If an application repetitively makes calls to backup$start
         (greater than, say, 35,000) a %backup-f-insbufspace,
         insufficient buffer space error is received.

         Images Affected:[SYSEXE}BACKUP.EXE

      o  If ODS-5 files are converted to ODS-2, the following problems
         can occur:

          o  A BACKUP/IMAGE of the disk with the /NOALIAS switch will
             not pick up the directory structure of any of the files and
             directories which were created during the time when the
             disk was an ODS-5 structure.  I.E., file and directories
             would be listed in a log file such as:

             %BACKUP-S-COPIED, copied DKA100:[]ODS5TEST.DIR
             %BACKUP-S-COPIED, copied DKA100:[]50AIPECO1NOTES.TXT
             %BACKUP-S-COPIED, copied DKA100:[]COMPAQ.TXT
             %BACKUP-S-COPIED, copied DKA100:[]DECEVENT_VMS_VAX.TXT
             %BACKUP-S-COPIED, copied DKA100:[]ESCALFMC.TXT
             %BACKUP-S-COPIED, copied DKA100:[]FATDIR.TXT
             %BACKUP-S-COPIED, copied DKA100:[]FATDRIVE.TXT

          o  When trying to add ACL's to previously created ODS-5 files,
             the following error occurs:

             %SET-I-NOALIAS, $11$DUA431:[FMCDBS]SDBXD1.JIM;1 is an alias
             entry; file not modified.

          o  Previously created ODS-5 directories with files still in
             them can be deleted with no error occurring.

          o  An ANALYZE/DISK will report the following error on
             previously created ODS-5 files which have been deleted
             after the disk was converted.

                  %ANALDISK-W-LOSTHEADER, file (18,1,1) JP.TXT
                  not found in a directory

         Images Affected:[SYSLIB]BACKUPSHR.EXE

      o  When BACKUP tries to save a shelved file, the QIO does not
         return and both BACKUP and HSM hang.  Also, when using XABITM
         to tell RMS that no caching via the XAB$_CACHING_ATTRIBUTE and
         XAB$_CACHING_OPTIONS items was done, HSM does not work
         correctly if the order was XABITM -> XABPRO

         Images Affected:[SYSEXE]BACKUP.EXE

      o  Incremental restores of or to an ODS-5 disk may get the
         following error sequence:

            %BACKUP-E-INCENTERR, error creating directory entry, etc...
            -SYSTEM-W-DUPFILENAME, duplicate file name
            %RMS-F-SYN, file specification syntax error

         Images Affected:[SYSEXE]BACKUP.EXE

      o  During an image save, BACKUP scans alias directories causing
         multiple copies of the primary files to be saved.  This
         increases the time to do the image save and the size of the

         Images Affected:[SYSEXE]BACKUP.EXE

      o  When multiple input specifiers are entered on the command line
         and wildcards are used for all file name parameters except the
         version (e.g.  *.*;), it is possible that all files could be
         saved/copied instead of just the latest version.

         Images Affected:[SYSEXE]BACKUP.EXE

      o  After an image backup, if the disk is re-mounted the following
         error may occur:

            %MOUNT-F-BADCHKSUM, bad file header checksum

         This can especially occur if the disk is mounted as a shadowset

         Images Affected:[SYSLIB]BACKUPSHR.EXE

      o  Customers running BACKUPs to tape drives that support Fast Skip
         positioning commands (characteristic of most directly connected
         DLT tape drives), and who are running MME applications, such as
         MTI's MMSUBSYS, may experience problems restoring subsequent
         volumes of a multi-tape backup.

         If tape labels are provided on the BACKUP command line for each
         of the continuation tapes, then the continuation tapes are
         created correctly.  However, if a 'scratch' tape is used, the
         continuation tape will be created with an incorrect HDR1
         record, rendering it unsuitable for future restore operations.

         No errors or warning messages will be displayed during tape
         creation, but on restore, the following error will be seen:

              %BACKUP-I-WRONGVOL, ALPHA3$MKD0:[000000]SY2_IMG.; is not the
              next volume in the set

         Images Affected:[SYSLIB]BACKUPSHR.EXE

      o  A BACKUP/XQP/IGNORE=INTERLOCK command could result in
         intermittent READATTR/NOSUCHFILE errors.

         When using a /IGNORE=INTERLOCK switch with BACKUP, files are
         accessed with NOLOCK since the use of the qualifier implies
         target files will be open.  A read operation with NOLOCK access
         (which causes the windows to be created/completed) will force
         the XQP to re-build the FCB chain.  In order to do so, the
         extension FCB chain is deleted and then rebuilt.  If, at the
         same time, another process comes along with a read attributes
         call, the XQP will find that the extension FCB chain is missing
         and not find the extension FCB for the header.  The XQP assumes
         that the caller is trying to get to the extension header
         directly and returns a NOSUCHFILE error.  There is nothing that
         the XQP can do in this case.  Another process is forcing the
         FCB chain to be rebuilt and because of the nolock access, the
         XQP cannot trust the chain.

         BACKUP attempts recovery (retry) from a READATTR error, when a
         "no such file" error is returned from the XQP when reading an
         extension header, with open, fragmented files (/IGN=INTERLOCK
         is used).

         The fix is to retry the same extension header 3 times.  If any
         of those access attempts are successful, continue to move
         forward through the file while logging the number of attempts.
         If the retry count is exhausted the file is no longer
         considered a target and the READATTR/NOSUCHFILE error will be
         reported.  A new message has been added that reports the retry

         Following are a few examples of possible message sequences:

          o  Success example 1:  Recovered from the first and only

             %BACKUP-W-READATTRRETRY, 1 READATTR error occurred reading

          o  Success example 2:  17 retries to save the file, though it
             was saved successfully.

             %BACKUP-W-READATTRRETRY, 17 READATTR errors occurred reading

          o  Failure, example 1:  A failing sequence where no successful
             retries occurred before eventually failing on the same
             extheader 3 times.

             %BACKUP-E-READATTR, error reading attributes for
             -SYSTEM-W-NOSUCHFILE, no such file
             %BACKUP-W-READATTRRETRY, 1 READATTR error occurred reading

          o  Failure Example 2:  A failing sequence of 3 successful
             retries while moving forward through the file on different
             EXTHDRS, but eventually, unable to recover from the fourth
             READATTR detected.

             %BACKUP-E-READATTR, error reading attributes for
             -SYSTEM-W-NOSUCHFILE, no such file
             %BACKUP-W-READATTRRETRY, 4 READATTR errors occurred reading

         The larger th size, more fragmented and interactive the open
         file, the lesser the chance of success.  Use of
         /IGNORE=INTERLOCK implies open files are to be processed.  If
         messages for files are paired (both READATTR/READATTRRETRY are
         reported) then the file did not get saved completely.  Success
         is a READATTRRETRY message only.

         Images Affected:[SYSEXE]BACKUP.EXE


      o  BACKUP may fail with BACKUP-F-GETCHN/SYSTEM-I-IVIDENT error
         while performing a /IMAGE operation on a disk that is mounted
         /FOREIGN.  For example:

         %BACKUP-F-GETCHN, error getting device characteristics for
         -SYSTEM-F-IVIDENT, invalid identifier format

         Images Affected:[SYSEXE]BACKUP.EXE

      o  A BACKUP-F-CLUSTER error message can be received during a
         BACKUP/IMAGE/NOINIT operation.  Particularly after
         pre-initializing a large output device with a small cluster
         value and a large/max header/ number of files.

         Images Affected:[SYSEXE]BACKUP.EXE


  o  BACKUP ignores files with ^00 in the filename

          Images Affected:  [SYSEXE]BACKUP.EXE

  o  When  BACKUP  operations  are  done  on  a  system  with  many
     resources and where either the authorized privileges or SYSGEN
     PQL values are very large, an ACCVIO could occur.

          Images Affected:  [SYSEXE]BACKUP.EXE

  o  BACKUP fails when  the  input  saveset  is  referenced  via  a
     searchlist.  For example:

          $ DIR VDE$SYSTEM:*.BCK

          Directory SYS$COMMON:[VDE]


          Total of 1 file.


          Listing of save set(s)

          %BACKUP-F-OPENIN, error opening
          -RMS-E-FNF, file not found

          Images Affected:  [SYSEXE]BACKUP.EXE

     error  combination  with  RMT  or INFOSERVER remotely accessed
     tape  devices.   Particularly  when  only  a  /LIST   and   no
     /DENSITY/MEDIA  qualifiers  are supplied in the BACKUP command

          Images Affected: [SYSEXE]BACKUP.EXE


No reboot is necessary after successful installation of the kit.

Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:


The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt

Special Installation Instructions:

     o  Scripting of Answers to Installation Questions

        During installation, this kit will ask and require user
        response to several questions.  If you wish to automate the
        installation of this kit and avoid having to provide responses
        to these questions, you must create a DCL command procedure
        that includes the following definitions and commands:


           -  Add the following qualifiers to the PRODUCT INSTALL
              command and add that command to the DCL procedure.


           -  De-assign the logicals assigned

        For example, a sample command file to install the
        VMS73_BACKUP-V0200 kit would be:

          $ exit

All trademarks are the property of their respective owners.

Files on this server are as follows:
privacy statement using this site means you accept its terms