[Info-vax] OpenVMS versus Windows/GE Telemetry Control Systems.

David Froble davef at tsoft-inc.com
Wed Jan 16 13:48:24 EST 2013


JohnF wrote:
> David Froble <davef at tsoft-inc.com> wrote:
>> JohnF wrote:
>>> Trying to convince a manager who wants to migrate
>>> that it's not necessary can't be solely based on the unadorned
>>> fact statements above.
>> Well, if a manager wants to migrate, then many times that's what is 
>> going to happen, and please don't confuse him/her with such trivia as 
>> "facts".
> 
> The very rare still-VMS-shops that I come across (for new VMS logo
> I nominate Dodo bird) are managed and staffed by old-timers who don't
> "want to migrate", as you put it, but feel pressured to migrate for
> all the reasons enumerated by many others in this ng on many previous
> occasions. Most would >>welcome<< good facts and a good argument
> not to, as far as I can tell. But you snipped the question at the
> bottom of my preceding post. Care to suggest some answers I might
> be able to pass on?

I had thought there were some very good posts in this thread about that.

See my post on 1-11, Bob Gezelter on 1,11, and others.

In general, arguing for and against upgrades of a system is not very 
productive.  Rather, a constant evaluation of the system should occur. 
The problem with that is that some will not understand the purpose. 
Some PHB is going to ask, "are we going to do something, or not?"

One good thing to have is a "disaster plan".  I would add, "an up to 
date" disaster plan.  Not just some document that was prepared in the 
past and then filed away somewhere.  Such would tell you what is 
required, should something break.  As long as there is a valid response, 
then it ain't broke.  When there is no longer a valid response, then 
perhaps it's time to come up with a valid response, whatever that is, 
and could include a plan for installing a new system.

One thing pointed out in this thread was the "lifetime" of a windows 
system.  There are people running 20 year old stuff on VMS, including 20 
year old versions of VMS.  That most likely has never happened with 
windows, and most likely won't ever happen with windows.  One important 
thing to consider is the expected lifetime of any new system.  What's 
management going to say when you tell them that their new system will 
most likely need to be replaced again is maybe 5 years?  Yeah, you can 
continue to run the old stuff, but it gets harder and harder to support 
it.  Gee, sounds like VMS sometimes.  So any new windows system isn't 
going to solve that problem, just put it off for a few years.



More information about the Info-vax mailing list