What is VMS?

Recently I had a conversation with a account manager of a large software company who never heard of VMS.

VMS is an old operating system, but it is still used in a lot of companies.

History

VMS is an operating system, developed in 1977 by Digital Equipment Corporation (DEC). The name VMS means Virtual Memory System.

The first version ran on a 32-bit VAX-11/780 (also a DEC machine). VMS was rewritten in 1992 for DEC's 64-bit Alpha processor. From that moment on, the name was changed in OpenVMS. DEC was taken over by Compaq in 1998 and in 2001 VMS was ported to Intel's Itanium (IA-64) processor. Compaq was taken over by HP in 2002, but OpenVMS still exists, on Alpha and on Itanium systems.

OpenVMS is known as a robust and stable operating system. Sometimes people joke that the uptime of Windows is measured in days, of UNIX in months, but of VMS systems in years.

At the hackers conference DEFCON9, 4300 hackers were present. None of them was able to break in into an OpenVMS system running an HP Secure Webserver. The system was declared "cool and unhackable" by the hackers.

Properties

OpenVMS file systems consist of separate disks, just like Windows. OpenVMS contains a Record Management System which supports several file types (stream, sequential, relative and indexed files). This enables 'native' basic database functionality built in the filesystem.

OpenVMS has clustering possibilities way ahead of UNIX and Windows. For instance, in VMS clusters it is possible to work on the same file from two nodes, because the cluster supports two systems sharing the same disk (over SCSI).

Batch processing in OpenVMS is also better supported than in UNIX or Windows.

OpenVMS has a concept called "logical names". Logical names are system variables referring to a disk, a directory or file, or that contain other specific information. For instance the logical SYS$SYSDEVICE contains the system's bootdevice.

In OpenVMS files have version numbers. This way errors can easily be corrected. A directory listing is shown below:

DIR 
SJAAK.TXT;1 SJAAK.TXT;2 SJAAK.TXT;3 

The number behind the ; states the version of the file. When a file is changed by accident, the previous (original) version can be copied back easily.

Just like UNIX has shell scripting, VMS has the DCL language. The possibilities of both languages are comparable.

Cons

VMS is an expensive operating system. The price was always much higher than UNIX or Windows (and Linux of course).

TCP/IP was not natively implemented in VMS for a long time. Still, a separate product is needed for TCP/IP (the native networking technology is DECnet).

Applications

Because of the robust properties and the good security, VMS is often used in:

  • Production (automotive, steel and aluminum production, SCADA systems, etc)
  • Medical
  • Defense
  • Space
  • Secret services
  • Telecommunications (until recently, most SMS test-message systems were based on VMS)
  • Nuclear
  • Financial institutions
  • Chemical industry

This entry was posted on Friday 02 February 2007

Earlier articles

Infrastructure as code

My Book

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Supercomputer architecture

Desktop virtualization

Stakeholder management

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Infrastructure Architecture - Course materials

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

Computer crime

Introduction to Cryptography

Introduction to Risk management

The history of UNIX and Linux

The history of Microsoft Windows

The history of Novell NetWare

The history of operating systems - MS-DOS

The history of Storage

The history of Networking

The first computers

History of servers

Tips for getting your ITAC certificate

Studying TOGAF

Is your data safe in the cloud?

Proof of concept

Who needs a consistent backup?

Measuring Enterprise Architecture Maturity

Human factors in security

Master Certified IT Architect

ITAC certification

Open group ITAC /Open CA Certification

Human factors in security

Google outage

SAS 70

TOGAF 9 - What's new?

DYA: Development without architecture

Spam is big business

Why IT projects fail

Power and cooling

Let system administrators participate in projects

The 7 Habits of Highly Effective People

Archimate

A meeting with John Zachman

ITAC - IT Architect certification

Personal Information is Personal Property

The Irresistible Forces Meet the Movable Objects

Hardeningscheck and hack testing for new servers

Knowledge management

Information Lifecycle Management - What is ILM

LEAP: The Redmond trip

LEAP: The last Dutch masterclasses

What do system administrators do?

Is software ever finished?

SCADA systems

LEAP - Halfway through the Dutch masterclasses

Securing data: The Castle versus the Tank

Non-functional requirements

LEAP - Microsoft Lead Enterprise Architect Program

Reasons for making backups

Log analysis - Use your logging information

Archivering data - more than backup

Patterns in IT architecture

Layers in IT security

High performance clusters and grids

Zachman architecture model

High Availability clusters

Monitoring by system administrators

What is VMS?

IT Architecture certifications

Storage Area Networks (SAN)

Documentation for system administrators

Rootkits

Presentations: PowerPoint sheets are not enough

99,999% availability

Linux certification: RHCE and LPI

IT Infrastructure model

Sjaak Laan


Recommended links

Ruth Malan
Gaudi site
Byelex
XR Magazine
Esther Barthel's site on virtualization


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan