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

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

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

connection tools
» nameserver lookup
» traceroute
» ping

Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_RMS-V0400 Alpha V7.3 RMS ECO Summary
TITLE: OpenVMS VMS73_RMS-V0400 Alpha V7.3 RMS 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.

*OpenVMS] VMS73_RMS-V0400 Alpha V7.3 RMS ECO Summary

New Kit Date:       23-JUL-2002
Modification Date:  Not Applicable
Modification Type:  NEW KIT

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

OP/SYS:     OpenVMS Alpha


SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  VMS73_RMS-V0400
     ECO Kits Superseded by This ECO Kit:  VMS73_RMS-V0300
     ECO Kit Approximate Size:  2800 Blocks
     Kit Applies To:  OpenVMS Alpha V7.3
     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), 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, or later, should also be installed:



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


  o  RMS:  Fix to prevent possible process hangs and system crashes
     when files with global buffers are accessed.

     An application accessing a file with  global  buffers  enabled
     might  experience  any one of several symptoms ranging from an
     IVLOCKID being returned to RMS through a possible  SSRVEXCEPTN
     due to corruption of an RMS internal control structure.

     Prior to this change, it is possible  for  an  internal  table
     maintained  by  RMS (the Global Buffer Interlock Table) within
     its global buffer sections to overflow.  This can  potentially
     result in corruption to adjoining control structures.  No user
     data are compromised; however, the process  may  hang  or  the
     system  crash  dependent on what is overwritten.  This problem
     is most prevalent on systems where there is a high turnover of

       Images Affected:[SYS$LDR]RMS.EXE

  o  RMS:  Fix for a lock hang on a global buffer resource.

     The symptoms of the hang are as follows:

       -  A global buffer  resource  has  in  its  granted  queue  a
              process PW lock and a system CR lock.

       -  The conversion queue for this resource has a long line  of
              NL-to-PW  or  NL-to-EX  requests blocked by the PW granted

     This is not a lock manager problem.  The PW global buffer lock
     holder  is waiting for the system CR lock to be released.  The
     release  of  the  system  CR  lock  is  dependent  on  a  flag
     (internally  managed  by RMS) indicating a writer wants access
     to the  resource  and  a  reference  count  maintained  in  an
     internal  RMS structure.  Until the system CR lock is released
     and the flag cleared  by  the  last  referencer,  the  process
     holding the PW lock will continue to block any other processes
     lining up in the conversion queue.

     This fix corrects a race condition  where  if  a  process  was
     interrupted  (stopped  or aborted by a $delprc) while actively
     using the system CR lock, it was possible for the  cleanup  of
     the  internal  RMS structure to be bypassed.  This would cause
     the reference count to get out  of  sync  and  result  in  the
     system  CR  lock  not getting properly released after a writer
     requested access to the resource.

       Images Affected:[SYS$LDR]RMS.EXE

  o  RMS:  Avoid an exec-mode infinite loop if RMS ever attempts to
     add a duplicate key value to a compressed index bucket.

     An index bucket should  never  have  a  duplicate  key  value.
     There   is   the   potential,   however,   some  inconsistency
     (corruption) in a lower level could result in such an  attempt
     in  the case of a compressed key.  A correction has been added
     to issue a nonfatal RMS bugcheck (ISAM) and avoid the loop.

       Images Affected:[SYS$LDR]RMS.EXE          

  o  RMS:  Fix for some records being potentially skipped over in a
     reverse key search.

     If the very last  bucket  in  the  data  bucket  chain  for  a
     particular  key-of-reference  is empty (no valid records), the
     potential exists for any valid records in the next-to-the-last
     bucket  (and  only  this  bucket)  being  skipped  over in the
     backwards scan done by a reverse key search.

     This problem is restricted to a reverse key search.

       Images Affected:[SYS$LDR]RMS.EXE

  o  RMS:  Correction for circumflex returned in  resultant  string
     for search error cases.

     When a one-character wildcard % is used in  a  search,  if  no
     file  is  found  (an  error is returned), the resultant string
     returned in the user NAM[L] structure  has  a  circumflex  (^)
     character  inappropriately  inserted  just before the %.  This
     affects a number of DCL utilities which display the  resultant
     string  with  their error messages (e.g., DELETE, TYPE, RENAME
     and COPY).  For example:

          $ delete %.jnk;*
          %DELETE-W-SEARCHFAIL, error searching for SYS$COMMON:[FOO]^%.JNK;*
          -RMS-E-FNF, file not found

          Images Affected:[SYS$LDR]RMS.EXE

  o  RMS:  Set the return length of the auxiliary buffer for  calls

     The return length of the auxiliary buffer  ("retlen"  optional
     parameter)  that  was passed to SYS$FILESCAN was not being set
     when the  Field  Flags  argument  ("fldflags"  parameter)  was
     absent.    This   change   sets   the   return   length  value
     unconditionally when one has been requested.

       Images Affected:[SYS$LDR]RMS.EXE

  o  CONVERT:  Fix for remote file DAP protocol regression.

     The convert utility fails with the following  error  when  the
     input  file is a sequential file on a remote foreign (non-VMS)
     system and the output file is  a  sequential  file  on  a  VMS
     system if and only if /SORT is explicitly specified or implied
     by /FDL:

     %CONV-F-READERR, Error reading (IBM_filename)
     -RMS-F-BUG_DAP, Data Access Protocol error detected; 
                     DAP code = 0001A008

     The problem is not reproducable using a remote VMS system.

       Images Affected:[SYSEXE]CONVERT.EXE


  o  Fix  for  RMS  global  buffer  hang  due  to  abort  ($delprc)

     An application may  experience  a  hang  under  the  following

       -  RMS global buffers are enabled on some files.

       -  Many processes are terminated with $delprc (e.g., STOP/ID)
          when files are still open.

       -  The   application   is   restarted   after   the   process
          terminations without rebooting the system.

     The symptom for this problem is that during the restart of the
     application,  a process enters a tight loop in executive mode.
     Once encountered, a system reboot is  required  to  clear  the

          Images Affected:  [SYS$LDR]RMS.EXE

  o  RMS fix for inconsistent secondary key index structure.

     Any application that does a lot of deleting  or  does  updates
     that  change  a  no  duplicate  secondary key value to another
     value in an indexed file is a  potential  candidate  for  this

     An ANALYZE/RMS_FILE of the indexed file reports the  following
     error for a secondary key:

        "Index bucket references missing data bucket with VBN nnn"

     The problem may be that  the  secondary  index  structure  has
     duplicate  index  value  entries  and  there  should  never be
     duplicates in the index structure.   If  the  secondary  index
     allows  a  binary  search  (is uncompressed), records could be
     hidden using an exact secondary key lookup.

     This   problem   results   from   the   entire   space   being
     inappropriately  reclaimed for the physically last SIDR record
     in some secondary data  bucket  which  contains  only  deleted

     This problem is restricted to an indexed file with a secondary
     key  that allows no duplicates.  The primary key contents will
     be intact and correct, and a convert of the file will  rebuild
     the  secondary  indexes  and  leave  the  file in a consistent

          Images Affected:  [SYS$LDR]RMS.EXE

  o  Fix to prevent the CONVERT/RECLAIM utility from  producing  an
     inconsistent  index  structure  in  an  indexed  file during a

     An ANALYZE/RMS_FILE reports the following error:

        "Index bucket references missing data bucket with VBN nnn"

     A level 1 index record associated with a data (level 0) bucket
     that  was  reclaimed was not removed from the index bucket, as
     it should have been.

     It is extremely difficult to detect  in  advance  of  doing  a
     convert/reclaim  whether  an  indexed  file is vulnerable if a
     reclaim were applied to it.  For  example,  one  condition  is
     that  one of the initial level 1 index buckets associated with
     data buckets eligible for reclamation has some condition  (for
     example,  only one index record) that will cause a rollback of
     a removed index record during a reclamation.

     Without the fix, doing a full convert  (without  the  /RECLAIM
     qualifier) ensures avoiding this problem.

          Images Affected:  [SYSEXE]RECLAIM.EXE               

  o  Fix to the CONVERT utility to prevent the signal  of  a  fatal
     read  error  (CONV-F-READERR)  with  an RMS-S-NORMAL secondary
     status when callable convert  is  invoked  within  a  threaded
     application.   This  correction  prevents  the erroneous error
     signal when the end of the input file is reached.

     Although callable convert is not a thread safe application, it
     is  possible  to  invoke  the callable interface from within a
     single instance within a single thread.

          Images Affected:  [SYSEXE]CONVERT.EXE

  o  Fix to the CONVERT utility to prevent  a  convert  which  uses
     either  network  or  tape  input from creating an empty output
     indexed file.

          Images Affected:  [SYSEXE]CONVERT.EXE


This kit requires a system reboot.  Compaq strongly recommends that
a  reboot  is performed immediately after kit installation to avoid
system instability

If you have other nodes in your OpenVMS cluster, 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.


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


  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_RMS-V0300 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