[Info-vax] Questions and observations about OpenVMS

Forrest Aldrich forrie at forrie.com
Sat Mar 6 16:44:26 EST 2021


In follow-up, here are some questions and such I have about OpenVMS.

Consider this the perspective of an inexperienced user. I last touched 
VMS back in the late 80's, but it was cursory at best.   I want to 
understand OpenVMS today, it's role, application and possibly what 
directions it could go in.



1. Current/modern applications for OpenVMS.  What companies are using it 
and for what reason do they continue to remain on OpenVMS vs another OS 
(apart from older proprietary code that simply works, as-is).


2. Direction of OpenVMS.  Apart from older industries, I wonder about 
the future direction of OpenVMS.  They will be completing the port to 
x86_64, which I believe opens many opportunities for the platform. 
Could we see OpenVMS become a desktop server, or in smaller roles where 
clustering may also be applied.  Might we see companies like Autodesk, 
Adobe, et al embracing the platform for their products.   What would 
that mean to smaller shops that run their own servers -- or, might we 
even see OpenVMS operating in the cloud as well.    In these scenarios, 
I wonder if OpenVMS's native clustering capabilities would benefit 
resource-intensive applications -- imagine being able to cluster a few 
boxes you happen to have around as a "standard feature" (Linux lacks 
this, mostly).


3.  Licensing, relative costs.  OpenVMS is an extremely expensive OS to 
license, which may present challenges in its migrating into other 
industries.  Depending on #2, it might be difficult for a systems admin 
to justify the cost, versus other common solutions available.   I live 
close to OpenVMS's home office; my communications with them have been 
met with cold responses -- I've recommended they consider different 
licensing models.  For example, their community-based licensing is nice, 
but it's a one-off and you won't get upgrades.   As a systems admin, and 
depending on #2, I'd prefer to have a full-on, non-commercial license 
that receives all the updates -- there could be many benefits of getting 
OpenVMS into the hands of smaller shops and sysadmins.


4.  Modern/general perception of VMS.  When I mention VMS to anyone, 
I've seen eyes roll and mentions of "dinosaur" etc., but I see a 
potential "gold mine" if OpenVMS could work in the above --  with the 
right partnerships to bring more commercial (and open) code to the 
platform.   My sense is that OpenVMS probably has "enough" high-end 
commercial industry that they can afford not to care, but for how long? 
  They have been mum on future plans, but I can't imagine it doesn't 
include at least some of this.

5.  Bringing OpenVMS into the modern age.  From scanning different 
articles, it seems there remains some work in bringing OpenVMS into the 
modern world, for example updates to DCL and other relative quirks.


OpenVMS's idea of security (ie: concentric circles, operate with just 
what is needed) makes a ton of sense to me.  We don't hear about VMS 
being hacked or riddled with malware.

With the development of a nice desktop environment (think MacOS, as an 
example), I can see OpenVMS in many places it hasn't been.

Okay, that's it for now.  Forgive any ignorance, these are simply 
questions/observations I have.  I am very intrigued.



Thanks in advance,


Forrest










More information about the Info-vax mailing list