Specifications

OpenVMS Operating System for Alpha and VAX (Versions 7.1, 7.1–1H1, 7.1–1H2, and 7.1–2) SPD 41.87.06
style property-tab dialogs. Both DECnet and/or TCP/IP
transports are supported on client and server. In addi-
tion, the PATHWORKS client is no longer required.
Restrictions:
• Managing OpenVMS Cluster members as individual
nodes is not supported. OpenVMS Cluster systems
are treated as indivisible entities; an operation cannot
be performed on specific cluster members.
• OpenVMS Cluster systems with multiple UAFs are
not supported.
• PCs currently support TCP/IP and DECnet Phase IV
only.
Supported Software Configurations:
OpenVMS Server Software
Operating System Communication Protocol
OpenVMS VAX V6.1 or higher Digital TCP/IP Services for
OpenVMS V3.2 or higher, or
DECnet for OpenVMS
OpenVMS Alpha V6.2 or
higher
Digital TCP/IP Services for
OpenVMS V3.1 or higher, or
DECnet for OpenVMS
PC Client Software
Operating System Communication Protocol
Microsoft Windows NT, V4.0
and V3.51
Windows Sockets V1.1
Compliant TCP/IP Stack, or
PATHWORKS V5.1 for DOS
and Windows
Microsoft Windows 95 Windows Sockets V1.1
Compliant TCP/IP Stack, or
PATHWORKS V5.1 for DOS
and Windows
Microsoft Windows for Work-
groups, V3.11
Windows Sockets V1.1
Compliant TCP/IP Stack, or
PATHWORKS V5.1 for DOS
and Windows
Microsoft Windows, V3.1 Windows Sockets V1.1
Compliant TCP/IP Stack, or
PATHWORKS V5.1 for DOS
and Windows
Important Notes:
• PATHWORKS for Windows 95 is not supported.
• When running under Windows NT and Windows
95, OpenVMS Management Station supports TCP/IP
connections only.
• OpenVMS VAX Version 6.1 requires a remedial kit
(VAXCXXL01 061) to operate correctly.
• Additional TCP/IP stacks for OpenVMS have not
been tested. However, TCP/IP stacks that are 100%
compliant with the QIO interface for Digital TCP/IP
Servers for OpenVMS should also work. Contact
your TCP/IP vendor for additional information and
support issues.
DECamds
DECamds Version 7.1 is available on the OpenVMS dis-
tribution kit. DECamds is a separately installable, real-
time, high-performance, multisystem monitoring utility.
It is supported on any system running OpenVMS Ver-
sion 7.1. With OpenVMS Version 7.1, the right to use
DECamds is included under the terms and conditions
of the OpenVMS operating system base license (both
Alpha and VAX).
DECamds provides system resource monitoring, inves-
tigation aid, and correction capability. This enables sys-
tem managers to proactively and effectively manage
multiple systems from a centralized DECwindows dis-
play.
The DECamds software includes an OpenVMS device
driver, which runs on every node that is monitored. It
also includes console software, which runs on the cen-
tralized X Window monitoring station.
Batch and Print Queuing System
OpenVMS provides an extensive batch and print capa-
bility that allows the creation of queues and the setup
of spooled devices to process noninteractive workloads
in parallel with timesharing or real-time jobs.
The OpenVMS batch and print operations support two
types of queues: generic queues and execution queues.
A generic queue is an intermediate queue that holds a
job until an appropriate execution queue becomes avail-
able to initiate the job. An execution queue is a queue
through which the job (either print or batch) is actually
processed.
The system queues batch jobs for execution. The sys-
tem manager can regulate the number of queues and
the number of streams per queue (the number of batch
jobs in the queue that can execute concurrently).
Both generic and execution batch queues can have dif-
ferent attributes, such as the maximum CPU time per-
mitted, working set size, and priority. Facilities are pro-
vided for starting and stopping queues and for starting
and stopping jobs in a queue. Because multiple exe-
cution queues can be associated with a generic queue,
OpenVMS VAX enables load balancing across available
CPUs in an OpenVMS Cluster system, increasing over-
all system throughput.
5