----------------------------------------------------------------------------------
@MSGID: 2@dont-email.me> 2117f0e8
@REPLY:
<87459065-815a-4bf8-ad22-f1bea45da3ccn@googlegroups.com> 227c0dde
@REPLYADDR Simon Clubley
<clubley@remove_me.eisner.decus.org-Earth.UFP>
@REPLYTO 2:5075/128 Simon Clubley
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 2@dont-email.me>
@RFC-References:
<9-SdndysAIPxU4n4nZ2dnZfqnPednZ2d@supernews.com> <87459065-815a-4bf8-ad22-f1bea45da3ccn@googlegroups.com>
@TZUTC: -0000
@PID: slrn/0.9.8.1 (VMS/Multinet)
@TID: FIDOGATE-5.12-ge4e8b94
On 2023-09-28,
ultr...@gmail.com <
ultradwc@gmail.com> wrote:
> On Wednesday, September 27, 2023 at 8:53:13?PM UTC-4, David Turner wrote:
>> How many people are running X86 variant of OpenVMS in Production?
>> That is on the virtual machine....
>> Just want to see when I should retire....
>> ;0(
As of today, that number should be zero as x86-64 VMS is nowhere near
ready for running the mission-critical workloads that VMS is used for.
Due to these workloads, I don`t think you can call it ready until at
least 6-12 months after everything is available to production-quality
standard and VMS is being built using native compilers/etc.
However, as of today, there should also be a good number of sites
actively testing it to determine if their applications work ok and
to find and report any problems back to VSI.
Don`t forget there needs to be a business case for spending the money
to move to x86-64 VMS and a measured assessment of whether the new
platform at least meets the robustness guarantees that the company`s
current architecture provides.
>
> they need to get it running native first before you can
determine your retire date
It is running native. Do you actually mean running on bare metal ?
If so, that`s a low priority as the market has very much changed
in that area.
Simon.
--
Simon Clubley,
clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.
--- slrn/0.9.8.1 (VMS/Multinet)
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441