Loading AI tools
Computer operating system From Wikipedia, the free encyclopedia
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]
 | |
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 state | Current |
| Source model | Closed-source with open-source components. Formerly source available[4][5] |
| Initial release | Announced: October 25, 1977 V1.0 / August 1978 |
| Latest release | V9.2-2 / January 25, 2024[6] |
| Latest preview | E9.2-3 / August 8, 2024 |
| Marketing target | Servers (historically Minicomputers, Workstations) |
| Available in | English, Japanese.[7] Historical support for Chinese (both Traditional and Simplified characters), Korean, Thai.[8] |
| Update method | Concurrent 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 | vmssoftware |
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]
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 backward compatibility with DEC's existing RSX-11M operating system.[9] 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.[30] 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.[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]
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 of 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]
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 another 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 confused 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]
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 Linkable 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 been 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]
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 is being explored 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]
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]
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]
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]
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 2 TiB volumes.[97] DEC attempted to replace it with a log-structured 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]
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).[102] 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.[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]
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.[91][103]
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] OpenVMS clusters allow applications to function during planned or unplanned outages.[105] Planned outages include hardware and software upgrades.[106]
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] VAX/VMS V1.0 featured support for DECnet Phase II,[108] 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).[109] 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).[110][111] TCP/IP Services is based on a port of the BSD network stack to OpenVMS,[112] 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.[113] 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.[114]
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.[115]
DEC (and its successor companies) provided a wide variety of programming languages for VMS. Officially supported languages on VMS, either current or historical, include:[116][117]
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.[118] 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.[119] 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.[120]
DEC provided a collection of software development tools in a layered product named DECset (originally named VAXset).[116] This consisted of the following tools:[121]
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.[123] A pair of lower-level debuggers, named DELTA and XDELTA, can be used to debug privileged code in additional to normal application code.[124]
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.[125]
DEC created a number of optional database products for VMS, some of which were marketed as the VAX Information Architecture family.[126] These products included:
In 1994, DEC sold Rdb, DBMS and CDD to Oracle, where they remain under active development.[131] In 1995, DEC sold DSM to InterSystems, who renamed it Open M, and eventually replaced it with their Caché product.[132]
Examples of third-party database management systems for OpenVMS include MariaDB,[133] Mimer SQL[134] (Itanium and x86-64[135]), and System 1032.[136]
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.
The DIGITAL Command Language (DCL) has served as the primary command language interpreter (CLI) of OpenVMS since the first release.[137][30][10] Other official CLIs available for VMS include the RSX-11 Monitor Console Routine (MCR) (VAX only), and various Unix shells.[116] 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.[138][139][140] A lower level interface named Screen Management Services (SMG$), comparable to Unix curses, also exists.[141]
Over the years, VMS has gone through a number of different GUI toolkits and interfaces:
Versions of VMS running on DEC Alpha workstations in the 1990s supported OpenGL[152] and Accelerated Graphics Port (AGP) graphics adapters. VMS also provides support for older graphics standards such as GKS and PHIGS.[153][154] Modern versions of DECwindows are based on X.Org Server.[10]
OpenVMS provides various security features and mechanisms, including security identifiers, resource identifiers, subsystem identifiers, ACLs, intrusion detection and detailed security auditing and alarms.[155] Specific versions evaluated at Trusted Computer System Evaluation Criteria Class C2 and, with the SEVMS security enhanced release at Class B1.[156] OpenVMS also holds an ITSEC E3 rating (see NCSC and Common Criteria).[157] Passwords are hashed using the Purdy Polynomial.
SYSTEM, FIELD, SYSTEST and DECNET) with default passwords which were often left unchanged by system managers.[158][159] 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.[160] 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.[161] In V5.0, the default passwords were removed, and it became mandatory to provide passwords for these accounts during system setup.[38]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.[116] In 1992, DEC released the POSIX for OpenVMS layered product, which included a shell based on the KornShell.[164] 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.[165] Amongst other GNU tools, GNV includes a port of the Bash shell to VMS.[166] Examples of third-party Unix compatibility layers for VMS include Eunice.[167]
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.[168] Since then, several companies producing OpenVMS software have made their products available under the same terms, such as Process Software.[169] 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.[170]
In March 2020, HPE announced the end of the OpenVMS Hobbyist Program.[171] 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.[172] The CLP was launched in July 2020, and provides licenses for VSI OpenVMS releases on Alpha, Integrity and x86-64 systems.[173] 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.[174]
| Version | Vendor | Release date [175][9][176] |
End of support [177][178][179] |
Platform | Significant changes, new hardware support [180][146] |
|---|---|---|---|---|---|
| X0.5[n 1] | DEC | April 1978[181] | ? | VAX | First version shipped to customers[29] |
| V1.0 | August 1978 | First production release | |||
| V1.01 | ?[n 2] | Bug fixes[182] | |||
| V1.5 | February 1979[n 3] | Support for native COBOL, BLISS compilers[182] | |||
| V1.6 | August 1979 | RMS-11 updates[183] | |||
| V2.0 | April 1980 | VAX-11/750, new utilities including EDT | |||
| V2.1 | ?[n 4] | ? | |||
| V2.2 | April 1981 | Process limit increased to 8,192[185] | |||
| V2.3 | May 1981[186] | Security enhancements[187] | |||
| V2.4 | ? | ? | |||
| V2.5 | ? | BACKUP utility[188] | |||
| V3.0 | April 1982 | VAX-11/730, VAX-11/725, VAX-11/782, ASMP | |||
| V3.1 | August 1982 | PL/I runtime bundled with base OS[189] | |||
| V3.2 | December 1982 | Support for RA60, RA80, RA81 disks[190] | |||
| V3.3 | April 1983 | HSC50 disk controller, BACKUP changes[191] | |||
| V3.4 | June 1983 | Ethernet support for DECnet,[192] VAX-11/785 | |||
| V3.5 | November 1983 | Support for new I/O devices[193] | |||
| V3.6 | April 1984 | Bug fixes[194] | |||
| V3.7 | August 1984 | Support for new I/O devices[195] | |||
| V4.0 | September 1984 | VAX 8600, MicroVMS, VAXclusters[196] | |||
| V4.1 | January 1985 | MicroVAX/VAXstation I, II[197] | |||
| V4.2 | October 1985 | Text Processing Utility | |||
| V4.3 | December 1985 | DELUA Ethernet adapter support | |||
| V4.3A | January 1986 | VAX 8200 | |||
| V4.4 | July 1986 | VAX 8800/8700/85xx, Volume Shadowing | |||
| V4.5 | November 1986 | Support for more memory in MicroVAX II | |||
| V4.5A | December 1986 | Ethernet VAXclusters | |||
| V4.5B | March 1987 | VAXstation/MicroVAX 2000 | |||
| V4.5C | May 1987 | MicroVAX 2000 cluster support | |||
| V4.6 | August 1987 | VAX 8250/8350/8530, RMS Journalling | |||
| V4.7 | January 1988 | First release installable from CD-ROM | |||
| V4.7A | March 1988 | VAXstation 3200/3500, MicroVAX 3500/3600 | |||
| V5.0 | April 1988 | VAX 6000, SMP, LMF, Modular Executive | |||
| V5.0-1 | August 1988 | Bug fixes | |||
| V5.0-2 | October 1988 | ||||
| V5.0-2A | MicroVAX 3300/3400 | ||||
| V5.1 | February 1989 | DECwindows | |||
| V5.1-B | VAXstation 3100 30/40, Desktop-VMS | ||||
| V5.1-1 | June 1989 | VAXstation 3520/3540, MicroVAX 3800/3900 | |||
| V5.2 | September 1989 | Cluster-wide process visibility/management | |||
| V5.2-1 | October 1989 | VAXstation 3100 38/48 | |||
| V5.3 | January 1990 | Support for third-party SCSI devices | |||
| V5.3-1 | April 1990 | Support for VAXstation SPX graphics | |||
| V5.3-2 | May 1990 | Support for new I/O devices | |||
| V5.4 | October 1990 | VAX 65xx, VAX Vector Architecture | |||
| V5.4-0A | VAX 9000, bug fixes for VAX 6000 systems | ||||
| V5.4-1 | November 1990 | New models of VAX 9000, VAXstation, VAXft | |||
| V5.4-1A | January 1991 | VAX 6000-400 | |||
| V5.4-2 | March 1991 | VAX 4000 Model 200, new I/O devices | |||
| V5.4-3 | October 1991 | FDDI adapter support | |||
| V5.5 | November 1991 | Cluster-wide batch queue, new VAX models | |||
| A5.5 | Same as V5.5 but without new batch queue | ||||
| V5.5-1 | July 1992 | Bug fixes for batch/print queue | |||
| V5.5-2HW | September 1992 | VAX 7000/10000, and other new VAX hardware | |||
| V5.5-2 | November 1992 | September 1995 | Consolidation of previous hardware releases | ||
| V5.5-2H4 | August 1993 | New VAX 4000 models, additional I/O devices | |||
| V5.5-2HF | ? | VAXft 810 | |||
| V1.0[n 5] | November 1992 | Alpha | First release for Alpha architecture | ||
| V1.5 | May 1993 | Cluster and SMP support for Alpha | |||
| V1.5-1H1 | October 1993 | New DEC 2000, DEC 3000 models | |||
| V6.0 | June 1993 | VAX | TCSEC C2 compliance, ISO 9660, Motif | ||
| V6.1 | April 1994 | VAX, Alpha | Merger of VAX and Alpha releases, PCSI | ||
| V6.1-1H1 | September 1994 | Alpha | New AlphaStation, AlphaServer models | ||
| V6.1-1H2 | November 1994 | ||||
| V6.2 | June 1995 | March 1998 | VAX, Alpha | Command Recall, DCL$PATH, SCSI clusters | |
| V6.2-1H1 | December 1995 | Alpha | New AlphaStation, AlphaServer models | ||
| V6.2-1H2 | March 1996 | ||||
| V6.2-1H3 | May 1996 | ||||
| V7.0 | January 1996 | VAX, Alpha | 64-bit addressing, Fast I/O, Kernel Threads | ||
| V7.1 | January 1997 | July 2000 | Very Large Memory support, DCL PIPE, CDE | ||
| V7.1-1H1 | November 1997 | Alpha | AlphaServer 800 5/500, 1200 | ||
| V7.1-1H2 | April 1998 | Support for booting from third-party devices | |||
| V7.1-2 | Compaq | December 1998 | Additional I/O device support | ||
| V7.2 | February 1999 | June 2002 | VAX, Alpha | OpenVMS Galaxy, ODS-5, DCOM | |
| V7.2-1 | July 1999 | Alpha | AlphaServer GS140, GS60, Tsunami | ||
| V7.2-1H1 | June 2000 | AlphaServer GS160, GS320 | |||
| V7.2-2 | September 2001 | December 2002 | Minicopy support for Volume Shadowing | ||
| V7.2-6C1 | August 2001 | ? | DII COE conformance[198] | ||
| V7.2-6C2 | July 2002 | ||||
| V7.3 | June 2001 | December 2012 | VAX | Final release for VAX architecture | |
| June 2004 | Alpha | ATM and GBE clusters, Extended File Cache | |||
| V7.3-1 | HP | August 2002 | December 2004 | Alpha | Security and performance improvements |
| V7.3-2 | December 2003 | December 2006 | AlphaServer GS1280, DS15 | ||
| V8.0 | June 2003 | December 2003 | IA64 | Evaluation release for Integrity servers | |
| V8.1 | December 2003 | February 2005 | Second evaluation release for Integrity servers | ||
| V8.2 | February 2005 | June 2010 | Alpha, IA64 | Production release for Integrity servers | |
| V8.2-1 | September 2005 | IA64 | Support for HP Superdome, rx7620, rx8620 | ||
| V8.3 | August 2006 | December 2015 | Alpha, IA64 | Support for additional Integrity server models | |
| V8.3-1H1 | November 2007 | IA64 | Support for HP BL860c, dual-core Itanium | ||
| V8.4 | June 2010 | December 2020 | Alpha, IA64 | Support for HPVM, clusters over TCP/IP[199] | |
| V8.4-1H1 | VSI | May 2015 | December 2022 | IA64 | Support for Poulson processors[200] |
| V8.4-2 | March 2016 | Support for HPE BL890c systems, UEFI 2.3 | |||
| V8.4-2L1 | September 2016 | December 2024 | OpenSSL updated to 1.0.2[201] | ||
| January 2017[202] | TBA | Alpha | |||
| V8.4-2L2 | July 2017 | Final release for Alpha architecture[203] | |||
| V8.4-2L3 | April 2021 | December 2028 | IA64 | Final release for Integrity servers[203] | |
| V9.0 | May 2020 | June 2021 | x86-64 | x86-64 Early Adopter's Kit[204] | |
| V9.1 | June 2021 | September 2021 | x86-64 Field Test[83] | ||
| V9.1-A | September 2021 | April 2022 | DECnet-Plus for x86-64[84] | ||
| V9.2 | July 2022 | June 2023 | x86-64 Limited Production Release[205] | ||
| V9.2-1 | June 2023 | December 2026 | AMD CPUs, OpenSSL 3.0, native compilers[206] | ||
| V9.2-2 | January 2024 | TBA | Bug fixes[6] | ||
| V9.2-3 | December 2024 | TBA | VMware vMotion, VMDirectPath | ||
Legend: Old version, not maintained Old version, still maintained Latest version Future release | |||||
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
