OpenVMS

Last updated

OpenVMS
Vsi-openvms-logo.svg
DECwindows-openvms-v7.3-1.png
OpenVMS V7.3-1 running the CDE-based DECwindows "New Desktop" GUI
Developer VMS Software Inc (VSI) [1] (previously Digital Equipment Corporation, Compaq, Hewlett-Packard)
Written in Primarily C, BLISS, VAX MACRO, DCL. [2] Other languages also used. [3]
Working stateCurrent
Source model Closed-source with open-source components. Formerly source available [4] [5]
Initial releaseAnnounced: October 25, 1977;45 years ago (1977-10-25)
V1.0 / August 1978;44 years ago (1978-08)
Latest release V9.2 / July 14, 2022;4 months ago (2022-07-14) [6]
Marketing target Servers (historically Minicomputers, Workstations)
Available in English, Japanese. [7] Historical support for Chinese (both Traditional and Simplified characters), Korean, Thai. [8]
Update methodConcurrent upgrades,
rolling upgrades
Package manager PCSI and VMSINSTAL
Platforms VAX, Alpha, Itanium, x86-64
Kernel type Monolithic kernel with loadable modules
Influenced VAXELN, MICA, Windows NT
Influenced by RSX-11M
Default
user interface
DCL CLI and DECwindows GUI
License Proprietary
Official website www.vmssoftware.com

OpenVMS, often referred to as just VMS, [9] 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. [10] Customers using OpenVMS include banks and financial services, hospitals and healthcare, telecommunications operators, network information services, and industrial manufacturers. [11] [12] During the 1990s and 2000s, there were approximately half a million VMS systems in operation worldwide. [13] [14] [15]

Contents

It was first announced by Digital Equipment Corporation (DEC) as VAX/VMS (Virtual Address eXtension/Virtual Memory System [16] ) alongside the VAX-11/780 minicomputer in 1977. [17] [18] [19] OpenVMS has subsequently been ported to run on DEC Alpha systems, the Itanium-based HPE Integrity Servers, [20] and select x86-64 hardware and hypervisors. [21] Since 2014, OpenVMS is developed and supported by VMS Software Inc. (VSI). [22] [23] OpenVMS offers high availability through clustering — the ability to distribute the system over multiple physical machines. [24] This allows clustered applications and data to remain continuously available while operating system software and hardware maintenance and upgrades are performed, [25] or if part of the cluster is destroyed. [26] VMS cluster uptimes of 17 years have been reported. [27]

History

Origin and name changes

Stylized "VAX/VMS" used by Digital VAX VMS logo.svg
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. [28] 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. [29] VMS was mostly written in VAX MACRO with some components written in BLISS. [9]

One of the original goals for VMS was backwards compatibility with DEC's existing RSX-11M operating system. [9] Prior to the V3.0 release, VAX/VMS included an 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. [30] The RSX AME played an important role on early versions of VAX/VMS, which used re-used certain RSX-11M user mode utilities before native VAX versions had been developed. [9] By the V3.0 release, all compatibility mode utilities were replaced with native implementations. [31] In VAX/VMS V4.0, RSX AME was removed from the base system, and replaced with an optional layered product named VAX-11 RSX. [32]

"Albert the Cheshire Cat" mascot for VAX/VMS, used by the DECUS VAX SIG Vms-albert-cheshire-cat.png
"Albert the Cheshire Cat" mascot for VAX/VMS, used by the DECUS VAX SIG

A number of distributions of VAX/VMS were created:

With the V5.0 release in April 1988, DEC began to refer to VAX/VMS as simply VMS in its documentation. [47] In July 1992, [48] DEC renamed VAX/VMS to OpenVMS as an indication for its support of open systems industry standards such as POSIX and Unix compatibility, [49] and to drop the VAX connection since a migration to a different architecture was underway. The OpenVMS name was first used with the OpenVMS AXP V1.0 release in November 1992. DEC began using the OpenVMS VAX name with the V6.0 release in June 1993. [50]

Port to Alpha

"Vernon the Shark" logo for OpenVMS Dec-vms-vernon.png
"Vernon the Shark" logo for OpenVMS

During the 1980s, DEC planned to replace the VAX platform and the VMS operating system with the PRISM architecture and the MICA operating system. [52] 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. [53] 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. [54] This led to the creation of the Alpha architecture. [55] 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. [54] [56]

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. [57] Furthermore, a significant amount of the VMS kernel, layered products, and customer-developed applications were implemented in VAX MACRO assembly code. [9] 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, [58] 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 for Alpha. [4] The Alpha code library was based on a snapshot of the VAX/VMS code base circa V5.4-2. [59] 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. [59] The decision to use the 1.x version numbering stream for the pre-production quality releases of OpenVMS AXP caused confusion for some customers, and was not repeated in the subsequent ports of OpenVMS to new platforms. [57]

When VMS was ported to Alpha, it was initially left as a 32-bit only operating system. [58] 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. [60] 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. [61] 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. [62]

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. [63] [64]

Port to Intel Itanium

"Swoosh" logo used by HP for OpenVMS 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. [65] 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. [66] The porting began in late 2001, and the first boot on took place on January 31, 2003. [67] The first boot consisted of booting a minimal system configuration on a HP i2000 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. [10] 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. [68]

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. [57] 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, [69] reimplementing the functionality previously provided by Alpha PALcode inside the kernel, [70] using new executable file formats (Executable and Linking Format and DWARF), [71] and adopting IEEE 754 as the default floating point format. [72]

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 translated with VEST. [73]

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. [74]

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. [75] 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. [76] Initial support was targeted for KVM and VirtualBox. Support for VMware was announced in 2020, and Hyper-V has been described as a future target. [77] In 2021, the x86-64 port was demonstrated running on an Intel Atom-based single-board computer. [78]

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, [79] changing the boot process so that OpenVMS is booted from a memory disk, [80] and simulating the four privilege levels of OpenVMS in software since only two of x86-64's privilege levels are usable by OpenVMS. [70]

The first boot was announced on May 14, 2019. This involved booting OpenVMS on VirtualBox, and successfully running the DIRECTORY command. [81] 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. [21] 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. [82] In June 2021, VSI released the V9.1 Field Test, making it available to VSI's customers and partners. [83] 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. [84]

OpenVMS 9.2 for x86-64 reached General Availability on July 14, 2022. [6]

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. [85] 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. [86] 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. [87]

A now-defunct project named FreeVMS attempted to develop an open source operating system following VMS conventions. [88] [89] 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. [90]

Architecture

The architecture of the OpenVMS operating system, demonstrating the layers of the system, and the access modes in which they typically run Openvms-system-architecture.svg
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). [91] 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: [91] [92]

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). [70]

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. [91]

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. [92] 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. [93]

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. [91] [92] 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. [94] 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. [95]

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. [96] 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. [97] VMS is also capable of accessing files on ISO 9660 CD-ROMs and magnetic tape with ANSI tape labels. [98]

Files-11 is limited to 2TiB volumes. [97] DEC attempted to replace it with a log-structured file system file system named Spiralog first released in 1995. [99] However, Spiralog was discontinued due to a variety of problems, including issues with handling full volumes. [100] Instead, there has been discussion of porting the open source GFS2 file system to OpenVMS. [101]

Command Language Interpreter

An OpenVMS Command Language Interpreter (CLI) implements a command line interface for OpenVMS; responsible for executing individual commands, as well as command procedures (equivalent to shell scripts or batch files). [102] The standard CLI for OpenVMS is the DIGITAL Command Language, although other options are available as well.

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. [103] 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. [91]

Due to the fact that the CLI is loaded into the same address space as user code, and that 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. [91] [103]

Features

VAXstation 4000 model 96 running OpenVMS V6.1, DECwindows Motif and the NCSA Mosaic browser DEC VAXstation 4000 96 OpenVMS 6.1.jpeg
VAXstation 4000 model 96 running OpenVMS V6.1, DECwindows Motif and the NCSA Mosaic browser

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. [104] 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. [24] (VAX, Alpha, and Itanium computers each have a different architecture.) OpenVMS clusters allow applications to function during planned or unplanned outages. [105] Planned outages include hardware and software upgrades. [106]

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. [107] 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). [108] 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). [109] [110] TCP/IP Services is based on a port of the BSD network stack to OpenVMS, [111] 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. [112] 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. [113]

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. [114]

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: [115] [116]

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. [117] 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. [118] 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. [119]

Development Tools

The "Grey Wall" of VAX/VMS documentation, at Living Computers: Museum + Labs Vax-vms-grey-wall.jpg
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). [115] This consisted of the following tools: [120]

The OpenVMS Debugger supports all DEC compilers and many third party languages. It allows breakpoints, watchpoints and interactive runtime program debugging either using a command line or graphical user interface. [122] A pair of lower-level debuggers, named DELTA and XDELTA, can be used to debug privileged code in additional to normal application code. [123]

In 2019, VSI released an officially-supported Integrated Development Environment for VMS based on Visual Studio Code. [76] This allows VMS applications to be developed and debugged remotely from a Microsoft Windows, macOS or Linux workstation. [124]

Database management

DEC created a number of optional database products for VMS, some of which were marketed as the VAX Information Architecture family. [125] These products included:

In 1994, DEC sold Rdb, DBMS and CDD to Oracle, where they remain under active development. [130] In 1995, DEC sold DSM to InterSystems, who renamed it Open M, and eventually replaced it with their Caché product. [131]

Examples of third-party database management systems for OpenVMS include MariaDB, [132] Mimer SQL [133] and System 1032. [134]

User interfaces

OpenVMS Alpha V8.4-2L1, showing the DCL CLI in a terminal session Openvms-8.4-2L1-dcl.png
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. [135] [30] [10] Other official CLIs available for VMS include the RSX-11 MCR (VAX only), and various Unix shells. [115] 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. [136] [137] [138] A lower level interface named Screen Management Services (SMG$), comparable to Unix curses, also exists. [139]

Graphical user interfaces

VWS 4.5 running on top of VAX/VMS V5.5-2 VAX-VMS-VWS.png
VWS 4.5 running on top of VAX/VMS V5.5-2
DECwindows XUI window manager running on top of VAX/VMS V5.5-2 VMS-XUI-Colour.png
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. [140] It exposed an API called the User Interface Services (UIS). [141] It ran on a limited selection of VAX hardware. [142]
  • In 1989, DEC replaced VWS with a new X11-based windowing system named DECwindows. [143] It was first included in VAX/VMS V5.1. [144] 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. [145] Parts of XUI were subsequently used by the Open Software Foundation as the foundation of the Motif toolkit. [146]
  • In 1991, DEC replaced XUI with the Motif toolkit, creating DECwindows Motif. [147] [148] As a result, the Motif Window Manager became the default DECwindows interface in OpenVMS V6.0, [144] although the XUI window manager remained as an option.
  • In 1996, as part of OpenVMS V7.1, [144] DEC released the New Desktop interface for DECwindows Motif, based on the Common Desktop Environment (CDE). [149] 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 OpenGL [150] and Accelerated Graphics Port (AGP) graphics adapters. VMS also provides support for older graphics standards such as GKS and PHIGS. [151] [152] Modern versions of DECwindows are based on X.Org Server. [10]

Security

OpenVMS provides various security features and mechanisms, including security identifiers, resource identifiers, subsystem identifiers, ACLs, intrusion detection and detailed security auditing and alarms. [153] Specific versions evaluated at Trusted Computer System Evaluation Criteria Class C2 and, with the SEVMS security enhanced release at Class B1. [154] OpenVMS also holds an ITSEC E3 rating (see NCSC and Common Criteria). [155] 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. [156] [157] 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. [158] 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. [159] In V5.0, the default passwords were removed, and it became mandatory to provide passwords for these accounts during system setup. [38]
  • 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 CTRL/Y and return to the DCL prompt, and the fact that DCL retains the privileges of the interrupted image. [160] 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. [161]

POSIX compatibility

Various official Unix and POSIX compatibility layers were created for VMS. The first of which was DEC/Shell - which was a layered product consisting of ports of the Version 7 Unix Bourne shell and several other Unix utilities to VAX/VMS. [115] In 1992, DEC released the POSIX for OpenVMS layered product, which included a shell based on the Korn Shell. [162] 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. [163] Amongst other GNU tools, GNV includes a port of the Bash shell to VMS. [164] Examples of third party Unix compatibility layers for VMS include Eunice. [165]

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. [166] Since then, several companies producing OpenVMS software have made their products available under the same terms, such as Process Software. [167] 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. [168]

In March 2020, HPE announced the end of the OpenVMS Hobbyist Program. [169] 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. [170] The CLP was launched in July 2020, and provides licenses for VSI OpenVMS releases on Alpha and Integrity systems. OpenVMS x86-64 licenses will be made available when a stable version is released for this architecture. [171] 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. [172]

Release history

Release history of OpenVMS
VersionVendorRelease date
[173] [9] [174]
End of support
[175] [176] [177]
PlatformSignificant changes, new hardware support
[178] [144]
Old version, no longer maintained: X0.5 [n 1] DECApril 1978 [179] ?VAXFirst version shipped to customers [29]
Old version, no longer maintained: V1.0August 1978First production release
Old version, no longer maintained: V1.01? [n 2] Bug fixes [180]
Old version, no longer maintained: V1.5February 1979 [n 3] Support for native COBOL, BLISS compilers [180]
Old version, no longer maintained: V1.6August 1979RMS-11 updates [181]
Old version, no longer maintained: V2.0April 1980 VAX-11/750, new utilities including EDT
Old version, no longer maintained: V2.1? [n 4] ?
Old version, no longer maintained: V2.2April 1981Process limit increased to 8,192 [183]
Old version, no longer maintained: V2.3May 1981 [184] Security enhancements [185]
Old version, no longer maintained: V2.4??
Old version, no longer maintained: V2.5?BACKUP utility [186]
Old version, no longer maintained: V3.0April 1982 VAX-11/730, VAX-11/725, VAX-11/782, ASMP
Old version, no longer maintained: V3.1August 1982PL/I runtime bundled with base OS [187]
Old version, no longer maintained: V3.2December 1982Support for RA60, RA80, RA81 disks [188]
Old version, no longer maintained: V3.3April 1983HSC50 disk controller, BACKUP changes [189]
Old version, no longer maintained: V3.4June 1983Ethernet support for DECnet, [190] VAX-11/785
Old version, no longer maintained: V3.5November 1983Support for new I/O devices [191]
Old version, no longer maintained: V3.6April 1984Bug fixes [192]
Old version, no longer maintained: V3.7August 1984Support for new I/O devices [193]
Old version, no longer maintained: V4.0September 1984 VAX 8600, MicroVMS, VAXclusters [194]
Old version, no longer maintained: V4.1January 1985MicroVAX/VAXstation I, II [195]
Old version, no longer maintained: V4.2October 1985 Text Processing Utility
Old version, no longer maintained: V4.3December 1985DELUA ethernet adapter support
Old version, no longer maintained: V4.3AJanuary 1986VAX 8200
Old version, no longer maintained: V4.4July 1986VAX 8800/8700/85xx, Volume Shadowing
Old version, no longer maintained: V4.5November 1986Support for more memory in MicroVAX II
Old version, no longer maintained: V4.5ADecember 1986Ethernet VAXclusters
Old version, no longer maintained: V4.5BMarch 1987VAXstation/MicroVAX 2000
Old version, no longer maintained: V4.5CMay 1987MicroVAX 2000 cluster support
Old version, no longer maintained: V4.6August 1987VAX 8250/8350/8530, RMS Journalling
Old version, no longer maintained: V4.7January 1988First release installable from CD-ROM
Old version, no longer maintained: V4.7AMarch 1988VAXstation 3200/3500, MicroVAX 3500/3600
Old version, no longer maintained: V5.0April 1988 VAX 6000, SMP, LMF, Modular Executive
Old version, no longer maintained: V5.0-1August 1988Bug fixes
Old version, no longer maintained: V5.0-2October 1988
Old version, no longer maintained: V5.0-2AMicroVAX 3300/3400
Old version, no longer maintained: V5.1February 1989DECwindows
Old version, no longer maintained: V5.1-BVAXstation 3100 30/40, Desktop-VMS
Old version, no longer maintained: V5.1-1June 1989VAXstation 3520/3540, MicroVAX 3800/3900
Old version, no longer maintained: V5.2September 1989Cluster-wide process visibility/management
Old version, no longer maintained: V5.2-1October 1989VAXstation 3100 38/48
Old version, no longer maintained: V5.3January 1990Support for third-party SCSI devices
Old version, no longer maintained: V5.3-1April 1990Support for VAXstation SPX graphics
Old version, no longer maintained: V5.3-2May 1990Support for new I/O devices
Old version, no longer maintained: V5.4October 1990VAX 65xx, VAX Vector Architecture
Old version, no longer maintained: V5.4-0A VAX 9000, bug fixes for VAX 6000 systems
Old version, no longer maintained: V5.4-1November 1990New models of VAX 9000, VAXstation, VAXft
Old version, no longer maintained: V5.4-1AJanuary 1991VAX 6000-400
Old version, no longer maintained: V5.4-2March 1991VAX 4000 Model 200, new I/O devices
Old version, no longer maintained: V5.4-3October 1991 FDDI adapter support
Old version, no longer maintained: V5.5November 1991Cluster-wide batch queue, new VAX models
Old version, no longer maintained: A5.5Same as V5.5 but without new batch queue
Old version, no longer maintained: V5.5-1July 1992Bug fixes for batch/print queue
Old version, no longer maintained: V5.5-2HWSeptember 1992 VAX 7000/10000, and other new VAX hardware
Old version, no longer maintained: V5.5-2November 1992September 1995Consolidation of previous hardware releases
Old version, no longer maintained: V5.5-2H4August 1993New VAX 4000 models, additional I/O devices
Old version, no longer maintained: V5.5-2HF? VAXft 810
Old version, no longer maintained: V1.0 [n 5] November 1992AlphaFirst release for Alpha architecture
Old version, no longer maintained: V1.5May 1993Cluster and SMP support for Alpha
Old version, no longer maintained: V1.5-1H1October 1993New DEC 2000, DEC 3000 models
Old version, no longer maintained: V6.0June 1993VAX TCSEC C2 compliance, ISO 9660, Motif
Old version, no longer maintained: V6.1April 1994VAX, AlphaMerger of VAX and Alpha releases, PCSI
Old version, no longer maintained: V6.1-1H1September 1994AlphaNew AlphaStation, AlphaServer models
Old version, no longer maintained: V6.1-1H2November 1994
Old version, no longer maintained: V6.2June 1995March 1998VAX, AlphaCommand Recall, DCL$PATH, SCSI clusters
Old version, no longer maintained: V6.2-1H1December 1995AlphaNew AlphaStation, AlphaServer models
Old version, no longer maintained: V6.2-1H2March 1996
Old version, no longer maintained: V6.2-1H3May 1996
Old version, no longer maintained: V7.0January 1996VAX, Alpha64-bit addressing, Fast Path I/O, Kernel Threads
Old version, no longer maintained: V7.1January 1997July 2000Very Large Memory support, DCL PIPE, CDE
Old version, no longer maintained: V7.1-1H1November 1997AlphaAlphaServer 800 5/500, 1200
Old version, no longer maintained: V7.1-1H2April 1998Support for booting from third party devices
Old version, no longer maintained: V7.1-2CompaqDecember 1998Additional I/O device support
Old version, no longer maintained: V7.2February 1999June 2002VAX, AlphaOpenVMS Galaxy, ODS-5, DCOM
Old version, no longer maintained: V7.2-1July 1999AlphaAlphaServer GS140, GS60, Tsunami
Old version, no longer maintained: V7.2-1H1June 2000AlphaServer GS160, GS320
Old version, no longer maintained: V7.2-2September 2001December 2002Minicopy support for Volume Shadowing
Old version, no longer maintained: V7.3June 2001December 2012VAXFinal release for VAX architecture
June 2004Alpha ATM and GBE clusters, Extended File Cache
Old version, no longer maintained: V7.3-1HPAugust 2002December 2004AlphaSecurity and performance improvements
Old version, no longer maintained: V7.3-2December 2003December 2006AlphaServer GS1280, DS15
Old version, no longer maintained: V8.0June 2003December 2003IA64Evaluation release for Integrity servers
Old version, no longer maintained: V8.1December 2003February 2005Second evaluation release for Integrity servers
Old version, no longer maintained: V8.2February 2005June 2010Alpha, IA64Production release for Integrity servers
Old version, no longer maintained: V8.2-1September 2005IA64Support for HP Superdome, rx7620, rx8620
Old version, no longer maintained: V8.3August 2006December 2015Alpha, IA64Support for additional Integrity server models
Old version, no longer maintained: V8.3-1H1November 2007IA64Support for HP BL860c, dual-core Itanium
Old version, no longer maintained: V8.4June 2010December 2020Alpha, IA64Support for HPVM, clusters over TCP/IP [196]
Older version, yet still maintained: V8.4-1H1VSIMay 2015December 2022IA64Support for Poulson processors [197]
Older version, yet still maintained: V8.4-2March 2016Support for HPE BL890c systems, UEFI 2.3
Older version, yet still maintained: V8.4-2L1September 2016December 2024OpenSSL updated to 1.0.2 [198]
January 2017 [199] TBAAlpha
Older version, yet still maintained: V8.4-2L2July 2017Final release for Alpha architecture [200]
Older version, yet still maintained: V8.4-2L3April 2021December 2028IA64Final release for Integrity servers [200]
Old version, no longer maintained: V9.0May 2020June 2021x86-64x86-64 Early Adopter's Kit [201]
Old version, no longer maintained: V9.1June 2021September 2021x86-64 Field Test [83]
Old version, no longer maintained: V9.1-ASeptember 2021April 2022HPE Proliant DL380, DECnet-Plus [84]
Current stable version:V9.2July 2022 [202] December 2028x86-64 Limited Production Release [176]
Future release: V9.2-1December 2022December 2029x86-64 Production Release [176]
Future release: V9.2-22023TBAImproved cluster security [176]
Legend:
Old version
Older version, still maintained
Latest version
Latest preview version
Future release
  1. X0.5 was also known as "Base Level 5". [179]
  2. 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. [180]
  3. 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.
  4. The existence of releases V2.0 through V2.5 are documented in the V3.0 release notes. [182]
  5. 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.

See also

Related Research Articles

<span class="mw-page-title-main">Digital Equipment Corporation</span> U.S. computer manufacturer 1957–1998

Digital Equipment Corporation, using the trademark Digital, was a major American company in the computer industry from the 1960s to the 1990s. The company was co-founded by Ken Olsen and Harlan Anderson in 1957. Olsen was president until forced to resign in 1992, after the company had gone into precipitous decline.

<span class="mw-page-title-main">DEC Alpha</span> 64-bit RISC instruction set architecture

Alpha is a 64-bit reduced instruction set computer (RISC) instruction set architecture (ISA) developed by Digital Equipment Corporation (DEC). Alpha was designed to replace 32-bit VAX complex instruction set computers (CISC) and to be a highly competitive RISC processor for Unix workstations and similar markets.

<span class="mw-page-title-main">Itanium</span> Family of 64-bit Intel microprocessors

Itanium is a discontinued family of 64-bit Intel microprocessors that implement the Intel Itanium architecture. Launched in June 2001, Intel marketed the processors for enterprise servers and high-performance computing systems. The Itanium architecture originated at Hewlett-Packard (HP), and was later jointly developed by HP and Intel.

<span class="mw-page-title-main">Minicomputer</span> Mid-1960s–late-1980s class of smaller computers

A minicomputer, or colloquially mini, is a class of smaller general purpose computers that developed in the mid-1960s and sold at a much lower price than mainframe and mid-size computers from IBM and its direct competitors. In a 1970 survey, The New York Times suggested a consensus definition of a minicomputer as a machine costing less than US$25,000, with an input-output device such as a teleprinter and at least four thousand words of memory, that is capable of running programs in a higher level language, such as Fortran or BASIC.

<span class="mw-page-title-main">VAX</span> Line of computers sold by Digital Equipment Corporation

VAX is a series of computers featuring a 32-bit instruction set architecture (ISA) and virtual memory that was developed and sold by Digital Equipment Corporation (DEC) in the late 20th century. The VAX-11/780, introduced October 25, 1977, was the first of a range of popular and influential computers implementing the VAX ISA. The VAX family was a huge success for DEC – over 100 models were introduced over the lifetime of the design, with the last members arriving in the early 1990s. The VAX was succeeded by the DEC Alpha, which included several features from VAX machines to make porting from the VAX easier.

<span class="mw-page-title-main">HP-UX</span> Operating system

HP-UX is Hewlett Packard Enterprise's proprietary implementation of the Unix operating system, based on Unix System V and first released in 1984. Current versions support HPE Integrity Servers, based on Intel's Itanium architecture.

<span class="mw-page-title-main">Tru64 UNIX</span> Computer operating system

Tru64 UNIX is a discontinued 64-bit UNIX operating system for the Alpha instruction set architecture (ISA), currently owned by Hewlett-Packard (HP). Previously, Tru64 UNIX was a product of Compaq, and before that, Digital Equipment Corporation (DEC), where it was known as Digital UNIX.

DECnet is a suite of network protocols created by Digital Equipment Corporation. Originally released in 1975 in order to connect two PDP-11 minicomputers, it evolved into one of the first peer-to-peer network architectures, thus transforming DEC into a networking powerhouse in the 1980s. Initially built with three layers, it later (1982) evolved into a seven-layer OSI-compliant networking protocol.

<span class="mw-page-title-main">Ultrix</span> Series of discontinued Unix operating systems by DEC

Ultrix is the brand name of Digital Equipment Corporation's (DEC) discontinued native Unix operating systems for the PDP-11, VAX, MicroVAX and DECstations.

<span class="mw-page-title-main">DIGITAL Command Language</span>

DIGITAL Command Language (DCL) is the standard command language adopted by many of the operating systems created by Digital Equipment Corporation. DCL had its roots in IAS, TOPS-20, and RT-11 and was implemented as a standard across most of Digital's operating systems, notably RSX-11 and RSTS/E, but took its most powerful form in VAX/VMS. DCL continues to be developed by VSI as part of OpenVMS.

Oracle Rdb is a relational database management system for the OpenVMS operating system. It was originally released by Digital Equipment Corporation (DEC) in 1984 as VAX Rdb/VMS.

VSI BASIC for OpenVMS is the latest name for a dialect of the BASIC programming language created by Digital Equipment Corporation (DEC) and now owned by VMS Software Incorporated (VSI). It was originally developed as BASIC-PLUS in the 1970s for the RSTS-11 operating system on the PDP-11 minicomputer. It was later ported to OpenVMS, first on VAX, then Alpha, and most recently Integrity.

VAXELN is a discontinued real-time operating system for the VAX family of computers produced by the Digital Equipment Corporation (DEC) of Maynard, Massachusetts.

VAX MACRO is the computer assembly language implementing the VAX instruction set architecture for the OpenVMS operating system, originally released by Digital Equipment Corporation (DEC) in 1977.

Windows NT is a proprietary graphical operating system produced by Microsoft, the first version of which was released on July 27, 1993. It is a processor-independent, multiprocessing and multi-user operating system.

A VMScluster, originally known as a VAXcluster, is a computer cluster involving a group of computers running the OpenVMS operating system. Whereas tightly coupled multiprocessor systems run a single copy of the operating system, a VMScluster is loosely coupled: each machine runs its own copy of OpenVMS, but the disk storage, lock manager, and security domain are all cluster-wide, providing a single system image abstraction. Machines can join or leave a VMScluster without affecting the rest of the cluster. For enhanced availability, VMSclusters support the use of dual-ported disks connected to two machines or storage controllers simultaneously.

Charon is the brand name of a group of software products able to emulate several CPU architectures. The emulators available under this brand mostly cover the Digital Equipment DEC hardware platforms PDP-11, VAX, and AlphaServer, which support many of the legacy operating systems, including Tru64 and OpenVMS. The product range also includes virtualization solutions for HP 3000 using MPE/iX and SPARC. Charon software products have been developed by the Swiss software company Stromasys SA, which has its headquarters in Cointrin, near Geneva.

Synergy DBL is a compiled, imperative programming language designed for business use. The language was originally called DBL; later it was referred to as Synergy Language; as of 2012 the official name is Synergy DBL. It is based on Digital Equipment Corporation’s DIBOL programming language.

The History of the Berkeley Software Distribution begins in the 1970s.

MICA was the codename of the operating system developed for the DEC PRISM architecture. MICA was designed by a team at Digital Equipment Corporation led by Dave Cutler. MICA's design was driven by Digital's need to provide a migration path to PRISM for Digital's VAX/VMS customers, as well as allowing PRISM systems to compete in the increasingly important Unix market. MICA attempted to address these requirements by implementing VMS and ULTRIX user interfaces on top of a common kernel that could support the system calls, libraries and utilities needed for both environments.

References

  1. Patrick Thibodeau (July 31, 2014). "HP gives OpenVMS new life". Computerworld . Retrieved October 21, 2021.
  2. Camiel Vanderhoeven (May 30, 2021). "How much of VMS is still in MACRO-32?". Newsgroup:  comp.os.vms . Retrieved October 21, 2021.
  3. "2.7 In what language is OpenVMS written?". The OpenVMS Frequently Asked Questions (FAQ). Hewlett Packard Enterprise. Archived from the original on August 10, 2018.
  4. 1 2 "Access to OpenVMS Source Code?". HP OpenVMS Systems ask the wizard. September 2, 1999. Archived from the original on October 28, 2017.
  5. "Webinar 16: x86 Update". VSI. October 15, 2021. Archived from the original on December 11, 2021. Retrieved November 2, 2021.
  6. 1 2 "VSI OpenVMS v9.2 Released". VSI. July 14, 2022. Retrieved July 14, 2022.
  7. "Japanese OpenVMS OS (JVMS)". VSI. Retrieved February 5, 2021.
  8. Michael M. T. Yau (1993). "Supporting the Chinese, Japanese, and Korean Languages in the OpenVMS Operating System" (PDF). Digital Technical Journal. 5 (3). Retrieved October 21, 2021.
  9. 1 2 3 4 5 6 "OpenVMS at 20 Nothing stops it" (PDF). Digital Equipment Corporation. October 1997. Retrieved February 12, 2021.
  10. 1 2 3 4 "Software Product Description and QuickSpecs - VSI OpenVMS Version 8.4-2L1 for Integrity servers" (PDF). VMS Software Inc. July 2019. Retrieved January 2, 2021.
  11. "VSI Business & New Products Update – April 9, 2019" (PDF). VSI. April 2019. Retrieved May 4, 2021.
  12. Charles Babcock (November 1, 2007). "VMS Operating System Is 30 Years Old; Customers Believe It Can Last Forever". InformationWeek. Retrieved February 19, 2021.
  13. Drew Robb (November 1, 2004). "OpenVMS survives and thrives". computerworld.com. Retrieved December 31, 2020.
  14. Tao Ai Lei (May 30, 1998). "Digital tries to salvage OpenVMS". computerworld.co.nz. Retrieved December 31, 2020.
  15. Jesse Lipcon (October 1997). "OpenVMS: 20 Years of Renewal". Digital Equipment Corporation. Archived from the original on February 17, 2006. Retrieved February 12, 2021.
  16. "VAX-11/780 Hardware Handbook" (PDF). Digital Equipment Corporation. 1979. Retrieved October 17, 2022.
  17. Patrick Thibodeau (June 11, 2013). "OpenVMS, R.I.P. 1977-2020?". Computerworld .
  18. Tom Merritt (2012). Chronology of Tech History. p. 104. ISBN   978-1300253075.
  19. "VAX 11/780 - OLD-COMPUTERS.COM : HISTORY / detailed info" . Retrieved April 25, 2020.
  20. "VSI Products". VSI.
  21. 1 2 "Rollout of V9.0 and Beyond" (PDF). VSI. May 19, 2020. Retrieved May 4, 2021.
  22. "HP hands off OpenVMS development to VSI". Tech Times. August 1, 2014. Retrieved January 29, 2016.
  23. "VMS Software, Inc. Named Exclusive Developer of Future Versions of OpenVMS Operating System" (Press release). Retrieved October 27, 2017.
  24. 1 2 "VSI Products - Clusters". VSI. Retrieved May 4, 2021.
  25. "Cluster Uptime". November 28, 2003. Archived from the original on February 29, 2012. Retrieved December 20, 2020.
  26. "Commerzbank Survives 9/11 with OpenVMS Clusters" (PDF). July 2009. Retrieved August 14, 2020.
  27. "February 2018 Business & Technical Update" (PDF). VSI. February 2018. Retrieved May 4, 2021.
  28. Cutler, Dave (February 25, 2016). "Dave Cutler Oral History". youtube.com (Interview). Interviewed by Grant Saviers. Computer History Museum. Archived from the original on December 11, 2021. Retrieved February 26, 2021.
  29. 1 2 Stephen Hoffman (September 2006). "What is OpenVMS? What is its history?". hoffmanlabs.com. Archived from the original on May 18, 2021. Retrieved January 3, 2021.
  30. 1 2 "Software Product Description - VAX/VMS Operating System, Version 1.0" (PDF). Digital Equipment Corporation. September 1978. Retrieved October 21, 2021.
  31. "a simple question: what the h*ll is MCR?". Newsgroup:  comp.os.vms. September 14, 2004. Retrieved December 31, 2020.
  32. "Software Product Description VAX-11 RSX, Version 1.0" (PDF). Digital Equipment Corporation. October 1984. Retrieved September 20, 2021.
  33. "Hello from....well what used to be SpitBrook". openvmshobbyist.com. February 27, 2007. Retrieved January 24, 2021.
  34. "Computer system VAX/VMS". altiq.se. Retrieved January 24, 2021.
  35. Michael D Duffy (2002). Getting Started with OpenVMS: A Guide for New Users. ISBN   978-0080507354.
  36. "Micro VMS operating system". Computerworld . June 18, 1984. p. 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 ...
  37. Kathleen D. Morse. "The VMS/MicroVMS merge". DEC Professional Magazine. pp. 74–84.
  38. 1 2 "VMS Version 5.0 Release Notes" (PDF). DEC. April 1988. Retrieved July 21, 2021.
  39. Bob McCormick (January 11, 1989). "DECUServe WORKSTATIONS Conference 8". home.iae.nl. Retrieved December 22, 2020.
  40. "Office Archaeology". blog.nozell.com. February 24, 2004. Retrieved December 22, 2020.
  41. "Software Product Description - Desktop-VMS, Version 1.2" (PDF). Digital. January 1991. Archived from the original (PDF) on August 16, 2000. Retrieved February 2, 2022.
  42. "OpenVMS pages of proGIS Germany". vaxarchive.org. Retrieved December 22, 2020.
  43. D.O. Andrievskaya, ed. (May 1989). "Computer Complexes, Technical Equipment, Software And Support Of The System Of Small Electronic Computer Machines (SM Computer)" (PDF) (in Russian). Soviet Union Research Institute of Information and Economics. Retrieved October 16, 2021.
  44. Prokhorov N.L.; Gorskiy V.E. "Basic software for 32-bit SM computer models". Software Systems Journal (in Russian). 1988 (3). Retrieved October 15, 2021.
  45. Egorov G.A.; Ostapenko G.P.; Stolyar N.G.; Shaposhnikov V.A. "Multifunctional operating system that supports virtual memory for 32-bit computers". Software Systems Journal (in Russian). 1988 (4). Retrieved October 15, 2021.
  46. "Installing OS MOS-32M" (PDF). pdp-11.ru (in Russian). June 16, 2012. Archived from the original (PDF) on October 27, 2021. Retrieved October 15, 2021.
  47. "VMS Version 5.0 Release Notes" (PDF). Digital Equipment Corporation. April 1988. Retrieved October 27, 2021.
  48. "Digital Introduces First Generation of OpenVMS Alpha-Ready Systems". Digital Equipment Corporation. July 15, 1992. Retrieved January 25, 2021.
  49. "OpenVMS Definition from PC Magazine Encyclopedia".
  50. Arne Vajhøj (November 29, 1999). "OpenVMS FAQ - What is the difference between VMS and OpenVMS?". vaxmacro.de. Retrieved January 25, 2021.
  51. "History of the Vernon the VMS shark". vaxination.ca. Retrieved January 24, 2021.
  52. Dave Cutler (May 30, 1988). "DECwest/SDT Agenda" (PDF). bitsavers.org.
  53. "EV-4 (1992)". February 24, 2008.
  54. 1 2 Comerford, R. (July 1992). "How DEC developed Alpha". IEEE Spectrum. 29 (7): 26–31. doi:10.1109/6.144508.
  55. "Managing Technological Leaps: A study of DEC's Alpha Design Team" (PDF). April 1993.
  56. Supnik, Robert M. (1993). "Digital's Alpha project". Communications of the ACM. 36 (2): 30–32. doi:10.1145/151220.151223. ISSN   0001-0782. S2CID   32694010.
  57. 1 2 3 Clair Grant (June 2005). "Porting OpenVMS to HP Integrity Servers" (PDF). OpenVMS Technical Journal. 6.
  58. 1 2 Nancy P. Kronenberg; Thomas R. Benson; Wayne M. Cardoza; Ravindran Jagannathan; Benjamin J. Thomas III (1992). "Porting OpenVMS from VAX to Alpha AXP" (PDF). Digital Technical Journal. 4 (4). Retrieved October 3, 2022.
  59. 1 2 "OpenVMS Compatibility Between VAX and Alpha". Digital Equipment Corporation. May 1995. Retrieved October 22, 2021.
  60. "Extending OpenVMS for 64-bit Addressable Virtual Memory" (PDF). Digital Technical Journal. 8 (2): 57–71. 1996. S2CID   9618620.
  61. "The OpenVMS Mixed Pointer Size Environment" (PDF). Digital Technical Journal. 8 (2): 72–82. 1996. S2CID   14874367. Archived from the original (PDF) on February 19, 2020.
  62. "VSI OpenVMS Programming Concepts Manual, Vol. 1" (PDF). VSI. April 2020. Retrieved October 7, 2020.
  63. "HP OpenVMS Alpha Partitioning and Galaxy Guide". HP. September 2003. Retrieved October 22, 2021.
  64. James Niccolai (October 14, 1998). "Compaq details strategy for OpenVMS". Australian Reseller News. Retrieved January 14, 2021.
  65. "Compaq OpenVMS Times" (PDF). January 2002. Archived from the original (PDF) on March 2, 2006.
  66. Andrew Orlowski (June 25, 2001). "Farewell then, Alpha – Hello, Compaq the Box Shifter". theregister.com. Retrieved December 21, 2020.
  67. Sue Skonetski (January 31, 2003). "OpenVMS Boots on Itanium on Friday Jan 31". Newsgroup:  comp.os.vms . Retrieved December 21, 2020.
  68. "HP C Installation Guide for OpenVMS Industry Standard 64 Systems" (PDF). HP. June 2007. Retrieved March 2, 2021.
  69. Thomas Siebold (2005). "OpenVMS Integrity Boot Environment" (PDF). decus.de. Retrieved December 21, 2020.
  70. 1 2 3 Camiel Vanderhoeven (October 8, 2017). Re-architecting SWIS for X86-64. YouTube . Archived from the original on December 11, 2021. Retrieved October 21, 2021.
  71. Gaitan D’Antoni (2005). "Porting OpenVMS Applications to Itanium" (PDF). hp-user-society.de. Retrieved December 21, 2020.
  72. "OpenVMS floating-point arithmetic on the Intel Itanium architecture" (PDF). decus.de. 2003. Retrieved December 21, 2020.
  73. Thomas Siebold (2005). "OpenVMS Moving Custom Code" (PDF). decus.de. Retrieved December 21, 2020.
  74. Paul Lacombe (2005). "HP OpenVMS Strategy and Futures" (PDF). de.openvms.org. Retrieved December 21, 2020.
  75. "VMS Software, Inc. Named Exclusive Developer of Future Versions of OpenVMS Operating System". July 31, 2014. Archived from the original on August 10, 2014.
  76. 1 2 "OpenVMS Rolling Roadmap" (PDF). VSI. December 2019. Archived from the original (PDF) on June 10, 2020. Retrieved May 4, 2021.
  77. "VSI V9.0 Q&A". VSI. June 16, 2020. Retrieved May 4, 2021.
  78. VSI (June 1, 2021). OpenVMS x64 Atom Project. YouTube . Archived from the original on December 11, 2021. Retrieved June 2, 2021.
  79. 2017 LLVM Developers' Meeting: J. Reagan "Porting OpenVMS using LLVM". YouTube . October 31, 2017. Archived from the original on December 11, 2021.
  80. "State of the Port to x86_64 January 2017" (PDF). January 6, 2017. Archived (PDF) from the original on November 4, 2019.
  81. "VMS Software Inc. Announces First Boot on x86 Architecture". VSI. May 14, 2019. Retrieved May 4, 2021.
  82. "State of the Port". VSI. Archived from the original on April 18, 2021. Retrieved April 16, 2021.
  83. 1 2 "OpenVMS 9.1". VSI. June 30, 2021. Archived from the original on June 30, 2021. Retrieved June 30, 2021.
  84. 1 2 "VMS Software Releases OpenVMS V9.1-A". VSI. September 30, 2021. Retrieved September 30, 2021.
  85. Catherine Richardson; Terry Morris; Rockie Morgan; Reid Brown; Donna Meikle (March 1987). "MICA Software Business Plan" (PDF). Bitsavers. Retrieved January 4, 2021.
  86. Zachary, G. Pascal (2014). Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft. Open Road Media. ISBN   978-1-4804-9484-8 . Retrieved January 4, 2021.
  87. Mark Russinovich (October 30, 1998). "Windows NT and VMS: The Rest of the Story". ITPro Today. Retrieved January 4, 2021.
  88. Eugenia Loli (November 23, 2004). "FreeVMS 0.1.0 Released". OSnews. Retrieved April 2, 2022.
  89. "FreeVMS official web page". Archived from the original on September 8, 2018.
  90. Wiecek, Cheryl A.; Kaler, Christopher G.; Fiorelli, Stephen; Davenport, Jr., William C.; Chen, Robert C. (April 1992). "A Model and Prototype of VMS Using the Mach 3.0 Kernel". Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures: 187–203. Retrieved September 20, 2021.
  91. 1 2 3 4 5 6 Ruth E. Goldenberg; Lawrence J. Kenah; Denise E. Dumas (1991). VAX/VMS Internals and Data Structures, Version 5.2. Digital Press. ISBN   978-1555580599.
  92. 1 2 3 Hunter Goatley; Edward A. Heinrich. "Writing VMS Privileged Code Part I: The Fundamentals, Part 1". hunter.goatley.com. Retrieved January 31, 2021.
  93. Paul A. Karger; Mary Ellen Zurko; Douglas W. Benin; Andrew H. Mason; Clifford E. Kahnh (May 7–9, 1990). A VMM security kernel for the VAX architecture (PDF). Proceedings. 1990 IEEE Computer Society Symposium on Research in Security and Privacy. IEEE. doi:10.1109/RISP.1990.63834 . Retrieved January 31, 2021.
  94. "VSI OpenVMS System Services Reference Manual: A–GETUAI" (PDF). VSI. June 2020. Retrieved February 15, 2021.
  95. Wayne Sewell (1992). Inside VMS: The System Manager's and System Programmer's Guide to VMS Internals. Van Nostrand Reinhold. ISBN   0-442-00474-5.
  96. "VSI OpenVMS I/O User's Reference Manual" (PDF). VSI. August 2019. Retrieved January 13, 2021.
  97. 1 2 "Andy Goldstein on Files-11, the OpenVMS File Systems". VSI Official Channel. July 25, 2019. Archived from the original on January 12, 2021. Retrieved January 3, 2021.
  98. "VSI OpenVMS Guide to OpenVMS File Applications" (PDF). VSI. July 23, 2019. Retrieved January 13, 2021.
  99. "Why was Spiralog retired?". Hewlett Packard Enterprise Community - Operating System - OpenVMS. January 10, 2006. Retrieved January 13, 2021.
  100. "Why was Spiralog retired?". Hewlett Packard Enterprise Community - Operating System - OpenVMS. January 10, 2006. Retrieved January 13, 2021.
  101. "VSI OpenVMS Software Roadmap 2020" (PDF). September 2020. Archived from the original (PDF) on December 7, 2020. Retrieved September 23, 2020.
  102. "OpenVMS User's Manual" (PDF). VSI. VSI. July 2020. Chapter 14, Advanced Programming with DCL. Retrieved April 9, 2021.
  103. 1 2 Simon Clubley (July 3, 2017). "How dangerous is it to be able to get into DCL supervisor mode?". Newsgroup:  comp.os.vms . Retrieved February 1, 2021.
  104. "VSI OpenVMS Cluster Systems" (PDF). VSI. August 2019. Retrieved January 13, 2021.
  105. "Building Dependable Systems: The OpenVMS Approach" (PDF). DEC. May 1994. Retrieved July 31, 2021.
  106. "Cluster Uptime". November 28, 2003. Archived from the original on February 29, 2012. Retrieved December 20, 2020.
  107. "DECnet for OpenVMS Guide to Networking" (PDF). VSI. August 2020. Retrieved January 14, 2021.
  108. "VSI Products - DECnet". VSI. Retrieved January 14, 2021.
  109. "VMS/ULTRIX System Manager's Guide". Digital Equipment Corporation. September 1990. Retrieved January 21, 2021.
  110. "VSI OpenVMS TCP/IP User's Guide" (PDF). VSI. August 2019. Retrieved January 14, 2021.
  111. Robert Rappaport; Yanick Pouffary; Steve Lieman; Mary J. Marotta (2004). "Parallelism and Performance in the OpenVMS TCP/IP Kernel". OpenVMS Technical Journal. 4.
  112. Alan Abrahams; David A. Low (1992). "An Overview of the PATHWORKS Product Family" (PDF). Digital Technical Journal. 4 (1).
  113. Andy Goldstein (2005). "Samba and OpenVMS" (PDF). de.openvms.org. Retrieved January 1, 2021.
  114. "Local Area Transport Network Concepts" (PDF). DEC. June 1988. Retrieved January 14, 2021.
  115. 1 2 3 4 5 "VAX/VMS Software Language and Tools Handbook" (PDF). bitsavers.org. 1985. Retrieved December 31, 2020.
  116. "VSI List of Products". VSI. Retrieved May 4, 2021.
  117. "VSI OpenVMS Calling Standard" (PDF). January 2021. Retrieved May 4, 2021.
  118. "VSI OpenVMS Programming Concepts Manual, Volume II" (PDF). VSI. April 2020. Retrieved May 4, 2021.
  119. "SDL, LANGUAGE, Data Structure/Interface Definition Language". digiater.nl. November 1996. Retrieved January 3, 2021.
  120. "DECset". VSI. Retrieved January 2, 2021.
  121. "VSI OpenVMS DCL Dictionary: A-M" (PDF). VSI. April 2020. Retrieved January 2, 2021.
  122. "VSI OpenVMS Debugger Manual" (PDF). VSI. June 2020. Retrieved May 4, 2021.
  123. "VSI OpenVMS Delta/XDelta Debugger Manual" (PDF). VSI. August 2019. Retrieved December 31, 2020.
  124. "VMS IDE". marketplace.visualstudio.com. Retrieved January 2, 2021.
  125. "VAX/VMS Software Information Management Handbook" (PDF). Digital Equipment Corporation. 1985. Retrieved January 24, 2021.
  126. Ian Smith (2004). "Rdb's First 20 Years: Memories and Highlights" (PDF). Archived from the original (PDF) on November 3, 2005. Retrieved January 24, 2021.
  127. "Compaq ACMS for OpenVMS Getting Started". Compaq. December 1999. Retrieved January 24, 2021.
  128. "Building Dependable Systems: The OpenVMS Approach". Digital Equipment Corporation. March 1994. Retrieved October 17, 2022.
  129. "Cover Letter for DECADMIRE V2.1 MUP Kit - DECADMIRE V2.1A". Digital Equipment Corporation. 1995. Retrieved January 24, 2021.[ permanent dead link ]
  130. Kevin Duffy; Philippe Vigier (2004). "Oracle Rdb Status and Direction" (PDF). Retrieved January 24, 2021.
  131. Larry Goelz; John Paladino (May 31, 1999). "Cover Letter re DSM". Compaq. Retrieved January 24, 2021.[ permanent dead link ]
  132. Neil Rieck (June 29, 2020). "OpenVMS Notes MySQL and MariaDB" . Retrieved January 24, 2021.
  133. Bengt Gunne (2017). "Mimer SQL on OpenVMS Present and Future" (PDF). Retrieved January 24, 2021.
  134. "Rocket Software System 1032". Rocket Software. Retrieved January 24, 2021.
  135. Stephen Hoffman; Paul Anagnostopoulos (1999). Writing Real Programs in DCL, second edition. ISBN   1-55558-191-9.
  136. "Software Product Description HP DECforms for OpenVMS, Version 4.0" (PDF). Hewlett Packard Enterprise. August 2006. Retrieved January 1, 2021.[ permanent dead link ]
  137. "Software Product Description HP FMS for OpenVMS, Version 2.5" (PDF). Hewlett Packard Enterprise. January 2005. Retrieved January 1, 2021.[ permanent dead link ]
  138. "Compaq TDMS for OpenVMS VAX, Version 1.9B" (PDF). Hewlett Packard Enterprise. July 2002. Retrieved January 1, 2021.[ permanent dead link ]
  139. "OpenVMS RTL Screen Management (SMG$) Manual". Hewlett Packard Enterprise. 2001. Archived from the original on December 4, 2020. Retrieved January 1, 2021.
  140. Rick Spitz; Peter George; Stephen Zalewski (1986). "The Making of a Micro VAX Workstation" (PDF). Digital Technical Journal. 1 (2). Retrieved October 21, 2021.
  141. "MicroVMS Workstation Graphics Programming Guide" (PDF). Digital Equipment Corporation. May 1986. Retrieved October 21, 2021.
  142. Fred Kleinsorge (January 4, 2007). "comp.os.vms - Dec VWS Internals". Newsgroup:  comp.os.vms . Retrieved February 27, 2021.
  143. Scott A. McGregor (1990). "An Overview of the DECwindows Architecture" (PDF). Digital Technical Journal. Digital Equipment Corporation. 2 (3). Retrieved October 21, 2021.
  144. 1 2 3 4 "(Open)VMS(/ VAX), Version overview". vaxmacro.de. Retrieved October 21, 2021.
  145. "Migrating VWS/UIS Applications to DECwindows?". HP OpenVMS ask the wizard. November 9, 2004. Archived from the original on September 15, 2018.
  146. Janet Dobbs (August 1989). "Strategies for Writing Graphical UNIX Applications Productively and Portably" (PDF). AUUG Newsletter. 10 (4): 50. Retrieved December 29, 2021.
  147. "Using DECwindows Motif for OpenVMS" (PDF). VSI. October 2019. Retrieved October 21, 2020.
  148. S. Kadantsev; M. Mouat. Early Experience With DECwindows/Motif In the TRIUMF Central Control System (PDF). 13th International Conference on Cyclotrons and their Applications. pp. 676–677.
  149. "Getting Started With the New Desktop". Digital Equipment Corporation. May 1996. Retrieved October 21, 2021.
  150. OpenGL Frequently Asked Questions (FAQ) [1/3]. Faqs.org. Retrieved on July 17, 2013.
  151. "Software Product Description VSI Graphical Kernel System" (PDF). VSI. 2017. Retrieved January 2, 2021.
  152. "Software Product Description DEC PHIGS Version 3.1 for OpenVMS VAX" (PDF). Hewlett Packard Enterprise. April 1995. Retrieved January 2, 2021.[ permanent dead link ]
  153. "VSI OpenVMS Guide to System Security" (PDF). VSI. December 2019. Retrieved April 26, 2021.
  154. National Computer Security Center (NCSC) Trusted Product Evaluation List (TPEL)
  155. "HP OpenVMS Guide to System Security". Hewlett Packard. September 2003. Retrieved October 21, 2021.
  156. Green, James L.; Sisson, Patricia L. (June 1989). "The "Father Christmas" Worm" (PDF). 12th National Computer Security Conference Proceedings. Retrieved November 23, 2015.
  157. Kevin Rich (November 2004). "Security Audit on OpenVMS: An Internal Auditor's Perspective". SANS Institute. Retrieved July 21, 2021.
  158. Claes Nyberg; Christer Oberg; James Tusini (January 20, 2011). "DEFCON 16: Hacking OpenVMS". YouTube . Archived from the original on December 11, 2021. Retrieved July 21, 2021.
  159. Stoll, Clifford (1989). The Cuckoo's Egg : tracking a spy through the maze of computer espionage (1st ed.). New York: Doubleday. ISBN   0-385-24946-2.
  160. 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.
  161. John Leyden (February 6, 2018). "Ghost in the DCL shell: OpenVMS, touted as ultra reliable, had a local root hole for 30 years". theregister.com. Retrieved January 13, 2021.
  162. Digital Equipment Corporation (1994). Software Product Description - POSIX for OpenVMS 2.0.
  163. "OpenVMS Alpha Version 7.3-1 New Features and Documentation Overview Begin Index". June 2002.[ permanent dead link ]
  164. "VSI Products - GNV". VSI. Retrieved August 19, 2020.
  165. "ϕnix: a Unix emulator for VAX/VMS" (PDF). August 10, 1987. Archived from the original (PDF) on January 22, 2004.
  166. "Compaq and DECUS expand Free License OpenVMS Hobbyist Program". Compaq. March 10, 1999. Retrieved August 1, 2021.
  167. "Hobbyist Program". Process Software. Retrieved April 24, 2020.
  168. Bill Pedersen; John Malmberg. "VMS Hardware". vms-ports. Retrieved July 30, 2021.
  169. "HPE sets end date for hobbyist licenses for OpenVMS". Archived from the original on July 4, 2020. Retrieved July 4, 2020.
  170. "VMS Software Announces Community License". VSI. April 22, 2020. Retrieved May 4, 2021.
  171. "VMS Software Community License Available". VSI. July 28, 2020. Retrieved May 4, 2021.
  172. "VSI Announces Community License Updates". VSI. June 11, 2020. Retrieved May 4, 2021.
  173. "HP OpenVMS Systems - OpenVMS Release History". June 21, 2010. Archived from the original on October 7, 2018.
  174. "OpenVMS – A guide to the strategy and roadmap". VSI. Retrieved September 27, 2021.
  175. "HP OpenVMS Systems - Supported Software Versions - January 2014". Archived from the original on October 14, 2018.
  176. 1 2 3 4 "VSI OpenVMS Software Roadmap 2021" (PDF). VSI. VSI. Retrieved September 30, 2021.
  177. "OpenVMS Software Technical Support Service" (PDF). hp.com. Hewlett Packard. October 2003. Retrieved February 1, 2022.
  178. "OpenVMS Release History". Bitsavers. HP. Retrieved January 23, 2022.
  179. 1 2 Andy Goldstein (September 16, 1997). "When Did VMS First Come Out?". Newsgroup:  comp.os.vms . Retrieved March 5, 2022.
  180. 1 2 3 VAX/VMS Release Notes Version 1.5. DEC. February 1979. AA-D015B-TE.
  181. VAX/VMS Release Notes Version 1.6. DEC. August 1979. AA-J039A-TE.
  182. "VAX/VMS Release Notes Version 3.0" (PDF). DEC. May 1982. AA-D015D-TE. Retrieved February 6, 2022.
  183. "VAX/VMS Internals and Data Structures" (PDF). DEC. April 1981. Retrieved February 6, 2022.
  184. "VAX-11 Information Directory and Index" (PDF). DEC. May 1981. AA-D016D-TE. Retrieved February 6, 2022.
  185. "GRPNAM SECURITY HOLE IN LOGIN". DEC. Retrieved February 6, 2022.
  186. Bob Boyd (September 18, 1987). "First Introduction of BACKUP utility". Newsgroup:  comp.os.vms . Retrieved February 6, 2022.
  187. VAX/VMS Release Notes Version 3.1. DEC. August 1982. AA-N472A-TE.
  188. VAX/VMS Release Notes Version 3.2. DEC. December 1982. AA-P763A-TE.
  189. VAX/VMS Release Notes Version 3.3. DEC. April 1983. AA-P764A-TE.
  190. VAX/VMS Release Notes Version 3.4. DEC. June 1983. AA-P765A-TE.
  191. VAX/VMS Release Notes Version 3.5. DEC. November 1983. AA-P766A-TE.
  192. VAX/VMS Release Notes Version 3.6. DEC. April 1984. AA-V332A-TE.
  193. VAX/VMS Release Notes Version 3.7. DEC. August 1984. AA-CJ33A-TE.
  194. vms-source-listings
  195. vms-source-listings
  196. "HP OpenVMS Systems - OpenVMS Version 8.4". Archived from the original on September 2, 2010.
  197. "VMS Software, Inc. Launches New Version of OpenVMS Operating System Worldwide" (PDF) (Press release). June 1, 2015. Archived from the original (PDF) on August 7, 2015. Retrieved June 4, 2015.
  198. "VMS Software, Inc. Launches New Version 8.4-2L1 of OpenVMS Operating System Worldwide". VSI (Press release). September 23, 2016. Retrieved May 4, 2021.
  199. "VMS Software, Inc. Launches VSI OpenVMS Alpha V8.4-2L1 for Alpha Hardware". VSI (Press release). January 27, 2017. Retrieved May 4, 2021.
  200. 1 2 "Roadmap Update". VSI. September 2020. Archived from the original on September 27, 2020. Retrieved September 23, 2020.
  201. "OpenVMS for x86 V9.0 EAK goes to first customer on May 15, 2020". VSI. April 24, 2020. Retrieved May 4, 2021.
  202. "VSI Announces Initial Focus on Hypervisor Support for OpenVMS on x86". VSI. May 5, 2022. Retrieved May 5, 2022.

Further reading