OpenVMS

OpenVMS, often referred to as just VMS,[9] is a multi-user, multiprocessing virtual memory-based operating system designed to support time-sharing, batch processing, transaction processing and workstation applications.[10] It was first announced by Digital Equipment Corporation as VAX/VMS (Virtual Address eXtension/Virtual Memory System[11]) alongside the VAX-11/780 minicomputer in 1977.[12][13][14] OpenVMS has subsequently been ported to run on DEC Alpha systems, the Itanium-based HPE Integrity family of computers,[15] and select x86-64 hardware and hypervisors.[16] Since 2014, OpenVMS is developed and supported by a company named VMS Software Inc. (VSI).[17][18]

OpenVMS
OpenVMS V7.3-1 running the CDE-based DECwindows "New Desktop" GUI
DeveloperVMS Software Inc (VSI)[1] (previously Digital Equipment Corporation, Compaq, Hewlett-Packard)
Written inPrimarily VAX MACRO, BLISS, C, DCL.[2] Other languages also used.[3]
OS familyDEC OS family
Working stateCurrent
Source modelClosed source, source available[4]
Initial releaseOctober 25, 1977 (1977-10-25)
Latest releaseV8.4-2L2 / July 10, 2017 (2017-07-10)[5]
Latest previewV9.0-F / December 9, 2020 (2020-12-09)[6]
Marketing targetHigh-end computer server
Available inEnglish, Japanese.[7] Historical support for Chinese (both Traditional and Simplified characters), Korean, Thai.[8]
Update methodConcurrent upgrades,
rolling upgrades
Package managerPCSI and VMSINSTAL
PlatformsVAX, Alpha, Itanium, x86-64
Kernel typeMonolithic kernel with loadable modules
Default user interfaceDCL CLI and DECwindows GUI
LicenseProprietary
Official websitewww.vmssoftware.com

The system offers high availability through clustering and the ability to distribute the system over multiple physical machines,[19] allowing clustered applications and data to remain continuously accessible while operating system software and hardware maintenance and upgrades are performed,[20] or when a whole data center is destroyed.[21] VMS cluster uptimes of up to 17 years have been reported.[22] Customers using OpenVMS include banks and financial services, hospitals and healthcare, telecommunications operators, network information services, and industrial manufacturers.[23] During the 1990s and 2000s, there were nearly half a million VMS systems in operation worldwide.[24][25]

History

Origin and name changes
"Albert the Cheshire Cat" mascot for VAX/VMS, used by the DECUS VAX SIG[26][27]

In April 1975, Digital Equipment Corporation embarked on a hardware project, code named Star, to design a 32-bit virtual address extension to its PDP-11 computer line. A companion software project, code named Starlet, was started in June 1975 to develop a totally new operating system, based on RSX-11M, for the Star family of processors.[9] These two projects were tightly integrated from the beginning. Gordon Bell[28] was the VP lead on the VAX hardware and its architecture. Roger Gourd was the project lead for the Starlet program, with software engineers Dave Cutler (who would later lead development of Microsoft's Windows NT), Dick Hustvedt, and Peter Lipman acting as the technical project leaders, each having responsibility for a different area of the operating system. The Star and Starlet projects culminated in the VAX-11/780 computer and the VAX/VMS operating system. The Starlet name survived in VMS as a name of several of the main system libraries, including STARLET.OLB and STARLET.MLB.[29]

With the introduction of the MicroVAX range such as the MicroVAX I, MicroVAX II and MicroVAX 2000 in the mid-to-late 1980s, DIGITAL released MicroVMS versions specifically targeted for these platforms which had much more limited memory and disk capacity; e.g. the smallest MicroVAX 2000 had a 40MB RD32 hard disk and 2MB of RAM, and its CPU had to emulate some of the VAX floating point instructions in software. MicroVMS kits were released for VAX/VMS 4.4 to 4.7 on TK50 tapes and RX50 floppy disks, but discontinued with VAX/VMS V5.0.

Beginning in 1989, a short lived distribution of VMS named Desktop-VMS was sold with VAXstation systems. It consisted of a bundle of VMS, DECwindows, DECnet, VAXcluster support, and software that was designed to help non-technical users set up their workstation without assistance.[30][31] Desktop-VMS had its own versioning scheme beginning with V1.0, which corresponded to the V5.x releases of VAX/VMS.[32]

In July 1992,[33] Digital renamed VAX/VMS to OpenVMS as an indication for its support of "open systems" industry standards such as POSIX and Unix compatibility,[34] and to drop the VAX connection as the port to DIGITAL's 64-bit Alpha RISC processor was in process. The OpenVMS name was first used with the OpenVMS AXP V1.0 release in November 1992. Digital began using OpenVMS VAX instead of VAX/VMS with the V6.0 release in June 1993.[35]

Port to DEC Alpha
"Vernon the Shark" logo for OpenVMS[36]

In 1988, after the cancellation of the PRISM project, Ken Olsen asked Bob Supnik to investigate ways that Digital could keep the performance of VAX/VMS systems competitive with RISC-based Unix systems.[37] A group of engineers known as the "Extended VAX" or "EVAX" task force was formed, who originally attempted to produce a RISC-like subset of the VAX architecture.[37][38] When this approach turned out to be a dead end, the group began investigating the feasibility of porting VMS and its applications to a clean-slate RISC architecture. The group decided to adopt the Prism architecture with modifications, which eventually became the Alpha.[39] The project to port VMS to the Alpha architecture began in 1989, and booted successfully on real hardware for the first time in 1991.[38]

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.[40] Furthermore, a significant amount of the VMS kernel, layered products, and customer-developed applications were implemented in VAX MACRO assembly code.[9] To port the VAX MACRO code, the MACRO-32 compiler was created, which translated VAX MACRO to Alpha object code.[41] Digital also created a VAX to Alpha translation facility, known as the VAX Environment Software Translator (VEST) to convert VAX executables where it was not possible to recompile the code for Alpha.[42] The VAX compilers for high level languages, many of which had their own bespoke code generators,[43] were converted to use a common compiler backend named GEM.[44] Certain low-level details of the VAX architecture, such as interrupt handling and atomic queue instructions, were emulated in PALcode - which further minimized the amount of changes required to port the VMS kernel to Alpha.

The VMS port to Alpha resulted in the creation of two separate source code libraries (based on a source code management tool known as the VMS Development Environment, or VDE)[4] for VAX, and for Alpha. The Alpha code library was based on a snapshot of the VAX/VMS code base circa V5.4-2.[45] 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.[45] 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.[40]

When VMS was ported to Alpha, it was initially left as a 32-bit only operating system.[41] 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.[46] 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.[47] 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.[48]

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.[49][50]

Port to Intel Itanium
"Swoosh" logo used by HP for OpenVMS

In 2001, just prior to its acquisition by Hewlett-Packard, Compaq announced the port of OpenVMS to the Intel Itanium architecture.[51] 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.[52] The porting began in late 2001, and the first boot on took place on the 31st of January 2003.[53] 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 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.[40] Whereas the VAX and Alpha architectures were specifically designed to support the low-level needs of OpenVMS, Itanium was not. This required certain architectural dependencies of OpenVMS to be replaced, or emulated in software. Some of the changes included:

  • The Extensible Firmware Interface (EFI) is used to boot OpenVMS on the Integrity platform, taking over the role of the System Reference Manual (SRM) firmware on Alpha. Support for ACPI was also added to OpenVMS, since this is used to discover and manage hardware devices on the Integrity platform.[54]
  • For Itanium, the functionality which was implemented using PALcode for Alpha was moved into a component of the OpenVMS kernel named the Software Interrupt Services (SWIS).[55]
  • The Itanium port adopted a new calling standard based on Intel's Itanium calling convention, with extensions to support the OpenVMS Common Language Environment. Furthermore, it replaced the OpenVMS-specific executable formats used on the VAX and Alpha with the standard Executable and Linking Format (ELF) and DWARF formats.[56]
  • IEEE 754 was adopted as the default floating point format, replacing the VAX floating point format that was the default on both the VAX and Alpha architectures. For backwards compatibility, it is possible to compile code on Itanium to use the VAX floating point format, but it relies on software emulation.[57]
  • The operating system's internal structures were extended to support the 50-bit physical addressing available on Itanium, allowing 1PiB of memory to be addressed.[58] The Itanium port otherwise retained the mixed 32-bit/64-bit pointer architecture which was introduced in OpenVMS Alpha V7.0.

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

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

Port to x86-64

When VMS Software Inc. (VSI) announced that they secured the rights to develop the OpenVMS operating system from HP, they also announced their intention to port OpenVMS to the x86-64 architecture.[61] 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 8.x.

The x86-64 port is targeted for specific servers from HPE and Dell, as well as certain virtual machine hypervisors.[62] 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.[63]

The x86-64 port is built from the same source code library as the Alpha and Itanium architectures, using conditional compilation to manage the architecture-specific code needed to support the x86-64 platform.[64] As with the Alpha and Itanium ports, the x86-64 port made some changes to simplify porting and supporting OpenVMS on the new platform:

  • VSI adopted the open source LLVM compiler backend, replacing the proprietary GEM backend used in the Alpha and Itanium ports. A translator was developed to map the GEM IR to LLVM IR, allowing the existing compiler frontends to be reused. In addition, the open source Clang compiler was adopted as the officially supported C++ compiler for OpenVMS under x86-64.[65]
  • On x86-64, OpenVMS makes more extensive use of UEFI and ACPI to detect and initialize hardware on boot. As part of this, VMS is now booted from a memory disk, instead of the traditional VMS boot mechanism – which relied on "boot drivers" containing a basic implementation of the filesystem, and which was tied to specific hardware devices. The changes to the boot process necessitated the creation of a "Dump Kernel" – this is a secondary kernel which is loaded in the background at boot time, and is invoked in case OpenVMS needs to write a crash dump to disk.[66]
  • OpenVMS assumes the presence of four hardware-provided privilege levels to provide isolation between user applications, and various parts of the operating system. While x86-64 nominally provides four privilege levels, they are only equivalent to two of the privilege levels on the VAX, Alpha and Itanium. In the x86-64 port, the Software Interrupt Services (SWIS) module of the kernel is extended to emulate the missing privilege levels.[55]
  • As with the Itanium port, the calling standard for x86-64 is an extension of the platform's standard calling convention, specifically the System V AMD64 ABI. Certain characteristics of the x86-64 architecture created challenges for defining a suitable calling standard. For example, due to the small number of general purpose registers for x86-64, the MACRO-32 compiler has to store the contents of the emulated VAX registers in an in-memory "pseudo registers" structure instead of using the processor's hardware registers as is done on Alpha and Itanium.[67]

The first boot was announced on the 14th May 2019. This involved booting OpenVMS on VirtualBox, and successfully running the DIRECTORY command.[68] Later in 2019, the first "real boot" was announced - this consisted of the operating system booting in a completely standard manner, a user logging into the system, and running the DIRECTORY command.[69] In May 2020, the V9.0 Early Adopter's Kit release was made available to certain customers. This contains the full OpenVMS operating system running in a VirtualBox VM with certain limitations - most significantly, little to no layered products are available, and code can only be compiled for x86-64 using cross compilers which run on Itanium-based OpenVMS systems.[16] Following the V9.0 release, VSI has released a series of monthly updates which add additional functionality, these are designated V9.0-A, V9.0-B, etc.[6]

Major release timeline
Version Release date[70][9] End-of-life date[71] Notes
Old version, no longer maintained: X0.5 Late 1977 ? First version shipped to early VAX-11/780 customers.[29]
Old version, no longer maintained: V1.0 August 1978 ? First commercial release.
Old version, no longer maintained: V2.0 April 1980 ? VAX-11/750
Old version, no longer maintained: V3.0 April 1982 ? VAX-11/730, VAX-11/725, VAX-11/782, ASMP
Old version, no longer maintained: V4.0 September 1984 ? VAX 8600 and MicroVMS (for MicroVAX), VAXclusters
Old version, no longer maintained: V5.0 April 1988 ? VAX 6000, SMP, License Management Facility, Modular Executive
Old version, no longer maintained: V1.0 AXP November 1992 ? first OpenVMS AXP (Alpha) specific version
Old version, no longer maintained: V6.0 June 1993 ? VAX 7000 and 10000, NCSC Class C2 compliance
Old version, no longer maintained: V6.1 April 1994 ? merging of VAX and Alpha AXP version numbers
Old version, no longer maintained: V7.0 January 1996 31 March 1998 full 64-bit virtual addressing on Alpha
Old version, no longer maintained: V7.3 June 2001 31 December 2012 Final release for the VAX architecture
Old version, no longer maintained: V8.0 June 2003 December 2003 Limited availability eval for Integrity
Old version, no longer maintained: V8.2 February 2005 30 April 2014 Common Alpha and Itanium production release
Old version, no longer maintained: V8.4 June 2010 31 December 2020 Virtual machine guest under HPVM. Clusters over TCP/IP. Last release from HP.[72]
Older version, yet still maintained: V8.4-1H1 May 2015 31 December 2022 Support for "Poulson" Itanium processors, first release from VSI.[73]
Older version, yet still maintained: V8.4-2L1 September 2016 31 December 2024 OpenSSL updated to 1.0.2.[74]
January 2017 TBA First Alpha architecture release from VSI.[75]
Current stable version: V8.4-2L2 July 2017 TBA Final release for the Alpha architecture.[76]
Future release: V8.4-2L3 H1 2021 TBA Final release for the Itanium architecture.[76]
Latest preview version of a future release: V9.0 May 2020 H1 2021 x86-64 Limited Early Adopter's Kit[77]
Future release: V9.1 H1 2021 H2 2021 x86-64 General Early Adopter's Kit[78]
Future release: V9.2 H2 2021 TBA x86-64 General Release[78]
Legend:
Old version
Older version, still maintained
Latest version
Latest preview version
Future release

Architecture
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, a Command Language Interpreter which runs at an intermediate level of privilege, and utilities and run-time libraries (RTLs) which run in an unprivileged mode, but can potentially run at a higher level of privilege if authorized to do so.[79] 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:[79][80]

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

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 which runs at the executive access mode.[79]

The components of the Executive which run outside the Kernel include the Record Management Services, and certain system services such as image activation. The main distinction between the kernel and executive 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.[80] 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.[81]

The Kernel compromises 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.[79][80] In addition, other functionality such as logical name management, synchronization and system service dispatch are implemented inside the kernel.

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).[82] 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.[83] 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.[79] A CLI gets mapped into a process' private address space through execution of the LOGINOUT image, which can either be executed manually, or automatically by certain process creation system services.[48]

Due to 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 memory at supervisor access mode. This is in order to prevent accidental or malicious manipulation of the CLI's code and data structures by user mode code.[79][83]

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

User interfaces

VMS was originally designed to be used and managed interactively using Digital'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 graphical terminals connected to a server.

Command line interfaces
Main article: DIGITAL Command Language
OpenVMS Alpha V8.4-2L1, showing the DCL CLI in a terminal session

The DIGITAL Command Language has served as the primary Command Language Interpreter (CLI) of OpenVMS since the first release.[84][85][10] Other official CLIs available for VMS include the RSX-11 MCR (VAX only), and various Unix shells.[86] Digital provided tools for creating text-based user interface applications - the Form Management System (FMS) and Terminal Data Management System (TDMS), later succeeded by DECforms.[87][88][89] A lower level library, comparable to Unix curses called the Screen Management Services (SMG$) also exists.[90]

Graphical user interfaces
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

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.[91] It exposed an API called the User Interface Services (UIS).[92] It ran on a limited selection of VAX hardware.[93]
  • In 1989, DEC replaced VWS with a new X11-based windowing system named DECwindows.[94] It was first included in VAX/VMS V5.1.[95] Early versions of DECwindows featured an interface built on top of a proprietary toolkit named the X User Inteface (XUI). A layered product named UISX was provided to allow VWS/UIS applications to run on top of DECwindows.[96]
  • In 1991, DEC replaced XUI with the Motif toolkit, creating DECwindows Motif.[97][98] As a result, the Motif Window Manager became the default DECwindows interface in OpenVMS V6.0,[95] although the XUI window manager remained as an option.
  • In 1996, as part of OpenVMS V7.1,[95] DEC released the "New Desktop" interface for DECwindows Motif.[99] The New Desktop consisted of a significant subset of the Common Desktop Environment. 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[100] and Accelerated Graphics Port (AGP) graphics adapters. VMS also provides support for older graphics standards such as GKS and PHIGS.[101][102] Modern versions of DECwindows are based on X.org Server.[10]

Clustering
Main article: VMScluster

OpenVMS supports clustering (first called VAXcluster and later VMScluster), where multiple systems run their own instance of the operating system, but share disk storage, processing, a distributed lock manager, a common management and security domain, job queues and print queues, providing a single system image abstraction. The systems are connected either by proprietary specialized hardware (Cluster Interconnect) or an industry-standard Ethernet LAN. OpenVMS supports up to 96 nodes in a single cluster, and allows mixed-architecture clusters, where VAX and Alpha systems, or Alpha and Itanium systems can co-exist in a single cluster. VMS clusters allow the creation of applications which can withstand planned or unplanned outages of part of the cluster.[103][19]

File system
Main articles: Files-11 and Record Management Services

OpenVMS provides feature-rich facilities for file management. The typical user and application interface into the file system is via the Record Management Services (RMS), although applications can interface directly with the underlying file system through the QIO system services.[104] RMS supports multiple record-oriented file access methods and record formats (including a stream format where the file is treated as a stream of bytes, similar to Unix). RMS also supports remote file access via DECnet,[105] and optional support for journaling.[106]

The file systems supported by VMS are referred to as the Files-11 On-Disk Structures (ODS), which provide disk quotas, access control lists and file versioning.[107] The most significant structure levels are ODS-2, which is the original VMS file system, and ODS-5, which extended ODS-2 with support for Unicode file names, case sensitivity, hard links and symbolic links.[108] VMS is also capable of accessing files on ISO 9660 CD-ROMs and magnetic tape with ANSI tape labels.[109]

Alongside the OpenVMS Alpha V7.0 release in 1995, Digital released a log-structured file system named Spiralog which was intended as a potential successor to Files-11.[110] Spiralog shipped as an optional product, and was discontinued at the release of OpenVMS Alpha 7.2.[111] Spiralog's discontinuation was due to a variety of problems, including issues with handling full volumes.[112] The developers of Spiralog began work on a new file system in 1996, which was put on hold and later resumed by VSI in 2016 as the VMS Advanced File System (VAFS, not to be confused with Digital's AdvFS for Tru64).[113][114] VAFS no longer appears on recent roadmaps, and instead VSI have discussed porting the open source GFS2 file system to OpenVMS.[78][115] One of the major motivations for replacing the Files-11 structures is that they are limited to 2TiB volumes.[108]

Networking
Main article: DECnet

Digital's 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.[116] Modern versions of VMS support both the traditional Phase IV DECnet protocol, as well the OSI-compatible Phase V (also known as DECnet-Plus).[117] 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).[118][119] TCP/IP Services is based on a port of the BSD network stack to OpenVMS,[120] along with support for common protocols such as SSH, DHCP, FTP and SMTP. Due to the fact that the official TCP/IP stack was introduced relatively late, multiple third party TCP/IP stacks have been created for VMS. Some of these third party TCP/IP stacks remain under active development, such as TCPware and MultiNet.[121]

Digital 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.[122] PATHWORKS was based on LAN Manager and supported either DECnet or TCP/IP as a transport protocol. 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.[123]

Digital provided the Local Area Transport (LAT) protocol which allowed remote terminals and printers to be attached to a VMS system through a terminal server.[124]

Timekeeping

OpenVMS represents system time as the signed 64-bit number of 100 nanosecond intervals (that is, ten million units per second; also known as a 'clunk'[125][126]) since the epoch.[79] The epoch of OpenVMS is midnight preceding November 17, 1858, which is the start of Modified Julian Day numbering.[127] This will allow time computations up to 31-JUL-31086 02:48:05.47 before overflow occurs.[127]

While the native OpenVMS time format can range far into the future, applications based on the C runtime library will likely encounter timekeeping problems beyond January 19, 2038 due to the Year 2038 problem. Applications may also encounter the Year 10,000 problem due to fixed-length date fields.[128]

Programming

Digital (and its successor companies) provided a wide variety of programming languages for VMS. Officially supported languages on VMS, either current or historical, include:[86][129]

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.[67] Because of this, it is possible and straightforward 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.[130][131] Digital created a tool named the Structure Definition Language (SDL), which allowed data type definitions to be generated for different languages from a common definition.[132]

Digital provided a collection of software development tools as a layered product named DECset (originally named VAXset).[86] This consisted of the Language-Sensitive Editor (LSE), a version control system (the Code Management System or CMS), a build tool (the Module Management System or MMS), a static analyzer (the Source Code Analyzer or SCA), as well as testing tools (the Digital Test Manager and the Performance and Coverage Analyzer or DTM and PCA respectively).[133] In addition, a number of text editors are included in the operating system, including EDT, EVE and TECO.[134]

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.[135] A pair of lower-level debuggers, called DELTA and XDELTA, can be used to debug privileged code in additional to normal application code.[136]

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

Database management
The "Grey Wall" of VAX/VMS documentation, at Living Computers: Museum + Labs

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

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

Examples of third-party database management systems for OpenVMS include MariaDB,[145] Mimer SQL[146] and System 1032.[147]

Standard streams

In a manner similar to Unix, VMS defines several standard input and output channels[82] with these logical names:

SYS$INPUT – Standard input. Used interactively, this represents the terminal keyboard. Used in a batch file, it is batch file lines not preceded with a $ symbol, or specified as an input deck using the DECK command.

SYS$OUTPUT – Standard output. Used interactively, this is the terminal display. Used in a batch file, it outputs to the screen if the file is run interactively or to the log file when the file is run noninteractively.

SYS$ERROR – Standard error. Used interactively, this is the terminal display. In a batch file, it is the terminal display when the file is run interactively, or to the log file when the file is run noninteractively, or in the special case of RUN /DETACH, to the output file or device specified with the /ERROR= parameter.

SYS$COMMAND – Does not have a direct analogue in the Unix model. Used interactively, it will read from the terminal. Used in a batch file when run interactively, it will read from the terminal. Used in a batch file run noninteractively, it will read from the SYS$INPUT stream (if one is defined), otherwise it will read nothing and return end of file. /dev/tty on Unix is similar to SYS$COMMAND in interactive sessions, but is not available in non-interactive sessions.

Security

OpenVMS provides various security features and mechanisms, including security identifiers, resource identifiers, subsystem identifiers, ACLs, and detailed security auditing and alarms. Specific versions evaluated at DoD NCSC Class C2 and, with the SEVMS security enhanced services support, at NCSC Class B1, per the NCSC Rainbow Series.[148] OpenVMS also holds an ITSEC E3 rating (see NCSC and Common Criteria).[149][150] Passwords are hashed using the Purdy Polynomial.

Vulnerabilities

A 33-year-old vulnerability in VAX/VMS and OpenVMS 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 bypass system security and take full control of the system. 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 access to the privileges of the images that it requests to be loaded into the DCL process when the image is interrupted.[151] The buffer overflow bug allowed shellcode to be executed with the privileges of an interrupted image, and thus allowing an attacker to carry out a privilege escalation attack.[152]

Cross platform compatibility

VAX/VMS originally included an RSX-11M compatibility layer named the RSX Application Migration Executive (AME) which allowed user mode RSX-11M software to be run unmodified on top of VMS.[85] This relied on the PDP-11 compatibility mode implemented in the VAX-11 processors.[153] The RSX AME played an important role on early versions of VAX/VMS, which used re-used certain RSX-11M user space utilities before native VAX versions had been developed.[9] This was discontinued in VAX/VMS V3.0 when all compatibility mode utilities were replaced with native implementations, and RSX AME was removed from the base system.[154] At this point, RSX AME was replaced with an optional layered product on VAX named VAX-11 RSX, which relied on software emulation to run PDP-11 code on newer VAX processors.[153] A VAX port of the RTEM compatibility layer for RT-11 applications was also available from Digital.[155]

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

Digital licensed SoftPC (and later SoftWindows), and sold it as a layered product for both the VAX and Alpha architectures, allowing Windows and DOS applications to run on top of VMS.[160][161]

Open source applications

Some of the open source applications which have been ported to OpenVMS include:[62][129]

There are a number of community projects to port open source software to VMS, include VMS-Ports[162] and GNV (GNU's Not VMS).[163]

Hobbyist programs

Despite being a proprietary commercial operating system, 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.[164][165] Since then, several companies producing OpenVMS software have made their products available under the same terms, such as Process Software[166] and MVP Systems.[167] In 2012, HP staff took over the administration of the hobbyist licences.[168] Registration was simplified, and software kits for operating system and layered products were made available on request via FTP download (previously it had to be shipped on CD).[169]

In March 2020, HPE announced that they were concluding the OpenVMS Hobbyist license program.[170] This was followed by an announcement from VSI in April 2020 that VSI they would launch a Community License Program (CLP) to replace the old Hobbyist Program.[171] 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 available later as a more stable version is released for this architecture.[172] 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.[173]

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 a strong degree of backwards compatibility with VMS applications while also supporting Ultrix applications on top of the same kernel.[174] MICA was ultimately cancelled along with the rest of the PRISM platform, leading Dave Cutler to leave Digital for Microsoft. At Microsoft, Cutler led the creation of the Windows NT operating system, which was heavily inspired by the architecture of MICA.[175] 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.[176] This lineage is made clear in Cutler's foreword to "Inside Windows NT" by Helen Custer.[177]

FreeVMS was an attempt to develop an open source operating system following VMS conventions.[178] As of April 2019 the associated mailing list had been totally inactive for two years and shown limited activity for some years prior to that.[179] FreeVMS supported the x86-64 architecture using an L4 microkernel.[178]

See also

References
  1. "HP gives OpenVMS new life". Computerworld. July 31, 2014.
  2. Stephen Hoffman (June 6, 2000). "C bashing (was Re: VMS File Caching Futures)". Newsgroup: comp.os.vms.
  3. "2.7 In what language is OpenVMS written?". The OpenVMS Frequently Asked Questions (FAQ). Hewlett Packard Enterprise. Archived from the original on 2018-08-10.
  4. "Access to OpenVMS Source Code?". HP OpenVMS Systems ask the wizard. September 2, 1999. Archived from the original on 2017-10-28.
  5. "VMS Software, Inc. Launches VSI OpenVMS Alpha V8.4-2L2 Performance Release for Alpha". vmssoftware.com. 2017-07-10. Retrieved 2020-09-23.
  6. "State of the Port". vmssoftware.com. Retrieved 2020-12-14.
  7. "Japanese OpenVMS OS (JVMS)". vmssoftware.com. Retrieved 2021-02-05.
  8. Michael M. T. Yau (1993). "Supporting the Chinese, Japanese, and Korean Languages in the openVMS Operating System" (PDF). Digital Technical Journal. 5 (3).
  9. "OpenVMS at 20 Nothing stops it". October 1997. Archived from the original (PDF) on 2017-01-22.
  10. "Software Product Description and QuickSpecs - VSI OpenVMS Version 8.4-2L1 for Integrity servers" (PDF). VMS Software Inc. July 2019. Retrieved 2021-01-02.
  11. "VAX-11/780 Hardware Handbook" (PDF). ece.cmu.edu. 1979. Retrieved 2020-12-16.
  12. Patrick Thibodeau (June 11, 2013). "OpenVMS, R.I.P. 1977-2020?". Computerworld.
  13. Tom Merritt (2012). Chronology of Tech History. p. 104. ISBN 978-1300253075.
  14. "VAX 11/780 - OLD-COMPUTERS.COM : HISTORY / detailed info". Retrieved 2020-04-25.
  15. "VSI Products". VSI.
  16. "Rollout of V9.0 and Beyond" (PDF). 19 May 2020.
  17. "HP hands off OpenVMS development to VSI". Tech Times. August 1, 2014. Retrieved 2016-01-29.
  18. "VMS Software, Inc. Named Exclusive Developer of Future Versions of OpenVMS Operating System" (Press release). Retrieved October 27, 2017.
  19. "VSI Products - Clusters".
  20. "Cluster Uptime". 2003-11-28. Archived from the original on 2012-02-29. Retrieved 2020-12-20.
  21. "Commerzbank Survives 9/11 with OpenVMS Clusters" (PDF). July 2009. Retrieved 2020-08-14.
  22. "February 2018 Business & Technical Update" (PDF). February 2018. Retrieved 2020-08-14.
  23. "VSI Business & New Products Update – April 9, 2019" (PDF). April 2019. Retrieved 2020-08-14.
  24. Drew Robb (2004-11-01). "OpenVMS survives and thrives". computerworld.com. Retrieved 2020-12-31.
  25. Tao Ai Lei (1998-05-30). "Digital tries to salvage OpenVMS". computerworld.co.nz. Retrieved 2020-12-31.
  26. "Hello from....well what used to be SpitBrook". openvmshobbyist.com. 2007-02-27. Retrieved 2021-01-24.
  27. "Computer system VAX/VMS". altiq.se. Retrieved 2021-01-24.
  28. "Gordon Bell Biography". research.microsoft.com.
  29. Stephen Hoffman (September 2006). "What is OpenVMS? What is its history?". hoffmanlabs.com. Retrieved 2021-01-03.
  30. Bob McCormick (1989-01-11). "DECUServe WORKSTATIONS Conference 8". home.iae.nl. Retrieved 2020-12-22.
  31. "Office Archaeology". blog.nozell.com. 2004-02-24. Retrieved 2020-12-22.
  32. "openVMS pages of proGIS germany". vaxarchive.org. Retrieved 2020-12-22.
  33. "Digital Introduces First Generation of OpenVMS Alpha-Ready Systems". Digital. 1992-07-15. Retrieved 2021-01-25.
  34. "OpenVMS Definition from PC Magazine Encyclopedia".
  35. Arne Vajhøj (1999-11-29). "OpenVMS FAQ - What is the difference between VMS and OpenVMS?". vaxmacro.de. Retrieved 2021-01-25.
  36. "History of the Vernon the VMS shark". vaxination.ca. Retrieved 2021-01-24.
  37. "EV-4 (1992)". 2008-02-24.
  38. Comerford, R. (July 1992). "How DEC developed Alpha". IEEE Spectrum. 29 (7): 26–31. doi:10.1109/6.144508.
  39. "Managing Technological Leaps: A study of DEC's Alpha Design Team" (PDF). April 1993.
  40. Clair Grant (June 2005). "Porting OpenVMS to HP Integrity Servers" (PDF). OpenVMS Technical Journal. 6.
  41. 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).
  42. "OpenVMS Compatibility Between VAX and Alpha" (PDF). itec.suny.edu. May 1995. Retrieved 2020-12-21.
  43. "VAX VMS going forward". comp.os.vms.narkive.com. 2020-07-17. Retrieved 2021-01-22.
  44. David S. Blickstein; Peter W. Craig; Caroline S. Davidson; R. Neil Fairnan,Jr.; Kent D. Glossop; Richard B. Grove; Steven O. Hobbs; William B. Noyce (1992). "The GEM Optimizing Compiler System" (PDF). Digital Technical Journal. 4 (4).
  45. "OpenVMS Compatibility Between VAX and Alpha". May 1995.
  46. "Extending OpenVMS for 64-bit Addressable Virtual Memory" (PDF). Digital Technical Journal. 8 (2): 57–71. 1996. S2CID 9618620.
  47. "The OpenVMS Mixed Pointer Size Environment" (PDF). Digital Technical Journal. 8 (2): 72–82. 1996. S2CID 14874367.
  48. "VSI OpenVMS Programming Concepts Manual, Vol. 1" (PDF). vmssoftware.com. April 2020. Retrieved 2020-10-07.
  49. "HP OpenVMS Alpha Partitioning and Galaxy Guide". September 2003.
  50. James Niccolai (1998-10-14). "Compaq details strategy for OpenVMS". Australian Reseller News. Retrieved 2021-01-14.
  51. "Compaq OpenVMS Times" (PDF). January 2002. Archived from the original (PDF) on March 2, 2006.
  52. Andrew Orlowski (2001-06-25). "Farewell then, Alpha – Hello, Compaq the Box Shifter". theregister.com. Retrieved 2020-12-21.
  53. Sue Skonetski (2003-01-31). "OpenVMS Boots on Itanium on Friday Jan 31". groups.google.com. Retrieved 2020-12-21.
  54. Thomas Siebold (2005). "OpenVMS Integrity Boot Environment" (PDF). decus.de. Retrieved 2020-12-21.
  55. "Re-architecting SWIS for X86-64". 8 October 2017.
  56. Gaitan D’Antoni (2005). "Porting OpenVMS Applications to Itanium" (PDF). hp-user-society.de. Retrieved 2020-12-21.
  57. "OpenVMS floating-point arithmetic on the Intel Itanium architecture" (PDF). decus.de. 2003. Retrieved 2020-12-21.
  58. "Upgrading Privileged-Code Applications on OpenVMS Alpha and OpenVMS I64 Systems". hpe.com. January 2005. Retrieved 2020-12-21.
  59. Thomas Siebold (2005). "OpenVMS Moving Custom Code" (PDF). decus.de. Retrieved 2020-12-21.
  60. Paul Lacombe (2005). "HP OpenVMS Strategy and Futures" (PDF). de.openvms.org. Retrieved 2020-12-21.
  61. "VMS Software, Inc. Named Exclusive Developer of Future Versions of OpenVMS Operating System". 31 July 2014. Archived from the original on 10 August 2014.
  62. "OpenVMS Rolling Roadmap" (PDF). VMS Software. December 2019.
  63. "VSI V9.0 Q&A". 16 June 2020.
  64. "State of the Port to x86_64 April 2017" (PDF). 3 April 2017. Archived (PDF) from the original on 5 November 2019.
  65. "2017 LLVM Developers' Meeting: J. Reagan "Porting OpenVMS using LLVM"". 31 October 2017.
  66. "State of the Port to x86_64 January 2017" (PDF). 6 January 2017. Archived (PDF) from the original on 5 November 2019.
  67. "VSI OpenVMS Calling Standard" (PDF). May 2020.
  68. "VMS Software Inc. Announces First Boot on x86 Architecture". 14 May 2019.
  69. "State of the Port". 2 November 2019. Archived from the original on 2 November 2019.
  70. "HP OpenVMS Systems - OpenVMS Release History". June 21, 2010. Archived from the original on October 7, 2018.
  71. "HP OpenVMS Systems - Supported Software Versions - January 2014". Archived from the original on October 14, 2018.
  72. "HP OpenVMS Systems - OpenVMS Version 8.4". Archived from the original on September 2, 2010.
  73. "VMS Software, Inc. Launches New Version of OpenVMS Operating System Worldwide" (PDF) (Press release). June 1, 2015.
  74. "VMS Software, Inc. Launches New Version 8.4-2L1 of OpenVMS Operating System Worldwide" (Press release). VMS Software, Inc. March 22, 2016.
  75. "VMS SOFTWARE, INC. LAUNCHES VSI OPENVMS ALPHA V8.4-2L1 FOR ALPHA HARDWARE" (Press release). VMS Software, Inc. January 27, 2017.
  76. "Roadmap". vmssoftware.com. September 2020. Archived from the original on 2020-09-27. Retrieved 2020-09-23.
  77. "OpenVMS for x86 V9.0 EAK goes to first customer on May 15, 2020". April 24, 2020. Archived from the original on April 25, 2020.
  78. "VSI OpenVMS Software Roadmap 2020" (PDF). September 2020. Retrieved 2020-09-23.
  79. Ruth E. Goldenberg; Lawrence J. Kenah; Denise E. Dumas (1991). VAX/VMS Internals and Data Structures, Version 5.2. Digital Press. ISBN 978-1555580599.
  80. Hunter Goatley; Edward A. Heinrich. "Writing VMS Privileged Code Part I: The Fundamentals, Part 1". hunter.goatley.com. Retrieved 2021-01-31.
  81. Paul A. Karger; Mary Ellen Zurko; Douglas W. Benin; Andrew H. Mason; Clifford E. Kahnh (7–9 May 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 2021-01-31.CS1 maint: date format (link)
  82. "OpenVMS User's Manual" (PDF). vmssoftware.com. July 2020. Chapter 14, Advanced Programming with DCL. Retrieved 2020-09-13.
  83. Simon Clubley (2017-07-03). "How dangerous is it to be able to get into DCL supervisor mode?". comp.os.vms.narkive.com. Retrieved 2021-02-01.
  84. Stephen Hoffman; Paul Anagnostopoulos (1999). Writing Real Programs in DCL, second edition. ISBN 1-55558-191-9.
  85. "Software Product Description - VAX/VMS Operating System, Version 1.0" (PDF). September 1978.
  86. "VAX/VMS Software Language and Tools Handbook" (PDF). bitsavers.org. 1985. Retrieved 2020-12-31.
  87. "Software Product Description HP DECforms for OpenVMS, Version 4.0" (PDF). hpe.com. August 2006. Retrieved 2021-01-01.
  88. "Software Product Description HP FMS for OpenVMS, Version 2.5" (PDF). hpe.com. January 2005. Retrieved 2021-01-01.
  89. "Compaq TDMS for OpenVMS VAX, Version 1.9B" (PDF). hpe.com. July 2002. Retrieved 2021-01-01.
  90. "OpenVMS RTL Screen Management (SMG$) Manual". hpe.com. 2001. Retrieved 2021-01-01.
  91. "Digital Technical Journal Vol. 1 No. 2" (PDF).
  92. "MicroVMS Workstation Graphics Programming Guide" (PDF).
  93. "comp.os.vms - Dec VWS Internals".
  94. "Digital Technical Journal Vol. 2 No. 3" (PDF).
  95. "(Open)VMS(/ VAX), Version overview".
  96. "Migrating VWS/UIS Applications to DECwindows?". HP OpenVMS ask the wizard. November 9, 2004. Archived from the original on September 15, 2018.
  97. "Using DECwindows Motif for OpenVMS" (PDF). vmssoftware.com. October 2019. Retrieved 2020-10-21.
  98. 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.
  99. "Getting Started With the New Desktop".
  100. OpenGL Frequently Asked Questions (FAQ) [1/3]. Faqs.org. Retrieved on 2013-07-17.
  101. "Software Product Description VSI Graphical Kernel System" (PDF). vmssoftware.com. 2017. Retrieved 2021-01-02.
  102. "Software Product Description DEC PHIGS Version 3.1 for OpenVMS VAX" (PDF). hpe.com. April 1995. Retrieved 2021-01-02.
  103. "VSI OpenVMS Cluster Systems" (PDF). VSI. August 2019. Retrieved 2021-01-13.
  104. "VSI OpenVMS I/O User's Reference Manual" (PDF). VSI. August 2019. Retrieved 2021-01-13.
  105. "OpenVMS Record Management Services Reference Manual". June 2002.
  106. "RMS Journaling". VSI. Retrieved 2021-01-13.
  107. Kirby McCoy (1990). VMS File System Internals. Bedford, Mass.: Digital Press. ISBN 1-55558-056-4.
  108. "Andy Goldstein on Files-11, the OpenVMS File Systems". VSI Official Channel. 2019-07-25. Retrieved 2021-01-03.
  109. "VSI OpenVMS Guide to OpenVMS File Applications" (PDF). VSI. 2019-07-23. Retrieved 2021-01-13.
  110. James E. Johnson; William A. Laing (1996). "Spiralog Log-Structured File System" (PDF). Digital Technical Journal. 8 (2).
  111. "OpenVMS Version 7.2 Release Notes". Compaq. January 1999. Retrieved 2021-01-13.
  112. "Why was Spiralog retired?". community.hpe.com. 2006-01-10. Retrieved 2021-01-13.
  113. Andy Goldstein; Robert A. Brooks; Camiel Vanderhoeven. "A detailed look at the on-disk structure of the VMS Advanced File System (VAFS)" (PDF). VSI. Retrieved 2021-01-13.
  114. "Andy Goldstein on the New File System for OpenVMS v.9.0". VSI. 2019-05-08. Retrieved 2021-01-14.
  115. "VSI OpenVMS Roadmap: V9.2 is x86-64 only". 2020-09-23. Retrieved 2021-01-14.
  116. "DECnet for OpenVMS Guide to Networking" (PDF). VSI. August 2020. Retrieved 2021-01-14.
  117. "VSI Products - DECnet". VSI. Retrieved 2021-01-14.
  118. "VMS/ULTRIX System Manager's Guide" (PDF). Digital. September 1990. Retrieved 2021-01-21.
  119. "VSI OpenVMS TCP/IP User's Guide" (PDF). VSI. August 2019. Retrieved 2021-01-14.
  120. Robert Rappaport; Yanick Pouffary; Steve Lieman; Mary J. Marotta (2004). "Parallelism and Performance in the OpenVMS TCP/IP Kernel". OpenVMS Technical Journal. 4.
  121. Neil Rieck (2020-07-20). "OpenVMS Notes: TCPware - MultiNet Tips". Retrieved 2021-01-21.
  122. Alan Abrahams; David A. Low (1992). "An Overview of the PATHWORKS Product Family" (PDF). Digital Technical Journal. 4 (1).
  123. Andy Goldstein (2005). "Samba and OpenVMS" (PDF). de.openvms.org. Retrieved 2021-01-01.
  124. "Local Area Transport Network Concepts" (PDF). DEC. June 1988. Retrieved 2021-01-14.
  125. "README file for clunk routines". November 6, 1987.
  126. "The Wombat Examiner, Vol. 3, No. 1". February 1981.
  127. "Why is Wednesday, November 17, 1858 the base time for OpenVMS (VAX VMS)?". Stanford University. 24 July 1997. Archived from the original on 24 July 1997. Retrieved 8 January 2020.
  128. Detailed information on time and timekeeping, and on daylight saving time and time zone differential factor operations, is contained in the OpenVMS FAQ.
  129. "VSI List of Products". VMS Software.
  130. "OpenVMS Programming Environment Manual". March 1994. 7.1 Common Language Environment.
  131. "VSI OpenVMS Programming Concepts Manual, Volume II" (PDF). VSI. March 2020. Retrieved 2021-01-13.
  132. "SDL, LANGUAGE, Data Structure/Interface Definition Language". digiater.nl. November 1996. Retrieved 2021-01-03.
  133. "DECset". vmssoftware.com. Retrieved 2021-01-02.
  134. "VSI OpenVMS DCL Dictionary: A-M" (PDF). vmssoftware.com. April 2020. Retrieved 2021-01-02.
  135. "VSI OpenVMS Debugger Manual" (PDF). vmssoftware.com. July 2020. Retrieved 2020-12-31.
  136. "VSI OpenVMS Delta/XDelta Debugger Manual" (PDF). vmssoftware.com. August 2019. Retrieved 2020-12-31.
  137. "VMS IDE". marketplace.visualstudio.com. Retrieved 2021-01-02.
  138. "VAX/VMS Software Information Management Handbook" (PDF). Digital. 1985. Retrieved 2021-01-24.
  139. Ian Smith (2004). "Rdb's First 20 Years: Memories and Highlights" (PDF). Archived from the original (PDF) on 2005-11-03. Retrieved 2021-01-24.
  140. "Compaq ACMS for OpenVMS Getting Started". Compaq. December 1999. Retrieved 2021-01-24.
  141. "Building Dependable Systems: The OpenVMS Approach" (PDF). Digital. March 1994. Retrieved 2021-01-24.
  142. "Cover Letter for DECADMIRE V2.1 MUP Kit - DECADMIRE V2.1A". Digital. 1995. Retrieved 2021-01-24.
  143. Kevin Duffy; Philippe Vigier (2004). "Oracle Rdb Status and Direction" (PDF). Retrieved 2021-01-24.
  144. Larry Goelz; John Paladino (1999-05-31). "Cover Letter re DSM". Compq. Retrieved 2021-01-24.
  145. Neil Rieck (2020-06-29). "OpenmVMS Notes MySQL and MariaDB". Retrieved 2021-01-24.
  146. Bengt Gunne (2017). "Mimer SQL on OpenVMS Present and Future" (PDF). Retrieved 2021-01-24.
  147. "Rocket Software System 1032". Rocket Software. Retrieved 2021-01-24.
  148. National Computer Security Center (NCSC) Trusted Product Evaluation List (TPEL)
  149. "VSI OpenVMS Guide to System Security" (PDF). VSI. August 2019. Retrieved 2021-01-13.
  150. "OpenVMS Guide to System Security - Appendix C".
  151. 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.
  152. John Leyden (2018-02-06). "Ghost in the DCL shell: OpenVMS, touted as ultra reliable, had a local root hole for 30 years". theregister.com. Retrieved 2021-01-13.
  153. "VAX-11 RSX Software Product Description" (PDF). Digital. September 1985. Retrieved 2020-12-31.
  154. "a simple question: what the h*ll is MCR?". comp.os.vms.narkive.com. 2004-09-14. Retrieved 2020-12-31.
  155. "VAX-11 RTEM RELEASE NOTES". Digital. July 1986. Retrieved 2021-01-19.
  156. Digital Equipment Corporation (1994). Software Product Description - POSIX for OpenVMS 2.0.
  157. "OpenVMS Alpha Version 7.3-1 New Features and Documentation Overview Begin Index". June 2002.
  158. "VSI Products - GNV". Retrieved 2020-08-19.
  159. "ϕnix: a Unix emulator for VAX/VMS" (PDF). 1987-08-10. Archived from the original (PDF) on 2004-01-22.
  160. "DEC SoftPC User's Guide for the VMS Operating System". Digital. May 1993. Retrieved 2021-01-01.
  161. "Software Product Description DEC Softwindows/SoftPC for OpenVMS AXP, Version 5.0". Digital. November 1994. Retrieved 2021-01-01.
  162. "vms-ports". Retrieved 2020-08-20.
  163. "GNU for VMS". Retrieved 2020-08-20.
  164. "OpenVMS Hobbyist Program".
  165. "OpenVMS News & Discussion". openvms.org. Archived from the original on 2015-03-21.
  166. "Hobbyist Program". Process Software. Retrieved 2020-04-24.
  167. "MVP Systems - The OpenVMS Hobbyist Program". Archived from the original on January 6, 2009.
  168. "HP Bringing the Hobbyist Program In-House". openvmshobbyist.com. 2012-01-25. Retrieved 2021-01-01.
  169. "The new OpenVMS Hobbyist license registration is in place!". openvmshobbyist.com. 2012-01-27. Retrieved 2021-01-01.
  170. "HPE sets end date for hobbyist licenses for OpenVMS".
  171. "VMS Software Announces Community License".
  172. "VMS Software Community License Available". 2020-07-28.
  173. "VSI Announces Community License Updates".
  174. Catherine Richardson; Terry Morris; Rockie Morgan; Reid Brown; Donna Meikle (March 1987). "MICA Software Business Plan" (PDF). bitsavers.org. Retrieved 2021-01-04.
  175. 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 2021-01-04.
  176. Mark Russinovich (1998-10-30). "Windows NT and VMS: The Rest of the Story". itprotoday.com. Retrieved 2021-01-04.
  177. "OpenVMS on IA-32 ?".
  178. "FreeVMS official web page". Archived from the original on September 8, 2018.
  179. "The FreeVMS Archives". Archived from the original on 10 April 2019.

Further reading
  • Roland Hughes (December 2006). The Minimum You Need to Know to Be an OpenVMS Application Developer. ISBN 978-0-9770866-0-3.
  • Roland Hughes. The Minimum You Need to Know About Java on OpenVMS, Volume 1. ISBN 978-0-9770866-1-0. Archived from the original on January 15, 2009.
  • Roland Hughes. The Minimum You Need to Know About Service Oriented Architecture. ISBN 978-0-9770866-6-5. Archived from the original on January 15, 2009.
  • Getting Started with OpenVMS, Michael D. Duffy, ISBN 1-55558-279-6
  • Getting Started with OpenVMS System Management, 2nd Edition, David Donald Miller, Stephen Hoffman, Lawrence Baldwin, ISBN 1-55558-243-5
  • Introduction to OpenVMS, 5th Edition, Lesley Ogilvie Rice, ISBN 1-55558-194-3
  • Introduction to OpenVMS, David W Bynon, ISBN 1-878956-61-2
  • OpenVMS Alpha Internals and Data Structures: Memory Management, Ruth Goldenberg, ISBN 1-55558-159-5
  • OpenVMS Alpha Internals and Data Structures : Scheduling and Process Control : Version 7.0, Ruth Goldenberg, Saro Saravanan, Denise Dumas, ISBN 1-55558-156-0
  • OpenVMS Performance Management, Joginder Sethi, ISBN 1-55558-126-9
  • OpenVMS System Management Guide, Lawrence Baldwin, ISBN 1-55558-143-9
  • The hitchhiker's guide to VMS : an unsupported-undocumented-can-go-away-at-any-time feature of VMS, Bruce Ellis, ISBN 1-878956-00-0
  • The OpenVMS User's Guide, Second Edition, Patrick Holmay, ISBN 1-55558-203-6
  • Using DECwindows Motif for OpenVMS, Margie Sherlock, ISBN 1-55558-114-5
  • VAX/VMS Internals and Data Structures: Version 5.2 ("IDSM"), Ruth Goldenberg, Saro Saravanan, Denise Dumas, ISBN 1-55558-059-9
  • Writing OpenVMS Alpha Device Drivers in C, Margie Sherlock, Leonard Szubowicz, ISBN 1-55558-133-1
  • Writing Real Programs in DCL, second edition, Stephen Hoffman, Paul Anagnostopoulos, ISBN 1-55558-191-9
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.