Replies

I'm sure the majority of your applications that run on OpenVMS are based on the Alpha architecture. If this article tells us anything, it is this -- HP is NO LONGER GOING TO SUPPORT THE ALPHA PLATFORM in a few years.

DON'T MAKE ME COME DOWN THERE!

The last sales of the Alpha family will occur in 2006.

The VMS rule of thumb is that a system will be supported for at least five years after its last sale date.

Hardware support in all likelihood will continue for a long time after that.

Hardware support is still around for most MicroVAXes, VAXstations and most of the VAX family!

For those who are interested in seeing what HP's plans are for the future of VMS, here is a link to HP's OpenVMS Roadmap which is the publicly available plan (Links at the bottom of the page have presentation source)

For those with applications that run on the VMS thinking about their future, it looks like we have about 5 to 6 years to rethink if we want to run on an ITANIUM based VMS platform...( what HP calls the INTEGRITY PLATOFORM) or maybe to upgrade ( I don't think it is the right word, so lets use the word -- MOVE ) to a different Operating System platform altogether ??

Hard choices. Also hard to determine how much longer VMS will live ....I don't know if there are any new installations out there at all.

Bite your tongue for even THINKING that.

There are things I know that I can't say publicly.

VMS sales increased this year over last year.

The percentage of growth would, quite frankly surprise you. (It surprised me.)

A training vendor with whom I spoke said that this year they did more VMS training than in the last several years combined, and a good deal of this was at new sites.

9/11 opened a lot of corporate eyes about business continuity, disaster recovery and high availability computing.

Link to Success story about Commerzbank, located 100 yards from the WTC. Link to longer article in .pdf

There were several companies located *in* the WTC that ran OpenVMS and whose systems kept going thanks to the robustness of VMS clustering with systems located at remote sites.

Some years before 2001, Credit Lyonnais' data center in France BURNED DOWN, and they didn't lose any data.

The eternal monthly Microsoft patch cycle is opening corporate eyes as well.

Corporate IT departments have to test each month's patch releases with whatever their suite of software products is and then deploy the patches du jour.

If you've got more than fifty or so systems, by the time you manage to do that, another round of patches is released.

And that cycle becomes exteremely expensive in terms of down time and personnel expense, not to mention the burnout factor in the people who have to do all that stuff on nights and weekends.

I watched a major federal agency spend WEEKS and heaven knows how many thousands of man-hours eradicating a worm.

It's called Total Cost of Ownership, boys and girls.

And one plus that you haven't mentioned: OpenVMS running on Superdomes will allow you to have one system that runs multiple OS's simultaneously.

The main VMS page is located at http://www.hp.com/go/openvms

I don't work for HP, but I *am* a VMS bigot.