[Info-vax] VMS Software: New US Mailing Address

[Bill Gunshannon]

On 10/12/22 20:09, Arne Vajhøj wrote:
> On 10/12/2022 8:04 PM, Bill Gunshannon wrote:
>> On 10/12/22 17:40, Arne Vajhøj wrote:
>>> On 10/12/2022 10:27 AM, Bill Gunshannon wrote:
>>>> On 10/12/22 09:05, Simon Clubley wrote:
>>>>> There's been no negative comments about Rdb recently, so I assume that
>>>>> is still on course for release on x86-64 VMS. Of course, if Rdb wasn't
>>>>> released for x86-64 VMS then that would be a very serious blow to 
>>>>> VSI's
>>>>> plans.
>>>>
>>>> A database is the least serious of these problems.  VSI could easily
>>>> (well, maybe  not easily) decide that Postgres was going to be the VMS
>>>> database just like RDB was, at one time, a DEC product.  It is easily
>>>> a suitable replacement for either Oracle or RDB.  Just suffers from NIH
>>>> syndrome.
>>>
>>> Databases are usually one of the most expensive pieces to
>>> change.
>>>
>>> Unless the client applications has been written specifically to
>>> not be tied a specific database, then there are client application
>>> changes.
>>>
>>> There is the data conversion.
>>>
>>> There is the OPS & DBA procedures and training.
>>>
>>> And everything need to be tested.
>>
>> And the alternative is to sit around and wait until someone pulls
>> the rug out from under your operation.  How much of this do VMS
>> people need to see before they start planning ahead?
> 
> I agree that it is generally good to plan ahead. And when something
> is officially declared EOL then it is time to act.

EOL time may be too late, depending on the complexity of the
application.

> 
> But in the specific case then Rdb is still promised for VMS x86-64
> and VMS PostgreSQL is not even released, so planning that one may be
> premature.

Thus the reason I mentioned VSI adopting it just as DEC owned RDB
for all those years.  Or maybe an ISV?  :-)

bill