IMPORTANT NOTICE

Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

To obtain this kit please call the Customer Support Centre or use the FTP site Search for this ECO kit and dependencies Search the Compaq FTP web site this kit (exact match) Search the Compaq FTP web site this or related ECOs

Copyright (c) Digital Equipment Corporation 1998.  All rights reserved.

PRODUCT:    POLYCENTER Striping for OpenVMS VAX, Version 2.1

OP/SYS:     OpenVMS VAX

COMPONENT:  Striping Driver (STDRIVER)

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  STRIPEVAXE02021
     ECO Kits Superseded by This ECO Kit:  STRIPEVAXE01021
     ECO Kit Approximate Size: 1897 Blocks
                    Saveset A: 1890 Blocks

     Kit Applies To:  POLYCENTER Striping for OpenVMS VAX V2.1 on
                      OpenVMS VAX V5.4, V5.4-1, V5.4-2, V5.4-3,
                                  V5.5, V5.5-1, V5.5-2, V6.0, V6.1

     System/Cluster Reboot Necessary:  Yes

NOTE:  The installation kit for this ECO does not contain any
       executable images.  The appropriate image will be
       generated by the object modules at installation time
       depending upon the version of OpenVMS VAX to which
       the kit is applied.


ECO KIT SUMMARY:

An ECO kit exists for the Striping Driver on OpenVMS VAX V5.4
through V6.1.  This kit addresses the following problems:

PROBLEMS ADDRESSED IN STRIPEVAXE02021:

NOTE: This kit contains a remedial to correct behavior caused by the
      use of OpenVMS patch kit VAXSHAD09, "shadowing writes past the
      legal length of an IRP for OpenVMS V6.1 and earlier".  In OpenVMS
      V6.2, OpenVMS expanded the size of the IRP data structure.  The
      VAXSHAD09 patch kit utilizes these values for 6.2 and earlier
      versions of OpenVMS.

  o  Increase the size of the structure that contain the member IRPs.


PROBLEMS ADDRESSED IN STRIPEVAXE01021:

  o  If a BIND fails because a stripeset is already bound,
     some of the existing stripeset data structures are
     deallocated.

  o  When a stripeset is initialized using the /FILES_11
     qualifier, a signed comparison is made against the 8.5
     GB limit. This may cause a stripeset larger that 8.5 GB
     to be created.

  o  The BIND_UNBIND_LCK descriptor is not locked down.  This
     might cause a PGFIPLHI bugcheck to could occur when binding
     a stripeset.

  o  Incorrectly clearing the UCB$W_REFC field causes a negative
     reference count and dangling locks with cleared value blocks
     for a stripeset device.


RELATED ARTICLES:

Detailed articles describing the problems listed above may exist in
the STORAGE and OPENVMS databases.  To view these articles, open
the appropriate product database and perform a query using either of
the following search strings: 'STRIPEVAXE02021' or 'STRIPEVAX'.


ECO KIT ORDERING INSTRUCTIONS:

If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool.  If you are not familiar with how to request
kits electronically, please open the DIA or DSNLINK database and
review the article entitled:

  [AES] How To Electronically Request ECO Kits Using Service Tools


INSTALLATION NOTES:

The system must be rebooted after this kit is installed to make use
of the new images. If you have other nodes in your OpenVMS VAXcluster, they
must be rebooted or you must install this kit on each system in order
to make use of the new images.