Digital PDFs

AE-HQ86F-TE

December 1989

21 pages

Original

1.6MB

Document:	VMS Operating System V5.1 SPD 25.01.31 Jan89
Order Number:	AE-HQ86F-TE
Revision:
Pages:	21
Original Filename:	http://bitsavers.org/pdf/dec/vax/vms/SPD/AE-HQ86F-TE_VMS_Operating_System_V5.1_SPD_25.01.31_Jan89.pdf

OCR Text

Software
Product
Description
PRODUCT NAME: VMS Operating

System, Version 5.1

SPO 25.01.31

DESCRIPTION

General User

System Overview

Text Processing - The Extensible VAX Editor (EVE) is
one of several text editors supplied by DIGITAL and it
permits the user to quickly Insert and delete text. EVE is
a full screen editor that allows the text to be scrolled on
the screen of an interactive terminal. EVE is written in the
Text Processing Utility (TPU) language. EVE provides an
EDT-style keypad.

VMS is a general purpose multiuser operating system
which supports VAX, MicroVAX and VAXstation series
computers. It works reliably and efficiently in both development and production environments. VMS can be tuned
to perform well in a wide variety of applications, including
compute-Intensive, I/O-intensive, real-time, and combinations of those and other environments. (The actual
amount of work supported with good performance depends upon the processor type, available physical memory, and secondary storage operations.)
VMS has well integrated networking, distributed computIng, and multiprocessing capabilities. It contains extensive ease-of-use, programmer productivity, and system
management features.

User Environment
General Access

Users may access VMS by using the English-like
DIGITAL Command language (DCl), the standard command language for VMS which is supplied with the system. DCl commands take the form of a command name
followed by parameters and qualifiers.
DCl commands can be entered from a terminal or can
be included In command procedures. Command procedures may be Invoked directly in an interactive session of
may be submitted to a batch queue for deferred execution. DCl commands provide information about the system, initiate system utilities, and initiate user programs.
DCl and VMS Utilities have a consistent integrated help
subsystem to provide summary operational information
on all aspects of system operation.
Tools and Utilities

VMS provides a number of tools and utilities for general
users, programmers and system managers.· This section
briefly describes each group of tools and utilities.

Mail Facility - The Mail facility permits a user to send
messages to any other user by typing the recipient's
name, the subject of the message, and the text of the
message. Multi-node operation is available if
DEenet-VAX is installed.
Command-level Programming - Command-level programming allows the user to create special files called
command procedures that contain a series of DCl commands. When a user invokes a command procedure, the
system processes the commands in the command procedure. The user can also use special DCL commands to
assign symbolic names, evaluate numerical and logical
expressions, accept parameters, communicate interactively with the user invoking the command procedure,
perform conditional (IF-THEN-ELSE) and branching
(GOTO) logic, and handle error conditions.
User Environment Tailoring - VMS allows user tailoring of
their environment, including user specific login command
files, shorthand commands, binding of commands to
function keys, and command recall and editing.
Other utilities include Sort/Merge, DIRECTORY, COPY,
DELETE, TYPE, PRINT, PURGE, RENAME and
SET/SHOW status.
Programmer

librarian Utility - The librarian utiliw permits efficient
storage of object modules, macros, help text, or any
general record-oriented information in central, easily accessible files. Object module libraries are searched by
the linker when the linker finds a reference it cannot
resolve in one of its input files. Macro libraries are
searched by the assembler when the assembler finds a
macro that is not defined in the input file.

®PoslScript Is a registered trademark of Adobe Systems, Inc.

lMX Window System and Its derivations (X, X11, X Version 11, X Window
System) are trademarks of the Massachusetts Institute of Technology

January 1989

software

AE-HQ86F-TE

SPD 25.01.31

VMS Operating System, Version 5.1
Symh,.,lic O~hI.l9gf!'r - The $ymholic dAbu99Etr hp.lps th9
user trace program execution and allows a user to display and modify register contents using the same symbols that are In the source code.
RMS File Utilities - RMS file utilities allow the user to
analyze the internal structure of an RMS file. They can
help the user determine the most appropriate set of
parameters for an RMS file, and how to create, efficiently
load, and reclaim space In an RMS file. (Refer to "VMS
Record Management Services" section of this SPD for
more Information on RMS.)
File Differences Utility - This utility compares the contents
of two files and lists those records that do not match.
Terminal Fallback Facility (TFF) - This facility allows DEC
7bit terminals, such as the VT100, to input and output
the DEC Multinational Character Set (MCS). Specific
tables allow conversion for a number of different 7bit
National Replacement Character sets, such as French,
German, Spanish and Swedish, to MCS. TFF also allows
character composing on terminals without use of the
compose key.
National Character Set (NCS) Utility - This utility allows
the user to define non-ASCII standard string collating
sequences and to define conversion functions. Conversion functions use conversion algorithms to change an
Input string, for example, change lower case characters
to upper case. NCS also allows RMS indexed files to be
collated via user-specified collating sequences.
System Manager

Backup - This utility provides full volume and incremental
file backup for file-structured, mounted volumes and volume sets. Individual files, selected directory structures,
or all files on a volume set can be backed up and
restored using standard file naming conventions and can
be selected by date. Files can be backed up to magnetic
tape or to another disk.. You can back up and restore
selected files using on-line backup or entire volumes
using standalone backup.
Analyze Disk Structure - This utility compares the structure Information on a disk volume with the contents of the
disk, prints the structure information, 'and permits
changes to that information.
MONITOR - This utility permits the system manager to
monitor different classes of systemwide performance
data (for example, process activity," 110 activity, and
memory management activity) at user-specified intervals.
The data may be displayed as it is gathered or saved in a
file for later use.

VAXcluster Systems.
VMS System Management (SYSMAN) Utility - This utility
allows the system manager to define a system management environment so that operations performed from the
local VAX system are executed on all other VAX systems
in the defined environment. The environment may include VAX systems in a DEC net-VAX network or in a
VAXciuster System.
Program Development

VMS provides a comprehensive set of tools for developing programs including editors (such as EVE for editing
source programs), a linker, a librarian, and a symbolic
debugger. The assembly-level VAX MACRO language is
supplied with VMS.
The VMS Run-Time Library provides general string manipulation, Input/Output (1/0), 110 conversion, terminal
independent screen handling, date and time formatting
routines, common mathematical functions, signaling and
condition handling, and other general purpose functions.
These routines can be called from programs written in
VAX MACRO or from VAX Ada, VAX BASIC, VAX
BLlSS-32, VAX C, VAX COBOL, VAX DIBOL, VAX
FORTRAN, VAX PASCAL, VAX PUI, VAX RPG, and
VAX SCAN.
Major VAX languages (including those listed above adhere to the VAX common calling standard, meaning that
routines written in any of these languages may directly
call routines written in any other language. Development
of applications using multiple languages is simple and
straightforward.
All routines in the run-time library follow standard call and
condition handling conventions and most are contained
within a shareable image.
At a lower level, programs can call system services
directly for security,event flag. asynchronous system
trap, logical name, record and file 110, process oontrol,
timer, time conversion, condition handling, lock management, and memory management services. Again, system
services use standard call and condition handling conventions.
VMS supports execution of non-privileged images created on earlier versions of VMS. Recompiling and
relinking are in· general not required.

. System Management
Security and Control

VMS provides privilege, protection, and quota mechanisms to control user access to system-controlled structures in physical structures in physical memory,
system-structured files and volumes, and certain devices.

License Management Facility (LMF) - This facility allows
the system manager to easily determine which software
products are licensed and installed on a standalone VAX
and on each of the VAX systems in a VAXciuster System. It allows the system manager to limit use of the
software products to a subset of systems in a VAXcluster
,and It provides an audit trail which allows the system
manager to track license changes that occur within a
VAXcluster system. Refer to the section entitled
"VAXcluster Support" for more Information on

The system maintains information about user accounts in
the user authorization file (UAF). which can be modified
by the system manager. When creating user accounts
with the Authorize Utility, the system manager assigns
the privileges and quotas associated with each user
account. The system manager also assigns a unique

- 2 •

VMS Operating System, Version 5.1

SPD 25.01.31

user name. password. and user Identlfleatlon code (Ule)
to each account. Optionally, additional Identifiers may be
assigned to each account, permitting users to belong to
multiple overlapping groups or projects. Account use
may be limited by time of day, day of week and type of
access, such as local vs. remote vs. batch.

the system disk. Application programs will execute as
long as the layered products or optional software
DO NOT DEPEND on optional software run-time components that are not supported in the tailored environment.
Refer to the product's System Support Addendum (SSA)
for the optional products supported in the tailored
environment.

To log in and gain access to the system, the user must
supply the user name and password. The password is
encoded and does not appear on terminal displays. Users can change their password voluntarily, or the system
manager can selectively enforce password length,
change frequency, and generation of pronounceable
nonsense passwords.

Installation

VMS is distributed as binary kits on tape, disk. or
CDROM. Procedures for setting up the system disk from
a kit and for preparing the system for day-to-day operations are simple and straightforward. The procedures are
described in the installation and operation guide for each
processor.

login security Includes breakin detection, which allows
terminals to be disabled when password guessing Is
detected. When a user logs In, the system displays a
message stating when the last login for the account
occurred.

Batch/Print Facility

VMS provides an extensive batch/print facility which allows the creation of queues and spooled devices in order
to process non-interactive workloads in parallel with timesharing or real-time jobs.

A UIC consists of two fields, the unique user field and a
group field. Every file, device, queue, or other system
object Is labeled with the UIC of its owner (normally the
user who created the object).

The system queues batch jobs for execution. The system
manager can regulate the number of queues and the
number of streams per queue (that is, the number of
batch jobs in the queue that can execute concurrently).

Ales, devices, queues, and other system objects are
assigned a protection mask which allows read, execute,
write, and delete access to be selectively granted to the
object's owner and group, to privileged system users,
and to all other users. In addition, files, devices, queues,
and some other system objects may be protected with
access control lists to allow access to be selectively
granted or denied to a list of individual users, groups or
identifiers.

Different batch job queues may have different attributes
such as the maximum CPU time permitted, working set
size, and priority. Facilities are provided for starting and
stopping queues, as well as the jobs in a queue.
Print queues, both generic and specific (with forms
recognition) together with queue management facilities
give the user versatile print capabilities.

Scavenge protection may be selectively enabled in the
form of file high-water marking, erase on allocate, and
erase on delete, to ensure that file contents cannot be
read after the file has been deleted.

Accounting

For accounting purposes, VMS keeps records of the use
of system resources. These statistics include processor
and memory utilization, I/O counts, print symbiont line
counts, image activation counts, and process termination
records.

Security alarms are provided to allow selective auditing
of security related events, including
• login and logout

Autoconfigure/Autogen

• login failures and breakin attempts

VMS provides utilities to automatically configure the
available devices into the system tables, and to set
system operational parameters based on the detected
peripheral and memory configuration. There is no need
for a traditional "system generation" process when the
hardware configuration is expanded or otherwise modi~
fied.

• Authorization changes
• Ale access, selectable by use of privllige, type of
access, and by individual file
Note that DIGITAL does not warrant that the system is
secure, although DIGITAL will fix security problems
brought to our attention as promptly as circumstances
warrant.

VMS INS TAL
VMS includes an facility to automate operating system
software updates, as well as handle the installation of
optional DIGITAL-supplied software products.

Tailoring Facility

Tailoring allows users to enjoy the full functionality of
VMS while providing a compact version of the operating
system on the system disk that is tailored to the users'
needs. Tailoring Is supported on processors with small
disk configuration. VMS upgrade procedures are not
supported In tailored environments.

System Environment
Process and Scheduling

The basic unit of execution in VMS is the process which
consists of individual address space and registers known
as "context" and code called an "executable image." The
context identifies the process and describes its current

Due to space constraints, there is no guarantee that
products can be installed if user code and data reside on

- 3 •

SPD 25.01.31

VMS Operating System, Version 5.1
state. Executable images consist of system programs
and user programs that have been compiled and linked.
The maximum number of concurrent processes is 8192
per VAX system.
Processes receive processor time to execute their images based on the priority of the process. Thirty-two
priorities are recognized. Priorities 0-15 are for time
-sharing processes and applications that are not time
critical (four Is the typical default for time-sharing processes) and priorities 16-31 are for real-time processes.
Each time an event such as an I/O interrupt occurs, the
system first services the event then passes control to the
highest priority process ready to execute. The system
automatically adjusts prioritles of processes whose base
priority is in the range of 0 to 15 to favor I/O-bound
processes, but the system will not adjust the priority of a
process in the range of 16 to 31.
Real-time processes can be assigned higher priorities to
ensure that they receive processor time whenever they
are ready to execute. Real-time processes are scheduled
pre-emptively; that is, if a real-time process is ready to
execute, it is given the processor immediately, unless a
real-time process with a higher priority is ready to execute.
VMS uses paging and swapping mechanisms to provide
sufficient physical memory for both multiple concurrently
executing processes and for processes whose memory
requirements exceed available physical memory. The
maximum working set size is 100,000 pages of memory.

operations simultaneously. The processors can perform
operations in all VAX access modes (user, supervisor,
executive, and kernel).
VMS SMP configurations consist of multiple central processing units executing code from a single shared memory address space. Users and processes share a single
copy of VMS. SMP also provides simultaneous shared
access to common data in global sections to all processors. VMS SMP dynamically balances the execution of
all processes across all available procr:tssors based on
process priority.
SMP support is an integral part of VMS and is provided
transparently to the user. Because an SMP system is a
single system entity, it is configured into a network and
VAXcluster systems as a single node.
VAXcluster Support

A VAXcluster system is formed by coupling a VAX processor with mass-storage servers or with other VAX
systems, and, optionally, with mass storage servers
known as "Hierarchical Storage Controllers" (HSCs).
These cooperating, independent processors may share a
single disk-resident copy of VMS, RMS data down to the
record level, and locally attached or HSC-based disks.
VAXcluster systems provide data sharing and easy incremental growth, and may be configured to provide high
availability computing environments.
Refer to VAXcluster Software (SPD 29.78.xx) for more
information.
Networking Facilities

Processes can, however, exercise control over memory
management. A real-time process, for example, can inhibit paging or swapping of critical code and data.

VMS provides device drivers for all DIGITAL Ethernef
adapters listed below. Application programmers can use
the 010 system service to communicate with other systems connected via the Ethernet using either Ethernet or
IEEE 802.3 packet format. Simultaneous use of DIGITAL
Ethernet and IEEE 802.3 protocols are supported on any
DIGITAL Ethernet adapter. Refer to the DECnet-VAX
Software Product Description (SPD 25.03.xx) for further
information on supported communications devices.

Peripheral devices can be managed by the system or
allocated by individual processes. At least one disk must
be a system disk. Other disks can be designated as data
disks for the general use of all users logging into the
system or for a group of users. Interactive terminals are
controlled by the system, and the system normally controls one or more printers.

DIGITAL's terminal server products can be used for t~r
minal access to VMS. When used in a VAXcluster system environment, terminal servers automatically distribute users, at login time, across the available VAX
systems.

Interprocess Communication

VMS provides a number of facilities for application that
consist of multiple cooperating processes:
• Mailboxes are virtual devices that allow processes to
communicate with queued messages.

VMS can also establish a connection to other devices
(such as printers) attached to such terminal servers.

• Shared memory sections permit multiple processes
concurrent access to shared address space.

DECnet-VAX offers task-to-task communications, file
management, downline system and task loading. network command terminals, and network resource sharing
capabilities using the DIGITAL Network Architecture
(DNA) protocols. Refer to DEC net-VAX (SPD 25.03.xx)
for more information on this product.

• Common event flags provide simple synchronization.
• The lock manager provides a more comprehensive
enqueue/dequeue facility with multi-level locks, values, and ASTs.

Reliability

Symmetric Multiprocessing

The system handles errors as transparently as possible
while maintaining data integrity and providing sufficient
information to diagnose the errors. The system limits the
effects of an error by first attempting to recover from the

VMS provides symmetric multiprocessing (SMP) support
for multiprocessor VAX systems. SMP is a form of tightly
coupled multiprocessing In which all processors perform

- 4 -

VMS Operating System, Version 5.1

SPD 25.01.31

error: thltn If recovery fn"~. by rftportJng the error to the
current process for action; and finally (If the error cannot
be clearly bounded), by shutting down and restarting the
system. VMS will shut Itself down rather than continue
operating with a condition that could propagate undetected bad data. The types of errors possible are as
follows:
•

Processor errors (machine checks)

•

Operating system errors (system errors or undetected
hardware failures)

•

User errors

•

Memory errors (The system examines memory at
start-up time and does not use any pages found to be
bad. During system operation, the hardware transparently corrects all single-bit memory errors, for those
systems with ECC. memory. An unrecoverable error
causes the memory page on which the error occurred
to be added to the bad page list; If the page has not
been modified, system operation continues with a new
copy of the page.)

•

1/0 errors

VMS Includes a User Environment Test Package which
verifies that the VMS operating system is properly
Installed on the customer's configuration and ready for
use.
Input/Output
The 010 system services provide a direct interface to the
operating systems I/O routines. These services are available from within most VAX programming languages and
can be used to perform low-level 1/0 operations efficiently with a minimal amount of system overhead for
time-critical applications.
Device drivers execute 1/0 instructions to transfer data to
and from the device and to communicate directly with an
1/0 device. Each type of 1/0 device requires its own
driver. DIGITAL supplies drivers for all devices supported
by the VMS Operating System and provides 010 system
service routines to access the special device dependent
features available in many of these devices. Users with
special needs or nonstandard devices can write their
own device drivers. (The "VMS Device Support Manual"
in the VMS Extended Documentation set describes how
to write your own device driver.)

The system logs all processor errors, all operating system errors detected through Internal consistency checks,
all double-bit memory errors (and a summary of corrected single-bit errors), and all I/O errors. (Double-bit
errors are detected only on those VAX and MicroVAX
systems with ECC memory.)

The VMS Operating System suports a variety of disk and
tape peripheral devices, as well as terminals, networks,
mailboxes (virtual devices for interprocess communication), and more general 1/0 devices, including line printers, card readers, and general data acquisition devices.

If the system is shut down because of an unrecoverable
hardware or software error, a dump of physical memory
Is written; the dump includes the contents of the processor registers. The VMS System Dump Analyzer utility is
provided for analyzing dumps.

VMS RMS is a set of 1/0 services that help application
programs process and manage files and records. Although it is primarily intended to provide a comprehensive software interface to mass storage devices, VMS
RMS also supports device-independent access to
unit-record devices.

VMS Record Management Services (VMS RMS)

If power fails, the system shuts down automatically.
When power is restored, the system restarts automatically and resumes processing at the point of interruption
if the system has a time-of-day clock and a memory
battery back-up unit, If the contents of memory are still
valid and If the system is set to permit automatic
re-booting. The system restarts devices and communications lines. All 1/0 operations in progress, including magnetic tape, are restarted. On request, programs can be
notified of power restoration. An optional battery operated hardware clock resets the date and time of day
when the system restarts. If the system does not have a
battery backup unit, or if the memory contents are not
valid on power restoration, the system will reboot automatically if the system is set to permit automatic
rebooting.

VMS RMS supports sequential, relative, and indexed file
organizations in fixed-length and variable-length record
formats. VMS RMS also supports byte stream formats for
sequential file organization. VMS RMS record access
modes provide access to records in four ways: sequentially, directly by key value, directly by relative record
number, and directly by record file address. VMS RMS
also supports block 1/0 operations for various
performance-critical applications that may require
user-defined file organizations and record ·formats.
VMS RMS ensures safe and efficient file sharing by
providing multiple file access modes, automatic record
locking where applicable, and optional buffer sharing by
multiple processes.

Diagnostics can be run on individual devices during normal system operation.

VMS RMS utilities aid file creation and record maintenance. These utilities convert files from one organization
and format to another, restructure indexed files for storage and access efficiency, and reclaim data structures
within indexed files. The utilities also generate appropriate reports.

Certain critical components can operate in degraded
mode. For example, the memory cache can be disabled.
The system places a component in degraded mode
when errors pass a threshold level.

For systems that have DECnet installed, VMS RMS provides a subset of file and record management services to
remote network nodes. Network remote file operations
are generally transparent to user programs.

If, for any reason, the system disk does not come back
on line after a power failure within a specific time after
the CPU regains power, the system shuts down.

-5 -

SPD 25.01.31

VMS Operating System, Version 5.1
OCl commands sum as EDIT. CREATE, COpy TYPE,
and PRINT allow manipulation at the DCl command
level of RMS files and records within RMS files.
Disks and Tape Volumes

Disk volumes can be organized into volume sets. Volume
sets can contain a mix of disk device types and can be
extended by adding volumes. Within a volume set, files
of any organization type can span multiple volumes. Ales
can be allocated to the set as a whole (the default) or to
specific volumes within the set. Optionally, portions of
Indexed files can be allocated to specific areas of a
single disk volume or to specific volumes in a volume set.

To determine whether a specific DECwindows application runs distributed across different operating systems,
refer to the application's product description. The applications included with VMS, described in following section,
are supported for distributed operation between VMS
systems.
The DECwindows desktop environment also provides a
new user interface to VMS and promotes the establishment of a consistent style of graphical VMS user interface by including a new set of integrated desktop
applications.
X Window System Support

Disk quotas can be placed on the amount of space
individual users can allocate. Quota assignment is made
by User Identification Code and can be controlled for
each volume set in the system (or for each individual
volume If the volume Is not part of a set).

The VMS implementation of the DECwindows environment is compatible with the X Window System,
Version 11. This conformance has been validated by use
of the X Testing Consortium's validation suites. Specifically, conformance is provided as follows:

Disk structure Information can be cached in memory to
reduce the 1/0 overhead required for file management
services. Although not required to do so, users can
preallocate space and control automatic allocation. For
example, a file can be extended by a given number of
blocks, contiguously or noncontiguously, for optimal file
system performance In specific cases.

• Support is Included for the X display server, X network
protocol, and X programming library (Xlib) from Release 2 of the X Window System.

The system applies software validity checks and
checksums to critical disk structure Information. If a volume is improperly dismounted because of user error or
system failure, the system automatically rebuilds the volume's structure information the next time the volume is
mounted. The system detects bad blocks dynamically
and prevents their reuse once the files to which the
blocks were allocated are deleted. On Digital Storage
Architecture (D3A) disks, the disk controller dynamically
detects and replaces bad blocks automatically.
The system provides eight levels of named directories
and subdirectories whose contents are alphabeticallyordered. Device and file specifications follow standard
DIGITAL conventions. logical names can be used to
abbreviate the specifications and to make application
programs device and file-name independent. A logical
name can be assigned to an entire specification, to a
portion of a specification, or to another logical name.
VMS supports multi-volume magnetic tape files with
transparent volume switching. Access positioning is done
either by filename or by relative file position.

• Support is included for the Xto~kit programming library from Release 3 of the X Window System.
Workstation Device Support

The VMS DECwindows environment provides several
software components to support displaying graphics and
windowing output on and receiving keyboard and pointer
driver input from VAX workstations.
Device drivers are provided to support output to monochrome and color displays and to receive input from
keyboard, mouse, and tablet devices.
Display servers compatible with the X Window System
receive output requests from applications and translate
those requests into driver commands. They also relay
driver generated input events back to the applications.
Over 400 video fonts are provided in a variety of styles
and point sizes for use on 75 and 100 dot per inch (dpi)
monitors. These video fonts have been designed to correspond directly to the fonts used by DIGITAL's PostScript® printers. In addition, a font compiler is provided
so that customers can make their own private fonts available on their DECwindows systems.
The User Environment

The user environment consists of four basic components.

VMS DECwlndows Features

The Session Manager provides the top-level user interface to a DECwindows workstation. It performs application activiation, session-wide customization, screen printing, security management and session control.

Integral to VMS V5.1 is support for the DECwindows
desktop environment. This new computing environment
is based on the Industry standard X Window System™.
X Version 11 is a network based window system. The
protocol is implemented in the servers on the display
end, and libraries on the client end. DIGITAL fully supports the X 11 Protocol In the VMS DECwindows Clients,
libraries, and Server with DECnet as the underlying
communications protocol.

The Window Manager provides user control for overlapping windows through various functions.
File View is a graphical interface to the VMS Operating
System that allows users to execute system commands
and run DECwindows applications.

• 6 •

VMS Operating System, Version 5~1

SPD 25.01.31

The DECterm terminal emulator provid~s workstation users With a familiar Interface for accessing existing VMS
features and applications. It Is a ReGIS and slxel capable
VT320 terminal emulator. Programs written for VT52,
VT100, VT220, or VT320 class terminals and using standard VMS terminal driver features operate without modification In this workstation window. OECterm additionally
provides workstation-orlented features such as
mouse-based cursor positioning, variable screen sizes,
and cutting and pasting of text between terminal emulators and other OECwlndow appllcation$.

programming 'anguages. The X and XUI programming
libraries have all been provided with procedural language
bindings In both the style of the VAX calling standard and
the style of the MIT C language programming conventions. The COA libraries have been provided only with
VAX calling standard bindings.
specific support is provided for the following languages:

Applications

A set of Integrated desktop applications Is provided as a
base component of the OECwindows environment.
These applications establish and demonstrate the consistent OECwindows user model. They also provide
some basic end user capabilities.

VAX Ada

VAX FORTRAN

VAX BASIC

VAX MACRO

BlISS-32
Implementation Language

VAX PASCAL

VAX C (VAX calling standard of
VAX PUI MIT convention.
X Window System (X) Programming Support

The X Window System compatible X programming library
(Xlib) provided by the VMS OECwindows environment
provides basic resource management (windows, color
maps, input devices) and bitmap graphics services. It
defines a mapping of the X network protocol to procedure library.

These applications are:
• Bookreader - A 1001 for viewing the contents of books
that are distributed and stored on-line
• Calculator - A simple four function calculator

• Cardfiler - A hierarchical information storage application similar to an online address andlor phone book.

The Xtoolkit programming library included with Release 3
of the X Version 11 Window System is also supported by
the VMS OECwindows environment. It is described further under XUI Programming Support.

• Clock - An analog andlor digital date and time display

X User Interface (XUI) Programming Support

• Compound document viewers - Tools for reading documents containing compound text, graphics, and image data on terminals and OECwlndows workstations

XUI determines the application model for DIGITAL and
third-party software tailored for the OECwindows environment. It establishes the conventions and styles that are
encouraged for applications that share a OECwindows
workstation. Applications use XUI components to build
user interfaces that make them look and feel like integrated members of the DIGITAL computing environment.

• Calendar - A personal time management system

• Mail - A OECwlndows user Interface to the VMS Mail
facility
• Notepad - A simple text editor

The XUI Style Guide, available in the VMS OECwindows
Programming Kit, describes the principles, philosophy,
and components used to build consistent and
well-integrated OECwindows applications.

• Paint - A simple bitmap graphics editor
• Puzzle Game - A game that challenges you to sort
mixed up puzzle tiles
• TPU/EVE - A OECwlndows user Interface to the VMS
TPU/EVE editorbul;

Its concepts are implemented by the XUI Toolkit. The
XUI Toolkit is a superset of the X Window System
Xtoolkit and contains four components:

execution of and output display from each of the
above applications Is supported across the network
between VMS systems.

• Xtoolkit components for managing, modifying, and
creating user interface components (known as widgets and gadgets)

Programming

The VMS OECwindows environment Includes an extensive set of programming libraries and tools for use by
developers of new applications. These components support the development of portable applications by focusing
on three broad areas:

• OECwindows widgets and gadgets for implementing
common user interface objects such as scroll bars.
menus. and push buttons

• X Window System support

• Resource manager routines for loading user interface
definition files and creating widgets and gadgets
based on their contents

• Utility routines that provide applications with functions
for performing common tasks such as cut and paste

• X User Interface (XUI) support
• Compound Oocument Architecture (COA) support

The XUI Toolkit is used in conjunction wtih the
OECwindows User Interface Language (UIL) compiler.

Components from each of these areas can be used in
any combination to address the needs of applications.
They can also use the tools from a variety of different

-7-

SPO 25.01.31

VMS Operating System, Version 5.1

• ANSI X'3.4-1986~ American Standard Code for Information Interchange

The lIser Interface definition files produCflld by this compiler contain the data to separate form and function in
OECwlndows applications and allow OECwlndows toolkit
widget and gadget details, such as menu item labels, to
be stored separately from the toolkit and application
run-time code. This capability allows application developers to easily prototype and modify user interface designs,
separate form and function In applications, and support
internationallzable products.

• ANSI X3.22-1973: Recorded Magnetic Tape (800
BPI, NRZI)
• ANSI X3.26-1 980: Hollerith Punched Card Code
• ANSI X3.39-1986: Recorded Magnetic Tape (1600
BPI, PEl
• ANSI X3.40-1983: Unrecorded Magnetic Tape

Compound Document Architecture (CDA) Programming Support

• ANSI X3.41-1974: Code Extension Techniques for
Use with 7-blt ASCII

The bOA Toolkit provides access routines that applications can use to easily create, read, and write files
containing compound text, graphics, and Imaging data.
These files provide a vehicle for recording this information on disk, a medium for interchange of this data
between applications, and an intermediate form from
which high-resolution printable graphics data can be
generated.

• ANSI X3.42-1975: Representation of Numeric Values
in Character Strings
• ANSI X3.27-1987: File Structure and Labeling of Magnetic Tapes for Information Interchange (Level 3)
• ANSI X3.54-1986: Recorded Magnetic Tape (6250
BPI. GCR)

In addition to providing support for developing new applications to access compount documents, VMS also provides fallback support allowing many existing utilities to
read and operate onthese new kinds of files.

• ANSI/IEEE 802.2-1985: Logical Link Control
• ANSIIIEEE 802.3-1985: Carrier Sense Multiple Access with Collision Detection

Transport Mechanisms

• FIPS PUB 1, 2, 3-1, 7, 13,14,15,16,22,25,26,35,
37, and 79, but not FIPS PUB 17-1 or 46; other FIPS
PUBs are not applicable

VMS OECwindows supports two different mechanisms
for transport of X network protocol packets between
applications and display servers.

• ISO 646: ISO 7-bit Coded Character Set for Information Exchange

The first mechanism Is OECnet. This transport is used
when the OECwlndows application and display server
are distributed across two different machines In the
network.

• ISO 1001: File structure and labelling of magnetic
tapes for information interchange (Level 3)
• ISO 1.863: Information Processing - 9-track, 12,7 mm
(0.5 in) wide magnetic tape for information interchange recorded at 32 rpmmm (800 rpi)

The second mechanism is a VMSOECwindows-specific
shared memory-based transport. When the OECwindows
application and display server are located on the same
workstation, this optimization provides significantly
greater performance. It Is the default transport under
these circumstances.

• ISO 1864: Information Processing - Unrecorded 12, 7
mm (0.5 in) wide magnetic tape for information interchange - 35 ftpmm (800 ftpi) NRZI, 126 ftpmm (3200
ftpi) phase encoded and 356 ftmm (9042 ftpi), NRZI

VAX Volume Shadowing

• ISO 2022: Code Extension Techniques for Use with
ISO 646

VAX Volume Shadowing Is a feature available on VAX
systems using HSC-series controllers with RA-series
disks. This feature enhances data availability by duplicatIng all data written to disk onto two or three compatible
disk volumes. Refer to VAX Volume Shadowing
(SPO 27.29.xx) for more Information.

• ISO 3307: Representations of Time of. the Day
• ISO 3788: Information Processing - 9-track, 12,7 mm
(0.5 in) wide magnetic tape for information interchange recorded at 63 rpmm (1 600 rpt). phase
encoded

VAX RMS Joumaling

VAX RMS Journaling Is a tool which maintains the data
Integrity of RMS files In the face of a number of failure
scenarios. It help$ to protect RMS file data from becomIng lost or Inconsistent. Refer to VAX RMS Journaling
(SPO 27.58.xx) for more Information.

• ISO 4873: 8-bit Code for Information Interchange Structure and Rules for Implemetation
• ISO 5652: Recorded magtape (6250)
• ISO 6429: Control Functions for Coded Character
Sets

Standards

VMS Is based on the following American National Standards Institute (ANSI), U.S. Federal Information Processing (FIPS), and Intemational Standards Organization
(ISO) standards:

• X display server, X network protocol, and X programming library (Xlib) from Release 2
• Xtoolkit programming library from Release 3

•8 •

SPO 25.01.31

VMS Operating System, Version 5.1

GROWTH CONSIOERA110NS

The minimum amount of memory supported for a
standalone VMS system 22MB. This first table contains
the minimum amount of additional memory required for
the following components to be installed on a VMS
system.

The minimum hardware requirements for any future version of this product may be different from the minimum
hardware requirements of this version.
VMS Disk Block Requirements

Component

Block Space Requirements (Block Cluster Size = 2):
The disk block size for the VMS Operating System,
Version .' 5.1, after Installation is approximately 61 ,000
blocks. This figure Includes 5,600 blocks· for page and
swap files. Most systems will require larger page and
swap flies. This figure also includes library files which are
in data-reduced format. Most system managers choose
to expand these files (for faster access). The expansion
requires approximately 7,000 additional blocks;
At least 9,000 free blocks are required to upgrade from
VMS V5.0 or VMS V5.0-x to VMS V5.1. The recommended amount is 23,000 free blocks.

Necessary Memory

OECnet

VAXcluster

1.5

OECwindows with remote execution
of applications

1.5

OECwindows with local execution
of applications

2.0

Two example configurations based
on the above table are:

VMS DECwinclows Disk Block Requirement
System

The disk block size for the complete VMS OeCwindows
environment after installation is approximately 50,000
blocks. This is in addition to the 61 ,000 blocks required
for the other components of the VMS Operating System
environment. Select portions of the environment may be
installed therefore using less disk space. Peak usage
during Installtlon is within 5,000 blocks of the net usage
for that Installation.

Minimum Supported Memory

OeCwindows with applications
executing remotely, and OeCnet
OECwindows with applications
executing locally, VAXcluster and
OECnet

The following list describes how many blocks are needed
for each section:

Note:

• User environment and applications - 16,500 blocks.
This section provides support for running VMS
OeCwindows applications on VAX computer servers.
• Workstation device support - 8.000 blocks. This number includes 2,500 blocks for the 75 dpl fonts and
3,000 blocks for the 100 dpi fonts. On 75 dpi systems,
the 100 dpl fonts do not have to be installed. On 100
dpi systems, both sets of fonts must be installed.

4.0

6.0

These memory requirements are the minimums.
More memory will be required for satisfactory
performance of the operating system and
OECwindows applications. The performance
and memory usage of VMS OeCwindows
systems is particularly sensitive to system
configuration and window appplication usage.
Remote execution of an application requires an
additional system which runs the application
while the display of the application occurs on the
local workstation.

• Programming Support - 25,000 blocks (approximately
3,000 per language). This number includes support
for all the programming languages. If only a subset of
languages are installed, the amount of disk space will
be less.

Please refer to VMS documentation for more information
on performance.

Note that the individual sizes add up to more than the
total because some components are shared by multiple
portions of the environment. Please refer to documentation for details concerning the partial installation of the
VMS OECwindows software.

The VMS OECwindows software is not supported on the
MicroVAX I. VAXstation I. VAX-111725. and the
VAX-11/730.

Memo~ Requ"emen~

VMS License Information

The following tables describe the minimum amount of
memory required for a system user to install, boot and
login to a VMS system. To ensure satisfactory performance of applications, additional memory will be
required.

The VMS Operating System uses one of four different
kinds of licenses depending on the hardware and
software configurations used and c.uu.emty StIppOrted.
These are the four types of VMS licenses:

Please refer to specific layered product Software Product
Descriptions for their memory requirements.

VMS DECwindows System Restrictions

·9·

SPD 25.01.31

VMS Operating System, Version 5.1
VMS A vailability License

Documentation

this type of license provides unlimited use to the USers
on a system. These licenses are sometimes referred to
as capacity licenses. VMS availability licenses are sized
according to system type.

Extensive and complete documentation is available for
VMS. The documentation is organized into functional
subkits, based on usage of the subkit. For example, all
system management manuals are in one subklt. An
easy-to-use desk-top set of manuals is also available for
users who do not require extensive documentation.

VMS Multiuser License

This type of license provides use according to a specified
number of concurrent users. This is an activity-based
license.

Documentation for VMS DECwindows is available in
printed form, in two different sets. The VMS
DECwindows User Kit is for the end application user and
the VMS DECwindows Programming Kit is for the
DECwindows software developer.

VMS Workstation License

This type of license provides use for a single-user on a
VAX Workstation.

The VMS DECwindows Online Documentation compact
disc contains both the User Kit and the Programmer Kit.

VMS Server License

ORDERING INFORMATION

This type of license provides for the non-Interactive use
of VMS.

Software License: QL-001A*-**

Not all VMS license types are available for all system
models.

Software Media (with Extended Documentation Set):
QA-001 A*-**

H no VMS license is registered and activated via the

Software Documentation (with Extended Documentation
Set): QA-001 AA-GZ

License Management Facility, then a single login is
permitted for system management purposes, generally
through the system console (OPAO:).

Software Product Services (with Extended Documentation Set): QT-001A*-**

Several of the VMS license types are based on number
of concurrent uses called an activity license. Every product has the option to define an activity as related to the
License Management Facility. VMS defines activities,
sometimes referred to as VMS "users", as follows:

Software Media
QA-09SA *-**

• Each remote terminal connection is considered an
activity. This Is true even Hyou set host to your local
node (SET HOST 0).

Software Product Services (with Base Documentation
Set): QA-09SA *_••

• A batch job is not considered an activity.
• A remote network connection (other than a remote
terminal connection) Is not considered an activity.
SOFTWARE LICENSING
VMS DECwlndows Is an integral part of the VMS OperatIng System requiring no additional license.

Base

Documentation

Set):

Software Documentation (with Base Documentation Set):·
QA-09SAA-GZ

• Each connection from a terminal server is considered .
an activity.
• A multiple-window session on a workstation is
considered one activity, regardless of the number of
windows.

(with

VMS
DECwindows
QA-09SAB-GZ

User

Kit

Documentation:

VMS DECwindows Programming Kit Documentation:
QA-001 AM-GZ
VMS DECwindows Online Documentation CD:
QA-VP4AA-G8
The Software Media with the Extended Documentation
Set is recommended for users managing a high-end VAX
system (e.g., a VAX 8600 or VAX 8830), VAXcluster
systems, or aDECnet-VAX network. The Software Media
with the Base Documentation Set is recommended for
managers of small standalone systems, for general
end-users;

The VMS software is furnished under the licensing provisions of DIGITAL's Standard Terms and Conditions. For
more information about DIGITAL's licensing terms and
policies, contact your local DIGITAL office.

DISTRIBUTION MEDIA
Disk:

RA60, RX33, RL02. RK07. RC25

License Management Facility Support

Tape:

9-track 1600 BPI Magtape (PE). TK50 Streaming
Tape

this product requires the use of the License Management Facility.

VMS DECwlndows

License units for this product are allocated on a per-CPU
plus per-user basis.

VMS

Disk:

Compact Disk

Tape:

9-track 1600 BPI Magnetic Tape (PE), TK50
Streaming Tape

• 10 •

SPD 25.01.31

VMS Operating System, Version 5.1
The VMS DECwlndows software Is avallabl~ on the three
media types listed above. The VMS DECwlndows software Is a separately Installable option. It has been designed this way to allow users who do not have the need
to Install VMS DECwindows software to conserve disk
space and also to allow systems with less than minimum
configuration requirements to continue to run VMS.

OECwlndows. DECnet·VAX, and VAXrlus1er Software
may be different from current hardware requirements.
For configuration details about VAX hardware, refer to
the VAX System and Options Catalog and the Networks
and Communications Buyers Guide.
Refer to the individual SPOs for DEC net-VAX and
VAXcluster Software for detailed product information.

SOFTWARE PRODUCT SERVICES
A variety of service options are available from DIGITAL.
For more information, contact your local DIGITAL office.

Product Name
DECnet-VAX
VAXcluster Software

SOFTWARE WARRANTY

How to Read Charts

Warranty for this software product is provided by
DIGITAL with the purchase of a license for the product
as defined In the Software Warranty Addendum of this
SPD.

• The first column lists the VAX system, the devices
(tape, disk, or COROM) from which the VMS
Operating System can be loaded onto the system
disk, and the maximum number of bus(ses) supported
on the system.

VMS, VAXciuster, and DECnet-VAX Supported
Hardware
This section of the SPD contains three parts: Hardware
Charts, Appendix A, and Appendix B.
The charts list the hardware that VMS, DECnet-VAX, and
VAXcluster Software support. The minimum hardware
configuration must include a load device and a system
disk. Combinations of hardware options are subject to
limitations such as bandwidth, physical configuration
constraints, and electrical load and power supply.
Appendix A describes system-specific restrictions for the
configurations listed.
Appendix B describes DIGITAL terminals, disks, tapes,
controllers, communications options, and VAXcluster options. Some restrictions for specific devices are listed if
applicable.
The content of this hardware configuration appendices is
Intended to be a general guide and does not describe all
possible hardware configurations or circumstances. Any
particular configuration should be discussed with
DIGITAL. Contact DIGITAL for the most up-to-date information on possible hardware configurations.
DIGITAL reserves the right to change the number and
type of devices supported by VMS, OECnet-VAX, and
VAXcluster Software. The minimum hardware requirements for future versions and updates of VMS, VMS

SPD Number
2S.03.xx
29.7S.xx

• The second column lists the disk controllers and
drives that can be used on the system. A disk
controller can be used with any disk drive listed next
to it: for example, on a MicroVAX II or VAXstation II
system, the RODX3 disk controller can be used with
an ROS2, RDS3, ROS4, RXSO. or RX33 disk drive.
• The third column lists the tape controllers and drives
that can be used on the system. The tape controller
can be used with any tape drive listed next to it: for
example, on a MicroVAX II or VAXstation II system,
the TOK50 controller can be used with the TK50 tape
drive.
• The fourth column lists the communications options
(synchronous and asynchronous) available for the
system. See the Load Unit Table in the OECnet-VAX
SPO to calculate the number of adapters allowed on
each system.
• The fifth column lists the VAXcluster options (Ethernet
and Computer Interconnect) available for connecting
systems into VAXcluster Configurations. The listed
Ethernet devices also may be used for network con.
nections.
• The sixth column lists other hardware that can be
used and the maximum amount of memory allowed
on the systems in each category.

- 11 -

SPD 25.01.31

VMS Operating System, Version 5.1

SYSTEM

DISKS
DRIVE
CTRL

RQDX1
MicroVAX I
VAXstation I
(LOAD DEVICE)
RX50 ""
KLESI
(BUS)
1 Q-bus

TAPES
DRIVE
CTRL

VAXCLUSTER
COMMUNICATION
OPTIONS
( Ethernet/Cf)
OPTIONS

RD51
RD52
RX50

(Asynch)
DZV11
DHV11 "
DZQ11

(Ethernet)
DEQNA +

MISCELLANEOUS
VCB01-KP (VSI)
4 MB max mem

RC25

Can be used on a MicroVAX I system only.

...... RX50 diskette is not a VMS distribution media .

+ VAXcluster Software does not support this option. MicroVAX I and VAXstation I systems are not supported in a VAXcluste
system.
KDA50
MicroVAX"
VAXstatlon II
(LOAD DEVICE)
TK50
Magtape
RX33
RQDX2
RRD50
(BUS)
1 Q-bus

RA60 "
RA80 ...
RA81 ...

RQDX3

RD52
RD53
RD54
RX50
RX33
RRD50
RC25

KRQ50
KLESI

...

TQK50

TK50

TQK70

TK70

TSV05

TS05

KLESI

TU81-Plus ..
RV20 "

(Asynch)
CXA16 "+
CXB16 "'+
CXY08 ..
DZV11
DHV11 '"
DHQ11 .
DZQ11

RA82 •
RD51
RD52
RD53
RX50

(Ethernet)
DEQNA
DELQA

DRV11-WA ..
LPV11
VCB01-KP (VSII)
VCB02-B (VSII/GPX)
VCB02-D (VSII/GPX)
RQDXE
16 MB max mem

(Synch)
DMV11
DSV11

Can be used on a MicroVAX " system only .

+ DECnet-VAX does not support these options.
MlcroVAX 2000
Integral
V AXstation 2000
(lOA~&VICE)
RX33
(BUS)
NlA

RD32
RD53
RD54
RX33

TZK50

TK50

(Asynch)
Integral serial
Controller +
DHT32·+

(Ethernet)
DESVA

VS40X (VS2000)
14 MB max mem

($ynch)
DST32·+

Can be used on a MicroVAX 2000 system only.

+ DEC net-VAX does not support the DHT32. See the appendices for further DEC net-VAX restrictions.
VAXstation 3200 RQDX3
(LOAD DEVICE)
TK50
(BUS)
1 Q-bus

RD53
RD54

TQK50/07 TK50

(Asynch)
DHV11

TSV05

DZQ11

TS05

(Synch)
DSV11

- 12 -

(Ethernet)
DELQA

Graphic Subsystem
for the VS 3200
32 MB max mem

SPD 25.01.31

VMS Operating System, Version 5.1

- C;ontnued
SYSTEM
MicroVAX

3300/3400

DIS.KS
CTRL
DRIVE
Integral
DSSI

RF30

TAPES
CTRL
DRIVE
TQK70
TQK50

VAXCLUSTER
OPTIONS
COMMUNICATION
(Ethernet/CI)
OPTIONS
(Asynch)
CXA16 +
CXB16 +
CXY08

TK70
TK70

VAXserver

3300/3400

MISCELLANEOUS

(Ethernet)
Imbedded
Controller
28 MB max mem

(LOAD DEVICE)
TK70
(BUS)
1 DSSI
1 Q-bus
+ DEC net-VAX does not support these options.

(Synch)
DSV11

TQK70
TK70
MlcroVAX 3500
RQDX3
RD53 •
VAXstatlon 3500
RD54 •
TSV05
TS05
VAXserver 3500
KDA50
RASO
(LOAD DEVICE)
RA70
TU81-Plus
KLESI
TK70
RA80
RV20
RA81
Magtape
RA82
(BUS)
1 Q-bus
Can be used on a MicroVAX 3500 system only .

(Asynch)
CXA16 +
CXB16 +
CXY08
(Synch)
DSV11

(Ethernet)
DELQA
DESOA

Graphic Subsystem
for the VS 3500
64 MB max mem

(Asynch)
CXA16 +
CXB16 +
CXY08

(Ethernet)
DELQA
DESOA

LPV11-SA

(Ethernet)
DEBNK

3 disk drives max

+ DECnet-VAX does not support these options.
MicroVAX 3600
KDA50
RA60
TOK70
VAXserver 3600
RA70
RA80
TSV05
VAXserver 3602
(LOAD DEVICE)
RA81
KLESI
RA82
TK70
Magtape
(BUS)
1 Q-bus
+ DECnet-VAX does not support these options.

TK70
TS05
TU81-Plus
RV20

(Synch)
DSV11

DEBNK TK50
VAXstation 8000 KRBTA
RD53
(LOAD DEVICE)
RD54
TK50
(BUS)
VAXBI
•• High Performance Workstation Software is needed in addition to VMS.

- Continued

- 13 -

64 MB max mem

32 MB max mem

VMS Operating System, Version 5.1

SYSTEM

DISKS
CTRL
DRIVE

VAX-111725
(UNIBUS)
VAX-111730
UDA50
RA60
(LOAD DEVICE)
RA80
RA81
RC25 •
RL02 **
RA82
RA60 ••
Magtape **
RK711
RK07
(BUS)
RL02··
1 UNIBUS
RL211

SPD 25.01.31

TAPES
CTRL
DRIVE

VAXCLUSTER
COMMUNICATION
OPTIONS
OPTIONS
( Ethernet/CI)

(UNIBUS)
TS11
TU80
TU81

TS11

KLESI

TU81-Plus

(Ethernet)
DEUNA +
DELUA +

(Synch)
DMF32

RX211
RUX50
KLESI

(Asynch)
DMF32
DZ11
DZ32
DMZ32
DHU11

RX02 **
RX50
RC25 •
(INTEGRAL)
IDC
RL02
RSO

MISCELLANEOUS
CR11
DR11-W
DMF32-LP
LP11
LPA11
FP730

3 MB max mem
(VAX-111725)

DMR11

5 MB max mem
(VAX-111750)

Can be used on VAX-111725 systems only.

•* Can be used on VAX-111730 systems only.
+ VAXcluster Software does not support the option. The VAX-111725 and VAX-111730 systems are not supported
In VAXcluster systems.
VAX-111750
(UNIBUS)
(L9AD DEVICE) UDA50
RA60
RL02
RASO
RK07
RA81
RA60
RA82
MAGTAPE
(BUSSES)
RK711
RK07
2 UNIBUS
3 MASSBUS
RL02
R~211
RX211
KLESI
RX02
RUX50
RC25
RX50
(MASSBUS)
RM03
RM05
RMSO
RP06
RP07
VAX-11I7SO
(UNIBUS)
VAX-1117as
UDA50
RA60
(LOAD DEVICE)
RASO
RK07
RA81
RA60
RA82
Magtape
(BUSSES)
RK711
RK06
4 UNIBUS
RK07
4 MASSBUS
RL211
RL02
RX211
KLESI

RX02
'RC25

RUX50

RX50

(MASSBUS)
RM03
RM05
RMSO
RP05
RP06
RP07

(UNIBUS)
TS11
TU80
TU81

TS11

KLESI

TU81-Plus
RV20

TUK50

TK50

(Asynch)
DMF32
DZ11
DZ32
DMZ32
DHU11

(Ethernet)
DEUNA
DELUA
(CI)
C1750

DR11-W
DR750
DW750
FP750
H7112
KU750
14 MB max mem

(Synch)
DMF32
DMR11

(MASSBUS)
TM03
TE16
TU77
TM78

TS11

TU78
(UNIBUS)
TS11
TU80
TU81

KLESI

TU81-Plus
RV20

TUK50

TK50

(MASSBUS)
TM03
TE16
TU45
TU77
TM78
TU78

• 14 •

(Asynch)
DMF32
DZ11
DZ32
DMZ32
DHU11
(Synch)
DMF32
DMR11

(Ethernet)
DEUNA
DELUA
(CI)
CI780

DR11-W
DR7SO
DW7SO
H7112
FP780
KE780
KU7SO
64 MB max mem

VMS Operating System, Vers,lon 5.1

SPD 25.01.31

- Continued
SYSTEM

DISKS
CTRL
DRIVE

VAX 8600
(UNIBUS)
VAX 8650
UDA50
RA60
(LOAD DEVICE)
RASO
Magtape
RA81
(BUSSES)
RA82
7 UNIBUS
6 MASSBUS
RL211
RL02
2 SBI
RX211
RX02
RUX50
RX50
KLESI
RC25
(MASSBUS)
RM03
RM05
RMSO
RP05
RP06
RP07
(INTEGRAL)
IDTC
RA60
RASO
RA81
RA82
TU81
VAX 8200
(VAXBI)
VAX 8250
KDB50
RAGO
(LOAD DEVICE)
RASO
Magtape
RA81
RA60
RA82
(BUSSES)
1 VAXBI
1 UNIBUS

TAPES
CTRL
DRIVE
(UNIBUS)
TS11
TU80
TU81

(Asynch)
DMF32
DZ11
DZ32
DMZ32
DHU11
(Synch)
DMF32
DMR11

(Ethernet)
DEUNA
DELUA

(Asynch VAXBI)
DHB32
DMB32

(Ethernet)
DEBNA
DELUA

TU80
TU81-Plus
TK50

(Asynch UNIBUS)
DHU11
DMF32
DMZ32
(Synch VAXBI)
DMB32
DSB32

(CI)
CIBCA-AA
CIBCI

KLESI

(VAXBI)
TU81-Plus
RV20

(Asynch VAXBI)
DHB32
DMB32

(Ethernet)
DEBNA
DELUA

TS11

(UNIBUS)
TU80
TU81-Plus

(Asynch UNIBUS)
DHU11
DMF32
DMZ32

(CI)
CIBCA-AA
CIBCI

TS11

KLESI

TU81-Plus
RV20

TUK50

TK50

(CI)
CI780

MISCELLANEOUS
DR11-W
DR7SO
FP86-AA
260 MB max mem

(MASSBUS)
TM03
TE16
TU77
TM78

TU78

KLESI

(VAXBI)
TU81-Plus
RV20
(UNIBUS~

TS11
TUK50

VAX 8300
(VAXBI)
VAX 8350
KDB50
RAGO
(LOAD DEVICE)
RASO
Magtape
RA81
RA60
RA82
(BUSSES)
1 VAXBI
1 UNIBUS

VAXCLUSTER
COMMUNICATION
OPTIONS
OPTIONS
( Ethernet/CI)

TUK50

TK50
(Synch VAXBI)
DMB32
DSB32

- -Continued

- 15 -

DMB32-LP
DR11-W
DWBUA
LP11
128 MB max mem

SPD 25.01.31

VMS Operating System, Version 5.1

f
d
- Conlnue
SYSTEM

DISKS
CTRL
DRIVE

VAX 85xx
(VAXBI)
RA60
(LOAD DEVICE) KDB50
RA80
Magtape
RA81
(BUSSES)
2 VAXBI
RA82
1 UNIBUS

VAX 8700
(VAXBI)
VAX 8800
KDB50
RA60
(LOAD DEVICE)
RA80
RA81
Magtape
(BUSSES)
RA82
4 VAXBI
2 UNIBUS

VAXCLUSTER
COMMUNICATION
OPTIONS
OPTIONS
( Ethernet/CI)

TAPES
DRIVE
CTRL
KLESI

KLESI

(VAXBI)
TU81-Plus
RV20

(Asynch VAXBI)
DHB32
DMB32

(Ethernet)
DEBNA
DELUA

(Asynch UNIBUS)
DHU11
DMF32
DMZ32
(Synch VAXBI)
DMB32
DSB32

(CI)
CIBCA-AA

(Asynch VAXBI)
DHB32
DMB32

(Ethernet)
DEBNA
DELUA

(Asynch UNIBUS)
DHU11
DMF32
DMZ32

(CI)
CIBCA-AA

MISCELLANEOUS
DMB32-LP
DR11-W
DWBUA
LP11
256 MB max mem

DMB32-LP
DR11-W
DWBUA
LP11
512 MB max mem

CIBCI

(Synch VAXBI)
DMB32
DSB32
(VAXBI)
VAX 6210/6220
VAX 6230/6240
KDB50
RA60
VAX 6210
RA80
VAX 6220
RA81
(LOAD DEVICE)
RA82
TK50
(BUSSES)
6 VAXBI
1 UNIBUS ..

KLESI

(VAXBI)
TU81-Plus

(Asynch)
DMB32
DHB32

(Ethernet)
DEBNA

(Synch)
DMB32
DSB32

(CI)
CIBCA-AA
CIBCA-BA

LP11 ..
DMB32-LP
DR11-W"
DWBUA ..
256 MB max mem

.. The DweUA UNIBUS adapter is supported on the VAX 6210 and VAX 6220 systems only.

VAX 8810 ..
(VAXBI)
VAX 8820
RA60
KDB50
VAX 8830
RA80
VAX 8840
RA81
(LOAD DEVICE)
RA82
Magtape
(BUSSES)
6 VAXBI
1 UNIBUS

KLESI

(VAXBI)
TU81-Plus

(Asynch)
DMB32
DHB32
(Synch VAXBI)
DMB32
DSB32

(Ethernet)
DEBNA
(CI)
CIBCA-AA
CIBCA-BA

LP11'
DMB32-LP
DR11-W
DWBUA
512 MB max mem

.. The VAX 8810 can support up to a maximum of 4 VAXBls.
Note:

The VMS software that runs on the MicroVAX console subsystem is licensed for use only with standard
oonsole activities. No other use is intended or implied.

Note:

The Wide Area Network Software product contains the synchronous device drivers and is required for the use
of the synchronous oommunication option. Refer to SPD 29.64.xx for more information.

Note:

The VMS software that runs on the MicroVAX
console subsystem is licensed for use only with
standard console activities. No other use is intended or implied.

Note:· The Wide Are Network Software Product contains the synchronous device drivers and is required for the use of the synchronous communication option. Refer to SPO 29.64.xx for more
information.

Appendix A
This appendix describes some restrictions to the system
configurations listed in the charts. See the VAX System
and
Options
Catalog
and
the
Network
and
Communications Buyers Guide for details of VAX
hardware configurations.

- 16 -

SPD 25.01.31

VMS Operating System, Version 5.1

MlcroVAX , I VAXststlon , Systems

VAX 82xx / VAX 83xx Systems

The VMS oeCwindows environment Is not supported on
these systems.

The VAX 82xx and the VAX 83xx series systems support
up to a maximum of four KDB50 disk controllers for
configuration 2 systems and a maximum of two KDB50
controllers for configuration 1 systems.

Micro VAX II System
The CX series boards can be used In a BA213 cabinet
only.

MlcroVAX 2000 and VAXstatlon 2000 Systems
OECnet-VAX supports only one asynchronous
data/modem RS-232C serial line up to 9600 baud on the
Integral 4 line asynchronous controller.

VAXserver 3602 System

The VAX 82xx and the VAX 83xx series systems support
a maximum of three TU80 or TU81-Plus tape drives per
system for configuration 2 systems and one TU80 or
TU81-Plus drive for configuration 1 systems.
One TUK50 tape controller per system is supported.

VAX 8600 and VAX 8650 Systems
Two CR11 Card readers are supported per system.

The VAXserver 3602 is two VAXserver 3600 systems.

VAX-111725 and VAX-111730 System
The VAX-111730 system supports additional memory to· a
maximum of 5 MB for systems configured with R80/RL02
or dual RL02 disks. Other VAX-11 f130 system configurations support a maximum of 3 MB of memory.
A maximum of two RL02 disk drives can be added to the
dual RL02 and the R80/RL02 configuration for the
VAX-111730 only.
The VAX-111725 and the VAX-11f130 systems supports
one UNIBUS magnetic tape subsystem.
Refer· to the Hardware System and Options Catalog for
the different hardware options supported on these systems.

The VAX 8600 and tI1e' VAX 8650 systems can support
up to four TU80, TU81 or TU81-Plus magnetic tape
drives per UNIBUS.

VAX 85xx, VAX 8700 and VAX 8800 Systems
The VAX 85xx. VAX 8700 and VAX 8800 systems support a maximum of two TU81-Plus tape drives per VAXBI
channel to a maximum of four TU81-Plus tape drives per
system.
On systems configured with 512 MB of memory. only
511.5 MB is addressable by VMS. The upper .5MB of
memory is reserved.

VAX 8810, VAX 8820, VAX 8830, VAX 8840
Systems

The VMS OECwindows environment is not suported on
these systems.

On systems configured with 512 MB of memory, only
511.5 MB is addressable by VMS. The upper .5MB of
memory is reserved.

VAX-111750 System

Appendix B

The VAX-11I7SO system must be at a minimum hardware ECO Revision of 4. However, If the VAX-11f150
system has a CI7S0 adapter or a UOA5O controller, the
system must be at a minimum hardware ECO Revision of
S.lf the VAX-11I7S0 system has both a CI750 adapter
and a UOASO controller, the system must be at a minimum hardware eco Revision of 7.

This appendix describes DIGITAL terminals. disks,
tapes. controllers. communications options. and
VAXcluster options.

If the VAX-11I7S0 system has a CI7S0 adapter and a
UOASO controller the UOASO controller must be at
REV S.
One DR7S0 high performance, general purpose interface
is supported. However the DR750 interface and the
CI750 adapter are not supported on the same system.
The VAX-11f15O system console 1U58 tape cartridge
only can be used as console media and not as a storage
device.
The VAX-11I7S0 system can support up to two magnetic
tape SUbsystems.

VAX-111780 and VAX-111785 Systems

Terminals and Terminal Line Interfaces
To prevent input from overflowing a buffer. terminals use
the ASCII control characters DC1 and DC3 for synchronization as defined by DIGITAL's DEC STD 111,
Revision A.
The following table lists the terminals that are supported
by VMS:
VT52
VT300-series

VT100-series
LA-series

VT200-series
LQP02

Terminals on Professional 350. R~inbow 100, and
DECmate II systems· emUlate VT100 terminals.
Only limited support is available for the VTS2. The
VT131. when running an application. operates in block
mode. When interacting with VMS and its associated
utilities. the VT131 only operates in VT100 (or
interactive) mode and not in block mode.

The VAX-11f180 and the VAX-111785 systems can support up to two UNIBUS magnetic tape subsystems.

- 17 -

SPD 25.01.31

VMS Operating System, Version 5.1

Disks
(MSCP)

RA82

205 MB removable disk
drive
280 MB fixed disk drive
128 MB fixed disk drive
456 MB fixed disk drive
622 MB fixed disk drive

RA90

1.2 GB fixed disk drive

(MSCP)

RC25 +

2 disks each 26 MB (1
fixed and 1 removable )
disk drive with shared
spindle

(a-bus,
UNIBUS)

RASO
RA70

RA80
RA81

RD32 +

(MSCP)
(MSCP)
(MSCP)
(MSCP)

(a-bus)
(O-bus)
(O-bus)

RD54

159 MB fixed disk drive

(a-bus)

RF30

150 MB fixed disk drive

(DSSI)

RK06* + 14 MB removable disk drive (UNIBUS)
28 MB removable disk drive (UNIBUS)

RL02* + 10MB removable disk drive (UNIBUS)
RM03 +
RM05
RMSO
R80 +

67 MB removable disk drive (MASSBUS)
256 MB removable disk
(MASSBUS)
drive
124 MB fixed disk drive
(MASSBUS)

+ Device cannot be used as a VMS system disk with

VMS DECwindows environment.

Tapes
TK50

TE16

RP05 +

88 MB removable disk drive (MASSBUS)

RP06

176 MB removable disk
(MASSBUS)
drive
516 MB fived disk drive
(MASSBUS)
(2.2 MB/sec transfer rate is supported if
the RH780 is at REV B1 or greater for
the VAX-11n8O, VAX-11nS5, VAX 8600
and VAX 8650)

(UNIBUS)
RX02* + 512K byte diskette
The RX02 drive also writes using
single-density RX01 diskettes.
RX50* + 400K byte diskette

(a-bus)

RX33* + 1.2 MB diskette
Requires minimum RODX3
microcode of Version 3.0.

(O-bus)

95 Me,S 1/4" streaming
tape cartridge
296 MB, 5 1/4" streaming
tape cartridge

(O-bus)

9 track magnetic tape

(MASSBUS)

(a-bus)

TUn
9 track magnetic tape
(MASSBUS)
TU78
9 track magnetic tape
(MASSBUS)
TU80
9 track magnetic tape
(UNIBUS)
TU81
9 track magnetic tape
(UNIBUS)
TU81·Plus Streaming 9 track magnetic (a-bus,
tape
UNIBUS,
VAXBI)
TS05
TS11

9 track magnetic tape
9 track magnetic tape

(O-bus)
(UNIBUS)

Controllers
DMB32-LP

VAXBI DMA parallel high speed line
printer controller

DMF32-LP

UNIBUS DMA parallel high speed line
printer controller for VAX-11/725 and
VAX-11n30 systems

HSC50

Hierarchical Storage Controller for
MSCP disks and TMSCP tapes. (HSC
Software, minimum Version 3.50 must
be running for dual porting of TA-series
tape drives.)

HSC70

Hierarchical Storage Controller for
MSCP disks and TMSCP tapes. (HSC
Software, minimum Version 3.50 must
be running for dual porting of TA-series
tape drives.)

IDC

Integrated
Disk
Controller
for
VAX-11 n25 and VAX-11 n30 systems

IDTC

Integral Disk and Tape Controller for
VAX 8600 and VAX 8650 systems

LPA11-K

Microprocessor controller for laboratory
acquisition 1/0 devices. accomodating
up to two AD11-Ks. one AA 11-K. one
KW11-K, two AM11-Ks, and five
DR11-Ks. One LPA11-K controller is
supported per UNIBUS and a maximum of two are supported per system

124 MB fixed disk drive for
VAX-11n25 and VAX·11n30

RRD50* + 600 MB Read Only Optical (a-bus)
disk drive

RP07

* Device cannot be used as a system disk.

TK70

42 MB fixed disk drive for MicroVAX 2000
and VAXstation 2000.

RD51* + 10 MB fixed disk drive
RD52 + 31 MB fixed disk drive
RD53 + 71 MB fixed disk drive

RK07 +

RV20· + 2GB Write Once Read
(O-bus, UNIMany Optical disk
BUS, VAXBI)
Cannot be used as a system disk. VMS
treats as tape device.

- 18 -

VMS Operating System, Version 5.1
KOA50

O-hus MS~P disk contro"-.r - The
KDA50 disk contoller supports up to
following
drives:
four
of
the
RA60,RA70,RASO, RA81 and RA82

KDB50

VAXBI MSCP disk controller - The
KDB50 disk controller supports up to
four of the following drives: RA60,
RA80, RA81, and RA82

KlESI

a-bus, UNIBUS and VAXBI tape controller for the TU81-Plus, RV20 or
RC25.

KRa50

a-bus Controller fOr the RRD50 "compact disk reader

lP11

UNIBUS parallel high speed line printer
controller for the lPxx printers.

lPV11

Q-buS parallel high speed line printer
controller

RK711

UNIBUS Disk controller for RK07 disk
drives

Rl211

UNIBUS Disk controller for the Rl02
disk drive

RaDXx

a-bus Disk controller for MicroVAX
and VAXstation systems. There is a
RaDX1, RaDX2 and a RaDX3. The
RaDXx disk controller supports as
many as 4 disk units, with each RX50
diskette drive counting as two units.
Due to controller limitations the system
supports a maximum of 4 devices; the
number of RD/RX devices the system
supports depends on the enclosure.
The RaDX3 disk contoller is required
for the RD54 and the RX33 drives.

SPD 25.01.31
UDASO

UNIBUS MSCP disk controller. The
UDA50 controller must have a minimum microcode version of REV 3. The
UDA50 controller supports up to 4 of
the following disk drives: RA60, RASO,
RA81, and RA82

MASSBUS AdapterlTape Subsystems
These include a MASSBUS "adapter. a tape formatter.
and a transport (a TU77 for the TxUn subsystems, a
TE16 transport for TxE16 SUbsystem, or a TU78 for the
TEU78 subsystem).
A maximum of three additional TU77 magnetic tape
transports can be added to a TxUn subsystem and a
maximum of seven additional TE16 magnetic tape trans~
ports can be added to a TxE16 subsystem. Different
magnetic tape transports cannot be mixed on the same
tape subsystem.
With disks and magnetic tape transports mixed on the
same MASSBUS, the following rules apply:
• Disks can be added to a magnetic tape SUbsystem, to
a maximum of seven additional disks per tape
subsystem.
• Tapes cannot be added to a disk subsystem.

Asynchronous Terminal Controllers
CXA 16

16 line serial terminal multiplexer
(DEC-423), maximum baud rate sup-"
ported: 19200. (No modem control)
(a-bus)

CXB16

16 line serial terminal multiplexer
(RS422), maximum baud rate supported: 19200. (No modem control)
(a-bus)

CXY08

8 line serial terminal" multiplexer
(RS232), maximum baud rate supported: 19200. (Full modem control)
(O-bus)

RX211

UNIBUS Diskette controller for two
RX02 drives. One RX211 diskette
controller is supported per system

RUX50

UNIBUS" Diskette controller for RX50
drives. One RUX50 diskette controller
is supported per system

DHB32

TM03

MASSBUS tape controller for the TE16
and TU77 magnetic tape drives

16 line asynchronous terminal controller for VAXBI, maximum baud rate
supported: 19200. (VAXBI)

DHF11

TM78

MASSBUS tape controller for the TU78
magnetic tape drive

32 line asynchronous terminal controller (DEC 423), maximum baud rate
supported: 19200. (No modem control)
(a-bus)

TaK50

Q-bus tape contoller for the TKSO cartridge tape drive

DHT32

TOK70

Q-bus tape controller for the TK70 cartridge tape drive

8 line asynchronous terminal controller
(DEC 423) (No modem control)
(MicroVAX 2000)

DH011

TSV05

a-bus tape controller for the TS05
magnetic tape drive

TS11

UNIBUS tape controller for the TS11
magnetic tape drive

8 line asynchronous terminal controller
(EIA RS-232-C or RS-423-A), maximum baud rate supported: 19200. (Full
modem control) (O-bus)

DHU11

TUK50

UNIBUS tape controller for the TK50
cartridge tape drive. One TUK50 tape
controller supported per system

16 line asynchronous terminal controller (RS-232-C), maximum baud rates
supported: VMS 19200, DECnet-VAX
9600. (Full modem control) (UNIBUS)

- 19 -

SPD 25.01.31

VMS Operating System, Version 5.1
With ItR next major funetlnnAI relf!t8se.
DECnet-VAX will retire support for this
device when used on a DWBUA UNIBUS adapter on a VAXBI.
DHV11

DMB32

a line asynchronous terminal controller
(EIA RS-232-C or RS-423-A), maximum baud rate~ supported: VMS
19200, DECnet-VAX 9600. (Full modem control) (a-bus)
a line asynchronous terminal controller,
maximum baud rates supported: VMS
supports 19200, DECnet-VAX supports 9600. (Full modem control)
(VAXBI)

DMF32

aline asynchronous terminal controller,
maximum baud rates supported: VMS
supports 19200, DECnet-VAX supports 9600. (Full modem control on first
2 lines) (UNIBUS)

DMZ32

24 line asynchronous terminal controller (EIA RS-232-C or RS-423-A ), maximum baud rates supported: VMS supports 19200, DECnet-VAX supports
9600. (Modem support dependent on
configuration) (UNIBUS)
With its next major functional release,
DECnet-VAX will retire support for this
device when used on .a DWBUA
UNIBUS adapter on a VAXBI.

DZ11

DZ32

DZ011

DZV11

a line asynchronous terminal controller
(EIA
RS-232-C
or
RS-423-A),
maximum baud rate supported: 9600.
(Partial modem control) (UNIBUS)
a line asynchronous terminal controller
(EIA
RS-232-C
or
RS-423-A).
maximum baud rate supported: 9600.
(Partial modem control) (UNIBUS)
4 line asynchronous terminal controller
(EIA RS-232-C or RS-423-A), maximum baud rate supported: VMS supports 19200, DECnet-VAX supports
9600. (Partial modem contol) (a-bus)
4 line asynchronous terminal controller
(EIA RS-232-C or RS-423-A), maximum baud rate supported: VMS supports 19200, DECnet-VAX supports
9600. (Partial modem control) (a-bus)

Synchronous Controllers
The Wide Area Network Software Product contains the
synchronous device drivers and is required for the use of
the synchronous communication option. Refer to SPD
29.64.xx) for more information.
DMB32

Point-ta-point synchronous interface
(VAXBI)

DMC11

High speed local point-ta-point synchronous interface
Retired Device no longer offered as an
option. (UNIBUS)

DMF32

Point-ta-point or multipoint synchronous interface (UNIBUS)

DMP11

Point-ta-point or multipoint synchronous interface (UNIBUS)
Retired Device no longer offered as an
option.

DMR11

Remote point-to-point synchronous interface (UNIBUS)
Replaces DMC11.

DMV11

Point-ta-point or multipoint synchronous Interface (a-bus)

DSB32

Two line, multiple protocol, synchronous adapter (VAXBI)

DST32

Synchronous single line support for
DDCMP up to 9.6 kilobits/second, full
duplex for MicroVAX 2000 systems.
Concurrent use with the DHT32 is not
supported.

DSV11

Synchronous, 2 line, half or full duplex
point-to-point communication interface
supporting DDCMP (1 or 2 lines up to
64 kbps)

Ethernet Options
DEUNA

Ethernet to UNIBUS controller

DELUA

Ethernet to UNIBUS controller - The
minimum revision level required is F1.

DEBNA

Ethernet to VAXBI communication controller

DESVA

Ethernet controller interface

DEaNA

Ethernet Controller to a-bus. The minimum revision level required is K3. All
systems utilizing a DEONA must operate with software data checking enabled. Since AUTOGEN will automatically set the correct parameter. no
system management intervention is required.

DELOA

Ethernet Controller to a-bus. This is
the replacement for DEaNA. The minimum revision level required is C3.

Integral asychronous serial lines for the MicroVAX 2000
and the VAXstation 2000.
On the MicroVAX 2000, one line is the modem/data line
and three are data-only lines. On the VAXstation 2000,
the lines support keyboard, mouse, modem connection.
and printer or plotter. DECnet-VAX supports only one
asynchronous data/modem RS-232C serial line up to
9600 baud on the integral 4 line asynchronous controller.

- 20 -

SPD 25.01.31

VMS Operating System, Version 5.1
Di9it~1

CIOptlons

DSSI

VAXcluster Software supports one CI adapter per
system.

DWBUA

VAXBI to UNIBUS adapter

DW750

UNIBUS Adapter for second UNIBUS
for the VAX-11fl50 system.

FP730

Floating Point Accelerator for the
VAX-11 fl30 system.

FP750

Floating Point Accelerator for the
VAX-11fl50 system.

FP780

Floating Point Accelerator for the
VAX-11 fl80 and VAX-11 fl85 systems.

FP86-AA

Floating Point Accelerator for the VAX
8600 and VAX 8650 systems.

H7112

Memory
battery
back-up
for
VAX-11/750, VAX-11/780, VAX-11/
785, VAX 8600 and VAX 8650
systems. This is
required for
power-fail/recovery.

KE780

G and H floating point microcode for
the VAX-11/780 and the VAX-11fl85
systems.

C1750

CI780

CIBCI

CI Adapter for VAX-11 fl50 systems (Minimum microcode version REV 8 is
required.)
CI
Adapter
for
VAX-11 fl50,
VAX-111780, VAX-111785, VAX 8600,
and VAX 8650 systems. (Minimum
microcode version REV 8 is required.)
CI Adapter for VAXBI systems - (Minimum microcode version REV 8 Is required.)

CIBCA-AA

Native CI Adapter for VAXBI systems (Minimum microcode version REV 5 is
required.)

CIBCA-BA

Native CI Adapter for VAXBI systems

Miscellaneous

Small Storage Interconnect

CR11

Card reader. One CR11 card reader
supported per system. (UNIBUS)

DRV11-WA

General
(Q-bus)

Interface

KU780

DR11-W

General Purpose high speed DMA Interface - One DR11-W interface is supported per UNIBUS

User Writable Control Store for the
VAX-11 fl80 and the VAX-11 fl85 systems.

MA780

High performance general purpose interface for the VAX-11fl50. One
DR750 Interface is supported per system.

Multiport shared memory. A multiple
version VMS V4.7 and VMS V5.x-n
VAXcluster system is not supported if
the system is configured with MA780
memory.

SBI

High performance general purpose interface for the VAX-11 fl80 and
VAX-11fl85. One DR780 interface is
supported per system.

System Backplane Interconnect for the
VAX-11fl80, VAX-11fl85, and I/O
BUS for the VAX 8600 and VAX 8650
systems.

VS40X

4-plane graphics cooprocessor

DR750

DR780

Purpose

DMA

- 21 -