OpenVMS explained

OpenVMS
Logo Size:250px
Developer:VMS Software Inc (VSI)[1] (previously Digital Equipment Corporation, Compaq, Hewlett-Packard)
Source Model:Closed-source with open-source components. Formerly source available[2]
Kernel Type:Monolithic kernel with loadable modules
Supported Platforms:VAX, Alpha, Itanium, x86-64
Ui:DCL CLI and DECwindows GUI
Released:Announced:
V1.0 /
Latest Release Version:V9.2-2
Latest Release Date:[3]
Latest Preview Version:E9.2-3
Marketing Target:Servers (historically Minicomputers, Workstations)
Programmed In:Primarily C, BLISS, VAX MACRO, DCL.[4] Other languages also used.[5]
Language:English, Japanese.[6] Historical support for Chinese (both Traditional and Simplified characters), Korean, Thai.[7]
Updatemodel:Concurrent upgrades,
rolling upgrades
Package Manager:PCSI and VMSINSTAL
Working State:Current
License:Proprietary
Influenced By:RSX-11M
Influenced:VAXELN, MICA, Windows NT

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

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

History

Origin and name changes

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.[25] The Star and Starlet projects culminated in the VAX-11/780 computer and the VAX/VMS operating system. The Starlet project's code name survives in VMS in the name of several of the system libraries, including STARLET.OLB and STARLET.MLB. VMS was mostly written in VAX MACRO with some components written in BLISS.[8]

One of the original goals for VMS was backward compatibility with DEC's existing RSX-11M operating system.[8] Prior to the V3.0 release, VAX/VMS included a compatibility layer named the RSX Application Migration Executive (RSX AME), which allowed user-mode RSX-11M software to be run unmodified on top of VMS. The RSX AME played an important role on early versions of VAX/VMS, which used certain RSX-11M user-mode utilities before native VAX versions had been developed.[8] By the V3.0 release, all compatibility-mode utilities were replaced with native implementations.[26] In VAX/VMS V4.0, RSX AME was removed from the base system, and replaced with an optional layered product named VAX-11 RSX.[27]

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.[40] In July 1992,[41] DEC renamed VAX/VMS to OpenVMS as an indication of its support of open systems industry standards such as POSIX and Unix compatibility,[42] 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.[43]

Port to Alpha

During the 1980s, DEC planned to replace the VAX platform and the VMS operating system with the PRISM architecture and the MICA operating system.[44] 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.[45] After a number of failed attempts to design a faster VAX-compatible processor, the group demonstrated the feasibility of porting VMS and its applications to a RISC architecture based on PRISM. This led to the creation of the Alpha architecture.[46] 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.[47] [48]

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.[49] Furthermore, a significant amount of the VMS kernel, layered products, and customer-developed applications were implemented in VAX MACRO assembly code. Some of the changes needed to decouple VMS from the VAX architecture included the creation of the MACRO-32 compiler, which treated VAX MACRO as a high-level language, and compiled it to Alpha object code,[50] 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.[51] The Alpha code library was based on a snapshot of the VAX/VMS code base circa V5.4-2. 1992 saw the release of the first version of OpenVMS for Alpha AXP systems, designated OpenVMS AXP V1.0. In 1994, with the release of OpenVMS V6.1, feature (and version number) parity between the VAX and Alpha variants was achieved; this was the so-called Functional Equivalence release.[52] The decision to use the 1.x version numbering stream for the pre-production quality releases of OpenVMS AXP confused some customers, and was not repeated in the subsequent ports of OpenVMS to new platforms.

When VMS was ported to Alpha, it was initially left as a 32-bit only operating system. This was done to ensure backwards compatibility with software written for the 32-bit VAX. 64-bit addressing was first added for Alpha in the V7.0 release.[53] 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.[54] 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.[55]

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.[56] [57]

Port to Intel Itanium

In 2001, prior to its acquisition by Hewlett-Packard, Compaq announced the port of OpenVMS to the Intel Itanium architecture.[58] 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.[59] The porting began in late 2001, and the first boot on took place on January 31, 2003.[60] 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. 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.[61]

The Itanium port was accomplished using source code maintained in common within the OpenVMS Alpha source code library, with the addition of conditional code and additional modules where changes specific to Itanium were required. This required certain architectural dependencies of OpenVMS to be replaced, or emulated in software. Some of the changes included using the Extensible Firmware Interface (EFI) to boot the operating system,[62] reimplementing the functionality previously provided by Alpha PALcode inside the kernel, using new executable file formats (Executable and Linkable Format and DWARF),[63] and adopting IEEE 754 as the default floating point format.[64]

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

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

Port to x86-64

When VMS Software Inc. (VSI) announced that they had secured the rights to develop the OpenVMS operating system from HP, they also announced their intention to port OpenVMS to the x86-64 architecture.[67] 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.[68] 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.[69] In 2021, the x86-64 port was demonstrated running on an Intel Atom-based single-board computer.[70]

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

The first boot was announced on May 14, 2019. This involved booting OpenVMS on VirtualBox, and successfully running the [[Directory (OpenVMS command)|DIRECTORY]] command.[74] 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.[75] 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.[76] In June 2021, VSI released the V9.1 Field Test, making it available to VSI's customers and partners.[77] 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.[78]

Influence

During the 1980s, the MICA operating system for the PRISM architecture was intended to be the eventual successor to VMS. MICA was designed to maintain backwards compatibility with VMS applications while also supporting Ultrix applications on top of the same kernel.[79] 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.[80] 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.[81]

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

Architecture

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

These VAX architecture mechanisms are implemented on Alpha, Itanium and x86-64 by either mapping to corresponding hardware mechanisms on those architectures, or through emulation (via PALcode on Alpha, or in software on Itanium and x86-64).

Executive and Kernel

The OpenVMS Executive comprises the privileged code and data structures which reside in the system space. The Executive is further subdivided between the Kernel, which consists of the code which runs at the kernel access mode, and the less-privileged code outside of the Kernel which runs at the executive access mode.

The components of the Executive which run at executive access mode include the Record Management Services, and certain system services such as image activation. The main distinction between the kernel and executive access modes is that most of the operating system's core data structures can be read from executive mode, but require kernel mode to be written to. Code running at executive mode can switch to kernel mode at will, meaning that the barrier between the kernel and executive modes is intended as a safeguard against accidental corruption as opposed to a security mechanism.[87]

The Kernel comprises the operating system's core data structures (e.g. page tables, the I/O database and scheduling data), and the routines which operate on these structures. The Kernel is typically described as having three major subsystems: I/O, Process and Time Management, Memory Management. In addition, other functionality such as logical name management, synchronization and system service dispatch are implemented inside the Kernel.

OpenVMS allows user-mode code with suitable privileges to switch to executive or kernel mode using the $CMEXEC and $CMKRNL system services, respectively.[88] 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.[89]

File system

See main article: Files-11 and Record Management Services. 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.[90] 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.[91] VMS is also capable of accessing files on ISO 9660 CD-ROMs and magnetic tape with ANSI tape labels.[92]

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

Command Language Interpreter

An OpenVMS Command Language Interpreter (CLI) implements a command-line interface for OpenVMS, responsible for executing individual commands and command procedures (equivalent to shell scripts or batch files).[96] 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.[97] Whereas a Unix shell will typically run executables by creating a separate process using fork-exec, an OpenVMS CLI will typically load the executable image into the same process, transfer control to the image, and ensure that control is transferred back to CLI once the image has exited and that the process is returned to its original state.

Because the CLI is loaded into the same address space as user code, and the CLI is responsible for invoking image activation and image rundown, the CLI is mapped into the process address space at supervisor access mode, a higher level of privilege than most user code. This is in order to prevent accidental or malicious manipulation of the CLI's code and data structures by user-mode code.[85]

Features

Clustering

See main article: VMScluster. 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.[98] 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.[99] OpenVMS clusters allow applications to function during planned or unplanned outages.[100] Planned outages include hardware and software upgrades.[101]

Networking

See main article: DECnet.

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.[102] VAX/VMS V1.0 featured support for DECnet Phase II,[103] 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).[104] 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).[105] [106] TCP/IP Services is based on a port of the BSD network stack to OpenVMS,[107] 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.[108] 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.[109]

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

Programming

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

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

Development tools

DEC provided a collection of software development tools in a layered product named DECset (originally named VAXset). This consisted of the following tools:[116]

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

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

Database management

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

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

Examples of third-party database management systems for OpenVMS include MariaDB,[128] Mimer SQL[129] (Itanium and x86-64[130]), and System 1032.[131]

User interfaces

VMS was originally designed to be used and managed interactively using DEC's text-based video terminals such as the VT100, or hardcopy terminals such as the DECwriter series. Since the introduction of the VAXstation line in 1984, VMS has optionally supported graphical user interfaces for use with workstations or X terminals such as the VT1000 series.

Text-based user interfaces

See main article: DIGITAL Command Language.

The DIGITAL Command Language (DCL) has served as the primary command language interpreter (CLI) of OpenVMS since the first release.[132] [133] Other official CLIs available for VMS include the RSX-11 Monitor Console Routine (MCR) (VAX only), and various Unix shells. DEC provided tools for creating text-based user interface applications – the Form Management System (FMS) and Terminal Data Management System (TDMS), later succeeded by DECforms.[134] [135] [136] A lower level interface named Screen Management Services (SMG$), comparable to Unix curses, also exists.[137]

Graphical user interfaces

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[148] and Accelerated Graphics Port (AGP) graphics adapters. VMS also provides support for older graphics standards such as GKS and PHIGS.[149] [150] Modern versions of DECwindows are based on X.Org Server.

Security

OpenVMS provides various security features and mechanisms, including security identifiers, resource identifiers, subsystem identifiers, ACLs, intrusion detection and detailed security auditing and alarms.[151] Specific versions evaluated at Trusted Computer System Evaluation Criteria Class C2 and, with the SEVMS security enhanced release at Class B1.[152] OpenVMS also holds an ITSEC E3 rating (see NCSC and Common Criteria).[153] Passwords are hashed using the Purdy Polynomial.

Vulnerabilities

POSIX compatibility

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

Hobbyist programs

In 1997, OpenVMS and a number of layered products were made available free of charge for hobbyist, non-commercial use as part of the OpenVMS Hobbyist Program.[164] Since then, several companies producing OpenVMS software have made their products available under the same terms, such as Process Software.[165] 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.[166]

In March 2020, HPE announced the end of the OpenVMS Hobbyist Program.[167] 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.[168] The CLP was launched in July 2020, and provides licenses for VSI OpenVMS releases on Alpha, Integrity and x86-64 systems.[169] 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.[170]

Release history

Release history of OpenVMS
VersionVendorRelease date
[171] [172] 		End of support
[173] [174] [175] 		PlatformSignificant changes, new hardware support
[176]
DECApril 1978[177] VAXFirst version shipped to customers[178]
August 1978First production release
Bug fixes
February 1979Support for native COBOL, BLISS compilers[179]
August 1979RMS-11 updates[180]
April 1980VAX-11/750, new utilities including EDT
April 1981Process limit increased to 8,192[181]
May 1981[182] Security enhancements[183]
BACKUP utility[184]
April 1982VAX-11/730, VAX-11/725, VAX-11/782, ASMP
August 1982PL/I runtime bundled with base OS[185]
December 1982Support for RA60, RA80, RA81 disks[186]
April 1983HSC50 disk controller, BACKUP changes[187]
June 1983Ethernet support for DECnet,[188] VAX-11/785
November 1983Support for new I/O devices[189]
April 1984Bug fixes[190]
August 1984Support for new I/O devices[191]
September 1984VAX 8600, MicroVMS, VAXclusters[192]
January 1985MicroVAX/VAXstation I, II[193]
October 1985Text Processing Utility
December 1985DELUA Ethernet adapter support
January 1986VAX 8200
July 1986VAX 8800/8700/85xx, Volume Shadowing
November 1986Support for more memory in MicroVAX II
December 1986Ethernet VAXclusters
March 1987VAXstation/MicroVAX 2000
May 1987MicroVAX 2000 cluster support
August 1987VAX 8250/8350/8530, RMS Journalling
January 1988First release installable from CD-ROM
March 1988VAXstation 3200/3500, MicroVAX 3500/3600
April 1988VAX 6000, SMP, LMF, Modular Executive
August 1988Bug fixes
October 1988
MicroVAX 3300/3400
February 1989DECwindows
VAXstation 3100 30/40, Desktop-VMS
June 1989VAXstation 3520/3540, MicroVAX 3800/3900
September 1989Cluster-wide process visibility/management
October 1989VAXstation 3100 38/48
January 1990Support for third-party SCSI devices
April 1990Support for VAXstation SPX graphics
May 1990Support for new I/O devices
October 1990VAX 65xx, VAX Vector Architecture
VAX 9000, bug fixes for VAX 6000 systems
November 1990New models of VAX 9000, VAXstation, VAXft
January 1991VAX 6000-400
March 1991VAX 4000 Model 200, new I/O devices
October 1991FDDI adapter support
November 1991Cluster-wide batch queue, new VAX models
Same as V5.5 but without new batch queue
July 1992Bug fixes for batch/print queue
September 1992VAX 7000/10000, and other new VAX hardware
November 1992September 1995Consolidation of previous hardware releases
August 1993New VAX 4000 models, additional I/O devices
VAXft 810
November 1992AlphaFirst release for Alpha architecture
May 1993Cluster and SMP support for Alpha
October 1993New DEC 2000, DEC 3000 models
June 1993VAXTCSEC C2 compliance, ISO 9660, Motif
April 1994VAX, AlphaMerger of VAX and Alpha releases, PCSI
September 1994AlphaNew AlphaStation, AlphaServer models
November 1994
June 1995March 1998VAX, AlphaCommand Recall, DCL$PATH, SCSI clusters
December 1995AlphaNew AlphaStation, AlphaServer models
March 1996
May 1996
January 1996VAX, Alpha64-bit addressing, Fast I/O, Kernel Threads
January 1997July 2000Very Large Memory support, DCL PIPE, CDE
November 1997AlphaAlphaServer 800 5/500, 1200
April 1998Support for booting from third-party devices
CompaqDecember 1998Additional I/O device support
February 1999June 2002VAX, AlphaOpenVMS Galaxy, ODS-5, DCOM
July 1999AlphaAlphaServer GS140, GS60, Tsunami
June 2000AlphaServer GS160, GS320
September 2001December 2002Minicopy support for Volume Shadowing
August 2001DII COE conformance[194]
July 2002
June 2001December 2012VAXFinal release for VAX architecture
June 2004AlphaATM and GBE clusters, Extended File Cache
HPAugust 2002December 2004AlphaSecurity and performance improvements
December 2003December 2006AlphaServer GS1280, DS15
June 2003December 2003IA64Evaluation release for Integrity servers
December 2003February 2005Second evaluation release for Integrity servers
February 2005June 2010Alpha, IA64Production release for Integrity servers
September 2005IA64Support for HP Superdome, rx7620, rx8620
August 2006December 2015Alpha, IA64Support for additional Integrity server models
November 2007IA64Support for HP BL860c, dual-core Itanium
June 2010December 2020Alpha, IA64Support for HPVM, clusters over TCP/IP[195]
VSIMay 2015December 2022IA64Support for Poulson processors[196]
March 2016Support for HPE BL890c systems, UEFI 2.3
September 2016December 2024OpenSSL updated to 1.0.2[197]
January 2017[198] Alpha
July 2017Final release for Alpha architecture[199]
April 2021December 2028IA64Final release for Integrity servers
May 2020June 2021x86-64x86-64 Early Adopter's Kit[200]
June 2021September 2021x86-64 Field Test
September 2021April 2022DECnet-Plus for x86-64
July 2022June 2023x86-64 Limited Production Release[201]
June 2023December 2026AMD CPUs, OpenSSL 3.0, native compilers[202]
January 2024Bug fixes
December 2024VMware vMotion, VMDirectPath

See also

Further reading

External links

Notes and References

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

This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "OpenVMS".

Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2024, A B Cryer, All Rights Reserved. Cookie policy.