From Wikipedia, the free encyclopedia
This article contains content that is written like . Please help
by removing
and inappropriate , and by adding encyclopedic content written from a . (June 2017) ()
OpenVMS is a
for use in general-purpose computing. It is the successor to the VMS Operating System (VAX-11/VMS, VAX/VMS), that was produced by , and first released in 1977 for its series of
minicomputers. In the 1990s, it was used for the successor series of
systems. OpenVMS also runs on the HP -based families of computers. As of 2015, a port to the
architecture is underway.
The name VMS is derived from virtual memory system, according to one of its principal architectural features. OpenVMS is a proprietary operating system, but source code listings are available for purchase.
OpenVMS is a ,
-based operating system (OS) designed for use in , , and . When process priorities are suitably adjusted, it may approach
characteristics. The system offers high
and the ability to distribute the system over multiple physical machines. This allows the system to be tolerant against disasters that may disable individual data-processing facilities.
OpenVMS contains a
(GUI), a feature that was not available on the original VAX-11/VMS system. Prior to the introduction of DEC
systems in the 1980s, the operating system was used and managed from text-based , such as the , which provide serial data communications and screen-oriented display features. Versions of VMS running on
workstations in the 1990s supported
(AGP) graphics adapters.
Enterprise-class environments typically select and use OpenVMS for various purposes including , network services, manufacturing or transportation control and monitoring, critical applications and databases, and particularly environments where system uptime and data access is critical. System up-times of more than 10 years have been reported, and features such as rolling upgrades and clustering allow clustered applications and data to remain continuously accessible while operating system software and hardware maintenance and upgrades are performed, or when a whole data center is destroyed. Customers using OpenVMS include banks and financial services, hospitals and healthcare, network information services, and large-scale industrial manufacturers of various products.
As of mid-2014, Hewlett Packard (successor to DEC) licensed the development of OpenVMS exclusively to VMS Software Inc. (VSI). VMS Software will be responsible for developing OpenVMS, supporting existing hardware and providing roadmap to clients. The company has a team of veteran developers that originally developed the software during DEC's ownership.
This section needs additional citations for . Please help
by . Unsourced material may be challenged and removed. (September 2007) ()
4000 model 96 running OpenVMS 6.1 and DECwindows
In April 1975,
embarked on a hardware project, code named Star, to design a
virtual address extension to its
computer line. A companion software project, code named Starlet, was started in June 1975 to develop a totally new operating system, based on M, for the Star family of processors. These two projects were tightly integrated from the beginning.
was the VP lead on the VAX hardware and its architecture. Roger Gourd was the project lead for the Starlet program, with software engineers
(who would later lead development of 's ), , 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
11/780 computer and the VAX-11/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.
Over the years the name of the product has changed. In 1980 it was renamed, with version 2.0 release, to VAX/VMS (at the same time as the VAX-11 computer was renamed to simply VAX). With the introduction of the
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 memo e.g. the smallest MicroVAX 2000 had a 40MB RD32 hard disk and a maximum of 6MB 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
tapes and RX50 floppy disks, but discontinued with VAX/VMS 5.0. In 1991 it was renamed again to OpenVMS to indicate its support for industry standards such as
compatibility, and to drop the hardware connection as the port to DIGITAL's
processor was in process. The OpenVMS name first appeared after the version 5.4-2 release.
The VMS port to
resulted in the creation of a second and separate source code libraries (based on a source code management tool known as VDE) for the
source code library and a second and new source code library for the Alpha (and the subsequent
architectures. 1992 saw the release of the first version of OpenVMS for
systems, designated OpenVMS AXP V1.0. 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 next platform port to the Itanium.
In 1994, with the release of OpenVMS version 6.1, feature (and version number) parity between the VAX and Alpha variants was achieved. This was the so-called Functional Equivalence release, in the marketing materials of the time. Some features were missing however, e.g. based shareable images, which were implemented in later versions. Subsequent version numberings for the VAX and Alpha variants of the product have remained consistent through V7.3, though Alpha subsequently diverged with the availability of the V8.2 and V8.3 releases.
In 2001, just prior to its acquisition by ,
announced the port of OpenVMS to the
architecture. This port was accomplished using source code maintained in common within the OpenVMS Alpha source code library, with conditional and additional modules where changes specific to Itanium were required. The OpenVMS Alpha pool was chosen as the basis of the port as it was significantly more portable than the original OpenVMS VAX source code, and because the Alpha source code pool was already fully 64-bit capable (unlike the VAX source code pool). With the Alpha port, many of the VAX hardware-specific dependencies had been previously moved into the Alpha SRM firmware for OpenVMS. Features necessary for OpenVMS were then moved from SRM into OpenVMS I64 as part of the Itanium port.
Unlike the port from VAX to Alpha, in which a snapshot of the VAX code base circa V5.4-2 was used as the basis for the Alpha release and the 64-bit source code pool then diverged, the OpenVMS Alpha and I64 (Itanium) versions of OpenVMS are built and maintained using a common source code library and common tools. The core software source code control system used for OpenVMS is the VMS Development Environment (VDE).
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 following are recent OpenVMS I64 releases:
OpenVMS I64 V8.2, the first production-quality Itanium release, was shipped January 13, 2005. A V8.2 release is also available for Alpha platforms.
OpenVMS I64 V8.2-1, adding support for
and cell based systems, was released in September 2005. V8.2-1 is available for Itanium platforms only.
OpenVMS I64 V8.3, was released for Itanium platforms in September 2006. V8.3 is also available for Alpha systems.
OpenVMS I64 V8.3-1H1, was released in October 2007. It features full c-Class Integrity BladeServer blade support.
OpenVMS I64 and Alpha V8.4, was released in June 2010.
OpenVMS I64 V8.4-1H1, was released in June 2015.
Release date
End-of-life date
Old version, no longer supported: V1.0
25 October 1977
, Initial commercial release
Old version, no longer supported: V2.0
April 1980
Old version, no longer supported: V3.0
April 1982
Old version, no longer supported: V4.0
September 1984
and MicroVMS (for )
Old version, no longer supported: V5.0
April 1988
Old version, no longer supported: V5.1
November 1992
first OpenVMS AXP (Alpha) specific version
Old version, no longer supported: V6.0
31 December 2012
Old version, no longer supported: V6.1
April 1994
merging of VAX and Alpha AXP version numbers
Old version, no longer supported: V7.0
January 1996
full 64-bit virtual addressing on Alpha
Old version, no longer supported: V7.1
Old version, no longer supported: V8.0
limited availability eval for Integrity
Old version, no longer supported: V8.2
February 2005
Common Alpha and Itanium release
Old version, no longer supported: V8.3
September 2006
31 December 2015
Alpha, Itanium dual-core support
Old version, no longer supported: V8.3-1H1
October 2007
31 December 2015
c-Class Integrity blade server support
Older version, yet still supported: V8.4
Virtual machine guest under HPVM. Clusters over TCP/IP
Older version, yet still supported: V8.4-1H1
Support for "Poulson" Itanium processors
Current stable version: V8.4-2
April 2016
Support for HPE Itanium(R) 9500 series processor
Future release: V8.5
Itanium Updates, new TCP/IP stack
Future release: V9.0
Itanium General Release and x86-64 Early Adopter Release
Future release: V9.x
Itanium and x86-64
Old version
Older version, still supported
Latest version
Latest preview version
Future release
OpenVMS offers many features that are now considered standard requirements for any high-end server operating system. These include:
Integrated computer networking (originally , and later )
Symmetrical, asymmetrical, and
multiprocessing, including clustering
A hierarchical, feature-rich
Integrated
features such as
and relational databases, including , ,
Support for multiple computer
A standardized interoperability mechanism for calls between different programming languages
An extensible
command language ()
Hardware partitioning of multiprocessors
High level of security
OpenVMS uses the DECwindows
user interface (based on ) layered on top of OpenVMS's
compliant . Older versions of VMS instead used a proprietary window system known as VWS/UIS.
OpenVMS supports
(first called VAXcluster and later ), where multiple systems share disk storage, processing, job queues and print queues, and are connected either by proprietary specialized hardware (Cluster Interconnect) or an industry-standard
(usually ). A LAN-based cluster is often called a LAVc, for Local Area Network VMScluster, and allows, among other things, bootstrapping a possibly
over the network using the system disk of a bootnode.
VAXcluster support was first added in VMS version 4, which was released in 1984. This version only supported clustering over CI. Later releases of version 4 supported clustering over LAN (LAVC), and support for LAVC was improved in VMS version 5, released in 1988.
Mixtures of cluster interconnects and technologies are permitted, including Gigabit Ethernet (GbE), SCSI, FDDI, , CI and
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 (Various organizations have demonstrated triple-architecture clusters and cluster configurations with up to 150 nodes, but these configurations are not supported by HP).
Unlike many other clustering solutions, VMScluster offers transparent and fully distributed read-write with , which means that the same disk and even the same file can be accessed by several c the locking occurs only at the level of a single record of a file, which would usually be one line of text or a single record in a database. This allows the construction of high-availability multiply redundant database servers.
Cluster connections can span upwards of 500 miles, allowing member nodes to be located in different buildings on an office campus, or in different cities.
Host-based volume shadowing allows volumes (of the same or of different sizes) to be shadowed (mirrored) across multiple controllers and multiple hosts, allowing the construction of disaster-tolerant environments.
Full access into the
(DLM) is available to application programmers, and this allows applications to coordinate arbitrary resources and activities across all cluster nodes. This includes file-level coordination, but the resources and activities and operations that can be coordinated with the DLM are completely arbitrary.
OpenVMS V8.4 offers advances in clustering technology, including the use of industry-standard TCP/IP networking to bring efficiencies to cluster interconnect technology. Cluster over TCP/IP is supported in OpenVMS version 8.4, which was released in 2010.
With the supported capability of rolling upgrades and multiple system disks, cluster configurations can be maintained on-line and upgraded incrementally. This allows cluster configurations to continue to provide application and data access while a subset of the member nodes are upgraded to newer software versions.
OpenVMS has a very feature-rich , with support for stream and record-oriented IO, access control lists (), and file versioning. The typical user and application interface into the file system is via the Record Management Services or .
OpenVMS represents
as the 64-bit number of 100
intervals (that is, ten mill also known as a 'clunk') since the . The epoch of OpenVMS is midnight preceding November 17, 1858, which is the start of Modified
numbering. The clock is not necessarily updated every 100 for example, systems with a 100 Hz interval timer simply add 100000 to the value every hundredth of a second. The operating system includes a mechanism to adjust for hardwa when calibrated against a known time standard, it easily achieves an accuracy better than 0.01%. All OpenVMS hardware platforms derive timekeeping from an internal clock not associated with the AC supply power frequency.
While the system is shut down, time is kept by a Time-of-Year ("TOY") hardware clock. This clock keeps time to a lower resolution (perhaps 1 second) and generally, a lower accuracy (often 0.025% versus 0.01%). When the system is restarted, the VMS 64-bit time value is recomputed based on the time kept by the TOY clock and the last recorded year (stored on the system disk).
The 100 nanosecond granularity implemented within OpenVMS and the 63-bit absolute time representation (the sign bit indicates absolute time when clear and relative time when set) should allow OpenVMS trouble-free time computations up to 31-JUL-:05.47. At this instant, all clocks and time-keeping operations in OpenVMS will suddenly fail, since the counter will overflow and start from zero again.
Though 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 . Many components and applications may also encounter field-length-related date problems at year 10000 (see the ).
The common language programming environment is described in the OpenVMS Calling Standard and the OpenVMS Programming Concepts manuals. This provides mixed-language calls, and a set of language-specific, run-time library (RTL), and system service routines. The language calls and the RTLs are implemented in user-mode shareable images, while the system services calls are generally part of the operating system, or part of privileged-mode code. This distinction between languages and RTLs and system services was once fairly clean and clear, but the implementations and specifics have become rather more murky over the years.
Various utilities and tools are integrated, as are various add-on languages and tools.
Many Programming Examples are available via the OpenVMS FAQ.
The VMS Debugger supports all DEC compilers and many third party languages. It allows breakpoints, watchpoints and interactive runtime program debugging either using a
Among OpenVMS's notable features is the Common Language Environment, a strictly defined standard that specifies calling convention for functions and routines, including use of , , etc., independently of programming language. Because of this, it is possible and straightforward to call a routine written in one language () from another (), without needing to know the implementation details of the target language. OpenVMS itself is implemented in a variety of different languages (primarily ,
and ), and the common language environment and calling standard supports freely mixing these languages, and , , , , and others. This is in contrast to a system such as , which is implemented nearly entirely in the
Macro32 (an assembler on OpenVMS VAX, and a compiler on OpenVMS Alpha and on OpenVMS I64) is available within and integrated into OpenVMS. BLISS compilers are available for download, as are various ports of Perl, ,
and other languages. Java is available from the HP Java website. C, Fortran and other languages are commercial products, and are available for purchase.
In a manner similar to Unix, VMS defines several standard input and output streams 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 run interactively) or to the log file when run noninteractively.
SYS$ERROR - Standard error. Used interactively, this is the terminal display. In a batch file, it is the screen display (if run interactively), or to the log file if run interactively, 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.
This section needs expansion. You can help by . (April 2011)
OpenVMS provides various security features and mechanisms, including security identifiers, resource identifiers, subsystem identifiers, , and detailed security auditing and alarms. Specific versions evaluated at
NCSC Class C2 and, with the SEVMS security enhanced services support, at NCSC Class B1, per the NCSC . OpenVMS also holds an ITSEC E3 rating (see
and ). Passwords are hashed using the .
OpenVMS supports the following industry standard and open-source tools and applications:
Zip/Unzip ()
, as Mosquitto (MQTT broker) and Paho-C (MQTT client)
and libcurl
This section's use of
may not follow Wikipedia's policies or guidelines. Please
by removing
external links, and converting useful links where appropriate into . (February 2013) ()
The OpenVMS Operating System documentation for various releases, and for various core OpenVMS layered products, is available online at the HP website at:
Software Product Descriptions (SPD) are introductory and legal descriptions of various products, listing the various supported capabilities and product features. SPD documents for many OpenVMS-related products, and for OpenVMS itself, are available at:
The OpenVMS Frequently Asked Questions (FAQ) contains information and pointers associated with OpenVMS, and is available in various formats at:
The current OpenVMS release is 8.4-2L1 (Hudson), previous were OpenVMS V8.4-1H1 for Integrity servers, OpenVMS V8.4 for Alpha and OpenVMS V7.3 for VAX servers.
HP provides Current Version Support (CVS) and Prior Version Support (PVS) for various OpenVMS releases. The OpenVMS Roadmap guaranteed PVS status for specific releases (V5.5-2, V5.5-2H4, V6.2, V6.2-1H3, V7.3-2) until 2012, and only then ending with 24 months' prior notice. CVS is provided for the current release and for the immediately prior release.
On July 31, 2014, VMS Software, Inc. (VSI) announced that HP named VSI as the sole developer of future versions of the OpenVMS operating system and its layered product components. The first release, VSI OpenVMS Version 8.4-1H1 (Bolton), was released June 1, 2015. Next releases will support the latest Itanium hardware. The availability of VSI OpenVMS on x86-based servers is planned for 2018.
VSI has assembled a Massachusetts, US-based team of veteran OpenVMS developers, many harkening back to the core DEC team responsible for the initial and ongoing development of OpenVMS.
Some of the industry standards claimed in the OpenVMS Software Product Description are:
ANSI X3.4-1986:
ANSI X3.22-1973/FIPS 3-1: Magtape, 800 BPI
ANSI X3.27-1987/FIPS 79: Magtape, Labels and Volume Structures
ANSI X3.39-1986/FIPS 25: Magtape, 1600 BPI
ANSI X3.40-1983: Magtape, unrecorded
ANSI X3.41-1974: ASCII 7-bit control sequences
ANSI X3.42-1975: Numeric values in character strings
ANSI X3.54-1986/FIPS 50: Magtape, 6250 BPI
ANSI X3.131-1986/ISO ): -1
ANSI X3.131-1994/ISO ): SCSI-2
ANSI/-1985: logical link control
ANSI/-1985: Ethernet CSMA/CD
FIPS 1-2: Code for Information I includes ANSI X3.4-1977(86)/FIPS 15; ANSI X3.32-1973/FIPS 36; ANSI X3.41-1974/FIPS 35; FIPS 7
FIPS 16-1/ANSI X3.15-1976: Serial Comms Bit S FED STD 1010
FIPS 22-1/ANSI X3.1-1976: Synch signaling for DTE/DCE FED STD 1013
FIPS 37/ANSI X3.36-1975: Synch High-Speed signaling for DTE/DCE GIPS 1001
FIPS 86/-1979: Additional Controls for Use with ASCII
: ISO 7-bit Coded Character Set for Information Exchange
ISO 1001: Magtape, Labels and Volume Structures
ISO 1863: Magtape, 800 BPI NRZI
ISO 1864: Magtape, unrecorded / NRZI and PE
: Code extensions for ISO 646
: Time and Date Representations
ISO 3788: Magtape, 1600 BPI PE
ISO 4873: 8-bit Character Codes
ISO 5652: Magtape, 6250 BPI GCR
: Control Sequences
: CD-ROM volume and file structures
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. Since then, several companies producing OpenVMS software have made their products available under the same terms, such as Process Software and MVP Systems.
In 2011, HP staff took over the administration of the hobbyist licences. Registration was simplified and remained zero cost. The process from registering to receiving Product Authorisation Keys may take only a few hours in some cases. Software kits for operating system and layered products were made available on request via FTP download (previously it had to be shipped on CD which was chargeable). This process is not fully automatic and requires authorisation by HP Hobbyist Program staff.
operating system following VMS conventions called FreeVMS is in development, though no official releases have been made since 2010. FreeVMS supports the
architecture using an .
 maintains several publicly accessible historic computer systems, including a VAX 11/785 running OpenVMS 7.3.  from  and try running OpenVMS on the original equipment.
VMS is in some ways an ancestor of , together with
and an unreleased object-based operating system developed by
for . This lineage is made clear in Cutler's foreword to "Inside Windows NT" by Helen Custer.
OpenVMS-related terms and acronyms include:
– Digital's
(TP) system, often used with the DECdtm distributed transaction manager system service components of OpenVMS, and with the DECforms and
products in applications with transactional requirements
(CLI) – library routines for parsing VMS
parameters
– Digital's successor to the Forms Management System
– Digital's proprietary networking architecture which also includes .
– OpenVMS debuggers
(DCL) – Digital Command Language - .
– Digital's implementation of the .
– a simple synchronization mechanism
– low level
(FDL) – defines file record/field structure
(FMS) – Digital's first generation language-independent Form driver
(LAT) – is a LAN-based non-routable communications protocol to support DEC and other Terminal Servers
– Queued Input O the low-level I/O interface
– An SQL compliant relational database created by DEC but now owned by Oracle
(RMS) – high-level, language/device-independent
(RTL) – shared routines and functions, callable from any language
– OS-level virtualization implementations, co-habitating OpenVMS a form of system partitioning
OpenVMS Clusters – for redundancy, incremental hardware upgrades, or disaster tolerance
(S1032) – A high-performance database management system and application development environment designed to support the OpenVMS user community. Used at some companies in the 1980s and 90s, but, in little use today.
XQP – the eXtended QIO Processor (XQP), which implements the Files-11 filesystem since VMS 3.3.
. Faqs.org. Retrieved on .
. Archived from
. Tech Times. .
For general details on the port to Alpha, see the
book. For technical details on the port, see the .
Information from various comp.os.vms newsgroup postings from OpenVMS Engineers
for details.
for details. See
for details on
products from HP.
for details.
for details.
; see the DECnet and TCP/IP Services documentation, and see the User's Guide
; see the clustering and OpenVMS Galaxy documentation
; see the RMS and XQP documentation
; see the RMS documentation
; see the language documentation
; see the BLISS, Macro64, OPS5, Perl, PHP, Tcl/Tk and other language kits and tools
Writing Real Programs in DCL, second edition, Stephen Hoffman, Paul Anagnostopoulos,
; see the OpenVMS User's Guide
; see the OpenVMS Galaxy documentation
; see OpenVMS Guide to System Security manual
National Computer Security Center (NCSC) Trusted Product Evaluation List (TPEL)
OpenVMS at
Software Product Description (SPD)
Using DECwindows Motif for OpenVMS, Margie Sherlock,
For general details, see the . For more specific details, see the clustering-related manuals in the .
Details are in the RMS Utilities and RMS programming manuals, and in the I/O User's Reference Manual, all part of the . Also see the available , and the VMS File Systems Internals book, by Kirby McCoy,
Detailed information on time and timekeeping, and on daylight saving time and timezone differential factor operations, is contained in the .
, HoffmanLabs.org.
see the HP OpenVMS Guide to System Security manual at . Also see the
information.
. Business Wire 2014.
. February 24, 2015.
(PDF). January 11, 2017.
. January 11, 2017.
Thibodeau, Patrick. . ComputerWorld 2014.
(PDF). HP. November 2014. (Also see )
. openvms.org. Archived from
from the original on March 10, .
Neil Rieck. .
For information on layered products, see the
for the product. For OpenVMS components, see the .
January 15, 2009, at the . The Minimum You Need to Know About Service Oriented Architecture, Roland Hughes,
Getting Started with OpenVMS, Michael D. Duffy,
Getting Started with OpenVMS System Management, 2nd Edition, David Donald Miller, Stephen Hoffman, Lawrence Baldwin,
Introduction to OpenVMS, 5th Edition, Lesley Ogilvie Rice,
Introduction to OpenVMS, David W Bynon,
OpenVMS Alpha Internals and Data Structures: Memory Management, Ruth Goldenberg,
OpenVMS Alpha Internals and Data Structures : Scheduling and Process Control : Version 7.0, Ruth Goldenberg, Saro Saravanan, Denise Dumas,
OpenVMS Performance Management, Joginder Sethi,
OpenVMS System Management Guide, Lawrence Baldwin,
The hitchhiker's guide to VMS : an unsupported-undocumented-can-go-away-at-any-time feature of VMS, Bruce Ellis,
The OpenVMS User's Guide, Second Edition, Patrick Holmay,
Using DECwindows Motif for OpenVMS, Margie Sherlock,
VAX/VMS Internals and Data Structures: Version 5.2 ("IDSM"), Ruth Goldenberg, Saro Saravanan, Denise Dumas,
Writing OpenVMS Alpha Device Drivers in C, Margie Sherlock, Leonard Szubowicz,
Writing Real Programs in DCL, second edition, Stephen Hoffman, Paul Anagnostopoulos,
This section's use of
may not follow Wikipedia's policies or guidelines. Please
by removing
external links, and converting useful links where appropriate into . (February 2013) ()
Wikimedia Commons has media related to .
, contains historical facts
, contains historical facts
, archives on
, public access OpenVMS systems
architecture at
, new site
, at Hoffmanlabs.org
(archived March 21, 2015)
, primarily
, OpenVMS FILESERV
(archived July 15, 2011), 9
, InformationWeek, November 3, 2007
(102 pages long table of applications)
: Hidden categories:}