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
• Color or gray-scale rendition is automatically modi-
fied to take advantage of the monitor type through
either direct display, color dithering, or half-toning.
• Display PostScript display routines can be down-
loaded to the server and executed on command.
• Sophisticated graphics primitives, such as precisely
controlled Bezier curves, can be displayed.
The Display PostScript system also allows users to view
PostScript files with such applications as DECwindows
Mail and the CDA Viewer without generating hard copy.
The Terms and Conditions for Display PostScript can be
found in the DECwindows Motif for OpenVMS Software
Product Description (SPD 42.19.xx).
Monitoring Performance History (MPH) Software
Monitoring Performance History software (MPH) is dis-
tributed with the OpenVMS Version 7.1 distribution kit
and is installed separately. Install this software after in-
stalling or upgrading the system to OpenVMS Version
7.1.
MPH is a tool that collects information (such as error
logs, crash dump summaries, configuration, and perfor-
mance data) from the system on which it is installed.
This data is transmitted back to Compaq and is used to
set standard requirements for future releases of Open-
VMS, such as MeanTime Between Crash (MTBCr) and
MeanTime Between System Interruption (MTBSi). The
disk size requirement for MPH installation is approxi-
mately 1200 blocks. MPH requires 300 blocks of disk
space per node after installation.
MPH performs three main functions:
• Captures updates to the error log
• Captures the crash dump profile after the system re-
boots (if the crash dump is enabled and present.)
• Captures changes to the hardware configuration of a
cluster/node.
All data is stored in the MPH copy area (MPH$COPY)
and is transported to DPP on a weekly or daily basis.
MPH can use one of three transport mechanisms to
copy data from the MPH$COPY area:
• DSNLink: MPH data is transferred via DSNLink to
the CSC. The files are then copied from the CSC to
the Compaq processing site via Compaq’s internal
network.
• Internet: MPH data is mailed via Internet directly to
the Compaq processing site.
CONFORMANCE TO STANDARDS
OpenVMS is based on the following public, national, and
international standards.
POSIX and XPG4 BASE Support
The OpenVMS environment, with POSIX for OpenVMS
Version 2.0 and DEC C installed, extends the support
for POSIX standards to include the X/Open BASE spec-
ifications defined in the X/Open Portability Guide, Issue
4 (XPG4). The XPG4 BASE specifications extend the
system application programming interface and shell and
utilities offered in the IEEE POSIX standards. XPG4
also includes standards-based internationalization sup-
port.
The inclusion of XPG4 BASE support in the OpenVMS
environment gives application developers a broader set
of standards-based portability features to incorporate
into their applications. Most applications that strictly
conform to the POSIX and XPG4 specifications can
be developed on an OpenVMS system with POSIX for
OpenVMS and the DEC C compiler, and then ported
without modification to any other platform that also sup-
ports the same POSIX standards and XPG4 specifica-
tions.
Distributed Computing Environment (DCE) Support
The DCE for the OpenVMS product family provides a
set of the distributed computing features specified by
the Open Software Foundation’s (OSF) DCE, as well as
tools for application developers. With DCE, the OSF
has established a standard set of services and inter-
faces that facilitate the creation, use, and maintenance
of client/server applications. DCE for OpenVMS serves
as the basis for an open computing environment where
networks of multivendor systems appear as a single sys-
tem to the user. Because DCE makes the underlying
networks and operating systems transparent, applica-
tion developers can easily build portable, interoperable
client/server applications. Users can locate and share
information safely and easily across the entire enter-
prise. DCE for OpenVMS supplies system managers
with a set of tools to consistently manage the entire
distributed computing environment, while assuring the
integrity of the enterprise.
The DCE for OpenVMS product family currently consists
of the following products:
• DCE Runtime Services for OpenVMS, which is re-
quired for all systems participating in the DCE cell.
The Runtime Services includes DCE client functions
as well as DCE administration tools. DCE Runtime
Services allows client/server applications to interop-
erate over DECnet, TCP/IP, and UDP/IP network pro-
tocols.
19