  Mixed Version OpenVMS Cluster Support? 
 The Question is:
 
I have inherited a vax cluster consisting of
three workstations running vms 5.5-2, vms 6.1
and axp 6.1.   I cannot update the 5.5-2 due to
a dbms restriction.  In order to implemment patches
for y2k, I need to upgrade to vms 6.2 and axp
6.2.  Do you know if I can maintain the cluster
with (vms 5.5-2, vms 6.2 and axp 6.2).
 
I did get one answer from digital tech support,
indicating it would work with the y2k patches,
but the newsgroups indicate otherwise.
 
any thought appreciated
 
-rick raughton
 Virginia Commonwealth Univ
 
 
 The Answer is:
 
  From the OpenVMS Cluster Software Product Description (SPD) for V6.2:
 
    - Migration support is provided for VMSclusters running
      OpenVMS Version 6.2 and OpenVMS Versions 1.5 (Alpha), 5.5-2
      &amp; 6.0 (VAX), and V6.1 (Alpha &amp; VAX).
 
      Migration support means that Digital has qualified the two
      architectures/versions for use together in configurations
      that are migrating in a staged fashion to a higher version
      of OpenVMS or to Alpha systems. Digital will answer problem
      reports submitted about these configurations. However, in
      exceptional cases, Digital may recommend that you move your
      system to a warranted configuration as part of the solution.
 
    Note that Digital does not support the use of more than two
    versions of OpenVMS software in a VMScluster at a time.
 
    Digital recommends that all Alpha and VAX systems in a VMScluster
    run the latest version of OpenVMS.
 
  Certain of the answers you received to your 9-Jul-1999 posting of "y2k
  issue VMS 6.1 and 5.5-2" in the comp.os.vms newsgroup are incorrect or
  are misleading, or are potentially referencing details or other
  information not included in the particular question posed here.
 
  There are a few known restrictions in these mixed-version configurations,
  such as certain SYSMAN commands not necessarily functioning when originated
  from and targeting systems of certain version combinations.
 
  If you do move to OpenVMS V6.2 and then to the more recent V6.2 ECO kits
  for MOUNT and shadowing and similar, you will have a version of MOUNT and
  associated code that is newer than that of V5.5-2, though MOUNT is expected
  to be compatible.  (You will have the various problems that were fixed in
  the newer MOUNT lurking, obviously.)  These mixed-MOUNT configurations are
  intended for supporting rolling upgrades -- effectively similar to the
  migration environment referenced in the SPD.
 
  That written, there may well be no particular technical need to apply the
  Y2K Readiness kit, though non-technical requirements can (and often do)
  obviously dictate otherwise -- see the Y2K kit for details on the areas
  of OpenVMS affected.  The OpenVMS Wizard would strongly recommend testing
  your configuration, whether or not you choose to install the Y2K Readiness
  kit -- this testing should help you ferret out any catastrophic failures.
  Information on the recommended Y2K readiness testing procedures is
  included in the OpenVMS home page, and referenced in the OpenVMS FAQ.
  (The OpenVMS Wizard strongly discourages skipping any steps listed in the
  Y2K readiness testing procedure -- all steps are present for specific
  reasons, and to avoid specific problems, and to ensure that the systems
  will be functional after testing has completed.)
 
