[Info-vax] How to Avoid Old Software, Old Bugs?

[Phillip Helbig undress to reply]

In article <qqhqp9$3ro$1 at dont-email.me>, Stephen Hoffman
<seaohveh at hoffmanlabs.invalid> writes: 

> On 2019-11-13 20:11:47 +0000, Dave Froble said:

> > However, a production system usually cannot afford to have problems. 
> > One might attempt testing, but the real test of any such system is 
> > actually using it.  So, it can be a bad decision, either way.

Someone, I think here in comp.os.vms (as Hoff noted, the Kabouki theatre 
of the IT world), noted that EVERYONE has a test environment---some are 
lucky enough to have an environment which does only production.  :-)

> > It's why someone was recently looking for a MiceoVAX 3100 Model 98. 
> > They may have performed extensive testing and certification, and would 
> > really rather not have to go through that procedure again if they can 
> > avoid it.
> 
> Various of us here want brute-force uptime.

> Various of us have configurations we don't even want to reboot.  What 
> does that state about the fragility of our designs and of our apps?
> 
> About what we need to work on, but haven't been able to for whatever reason?

None of that might be relevant for the MicroVAX mentioned above.

> Sites running decades-old software, or that are still running a 
> MicroVAX, that are not staying current on hardware and software?

Might be the best bet for some people.

> Sustaining these old-release environments is not a viable market for an 
> operating system software vendor.

Did anyone suggest that it is, in the context of the MicroVAX mentioned 
above?