[Info-vax] New VSI Community license PAK

[Jan-Erik Söderholm]

Den 2020-10-21 kl. 15:57, skrev Dave Froble:
> On 10/21/2020 6:28 AM, abrsvc wrote:
>> On Tuesday, 20 October 2020 20:04:38 UTC-4, Dave Froble  wrote:
>>> On 10/20/2020 6:02 PM, abrsvc wrote:
>>>>>
>>>>> Why step 1? V8.4-2L1 runs on more or less any Alpha. To make it easier,
>>>>> use 8.4-2L1 on all Alphas, even if 8.4-2L2 *could* run on some.
>>>>
>>>> Per the note from Robert Brooks, 8.4-2l2 with patches will be required 
>>>> to be in a cluster with the x86 version.
>>>>
>>>
>>> No, Robert used "2Lx", which I take to be both 2L1 and 2L2.
>>>
>>> -- 
>>> David Froble                       Tel: 724-529-0450
>>> Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
>>> DFE Ultralights, Inc.
>>> 170 Grimplin Road
>>> Vanderbilt, PA  15486
>>
>> You are correct and I misread the note.  It would appear that both 
>> variants will be patched as you (and Robert) indicated.  My error.
>>
> 
> I will confess that I don't6 know all the ramifications, but, I do wonder 
> why VSI doesn't just issue a new version of VMS instead of a patch for an 
> existing version.  The end result would be the same, but new installs would 
> require an immediate patch.
> 

I would expect a total upgrade to need much more downtime. A patch is
usually a quick install and a reboot. It is only small parts of VMS
that are changed by this patch, after all.

A new version would also force such as Oracle to re-validate Rdb on
the new VMS version. And probably release a new version of Rdb that
has support for the new VMS version in it's version control.

No, just patching the cluster parts seems far easier.