Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Overview
VSI OpenVMS Version 8.4-1H1 for Integrity Servers
Introduction
This QuickSpecs describes the VMS Software Inc. (VSI) OpenVMS Operating System software for Integrity servers.
Description
OpenVMS is a general-purpose, multiuser operating system that runs in both production and development environments. Starting
with OpenVMS Version 8.2, HP introduced support for OpenVMS for Integrity servers. VSI OpenVMS Version 8.4-1H1 adds support
for HP Integrity i4 server models based on the Intel® Itanium® 9500 series processors.
OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides
symmetric multiprocessing (SMP) support for multiprocessing systems.
The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of
compute-intensive, I/O intensive, client/server, real-time, and other environments. Actual system performance depends on the type
of computer, available physical memory, and the number and type of active disk and tape drives.
The OpenVMS operating system has well-integrated networking, distributed computing, client/server, multiprocessing, and
windowing capabilities. It contains extensive features that promote ease-of-use, improve the productivity of programmers, and
facilitate system management.
For information about the VSI OpenVMS Version 8.4-1H1 new features, see the VSI OpenVMS Version 8.4-1H1 Cover Letter and
Release Notes.
NOTE: VSI OpenVMS Version 8.4-1H1 is the first release of the OpenVMS computing environment by VMS Software, Inc (VSI). The
following table describes the support status of VSI OpenVMS V8.4-1H1 with different server models.
Supported Servers
Server Model
rx2800 i4
BL860c i4
BL870c i4
BL890c i4
rx2800 i2
BL860c i2
BL870c i2
BL890c i2
VSI OpenVMS 8.4-1H1
Tested
Tested
Tested
Tested
Tested
Tested
Tested
Tested
HP Technical Support Available
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
VSI Technical Support Available
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Note: HP supports VSI OpenVMS V8.4-1H1 on HP Integrity i4 and HP Integrity i2 servers only. For the complete list of servers that
VSI supports, see http://vmssoftware.com/quickspec.
Upgrading to VSI OpenVMS V8.4-1H1
In addition to HP OpenVMS V8.4 with Update 900 or 1000, VSI supports upgrades from earlier versions of OpenVMS.
The following table describes the upgrade paths that VSI supports:
Supported Upgrade Paths
Current Version
Target Version
VSI Technical Support
HP OpenVMS V8.4 Upgrade 900 or 1000
VSI OpenVMS V8.4-1H1
Supported
HP OpenVMS V8.3-1H1
VSI OpenVMS V8.4-1H1
Supported
HP OpenVMS V8.3
VSI OpenVMS V8.4-1H1
Supported
HP OpenVMS V8.2-1
VSI OpenVMS V8.4-1H1
Not supported
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 1
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
User Environment
Users can access the OpenVMS software by using the English-like DIGITAL Command Language (DCL), the command language for
OpenVMS that is supplied with the system. DCL commands provide information about the system and initiate system utilities and
user programs. DCL commands take the form of a command name followed by parameters and qualifiers.
Users can enter DCL commands at a terminal or include them in command procedures. These command procedures can be run
interactively or submitted to a batch queue for later processing. Information about DCL and OpenVMS utilities is available on line
through the OpenVMS Help system.
For users who are familiar with the UNIX shell and utilities, an open source port of GNV is available. GNV implements a UNIX
environment on OpenVMS and includes an Implementation of the UNIX shell BASH (Bourne Again Shell) and many UNIX-shell
utilities.
The following tools and utilities are integrated into the OpenVMS operating system.
Text Processing
The Extensible Versatile Editor (EVE) is the default editor for OpenVMS. EVE allows users to insert, change, and delete text quickly.
EVE is a full-screen editor that allows users to scroll through text on a terminal screen. EVE provides an EDT-style keypad, allowing
EDT users to move easily to EVE.
Mail Utility
The Mail utility allows users to send messages to any other user on the system. Multinode operation is available if a DECnet or
TCP/IP product is installed and licensed on each participating node on the network.
Command Level Programming
Command-level programming allows users to create special files, called command procedures that contain a series of DCL
commands. When users execute a command procedure, the system processes the commands in the command procedure
consecutively.
User Environment Tailoring
Users can customize the computing environment with login command procedures, shorthand commands, binding of commands to
function keys, and command recall and editing.
Program Development Environment
OpenVMS includes a comprehensive set of tools for developing programs, including: run-time libraries (RTLs), a linker, a librarian,
and a symbolic debugger.
The following tools are available to the OpenVMS programmer.
Language and Run-Time Library Support
OpenVMS includes several RTLs that provide:
 String manipulation
 Parallel processing support
 I/O routines
 I/O conversion
 Terminal-independent screen handling
 Date and time formatting routines
 Highly accurate mathematical functions
 Signaling and condition handling
 Other general-purpose functions
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 2
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
With OpenVMS for Integrity servers, these routines can be called from programs written in such languages as MACRO-32, BASIC, C,
C++, COBOL, Fortran, and Pascal.
Also included in OpenVMS are language-support libraries. While each language is different, all provide support for sequential file
I/O, and most support direct and indexed file I/O. Language RTLs also provide support for I/O formatting, error handling, and in
Fortran, the ability to read unformatted files that contain data from other vendors.
RTLs are provided to support translated images created from user-mode images built on OpenVMS Alpha Version 6.1 through
Version 7.3-2.
Calling Standard
Many VSI languages adhere to the common calling standard. This means that routines written in any of these languages can directly
call routines written in any other language. Development of applications using multiple languages is simple and straight forward.
All user-accessible routines in the RTLs follow the appropriate platform calling standard and condition-handling conventions, and
most are contained within shareable images.
At a lower level, programs can call system services directly for security, event flag, asynchronous system trap, logical name, record
and file I/O, process control, timer, time conversion, condition handling, lock management, and memory management. Again,
system services use the appropriate platform calling standard and condition-handling conventions.
OpenVMS supports the execution of user-mode images created on earlier versions of OpenVMS. Typically, recompiling and relinking
are not required.
MACRO Compiler
With minor modifications, VAX MACRO-32 sources can be compiled for execution on Alpha or Integrity servers.
POSIX Threads Library
OpenVMS includes a user-mode, multithreading capability called POSIX Threads Library. POSIX Threads Library provides a POSIX
1003.1-1996 standard style threads interface. Additionally, POSIX Threads Library provides an interface that is the OpenVMS
implementation of Distributed Computing Environment (DCE) threads as defined by The Open Group.
POSIX Threads Library is a library of run-time routines that allows the user to create multiple threads of execution within a single
address space. With POSIX Threads Library Kernel Threads features enabled, POSIX Threads Library provides for concurrent
processing across all CPUs by allowing a multithreaded application to have a thread executing on every CPU (on both symmetric and
asymmetric multiprocessor systems). Multithreading allows computation activity to overlap I/O activity. Synchronization elements,
such as mutexes and condition variables, are provided to help ensure that shared resources are accessed correctly. For scheduling
and prioritizing threads, POSIX Threads Library provides multiple scheduling policies. For debugging multithreaded applications,
POSIX Threads Library is supported by the OpenVMS Debugger. POSIX Threads Library also provides Thread Independent Services
(TIS), which assist in the development of threadsafe APIs.
Librarian Utility
The Librarian utility permits storage of object modules, image files, macros, help files, text files, or any general record-oriented
information in central, easily accessible files. Object module and image file 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 MACRO-32 and MACRO-64 when either finds a
macro name that is not defined in the input file.
Hypersort
Hypersort is a portable library of user-callable routines that provide a high-performance sorting capability for Integrity servers.
Traceback Facility
When an application is compiled and linked with traceback information, the Traceback facility translates stack frame addresses into
routine names and line numbers and displays a symbolic traceback whenever a runtime error occurs in that application.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 3
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
Debugger
The OpenVMS Debugger allows users to trace program execution, as well as display and modify register contents using the same
symbols that are present in the source code.
The debugger contains a heap analyzer feature that displays a graphic view of memory allocations and deallocations in real time.
System Code Debugger
The OpenVMS System Code Debugger is a kernel code debugger. It allows a system code developer to trace the execution of
nonpageable system code at any interrupt priority level (IPL). Based on the OpenVMS Debugger, the System Code Debugger uses
the same interface and most of the same command set.
System Dump Analyzer (SDA) Utility
In the event of a system failure, OpenVMS writes the contents of memory to a preallocated dump file. This dump file can later be
analyzed using System Dump Analyzer (SDA). System dumps can either be full memory dumps, where all memory is written, or
selective memory dumps, where only portions of memory in use at the time of the system failure are written. The dump file can be
located on any locally connected disk. On Integrity servers, dump compression allows both full and selective dumps to be written to
smaller files than required for uncompressed dumps. Full memory dumps, if not compressed, require a dump file big enough to hold
all memory. Selective memory dumps write as much of the memory in use at the time of the system failure that will fit into the
dump file.
Spinlock Tracing Utility
The Spinlock Tracing Utility provides a mechanism for characterizing spinlock usage and can collect performance data for a given
spinlock on a per-CPU basis.
Process Dumps
When an application fails, a copy of its registers and memory can be written to a data file, which can be examined using the
ANALYZE PROCESS utility. This utility uses the same interface and commands as the OpenVMS Debugger to allow registers and
memory to be examined. On Integrity servers, another process can initiate the writing of the memory dump.
RMS File Utilities
Record Management Services (RMS) file utilities allow users to analyze the internal structure of an RMS file and tune the I/O,
memory, space and performance parameters of the file. The RMS file utilities can also be used to create, load, and reclaim space in
an RMS file. For more information about RMS, see the Operating System Environment section of this QuickSpecs.
File Differences Utility
This utility compares the contents of two files and lists those records that do not match.
Translated Image Environment (TIE) (Integrity servers)
OpenVMS for Integrity servers provides an array of services that allow the operation of programs which have undergone binary
translation from OpenVMS Alpha images or VESTed OpenVMS VAX images. These programs perform virtually all user-mode
functions on OpenVMS for Integrity servers and operate in combination with other programs (images) that have been translated
from OpenVMS Alpha or VAX, or have been built using native compilers on OpenVMS for Integrity servers. Without requiring special
source code, the TIE resolves differences between the Alpha and Integrity architectures, including floating-point.
For additional information, refer to the following web site: http://h71000.www7.hp.com/commercial/cace.html (under the Tools
section).
System Management Environment
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 4
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
OpenVMS provides a set of tools and utilities that aid the system manager in configuring and maintaining an optimal system as
follows:
Web-Based Enterprise Management Services for OpenVMS
Web-Based Enterprise Management (WBEM) Services for OpenVMS is an industry standard for monitoring and controlling resources.
It is available and installed automatically with OpenVMS on Integrity server systems. WBEM Services for OpenVMS (WBEMCIM) is
required for use of such features as HP Systems Insight Manager (HP SIM). In addition, WBEM Providers for OpenVMS is installed
automatically with OpenVMS for Integrity servers.
For server blade support, "Providers" are included that enable the monitoring of hardware and the operating system, including:
 Operating system
 Computer system
 Process and processor statistics
 Indication (monitors events)
 Firmware version
 Fan and power supply
 Management Processor
 CPU instance
 Memory instance
 Enclosure
VSI Availability Manager
VSI Availability Manager is a system management tool that enables you to monitor one or more OpenVMS nodes on an extended
local area network (LAN) from either an OpenVMS Alpha system, or an OpenVMS for Integrity server system, or a PC running
Windows. This tool helps system managers and analysts target a specific node or process for detailed analysis and also can resolve
certain performance or resource problems. It is the multiplatform replacement for the DECamds product and includes the DECamds
functionality in its capabilities.
Availability Manager has a wide-area capability whereby any system on the network supporting Availability Manager can be
managed from a central console. Moreover, Availability Manager is enhanced to support Cluster over IP to manage and monitor LAN
or IP path data, and IP interface for cluster communication.
The Data Collector, part of the Availability Manager product, collects system and process data on an OpenVMS node and should be
installed on each node that you need to monitor (Alpha and Integrity servers).
The Data Analyzer analyzes and displays the data collected by the Data Collector, and can analyze and display data from many
OpenVMS nodes simultaneously (OpenVMS Alpha nodes, and PCs running Windows).
Hardware recommendations and related documentation are available via the OpenVMS System Management web page located at:
http://www.hp.com/products/openvms/availabilitymanager/
Class Scheduler for CPU Scheduling
The Class Scheduler is a SYSMAN-based interface for defining and controlling scheduling classes for OpenVMS systems that allows
you to designate the percentage of CPU time that a system's user may receive by placing users into scheduling classes.
Batch and Print Queuing System
OpenVMS provides an extensive batch and print capability that allows the creation of queues and the setup of spooled devices to
process non-interactive 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 available to initiate the job. An execution queue
is a queue through which the job (either print or batch) is actually processed. Because multiple execution queues can be associated
with a generic queue, OpenVMS enables load balancing across available systems in an OpenVMS Cluster system, increasing overall
system throughput.
Print queues, both generic and execution, together with queue management facilities, provide versatile print capabilities, including
support for various print file formats.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 5
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
Accounting Utility
For accounting purposes, OpenVMS keeps records of system resource usage. These statistics include processor and memory
utilization, I/O counts, print symbiont line counts, image activation counts, and process termination records. The OpenVMS
Accounting utility allows you to generate various reports using this data.
Audit Analysis Utility
For security auditing purposes, OpenVMS selectively records critical, security-relevant events in the system security audit log file.
These records contain the date and time the event occurred, the identity of the associated user process, and information specific to
each event type. This information helps the system manager maintain system security and deter possible intruders. The OpenVMS
Audit Analysis utility allows you to generate various reports from this data.
Autoconfigure and AUTOGEN Utilities
The Autoconfigure and AUTOGEN utilities automatically configure the available devices in the system tables and set system
parameters based on the peripheral and memory architecture. This eliminates the need for a traditional system generation process
when the hardware configuration is expanded or otherwise modified.
The OpenVMS AUTOGEN command procedure sets several system parameters automatically by detecting the devices installed in a
configuration. A feedback option allows you to generate a report of recommended parameter settings based on previous usage
patterns.
Backup Utility
The Backup utility provides both full-volume and incremental file backups 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. Files can be selected by
various dates (such as creation or modification) and can be backed up to magnetic tape, magnetic disk, or Write Once Read Many
(WORM) optical disk. The Backup utility can also be used to restore a saveset or list the contents of a saveset.
The Backup utility has been extended to support volume up to 2 TiB. Backup utility has also been enhanced to create and restore a
compressed save set. The compressed save set can be created on disks and magnetic tapes. The compression ratio depends on the
data content in the files.
A Backup API is included for invoking backup routines from an executable procedure.
The Backup Manager for OpenVMS provides a screen-oriented interface to the Backup utility that assists users in performing routine
backup operations. The Backup Manager is menu driven and provides:
 Access to the save, restore, and list operations without having to understand Backup command syntax
 The ability to create, modify, recall, and delete Backup Manager templates that describe the Backup save operations
Recordable DVD
OpenVMS provides the capability on Integrity server systems to record locally mastered disk volumes or disk image files onto a CDR, CD-RW, DVD+R or DVD+RW optical-media recording device on specific drives and configurations.
Recordable CD
OpenVMS provides the capability to write once to CD-R media using an application shipping in the base operating system. The
feature supports only those writable CD devices (CD-RW) that ship with supported Alpha systems and supported Integrity servers.
For the application details, please reference the OpenVMS documentation set. For platforms supporting the CD-RW hardware
option, please refer to the appropriate page at the following web sites:
http://h18002.www1.hp.com/alphaserver/
http://www.hp.com/products1/servers/integrity/index.html
Analyze Disk Structure Utility
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 6
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
The Analyze Disk Structure 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. It can also be used to repair errors detected in the file structure of
disks.
License Management Facility (LMF)
The License Management Facility allows the system manager to enable software licenses and to determine which software
products are licensed on an OpenVMS system.
System Management Utility (SYSMAN)
The System Management utility allows system managers to define a management environment in which operations performed
from the local OpenVMS system can be executed on all other OpenVMS systems in the environment.
HP Services Tools
HP Services provides web-based tools for crash dump analysis and hardware fault isolation. For more information, visit the
following web site: http://h18000.www1.hp.com/support/svctools/
Security
OpenVMS provides a rich set of tools to control user access to system-controlled data structures and devices that store
information. OpenVMS employs a reference monitor concept that mediates all access attempts between subjects (such as user
processes) and security-relevant system objects (such as files). OpenVMS also provides a system security audit log file that records
the results of all object access attempts. The audit log can also be used to capture information regarding a wide variety of other
security-relevant events.
User account information, privileges and quotas associated with each user account is maintained in the system user authorization
file (SYSUAF). Each user account is assigned a user name, password, and unique user identification code (UIC). To log in and gain
access to the system, the user must supply a valid 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 specify how frequently passwords change, along with
minimum password length, and the use of randomly generated passwords.
Operations
OpenVMS allows for varying levels of privilege to be assigned to different operators. Operators can use the OpenVMS Help Message
utility to receive online descriptions of error messages. In addition, system-generated messages can be routed to different
terminals based on their interest to the console operators, tape librarians, security administrators, and system managers.
Security auditing is provided for the selective recording of security-related events. This auditing information can be directed to
security operator terminals (alarms) or to the system security audit log file (audits). Each audit record contains the date and time of
the event, the identity of the associated user process, and additional information specific to each event.
OpenVMS provides security auditing for the following events:
 Login and logout
 Login failures and break-in attempts
 Object creation, access, deaccess, and deletion; selectable by use
of privilege, type of access, and on individual objects
 Authorization database changes
 Network logical link connections for DECnet for OpenVMS, DECnetPlus, DECwindows, IPC, and SYSMAN
 Use of identifiers or privileges
 Installed image additions, deletions, and replacements
 Volume mounts and dismounts
 Use of the Network Control Program (NCP) utility
 Use or failed use of individual privileges
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 7
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
 Use of individual process control system services
 System parameter changes
 System time changes and recalibrations
Every security-relevant system object is labeled with the UIC of its owner along with a simple protection mask. The owner UIC
consists of two fields: the user field and a group field. System objects also have a protection mask that allows read, write, execute,
and delete access to the object's owner, group, privileged system users, and to all other users. The system manager can protect
system objects with access control lists (ACLs) that allow access to be granted or denied to a list of individual users, groups, or
identifiers. ACLs can also be used to audit access attempts to critical system objects.
OpenVMS applies full protection to the following system objects:
 Common event flag cluster
 Devices
 Files
 Group global sections
 Logical name tables
 Batch/print queues
 Resource domains
 Security classes
 System global sections
 ODS-2 volumes
 ODS-5 volumes
OpenVMS provides optional security solutions to protect your information and communications:
 OpenVMS includes encryption for data confidentiality that ships as part of the operating system, thereby removing the
requirement to license and install Encrypt separately. The ENCRYPT and DECRYPT commands, now part of OpenVMS,
support AES file encryption with 128, 192, or 256 bit keys. AES encryption is also supported by BACKUP/ENCRYPT, allowing
for the creation of encrypted tapes and save-sets. The built-in encryption functionality is backward-compatible with file
and backup tapes created by the former layered product Encryption for OpenVMS. This layered product featured 56-bit
Data Encryption Standard (DES), which continues to function today, allowing for the decryption of archived DES encrypted
data. The AES encryption functionality supports Electronic Code Book (ECB) and Cipher Block Chaining (CBC) block modes of
encryption.
The Cipher Feedback (CFB) and Output Feedback (OFB) 8-bit character stream modes are also supported from the
command line as well as by the programmatic APIs.
 Secure Sockets Layer (SSL) for OpenVMS Integrity server systems provides secure transfer of sensitive information over
the Internet
 Common Data Security Architecture (CDSA) is configured and initialized automatically during installation and upgrades and
is required for Secure Delivery purposes and other security features. If you install a newer version of CDSA without
upgrading the base operating system, you must initialize the CDSA software, using the following command. Enter the
command from an account that has both SYSPRV and CMKRNL privileges (for example, the SYSTEM account). $
SYS$STARTUP:CDSA$UPGRADE
 Kerberos for OpenVMS
 Per-Thread Security Profiles
 External Authentication
 Global and Local Mapping of LDAP users
 VSI Code Signing for OpenVMS: OpenVMS kits will be signed using VSI Code Signing Service
NOTE: Users who are externally authenticated by their LAN Manager need only remember a single user name/password
combination to gain access to their OpenVMS and LAN Manager accounts.
NOTE: Because no system can provide complete security, VSI cannot guarantee complete system security. However, VSI continues
to enhance the security capabilities of its products. Customers are strongly advised to follow all industry-recognized security
practices. OpenVMS recommended procedures are included in the HP OpenVMS Guide to System Security.
Operating System Environment
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 8
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
Processes and Scheduling
Executable images consist of system programs and user programs that have been compiled and linked. These images run in the
context of a process on OpenVMS systems. Sixty-four process priorities are recognized on OpenVMS for Integrity servers. Priorities
0 to 15 are for time-sharing processes and applications (four is the typical default for timesharing processes). Priorities 16 to 63 on
Integrity servers are for real-time processes. Real-time processes can be assigned higher priorities to ensure that they receive
processor time whenever they are ready to execute.
OpenVMS uses paging and swapping to provide sufficient virtual memory for concurrently executing processes. Paging and
swapping is also provided for processes whose memory requirements exceed available physical memory.
64-Bit Virtual Addressing
The OpenVMS for Integrity servers operating system provides support for 64-bit virtual memory addressing. This capability makes
the 8 TB virtual address space available to the OpenVMS operating system and to application programs. Future hardware
implementations for Integrity servers will provide greater capacity. OpenVMS applications can take advantage of 64-bit processing
by using 64-bit data types supported by the compilers. For further details, see the SPDs for the OpenVMS for Integrity servers
compilers.
Very Large Memory (VLM) Features
OpenVMS for Integrity servers provide the following additional memory management VLM features beyond those provided by 64bit virtual addressing. These features can be used by database servers to keep large amounts of data in memory, resulting in
dramatically increased runtime performance. The VLM features provided by OpenVMS for Integrity servers are:
 Memory-resident global sections
 Fast I/O for global sections
 Shared page tables
 Expandable global page table
 Reserved memory registry
DECdtm Services
The DECdtm services embedded in the OpenVMS operating system support fully distributed databases using a two-phase commit
protocol. The DECdtm services provide the technology and features for distributed processing, ensuring both transaction and
database integrity across multiple VSI resource managers. Updates to distributed databases occur as a single all-or-nothing
unit of work, regardless of where the data physically resides. This ensures the consistency of distributed data.
DECdtm services allow applications to define global transactions that can include calls to any number of VSI data management
products. Regardless of the mix of data management products used, the global transaction either commits or aborts. OpenVMS is
unique in providing transaction processing functionality with base operating system services.
DECdtm features include:
 Embedded OpenVMS system services that support the DECtp architecture, providing the features and technology for
distributed transaction processing.
 Ability for multiple disjoint resources to be updated automatically. These resources can be either physically disjointed on
different clusters at separate sites, or logically disjointed in different databases on the same node.
 Ability to use the X/Open Distributed Transaction Processing XA interface that enables the DECdtm transaction manager to
coordinate XA-compliant resource managers (the HP DECdtm XA Veneer), and XA-compliant transaction processing
systems to coordinate DECdtm-compliant resource managers (the DECdtm XA Gateway).
 Robust application development. Applications can be written to ensure that data is never in an inconsistent state, even in
the event of system failures.
 Ability to be called using any HP TP monitor or database product. This is useful for applications using several HP database
products.
Interprocess Communication
OpenVMS provides the following facilities for applications that consist of multiple cooperating processes:
 Mailboxes as virtual devices that allow processes to communicate with queued messages.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 9
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features






Shared memory sections on a single processor or an SMP system that permit multiple processes to access shared address
space concurrently.
Common event flags that provide simple synchronization.
A lock manager that provides a more comprehensive enqueue/dequeue facility with multilevel locks, values, and
asynchronous system traps (ASTs).
Intracluster communication services through which two processes running on the same system or on different OpenVMS
Cluster nodes can establish a connection and exchange data.
Logical names through which one process can pass information to other processes running on the same system or on
different OpenVMS Cluster nodes.
Network interprocess communication is available via TCP/IP Services and DECnet-Plus (product licenses are required).
Symmetric Multiprocessing (SMP)
OpenVMS provides symmetric multiprocessing (SMP) support for Integrity servers multiprocessor systems. SMP is a form of tightly
coupled multiprocessing in which all processors perform operations simultaneously. All processors perform operations in all
OpenVMS access modes, user, supervisor, executive, and kernel.
OpenVMS SMP configurations consist of multiple CPUs executing code from a single shared memory address space. Users and
processes share a single copy of OpenVMS for Integrity servers address space. SMP also provides simultaneous shared access to
common data in global sections to all processors. OpenVMS SMP selects the CPU where a process will run based on its priority and in
special cases as directed by the application. OpenVMS uses a specialized scheduling algorithm when running a nonuniform memory
access (NUMA) platform.
SMP support is an integral part of OpenVMS and is provided to the user transparently. Because an SMP system is a single system
entity, it is configured into a network and OpenVMS Cluster configurations as a single node.
VSI OpenVMS V8.4-1H1 supports a maximum of 32 cores in an instance of the operating system.
Networking Facilities
OpenVMS provides device drivers for all local area network (LAN) adapters listed in the LAN Options section of Appendix A of this
document. Application programmers can use the QIO system service to communicate with other systems connected via the LAN
using either Ethernet or Institute of Electrical and Electronics Engineers (IEEE) 802.3 packet format. Simultaneous use of HP
Ethernet and the IEEE 802.3 protocols are supported on any HP LAN adapter.
OpenVMS supports the following networking products:
 VSI TCP/IP Services for OpenVMS, the industry-standard set of protocols for interoperating between different operating
systems
 VSI DECnet-Plus, the Digital Network Architecture, Phase V
 VSI DECnet, the DIGITAL Network Architecture, Phase IV
These networking products are described in this QuickSpec under Associated Products.
Terminal Server Products
HP terminal server products provide terminal server access to OpenVMS. When used in an OpenVMS Cluster environment, terminal
servers distribute users across the available Integrity server systems at login time.
OpenVMS can also establish a connection to other devices (such as printers) attached to such terminal servers.
Universal Serial Bus Support
OpenVMS supports the Universal Serial Bus (USB) technology. Support for the USB interconnect enables OpenVMS systems to
connect to multiple supported USB devices using a single USB cable. OpenVMS supports one USB keyboard and mouse on systems
that are supported by OpenVMS and have USB hardware and a graphics controller.
Starting with HP OpenVMS version 8.3, serial support is provided through the USB serial multiplexer (MUX). OpenVMS supports
several generic chipsets which allow third-party USB-based serial multiplexers to connect to OpenVMS systems for RS232 serial
lines, traditional terminal connections, and low-speed system-to-system connectivity. For more information,
see the following website:
http://h71000.www7.hp.com/openvms/integrity/integrity_io_options.html
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 10
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
OpenVMS provides a USB configuration tool called UCM that can be used to track USB configuration changes like plug and unplug
events. UCM can also be used to restrict the automatic addition of specific devices and classes of devices. The UCM event log is used
by HP to help diagnose problems with USB devices.
Integrity Server Systems
Starting with OpenVMS version 8.3-1H1, OpenVMS supports USB low-, full-, and high-speed devices for all supported OpenVMS
Integrity systems. USB DVD support in OpenVMS version 8.3-1H1 includes both reading and burning DVDs on the following
supported Integrity server systems: rx2660, rx3600, rx6600.
Reliability
OpenVMS handles hardware errors as transparently as possible while maintaining data integrity and providing sufficient
information to diagnose errors. The system limits the effects of an error by first determining if the error is fatal. If the error occurs
in system context, the current OpenVMS system shuts down. If the error is not fatal, the system recovers actions pertinent to the
error and continues the current operation.
In all cases, information relevant to the error is written to the error log file for later analysis. Hardware errors include the following
categories:
 VSI OpenVMS Version 8.4-H1 supports CPU Component Indictment on Integrity servers.
 Processor errors. These include processor soft errors, processor hard errors, processor machine checks, and adapter
errors.
 Memory errors. These can be unrecoverable (hard) errors or recoverable (soft) errors. The system examines memory at
startup time and does not use any bad pages. During system operation, the system corrects all single-bit memory errors
for those systems with error correction code (ECC) memory.
 Correctible memory errors. A primary cause of these correctible memory errors is alpha particle radiation. On some
processors, when correctible memory errors occur, the memory controller corrects only the data returned to the CPU or I/O
controller. The actual data in memory is left with the error intact. Subsequent read operations cause correction cycles to
occur and, in most cases, an interrupt to report the error. On many of these processors, OpenVMS monitors the occurrence
of correctible memory errors and, in almost all cases, is able to remove the error condition by rewriting the data in
memory. Rewriting the data causes the data to be corrected in that memory location.
Other failures include:
 Operating system errors (system-detected inconsistencies or architectural errors in system context)
 User errors
 I/O errors
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 memory errors), and most I/O errors.
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 OpenVMS System Dump Analyzer (SDA) utility is provided for analyzing
memory dumps.
Input/Output
The QIO system service and other related I/O services provide a direct interface to the operating system's I/O routines. These
services are available from within most OpenVMS programming languages and can be used to perform low-level I/O operations
efficiently with a minimal amount of system overhead for time-critical applications.
Device drivers execute I/O instructions to transfer data to and from a device and to communicate directly with an I/O device. Each
type of I/O device requires its own driver. VSI supplies drivers for all devices supported by the OpenVMS operating system and
provides QIO system service routines to access the special features available in many of these devices.
OpenVMS supports a variety of disk and tape peripheral devices, as well as terminals, networks, and mailboxes (virtual devices for
interprocess communication), and more general I/O devices.
I/O Performance Features
Fast I/O provides a suite of additional system services that applications can use to improve I/O throughput. The fast I/O services
minimize the CPU resources required to perform I/O.
Fast Path provides a streamlined mainline code path through the I/O subsystem to improve both uniprocessor and multiprocessor
I/O performance. On multiprocessor systems, Fast Path allows all CPU processing for specific I/O adapters to be handled by a
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 11
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
specific CPU. This can significantly lower the demands on the primary CPU and increase the I/O throughput on multiprocessor
systems with multiple I/O ports. No user application changes are needed to take advantage of Fast Path. Fast Path can be utilized
by the $QIO system service or the Fast I/O services.
Extended File Cache (XFC)
The Extended File Cache (XFC) is a virtual block data cache provided with OpenVMS for Integrity servers. Similar to the Virtual I/O
Cache, the XFC is a clusterwide, file system data cache. Both file system data caches are compatible and coexist in the OpenVMS
Cluster.
The XFC improves I/O performance with the following features that are not available with the virtual I/O cache:
 Read-ahead caching
 Automatic resizing of the cache
 Larger maximum cache size
 No limit on the number of closed files that can be cached
 Control over the maximum size of I/O that can be cached
 Control over whether cache memory is static or dynamic
Record Management Services (RMS)
RMS is a set of I/O services that helps application programs to process and manage files and records. Although it is intended to
provide a comprehensive software interface to mass storage devices, RMS also supports device-independent access to unit-record
devices.
RMS supports sequential, relative, and indexed file organizations in fixed-length or variable-length record formats. RMS also
supports byte stream formats for sequential file organization.
RMS record access modes provide access to records in four ways:
 Sequentially
 Directly by key value
 Directly by relative record number
 Directly by record file address
RMS also supports block I/O operations for various performance-critical applications that require user-defined file organizations
and record formats.
RMS promotes safe and efficient file sharing by providing multiple file access modes and automatic record locking (where
applicable). RMS offers the options of enabling global buffers for buffer sharing by multiple processes.
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. These utilities also
generate appropriate reports.
For systems that have DECnet or DECnet-Plus installed, RMS provides a subset of file and record management services to remote
network nodes. Remote file operations are generally transparent to user programs.
Commands such as EDIT, CREATE, COPY, TYPE, and PRINT allow users to manipulate RMS records within RMS files at the DCL
command level.
Disk and Tape Volumes
The system manager can organize disk volumes 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. Files can be allocated
to the set as a whole (the default) or to specific volumes within the set. Optionally, the system manager can allocate portions of
indexed files to specific areas of a single disk or to specific volumes in a volume set.
The system manager can place quotas on a disk to control the amount of space individual users can allocate. Quota assignment is
made by UIC and can be controlled for each individual volume set in the system (or for each individual volume if the volume is not
part of a set).
The system manager can cache disk structure information in memory to reduce the I/O 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.
The system applies software validity checks and checksums to critical disk structure information. If a disk is improperly dismounted
because of user error or system failure, the system rebuilds the disk's structure information automatically the next time the disk is
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 12
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
mounted. The system detects bad blocks and prevents their reuse once the files to which the blocks were allocated are deleted. On
DIGITAL Storage Architecture (DSA) disks, the disk controller detects and replaces bad blocks automatically.
The system provides 255 levels of named directories and subdirectories whose contents are alphabetically ordered. Device and file
specifications follow VSI conventions. Users can use logical names to abbreviate the specifications and to make application
programs device and file name independent. Users can assign a logical name to an entire specification, to a portion of a
specification, or to another logical name.
OpenVMS supports multivolume magnetic tape files with transparent volume switching. Access positioning is done either by file
name or by relative file position.
Application Modernization and Integration Technologies
The VSI OpenVMS Application Modernization and Integration Infrastructure Package provides key Internet, e-business, and
integration software technologies that enhance OpenVMS for Integrity servers operating system and enable the development of ebusiness and enterprise integration solutions. These technologies are bundled with OpenVMS for Integrity server operating
systems. Several of the components are additionally bound by an open source software license.
The following components are included in the Base Operating Environment (BOE) for OpenVMS for Integrity servers:
 VSI Secure Web Server (SWS)
 Universal Description, Discovery, and Integration (UDDI) Client Toolkit
 Web Services Integration Toolkit (WSIT)
Additional information can be found in the OpenVMS Application Modernization and Integration Infrastructure Package Software
Product Description (SPD 80.58.xx) or on the OpenVMS Application Modernization and Integration website at:
http://www.hp.com/go/openvms/ebusiness/
Associated Products
The products in this section are not licensed as part of the OpenVMS Operating System and require a separate license.
VSI OpenVMS Cluster Software
VSI OpenVMS Cluster software is available for Integrity server systems, both as a separately licensed layered product and within the
High Availability Operating Environment (HA-OE) package on Integrity servers. It provides a highly integrated OpenVMS computing
environment that is distributed over multiple systems, separated in distance measured from feet up to 500 miles, containing up to
96 nodes.
OpenVMS Cluster systems and storage communicate using a combination of the following interconnects:
 Ethernet
 Small Computer Systems Interface (SCSI) (Storage Only)
 Fibre Channel (Storage Only)
VSI TCP/IP Services Version (minimum Version 5.7-13ECO05B) is needed for using IP for cluster communication. For more
information, see the Guidelines for HP OpenVMS Cluster Configurations and HP OpenVMS Cluster Systems guides.
Applications running on one or more nodes in an OpenVMS Cluster system share resources in a coordinated manner. While updating
data, the OpenVMS Cluster software synchronizes access to shared resources, preventing multiple processes on any node in the
cluster from uncoordinated access to shared data. This coordination ensures data integrity during concurrent update transactions.
Mixed-architecture and mixed-version clusters that contain both Alpha systems and Integrity server systems are supported.
Cluster satellite boot support on Integrity server systems is supported. This feature provides support for Integrity-to-Integrity
satellite booting. Cross-architecture booting (booting an Integrity satellite node from an Alpha boot server and vice-versa) is not
supported.
For more information, see the HP OpenVMS Cluster Software Software Product Description (SPD 29.78.xx).
VSI Volume Shadowing for OpenVMS
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 13
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
VSI Volume Shadowing for OpenVMS Integrity servers performs disk mirroring operations using a redundant array of independent
disks (RAID-1) storage strategy. Volume Shadowing for OpenVMS is available for Integrity server systems as both a separately
licensed product, as well as a component of the High Availability Operating Environment (HA-OE).
Volume Shadowing for OpenVMS provides high data availability for disk devices by ensuring against data loss that results from
media deterioration or controller or device failure. This prevents storage subsystem component failures from interrupting system
or application tasks.
For more information, see the HP Volume Shadowing for OpenVMS Software Product Description (SPD 27.29.xx).
VSI RMS Journaling for OpenVMS
VSI RMS Journaling for OpenVMS Alpha and Integrity servers is available as layered products and as a part of the High Availability
Operating Environment (HA-OE) on Integrity servers. Journaling enables a system manager, user, or application to maintain the
data integrity of RMS files in the event of a number of failure scenarios. These journaling products protect RMS file data from
becoming lost or inconsistent.
RMS Journaling provides the following three types of journaling:
 After-image journaling. Allows users to reapply modifications that have been made to a file. This type of journaling allows
users to recover files that are inadvertently deleted, lost, or corrupted.
 Before-image journaling. Allows users to reverse modifications that have been made to a file. This type of journaling
allows users to return a file to a previously known state.
 Recovery-unit journaling. Allows users to maintain transaction integrity. A transaction can be defined as a series of file
updates on one or more files. If any failure occurs during the transaction, recovery-unit journaling rolls back the partially
completed transaction to its starting point.
The binary kit for RMS Journaling ships with the OpenVMS Alpha and Integrity server distribution kits. To run the software,
customers must purchase a license and documentation. For more information, see the RMS Journaling for OpenVMS Software
Product Description (SPD 27.58.xx).
VSI TCP/IP Services for OpenVMS
VSI TCP/IP Services for OpenVMS is a System Integrated Product (SIP). For OpenVMS for Integrity servers, TCP/IP Services is licensed
as part of the Base Operating Environment (BOE); therefore, a separate license is not required.
VSI TCP/IP Services for OpenVMS is VSI's industry-standard implementation of the TCP/IP and NFS networking protocols on the
OpenVMS platform. TCP/IP Services for OpenVMS is integrated with the OpenVMS operating system installation. TCP/IP Services for
OpenVMS provides interoperability and resource sharing among systems running OpenVMS, UNIX, Windows, and other operating
systems that support TCP/IP. TCP/IP provides a comprehensive suite of functions and applications that support industry-standard
protocols for heterogeneous network communications and resource sharing. TCP/IP Services for OpenVMS provides a full TCP/IP
protocol suite including IP/multicasting, dynamic load balancing, rlogin proxy, network file access, remote terminal access, remote
command execution, remote printing, mail, application development, Post Office Protocol (POP), SNMP Extensible agent (eSNMP),
and Finger Utility. TCP/IP Version 5.7 also enables packet processing Engine (PPE), FTP anonymous light and stream control
transmission protocol (SCTP) for its customers.
Refer to the HP TCP/IP Services for OpenVMS Software Product Description (SPD 46.46.xx) for further information.
VSI DECnet-Plus and VSI DECnet Software
VSI DECnet for Integrity server software is a System Integrated Product (SIP). DECnet for OpenVMS for Integrity servers is a
component of the Base Operating Environment (BOE) on Integrity servers license bundle.
DECnet-Plus for OpenVMS for Integrity servers is a component of the Base Operating Environment (BOE) on Integrity servers license
bundle. The license for DECnet for OpenVMS for Integrity servers also grants the rights to use DECnet-Plus. Note that only one
version of DECnet can be active on a single system at any one time. Both DECnet and DECnet-Plus allow OpenVMS systems to
participate in network task-to-task communications for the purposes of transfer and copy of files, printing, the running of
applications, etc.
DECnet-Plus offers task-to-task communications, file management, downline system and task loading, network command
terminals, and network resource sharing capabilities as defined in the DIGITAL Network Architecture (DNA) Phase V protocols.
DECnet-Plus provides the newest DECnet features such as extended addressing and downline-load performance enhancements.
DECnet-Plus integrates DECnet and OSI protocols and now provides a linkage to TCP/IP using Request for Comments (RFC) 1006 and
RFC 1859. DECnet and OSI applications can now be run over DECnet (NSP), OSI (CLNS), and TCP/IP transports. For more information,
see the Associated Products section of this QuickSpec.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 14
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
For further information, see the DECnet-Plus for OpenVMS Software Product Description (SPD 50.45.xx), or the DECnet for OpenVMS
Software Product Description (SPD 48.48.xx).
VSI DECram for OpenVMS
VSI DECram for OpenVMS is a disk device driver that improves I/O performance by allowing an OpenVMS system manager to create
pseudo disks (RAMdisks) that reside in main memory. Frequently accessed data can be accessed much faster from a DECram device
than from a physical disk device. These RAMdisks can be accessed through the file system just as physical disks are accessed,
requiring no change to application or system software.
Because main memory is allocated for the DECram device, extra memory is generally required. The OpenVMS system manager can
designate the amount of memory dedicated to the DECram devices and the files that will be stored on it.
To run the DECram software, customers must first purchase a separate license.
For VSI OpenVMS for Integrity server customers, a software license for VSI DECram may be purchased as part of the OpenVMS Base
Operating Environment (BOE).
For more information, refer to the HP DECram for OpenVMS Software Product Description (SPD 34.26.xx).
VSI DECwindows Motif for OpenVMS
VSI DECwindows Motif for OpenVMS is a System Integrated Product (SIP). On the Integrity Server platform, the DECwindows product
is part of the Base Operating Environment (BOE) and is licensed under this package.
This product provides support for both OSF/Motif, a standards-based graphical user interface, and the X user interface (XUI) in a
single, run-time and development environment. DECwindows Motif displays the OSF/Motif user interface. Because both Motif and
XUI are based on X.org X Window System, applications written with either toolkit will run regardless of which environment the user
selects.
For more information, see the HP DECwindows Motif for OpenVMS Software Product Description (SPD 42.19.xx).
Conformance to Standards
OpenVMS is based on the following public, national, and international standards.
Distributed Computing Environment (DCE) Support
The DCE for the OpenVMS product family provides a set of the distributed computing features specified by The Open Group's DCE, as
well as tools for application developers. With DCE, The Open Group has established a standard set of services and interfaces 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 system to the user. Because DCE makes the
underlying networks and operating systems transparent, application developers can easily build portable, interoperable
client/server applications. Users can locate and share information safely and easily across the entire enterprise. 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.
DCE for OpenVMS currently consists of the following products:
 DCE Run-Time Services for OpenVMS
 DCE Application Developers' Kit for OpenVMS
 DCE Cell Directory Service (CDS)
 DCE Security Server, one of which is required for each DCE
The right to use the DCE Run-Time Services is included with the OpenVMS operating system base license. All other DCE products are
available as separate layered products. For more details, see the HP Distributed Computing Environment (DCE) for OpenVMS
Software Product Description (SPD 43.05.xx).
Support for OSF/Motif and X Window System Standards
DECwindows Motif provides support for OSF/Motif, a standards-based graphical user interface. DECwindows Motif also provides
support for the X Consortium's X Window System, Version 11, Release 6 (X11R6) server and the Version 11, Release 5 (X11R5)
client.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 15
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features
Standards Supported by OpenVMS
The OpenVMS operating system is based on the following public, national, and international standards. These standards are
developed by the American National Standards Institute (ANSI), U.S. Federal Government (responsible for FIPS), Institute of
Electrical and Electronics Engineers (IEEE), and the International Organization for Standardization (ISO). The following information
may be useful in determining responsiveness to stated conformance requirements as enabled in particular commercial and/or
government procurement solicitation documents.
 ANSI X3.4-1986: American Standard Code for Information Interchange
 ANSI X3.22-1973: Recorded Magnetic Tape (800 BPI, NRZI)
 ANSI X3.27-1987: File Structure and Labeling of Magnetic Tapes for Information Interchange
 ANSI X3.298: Limited support. Information Technology—AT Attachment-3 Interface (ATA-3)
 ANSI X3.39-1986: Recorded Magnetic Tape (1600 BPI, PE)
 ANSI X3.40-1983: Unrecorded Magnetic Tape
 ANSI X3.41-1974: Code Extension Techniques for Use with 7-bit ASCII
 ANSI X3.42-1975: Representation of Numeric Values in Character Strings
 ANSI X3.54-1986: Recorded Magnetic Tape (6250 BPI, GCR)
 ANSI X3.131-1986 (SCSI I): Small Computer System Interface
 ANSI X3.131-1994 (SCSI II): Small Computer System Interface
 ANSI/IEEE 802.2-1985: Logical Link Control
 ANSI/IEEE 802.3-1985: Carrier Sense Multiple Access with Collision Detection
 FIPS 1-2: Code for Information Interchange, Its Representations, Subsets, and Extensions
NOTE: 1-2 includes ANSI X3.4-1977(86)/FIPS 15; ANSI X3.32-1973/FIPS 36; ANSI X3.41-1974/FIPS 35; and FIPS 7.
 FIPS 3-1/ANSI X3.22-1973: Recorded Magnetic Tape Information Interchange (800 CPI, NRZI)
 FIPS 16-1/ANSI X3.15-1976: Bit Sequencing of the Code for Information Interchange in Serial-by-Bit Data Transmission
Note: FED STD 1010 adopts FIPS 16-1.
 FIPS 22-1/ANSI X3.1-1976: Synchronous Signaling Rates Between Data Terminal and Data Communication Equipment
Note: FED STD 1013 adopts FIPS 22-1.
 FIPS 25/ANSI X3.39-1986: Recorded Magnetic Tape for Information Interchange (1600 CPI, Phase Encoded)
 FIPS 37/ANSI X3.36-1975: Synchronous High-Speed Data Signaling Rates Between Data Terminal Equipment and Data
Communication Equipment
NOTE: FED STD 1001 adopts FIPS 37.
 FIPS 50/ANSI X3.54-1986: Recorded Magnetic Tape for Information Interchange, 6250 CPI (246 CPMM), Group Coded
Recording
 FIPS 79/ANSI X3.27-1987: Magnetic Tape Labels and File Structure for Information Interchange
 FIPS 86/ANSI X3.64-1979: Additional Controls for Use with American National Standard Code for Information
Interchange
NOTE: Other FIPS are not applicable.
NOTE: Information regarding interchangeability of ANSI and FED standards with FIPS is contained in ‘‘ADP
Telecommunications Standards Index,'' July 1988, published and maintained by the General Services Administration.
 ISO 646: ISO 7-bit Coded Character Set for Information Exchange
 ISO 1001: File Structure and Labeling of Magnetic Tapes for Information Interchange
 ISO 1863: Information Processing — 9-track, 12, 7 mm (0.5 in) wide magnetic tape for information interchange recorded at
32 rpmm (800 rpi)
 ISO 1864: Information Processing—Unrecorded 12, 7 mm (0.5 in) wide magnetic tape for information interchange — 35
ftpmm (800 ftpi) NRZI, 126 ftpmm (3 200 ftpi) phase encoded and 356 ftmm (9 042 ftpi), NRZI
 ISO 2022: Code Extension Techniques for Use with ISO 646
 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
 ISO 4873: 8-Bit Code for Information Interchange — Structure and Rules for Implementation
 ISO 5652: Recorded Magtape (6250)
 ISO 6429: Control Functions for Coded Character Sets
 ISO 9316: 1989 (SCSI-1) Small Computer System Interface
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 16
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Standard Features


ISO 9660: Information Processing—Volume and file structure of CD–ROM for information exchange
ISO 10288: 1994 (SCSI-2) Small Computer System Interface
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 17
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications
Installation
OpenVMS for Integrity servers is distributed as a binary kit on DVD. Procedures for setting up the system disk from media and for
preparing the system for day-to-day operations are provided in the VSI OpenVMS Version 8.4-1H1 Installation and Upgrade Manual.
The procedures use the POLYCENTER Software Installation (PCSI) utility to configure and install the OpenVMS Integrity operating
system.
Network Installation and Upgrade
InfoServer network booting is supported for OpenVMS installations and upgrades on any OpenVMS Integrity server systems that
support OpenVMS. For OpenVMS Integrity server systems, InfoServer network booting is supported on all LAN cards (also referred
to as LAN devices or adapters) that are supported by EFI.
For OpenVMS Integrity servers installations and upgrades, you can boot from a virtual DVD/CD drive on the LAN using the OpenVMS
InfoServer software application. You can use the OpenVMS InfoServer software application on all OpenVMS Integrity server systems
running Version 8.3 or higher. This support provides the additional advantage of allowing a network administrator to boot multiple
OpenVMS systems on the network from a single copy of the OpenVMS distribution CD or DVD.
Using the InfoServer software application on Integrity servers for network booting requires several one-time-only configuration
steps unique to OpenVMS Integrity servers. Any configuration procedures that might have been performed for network booting
using an InfoServer hardware system (traditionally used by Alpha systems) are not valid for the OpenVMS Integrity servers. Booting
from the InfoServer software application for OpenVMS on Integrity servers differs significantly from booting from the InfoServer
hardware system traditionally used by OpenVMS Alpha systems or from the InfoServer software application on OpenVMS Alpha
systems.
To install or upgrade the operating system over the network, OpenVMS Integrity server systems must use the InfoServer software
application that is integrated with the OpenVMS operating system.
For additional information, see the VSI OpenVMS Version 8.4-1H1 Installation and Upgrade Manual.
Virtual Connect
Virtual Connect is a set of interconnect modules and embedded software for HP BladeSystem c-Class enclosures; it simplifies the
setup and administration of server connections.
Virtual Media (vMedia)
Virtual Media (vMedia) is the overall name for a number of different devices that can exist on a PC. These devices appear as local
USB disk devices to the host system. You can also use vMedia devices to boot, install, or upgrade OpenVMS from over the network,
as described in the VSI OpenVMS Version 8.4-1H1 Installation and Upgrade Manual.
VSI OpenVMS v8.4-1H1 supports vMedia in the following Integrity server systems: BL860c i2, BL860c i4, BL870c i2, BL870c i4,
BL890c i2, BL890c i4, rx2800 i2, and rx2800 i4.
POLYCENTER Software Installation
The PCSI utility simplifies the installation and management of OpenVMS products. It is used to install, update, and uninstall
software products that have been prepared with the utility. In addition, the utility provides a database to track the installation,
reconfiguration, and uninstallation of software. For products installed with other installation technologies, the utility provides a
mechanism for adding information about them into the product database. The utility also provides the ability to manage
dependencies between products during the installation process.
For software providers, the PCSI utility simplifies the task of packaging software by providing a simple, declarative language for
describing material for the installation kit and defining how it is installed. The utility handles the functions, while the developer
instructs the utility what to do. This significantly reduces the complexity and time to develop installation procedures. The language
allows the developer to easily specify dependencies on other software, manage objects in the execution environment (such as files
and directories), and anticipate and resolve conflict before it occurs. The utility also significantly simplifies the packaging of
multiple software products into one logical product suite.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 18
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications
For OpenVMS for Integrity servers, you use the PCSI utility to install the operating system and to install layered products that are
compliant with the POLYCENTER utility.
All of the software product kits included on the OpenVMS Version 8.4-1H1 distribution media are signed using Secure Delivery. A
notable exception is the OpenVMS Operating System (the VMS product) because it is shipped in bootable form, not as a single file kit
that is signed.
For OpenVMS for Integrity servers, when you install or upgrade the operating system by booting from the distribution media,
layered products that have been signed are validated by the PCSI utility with the aid of a digital signature file (called a manifest).
Validation involves using the Secure Delivery component of CDSA to authenticate the originator of the product kit and to verify its
contents.
In addition, on OpenVMS for Integrity server systems, the PRODUCT SHOW HISTORY command displays the validation status of
installed products and identifies those that were installed from unsigned kits or were installed prior to the availability of the Secure
Delivery functionality.
VMSINSTAL
OpenVMS includes the VMSINSTAL facility to handle the installation of optional VSI supplied software products that have not been
converted to use the POLYCENTER Software Installation utility.
Test Package and Diagnostics
OpenVMS includes a User Environment Test Package (UETP), which verifies that the OpenVMS operating system is properly installed
and ready for use on the customer's systems.
You can run diagnostics on individual devices during normal system operation. Certain critical components can operate in degraded
mode.
OpenVMS For Integrity Servers Disk Space Requirements
Operating System Disk Space Requirements
The minimum disk space required for OpenVMS for Integrity servers is 3.4 GB. The disk space requirements for OpenVMS for
Integrity servers vary according to which options are installed:
File Category
Minimum OpenVMS files
DECwindows Support
Full DECwindows Motif (optional)
DECnet Support
DECnet-Plus
WBEMCIM
Other optional OpenVMS files
Paging file (required)
Swap file (suggested)
Dump file (optional)
Total
Space Used
2.4 GB
74 MB
132 MB
3 MB
66 MB
308 MB
167 MB
1028 MB
32 MB
181 MB
3.4 GB
NOTE: The minimum OpenVMS files listed in the table will allow you to run with minimal functionality. Not all OpenVMS commands
and utilities will function fully as documented in this minimum configuration. Not all VSI and other layered products will work in this
minimum configuration.
The minimum OpenVMS files are for a system configuration where all optional features have been declined during the initial
installation. For most applications, this is not a realistic OpenVMS environment.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 19
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications
The paging, swap, and dump file requirements are the minimum for a system with 64 MB of main memory. Additional memory in
most cases adds to the space needed for these files, as will particular needs of your application. With careful system management it
is possible to use the paging file space as a temporary dump file.
For an OpenVMS Cluster system disk, paging, swap, and dump files cannot be shared between nodes, so the files must either be
duplicated on the system disk or located on some other disk.
DECwindows Motif for OpenVMS for Integrity servers Disk Space Requirements
To support full OpenVMS for Integrity servers and full DECwindows Motif for OpenVMS for Integrity servers, a system disk with at
least 707 MB is recommended. However, a subset of the DECwindows Motif environment can be installed. The permanent amount of
space used is 135 MB. These disk space requirements are in addition to the disk space required for the OpenVMS for Integrity
servers operating system, as indicated in the OpenVMS for Integrity servers Disk Space Requirements table.
Installation of the DECwindows Motif layered product gives customers the option of installing any or all of the following
components:
 Run-time support (base kit) – 60 MB. This section provides support for running DECwindows Motif for OpenVMS for
Integrity servers applications on Integrity servers and is a required part of the installation.
 New Desktop – 35 MB. This is an optional component that allows use of the New Desktop environment. It includes
applications and application programming interfaces (APIs).
 DECwindows desktop – 8 MB. The DECwindows desktop is the user interface that was included in previous versions of
DECwindows Motif and includes the DECwindows Session Manager, FileView, and the Motif Window Manager.
 Programming support – 8 MB. This number includes support for the C, Pascal, and Fortran programming languages and for
the New Desktop. If only a subset of languages is installed, the amount of disk space required will be less.
 Programming examples – 8 MB. This number includes example audio files, the DECwindows desktop, and the New
Desktop. If only a subset of example files is installed, the amount of disk space required will be less.
Layered Product Disk Space Requirements
In addition to the disk space used directly by VSI or third-party layered products, there may be additional space used to store
information from those products in OpenVMS help libraries, command tables, object libraries, and elsewhere. The amount of
additional disk space required cannot be exactly predicted due to the possibility of recovering unused space already existing in
those library files. Unusually large modules contributed by layered products can also affect the amount of space required for
upgrading to a new version of the OpenVMS for Integrity servers operating systems.
Distribution Media
OpenVMS for Integrity servers
OpenVMS for Integrity servers is available on DVD. The OpenVMS for Integrity servers binary DVD contains the operating system and
layered product binaries for all layered products included with the Operating Environments.
Other items in the OpenVMS for Integrity Servers kit are delivered on CD or DVD. A single media kit contains the operating system,
Operating Environment component products, layered products, online documentation, and several hardcopy manuals.
Some Integrity servers do not include a built-in CD/DVD drive. You can use an external USB CD/DVD drive (you must supply this drive
and the required cable; they are not included with the Integrity servers). You can use InfoServer network booting to boot from a
virtual DVD drive on the network. In addition, beginning with OpenVMS Version 8.4, you can use HP SIM provisioning for similar
purposes, in which case you can install or upgrade OpenVMS on multiple servers (up to 8) in the network simultaneously. You can
also use virtual media (vMedia) devices to allow you to boot, install, or upgrade OpenVMS from over the network, as described in the
VSI OpenVMS Version 8.4-1H1 Installation and Upgrade Manual.
Documentation
For OpenVMS Version 8.4-1H1, documentation is available in the following formats:
Printed Books
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 20
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications
For OpenVMS Version 8.4-1H1, the following three new hardcopy books supplement the books in the OpenVMS Version 8.4
documentation set. These new books are also available on the VMS Software Inc website, or in .TXT formats on the OpenVMS OE
DVD:
 VSI OpenVMS Version 8.4-1H1 Cover Letter and Release Notes
 VSI OpenVMS Version 8.4-1H1 Installation and Upgrade Manual
 VSI OpenVMS Version 8.4-1H1 License Management Utility Manual
For OpenVMS for Integrity server customers, a third set is available: the OpenVMS OE Extension Manuals.
The Full Documentation Set is for users who need extensive explanatory information on all major OpenVMS resources, complete
reference information on system routines and utilities, detailed examples, OpenVMS Cluster guidelines, programming concepts, and
information on the Help Message utility. This set meets the needs of system managers and of system and application programmers.
It includes the Base Documentation Set.
The Base Set includes the most commonly used OpenVMS manuals, addressing the needs of general users and system managers of
small, standalone systems. Manuals such as the Release Notes, New Features, and the DCL Dictionary are included in the Base Set.
The OpenVMS OE Extension Manuals contain documentation for the following products that are licensed with the OpenVMS for
Integrity servers Operating Environments: DECnet-Plus for OpenVMS, DECprint Supervisor, DECwindows Motif, DCE, and TCP/IP
Services for OpenVMS.
Online Books
The OpenVMS Version 8.4-1H1 for Integrity servers media kit contains online documentation CDs for the Operating Environments
and the Layered Products.
Growth Considerations
The minimum hardware and software requirements for any future version of this product may be different from the requirements
for the current version.
Ordering Information
OpenVMS for Integrity Servers Ordering Information
With OpenVMS Version 8.4-1H1 for Integrity servers, the operating system software, layered product software, and online
documentation are delivered together in one media kit. Media is offered for Base (BOE) and High Availability (HA-OE) Operating
Environments. Purchase of an OE media product requires the purchase of a corresponding OE license on the same order.
Table 1 lists the media product offerings for the three Operating Environments. Table 2 lists the options available with each media
product offering.
Product No.
M1J86AA
Table 1
OpenVMS for Integrity Servers Media Offerings
Common Description
VSI OpenVMS Integrity servers OE Media
Table 2
OpenVMS for Integrity Servers Media Options
Media Option
Description
#A60
VSI OpenVMS for Integrity servers Version 8.4-1H1
#AJR
OE Media Kit on DVD
#0D1
Factory Installation
NOTE: 0D1 not available on i2 servers for VSI OpenVMS Version 8.4-1H1
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 21
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications
Each media order must include the OE Version option. Please specify option #A60 for VSI OpenVMS for Integrity servers Version 8.41H1.
For each media order, one of the following must be ordered:
 DVD Media (option #AJR)
 Factory Installation (option #0D1)
 DVD Media and Factory Installation (options #AJR and #0D1)
The purchase of at least one DVD Media option per customer site is strongly advised, since not all items on the DVD media are
included in the Factory Installation.
For a complete description of the OpenVMS for Integrity servers Operating Environments, or for additional ordering information, see
the VSI OpenVMS Operating Environment for OpenVMS Integrity Servers Software Product Description (SPD DO-VIBHAA-006) or the
HP Operating Environments for OpenVMS for Integrity Servers Software Product Description (SPD 82.34.xx).
OpenVMS for Integrity Servers Software Licenses
A license is referred to as a "License-to-Use" or LTU.
For OEs on new Integrity systems, the following hardware tiers are defined:
• Maximum of 2 Processors (BL860c i2, i4, rx2800 i2, i4)
• Maximum of 4 Processors (BL870c i2, i4)
• Maximum of 8 Processors (BL890c i2, i4)
The following are licenses offered for each OpenVMS for Integrity servers Operating Environment. One license of the appropriate
hardware tier is required to activate a socket.
Software Licenses
Table 3
Operating Environment Licenses with Options
M1J87AC
VSI OpenVMS V841H1 Base Operating Environment LTU
M1J87AC#828
VSI V841H1 BOE 2S LTU
M1J87AC#848
VSI V841H1 BOE 4S LTU
M1J87AC#888
VSI V841H1 BOE 8S LTU
M1J87AC#B01
VSI V841H1 including complete system
M1J87ACE
VSI V841H1 BOE E-LTU
M1J87ACE#828
VSI V841H1 BOE 2S E-LTU
M1J87ACE#848
VSI V841H1 BOE 4S E-LTU
M1J87ACE#888
VSI V841H1 BOE 8S E-LTU
M1J88AC
VSI V841H1 HAOE LTU
M1J88AC#828
VSI V841H1 HAOE 2S LTU
M1J88AC#848
VSI V841H1 HAOE 4S LTU
M1J88AC#888
VSI V841H1 HAOE 8S LTU
M1J88ACE
VSI V841H1 HAOE E-LTU
M1J88ACE#828
VSI V841H1 HAOE 2S E-LTU
M1J88ACE#848
VSI V841H1 HAOE 4S E-LTU
M1J88ACE#888
VSI V841H1 HAOE 8S E-LTU
NOTE: For information on HP OE licenses for prior version, see SPD 82.35.13.
Ordering OE License Upgrades
The Upgrade License is used when the Operating Environment is upgraded from a smaller OE to larger OE on the same Integrity
server.
The BOE to HA-OE License Upgrades deliver a license for HA-OE and the pricing gives credit for the previous purchase of the BOE.
Table 4 lists the OE license upgrade options.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 22
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications
Table 4
OE License Upgrade Options
Product No.
Common Description
M1J89AC
VSI OPENVMS V841H1 Integrity servers BOE to HA-OE Upgrade
M1J89AC#828
VSI V841H1 BOE to HAOE Upg 2S LTU
M1J89AC#848
VSI V841H1 BOE to HAOE Upg 4S LTU
M1J89AC#888
VSI V841H1 BOE to HAOE Upg 8S LTU
NOTE: For information on OE license upgrades for prior version, see the HP SPD 82.34.18.
Ordering OE License Trade-ins
The Trade-in policy provides partial software investment protection when the customer is moving to a new Integrity server. To be
eligible for credit, the user needs a valid license. The old software must be equivalent in function to the new software.
Trade-in equivalency for older OEs (FOE, EOE, MCOE):
FOE -> BOE
EOE -> HA-OE
MCOE -> HA-OE
Process:
1. The customer orders the new OE license.
2. The customer provides proof of license to the field representative.
3. The field calculates credit and applies it to the order.
4. License keys for the old system should be deleted at least 90 days after the new licenses/new system delivery.
Table 5 lists the OE license trade-ins.
Table 5
OE License Trade-ins
Product Number
M1J87ACN
M1J87ACN#828
M1J87ACN#848
M1J87ACN#888
M1J88ACN
M1J88ACN#828
M1J88ACN#848
M1J88ACN#888
Description
VSI V841H1 BOE Trade-in LTU
VSI V841H1 BOE Trade-in 2S LTU
VSI V841H1 BOE Trade-in 4S LTU
VSI V841H1 BOE Trade-in 8S LTU
VSI V841H1 HAOE Trade-in LTU
VSI V841H1 HAOE Trade-in 2S LTU
VSI V841H1 HAOE Trade-in 4S LTU
VSI V841H1 HAOE Trade-in 8S LTU
OpenVMS Hardcopy Documentation Sets
Hardcopy Documentation offerings are being phased out due to low demand. OpenVMS operating system and layered product
documentation can be found on http://www.vmssoftware.com and on http://www.hp.com/go/openvms/doc.
Software Licensing
The OpenVMS operating system software is furnished under the licensing provisions of VSI's Standard Terms and Conditions.
License Management Facility Support
The OpenVMS operating system supports the OpenVMS License Management Facility (LMF).
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 23
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications
If an OpenVMS license is not registered and activated using LMF, only a single login is permitted for system management purposes
through the system console (OPA0:).
Some of the OpenVMS license types are based on the number of concurrent users, called an activity license. Every product has the
option to define an activity as related to the LMF. OpenVMS Interactive User and ADL Interactive User Licenses define the number of
concurrent users who have activity licenses as defined by the LMF. OpenVMS defines activities, sometimes referred to as an
OpenVMS user, as follows:
 Each remote terminal connection is considered an activity. This is true even if users set host to their local nodes (SET HOST
0).
 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.
 A batch job is not considered an activity.
 A remote network connection (a connection other than a remote terminal connection) is not considered an activity.
For more information about VSI's licensing terms and policies, contact your VSI account representative.
Software License Information
(OpenVMS for Integrity Servers Only)
OpenVMS is offered with Per Socket License (PSL) on HP Integrity server Blades (BL8x0c i2/i4 server blades and rx2800 i2/i4
servers).
The OE bundles are groups of individual products offered together under a single license. OEs are offered with PSLs. One PSL is
required for each active processor socket in the system or hard partition. If additional processor sockets are later added to the
system or hard partition, each requires an additional PSL.
An OE license grants the right to use all the components included in the specified OE.
For OpenVMS for Integrity servers, once a customer purchases a new license, the only way the customer can obtain rights to new
versions of the product are:
• Through a Support Agreement
• Through a purchase of a new, full priced, license for that product
Other differences from OpenVMS Alpha licensing practices:
• User licenses are not required. The Base Operating Environment (BOE) license includes unlimited OpenVMS users.
• Version update licenses are not available. Update services are available only through a Support Agreement.
• Trade-in allowances are offered as license "options" rather than as separate licenses.
For more information regarding OpenVMS for Integrity servers licensing terms and policies, contact your local VSI sales office, or
find HP software licensing information on the Worldwide Web at:
http://h18000.www1.hp.com/products/software/info/terms/swl_sld.htm
The following technologies are licensed as part of the OpenVMS for Integrity servers operating system:
Product Name
VSI DECprint Supervisor (DCPS) for
OpenVMS
VSI Distributed Computing Environment (DCE)
Software Product Description (SPD)
SPD 44.15.xx
SPD 43.05.xx
Systems Supported
Integrity Server Systems Supported
The following HP Integrity servers are supported by VSI OpenVMS Version 8.4-1H1:
 HP Integrity BL860c i2 Server Blade (Itanium Quadcore processors); 1.33GHz/16MB, 1.6GHz/20MB, 1.73GHz/24MB;
included in c7000 and c3000 enclosure
 HP Integrity BL860c i2 Server Blade (Itanium Dualcore processors); 1.6GHz/10MB; included in c7000 and c3000 enclosure
 HP Integrity BL870c i2 Server Blade (Itanium Quadcore processors); 1.33GHz/16MB, 1.6GHz/20MB, 1.73GHz/24MB;
included in c7000 and c3000 enclosure
 HP Integrity BL870c i2 Server Blade (Itanium Dualcore processors); 1.6GHz/10MB; included in c7000 and c3000 enclosure
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 24
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Technical Specifications

HP Integrity BL890c i2 Server Blade (Itanium Quadcore processors) 1.33GHz/16MB, 1.6GHz/20MB, 1.73GHz/24MB; included
in c7000 and c3000 enclosure
 HP Integrity BL890c i2 Server Blade (Itanium Dualcore processors); 1.6GHz/10MB; included in c7000 and c3000 enclosure
 HP Integrity rx2800 i2 Server (Itanium Quad-core Processors); 1.33 GHz/16 MB on-chip L3 cache 9320 processor, or quad
core 1.60 GHz/20 MB on-chip L3 cache 9340.
 HP Integrity rx2800 i2 Server (Itanium Dual-core Processors); 1.6 GHz/10 MB on-chip L3 cache 9310 processor
 HP Integrity BL860c i4 Server Blade (Itanium Octa-core processors); 2.13GHz/24MB; 2.53GHz/32MB; included in c7000 and
c3000 enclosure
 HP Integrity BL860c i4 Server Blade (Itanium Quadcore processors); 1.73GHz/20MB 130W; 2.4GHz/32MB 170W included in
c7000 and c3000 enclosure
 HP Integrity BL860c i4 Server Blade (Itanium Dualcore processors); 2.13GHz/24MB 170W; 2.53GHz/32MB 170W;included in
c7000 and c3000 enclosure
 HP Integrity BL870c i4 Server Blade (Itanium Octa-core processors); 2.13GHz/24MB; 2.53GHz/32MB; included in c7000 and
c3000 enclosure
 HP Integrity BL870c i4 Server Blade (Itanium Quadcore processors); 1.73GHz/20MB 130W; 4-Core 9550 2.4GHz/32MB
170W, 1.6GHz/20MB, 1.73GHz/24MB; included in c7000 and c3000 enclosure
 HP Integrity BL870c i4 Server Blade (Itanium Dualcore processors); 2.13GHz/24MB 170W; 2.53GHz/32MB 170W; included in
c7000 and c3000 enclosure
 HP Integrity BL890c i4 Server Blade (Itanium Octa-core processors); 2.13GHz/24MB; 2.53GHz/32MB; included in c7000 and
c3000 enclosure
 HP Integrity BL890c i4 Server Blade (Itanium Quadcore processors) 2.13GHz/24MB 170W; included in c7000 and c3000
enclosure
 HP Integrity BL890c i4 Server Blade (Itanium Dualcore processors); 2.53GHz/32MB 170W; included in c7000 and c3000
enclosure
 HP Integrity rx2800 i4 Server (Itanium Octa-core Processors); 2.13GHz/24MB 170W on-chip L3 cache 9540 processor or
Octa-core 2.53GHz/32MB 170W on-chip L3 cache 9560 processor
 HP Integrity rx2800 i4 Server (Itanium Quad-core Processors); 1.73GHz/20MB 130W on-chip L3 cache 9520 processor, or
quad core 2.4GHz/32MB 170W on-chip L3 cache 9550.
 HP Integrity rx2800 i4 Server (Itanium Dual-core Processors); 2.13GHz/24MB 170W on-chip L3 cache 9540 or
2.53GHz/32MB 170W on 9560 processor
Note: HP supports VSI OpenVMS V8.4-1H1 on HP Integrity i4 and HP Integrity 2 servers only. For a complete list of servers that VSI
supports, see http://vmssoftware.com/quickspec.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 25
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Products Supported
Appendix A (OpenVMS for Integrity servers)
This appendix describes the HP options supported on HP OpenVMS for HP Integrity servers. It is left in this document for reference.
Please refer to VSI’s web page at http://www.vmssoftware.com for options supported by VSI’s OpenVMS.
LAN Options
HP PCI 10/100Base-T LAN Adapter (Linux Only)
HP 4-Port 100base-TX Ethernet LAN Adapter
HP GigE-TX PCI LAN Adapter (rx2600)
HP GigE-SX PCI LAN Adapter (rx2600)
HP PCI-X 2Port 1000Base-SX/T Gigabit Adapter
HP PCI-X 2-P SCSI/1000Base-T Multifunction Adapter
HP PCI-X 133MHz 10GbE SR Fiber Adapter
HP PCI-X 4-port 1000Base-T Adapter
Dual port UTP (copper) network interface card (NIC) that connects PCI-X to Ethernet and
IEEE 802.3 local area networks at 10, 100, or 1000 Mb/s. This card is supported as an
rx4640 core I/O option only
HP PCI-X 1000Base-T Card
HP PCI-X 1-port 1000Base SX Adapter
HP PCIe 2-port 1000Base-T LAN Adapter
HP PCIe 2-port 1000Base-SX LAN Adapter
HP PCIe 4-port 1000Base-T Gigabit Adapter
HP PCI-X 266MHz 10Gb Ethernet SR Multi-OS Card
NOTE: No boot support
Quad port UTP (copper) network interface card (NIC); connects PCIe to Ethernet and
IEEE 802.3 local area networks at 10, 100, or 1000 Mb/s.
HP NC360m Dual Port 1GbE BL-c Adapter
HP NC364m Quad Port 1GbE BL-c Adapter
HP NC532m Dual Port 10GbE Multifunction BL-c Adapter
HP Integrity PCIe 2-port 10GbE-SR Fabric Adapter
HP Integrity PCIe 2-port 10GbE-LR Fabric Adapter
HP Integrity PCIe 2-port 10GbE-CR Copper Adapter
445978-B21
447883-B21
467799-B21
AM225A
AM232A
AM233A
Fibre Channel Storage Options
HP PCI-X 2.0 Dual-port 4GB FC Adapter
HP PCI-X Dual Channel 2GB Fibre Channel HBA
HP 4Gb 2-port PCIe Fibre Channel Host Bus Adapter
HP 4Gb 1-port PCIe Fibre Channel Host Bus Adapter
HP 4Gb 2-port PCIe Fibre Channel Host Bus Adapter
HP PCI Express 1-port 8Gb Fibre Channel SR (QLogic) Adapter
HP PCI Express 2-port 8Gb Fibre Channel SR (QLogic) Adapter
QLogic QMH2562 8Gb Fibre Channel Host Bus Adapter for c-Class BladeSystem
HP PCI-X Dual Channel 2GB Fibre Channel HBA
HP 4Gb 2-port PCIe Fibre Channel Host Bus Adapter
AB379A
A6826A
AD300A
AD299A
AD355A
AH400A
AH401A
451871-B21
A6826A
AD300A
Parallel SCSI Storage Options
HP Smart Array 6402 U320 2CH Controller
HP Smart Array 6404 U320 4CH Controller
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
A5230A
A5506B
A6825A
A6847A
A7011A
AB290A
AB287A
AB545A
AB352A
AD331A
AD332A
AD337A
AD338A
AD339A
AD385A
NC364M
A9890A
A9891A
Page 26
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Products Supported
HP PCI-X Dual-Channel Ultra320 SCSI Adapter
HP Integrity PCI-E Ultra320 SCSI Adapter
Serial Attached SCSI (SAS) Storage Options
HP rx3600/rx6600 Core I/O Storage Controller
HP rx6600 2nd I/O Storage Controller
HP Integrity rx2660 SAS Smart Array P400 Card
HP Integrity rx3600/rx6600 Core I/O Upgrade
HP PCIe P800 SAS RAID Controller
HP PCIe SC44Ge SAS Host Bus Adapter
HP Smart Array P410/256 2-ports Int PCIe x8 SAS Controller.
HP Smart Array P711m/1G 6Gb FBWC 4-ports Ext Mezzanine SAS Controller
Storage and Network Combo Cards
HP PCI-X 2-P SCSI/1000Base-T Multifunction Adapter
HP PCI-X 2Gb FC/1Gb Ethernet Multifunction Adapter
HP 1000-SX and 2G FC PCI-X Combo Card
HP PCI-X 2G Fibre Channel/1000Base-T HBA
HP PCI-X 1-port 4Gb FC and 1-port 1000BT Adapter
HP PCI-X 2-port 4Gb FC and 2-port 1000BT Adapter
HP Server rx76xx/rp7420 Core I/O Card
HP PCIe 1-port 4Gb and 1-port 1000BT Adapter
HP PCIe 2-port 4Gb and 2-port 1000BT Adapter
Tape Devices
320GB SDLT Tape Drive
600GB SDLT Tape Drive
400GB LTO Ultrium 2 Tape Drive
400GB LTO Ultrium 2 Tape Drive
400GB LTO Ultrium 2 Tape Blade
800GB LTO Ultrium 3 Tape Drive
800GB LTO Ultrium 3 Tape drive
1.6TB LTO Ultrium 4 Tape Drive
3TB LTO Ultrium 5 Tape Drive
3TB LTO Ultrium 5 Tape Drive
72GB DAT Tape Drive
160GB DAT Tape Drive
Tape Autoloader
Virtual Tape Library
Ultrium and SDLT Tape Library
Ultrium Tape Library
Ultrium Tape Library
Ultrium Tape Library
Ultrium and SDLT Tape Library
Ultrium Tape Library
NOTE: Compressed capacity; assumes 2:1 data compression.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
A7173A
AT134A
AB036A
AB037A
AD397A
AD348A
AD335A
AH303A
462862- B21
513778-B21
AB290A
AB465A
A9782A
A9784A
AD193A
AD194A
A9918A
AD221A
AD222A
SDLT320
SDLT600
Ultrium 460
Ultrium 448
Ultrium 448c
Ultrium 960
Ultrium 920
Ultrium 1840
Ultrium 3000
Ultrium 3280
DAT72
DAT160
1/8 Autoloader
VLS6000
MSL6000
MSL2024
MSL4048
MSL8096
ESL E-Series
EML E-Series
Page 27
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Products Supported
Parallel SCSI and SAS Storage Shelves
14 disk Ultra320 single-bus enclosure
14 disk Ultra320 double-bus enclosure
14 disk Ultra320 2-node Shared SCSI enclosure1
12 3.5" SAS disk storage enclosure
25 SFF SAS disk storage enclosure
Half-height c-Class storage Blade with 6 SFF SAS disk
HP D2200sb PCIe Storage Blade
SAS Storage System
12 LFF 6Gb SAS/SATA disk enclosure
25 SFF 6Gb SAS/SATA disk enclosure
1Shelf is supported only on Integrity servers rx2620, rx2660, rx3600, rx6600.
Miscellaneous Options
HP USB OpenVMS Keyboard and 3-Button Mouse
HP Management (rx1600) CPU Card
HP OpenVMS/HP-UX 2D/3D PCI Graphics Card
HP PCI-X iLO Remote Management Adapter
HP Graphics USB Card (rx5670)
HP Virtual Connect FlexFabric 10Gb/24-port Module for c-Class BladeSystem
MSA30 SB
MSA30 DB
MSA30MI
MSA60
MSA70
SB40c
AP880A
MDS600
D2600
D2700
AB552A
A9803A
AB551A
AD307A
A6869A
571956-B21
Appendix B (OpenVMS for Integrity servers SAN Solutions)
This appendix describes the HP storage options supported on HP OpenVMS for HP Integrity servers. It is left in this document for
reference.
Please refer to VSI’s web page at http://www.vmssoftware.com for storage options supported by VSI’s OpenVMS.
Enterprise Storage Arrays
EVA
MSA
XP
Adapters and Switches
MDR
NSR
StorageWorks Enterprise Virtual Array 8400, 8100, 8000, 6400, 6100, 6000, 5000, 4400,
4100, 4000, 3000, P6500, P6300
StorageWorks Modular Storage Array 1000, 1500 (NOTE: OpenVMS support for the
MSA1500 requires a minimum MSA firmware of Version 7.), MSA2000fc G2, P2000 G3 FC,
P2000 G3 FC/iSCSI Combo (FC Connect)
StorageWorks XP Storage Array 128/1024, 48/512, P9500, 10000/12000, 20000/24000
DSGGA-AA/B
DSGGD
B-Series, M-Series, and C-Series
Switches
StorageWorks Modular Data Router for connecting SCSI and FC tape devices to a FC switch.
StorageWorks Network Storage Router for connecting SCSI and FC tape devices to a FC
switch.
8/16-port Fibre Channel switch
16-port 2 GB Fibre Channel switch
SAN-based FC Switches as supported by HP StorageWorks, new variants as available via the
following website: http://www.hp.com/go/storage
SAN-attached Tape Libraries
EML-E Series Tape Library
ESL-E Series Tape Library
Enterprise Storage Library
Enterprise Storage LibrarySI
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 28
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Products Supported
ESL9595
Enterprise Storage Library
ESL9322
Enterprise Storage Library
ESL9326
Enterprise Storage Library
ESL9198
Enterprise Storage Library
MSL2024
Business Class Library
MSL4048
Business Class Library
MSL8096
Business Class Library
MSL5000 Series
Modular Storage Library
MSL6000 Series
Modular Storage Library
VLS 6000
Enterprise Virtual Tape Library
VLS9000
Virtual Tape Library
VLS12000
Virtual Tape Library
D2D4106
D2D backup systems
D2D4112
D2D backup systems
D2D4312
D2D backup systems
D2D4324
D2D backup systems
NOTE: OpenVMS supports both SDLT and Ultrium 460/960 tape drives within HP StorageWorks Tape libraries.
For additional information on the SAN-attached Tape Libraries, see this website:
http://www.hp.com/go/storage
For the latest storage hardware device support with OpenVMS Version 8.4-1H1 on Integrity, please refer to this website:
http://www.hp.com/storage/spock
Abbreviations
APMP
ATA
ATAPI
COM
DLT
DSSI
EISA
FDDI
FSE
FWD
GigE
IDE
IEEE
I80277
LVD
MSCP
NCS
PCI
QIC
RAID
RMC
RMS
SDI
SMP
STI
TFF
Adaptive Partitioned Multi-Processing
AT/Attachment
ATA Packet Interface
Component Object Model
Digital Linear Tape
DIGITAL Storage Systems Interconnect
Extended Industry Standard Architecture
Fiber Distributed Data Interface
Fast Single Ended (SCSI)
Fast-Wide Differential (SCSI)
Gigabit Ethernet
Integrated Device (or Drive) Electronics
Institute of Electrical and Electronics Engineers
Intel® 82077 PC Compatible Floppy Interface
Low Voltage Differential
Mass Storage Control Protocol
National Character Set
Peripheral Component Interconnect
Quarter Inch Cartridge
Redundant Array of Independent Disks
Remote Procedure Call
Record Management Services
Standard Drive Interface
Symmetric Multiprocessing
Standard Tape Interface
Terminal Fallback Facility
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 29
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Products Supported
TIE
TMSCP
USB
VLM
XMI
Translated Image Environment
Tape Mass Storage Control Protocol
Universal Serial Bus
Very Large Memory
Extended Memory Interconnect
Software Warranty
This software product is provided by VSI with a 90-day conformance warranty in accordance with the VSI warranty terms applicable
to the license purchase.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 30
Retired
QuickSpecs
VSI OpenVMS Version 8.4-1H1 for Integrity servers
Phase 2
Summary of Changes
Date
28-Sep-2015
Version History
From Version 1 to 2
Action
Changed
Removed
Description of Change:
Overview, standard features, Technical Specifications sections
were updated.
Obsolete Skus removed:
 AB379B
 403619-B21
 508226-B21
© 2015 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and
12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are
licensed to the U.S. Government under vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set
forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
Java is a U.S. trademark of Sun Microsystems, Inc.
Microsoft Windows is a U.S. registered trademark of Microsoft Corporation.
UNIX is a registered trademark of The Open Group.
c04676519 — DA – 15274 Worldwide — Version 2 — September 28, 2015
Page 31
Download PDF
Similar pages