SUPPORT THE WORK

GetWiki

OpenVMS

ARTICLE SUBJECTS
aesthetics  →
being  →
complexity  →
database  →
enterprise  →
ethics  →
fiction  →
history  →
internet  →
knowledge  →
language  →
licensing  →
linux  →
logic  →
method  →
news  →
perception  →
philosophy  →
policy  →
purpose  →
religion  →
science  →
sociology  →
software  →
truth  →
unix  →
wiki  →
ARTICLE TYPES
essay  →
feed  →
help  →
system  →
wiki  →
ARTICLE ORIGINS
critical  →
discussion  →
forked  →
imported  →
original  →
OpenVMS
[ temporary import ]
please note:
- the content below is remote from Wikipedia
- it has been imported raw for GetWiki
{{Short description|Computer operating system}}{{Use mdy dates|date=November 2022}}









! Version! Vendor! Release dateWEB,weblink HP OpenVMS Systems - OpenVMS Release History, June 21, 2010,weblink" title="web.archive.org/web/20181007091949weblink">weblink October 7, 2018, WEB,weblink OpenVMS – A guide to the strategy and roadmap, VSI, September 27, 2021, ! End of supportWEB,weblink HP OpenVMS Systems - Supported Software Versions - January 2014,weblink" title="web.archive.org/web/20181014105654weblink">weblink October 14, 2018, WEB,weblink VSI OpenVMS Software Roadmap 2021, September 30, 2021, VSI, WEB,weblink OpenVMS Software Technical Support Service, October 2003, Hewlett Packard, February 1, 2022, hp.com, {{Dead link|date=January 2023 |bot=InternetArchiveBot |fix-attempted=yes }}! Platform! Significant changes, new hardware supportWEB,weblink OpenVMS Release History, HP, Bitsavers, January 23, 2022, | June 2004| Alpha
factoids
name OpenVMS| logo = Vsi-openvms-logo.svg| logo size = 250px| screenshot = DECwindows-openvms-v7.3-1.png



Common Desktop Environment>CDE-based DECwindows "New Desktop" GUICOMPUTERWORLD
(PREVIOUSLY DIGITAL EQUIPMENT CORPORATION, COMPAQ, HEWLETT-PACKARD)
PROPRIETARY SOFTWARE>CLOSED-SOURCE WITH OPEN-SOURCE SOFTWARE COMPONENTS. FORMERLY SOURCE AVAILABLE{{CITE WEB>URL=HTTPS://WWW.YOUTUBE.COM/WATCH?V=E8X3TGLFGO8 ARCHIVE-DATE=DECEMBER 11, 2021 TITLE=WEBINAR 16: X86 UPDATEPUBLISHER=VSI, November 2, 2021, {{cbignore}}| kernel_type = Monolithic kernel with loadable modulesVAX, DEC Alpha>Alpha, Itanium, x86-64DIGITAL Command Language>DCL Command-line interface and DECwindows Graphical user interface>GUIACCESS-DATE=2024-01-25TITLE=OPENVMS V9.2-2 PUBLIC AVAILABILITY, VSI, Server (computing)>Servers (historically Minicomputers, Workstations)C (programming language)>C, BLISS, VAX MACRO, DIGITAL Command Language.HTTPS://GROUPS.GOOGLE.COM/G/COMP.OS.VMS/C/3SWQIRQA1Y4/M/NPX29NM-AWAJAUTHOR=CAMIEL VANDERHOEVEN, May 30, 2021, comp.os.vms, October 21, 2021, Other languages also used.WEB,weblink The OpenVMS Frequently Asked Questions (FAQ), 2.7 In what language is OpenVMS written?, Hewlett Packard Enterprise,weblink" title="web.archive.org/web/20180810010816weblink">weblink August 10, 2018, English language>English, Japanese language.HTTPS://VMSSOFTWARE.COM/PRODUCTS/JVMS/WEBSITE=VSIChinese language>Chinese (both Traditional Chinese and Simplified Chinese>Simplified characters), Korean language, Thai language>Thai.HTTP://WWW.DTJCD.VMSRESOURCE.ORG.UK/PDFS/DTJ_V05-03_1993.PDF>AUTHOR=MICHAEL M. T. YAUJOURNAL=DIGITAL TECHNICAL JOURNALISSUE=3YEAR=1993, October 21, 2021, | updatemodel = Concurrent upgrades,rolling upgrades| package_manager = PCSI and VMSINSTAL| working_state = CurrentProprietary software>Proprietaryweblink}}| influenced_by = RSX-11MVAXELN, DEC MICA>MICA, Windows NT}}OpenVMS, often referred to as just VMS,WEB,weblink October 1997, OpenVMS at 20 Nothing stops it, Digital Equipment Corporation, February 12, 2021, is a multi-user, multiprocessing and virtual memory-based operating system. It is designed to support time-sharing, batch processing, transaction processing and workstation applications.WEB
,weblink
, Software Product Description and QuickSpecs - VSI OpenVMS Version 8.4-2L1 for Integrity servers
, VMS Software Inc.
, July 2019
, January 2, 2021
, Customers using OpenVMS include banks and financial services, hospitals and healthcare, telecommunications operators, network information services, and industrial manufacturers.WEB,weblink April 2019, May 4, 2021, VSI Business & New Products Update – April 9, 2019, VSI, MAGAZINE,weblink VMS Operating System Is 30 Years Old; Customers Believe It Can Last Forever, InformationWeek, November 1, 2007, Charles Babcock, February 19, 2021, During the 1990s and 2000s, there were approximately half a million VMS systems in operation worldwide.WEB,weblink OpenVMS survives and thrives, Drew Robb, November 1, 2004, computerworld.com, December 31, 2020, WEB,weblink Digital tries to salvage OpenVMS, Tao Ai Lei, May 30, 1998, December 31, 2020, computerworld.co.nz, September 25, 2021,weblink dead, WEB,weblink" title="web.archive.org/web/20060217141711weblink">weblink February 17, 2006,weblink October 1997, February 12, 2021, OpenVMS: 20 Years of Renewal, Jesse Lipcon, Digital Equipment Corporation, It was first announced by Digital Equipment Corporation (DEC) as VAX/VMS (Virtual Address eXtension/Virtual Memory SystemWEB,weblink VAX-11/780 Hardware Handbook, 1979, October 17, 2022, Digital Equipment Corporation, ) alongside the VAX-11/780 minicomputer in 1977.NEWS
, Computerworld
, Patrick Thibodeau
,weblink
, OpenVMS, R.I.P. 1977-2020?
, June 11, 2013
, April 27, 2024
, BOOK
, Chronology of Tech History, 104,weblink
, 978-1300253075, Tom Merritt, 2012, Lulu.com, WEB, VAX 11/780 - OLD-COMPUTERS.COM : HISTORY / detailed info,weblink
archive-url=https://web.archive.org/web/20230926164342weblinkurl-status=dead, OpenVMS has subsequently been ported to run on DEC Alpha systems, the Itanium-based HPE Integrity Servers,WEB
,weblink
, Supported Platforms, VSI, and select x86-64 hardware and hypervisors. Since 2014, OpenVMS is developed and supported by VMS Software Inc. (VSI).WEB, HP hands off OpenVMS development to VSI
,weblink
, Tech Times, August 1, 2014, April 27, 2024, PRESS RELEASE, VMS Software, Inc. Named Exclusive Developer of Future Versions of OpenVMS Operating System,weblink
high availability through computer cluster>clustering—the ability to distribute the system over multiple physical machines. This allows clustered applications and data to remain continuously available while operating system software and hardware maintenance and upgrades are performed,HTTPS://WEB.ARCHIVE.ORG/WEB/20120229042903/HTTP://WWW.OPENVMS.ORG/STORIES.PHP?STORY=03%2F11%2F28%2F7758863>ARCHIVE-DATE=FEBRUARY 29, 2012TITLE=CLUSTER UPTIMEACCESS-DATE=DECEMBER 20, 2020DATE=JULY 2009ACCESS-DATE=MAY 4, 2021PUBLISHER=VSI,

History

Origin and name changes

(File:VAX VMS logo.svg|thumb|right|Stylized "VAX/VMS" used by Digital)In April 1975, Digital Equipment Corporation embarked on a project to design a 32-bit extension to its PDP-11 computer line. The hardware component was code named Star; the operating system was code named Starlet. Roger Gourd was the project lead for VMS. Software engineers Dave Cutler, Dick Hustvedt, and Peter Lipman acted as technical project leaders.INTERVIEW, Cutler, Dave, Dave Cutler, Grant Saviers, Dave Cutler Oral History,weblinkweblink December 11, 2021, live, Computer History Museum, February 25, 2016, youtube.com, February 26, 2021, {{cbignore}} The Star and Starlet projects culminated in the VAX-11/780 computer and the VAX/VMS operating system. The Starlet project's code name survives in VMS in the name of several of the system libraries, including STARLET.OLB and STARLET.MLB. VMS was mostly written in VAX MACRO with some components written in BLISS.One of the original goals for VMS was backward compatibility with DEC's existing RSX-11M operating system. Prior to the V3.0 release, VAX/VMS included a compatibility layer named the RSX Application Migration Executive (RSX AME), which allowed user-mode RSX-11M software to be run unmodified on top of VMS. The RSX AME played an important role on early versions of VAX/VMS, which used certain RSX-11M user-mode utilities before native VAX versions had been developed. By the V3.0 release, all compatibility-mode utilities were replaced with native implementations.NEWSGROUP,weblink a simple question: what the h*ll is MCR?, December 31, 2020, September 14, 2004, comp.os.vms, In VAX/VMS V4.0, RSX AME was removed from the base system, and replaced with an optional layered product named VAX-11 RSX.WEB,weblink Software Product Description VAX-11 RSX, Version 1.0, October 1984, Digital Equipment Corporation, September 20, 2021, File:Vms-albert-cheshire-cat.png|thumb|right|"Albert the Cheshire Cat" mascot for VAX/VMS, used by the DECUSDECUSA number of distributions of VAX/VMS were created:
  • MicroVMS was a distribution of VAX/VMS designed for MicroVAX and VAXstation hardware, which had less memory and disk space than larger VAX systems of the time.BOOK, Getting Started with OpenVMS: A Guide for New Users,weblink 978-0080507354, Michael D Duffy, 2002, Elsevier, MicroVMS split up VAX/VMS into multiple kits, which a customer could use to install a subset of VAX/VMS tailored to their specific requirements.NEWS, Computerworld, June 18, 1984, 7, The Micro VMS operating system announced last week by Digital Equipment Corp. for its Microvax I family of microcomputers is a prepackaged version of ..., Micro VMS operating system,weblink MicroVMS releases were produced for each of the V4.x releases of VAX/VMS and was discontinued when VAX/VMS V5.0 was released.MAGAZINE, DEC Professional Magazine, The VMS/MicroVMS merge, 74–84
DATE=APRIL 1988ACCESS-DATE=JULY 21, 2021,
  • Desktop-VMS was a short-lived distribution of VAX/VMS sold with VAXstation systems. It consisted of a single CD-ROM containing a bundle of VMS, DECwindows, DECnet, VAXcluster support, and a setup process designed for non-technical users.WEB,weblink DECUServe WORKSTATIONS Conference 8, December 22, 2020, January 11, 1989, Bob McCormick, home.iae.nl, July 10, 2022,weblink" title="web.archive.org/web/20220710024529weblink">weblink dead, WEB,weblink Office Archaeology, February 24, 2004, December 22, 2020, blog.nozell.com, Desktop-VMS could either be run directly from the CD or could be installed onto a hard drive.WEB,weblinkweblink" title="web.archive.org/web/20000816181649weblink">weblink Software Product Description - Desktop-VMS, Version 1.2, Digital, January 1991, August 16, 2000, February 2, 2022, Desktop-VMS had its own versioning scheme beginning with V1.0, which corresponded to the V5.x releases of VMS.WEB,weblink OpenVMS pages of proGIS Germany, vaxarchive.org, December 22, 2020,
  • An unofficial derivative of VAX/VMS named MOS VP ()WEB,weblink Computer Complexes, Technical Equipment, Software And Support Of The System Of Small Electronic Computer Machines (SM Computer), May 1989, Russian, Soviet Union Research Institute of Information and Economics, October 16, 2021, D.O. Andrievskaya, was created in the Soviet Union during the 1980s for the SM 1700 line of VAX clone hardware.JOURNAL,weblink Software Systems Journal, 1988, 3, Basic software for 32-bit SM computer models, Prokhorov N.L., Gorskiy V.E., Russian, October 15, 2021, JOURNAL,weblink Software Systems Journal, 1988, 4, Multifunctional operating system that supports virtual memory for 32-bit computers, Egorov G.A., Ostapenko G.P., Stolyar N.G., Shaposhnikov V.A., Russian, October 15, 2021, MOS VP added support for the Cyrillic script and translated parts of the user interface into Russian.WEB,weblink Installing OS MOS-32M, June 16, 2012, October 15, 2021, Russian, pdp-11.ru, October 27, 2021,weblink dead, Similar derivatives of MicroVMS known as MicroMOS VP () or MOS-32M () were also created.
With the V5.0 release in April 1988, DEC began to refer to VAX/VMS as simply VMS in its documentation.WEB,weblink VMS Version 5.0 Release Notes, April 1988, Digital Equipment Corporation, October 27, 2021, In July 1992,WEB,weblink Digital Introduces First Generation of OpenVMS Alpha-Ready Systems, Digital Equipment Corporation, July 15, 1992, January 25, 2021, DEC renamed VAX/VMS to OpenVMS as an indication of its support of open systems industry standards such as POSIX and Unix compatibility,WEB, OpenVMS Definition from PC Magazine Encyclopedia
AUTHOR=ARNE VAJHøJACCESS-DATE=JANUARY 25, 2021ARCHIVE-DATE=SEPTEMBER 24, 2021URL-STATUS=DEAD,

Port to Alpha

{{See also|DEC PRISM#Legacy|DEC Alpha#History}}
missing image!
- dec-vms-vernon.png -
"Vernon the Shark" logo for OpenVMSWEB,weblink History of the Vernon the VMS shark, vaxination.ca, January 24, 2021,
During the 1980s, DEC planned to replace the VAX platform and the VMS operating system with the PRISM architecture and the MICA operating system.WEB,weblink DECwest/SDT Agenda, Dave Cutler, May 30, 1988, bitsavers.org, When these projects were cancelled in 1988, a team was set up to design new VAX/VMS systems of comparable performance to RISC-based Unix systems.WEB,weblink EV-4 (1992), February 24, 2008, After a number of failed attempts to design a faster VAX-compatible processor, the group demonstrated the feasibility of porting VMS and its applications to a RISC architecture based on PRISM. This led to the creation of the Alpha architecture.WEB,weblink April 1993, Managing Technological Leaps: A study of DEC's Alpha Design Team, The project to port VMS to Alpha began in 1989, and first booted on a prototype Alpha EV3-based Alpha Demonstration Unit in early 1991.JOURNAL, How DEC developed Alpha, July 1992, 10.1109/6.144508, Comerford, R., IEEE Spectrum, 29, 7, 26–31, JOURNAL, Supnik, Robert M., Digital's Alpha project, Communications of the ACM, 36, 2, 1993, 30–32, 0001-0782, 10.1145/151220.151223, 32694010, free, The main challenge in porting VMS to a new architecture was that VMS and the VAX were designed together, meaning that VMS was dependent on certain details of the VAX architecture.JOURNAL,weblink Porting OpenVMS to HP Integrity Servers, Clair Grant, OpenVMS Technical Journal, 6, June 2005, Furthermore, a significant amount of the VMS kernel, layered products, and customer-developed applications were implemented in VAX MACRO assembly code. Some of the changes needed to decouple VMS from the VAX architecture included the creation of the MACRO-32 compiler, which treated VAX MACRO as a high-level language, and compiled it to Alpha object code,JOURNAL,weblink Porting OpenVMS from VAX to Alpha AXP, Nancy P. Kronenberg, Thomas R. Benson, Wayne M. Cardoza, Ravindran Jagannathan, Benjamin J. Thomas III, Digital Technical Journal, 4, 4, 111–120, 1992, April 27, 2024, and the emulation of certain low-level details of the VAX architecture in PALcode, such as interrupt handling and atomic queue instructions.The VMS port to Alpha resulted in the creation of two separate codebases: one for VAX, and another for Alpha.WEB,weblink Access to OpenVMS Source Code?, HP OpenVMS Systems ask the wizard,weblink" title="web.archive.org/web/20171028043200weblink">weblink October 28, 2017, September 2, 1999, The Alpha code library was based on a snapshot of the VAX/VMS code base circa V5.4-2. 1992 saw the release of the first version of OpenVMS for Alpha AXP systems, designated OpenVMS AXP V1.0. In 1994, with the release of OpenVMS V6.1, feature (and version number) parity between the VAX and Alpha variants was achieved; this was the so-called Functional Equivalence release.WEB,weblink OpenVMS Compatibility Between VAX and Alpha, May 1995, Digital Equipment Corporation, October 22, 2021, The decision to use the 1.x version numbering stream for the pre-production quality releases of OpenVMS AXP confused some customers, and was not repeated in the subsequent ports of OpenVMS to new platforms.When VMS was ported to Alpha, it was initially left as a 32-bit only operating system. This was done to ensure backwards compatibility with software written for the 32-bit VAX. 64-bit addressing was first added for Alpha in the V7.0 release.JOURNAL,weblink Extending OpenVMS for 64-bit Addressable Virtual Memory, Digital Technical Journal, 8, 2, 1996, 57–71, 9618620, In order to allow 64-bit code to interoperate with older 32-bit code, OpenVMS does not create a distinction between 32-bit and 64-bit executables, but instead allows for both 32-bit and 64-bit pointers to be used within the same code.JOURNAL,weblinkweblink dead, February 19, 2020, The OpenVMS Mixed Pointer Size Environment, Digital Technical Journal, 8, 2, 1996, 72–82, 14874367, This is known as mixed pointer support. The 64-bit OpenVMS Alpha releases support a maximum virtual address space size of 8TiB (a 43-bit address space), which is the maximum supported by the Alpha 21064 and Alpha 21164.WEB,weblink VSI OpenVMS Programming Concepts Manual, Vol. 1, April 2020, October 7, 2020, VSI, One of the more noteworthy Alpha-only features of OpenVMS was OpenVMS Galaxy, which allowed the partitioning of a single SMP server to run multiple instances of OpenVMS. Galaxy supported dynamic resource allocation to running partitions, and the ability to share memory between partitions.WEB,weblink HP OpenVMS Alpha Partitioning and Galaxy Guide, September 2003, HP, October 22, 2021, WEB,weblink Compaq details strategy for OpenVMS, October 14, 1998, January 14, 2021, James Niccolai, Australian Reseller News, April 4, 2023,weblink dead,

Port to Intel Itanium

missing image!
- OpenVMS logo Swoosh 30 lg.jpg -
"Swoosh" logo used by HP for OpenVMS
In 2001, prior to its acquisition by Hewlett-Packard, Compaq announced the port of OpenVMS to the Intel Itanium architecture.WEB,weblink Compaq OpenVMS Times, January 2002,weblink" title="web.archive.org/web/20060302213751weblink">weblink March 2, 2006, dead, The Itanium port was the result of Compaq's decision to discontinue future development of the Alpha architecture in favour of adopting the then-new Itanium architecture.WEB,weblink Farewell then, Alpha – Hello, Compaq the Box Shifter
date=June 25, 2001website=theregister.com, The porting began in late 2001, and the first boot on took place on January 31, 2003.HTTPS://GROUPS.GOOGLE.COM/G/COMP.OS.VMS/C/ALWTUE7YLUW/M/X1_GVV1EFFEJ>TITLE=OPENVMS BOOTS ON ITANIUM ON FRIDAY JAN 31ACCESS-DATE=DECEMBER 21, 2020NEWSGROUP=COMP.OS.VMS, The first boot consisted of booting a minimal system configuration on a List of Hewlett-Packard products#Itanium based workstation, logging in as the SYSTEM user, and running the DIRECTORY command. The Itanium port of OpenVMS supports specific models and configurations of HPE Integrity Servers. The Itanium releases were originally named HP OpenVMS Industry Standard 64 for Integrity Servers, although the names OpenVMS I64 or OpenVMS for Integrity Servers are more commonly used.HTTPS://VMSSOFTWARE.COM/DOCS/IG_BVBV.PDFDATE=JUNE 2007ACCESS-DATE=MARCH 2, 2021, The Itanium port was accomplished using source code maintained in common within the OpenVMS Alpha source code library, with the addition of conditional code and additional modules where changes specific to Itanium were required. This required certain architectural dependencies of OpenVMS to be replaced, or emulated in software. Some of the changes included using the Extensible Firmware Interface (EFI) to boot the operating system,WEB,weblink OpenVMS Integrity Boot Environment, 2005, December 21, 2020, Thomas Siebold, decus.de, reimplementing the functionality previously provided by Alpha PALcode inside the kernel, using new executable file formats (Executable and Linkable Format and DWARF),WEB,weblink Porting OpenVMS Applications to Itanium, December 21, 2020, hp-user-society.de, 2005, Gaitan D’Antoni, and adopting IEEE 754 as the default floating point format.WEB,weblink OpenVMS floating-point arithmetic on the Intel Itanium architecture, decus.de, December 21, 2020, 2003, As with the VAX to Alpha port, a binary translator for Alpha to Itanium was made available, allowing user-mode OpenVMS Alpha software to be ported to Itanium in situations where it was not possible to recompile the source code. This translator is known as the Alpha Environment Software Translator (AEST), and it also supported translating VAX executables which had already been translated with VEST.WEB,weblink December 21, 2020, decus.de, 2005, OpenVMS Moving Custom Code, Thomas Siebold, Two pre-production releases, OpenVMS I64 V8.0 and V8.1, were available on June 30, 2003, and on December 18, 2003. These releases were intended for HP organizations and third-party vendors involved with porting software packages to OpenVMS I64. The first production release, V8.2, was released in February 2005. V8.2 was also released for Alpha; subsequent V8.x releases of OpenVMS have maintained feature parity between the Alpha and Itanium architectures.WEB,weblink HP OpenVMS Strategy and Futures, Paul Lacombe, 2005, December 21, 2020, de.openvms.org,

Port to x86-64

When VMS Software Inc. (VSI) announced that they had secured the rights to develop the OpenVMS operating system from HP, they also announced their intention to port OpenVMS to the x86-64 architecture.PRESS RELEASE,weblink VMS Software, Inc. Named Exclusive Developer of Future Versions of OpenVMS Operating System., July 31, 2014,weblink" title="web.archive.org/web/20140810031139weblink">weblink August 10, 2014, The porting effort ran concurrently with the establishment of the company, as well as the development of VSI's own Itanium and Alpha releases of OpenVMS V8.4-x.The x86-64 port is targeted for specific servers from HPE and Dell, as well as certain virtual machine hypervisors.WEB,weblink OpenVMS Rolling Roadmap, December 2019, VSI,weblink June 10, 2020, dead, May 4, 2021, Initial support was targeted for KVM and VirtualBox. Support for VMware was announced in 2020, and Hyper-V is being explored as a future target.WEB,weblink VSI V9.0 Q&A, VSI, April 27, 2024, In 2021, the x86-64 port was demonstrated running on an Intel Atom-based single-board computer.AV MEDIA,weblinkweblink December 11, 2021, live, OpenVMS x64 Atom Project, June 1, 2021, June 2, 2021, VSI, YouTube, {{cbignore}}As with the Alpha and Itanium ports, the x86-64 port made some changes to simplify porting and supporting OpenVMS on the new platform including: replacing the proprietary GEM compiler backend used by the VMS compilers with LLVM,AV MEDIA,weblinkweblink December 11, 2021, live, 2017 LLVM Developers' Meeting: J. Reagan "Porting OpenVMS using LLVM", YouTube, October 31, 2017, {{cbignore}} changing the boot process so that OpenVMS is booted from a memory disk,WEB,weblink State of the Port to x86_64 January 2017., January 6, 2017,weblink" title="web.archive.org/web/20191104221854weblink">weblink November 4, 2019, dead, and simulating the four privilege levels of OpenVMS in software since only two of x86-64's privilege levels are usable by OpenVMS.AV MEDIA,weblinkweblink December 11, 2021, live, Re-architecting SWIS for X86-64, October 8, 2017, Camiel Vanderhoeven, YouTube, October 21, 2021, {{cbignore}}The first boot was announced on May 14, 2019. This involved booting OpenVMS on VirtualBox, and successfully running the DIRECTORY command.WEB,weblink VMS Software Inc. Announces First Boot on x86 Architecture, May 14, 2019, May 4, 2021, VSI, In May 2020, the V9.0 Early Adopter's Kit release was made available to a small number of customers. This consisted of the OpenVMS operating system running in a VirtualBox VM with certain limitations; most significantly, few layered products were available, and code can only be compiled for x86-64 using cross compilers which run on Itanium-based OpenVMS systems.WEB,weblink Rollout of V9.0 and Beyond, May 19, 2020, May 4, 2021, VSI, Following the V9.0 release, VSI released a series of updates on a monthly or bimonthly basis which added additional functionality and hypervisor support. These were designated V9.0-A through V9.0-H.WEB,weblinkweblink April 18, 2021, dead, State of the Port, April 16, 2021, VSI, In June 2021, VSI released the V9.1 Field Test, making it available to VSI's customers and partners.WEB,weblink OpenVMS 9.1, June 30, 2021, June 30, 2021, VSI,weblink June 30, 2021, dead, V9.1 shipped as an ISO image which can be installed onto a variety of hypervisors, and onto HPE ProLiant DL380 servers starting with the V9.1-A release.WEB,weblink VMS Software Releases OpenVMS V9.1-A, September 30, 2021, September 30, 2021, VSI,

Influence

During the 1980s, the MICA operating system for the PRISM architecture was intended to be the eventual successor to VMS. MICA was designed to maintain backwards compatibility with VMS applications while also supporting Ultrix applications on top of the same kernel.WEB,weblink MICA Software Business Plan, Catherine Richardson, Terry Morris, Rockie Morgan, Reid Brown, Donna Meikle, March 1987, January 4, 2021, Bitsavers, MICA was ultimately cancelled along with the rest of the PRISM platform, leading Dave Cutler to leave DEC for Microsoft. At Microsoft, Cutler led the creation of the Windows NT operating system, which was heavily inspired by the architecture of MICA.BOOK, Zachary, G. Pascal, Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft, 2014, Open Road Media, 978-1-4804-9484-8,weblink January 4, 2021, en, As a result, VMS is considered an ancestor of Windows NT, together with RSX-11, VAXELN and MICA, and many similarities exist between VMS and NT.WEB,weblink Windows NT and VMS: The Rest of the Story, Mark Russinovich, October 30, 1998, January 4, 2021, ITPro Today, A now-defunct project named FreeVMS attempted to develop an open-source operating system following VMS conventions.WEB,weblink FreeVMS 0.1.0 Released, Eugenia Loli, November 23, 2004, OSnews, April 2, 2022, WEB,weblink FreeVMS official web page,weblink" title="web.archive.org/web/20180908204358weblink">weblink September 8, 2018, FreeVMS was built on top of the L4 microkernel and supported the x86-64 architecture. Prior work investigating the implementation of VMS using a microkernel-based architecture had previously been undertaken as a prototyping exercise by DEC employees with assistance from Carnegie Mellon University using the Mach 3.0 microkernel ported to VAXstation 3100 hardware, adopting a multiserver architectural model.

Architecture

(File:Openvms-system-architecture.svg|thumb|275px|The architecture of the OpenVMS operating system, demonstrating the layers of the system, and the access modes in which they typically run)The OpenVMS operating system has a layered architecture, consisting of a privileged Executive, an intermediately privileged Command Language Interpreter, and unprivileged utilities and run-time libraries (RTLs).BOOK, VAX/VMS Internals and Data Structures, Version 5.2,weblink 978-1555580599, Ruth E. Goldenberg, Lawrence J. Kenah, Denise E. Dumas, Digital Press, 1991, Unprivileged code typically invokes the functionality of the Executive through system services (equivalent to system calls in other operating systems).OpenVMS' layers and mechanisms are built around certain features of the VAX architecture, including:WEB,weblink Writing VMS Privileged Code Part I: The Fundamentals, Part 1, Hunter Goatley, Edward A. Heinrich, hunter.goatley.com, January 31, 2021, These VAX architecture mechanisms are implemented on Alpha, Itanium and x86-64 by either mapping to corresponding hardware mechanisms on those architectures, or through emulation (via PALcode on Alpha, or in software on Itanium and x86-64).

Executive and Kernel

The OpenVMS Executive comprises the privileged code and data structures which reside in the system space. The Executive is further subdivided between the Kernel, which consists of the code which runs at the kernel access mode, and the less-privileged code outside of the Kernel which runs at the executive access mode.The components of the Executive which run at executive access mode include the Record Management Services, and certain system services such as image activation. The main distinction between the kernel and executive access modes is that most of the operating system's core data structures can be read from executive mode, but require kernel mode to be written to. Code running at executive mode can switch to kernel mode at will, meaning that the barrier between the kernel and executive modes is intended as a safeguard against accidental corruption as opposed to a security mechanism.CONFERENCE,weblink A VMM security kernel for the VAX architecture, Paul A. Karger, Mary Ellen Zurko, Douglas W. Benin, Andrew H. Mason, Clifford E. Kahnh, May 7–9, 1990, Proceedings. 1990 IEEE Computer Society Symposium on Research in Security and Privacy, January 31, 2021, IEEE, 10.1109/RISP.1990.63834, The Kernel comprises the operating system's core data structures (e.g. page tables, the I/O database and scheduling data), and the routines which operate on these structures. The Kernel is typically described as having three major subsystems: I/O, Process and Time Management, Memory Management. In addition, other functionality such as logical name management, synchronization and system service dispatch are implemented inside the Kernel.OpenVMS allows user-mode code with suitable privileges to switch to executive or kernel mode using the $CMEXEC and $CMKRNL system services, respectively.WEB,weblink VSI OpenVMS System Services Reference Manual: A–GETUAI, VSI, June 2020, February 15, 2021, This allows code outside of system space to have direct access to the Executive's routines and system services. In addition to allowing third-party extensions to the operating system, Privileged Images are used by core operating system utilities to manipulate operating system data structures through undocumented interfaces.BOOK, Inside VMS: The System Manager's and System Programmer's Guide to VMS Internals,weblink 0-442-00474-5, Wayne Sewell, 1992, Van Nostrand Reinhold,

File system

The typical user and application interface into the file system is the Record Management Services (RMS), although applications can interface directly with the underlying file system through the QIO system services.WEB,weblink VSI OpenVMS I/O User's Reference Manual, August 2019, January 13, 2021, VSI, The file systems supported by VMS are referred to as the Files-11 On-Disk Structures (ODS), the most significant of which are ODS-2 and ODS-5.WEB,weblinkweblink January 12, 2021, dead, Andy Goldstein on Files-11, the OpenVMS File Systems, July 25, 2019, January 3, 2021, VSI Official Channel, VMS is also capable of accessing files on ISO 9660 CD-ROMs and magnetic tape with ANSI tape labels.WEB,weblink VSI OpenVMS Guide to OpenVMS File Applications, VSI, July 23, 2019, January 13, 2021, Files-11 is limited to 2TiB volumes. DEC attempted to replace it with a log-structured file system file system named Spiralog first released in 1995.WEB,weblink Why was Spiralog retired?, January 10, 2006, January 13, 2021, Hewlett Packard Enterprise Community - Operating System - OpenVMS, However, Spiralog was discontinued due to a variety of problems, including issues with handling full volumes.WEB,weblink Why was Spiralog retired?, January 10, 2006, January 13, 2021, Hewlett Packard Enterprise Community - Operating System - OpenVMS, Instead, there has been discussion of porting the open-source GFS2 file system to OpenVMS.WEB,weblinkweblink December 7, 2020, dead, VSI OpenVMS Software Roadmap 2020, September 23, 2020, September 2020,

Command Language Interpreter

An OpenVMS Command Language Interpreter (CLI) implements a command-line interface for OpenVMS, responsible for executing individual commands and command procedures (equivalent to shell scripts or batch files).WEB,weblink OpenVMS User's Manual, Chapter 14, Advanced Programming with DCL, VSI, April 9, 2021, July 2020, The standard CLI for OpenVMS is the DIGITAL Command Language, although other options are available.Unlike Unix shells, which typically run in their own isolated process and behave like any other user-mode program, OpenVMS CLIs are an optional component of a process, which exist alongside any executable image which that process may run.NEWSGROUP,weblink How dangerous is it to be able to get into DCL supervisor mode?, Simon Clubley, July 3, 2017, comp.os.vms, February 1, 2021, Whereas a Unix shell will typically run executables by creating a separate process using fork-exec, an OpenVMS CLI will typically load the executable image into the same process, transfer control to the image, and ensure that control is transferred back to CLI once the image has exited and that the process is returned to its original state.Because the CLI is loaded into the same address space as user code, and the CLI is responsible for invoking image activation and image rundown, the CLI is mapped into the process address space at supervisor access mode, a higher level of privilege than most user code. This is in order to prevent accidental or malicious manipulation of the CLI's code and data structures by user-mode code.

Features

File:DEC VAXstation 4000 96 OpenVMS 6.1.jpeg|thumb|VAXstation 4000 model 96 running OpenVMS V6.1, DECwindows Motif and the NCSA MosaicNCSA Mosaic

Clustering

OpenVMS supports clustering (first called VAXcluster and later VMScluster), where multiple computers run their own instance of the operating system. Clustered computers (nodes) may be fully independent from each other, or they may share devices like disk drives and printers. Communication across nodes provides a single system image abstraction.WEB,weblink VSI OpenVMS Cluster Systems, August 2019, January 13, 2021, VSI, Nodes may be connected to each other via a proprietary hardware connection called Cluster Interconnect or via a standard Ethernet LAN.OpenVMS supports up to 96 nodes in a single cluster. It also allows mixed-architecture clusters.WEB,weblink VSI Products - Clusters, VSI, May 4, 2021, OpenVMS clusters allow applications to function during planned or unplanned outages.WEB,weblink Building Dependable Systems: The OpenVMS Approach, May 1994, DEC, July 31, 2021, Planned outages include hardware and software upgrades.WEB,weblink" title="web.archive.org/web/20120229042903weblink">weblink February 29, 2012,weblink Cluster Uptime, November 28, 2003, December 20, 2020, live,

Networking

The DECnet protocol suite is tightly integrated into VMS, allowing remote logins, as well as transparent access to files, printers and other resources on VMS systems over a network.WEB,weblink DECnet for OpenVMS Guide to Networking, VSI, January 14, 2021, August 2020, January 21, 2021,weblink dead, VAX/VMS V1.0 featured support for DECnet Phase II,WEB,weblink Software Product Description: DECnet-VAX, Version 1, September 1978, DEC, 2023-05-23, and modern versions of VMS support both the traditional Phase IV DECnet protocol, as well as the OSI-compatible Phase V (also known as DECnet-Plus).WEB,weblink VSI Products - DECnet, VSI, January 14, 2021, Support for TCP/IP is provided by the optional TCP/IP Services for OpenVMS layered product (originally known as the VMS/ULTRIX Connection, then as the ULTRIX Communications Extensions or UCX).WEB,weblink VMS/ULTRIX System Manager's Guide, September 1990, Digital Equipment Corporation, January 21, 2021, WEB,weblink VSI OpenVMS TCP/IP User's Guide, VSI, January 14, 2021, August 2019, TCP/IP Services is based on a port of the BSD network stack to OpenVMS,JOURNAL,weblink Parallelism and Performance in the OpenVMS TCP/IP Kernel, Robert Rappaport, Yanick Pouffary, Steve Lieman, Mary J. Marotta, OpenVMS Technical Journal, 4, 2004, along with support for common protocols such as SSH, DHCP, FTP and SMTP.DEC sold a software package named PATHWORKS (originally known as the Personal Computer Systems Architecture or PCSA) which allowed personal computers running MS-DOS, Microsoft Windows or OS/2, or the Apple Macintosh to serve as a terminal for VMS systems, or to use VMS systems as a file or print server.JOURNAL,weblink An Overview of the PATHWORKS Product Family, Alan Abrahams, David A. Low, Digital Technical Journal, 4, 1, 8–14, 1992, April 27, 2024, PATHWORKS was later renamed to Advanced Server for OpenVMS, and was eventually replaced with a VMS port of Samba at the time of the Itanium port.WEB,weblink Samba and OpenVMS, Andy Goldstein, 2005, January 1, 2021, de.openvms.org, DEC provided the Local Area Transport (LAT) protocol which allowed remote terminals and printers to be attached to a VMS system through a terminal server such as one of the DECserver family.WEB,weblink Local Area Transport Network Concepts, June 1988, DEC, January 14, 2021,

Programming

DEC (and its successor companies) provided a wide variety of programming languages for VMS. Officially supported languages on VMS, either current or historical, include:WEB,weblink VAX/VMS Software Language and Tools Handbook, 1985, December 31, 2020, bitsavers.org, WEB,weblink VSI List of Products, VSI, May 4, 2021, {{Div col|colwidth=9em}} {{Div col end}}Among OpenVMS's notable features is the Common Language Environment, a strictly defined standard that specifies calling conventions for functions and routines, including use of stacks, registers, etc., independent of programming language.WEB,weblink VSI OpenVMS Calling Standard, January 2021, May 4, 2021, Because of this, it is possible to call a routine written in one language (for example, Fortran) from another (for example, COBOL), without needing to know the implementation details of the target language. OpenVMS itself is implemented in a variety of different languages and the common language environment and calling standard supports freely mixing these languages.WEB,weblink VSI OpenVMS Programming Concepts Manual, Volume II, April 2020, May 4, 2021, VSI, DEC created a tool named the Structure Definition Language (SDL), which allowed data type definitions to be generated for different languages from a common definition.WEB,weblink SDL, LANGUAGE, Data Structure/Interface Definition Language, November 1996, January 3, 2021, digiater.nl,

Development tools

File:Vax-vms-grey-wall.jpg|thumb|The "Grey Wall" of VAX/VMS documentation, at (Living Computers: Museum + Labs) ]]DEC provided a collection of software development tools in a layered product named DECset (originally named VAXset). This consisted of the following tools:WEB, DECset,weblink January 2, 2021, VSI, The OpenVMS Debugger supports all DEC compilers and many third-party languages. It allows breakpoints, watchpoints and interactive runtime program debugging using either a command line or graphical user interface.WEB,weblink VSI OpenVMS Debugger Manual, June 2020, May 4, 2021, VSI, A pair of lower-level debuggers, named DELTA and XDELTA, can be used to debug privileged code in additional to normal application code.WEB,weblink VSI OpenVMS Delta/XDelta Debugger Manual, August 2019, December 31, 2020, VSI, In 2019, VSI released an officially supported Integrated Development Environment for VMS based on Visual Studio Code. This allows VMS applications to be developed and debugged remotely from a Microsoft Windows, macOS or Linux workstation.WEB,weblink VMS IDE, January 2, 2021, Visual Studio Marketplace,

Database management

DEC created a number of optional database products for VMS, some of which were marketed as the VAX Information Architecture family.WEB,weblink VAX/VMS Software Information Management Handbook, 1985, January 24, 2021, Digital Equipment Corporation, These products included:
  • Rdb – A relational database system which originally used the proprietary Relational Data Operator (RDO) query interface, but later gained SQL support.WEB,weblink Rdb's First 20 Years: Memories and Highlights, Ian Smith, 2004,weblink" title="web.archive.org/web/20051103112619weblink">weblink November 3, 2005, dead, January 24, 2021,
  • DBMS – A database management system which uses the CODASYL network model and Data Manipulation Language (DML).
  • Digital Standard MUMPS (DSM) – an integrated programming language and key-value database.
  • Common Data Dictionary (CDD) – a central database schema repository, which allowed schemas to be shared between different applications, and data definitions to be generated for different programming languages.
  • DATATRIEVE – a query and reporting tool which could access data from RMS files as well as Rdb and DBMS databases.
  • Application Control Management System (ACMS) – A transaction processing monitor, which allows applications to be created using a high-level Task Description Language (TDL). Individual steps of a transaction can be implemented using DCL commands, or Common Language Environment procedures. User interfaces can be implemented using TDMS, DECforms or Digital's ALL-IN-1 office automation product.WEB,weblink$vaxdocmar002/database/acms_v43/6621/6621pro_contents.html, Compaq ACMS for OpenVMS Getting Started, Compaq, December 1999, January 24, 2021,
  • RALLY, DECadmire – Fourth-generation programming languages (4GLs) for generating database-backed applications.WEB,weblink Building Dependable Systems: The OpenVMS Approach, March 1994, October 17, 2022, Digital Equipment Corporation, DECadmire featured integration with ACMS, and later provided support for generating Visual Basic client-server applications for Windows PCs.WEB,weblink Cover Letter for DECADMIRE V2.1 MUP Kit - DECADMIRE V2.1A, 1995, Digital Equipment Corporation, January 24, 2021, {{Dead link|date=October 2022 |bot=InternetArchiveBot |fix-attempted=yes }}
In 1994, DEC sold Rdb, DBMS and CDD to Oracle, where they remain under active development.WEB,weblink Oracle Rdb Status and Direction, Kevin Duffy, Philippe Vigier, 2004, January 24, 2021, In 1995, DEC sold DSM to InterSystems, who renamed it Open M, and eventually replaced it with their Caché product.WEB,weblink Cover Letter re DSM, January 24, 2021, May 31, 1999, Larry Goelz, John Paladino, Compaq, {{Dead link|date=October 2022 |bot=InternetArchiveBot |fix-attempted=yes }}Examples of third-party database management systems for OpenVMS include MariaDB,WEB,weblink OpenVMS Notes MySQL and MariaDB, Neil Rieck, June 29, 2020, January 24, 2021, January 31, 2021,weblink" title="web.archive.org/web/20210131062246weblink">weblink dead, Mimer SQLWEB,weblink Mimer SQL on OpenVMS Present and Future, Bengt Gunne, 2017, April 27, 2024, (Itanium and x86-64WEB,weblink Mimer SQL is now available for OpenVMS on x86, Mimer Information Technology AB, 2023, ), and System 1032.WEB,weblink Rocket Software System 1032, Rocket Software, January 24, 2021, January 22, 2021,weblink dead,

User interfaces

(File:Openvms-8.4-2L1-dcl.png|thumb|right|OpenVMS Alpha V8.4-2L1, showing the DCL CLI in a terminal session)VMS was originally designed to be used and managed interactively using DEC's text-based video terminals such as the VT100, or hardcopy terminals such as the DECwriter series. Since the introduction of the VAXstation line in 1984, VMS has optionally supported graphical user interfaces for use with workstations or X terminals such as the VT1000 series.

Text-based user interfaces

The DIGITAL Command Language (DCL) has served as the primary command language interpreter (CLI) of OpenVMS since the first release.BOOK, Writing Real Programs in DCL, 2nd, Stephen, Hoffman, Paul, Anagnostopoulos, 1999, Digital Press, 1-55558-191-9, WEB,weblink September 1978, Software Product Description – VAX/VMS Operating System, Version 1.0, Digital Equipment Corporation, October 21, 2021, Other official CLIs available for VMS include the RSX-11 MCR (VAX only), and various Unix shells. DEC provided tools for creating text-based user interface applications – the Form Management System (FMS) and Terminal Data Management System (TDMS), later succeeded by DECforms.WEB,weblink Software Product Description HP DECforms for OpenVMS, Version 4.0, Hewlett Packard Enterprise, January 1, 2021, August 2006, {{Dead link|date=October 2022 |bot=InternetArchiveBot |fix-attempted=yes }}WEB,weblink Software Product Description HP FMS for OpenVMS, Version 2.5, Hewlett Packard Enterprise, January 1, 2021, January 2005, {{Dead link|date=October 2022 |bot=InternetArchiveBot |fix-attempted=yes }}WEB,weblink Compaq TDMS for OpenVMS VAX, Version 1.9B, July 2002, January 1, 2021, Hewlett Packard Enterprise, {{Dead link|date=October 2022 |bot=InternetArchiveBot |fix-attempted=yes }} A lower level interface named Screen Management Services (SMG$), comparable to Unix curses, also exists.WEB,weblink OpenVMS RTL Screen Management (SMG$) Manual, 2001, January 1, 2021, Hewlett Packard Enterprise, December 4, 2020,weblink" title="web.archive.org/web/20201204210834weblink">weblink dead,

Graphical user interfaces{{Anchor|DECwindows}}

(File:VAX-VMS-VWS.png|thumb|right|VWS 4.5 running on top of VAX/VMS V5.5-2)(File:VMS-XUI-Colour.png|thumb|right|DECwindows XUI window manager running on top of VAX/VMS V5.5-2)Over the years, VMS has gone through a number of different GUI toolkits and interfaces:
  • The original graphical user interface for VMS was a proprietary windowing system known as the VMS Workstation Software (VWS), which was first released for the VAXstation I in 1984.JOURNAL,weblink Rick Spitz, Peter George, Stephen Zalewski, The Making of a Micro VAX Workstation, Digital Technical Journal, 1, 2, 1986, October 21, 2021, It exposed an API called the User Interface Services (UIS).WEB,weblink MicroVMS Workstation Graphics Programming Guide, May 1986, October 21, 2021, Digital Equipment Corporation, It ran on a limited selection of VAX hardware.NEWSGROUP,weblink comp.os.vms - Dec VWS Internals, comp.os.vms, January 4, 2007, February 27, 2021, Fred Kleinsorge,
  • In 1989, DEC replaced VWS with a new X11-based windowing system named DECwindows.JOURNAL,weblink An Overview of the DECwindows Architecture, 1990, October 21, 2021, Digital Equipment Corporation, Digital Technical Journal, 2, 3, Scott A. McGregor, It was first included in VAX/VMS V5.1.WEB,weblink (Open)VMS(/ VAX), Version overview, vaxmacro.de, October 21, 2021, October 22, 2020,weblink" title="web.archive.org/web/20201022122158weblink">weblink dead, Early versions of DECwindows featured an interface built on top of a proprietary toolkit named the X User Interface (XUI). A layered product named UISX was provided to allow VWS/UIS applications to run on top of DECwindows.WEB,weblink Migrating VWS/UIS Applications to DECwindows?, HP OpenVMS ask the wizard, November 9, 2004,weblink" title="web.archive.org/web/20180915122243weblink">weblink September 15, 2018, Parts of XUI were subsequently used by the Open Software Foundation as the foundation of the Motif toolkit.JOURNAL,weblink Strategies for Writing Graphical UNIX Applications Productively and Portably, Janet Dobbs, August 1989, 50, 10, 4, AUUG Newsletter, December 29, 2021,
  • In 1991, DEC replaced XUI with the Motif toolkit, creating DECwindows Motif.WEB,weblink Using DECwindows Motif for OpenVMS, October 2019, October 21, 2020, VSI, CONFERENCE, Early Experience With DECwindows/Motif In the TRIUMF Central Control System, S. Kadantsev, M. Mouat, 13th International Conference on Cyclotrons and their Applications, 676–677,weblink August 28, 2019, November 25, 2017,weblink" title="web.archive.org/web/20171125063526weblink">weblink dead, As a result, the Motif Window Manager became the default DECwindows interface in OpenVMS V6.0, although the XUI window manager remained as an option.
  • In 1996, as part of OpenVMS V7.1, DEC released the New Desktop interface for DECwindows Motif, based on the Common Desktop Environment (CDE).WEB,weblink$axpdocdec023/office/dwmot126/vmsdw126/gettingstarted/getting_started.html, Getting Started With the New Desktop, Digital Equipment Corporation, May 1996, October 21, 2021, On Alpha and Itanium systems, it is still possible to select the older MWM-based UI (referred to as the "DECwindows Desktop") at login time. The New Desktop was never ported to the VAX releases of OpenVMS.
Versions of VMS running on DEC Alpha workstations in the 1990s supported OpenGLOpenGL Frequently Asked Questions (FAQ) [1/3]. Faqs.org. Retrieved on July 17, 2013. and Accelerated Graphics Port (AGP) graphics adapters. VMS also provides support for older graphics standards such as GKS and PHIGS.WEB,weblink Software Product Description VSI Graphical Kernel System, 2017, January 2, 2021, VSI, WEB,weblink Software Product Description DEC PHIGS Version 3.1 for OpenVMS VAX, April 1995, January 2, 2021, Hewlett Packard Enterprise, {{Dead link|date=October 2022 |bot=InternetArchiveBot |fix-attempted=yes }} Modern versions of DECwindows are based on X.Org Server.

Security

OpenVMS provides various security features and mechanisms, including security identifiers, resource identifiers, subsystem identifiers, ACLs, intrusion detection and detailed security auditing and alarms.WEB,weblink VSI OpenVMS Guide to System Security, December 2019, April 26, 2021, VSI, Specific versions evaluated at Trusted Computer System Evaluation Criteria Class C2 and, with the SEVMS security enhanced release at Class B1.National Computer Security Center (NCSC) Trusted Product Evaluation List (TPEL) OpenVMS also holds an ITSEC E3 rating (see NCSC and Common Criteria).WEB,weblink HP OpenVMS Guide to System Security, Hewlett Packard, September 2003, October 21, 2021, Passwords are hashed using the Purdy Polynomial.

Vulnerabilities

  • Early versions of VMS included a number of privileged user accounts (including SYSTEM, FIELD, SYSTEST and DECNET) with default passwords which were often left unchanged by system managers.JOURNAL, Green, James L., Sisson, Patricia L., The "Father Christmas" Worm, 12th National Computer Security Conference Proceedings, June 1989,weblink November 23, 2015, green1989, WEB,weblink Security Audit on OpenVMS: An Internal Auditor's Perspective, November 2004, Kevin Rich, SANS Institute, July 21, 2021, A number of computer worms for VMS including the WANK worm and the Father Christmas worm exploited these default passwords to gain access to nodes on DECnet networks.WEB,weblinkweblink December 11, 2021, live, DEFCON 16: Hacking OpenVMS, January 20, 2011, Claes Nyberg, Christer Oberg, James Tusini, YouTube, July 21, 2021, {{cbignore}} This issue was also described by Clifford Stoll in The Cuckoo's Egg as a means by which Markus Hess gained unauthorized access to VAX/VMS systems.BOOK, Stoll, Clifford, The Cuckoo's Egg : tracking a spy through the maze of computer espionage, 1989, Doubleday, New York, 0-385-24946-2, 1st, In V5.0, the default passwords were removed, and it became mandatory to provide passwords for these accounts during system setup.
  • A 33-year-old vulnerability in VMS on VAX and Alpha was discovered in 2017 and assigned the CVE ID {{CVE|2017-17482}}. On the affected platforms, this vulnerability allowed an attacker with access to the DCL command line to carry out a privilege escalation attack. The vulnerability relies on exploiting a buffer overflow bug in the DCL command processing code, the ability for a user to interrupt a running image (program executable) with {{kbd|CTRL/Y}} and return to the DCL prompt, and the fact that DCL retains the privileges of the interrupted image.On the internal workings of the CTRL-Y mechanism, see: OpenVMS AXP Internals and Data Structures, Version 1.5, sections 30.6.5.1 (CTRL/Y Processing) and 30.6.5.4 (CONTINUE Command) at pp. 1074–1076. The buffer overflow bug allowed shellcode to be executed with the privileges of an interrupted image. This could be used in conjunction with an image installed with higher privileges than the attacker's account to bypass system security.WEB, Ghost in the DCL shell: OpenVMS, touted as ultra reliable, had a local root hole for 30 years,weblink February 6, 2018, January 13, 2021, John Leyden, theregister.com,

POSIX compatibility

Various official Unix and POSIX compatibility layers were created for VMS. The first of these was DEC/Shell, which was a layered product consisting of ports of the Bourne shell from Version 7 Unix and several other Unix utilities to VAX/VMS. In 1992, DEC released the POSIX for OpenVMS layered product, which included a shell based on the KornShell.BOOK, Software Product Description - POSIX for OpenVMS 2.0, 1994, Digital Equipment Corporation, POSIX for OpenVMS was later replaced by the open-source GNV (GNU's not VMS) project, which was first included in OpenVMS media in 2002.WEB,weblink June 2002, OpenVMS Alpha Version 7.3-1 New Features and Documentation Overview Begin Index, {{Dead link|date=October 2022 |bot=InternetArchiveBot |fix-attempted=yes }} Amongst other GNU tools, GNV includes a port of the Bash shell to VMS.WEB,weblink VSI Products - GNV, August 19, 2020, VSI, Examples of third-party Unix compatibility layers for VMS include Eunice.WEB,weblinkweblink January 22, 2004, dead, August 10, 1987, Ï•nix: a Unix emulator for VAX/VMS,

Hobbyist programs

In 1997, OpenVMS and a number of layered products were made available free of charge for hobbyist, non-commercial use as part of the OpenVMS Hobbyist Program.WEB,weblink Compaq and DECUS expand Free License OpenVMS Hobbyist Program, Compaq, March 10, 1999, August 1, 2021, Since then, several companies producing OpenVMS software have made their products available under the same terms, such as Process Software.WEB,weblink Hobbyist Program, Process Software, April 24, 2020, Prior to the x86-64 port, the age and cost of hardware capable of running OpenVMS made emulators such as SIMH a common choice for hobbyist installations.WEB,weblink VMS Hardware, Bill Pedersen, John Malmberg, vms-ports, July 30, 2021, In March 2020, HPE announced the end of the OpenVMS Hobbyist Program.WEB,weblink HPE sets end date for hobbyist licenses for OpenVMS, July 4, 2020, July 4, 2020,weblink dead, This was followed by VSI's announcement of the Community License Program (CLP) in April 2020, which was intended as a replacement for the HPE Hobbyist Program.WEB,weblink VMS Software Announces Community License, April 22, 2020, VSI, May 4, 2021, The CLP was launched in July 2020, and provides licenses for VSI OpenVMS releases on Alpha, Integrity and x86-64 systems.WEB,weblink VMS Software Community License Available, July 28, 2020, VSI, May 4, 2021, OpenVMS for VAX is not covered by the CLP, since there are no VSI releases of OpenVMS VAX, and the old versions are still owned by HPE.WEB,weblink VSI Announces Community License Updates, June 11, 2020, VSI, May 4, 2021,

Release history

{{mw-datatable}}{| class="wikitable mw-datatable mw-collapsible" style="text-align:center; margin-left:1em; margin-right:0"|+ Release history of OpenVMS
o group=n|X0.5 was also known as "Base Level 5".}} DECDATE=SEPTEMBER 16, 1997NEWSGROUP=COMP.OS.VMS, March 5, 2022, | rowspan=54 {{dunno}} VAXAUTHOR=STEPHEN HOFFMANACCESS-DATE=JANUARY 3, 2021ARCHIVE-DATE=MAY 18, 2021URL-STATUS=DEAD,
o |V1.0}}| August 1978| First production release
o |V1.01}}group=n|While an exact release date is unknown, the V1.01 change log dates in the release notes for V1.5 suggest it was released some time after November 1978.}}| Bug fixes
o |V1.5}}group=n|For some of the early VAX/VMS releases where an official release date is not known, the date of the Release Notes has been used an approximation.}}DATE=FEBRUARY 1979, AA-D015B-TE,
o |V1.6}}| August 1979DATE=AUGUST 1979, AA-J039A-TE,
o |V2.0}}| April 1980VAX-11#VAX-11/750>VAX-11/750, new utilities including EDT
o |V2.1}}group=nDATE=MAY 1982URL=HTTP://WWW.BITSAVERS.ORG/PDF/DEC/VAX/VMS/3.0/AA-D015D-TE_VAX-VMS_RELEASE_NOTES_V3.0_MAY82.PDF, February 6, 2022, }}| {{dunno}}
o |V2.2}}| April 1981DATE=APRIL 1981ACCESS-DATE=FEBRUARY 6, 2022,
o |V2.3}}DATE=MAY 1981PUBLISHER=DEC, February 6, 2022, PUBLISHER=DEC, February 6, 2022,
o |V2.4}}| {{dunno}}| {{dunno}}
o |V2.5}}| {{dunno}}AUTHOR=BOB BOYDNEWSGROUP=COMP.OS.VMS, February 6, 2022,
o |V3.0}}| April 1982VAX-11#VAX-11/730>VAX-11/730, VAX-11#VAX-11/725, VAX-11#VAX-11/782>VAX-11/782, ASMP
o |V3.1}}| August 1982DATE=AUGUST 1982, AA-N472A-TE,
o |V3.2}}| December 1982DATE=DECEMBER 1982, AA-P763A-TE,
o |V3.3}}| April 1983DATE=APRIL 1983, AA-P764A-TE,
o |V3.4}}| June 1983DATE=JUNE 1983, AA-P765A-TE, VAX-11/785
o |V3.5}}| November 1983DATE=NOVEMBER 1983, AA-P766A-TE,
o |V3.6}}| April 1984DATE=APRIL 1984, AA-V332A-TE,
o |V3.7}}| August 1984DATE=AUGUST 1984, AA-CJ33A-TE,
o |V4.0}}| September 1984VAX 8000>VAX 8600, MicroVMS, VAXclustersvms-source-listings
o |V4.1}}| January 1985| MicroVAX/VAXstation I, IIvms-source-listings
o |V4.2}}| October 1985| Text Processing Utility
o |V4.3}}| December 1985| DELUA Ethernet adapter support
o |V4.3A}}| January 1986| VAX 8200
o |V4.4}}| July 1986| VAX 8800/8700/85xx, Volume Shadowing
o |V4.5}}| November 1986| Support for more memory in MicroVAX II
o |V4.5A}}| December 1986| Ethernet VAXclusters
o |V4.5B}}| March 1987| VAXstation/MicroVAX 2000
o |V4.5C}}| May 1987| MicroVAX 2000 cluster support
o |V4.6}}| August 1987| VAX 8250/8350/8530, RMS Journalling
o |V4.7}}| January 1988| First release installable from CD-ROM
o |V4.7A}}| March 1988| VAXstation 3200/3500, MicroVAX 3500/3600
o |V5.0}}| April 1988VAX 6000, Symmetric multiprocessing>SMP, LMF, Modular Executive
o |V5.0-1}}| August 1988 Bug fixes
o |V5.0-2}} October 1988
o |V5.0-2A}}| MicroVAX 3300/3400
o |V5.1}} February 1989| DECwindows
o |V5.1-B}}| VAXstation 3100 30/40, Desktop-VMS
o |V5.1-1}}| June 1989| VAXstation 3520/3540, MicroVAX 3800/3900
o |V5.2}}| September 1989| Cluster-wide process visibility/management
o |V5.2-1}}| October 1989| VAXstation 3100 38/48
o |V5.3}}| January 1990| Support for third-party SCSI devices
o |V5.3-1}}| April 1990| Support for VAXstation SPX graphics
o |V5.3-2}}| May 1990| Support for new I/O devices
o |V5.4}} October 1990| VAX 65xx, VAX Vector Architecture
o |V5.4-0A}}| VAX 9000, bug fixes for VAX 6000 systems
o |V5.4-1}}| November 1990| New models of VAX 9000, VAXstation, VAXft
o |V5.4-1A}}| January 1991| VAX 6000-400
o |V5.4-2}}| March 1991| VAX 4000 Model 200, new I/O devices
o |V5.4-3}}| October 1991| FDDI adapter support
o |V5.5}} November 1991| Cluster-wide batch queue, new VAX models
o |A5.5}}| Same as V5.5 but without new batch queue
o |V5.5-1}}| July 1992| Bug fixes for batch/print queue
o |V5.5-2HW}}| September 1992| VAX 7000/10000, and other new VAX hardware
o |V5.5-2}}| November 1992 September 1995| Consolidation of previous hardware releases
o |V5.5-2H4}} August 1993| New VAX 4000 models, additional I/O devices
o |V5.5-2HF}}| rowspan=8 {{dunno}}| VAXft 810
o group=n|While the versioning scheme reset to V1.0 for the first AXP (Alpha) releases, these releases were contemporaneous with the V5.x releases and had a similar feature set.}}| November 1992 Alpha| First release for Alpha architecture
o |V1.5}}| May 1993| Cluster and SMP support for Alpha
o |V1.5-1H1}}| October 1993| New DEC 2000, DEC 3000 models
o |V6.0}}| June 1993| VAXTrusted Computer System Evaluation Criteria>TCSEC C2 compliance, ISO 9660, Motif
o |V6.1}}| April 1994| VAX, Alpha| Merger of VAX and Alpha releases, PCSI
o |V6.1-1H1}}| September 1994 Alpha New AlphaStation, AlphaServer models
o |V6.1-1H2}}| November 1994
o |V6.2}}| June 1995 March 1998| VAX, Alpha| Command Recall, DCL$PATH, SCSI clusters
o |V6.2-1H1}}| December 1995 Alpha New AlphaStation, AlphaServer models
o |V6.2-1H2}}| March 1996
o |V6.2-1H3}}| May 1996
o |V7.0}}| January 1996 VAX, AlphaThread (computing)#Kernel threads>Kernel Threads
o |V7.1}}| January 1997 July 2000| Very Large Memory support, DCL PIPE, CDE
o |V7.1-1H1}}| November 1997 Alpha| AlphaServer 800 5/500, 1200
o |V7.1-1H2}}| April 1998| Support for booting from third-party devices
o |V7.1-2}} Compaq| December 1998| Additional I/O device support
o |V7.2}}| February 1999 June 2002| VAX, AlphaDistributed Component Object Model>DCOM
o |V7.2-1}}| July 1999 AlphaAlphaserver#Tsunami Family>Tsunami
o |V7.2-1H1}}| June 2000| AlphaServer GS160, GS320
o |V7.2-2}}| September 2001| December 2002| Minicopy support for Volume Shadowing
o |V7.2-6C1}}| August 2001| rowspan=2 {{dunno}} DII COE conformanceHTTPS://H41379.WWW4.HPE.COM/SOLUTIONS/GOVERNMENT/COE/>TITLE=COMMITMENT TO DII COE INITIATIVE PROVIDES LONGTERM SUPPORT AND APPLICATION PORTABILITY FOR OPENVMS CUSTOMERSHEWLETT PACKARD ENTERPRISE>ACCESS-DATE=2023-09-07,
o |V7.2-6C2}}| July 2002
o |V7.3}} June 2001| December 2012| VAX| Final release for VAX architecture
Asynchronous Transfer Mode>ATM and GBE clusters, Extended File Cache
o |V7.3-1}} HP| August 2002| December 2004 Alpha| Security and performance improvements
o |V7.3-2}}| December 2003| December 2006| AlphaServer GS1280, DS15
o |V8.0}}| June 2003| December 2003 IA64| Evaluation release for Integrity servers
o |V8.1}}| December 2003| February 2005| Second evaluation release for Integrity servers
o |V8.2}}| February 2005 June 2010| Alpha, IA64| Production release for Integrity servers
o |V8.2-1}}| September 2005| IA64| Support for HP Superdome, rx7620, rx8620
o |V8.3}}| August 2006 December 2015| Alpha, IA64| Support for additional Integrity server models
o |V8.3-1H1}}| November 2007| IA64| Support for HP BL860c, dual-core Itanium
o |V8.4}}| June 2010| December 2020| Alpha, IA64HPVM, clusters over TCP/IPHTTP://H71000.WWW7.HP.COM/OPENVMS84_ANNOUNCE.HTMLARCHIVE-URL=HTTPS://WEB.ARCHIVE.ORG/WEB/20100902030522/HTTP://H71000.WWW7.HP.COM/OPENVMS84_ANNOUNCE.HTMLURL-STATUS=DEAD,
o |V8.4-1H1}} VSI| May 2015 December 2022 IA64Poulson (processor)>Poulson processorsHTTPS://WWW.VMSSOFTWARE.COM/NEWS/PR20150601/PR20150601_VSI_8.4-IHI.PDF>TITLE=VMS SOFTWARE, INC. LAUNCHES NEW VERSION OF OPENVMS OPERATING SYSTEM WORLDWIDEACCESS-DATE=JUNE 4, 2015ARCHIVE-URL=HTTPS://WEB.ARCHIVE.ORG/WEB/20150807031302/HTTP://VMSSOFTWARE.COM/NEWS/PR20150601/PR20150601_VSI_8.4-IHI.PDF, dead,
o |V8.4-2}}| March 2016| Support for HPE BL890c systems, UEFI 2.3
co |V8.4-2L1}}| September 2016| December 2024 OpenSSL updated to 1.0.2HTTPS://VMSSOFTWARE.COM/ABOUT/NEWS/2016-09-23-VMS-SOFTWARE-INC-LAUNCHES-NEW-VERSION-8-4-2L1-OF-OPENVMS-OPERATING-SYSTEM-WORLDWIDE/>TITLE=VMS SOFTWARE, INC. LAUNCHES NEW VERSION 8.4-2L1 OF OPENVMS OPERATING SYSTEM WORLDWIDEWEBSITE=VSI, May 4, 2021,
DATE=JANUARY 27, 2017ACCESS-DATE=MAY 4, 2021, | rowspan=2 {{TBA}} Alpha
co |V8.4-2L2}}| July 2017Final release for Alpha architectureHTTPS://VMSSOFTWARE.COM/PRODUCTS/ROADMAP/ARCHIVE-DATE=SEPTEMBER 27, 2020ACCESS-DATE=SEPTEMBER 23, 2020WEBSITE=VSI,
co |V8.4-2L3}}| April 2021| December 2028| IA64| Final release for Integrity servers
o |V9.0}}| May 2020| June 2021 x86-64DATE=APRIL 24, 2020ACCESS-DATE=MAY 4, 2021,
o |V9.1}}| June 2021| September 2021| x86-64 Field Test
o |V9.1-A}}| September 2021| April 2022| HPE Proliant DL380, DECnet-Plus
o |V9.2}}| July 2022| June 2023DATE=JULY 14, 2022WEBSITE=VSI,
co |V9.2-1}}| June 2023| December 2026DATE=2023-06-15WEBSITE=VSI,
c |V9.2-2}}| January 2024| {{TBA}}| Bug fixes
{{Version show=111101}}
{{reflist|group=n}}

See also

References

{{Reflist|30em}}

Further reading

  • Getting Started with OpenVMS, Michael D. Duffy, {{ISBN|1-55558-279-6}}
  • Introduction to OpenVMS, 5th Edition, Lesley Ogilvie Rice, {{ISBN|1-55558-194-3}}
  • BOOK, OpenVMS AXP Internals and Data Structures: Version 1.5,weblink 978-1555581206, Ruth Goldenberg, Saro Saravanan, 1994, Digital Press,
  • OpenVMS Alpha Internals and Data Structures: Memory Management, Ruth Goldenberg, {{ISBN|1-55558-159-5}}
  • OpenVMS Alpha Internals and Data Structures : Scheduling and Process Control : Version 7.0, Ruth Goldenberg, Saro Saravanan, Denise Dumas, {{ISBN|1-55558-156-0}}
  • VAX/VMS Internals and Data Structures: Version 5.2 ("IDSM"), Ruth Goldenberg, Saro Saravanan, Denise Dumas, {{ISBN|1-55558-059-9}}
  • Writing Real Programs in DCL, second edition, Stephen Hoffman, Paul Anagnostopoulos, {{ISBN|1-55558-191-9}}
  • Writing OpenVMS Alpha Device Drivers in C, Margie Sherlock, Leonard Szubowicz, {{ISBN|1-55558-133-1}}
  • OpenVMS Performance Management, Joginder Sethi, {{ISBN|1-55558-126-9}}
  • Getting Started with OpenVMS System Management, 2nd Edition, David Donald Miller, Stephen Hoffman, Lawrence Baldwin, {{ISBN|1-55558-243-5}}
  • The OpenVMS User's Guide, Second Edition, Patrick Holmay, {{ISBN|1-55558-203-6}}
  • Using DECwindows Motif for OpenVMS, Margie Sherlock, {{ISBN|1-55558-114-5}}
  • BOOK, Inside VMS: The System Manager's and System Programmer's Guide to VMS Internals,weblink 0-442-00474-5, Wayne Sewell, 1992, Van Nostrand Reinhold,
  • The hitchhiker's guide to VMS : an unsupported-undocumented-can-go-away-at-any-time feature of VMS, Bruce Ellis, {{ISBN|1-878956-00-0}}
  • BOOK,weblink The Minimum You Need to Know to Be an OpenVMS Application Developer, Roland Hughes, December 2006, Logikal Solutions, 978-0-9770866-0-3,

External links

{{Commons category}} {{Digital Equipment Corporation}}{{Time-sharing operating systems}}{{Operating System}}

- content above as imported from Wikipedia
- "OpenVMS" does not exist on GetWiki (yet)
- time: 7:25am EDT - Sat, May 18 2024
[ this remote article is provided by Wikipedia ]
LATEST EDITS [ see all ]
GETWIKI 23 MAY 2022
GETWIKI 09 JUL 2019
Eastern Philosophy
History of Philosophy
GETWIKI 09 MAY 2016
GETWIKI 18 OCT 2015
M.R.M. Parrott
Biographies
GETWIKI 20 AUG 2014
CONNECT