OpenVMS ALPRMS01_062 Alpha V6.2 RMS/CONVERT 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:    OpenVMS Alpha

COMPONENT:  RMS.EXE - Record Management Services 
            CONVERT.EXE
            CONVSHR.EXE
            RECLAIM.EXE

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  ALPRMS01_062
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  1959 Blocks
     Kit Applies To:  OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2
     System/Cluster Reboot Necessary:  Yes


ECO KIT SUMMARY:

An ECO kit exists for RMS and CONVERT on OpenVMS Alpha V6.2 through V6.2-1H2.
This kit addresses the following problems: 

  o  Make last chance handler more robust when a process that has  a
     file  opened  with  global  buffers  enabled is terminated with
     STOP/ID.  STOP/ID invokes the RMS  abort  last  chance  handler
     (RM$LAST_CHANCE).  Problems addressed include:

      o  A potential deadlock in the RMS last-chance handler if  the
         same  file  is  open  more  than  once  within a process or
         subprocess and it has global buffers set on it.

      o  A potential fatal KRNLSTAKNV system crash due  to  nonfatal
         RMS  bugchecks from failing $GETLKI calls which cause error
         rundown recursion until the stack fills up.

  o  Fix for a bugcheck on a compressed secondary key.  An ISAM  RMS
     nonfatal   bugcheck   is   returned  by  RM$EXPAND_KEY  (module
     RM3PCKUNP).  This bugcheck is forced if key expansion  for  the
     deletion of a secondary index data record (SIDR) would overflow
     a SIDR data bucket.

     The current problem occurs in the context of  an  $UPDATE  that
     changes a secondary key value (with key compression enabled) if
     both the SIDR data bucket freespace is  exactly  equal  to  the
     bucket  size  minus  one and the key expansion of the next SIDR
     record (if any) results in a gain in bytes exactly equal to the
     number  of  bytes  to  be  deleted.   For both conditions to be
     satisfied makes the probability of  this  problem's  occurrence
     rare.

     The update to the primary record will have been completed;  the
     problem  occurs  during  the delete operation to remove the old
     secondary key value after the new updated secondary  key  value
     has  been added.  The file is not left corrupted.  A convert of
     the file will rebuild the secondary indexes and leave the  file
     in a consistent state.

     This problem is corrected in OpenVMS Alpha V7.0.

  o  Fix for a SIDR (secondary index  data  record)  compressed  key
     expansion problem that could result in a corrupted SIDR bucket.
     The conditions that are required make the  probability  of  its
     occurrence are rare.

     For this problem to occur requires both  (1)  the  presence  of
     many duplicate records for a secondary key, (2) a secondary key
     of string type that is 9 bytes or more in  length,  and  (3)  a
     very  particular key pattern which results in a number of bytes
     at the front of the key being compressed.  The  problem  occurs
     in  the context of a bucket split when the current design moves
     an entire SIDR array into a new bucket.  It  is  possible  that
     when  the  compressed  secondary  key  for  that  SIDR array is
     expanded in its position as the first record in the new bucket,
     it may grow larger than the bucket.

     Since the problem is with a secondary  key  bucket,  a  convert
     will recover all the data records in the corrupted file.

     This problem is fixed in OpenVMS Alpha V7.0.

  o  Audit  check  fix  for  installed  /OPEN  images.    Incomplete
     security  success  audit  information  is  generated upon image
     activation of installed /OPEN images in some cases.

  o  Fix for Known File Entry (KFE) file open SSRVEXCEPT (Unexpected
     system   service  exception)  due  to  ACCVIO  in  RM$KNOWNFILE
     (RMS0OPEN).

     Heavy concurrent INSTALL and F$FILE_ATTRIBUTE usage  may  cause
     locking conflicts accessing the KFE list, which can result in a
     bad KFE pointer being handed to RMS leading to ACCVIO.

     This problem is fixed in OpenVMS Alpha V7.0.

  o  Fix for crash with kernel-mode caller.

     A kernel-mode caller may crash with  KRNLSTAKNV  (kernel  stack
     not  valid).   A  page  in  the  kernel stack has the 'fault on
     write' bit set.

  o  Statistics setting on a file is lost from the FDL  produced  by
     ANALYZE/RMS/FDL.  File monitoring is always set to 'no' whether
     it is enabled or not.  The problem is not  with  ANALYZE[/RMS],
     but with RMS's processing of an XABITM list.

  o  The following error will be reported in converting a VFC-format
     file to a fixed-format file using the /PAD qualifier:

     %LIB-F-BADBLOADR, bad block address

     The problem is restricted to a convert  job  that  involves  an
     input  file with a VFC record format that is being converted to
     an output file with  a  fixed  record  format  using  the  /PAD
     qualifier.

     This problem was introduced in OpenVMS V6.1  and  is  fixed  in
     OpenVMS V7.0.


INSTALLATION NOTES:

In order for the corrections in this kit to take effect, the system
must be rebooted.  If the system is a member of a VMScluster,  the 
entire cluster should be rebooted. 

Colorado Site
Georgia Site

alprms01_062.README
alprms01_062.CHKSUM
alprms01_062.CVRLET_TXT
alprms01_062.a-dcx_axpexe