News for hackers. Stuff that matters.
Re:OpenVMS State of the Port to x86_64 [pdf] by fleitz on Monday July 17, 2017 @02:29AM (#14786121)
Imagine server that has been up for decades. It can remain live through OS upgrades, hardware upgrades and I believe even architecture changes.

It's like places that use mainframes it's probably not a good idea to build a new bank on mainframes but if you have one it's far less risk to keep the mainframe than rewrite everything.

OpenVMS has some very unique features but truthfully it's most valuable feature is it runs the software they have.

Re:OpenVMS State of the Port to x86_64 [pdf] by wogna on Monday July 17, 2017 @02:43AM (#14786172)
But that's the thing: places which fit those requirements usually run some IBM solution (AS/400 and the likes). I've never encountered VMS in production before, so I'm really curious to some concrete examples of companies using it.
Re:OpenVMS State of the Port to x86_64 [pdf] by gobusto on Monday July 17, 2017 @03:49AM (#14786443)
I used to work as a software developer in the UK insurance industry, and I can tell you that we (and hence several of the insurers/brokers we dealt with) used OpenVMS.

In contrast to some of the other comments here, we weren't using it because moving to another OS - or architecture - would have been a pain. In fact, our software originally ran on x86 machines at some point in the distant past, before we migrated it to OpenVMS relatively recently.

I don't know why OpenVMS was given preference over GNU/Linux, *BSD, or Windows; I'm guessing that the technical managers above me had their reasons, but I couldn't say what they were.

I left that job a few years ago, but I think that they did intend to eventually phase out the VMS systems as our new, GUI-based product slowly replaced the older text-based one.

Re:OpenVMS State of the Port to x86_64 [pdf] by koyote on Monday July 17, 2017 @05:34AM (#14786884)
We use it at our company (financial software). One of the reasons being that the code is older than Linux and VMS was a good bet at the time.

We have almost entirely moved away from it and onto Linux but considering the decades of code and systems built on and around it, it is truly a monumental task to move off VMS while keeping a system used by very high paying clients running smoothly.

Re:OpenVMS State of the Port to x86_64 [pdf] by eej71 on Monday July 17, 2017 @08:55AM (#14788008)
If your employer is who I think it is - you still have many years to go. :-)
Re:OpenVMS State of the Port to x86_64 [pdf] by bbatha on Monday July 17, 2017 @11:14PM (#14794047)
I haven't used other mainframe solutions, but one of my favorite features of VMS is logicals. Logicals are environment variables backed by a clustered key value store that's safe to use for distributed locks. Logicals appear to your process in a hierarchy of tables that inherit from one another, by default you have: job (shell subprocess) > process (shell session) > user > group > system (node) > cluster. You can also build your own tables stored with which ever chosen locality (system, cluster, etc) in the hierarchy. Meaning if you follow "12-factor" design, well it didn't have fancy name then, you could do things change configuration cluster wide in an instant.
Re:OpenVMS State of the Port to x86_64 [pdf] by lb1lf on Monday July 17, 2017 @05:36AM (#14786901)
We used to have a CNC machine controlled by a VMS box. I almost burst into tears when it was unceremoniously decommissioned while I was on holiday - that thing had been up for more than six years! (Which is not at all uncommon in VMS circles!)
Re:OpenVMS State of the Port to x86_64 [pdf] by pmlnr on Monday July 17, 2017 @03:10AM (#14786283)
Non military example: IKEA.
Re:OpenVMS State of the Port to x86_64 [pdf] by tssva on Monday July 17, 2017 @03:48AM (#14786438)
VMS was widely used in healthcare.
Re:OpenVMS State of the Port to x86_64 [pdf] by fleitz on Monday July 17, 2017 @12:36PM (#14790096)
Some cable companies run it