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
» DOS
» 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 VMS712_RMS-V0100 Alpha V7.1-2 RMS ECO Summary
TITLE: OpenVMS VMS712_RMS-V0100 Alpha V7.1-2 RMS ECO Summary
 
Modification Date:  01-FEB-2001
Modification Type:  Corrected name of required PCSI kit.

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, then it can
       be expanded by typing RUN kitname.pcsi-dcx_axpexe.  The resultant
       file will be the PCSI installation file which can be used to install
       the ECO.
 
OP/SYS:     OpenVMS Alpha V7.1-2

COMPONENT:  RMS

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VMS712_RMS-V0100
                    DEC-AXPVMS-VMS712_RMS-V0100--4.PCSI
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  2960 Blocks
     Kit Applies To:  OpenVMS Alpha V7.1-2
     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) must be installed BEFORE
       installation of this kit:

         VMS712_UPDATE-V0300
         VMS62TO71U2_PCSI-V0200

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

         None


ECO KIT SUMMARY:

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

Problems Addressed in VMS712_RMS-V0100:

  o   Fix to prevent an ACCVIO on a Put  or  update  to  an  indexed
      ile.

      A LDQ  (load  quad)  instruction  generated  by  the  Bliss-64
      compiler (default quadword alignment) may result in an attempt
      being made to read or write 4 bytes beyond the end of  an  RMS
      internal  buffer which ends exactly on a page boundary with an
      adjacent inaccessible page.

      The process may either:

        +  Terminate (if SYSGEN parameter BUGCHECKFATAL not  enabled)
           with an access violation (ACCVIO); or

        +  Crash  the  system  (if  BUGCHECKFATAL  enabled)  with   a
           SSRVEXCEPT ACCVIO.

      There are too many variables (for example, bucket size, number
      of  buffers,  record  location,  number of keys) to predict in
      advance that a file is vulnerable to this  problem.   However,
      we  do  know  that the right combination of conditions must be
      rare since the problem has been dormant for several  releases.
      It  was introduced with the conversion of several Bliss-32 RMS
      modules  to  Bliss-64  as  part  of  the  support  for  64-bit
      addresses added to Alpha V7.0.


      This fix is included in the next release after  OpenVMS  Alpha
      V7.2-1H1.


  o   Mark the Buffer Descriptor as busy for asynch multistreamed 
      block IO autoextends

      Performing  multistreamed  asynchronous  Block  IO  to  a
      sequential  file  could  result in random data corruption
      and/or sporadic  SS$_BADPARAM  errors  if  an  autoextend
      occurs.


      This fix is included in OpenVMS Alpha V7.2-1H1.

  o   Fix for potential application (or system) hang associated
      with global buffer hashing interlock.

      This kit includes fixes for two problems with the  global
      buffer  hashing  interlock  implementation  that have the
      potential of blocking the progress of other processes and
      thus inducing an application hang:

        +  Close potential window when  a  process  is  deleted.
           Expand  the  interlocked  instruction  for one bit to
           include  whole  quadword  so  that  modify  of   both
           interlock  and  pid gets done as an atomic operation.
           Otherwise, a process could be deleted  after  it  had
           set  the  interlock  but  before  its  pid  had  been
           assigned, which could result in there being no way to
           detect  that  an  interlock was held by a nonexistent
           process.

        +  Vary the timer delay before each retry for a  process
           waiting  for  an  interlock  to  be  released.   With
           sufficient contention, it was found that  the  system
           timer  processing  at  IPL 8 could block progress for
           the process  currently  holding  the  interlock  when
           expiration times were all restricted to 1 Msec.

      This fix is included in OpenVMS Alpha V7.2-1H1.


  o   Correction for processes exiting with RMS IORNDN non-fatal 
      bugcheck.

      Processes  may  disappear  with  RMS   IORNDN   non-fatal
      bugchecks  when an EXIT is requested by an Executive-mode
      application (such as ACMS).  This is a very small  timing
      window,  so  processes  with  a  large  number  of  files
      increases the probability of the problem occurring.

      If the SYSGEN parameter  BUGCHECKFATAL  is  not  enabled,
      then  the  process  will be terminated; if it is enabled,
      then the system will crash with  a  RMSBUG  (R2=FFFFFFF0,
      IORNDN) bugcheck.


      This fix is included in OpenVMS Alpha V7.2-1H1.

  o   FAL resource identifier file owner fix

      Creation of a file over  the  network  into  a  directory
      owned  by  a  resource identifier strips the high order 2
      bits  of  the  owner  field,  corrupting  the   ownership
      information.   Checking  the  owner  on the remote system
      will reveal a UIC looking  value  derived  from  the  low
      order  bits  of  the identifier.  Directory commands to a
      remote system will also strip the high order 2 bits  from
      a general identifier on the remote system, formatting the
      result in UIC format.

      The stripping of the high order 2 bits of the owner value
      may  result  in  the following errors being returned to a
      non-privileged user performing a  COPY/LOG  to  a  remote
      directory owned by a resource identifier:

      %COPY-S-COPIED, {file spec.} copied to {remote file spec.}
      %COPY-E-CLOSEOUT, error closing {file specification} as output
      -RMS-E-PRV, insufficient privilege or file protection
      violation.
                       
                    SPR_VMS_V5: # 05990
                    SPR_VMS_V5: # 02759
                    SPR_VMS_V5: # 02144
                    SPR_VMS_V5: # 00675
                    V6:         # 00287

      This fix is included in OpenVMS Alpha V7.2.

  o   Support for SET RMS_DEFAULT /CONTENTION_POLICY to address
      locking fairness issues.

      The  new  Alpha  global  buffer  read-mode  lock  support
      introduced  in  V7.2-1H1  is functionally compatible with
      both VAX and older Alpha releases.  Operations  in  mixed
      clusters  produce  correct  results.  However, there is a
      locking fairness issue that may arise with mixed  cluster
      operations.

      In a mixed cluster environment with very high  contention
      for  specific  buckets,  it  is  possible for accesses to
      write-shared  files  on  nodes  using  read-mode   bucket
      locking  to  dominate  access to a bucket.  Nodes without
      this support might be unable to access the bucket  for  a
      protracted period of time.

      It is also possible to observe comparable behavior on all
      OpenVMS   versions   when   dealing   with   accesses  to
      write-shared files without global buffers enabled -- even
      on a standalone system.  A similar fairness issue between
      lock conversions and new lock requests may be observed in
      which  the  new lock requests may remain ungranted for an
      extended period of time.

      This kit includes support in RMS  for  a  new  option  to
      improve  fairness  under  high  contention conditions for
      write-shared  files,  but  selecting  this   option   may
      noticably  increase  locking overhead.  The option may be
      set  at  a  process  or   system   level.    Since   many
      applications

      will never  encounter  this  issue,  the  default  system
      behavior  leaves  this  option  disabled.   A future lock
      management  enhancement   should   make   this   fairness
      workaround unnecessary for later releases.

      The option is  controlled  using  the  /CONTENTION_POLICY
      qualifier  to  the  DCL  command  SET  RMS_DEFAULT.   The
      following  are  valid  PROCESS  keywords   (/SYSTEM   not
      specified):

          NEVER        Never use the higher overhead option
                       to improve fairness for any write-shared
                       files accessed by this process; minimal
                       overhead.

          SOMETIMES    Use this option for fairer bucket
                       access (but higher overhead) to any
                       write-shared files with global
                       buffers enabled that are accessed by this
                       process.

          ALWAYS       Use this option for fairer bucket
                       access (but higher overhead) to all              
                       write-shared files accessed by this
                       process.

          SYSTEM_DEFAULT  (Default)  Use system setting. Note
                       that this keyword is disallowed with
                       /SYSTEM.


      The  following  are  valid   SYSTEM   keywords   (/SYSTEM
      specified):

          NEVER        (Default) Never use the higher
                       overhead option to improve fairness
                       for any write-shared files accessed
                       on the system; minimal overhead.

          SOMETIMES    Use this option for fairer bucket
                       access (but higher overhead) to any
                       write-shared files with global
                       buffers enabled that are accessed
                       on the system.

          ALWAYS       Use this option for fairer bucket
                       access (but higher overhead) to all
                       write-shared files accessed on the
                       system.                  


      In addition  to  the  RMS  image,  modifications  to  the
      following images are required:

                -  [SYSEXE]SET.EXE
                -  [SYSEXE]SHOW.EXE
                -  [SYSMSG]CLIUTLMSG.EXE
                -  replacement of modified SET.CLD in
                   [SYSLIB]DCLTABLES.EXE

      These   modified   images   are    available    in    the
      VMS712_CLIU-V0100   kit.    The  interface  to  this  new
      functionality is not available until this CLIUTL  kit  is
      installed.   Until  the  CLIUTL TIMA kit is available and
      installed, the default of NEVER for the CONTENTION_POLICY
      option cannot be overriden.

      Support for this new functionality in SET RMS_DEFAULT  is
      included   in   the  next  release  after  OpenVMS  Alpha
      V7.2-1H1.

  o   Prevent  callable  CONVERT  from  producing   ACCVIO   on
      repeated calls.

      The CONVERT utility may return an access violation and/or
      sort_on  errors when it is repeatedly invoked from within
      an  application   utilizing   the   callable   interface.
      Additionally,  an  invalid  file structure may be created
      when the callable interface is  invoked  repeatedly  from
      within an application.


      This fix is included in OpenVMS Alpha V7.2-1H1.

  o   Expand statistic display fields for Convert.

      The record count and/or bucket counts  displayed  by  the
      statistics  function  and  ^T  function  of  Convert were
      previously limited to 8 digits.  This resulted in a field
      of  "*"s  being displayed when greater than 8 digits were
      required for displaying.


      This fix is included in OpenVMS Alpha V7.2-1H1.


INSTALLATION NOTES:

The images in this kit will not take effect until the system is
rebooted.  If there are other nodes in the VMScluster, 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:

PRODUCT INSTALL VMS712_RMS /SOURCE=[location of Kit]

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

All trademarks are the property of their respective owners.

Files on this server are as follows:
»dec-axpvms-vms712_rms-v0100--4.README
»dec-axpvms-vms712_rms-v0100--4.CHKSUM
»dec-axpvms-vms712_rms-v0100--4.pcsi-dcx_axpexe
»vms712_rms-v0100.CVRLET_TXT
privacy statement using this site means you accept its terms