Software Product Description ___________________________________________________________________ PRODUCT NAME: HP OpenVMS Operating System for Alpha Version 7.3-1 and 7.3-2, and VAX Version 7.3 SPD 25.01.68 Note: This SPD describes the HP OpenVMS Operating System software for the Alpha and VAX computer family. Except where explicitly noted, the fea- tures described in this SPD apply equally to both Alpha and VAX sys- tems. HP OpenVMS Alpha and HP OpenVMS VAX operating system licenses and part numbers are architecture specific. Please refer to the Or- dering Information section of this SPD for further details. DESCRIPTION OpenVMS is a general-purpose, multiuser operating system that runs in both production and development environments. OpenVMS Alpha supports Hewlett-Packard's Alpha series computers, while OpenVMS VAX supports VAX, MicroVAX, VAXstation, and VAXserver series computers. OpenVMS soft- ware supports industry standards, facilitating application portabil- ity and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing Alpha and VAX systems. The OpenVMS Alpha operating system provides support for 64-bit virtual memory ad- dressing and Very Large Memory (VLM). 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. Ac- tual system performance depends on the type of computer, available phys- ical memory, and the number and type of active disk and tape drives. October 2003 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. OpenVMS Version 7.3-2 provides the following new features: o Support for new AlphaServer Series ES47. ES80, and GS1280 up to 64 processors. o Support for HP StorageWorks Modular SAN Array 1000 (MSA 1000), a new, high-performance, lower-cost storage array that enables a fabric- based connection from an OpenVMS cluster. o Performance and scalability improvements for LAN adapters, LAN-based cluster interconnects on multiple-CPU Alpha machines, and Smart Ar- ray Backplane RAID Controller. o System performance enhancements to improve OpenVMS scalability and overall system performance. o LAN Failover, which provides the ability to define multiple net- work adapters as a virtual network interface. o XFC performance enhancements to improve overall performance, make more efficient use of memory, and improve displays. o Component Indictment which is the ability to detect and report fail- ing hardware modules for customers using HP's System Event Analyzer product. o Shadowing enhancements by providing dynamic volume expansion (DVE) and dissimilar device shadowing (DDS). o Updates to the OpenVMS BACKUP Utility. o ACME Login Software Development Kit . o Updated versions of Kerberos, CDSA, and OpenSSL security features. o Improved UNIX style security features that allow for ease of port- ing UNIX style applications to OpenVMS. OpenVMS Alpha Version 7.3-1 provides the following: 2 o Automatic and manual failover from a direct Fibre Channel or SCSI storage path to an MSCP served path. o Multipath capability for Fibre Channel tapes. o Improved I/O throughput in a fiber storage environment. o System and application performance improvements in the areas of AST delivery, Mailbox I/O, time queue processing, PEdriver checksum- ming, RMS global buffers, faster SYS$GETJPI service used by the CRTL, and improved kernel threads performance for multithreaded appli- cations. o Improved scaling and performance for applications that use kernel threads because of floating-point registers and execution data block (FRED) enhancements. o Common Data Security Architecture (CDSA) enables the encryption/decryption of data and files on OpenVMS, UNIX[R], and Windows[R] systems. o Industry-standard security through the optional OpenSSL libraries now ported to OpenVMS. o Integrated Kerberos security for Token Based Authentication. o UNIX portability enhancements to enable easier porting of UNIX ap- plications to OpenVMS. o DECdtm XA Gateway and Veneer are enhancements to the DECdtm pro- gramming interface. o HP Secure Web Browser for OpenVMS Alpha (SWB) provides a powerful, flexible, and modern web browser based on Mozilla. The Mozilla web browser is designed for standards compliance, performance, and porta- bility. o Graphical Configuration Manager (GCM) for OpenVMS is a portable client/server application that provides a visual means of viewing and control- ling the configuration of partitioned AlphaServer systems running OpenVMS. 3 o Reduced time to write a system crash dump. OpenVMS Version 7.3 provides the following: o Improved disaster-tolerant capabilities with ATM and Gigabit Eth- ernet as cluster interconnects because of their inherent high-performance and long-distance capabilities. o Greater system availability during backups with faster reintegra- tion of shadow members after copies. o Enhanced OpenVMS support for the latest ENSA Storage offerings. o Greater serviceability for the AlphaServer GS160/320 systems with CPU Online Replace. o Substantial application performance benefits can be realized with the new Extended File Cache. o Improved cluster, SMP, and system performance through enhancements to RMS and the clusterwide Lock Manager, as well as Fast Path sup- port for Fibre Channel and SCSI storage architectures. o Industry Standard Kerberos V5 security, which allows OpenVMS ap- plications to communicate and authenticate with Windows 2000 do- mains and UNIX platforms. o OpenVMS Intrusion Detection expands to be cluster-wide, reducing chances of system break-ins. o Enterprise Capacity and Performance (ECP) Data Collector and ECP Performance Analyzer are now included with the purchase of Open- VMS Version 7.3. The OpenVMS license is expanded to include all of the following new e-business technologies. Additional details can be found in the HP Open- VMS e-Business Infrastructure Package Software Product Description (SPD 80.58.xx). - HP BridgeWorks - COM for OpenVMS - HP Enterprise Directory for e-Business 4 - HP Secure Web Server (based on Apache), including support for Java[TM] Servlets and JavaServer pages (JSP), PHP, and Perl - HP Secure Web Browser (based on Mozilla) - HP Software Development Kit (SDK) for the OpenVMS Operating Sys- tem, for the Java Platform. (HP Fast VM is now bundled with the HP SDK.) - HP XML Technology (based on technology from xml.apache.org) - NetBeans for OpenVMS - HP Reliable Transaction Router (RTR) - Simple Object Access Protocol (SOAP) Toolkit (based on technology from xml.apache.org) Now, with Version 2.0 of HP DECprint Supervisor (DCPS) for OpenVMS, the right to use all DCPS products -Base, -Open, and -Plus is bundled with the OpenVMS Operating System license. Media, documentation, and services are sold separately. USER ENVIRONMENT Users can access the OpenVMS software by using the English-like DIG- ITAL 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. With the DCL command PIPE, individual DCL operations can be connected using a UNIX-like command syntax. OpenVMS prompts users to enter re- quired DCL parameters, making it easy for novice users. Users can enter DCL commands at a terminal or include them in command procedures. These command procedures can be run interactively or sub- mitted to a batch queue for later processing. Information about DCL and OpenVMS utilities is available on line through the OpenVMS Help system. Online help includes summary information on all aspects of system operation. 5 For users who are familiar with the UNIX shell and utilities, Open- VMS is providing an Open Source port of GNU's GNV; that is a GNU-based, UNIX environment for OpenVMS. GNV 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 op- erating system. Text Processing The Extensible Versatile Editor (EVE) is the default editor for Open- VMS. EVE allows users to insert, change, and delete text quickly. Writ- ten in the DIGITAL Text Processing Utility (DECTPU) language, EVE is a full-screen editor that allows users to scroll through text on a ter- minal screen. EVE provides an EDT-style keypad, allowing EDT users to move easily to EVE. EDT is also supported on OpenVMS Alpha Version 7.3 and OpenVMS VAX Version 7.3. 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 prod- uct is installed and licensed on each participating node on the net- work. 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. Users can also use special DCL com- mands to: o Assign symbolic names o Evaluate numerical and logical expressions o Accept parameters o Communicate interactively with the user invoking the command pro- cedure 6 o Perform conditional (IF-THEN-ELSE) and branching (GOTO) logic o Handle error conditions User Environment Tailoring Users can customize the computing environment with login command pro- cedures, shorthand commands, binding of commands to function keys, and command recall and editing. Terminal Fallback Facility (TFF) This facility allows HP 7-bit terminals to input and output the HP Multi- national Character Set (MCS). Specific tables allow conversion for a number of different 7-bit National Replacement Character sets to MCS, such as French, German, Spanish, and Swedish. TFF also allows char- acter composition on terminals that do not have the compose key. National Character Set (NCS) Utility This utility allows users to define non-ASCII string collating sequences and to define conversion functions. Conversion functions use conver- sion algorithms to change an input string; for example, to change low- ercase characters to uppercase. NCS also allows OpenVMS Record Man- agement Services (RMS) indexed files to be collated using user-specified collating sequences. PROGRAM DEVELOPMENT ENVIRONMENT OpenVMS includes a comprehensive set of tools for developing programs, including: run-time libraries (RTLs), a linker, a librarian, and a sym- bolic debugger. The assembly-level VAX MACRO-32 language is supplied with OpenVMS VAX. In addition, the SDK for the Java Platform provides an environment in which to develop and deploy Java applications on Open- VMS Alpha. The following tools are available to the OpenVMS program- mer. HP Software Development Kit (SDK) for the Java Platform 7 The HP SDK for the Java Platform is a set of building blocks contain- ing basic development tools and a rich set of class libraries. 8 Language and Run-Time Library Support OpenVMS includes several RTLs that provide: o String manipulation o Parallel processing support o I/O routines o I/O conversion o Terminal-independent screen handling o Date and time formatting routines o Highly accurate mathematical functions o Signaling and condition handling o Other general-purpose functions With OpenVMS VAX, these routines can be called from programs written in such languages as VAX MACRO-32, Ada, BASIC, VAX BLISS-32 Implemen- tation Language, VAX C, C, C++, COBOL, VAX DIBOL, Fortran, Pascal, and VAX PL/I. With OpenVMS Alpha, these routines can be called from programs writ- ten in such languages as MACRO-32, MACRO-64, Ada, BASIC, C, C++, COBOL, Fortran, Pascal, Java, and PL/I. Also included in OpenVMS Alpha 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 ven- dors. RTLs are provided to support translated images created from user-mode images built on OpenVMS VAX Version 4.0 through Version 5.5-2. Depend- ing on the method used to create the VAX image, these RTLs can be use- ful for images built on later versions of OpenVMS VAX, which do not use features that were developed since OpenVMS VAX Version 5.5-2. 9 Translated image RTLs are used to support a few architectural features that differ between VAX and Alpha systems, such as VAX D-float and H- float. They also support programs converted to run on Alpha systems before native Alpha compilers were available for particular program- ming languages. Many HP languages adhere to the common calling standard. This means that routines written in any of these languages can directly call rou- tines written in any other language. Development of applications us- ing multiple languages is simple and straightforward. All user-accessible routines in the RTLs follow the OpenVMS Alpha or OpenVMS VAX calling standard and condition-handling conventions, and most are contained within shareable images. At a lower level, programs can call system services directly for se- curity, 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 OpenVMS VAX or OpenVMS Alpha 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 re- quired. MACRO Compiler (Alpha Only) With minor modifications, VAX MACRO-32 sources can be compiled for ex- ecution on Alpha. 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. 10 POSIX Threads Library is a library of run-time routines that allows the user to create multiple threads of execution within a single ad- dress space. With POSIX Threads Library Kernel Threads features en- abled, POSIX Threads Library provides for concurrent processing across all CPUs by allowing a multithreaded application to have a thread ex- ecuting on every CPU (on both symmetric and asymmetric multiproces- sor 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 ac- cessed correctly. For scheduling and prioritizing threads, POSIX Threads Library provides multiple scheduling policies. For debugging multi- threaded applications, POSIX Threads Library is supported by the Open- VMS Debugger. POSIX Threads Library also provides Thread Independent Services (TIS), which assist in the development of thread-safe APIs. Visual Threads Visual Threads is a tool available with OpenVMS Version 7.3 that lets you analyze your multithreaded applications. You can use it to debug potential thread-related logic problems, even those hard-to-find prob- lems that only occur because of slight timing differences. You can also use Visual Threads to pinpoint bottlenecks and performance problems by using its rule-based analysis, statistics capabilities and visu- alization techniques. Visual Threads can be used with any application that uses a POSIX threads API (POSIX, DCE, or CMA API), or is written in Java. Visual Threads features include the following: o Detects violation conditions based on the application of partic- ular rules in your application. Several predefined rules look for deadlock conditions, programming errors, and performance issues. o Lets you use templates to define your own rules to specify crite- ria for violation conditions. o Records events to a trace file so that you can play back and an- alyze them later. 11 o Dynamically displays events as they occur, with controls for search- ing and filtering. o Suspends execution of the application when it detects violation con- ditions. You can choose from several options at this point, includ- ing invoking the debugger in the appropriate context for your ap- plication. o Dynamically monitors multithreading objects (threads, mutexes, and so on) in real time. o Provides easy access to object-level statistics and current state information, including use of resources (for example, the mutexes a particular thread holds). o Automatic analysis of lock contention and lock granularity, sta- tistical hotspots, and processor utilization. o Visualizes thread state over time, level of contention, and object- level usage statistics. Librarian Utility The Librarian utility permits storage of object modules, image files, macros, help text, or any general record-oriented information in cen- tral, easily accessible files. Object module and image file libraries are searched by the linker when the linker finds a reference it can- not resolve in one of its input files. Alpha macro libraries are searched by the MACRO-32 compiler and MACRO-64 assembler when either finds a macro name that is not defined in the input file. VAX macro libraries are searched by the MACRO-32 assembler when the assembler finds a macro that is not defined in the input. Hypersort Hypersort is a portable library of user-callable routines that pro- vide a high-performance sorting capability for Alpha systems. 12 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. 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. Alpha System-Code Debugger The OpenVMS Alpha 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 Alpha 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 mem- ory to a preallocated dump file. This dump file can later be analyzed using System Dump Analyzer (SDA). System dumps can either be full mem- ory dumps, where all memory is written, or selective memory dumps, where only portions of memory in use at the time of the system failure is written. The dump file can be located on any locally connected disk. On Alpha only, 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 mem- ory in use at the time of the system failure that will fit into the dump file. Spinlock Tracing Utility 13 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 PRO- CESS utility. This utility uses the same interface and commands as the OpenVMS Debugger to allow registers and memory to be examined. On Al- pha only, another process can initiate the writing of the memory dump. RMS File Utilities Record Management Services (RMS) file utilities allow users to ana- lyze 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. Refer to the Operating System Environment section of this SPD for more information about RMS. File Differences Utility This utility compares the contents of two files and lists those records that do not match. Translated Image Environment (TIE) (Alpha Only) OpenVMS Alpha provides an array of services that allow the operation of programs which have undergone binary translation from OpenVMS VAX images. These programs perform virtually all user-mode functions on OpenVMS Alpha and operate in combination with other programs (images) that have been translated from OpenVMS VAX or have been built using native compilers on OpenVMS Alpha. Without requiring special source code, the TIE resolves differences between the VAX and Alpha archi- tectures, including floating-point registers, condition codes, excep- tion handling, and ASTs. The TIE included with OpenVMS Alpha can run images that have been translated elsewhere. 14 SYSTEM MANAGEMENT ENVIRONMENT OpenVMS provides a variety of features that aid the system manager in configuring and maintaining an optimal system. The following features are available to system managers. CPU Component Indictment With OpenVMS Alpha Version 7.3-2, the Component Indictment feature pro- vides higher system availability by stopping a failing CPU before it can cause a system halt. The component indictment process works in con- junction with a component of HP services tool, Web-Based Enterprise Service (WEBES). The fault-analysis utility, System Event Analyzer, identifies CPUs that are incurring a high or abnormal incidence of cor- rectable errors. System Event Analyzer notifies OpenVMS if a CPU is failing. OpenVMS can then remove the CPU from the active set before it causes the system to fail. CPU Component Indictment is supported on the following AlphaServer sys- tems: ES45, DS25, GS80, GS160, GS320, ES47, ES80, and GS1280. System Event Analyzer (SEA) Version 4.2 (or higher) is also required to be installed and running in automatic analysis mode. For information on the WEBES suite of tools, refer to the following website: http://searay- cxo.cxo.cpqcorp.net/service_tools/webes/. Recordable CD With OpenVMS Version 7.3-1, OpenVMS provides the capability to write once to CD-R media using an application shipping in the base operat- ing system. The feature supports only those writable CD-ROM devices (CD-RW) that ship with Alpha systems. For the application details, please reference the OpenVMS documentation set. For supported platforms sup- porting the CD-RW hardware option, please refer to the appropriate page at the following web site: http://h18002.www1.hp.com/alphaserver/ HP Availability Manager Version 2.2 15 HP Availability Manager is a system management tool that, from either an OpenVMS Alpha or a Wintel node, enables you to monitor one or more OpenVMS nodes on an extended local area network (LAN). This tool helps system managers and analysts target a specific node or process for de- tailed analysis. The Availability Manager collects system and process data from multiple OpenVMS nodes simultaneously. It analyzes the data and displays the output using a native Java GUI. It is included in the OpenVMS distribution kit. The Availability Manager tool evolved from the OpenVMS only DECamds product and its Motif graphical user interface (GUI). Because the Avail- ability Manager Data Analyzer requires a run-time environment, it does not run on OpenVMS VAX, which does not support Java. To run the Data Analyzer on VAX systems, you should use DECamds. Availability Manager packages its own Java environment. Availability Manager's Java environment will not conflict with any other Java en- vironment installed on the system. HP recommends using, at a minimum, the following hardware configuration: 500 MHz Alpha processor with 192 MB of memory. The Availability Manager for OpenVMS kit includes the Data Analyzer and Data Collector: o The Data Analyzer can be installed only on OpenVMS Alpha Versions 7.1, 7.1-2, 7.2, 7.2-1, 7.2-1 variants, 7.3, and 7.3-1. o The Data Collector can be installed on OpenVMS VAX and Alpha Ver- sions 6.2, 7.1, 7.1-2, 7.2, 7.2-1, 7.2-1 variants, 7.3, and 7.3- 1. On a Windows system, HP recommends using the following hardware con- figuration: o Windows 2000 or XP-400 MHz Intel[R] Pentium[R] processor with 192 MB of memory You can install the Availability Manager Data Analyzer on any system running Windows 2000 Service Pack 2 or Windows XP. You must deinstall previous versions of Availability Manager before installing Version 2.2. 16 DECamds DECamds is available on the OpenVMS distribution kit. DECamds is a sep- arately installable, real-time, high-performance, multisystem moni- toring utility. It is supported on any system running OpenVMS Version 7.1 or higher. With OpenVMS Version 7.1, the right to use DECamds was included under the terms and conditions of the OpenVMS operating sys- tem base license for both Alpha and VAX. DECamds is the predecessor of the newer application Availability Manager. DECamds provides system resource monitoring, investigation aid, and correction capability. This enables system managers to proactively and effectively manage multiple systems from a centralized DECwindows dis- play. DECamds software includes an OpenVMS device driver, which is in- stalled on every node on the LAN that is to be monitored. The soft- ware includes a Motif GUI application that allows a system manager to perform monitoring functions. The Motif application can be installed on any OpenVMS Alpha or VAX workstation. DECamds is currently in main- tenance mode. All new system management functionality requested for DECamds will be directed to the Availability Manager product. HP Management Agents for OpenVMS HP Insight Management Agents for OpenVMS consists of a web server for system management, with management agents that allow you to communi- cate with devices on their OpenVMS systems over the Internet or In- tranet. Management Agents for OpenVMS utilizes the Web-Based Enter- prise Management (WBEM) architecture. This is an architecture that al- lows one to use a web browser to monitor many devices that are con- nected to a network. Devices can be computer systems, networked print- ers, or network components such as routers. WBEM uses a three-tiered architecture that includes a management server, devices managed by web agents, and a web browser. Management Agents for OpenVMS uses SNMP and TCP/IP protocols that al- low the management server to communicate with OpenVMS devices. The man- agement agents use common web-enabling components to provide regis- tration, discovery, HTTP communications, and a home page for the man- aged devices. The management agents can send information directly to 17 the management server or they can create an HTML file to communicate directly with a browser. Management Agents for OpenVMS utilizes HP Insight Manager 7 on a Mi- crosoft Windows server as the management server/application. With the introduction of Insight Manager, management of all your HP platforms inclusive of OpenVMS from a single Windows server becomes a possibil- ity. Insight Manager, which is an example of a management server/application, is a web-based interface that enables you to look across a heteroge- neous computing services environment and access information about de- vices connected to the network. Using Insight Manager, you can obtain information about the configuration of OpenVMS systems and their com- ponents or peripherals. Management Agents for OpenVMS is an example of an Insight Manager web agent. It provides the means of communica- tion between OpenVMS devices and the web browser. The Insight Manager management server provides a single reference point for data from all devices. The management server uses its connection with the web browser to display device data to the user. Management Agents for OpenVMS is available from the following web page: http://h71000.www.7.hp.com/openvms/products/mgmt_agents/ HP OpenVMS Management Station HP OpenVMS Management Station is a powerful, Microsoft Windows based management tool for system managers and others who perform system man- agement tasks on OpenVMS systems. OpenVMS Management Station features a powerful, intuitive user interface. System managers and help desk staff no longer need to remember complicated DCL syntax or command pro- cedures to manage their OpenVMS systems. OpenVMS Management Station makes system management much easier. Three functional areas are now implemented in OpenVMS Management Sta- tion: user account management, printer queue management, and storage configuration management. For user account management, OpenVMS Man- agement Station supports account creation, modification, and deletion, as well as renaming accounts and displaying account attributes. Printer queue management makes it possible for system managers to manage all 18 printers, print queues, and jobs in their environment using a central- ized Windows GUI. This includes monitoring one or more printers, adding or removing printers, and their associated queues, examining and mod- ifying queue and printer attributes, and requeuing or deleting jobs. The storage configuration facility of the OpenVMS Management Station makes it easy for you to manage disk storage devices across multiple OpenVMS Cluster systems and OpenVMS nodes. With OpenVMS Management Sta- tion, you no longer need to maintain complicated command files to con- trol the storage environment. You can create, delete, and manage stor- age from an easy-to-use Windows interface. It provides a persistent database that can automatically determine and configure the storage configuration at system startup. OpenVMS Management Station is based on the Microsoft Management Con- sole (MMC). The Microsoft Management Console provides a common man- agement framework for various administration programs. OpenVMS Man- agement Station is implemented as an MMC snap-in and includes all of the MMC components you need. Features include: o Storage configuration management-You can create, delete, and man- age a disk volume under one interface. Wizards make it easy to add systems to be managed, create a volume, and so forth. o Configuration control over reboots- If you allow it to, OpenVMS Man- agement Station preserves the disk configuration across reboots. OpenVMS Management Station can mount and maintain your storage con- figuration without intervention. And, OpenVMS Management Station mounts volumes much faster than is possible with DCL or command pro- cedures, so performance is enhanced. o Coexistence with established environment-You do not have to change your existing DCL command procedures if you don't want to. You can use the display capabilities of OpenVMS Management Station with- out having to use the automated mount feature. In this way, you can give OpenVMS Management Station as little or as much control as you are comfortable with. 19 o Remote management supported-You can use OpenVMS Management Station to remotely manage your OpenVMS systems. Once you establish a TCP/IP RAS connection, you can then use OpenVMS Management Station to man- age your OpenVMS systems from home or on the road. Note: The version of MMC included in this baselevel requires files provided by Microsoft Internet Explorer. Version 3.02 or later of Internet Ex- plorer must be present on the system. The OpenVMS Management Station client supports only TCP/IP connections for primary servers, so at least one OpenVMS system must be running TCP/IP. If you are running Version 6.2 of OpenVMS and plan to manage shadow volumes, remedial kits are required. Additional TCP/IP stacks for OpenVMS have not been tested. However, TCP/IP stacks that are 100% compliant with the QIO interface for TCP/IP Services for OpenVMS should also work. Contact your TCP/IP vendor for additional information and support issues. 20 ECP Data Collector and ECP Performance Analyzer Beginning with the release of OpenVMS Version 7.3, ECP Data Collec- tor and ECP Performance Analyzer, engineered and supported by HP, are licensed with the OpenVMS operating system and available from the Open- VMS System Management web page at: http://h71000.www7.hp.com/openvms/system_management.html ECP Data Collector and ECP Performance Analyzer are licensed with the OpenVMS Alpha and VAX Operating Systems Version 6.2 or later. ECP Data Collector is a highly efficient, detailed performance data collector and ECP Performance Analyze provides graphic historical re- porting of OpenVMS performance parameters. Satisfying the needs of En- terprise Management, ECP provides an interface for the access of col- lected performance data. This interface converts the contents of the .CPC data file generated by the data collector into a formatted, comma- separated ASCII file that can then be used for performance analysis and reporting programs. The ECP Data Collector provides: o Robust data collection set-It collects more system metrics than other vendors (for example, over 250 OpenVMS performance parameters). o Flexible data collection-The sampling rate of data can be tuned down to sub-second intervals. o Low overhead-Audited production systems now running have routinely shown that the collector has less than 1.5% impact on CPU. The ECP Performance Analyzer provides: o Native OpenVMS product running under Motif o Viewing of performance data in graphical format o Analyzed data including CPU, memory, and I/O o User-selected sampling rate 21 Software support service for these products is sold separately. Please contact your HP services representative for further details. Graphical Configuration Manager (GCM) for OpenVMS V1.0 The Graphical Configuration Manager (GCM) for OpenVMS is a portable client-server application that provides a visual means of viewing and controlling the configuration of partitioned AlphaServer systems run- ning OpenVMS. The GCM client, a Java-based application, can run on any operating system that supports a TCP/IP network and the Java run-time environment-JDK V1.2.2 or higher. (Currently, the GCM client is not supported on Java JDK Version 1.3 or higher.) A GCM server runs as a detached process on each partitioned OpenVMS instance on one or more AlphaServer systems. All network communication that GCM performs uses the Secure Sockets Layer (SSL). The GCM administration database is encrypted. From a GCM client, an OpenVMS system manager can establish a secure connection to one or more GCM servers and can perform the following functions: o Display the configuration of partitioned AlphaServer systems o Utilize hot-swap characteristics of the current hardware platform o Execute distributed commands among partitioned instances o Reassign resources among soft-partitioned instances o View resource-specific characteristics o Shut down or reboot one or more instances o Invoke additional management tools o Create and engage Galaxy configuration models o View online documentation Class Scheduler for CPU Scheduling 22 With OpenVMS Version 7.3, a new SYSMAN-based interface for defining and controlling scheduling classes has been added. This new class sched- uler for both Alpha and VAX systems allows you to designate the per- centage of CPU time that a system's users 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 interme- diate queue that holds a job until an appropriate execution queue be- comes available to initiate the job. An execution queue is a queue through which the job (either print or batch) is actually processed. The system queues batch jobs for execution. The system manager can reg- ulate the number of queues and the number of streams per queue (the number of batch jobs in the queue that can execute concurrently). Both generic and execution batch queues can have different attributes, such as the maximum CPU time permitted, working set size, and prior- ity. Facilities are provided for starting and stopping queues and for starting and stopping jobs in a queue. Because multiple execution queues can be associated with a generic queue, OpenVMS VAX enables load bal- ancing across available CPUs in an OpenVMS Cluster system, increas- ing overall system throughput. Print queues, both generic and execution, together with queue manage- ment facilities, provide versatile print capabilities, including sup- port for various print file formats. The maximum number of process identifiers for queuing requests is 1024. Accounting Utility 23 For accounting purposes, OpenVMS keeps records of system resource us- age. These statistics include processor and memory utilization, I/O counts, print symbiont line counts, image activation counts, and pro- cess 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 se- curity and deter possible intruders. The OpenVMS Audit Analysis util- ity 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 config- uration 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 pa- rameter settings based on previous usage patterns. Backup Utility The Backup utility provides both full-volume and incremental file back- ups 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 save set or list the contents of a save set. 24 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: o Access to the save, restore, and list operations without having to understand Backup command syntax o The ability to create, modify, recall, and delete Backup Manager templates that describe the Backup save operations The Backup Manager works on all supported OpenVMS configurations with a video terminal. It uses the Screen Management (SMG) RTL routines to provide a window-like user interface. The software does not assume any privilege on the part of its user beyond access to the files and de- vices being operated upon. Standalone BACKUP Utility (VAX Only) Standalone BACKUP provides a mechanism for system managers to back up and restore system disks. This utility can also be used during the in- stallation of the OpenVMS VAX operating system. Analyze Disk Structure Utility 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. Monitor Utility The Monitor utility enables the system manager to monitor different classes of systemwide performance data including: process activity, I/O activity, memory-management activity, vector-processing activity (VAX only), and two-phase, commit-transaction activity at specified intervals. The data can be displayed as it is gathered or saved in a file for later use. 25 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. 26 System Management Utility (SYSMAN) The System Management utility allows system managers to define a man- agement environment in which operations performed from the local Open- VMS system can be executed on all other OpenVMS systems in the envi- ronment. The environment can include OpenVMS Alpha and VAX systems con- figured in an OpenVMS Cluster or multiple systems networked through HP DECnet or HP DECnet-Plus. Operations OpenVMS allows for varying levels of privilege to be assigned to dif- ferent 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 admin- istrators, and system managers. Security OpenVMS provides the following optional standards-based cryptographic security solutions to protect your information and communications. Secure Sockets Library (SSL for OpenVMS) Protecting communication links over a TCP/IP connection to an Open- VMS applictions can be accomplished through the use of the Secure Sock- ets Library. The OpenSSL APIs establish private, authenticated and re- liable communications link between applications. SSL for OpenVMS Version 1.0A is based on OpenSSL 0.9.6B and includes the security patches that address the buffer overflow vulnerabilities. The following has been added to SSL for OpenVMS: o 64-bit API support o Menu-driven certificate tool o A VMS Pseudo Random Number Generator o Enables SSL to run on any TCP/IP package on OpenVMS 27 o SSL Manual added to the OpenVMS documentation set Common Data Security Architecture (CDSA) The Common Data Security Architecture (CDSA) port for OpenVMS provides a security infrastructure that allows for the creation and deployment of multiplatform, Open Source industry standard cryptographic solu- tions. CDSA provides a flexible mix-and-match solution among a vari- ety of different applications and security services. This allows for compliance to local regulation while keeping the security underpin- nings transparent to the end user. Kerberos Kerberos Version 1.0 for OpenVMS Alpha and OpenVMS VAX, based on MIT Kerberos Version 5 Release 1.0.5, is included on the OpenVMS Version 7.3 distribution media. (Kerberos documentation provided by MIT is in- cluded on the OpenVMS documentation CD-ROM in HTML format.) Kerberos is a network authentication protocol designed to provide strong authentication for client/server applications by using secret-key cryp- tography. The Kerberos for OpenVMS authentication system, based upon work done by Massachusetts Institute of Technology (MIT), is provided in three separate components: o Key Distribution Center (KDC) server o Client subsystem o Two application programming interfaces, one written to comply with the Generic Security Service Application Programming Interface (GSS- API V2) specification as defined by RFC2078. The second API presents the Kerberos interface to the users. Both APIs are delivered as share- able images on OpenVMS. 28 Kerberos was created by the Massachusetts Institute of Technology as a solution to network security problems. The Kerberos protocol uses strong cryptography so that a client can prove its identity to a server (and vice versa) across an insecure network connection. After a client and server have used Kerberos to prove their identity, they can also encrypt all of their communications to assure privacy and data integrity. General information about Kerberos is available from the following World Wide Web address: http://web.mit.edu/kerberos/www/ Per-Thread Security Profiles Thread-level security allows for simplified multiprofile application development and improves overall performance while maintaining a high level of security. This feature allows each execution thread of a mul- tithreaded process to run an independent security profile without im- pacting the security profiles of other threads in the process. This feature, known as per-thread security profiles, includes a new security structure, known as the Persona Security Block (PSB), which supersedes many process-wide structures and fields, including the ARB, JIB username and account information, PHD privilege bits, and the PCB NOAUDIT cell. A new SYSGEN parameter, ARB_SUPPORT, has been added to allow system managers to control the level by which the current security data in the PSB will be backported to these old privilege data cells. There are four levels of support ranging from NONE (ARB_SUPPPORT = 0) to FULL (ARB_SUPPORT = 3). External Authentication External authentication is an optional feature that enables OpenVMS systems to authenticate designated users within a LAN Manager domain using their LAN Manager user name and password. 29 If you want to enable external authentication on your system, you need HP DECwindows Motif Version 1.2-4 or later and any requirements out- lined in the Advanced Server for OpenVMS Server Installation and Con- figuration Guide and the PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide. See these manuals and the Open- VMS Guide to System Security for detailed information about using ex- ternal authentication. For additional information on HP Advanced Server for OpenVMS and HP PATHWORKS for OpenVMS, refer to the Associated Prod- ucts section of this SPD. 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. In addition, the OpenVMS DCL com- mand SET PASSWORD has been enhanced to update the user's password in the LAN Manager domain database (as well as to synchronize the SYSUAF password). For externally authenticated users, the normal system authorization database (SYSUAF.DAT) is used to construct the OpenVMS process pro- file (UIC, privileges, quotas, and so on) and to apply specific lo- gin restrictions. However, there are two key differences between ex- ternally authenticated users and normal OpenVMS users. For externally authenticated users: o The password stored in the SYSUAF is not the password used to ver- ify the user at login time. o The SYSUAF user name selected to be used for OpenVMS process iden- tification may not be the same as the LAN Manager user name that was used to authenticate the user at login. The system manager spec- ifies the LAN Manager to OpenVMS user name mapping for each user. Authentication and Credential Management ($ACM) The Authentication and Credential Management ($ACM) service provides a common interface to all functions for performing authentication-related operations. 30 On a given OpenVMS system, multiple authentication policies may be ap- plicable. The system may be configured to augment the native (local OpenVMS) policy with alternatives pertaining to external environments, such as LAN Manager. Each policy, together with the operating envi- ronment to which it pertains, constitutes a domain of interpretation. Within a given domain, any entity, such as a user, that is subject to the applicable authentication policy, is referred to as a principal. The $ACM service can be used to authenticate a principal, initiate a password change request on behalf of a principal, query information about a particular domain, or report event data within a particular domain. Security APIs Security APIs for intrusion detection, proxy access, and impersonation services are available on both the Alpha and VAX platforms to provide better security in client/server applications. With OpenVMS Version 7.3, intrusion detection capabilities are expanded to be clusterwide. The Security Persona services provide the ability to support alter- nate security models. OpenVMS security persona services allow Open- VMS applications the ability to attach NT or any other non-OpenVMS se- curity credentials to an OpenVMS security profile. Government Security Ratings As the following table illustrates, OpenVMS is committed to consis- tently delivering rated security in our base products. 31 ___________________________________________________________________ OpenVMS Alpha E3 2001 6.2-1H3+ OpenVMS Alpha 6.1 C2 1996 SEVMS Alpha 6.1 B1 1996 OpenVMS VAX 6.1 C2 1995 SEVMS VAX 6.1 B1 1995 OpenVMS VAX 6.0 C2 1993 SEVMS VAX 6.0 B1 1993 VAX/VMS 4.3 C2 1988 ___________________________________________________________________ +Currently_in_ITSEC_Rating_________________________________________ These ratings represent the National Computer Security Center validation of the design of the OpenVMS and SEVMS operating sys- tems against DoD 5200.28-STD Department of Defense Trusted Com- puter System Evaluation Criteria. To obtain an evaluation summary, please visit the US NCSC at Trusted Product Evaluation Program (TPEP) home page at: http://www.radium.ncsc.mil/tpep/ OpenVMS provides a rich set of tools to control user access to system-controlled data structures and devices that store infor- mation. 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. The system manager maintains user account information in the sys- tem user authorization file (SYSUAF). When creating user accounts with the Authorize utility, the system manager assigns the priv- ileges and quotas associated with each user account. The system 32 manager also assigns a user name, password, and unique user iden- tification code (UIC) to each account. Additional identifiers can be assigned to each account, allowing users to belong to multi- ple overlapping groups or projects. The system manager can limit account use by the time of day, day of week, and type of access, such as local, remote, network, or batch. 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. OpenVMS provides a password dictionary filter that screens pass- word choices for common words, and a user password history filter that prevents users from re-using passwords that they have used within the past year. In addition to these built-in filters, a site can design and install its own filter to screen passwords according to a site-specific password policy. The system password hash algorithm can also be replaced with a private algorithm for those sites that have contractual obliga- tions to use specific public or private password encryption algo- rithms. The system manager can enable this feature on a per-user, per-password basis. Login security includes break-in detection, which disables ter- minals when password guessing is detected. Users retain a secure login path, which can thwart Trojan horse attacks against local terminals. Additionally, the system manager can associate a system password with dial-in terminal lines to prevent the display of any operating system-specific identification that might yield clues to possible attack methods. When a user logs in, the system displays a message stating when the last login for the account occurred and the number of failed attempts since the last successful login. 33 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. Sys- tem objects also have a protection mask that allows read, write, execute, and delete access to the object's owner, group, privi- leged system users, and to all other users. The system manager can protect system objects with access control lists (ACLs) that al- low access to be granted or denied to a list of individual users, groups, or identifiers. ACLs can also be used to audit access at- tempts to critical system objects. OpenVMS applies full protection to the following system objects: o Capabilities (VAX only) o Common event flag clusters o Devices o Files o Group global sections o Logical name tables o Batch/print queues o Resource domains o Security classes o System global sections o ODS-2 volumes o ODS-5 volumes OpenVMS provides security attribute defaults in the form of se- curity profile templates. These templates are referenced whenever a new object is created and provide a means of associating de- fault security information with each system object class, except for files. Protection information for files is inherited from the previous version of an existing file, the parent directory, or the default protection of the creating process. 34 Data scavenging protection can be enabled in the form of high- water marking and erase-on-delete attributes. These attributes ensure that the contents of a file cannot be read after the file has been deleted. The system manager can enforce file erasure on a per-volume basis. The system manager can also replace the disk erasure pattern with a private pattern for those sites that have contractual obligations to use a specific pattern. 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: o Login and logout o Login failures and break-in attempts o Object creation, access, deaccess, and deletion; selectable by use of privilege, type of access, and on individual objects o Authorization database changes o Network logical link connections for DECnet for OpenVMS, DECnet-Plus, DECwindows, IPC, and SYSMAN o Use of identifiers or privileges o Installed image additions, deletions, and replacements o Volume mounts and dismounts o Use of the Network Control Program (NCP) utility o Use or failed use of individual privileges o Use of individual process control system services o System parameter changes 35 o System time changes and recalibrations Note: Because no system can provide complete security, HP cannot guarantee complete system security. However, HP continues to en- hance the security capabilities of its products. Customers are strongly advised to follow all industry-recognized security prac- tices. OpenVMS recommended procedures are included in the OpenVMS Guide to System Security. OPERATING SYSTEM ENVIRONMENT OpenVMS VAX Processes and Scheduling The basic unit of execution in OpenVMS VAX is the process. A pro- cess consists of individual address space and registers known as context, and code called an executable image. The context iden- tifies the process and describes its current state. Executable images consist of system programs and user programs that have been compiled and linked. The maximum number of concurrent processes is 8,192 per OpenVMS VAX system. Processes receive time to execute their images based on the prior- ity. Thirty-two priorities are recognized on OpenVMS VAX, and 64 priorities are recognized on OpenVMS Alpha. Priorities 0 to 15 are for timesharing processes and applications (four is the typical default for timesharing processes). Priorities 16 to 32 on VAX and 16 to 63 on Alpha are for real-time processes. Each time an event such as an I/O interrupt occurs, the system services the event first and then passes control to the highest priority process ready to execute. The system automatically ad- justs the priorities of processes in the range of 0 to 15 to favor I/O-bound and interactive processes. However, the system does not adjust the priority of a process in the range of 16 to 31 for VAX or 16 to 63 for Alpha. 36 Real-time processes can be assigned higher priorities to ensure that they receive processor time whenever they are ready to ex- ecute. Real-time processes are scheduled preemptively; that is, if a real-time process is ready to execute, it is given to the processor immediately, unless a process with a higher priority is ready to execute. OpenVMS uses paging and swapping to provide sufficient virtual memory for concurrently executing processes. Paging and swapping are also provided for processes whose memory requirements exceed available physical memory. The maximum working set size is 512 MB of memory for VAX and 4 GB for Alpha. Programmers can control memory management from within an image. An image executing in a real-time process, for example, can inhibit paging or swapping of critical code and data. Peripheral devices can be managed by the system or allocated by individual processes. At least one disk must be a system disk. Other disks can be designated as data disks for the general use of all users logging in to the system or for a specific group of users. The system controls interactive terminals and one or more printers. OpenVMS Alpha Processes and Scheduling The basic unit of execution in OpenVMS Alpha is the kernel thread. A kernel thread consists of individual address space and registers known as context, and code called an executable image. The context identifies the kernel thread and describes its current state. Each process can have up to 256 kernel threads. Executable images con- sist of system programs and user programs that have been compiled and linked. The maximum number of concurrent processes is 16,384 per OpenVMS Alpha system. 37 Kernel threads receive processor time to execute their images based on the priority of the process. Thirty-two priorities are recognized on OpenVMS VAX, and 64 priorities are recognized on OpenVMS Alpha. Priorities 0 to 15 are for time-sharing processes and applications (four is the typical default for timesharing processes). Priorities 16 to 32 on VAX and 16 to 63 on Alpha are for real-time processes. Each time an event such as an I/O interrupt occurs, the system first services the event and then passes control to the highest priority kernel thread ready to execute. The system adjusts the priorities of kernel threads whose base priority is in the range of 0 to 15 to favor I/O-bound and interactive processes. However, the system does not adjust the priority of a kernel thread in the range of 16 to 31 for VAX or 16 to 63 for Alpha. Real-time processes can be assigned higher priorities to ensure that they receive processor time whenever they are ready to exe- cute. Real-time processes are scheduled preemptively; that is, if a real-time process is ready to execute, it is given to the pro- cessor immediately, unless a higher priority process is 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. Programmers can control memory management from within an image. An image executing in a real-time process, for example, can inhibit paging or swapping of critical code and data. Peripheral devices can be managed by the system or allocated by individual processes. At least one disk must be a system disk. Other disks can be designated as data disks for the general use of all users logging in to the system or for a specific group of users. The system controls interactive terminals and one or more printers. 64-Bit Virtual Addressing (Alpha Only) 38 The OpenVMS Alpha operating system provides support for 64-bit virtual memory addressing. This capability makes the 8 TB virtual address space, defined by the Alpha architecture, available to the OpenVMS Alpha operating system and to application programs. Future hardware implementations will provide greater capacity. OpenVMS Alpha compilers and applications take advantage of 64-bit processing by using 64-bit data types. Refer to the SPDs for the OpenVMS Alpha compilers for further details. Note that the appli- cation virtual address space defaults to a 32-bit implementation for compatibility and migration purposes. Very Large Memory (VLM) Features (Alpha Only) OpenVMS Alpha provides the following additional memory management VLM features beyond those provided by 64-bit virtual addressing: o Memory-resident global sections o Fast I/O for global sections o Shared page tables o Expandable global page table o Reserved memory registry Memory-resident global sections allow a database server to keep larger amounts of "hot" data cached in physical memory. The database server then accesses the data directly from physical memory without performing I/O read operations from the database files on disk. With faster access to the data in physical memory, run-time performance increases dramatically. As of OpenVMS Alpha Version 7.2, VLM applications that share a large memory-resident cache can use Fast I/O for memory shared by processes through global sections. Fast I/O improves the abil- ity of a VLM application, such as a database server, to handle larger capacities and higher data throughput rates. By reducing the CPU costs per I/O request, Fast I/O and memory-resident global sections dramatically increase performance for critical database server I/O operations. 39 Shared page tables allow that same database server to reduce the amount of physical memory consumed within the system. Because multiple server processes share the same physical page tables that map the large database cache, an OpenVMS Alpha system can support more server processes. This increases overall system capacity and decreases response time to client requests. Also, with shared page tables, the database server startup time is dramatically reduced because server processes can map memory- resident global sections hundreds of times faster than traditional global sections. With a multiple-gigabyte global database cache, the server startup performance gains can be significant. The system parameters GBLPAGES and GBLPAGFIL are dynamic parame- ters. Users with the CMKRNL privilege can change these parameter values on a running system. Increasing the value of the GBLPAGES parameter allows the global page table to expand, on demand, up to the new maximum size. The Reserved Memory Registry supports memory-resident global sec- tions and shared page tables. Through its interface within the SYSMAN utility, the Reserved Memory Registry allows an OpenVMS system to be configured with large amounts of memory set aside for use within memory-resident sections or other privileged code. The Reserved Memory Registry also allows an OpenVMS system to be prop- erly tuned through AUTOGEN, thus accounting for the preallocated reserved memory. Extended Physical Addressing (VAX Only) Physical address space is 32 bits. The OpenVMS VAX operating sys- tem can provide 3.5 GB of physical memory and .5 GB of I/O and adapter space. This enables large applications and workloads to access the large amounts of physical memory that they require. The following table lists the VAX processors that support this extended physical addressing: 40 _________________Accessible________________________________________ Physical System___________Memory______I/O_and_Adapter_Space_________________ VAX 6000 1.25 GB .5 GB Model 600 VAX 7000 3.5 GB .5 GB Series VAX 10000 3.5 GB .5 GB Series_____________________________________________________________ Vector Processing (VAX Only) A single data item with only one value is known as a scalar value. A group of related scalar values, or elements, with the same data type, is known as a vector. An extension to the VAX architecture defines an optional design for integrated vector processing that has been adopted by several VAX systems. The VAX vector architecture includes sixteen 64-bit vector registers (V0 through V15), each containing 64 elements, vector control registers, vector function units, and a set of vector instructions. VAX vector instructions transfer data between the vector registers and memory, perform integer and floating- point arithmetic, and execute processor control functions. A more detailed description of the VAX vector architecture, vector registers, and vector instructions appears in the VAX MACRO and Instruction Set Reference Manual. The OpenVMS VAX operating system provides fully shared, multipro- gramming support for VAX vector processing systems. By default, OpenVMS VAX loads vector support code when initializing vector- present systems but does not load it when initializing vector- absent systems. System managers can control this behavior by using the VECTOR_PROC system parameter. 41 The presence of vector support code in a system has little effect on processes running in a scalar-only system, or scalar processes running in a vector-present system. If many processes must compete simultaneously for vector processor resources, the system manager can maintain good performance by adjusting system resources and process quotas. The OpenVMS VAX operating system makes the services of the vec- tor processor available to system users by means of a software abstract known as a capability. A system manager can restrict the use of the vector processor to users holding a particular identi- fier by associating an ACL entry with the VECTOR object. The VAX Vector Instruction Emulation Facility (VVIEF) is a stan- dard feature of the OpenVMS VAX operating system. It allows vec- torized applications to be written and debugged in a VAX system in which vector processors are not available. VVIEF emulates the VAX vector processing environment, including the nonprivileged VAX vector instructions and the OpenVMS VAX vector system services. Use of VVIEF is restricted to code in user mode. DECdtm Services The DECdtm services embedded in the OpenVMS operating system sup- port fully distributed databases using a two-phase commit proto- col. The DECdtm services provide the technology and features for distributed processing, ensuring both transaction and database integrity across multiple HP resource managers. Updates to dis- tributed 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 HP data management prod- ucts. 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: 42 o Embedded OpenVMS system services that support the DECtp archi- tecture, providing the features and technology for distributed transaction processing. o Ability for multiple disjoint resources to be updated automat- ically. These resources can be either physically disjointed on different clusters at separate sites, or logically disjointed in different databases on the same node. o 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). o Robust application development. Applications can be written to ensure that data is never in an inconsistent state, even in the event of system failures. o Ability to be called using any HP TP monitor or database prod- uct. This is useful for applications using several HP database products. 43 Interprocess Communication OpenVMS provides the following facilities for applications that consist of multiple cooperating processes: o Mailboxes as virtual devices that allow processes to communi- cate with queued messages. o Shared memory sections on a single processor or an SMP system that permit multiple processes to access shared address space concurrently. o Galaxywide sections on a Galaxy platform that permit multiple processes in multiple instances to access shared address space concurrently. o Common event flags that provide simple synchronization. o A lock manager that provides a more comprehensive enqueue/dequeue facility with multilevel locks, values, and asynchronous system traps (ASTs). o 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. o Logical names through which one process can pass information to other processes running on the same system or on different OpenVMS Cluster nodes. o 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 both Alpha and VAX 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. 44 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 Alpha or OpenVMS VAX 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 special- ized 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 sys- tem entity, it is configured into a network and OpenVMS Cluster configurations as a single node. The maximum number of supported CPUs in an SMP configuration is 32. Networking Facilities OpenVMS provides device drivers for all HP local area network (LAN) adapters listed in the LAN Options section of Appendix A of this SPD. Application programmers can use the QIO system service to communicate with other systems connected via the LAN using ei- ther 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 standards defined by the ATM Forum's LANE Version 1.0 specifications for LAN emulation over an ATM network. By implementing an emulated LAN over an ATM network, you enable a group of ATM stations to act like a traditional LAN. LAN emulated over an ATM network allows you to run your existing applications basically unchanged, while the computers on which your applica- tions are running are connected to the ATM network. 45 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 pro- vides 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 us- ing 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. DECnet for OpenVMS VAX and Alpha offers the networking capabil- ities as defined in the DIGITAL Network Architecture (DNA) Phase IV. For more information, refer to the Associated Products section of this SPD. Terminal Server Products HP's terminal server products provide terminal server access to OpenVMS. When used in an OpenVMS Cluster environment, terminal servers distribute users across the available Alpha and VAX sys- tems at login time. OpenVMS can also establish a connection to other devices (such as printers) attached to such terminal servers. Universal Serial Bus Support With the OpenVMS V7.3-1 TIMA update kit, VMS731-EV7-V0100, and the AlphaServer ES47 and GS1280 systems, OpenVMS supports the Univer- sal Serial Bus (USB) technology. Support for the USB interconnect enables OpenVMS systems to connect to multiple supported USB de- vices using a single USB cable. OpenVMS supports the fully qual- ified USB devices listed in the appropriate AlphaServer platform configuration and options web site: http://h18002.www1.hp.com/alphaserver/ Reliability 46 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: o Processor errors. These include processor soft errors, proces- sor hard errors, processor machine checks, and adapter errors. o Memory errors. These can be unrecoverable (hard) errors or re- coverable (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 sys- tems with error correction code (ECC) memory. On OpenVMS VAX, an unrecoverable error causes the memory page on which the er- ror occurred to be added to the bad page list. If the page has not been modified, system operation continues with a new copy of the page. o Correctable memory errors. A primary cause of these correctable memory errors is alpha particle radiation. On some processors, when correctable 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. Subse- quent 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 correctable 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. On OpenVMS VAX, if the cause of the error is not transient, and the error condition persists, the operating system attempts to 47 move the data from the existing page, which contains the error, to a new page. The original page is then retired from use. Other failures include: o Operating system errors (system-detected inconsistencies or architectural errors in system context) o User errors o I/O errors The system logs all processor errors, all operating system errors detected through internal consistency checks, all double-bit mem- ory 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 Sys- tem Dump Analyzer (SDA) utility is provided for analyzing memory dumps. Power Failures (VAX Only) If the power fails, the system shuts down automatically. When power is restored, the system restarts automatically and resumes processing at the point of interruption under these circumstances: o If the system has a time-of-day clock and a memory battery backup unit o If the contents of memory are still valid o If the system is set to permit automatic rebooting The system restarts device and communication lines and all I/O operations in progress, including magnetic tape I/O operations. On request, programs can be notified of power restoration. An optional battery-operated hardware clock resets the date and time of day when the system restarts. If the system does not have a battery backup unit, or if the memory contents are not valid on 48 power restoration, the system reboots automatically if it is set to permit automatic rebooting. If, for any reason, after a power failure the system disk does not come back on line within a specific time after the CPU regains power, the system shuts down. 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 lan- guages and can be used to perform low-level I/O operations effi- ciently 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. HP supplies drivers for all devices supported by the OpenVMS operating system and pro- vides 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. With OpenVMS Alpha, users can write drivers for I/O devices that do not have inherent OpenVMS support. OpenVMS Alpha allows de- vice drivers to be written in C and MACRO-32. Documentation is available that describes how to write OpenVMS Alpha device drivers and how to convert existing OpenVMS VAX drivers to run on Open- VMS Alpha systems. The C compiler for OpenVMS Alpha is an optional layered product. With OpenVMS VAX, users can write their own drivers in MACRO-32 for I/O devices that do not have inherent OpenVMS support, as described in the appropriate documentation. I/O Performance Features 49 Fast I/O provides a suite of additional system services that ap- plications can use to improve I/O throughput. The fast I/O ser- vices 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 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. Disk and port drivers for the CIXCD, CIPCA, KGPSA, KZPBA, and KZPEA ports have been enhanced to take advan- tage of the Fast Path capability. 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) (Alpha Only) The Extended File Cache (XFC) is a new virtual block data cache provided with OpenVMS Alpha Version 7.3. 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: o Read-ahead caching o Automatic resizing of the cache o Larger maximum cache size o No limit on the number of close files that can be cached o Control over the maximum size of I/O that can be cached o Control over whether cache memory is static or dynamic Virtual I/O Cache 50 OpenVMS provides a standalone or clusterwide, file-oriented disk cache. Applications benefit from the advantages of the virtual I/O cache without any special coding. The virtual I/O file-caching algorithm is chosen based on the type of clusterwide access cur- rently in progress. Virtual I/O caching reduces current and po- tential I/O bottlenecks within OpenVMS systems. It reduces the number of I/Os to the disk subsystem, thereby reducing systemwide bottlenecks. 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 and variable-length record formats. RMS also sup- ports byte stream formats for sequential file organization. RMS record access modes provide access to records in four ways: o Sequentially o Directly by key value o Directly by relative record number o 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 applica- ble). RMS offers the options of enabling global buffers for buffer sharing by multiple processes. 51 RMS utilities aid file creation and record maintenance. These utilities convert files from one organization and format to an- other; restructure indexed files for storage and access effi- ciency; and reclaim data structures within indexed files. These utilities also generate appropriate reports. For systems that have DECnet for OpenVMS VAX and Alpha, or DECnet- Plus installed, RMS provides a subset of file and record manage- ment 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 or- ganization 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. 52 The system applies software validity checks and checksums to crit- ical disk structure information. If a disk is improperly dis- mounted because of user error or system failure, the system re- builds the disk's structure information automatically the next time the disk is mounted. The system detects bad blocks and pre- vents their reuse once the files to which the blocks were allo- cated 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 subdirec- tories whose contents are alphabetically ordered. Device and file specifications follow HP 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. 53 OPENVMS ALPHA SUPPORT FOR NEW ALPHASERVER SERIES SYSTEMS AlphaServer DS15 Series Systems OpenVMS Version 7.3-2 provides support for the HP AlphaServer and AlphaStation DS15 series systems. AlphaServer ES47, ES80, and GS1280 Series Systems OpenVMS Version 7.3-1 (with TIMA update kit) provides support for the HP AlphaServer ES47, ES80 and GS1280 series systems. The TIMA update kit ships in factory-installed systems and is also available at the following web site: http:://h71000.www7.hp.com/serv_support.html For the complete list of systems supported, see the section called Alpha Systems Supported in this SPD, and the AlphaServer platform configuration and options web site at: http://h18002.www1.hp.com/alphaserver/ OpenVMS Alpha Version 7.3-1 and higher provides hard partitioning support for the HP AlphaServer ES47, ES80, and GS1280. AlphaServer GS80, GS160, and GS320 Series Systems OpenVMS Alpha Versions 7.2-2 and higher provide support for the HP AlphaServer GS80, GS160 and GS320 series systems. This support includes: o OpenVMS support for hard and soft partitions (Galaxy) on Al- phaServer GS80, GS160, and GS320 series systems o OpenVMS Resource Affinity Domain (RAD) support for applications o OpenVMS Support for CPU Online Replace on AlphaServer GS160 and GS320 series systems (Version 7.3-1 and higher) For more information about using the OpenVMS RAD support for ap- plication features, refer to the OpenVMS Alpha Partitioning and Galaxy Guide. 54 E-BUSINESS AND INTEGRATION TECHNOLOGIES The HP OpenVMS e-Business Infrastructure Package provides key Internet and e-Business software technology that enhances the OpenVMS Alpha operating system. These technologies are licensed as part of the OpenVMS Alpha Operating System and are provided on the OpenVMS e-Business Infrastructure CD-ROM (order number QA-6LYAA-H8). Additional details can be found in the OpenVMS e- Business Infrastructure Package Software Product Description (SPD 80.58.xx). Most of these technologies can also be downloaded from: http://www.hp.com/go/openvms/ebusiness/ Attunity Connect "On Platform" Package Attunity Connect is object-oriented middleware that facilitates the development of applications that access, integrate, and update data from multiple, heterogeneous sources across a wide range of operating system platforms. The Attunity Connect "On Platform" package for OpenVMS provides ODBC, JDBC, and XML client APIs and ODBC, XML, and Oracle8i data adapters for accessing data sources on a single OpenVMS Alpha system. Additional data adapters for OpenVMS Alpha are available directly from Attunity. The full Attunity Connect product provides ODBC, JDBC, XML, ADO, and OLEDB client APIs, adapters for a large number of relational and nonrelational data sources, and support for a large number of popular platforms, including UNIX, Windows, OpenVMS, Tandem, and mainframes. When distributed data access to or from an OpenVMS Alpha system is required in a heterogeneous environment, the full Attunity Connect product is required and must be purchased directly from Attunity for all the platforms of interest, including OpenVMS Alpha. Services for the Attunity Connect "On Platform" Package for Open- VMS Alpha are provided under existing OpenVMS Operating System service agreements. 55 HP BridgeWorks HP BridgeWorks is an automated component-creation tool that ex- poses existing 3GL-based applications and modules as components using the JavaBeans, Enterprise JavaBeans, or COM object models and thus facilitates the development and deployment of distributed applications. HP BridgeWorks can "componentize" or "wrap" applications writ- ten in COBOL, Pascal, BASIC, C, Fortran, Ada, and any other 3GL language that supports the OpenVMS Calling Standard. Such applica- tions must have routines that are externally callable. BridgeWorks can also wrap DCL procedures, ACMS applications, and aggregate datatypes (structure and arrays). BridgeWorks consists of a GUI development tool on the Windows NT or Windows 2000 desktop, a server manager component on OpenVMS, and extensive online help. All the necessary files and code are generated to build the selected application or module into a com- ponent in a three-tier, distributed architecture. Web and desktop clients can then communicate with these new distributed components using industry-standard technologies as if they were the applica- tion that enables the development and deployment of solutions for the widest range of client platforms and the Internet. Software support service for this product is sold separately. COM for OpenVMS Component Object Model (COM) is a technology from Microsoft Cor- poration that allows developers to create distributed network objects. Digital Equipment Corporation and Microsoft jointly de- veloped the COM specification. First released by Microsoft on Windows NT[R] as Network Object Linking and Embedding (NetOLE), and then renamed Distributed COM (DCOM), the COM specification now includes network objects. 56 COM is used to create distributed applications made up of reusable objects. COM locates objects locally or in a network and uses the remote procedure call (RPC) wire protocol to communicate between these objects across the network. COM on OpenVMS delivers connectivity and interoperability between OpenVMS and Windows NT systems. With COM for OpenVMS, programmers write distributed applications that run across systems in a het- erogeneous environment. COM for OpenVMS is based on the Microsoft COM shipped on Windows NT 4.0 SP5 and implements many features of Microsoft COM, including activation, automation, monikers, type libraries, structured storage, and NTLM authentication on OpenVMS. COM for OpenVMS requires OpenVMS Alpha Version 7.2 or higher. The binary kit for COM (both developer kit and run-time) ships with the OpenVMS Alpha distribution kit. COM is not available on VAX. Software Support Service for this product is sold separately. For more information, see the COM for OpenVMS Software Product Description (SPD 70.45.xx). HP OpenVMS Enterprise Directory for e-Business (LDAPv3/X.500) The HP OpenVMS Enterprise Directory for e-Business, based on the X.500 standard, delivers robust and scaleable directory services across intranets, extranets and the Internet to customers, sup- pliers and partners. It combines the best of both the industry standard LDAPv3 and X.500 capabilities. The Lightweight Directory Access Protocol (LDAP) support allows access by a myriad of LDAP clients, user agents and applications. The X.500 support brings very high performance, resilience, advanced access controls and easy replication across the enterprise. Certified with Entrust/PKI 5 and Baltimore UniCERT 3.5.2, at sign- on this directory ensures that all users are authenticated with zero latency and that each can access only to those resources they are authorized to use. 57 OpenVMS Enterprise Directory for e-Business can contain infor- mation about anything of interest, including people, systems, network resources, applications, authentication certificates and databases. Both the established DAP interface and the LDAPv3 in- terface can be accessed simultaneously by disparate applications, thereby delivering full integration with existing environments. The OpenVMS Enterprise Directory for e-Business is available with OpenVMS Alpha Version 7.3 and 7.3-1 and is licensed with the Open- VMS Alpha operating system. It is also available on the OpenVMS Alpha Software Layered Products Library. Software support service for this product is sold separately. For further information, re- fer to the HP OpenVMS Enterprise Directory for e-Business Software Product Description (SPD 40.77.xx) HP Secure Web Server for OpenVMS Alpha HP Secure Web Server for OpenVMS Alpha (SWS) provides a power- ful, flexible web server based on the popular Apache Web Server from the Apache Software Foundation. SWS provides the following features: o HTTP/1.1 compliance (RFC2616) o All standard Apache extensions (modules) o Support for PHP, Perl, Java Servlets, and Java Server Pages (JSP) o Secure Sockets Layer (SSL) support (mod_ssl) using OpenSSL o Digital certificates from VeriSign Inc. To expand and extend the usefulness of SWS, the following optional software components are available for use with SWS: o mod_PHP provides support for PHP, a server-side, cross- platform, and HTML embedded scripting language that facilitates creation of dynamic web pages. PHP-enabled web pages can be created and edited the same as regular HTML pages. 58 o mod_PERL and Perl provide support for Perl, an interpreted high-level programming language that is highly portable across systems. Perl has become the premier scripting language of the Web, and many CGI programs are written in Perl. mod_Perl allows SWS modules to be written entirely in Perl. o mod_JK and Tomcat provide Java run-time support for Java Servlet and JavaServer Pages (JSP) technologies that facili- tate creation of dynamic web pages and Java-based application deployment. Services for HP Secure Web Server for OpenVMS Alpha are provided under existing OpenVMS Operating System service agreements. HP Secure Web Browser for OpenVMS Alpha HP Secure Web Browser for OpenVMS Alpha (SWB) provides a powerful, flexible, and modern web browser based on the Mozilla open-source project started in 1998 by Netscape Communications Corporation. The Mozilla Web Browser is designed for standards compliance, performance, and portability. Mozilla is the code base used for Netscape 7. SWB is the officially supported web browser for OpenVMS Alpha and provides a full featured and customizable browser with integrated web browsing, security, HTML document creation and editing, and clients for mail, news, and instant messaging. SWB includes sup- port for the following features: o Hypertext Markup Language (HTML 4.01) o Cascading Style Sheets (CSS1/2) o Document Object Model (DOM1/ 2) o Extensible Markup Language (XML) o Resource Definition Framework (RDF) o Secure Sockets Layer (SSL) o Java and JavaScript 59 Services for the HP Secure Web Browser for OpenVMS Alpha are pro- vided under existing OpenVMS operating system service agreements. HP Software Development Kit (SDK), for the Java Platform The HP SDK provides an environment in which to develop and de- ploy Java applications on OpenVMS Alpha. Java applications can be written once and run on any operating system that implements the Java run-time environment, which consists primarily of the Java Virtual Machine (JVM). The SDK is a set of building blocks con- taining basic development tools and a rich set of class libraries, including: o Java Compiler o Java Virtual Machine (JVM) o Fast VM for OpenVMS Alpha o Java Class Libraries o Java Applet Viewer o Java Debugger and other tools o A POSIX threads (pthreads) implementation that provides in- creased performance on multiprocessor systems o Flexible options for representing UNIX directory and file spec- ifications on OpenVMS systems The SDK now includes the Fast VM, which is new Just-In-Time (JIT) compiler technology designed to provide optimal Java run-time per- formance on OpenVMS Alpha systems. The Fast VM offers significant performance advantages over the Classic JIT provided with the SDK. Services for the SDK, for the Java Platform are provided under existing OpenVMS operating system service agreements. HP Extensible Markup Language (XML) Technology 60 To give applications the ability to parse, generate, manipulate, validate, and transform the HP Extensible Markup Language (XML) documents and data, the following components are provided using open source software from the Apache Software Foundation: o An XML parser in Java and C++ o An XSLT stylesheet processor in Java and C++ Services for the XML Technology for OpenVMS Alpha are provided under existing OpenVMS operating system service agreements. NetBeans for OpenVMS NetBeans provides an open-source, modular, and integrated develop- ment environment (IDE) for Java and JavaBeans development imple- mented in pure Java. The popularity of NetBeans is a result of its versatility, extensible architecture, and relative ease of use. The key features of NetBeans on OpenVMS include: o Support for Java, C/C++, XML, and HTML o Support for JSP, XML, RMI, CORBA, JINI, JDBC, and servlet tech- nologies o Support for Ant, CVS, CMS, and other version-control systems o Pluggable support for compilers, debuggers, and execution ser- vices o GUI form designer and other visual design tools o Wizards for code generation and management tools o Syntax-highlighting source editor By utilizing NetBeans versatility and extensible architecture, the following plug-ins are available only for OpenVMS and maximize the usefulness of NetBeans for development in an OpenVMS environment. o EDT editor keybindings 61 o C/C++ compiler support HP Reliable Transaction Router HP Reliable Transaction Router (RTR) is object-oriented, fault- tolerant, transactional messaging middleware used to implement highly extensible, distributed applications using client/server technology. Reliable Transaction Router provides a multicomponent software model in which clients running on front ends, routers, and servers running on back ends cooperate to provide reliable service and transactional integrity. Components are managed from an easy-to-use web interface. For example, the RTR client appli- cation could be an ASP (Active Server Page) script or a process interfacing to a web server through a standard interface such as CGI (Common Gateway Interface). Reliable Transaction Router enables computing enterprises to de- ploy distributed applications on OpenVMS Alpha systems. Software support service for this product is sold separately. Refer to the HP Reliable Transaction Router for OpenVMS Software Product Description (SPD 51.04.xx) for additional information. Simple Object Access Protocol (SOAP) Toolkit SOAP provides a simple, lightweight mechanism for exchanging structured and typed information between peers in a decentral- ized, distributed environment. SOAP is an XML-based protocol that consists of three parts: an envelope that defines a framework for describing the contents of a message and how to process it, a set of encoding rules for expressing application-defined datatypes, and a convention for representing remote procedure calls and re- sponses. SOAP defines a simple mechanism for expressing applica- tion semantics that allows SOAP to be used in a wide variety of systems. 62 The SOAP Toolkit is Java based and provides development tools to create SOAP clients or to implement server-side SOAP accessible services that use HTTP as the transport protocol. As a client li- brary, it provides the ability to invoke SOAP RPC services avail- able elsewhere, in addition to features for sending and receiving SOAP messages. As a mechanism to write new RPC or message accessi- ble services, it requires a Java servlet run-time environment such as that provided by CSWS_JAVA. ASSOCIATED PRODUCTS The products in this section are not licensed as part of the Open- VMS Operating System and require a separate license. 63 HP Advanced Server for OpenVMS Alpha HP Advanced Server for OpenVMS is supported on OpenVMS Alpha sys- tems only. Advanced Server V7.3 for OpenVMS is the only version of that product supported on OpenVMS Alpha Versions 7.3, 7.3-1, and 7.3-2. The HP Advanced Server for OpenVMS product evolved from PATHWORKS for OpenVMS (Advanced Server). Advanced Server is an OpenVMS-based network operating system (NOS) compatible with Microsoft networking technology. The software lets you establish OpenVMS systems as servers to provide Windows desktop users (including Windows 2000 and Windows XP Professional users) easy and efficient access to OpenVMS file and print ser- vices. Desktop users can use Microsoft products and utilities such as Windows Explorer to access these resources shared over the net- work. Advanced Server for OpenVMS combines the networking strengths and rich application set of Windows NT with the proven availability, scalability, and security of OpenVMS. The software supports the Windows NT integration features of OpenVMS Alpha Versions 7.3 and 7.3-1 and is compatible with Windows NT and Windows 2000 servers running in the same network. Advanced Server for OpenVMS can function as a file and print server for a small, isolated community of users or as the foun- dation of a large network distributed over a wide geographical area. The Advanced Server software also provides a flexible sys- tem for network administration and security, for both wide area networks (WANs) and local area networks (LANs). HP PATHWORKS for OpenVMS (Advanced Server) HP PATHWORKS for OpenVMS (Advanced Server), also known as PATH- WORKS Advanced Server, runs on OpenVMS Alpha and VAX systems. The only version supported on OpenVMS Alpha or VAX Versions 7.3, 7.3-1, and 7.3-2 is PATHWORKS Version 6.1 for OpenVMS (Advanced Server). PATHWORKS Advanced Server, as with Advanced Server for OpenVMS, is an OpenVMS-based network operating system compati- ble with, and enhancing, the Microsoft networking technology, and 64 providing file and print services for Windows desktop users, in- cluding Windows 2000 and Windows XP Professional. It is compatible with Windows NT servers running in the same network. HP Galaxy Software Architecture on OpenVMS Alpha HP Galaxy Software Architecture on OpenVMS Alpha is available as a separately licensed System Integrated Product (SIP). By running multiple instances of OpenVMS in a single computer or hard partition, an OpenVMS Galaxy computing environment gives you quantum improvements in: o Compatibility-Existing applications run without changes. o Availability-Presents opportunities to upgrade software and expand system capacity without downtime. o Scalability-Offers scaling alternatives that improve perfor- mance of SMP and cluster environments. o Adaptability-Physical resources can be dynamically reassigned to meet changing workload demands. o Cost of ownership-Fewer computer systems reduce system manage- ment requirements, floor space, and more. For more information about OpenVMS Galaxy licensing requirements, refer to the HP Galaxy Software Architecture on OpenVMS Alpha Software Product Description (SPD 70.44.xx). For more information about how to create, manage, and use an Open- VMS Galaxy computing environment, refer to the OpenVMS Alpha Par- titioning and Galaxy Guide. HP OpenVMS Cluster Software HP OpenVMS Cluster software is available for Alpha and VAX sys- tems as a separately licensed System Integrated Product (SIP). It provides a highly integrated OpenVMS computing environment that is distributed over multiple systems containing up to 96 nodes. 65 OpenVMS Cluster systems and storage communicate using a combina- tion of the following interconnects: o Memory Channel o CI o DIGITAL Storage Systems Interconnect (DSSI) o Fiber Distributed Data Interface (FDDI) o Ethernet o Small Computer System Interface (SCSI) o Shared Memory Cluster Interconnect (SMCI) (Galaxy only) o Fibre Channel (Storage Only) Version 7.2-1 and higher In addition, when configured with suitable FDDI bridges, OpenVMS Cluster configurations can use DS3/T3 and asynchronous transfer mode (ATM) networking infrastructures. 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 clus- ter from uncoordinated access to shared data. This coordination ensures data integrity during concurrent update transactions. Ap- plication programs specify the level of OpenVMS Cluster file shar- ing that is required; access is then coordinated by the extended QIO processor (XQP) and Record Management System (RMS). The OpenVMS queue manager controls the OpenVMS Cluster batch and print queues, which can be accessed by any node in the OpenVMS Cluster. Batch jobs submitted to OpenVMS Cluster queues are routed to any available CPU so that the batch load is shared. The Lock Manager provides synchronized services between systems in a cluster, for use by both system components such as RMS and XQP, and also for direct use by applications. 66 Two or more Alpha and VAX computers connected to the same Memory Channel, CI, DSSI, or SCSI interconnect must be configured as members of the same OpenVMS Cluster system. Mixed-architecture and mixed-version clusters that contain both Alpha systems and VAX systems are supported. OpenVMS Cluster systems provide a uniform computing environment that is highly scalable, highly available, and secure. OpenVMS Cluster software implements a single-security environment within a cluster configuration. The security subsystem ensures that all cluster-visible objects maintain consistent security profiles and that system security auditing controls operate clusterwide. Refer to the OpenVMS Cluster Software Software Product Description (SPD 29.78.xx) for more information. HP Volume Shadowing for OpenVMS HP provides HP Volume Shadowing for OpenVMS Alpha and VAX products for performing disk mirroring operations, using a redundant array of independent disks (RAID) 1 storage strategy. Volume Shadowing for OpenVMS is available for Alpha and VAX sys- tems as a separate licensed System Integration Product (SIP). Volume Shadowing for OpenVMS provides high data availability for disk devices by ensuring against data loss that results from me- dia deterioration or controller or device failure. This prevents storage subsystem component failures from interrupting system or application tasks. The system disk and Files-11 On-Disk Structure (ODS-2, ODS-5) data disks can be volume shadowed. Volume Shadowing for OpenVMS supports the clusterwide shadowing of HP Fibre Channel, SCSI, and DSA storage systems. Volume Shadowing for OpenVMS also supports shadowing of all MSCP served DSA disks and Fibre Channel and SCSI disks. All disks in a single shadow set must have the same number of logical blocks. Shadow set mem- bers can be located on a single system or anywhere in an OpenVMS 67 Cluster system. Disks can be configured on any MSCP or HP SCSI- compliant controller. Volume Shadowing for OpenVMS provides fault tolerance resulting from disk media errors or controller errors across the full range of Alpha and VAX processors and configurations. Shadow set member units can be located on different controllers and OpenVMS Alpha and OpenVMS VAX MSCP servers, providing configuration flexibility and a high degree of data availability. Volume Shadowing for OpenVMS supports up to 10,000 single-member shadow sets, and up to 1,000 devices in multiple member (two or three member) shadow sets, on a standalone or OpenVMS Cluster system. The binary kit for Volume Shadowing ships with the OpenVMS Alpha and VAX distribution kits. To run the software, customers must purchase a license. Refer to the HP Volume Shadowing for OpenVMS Software Product Description (SPD 27.29.xx) for more information. HP TCP/IP Services for OpenVMS emphasis>(HP TCP/IP Services for OpenVMS\bold) HP TCP/IP Services for OpenVMS is HP's industry-standard implemen- tation of the TCP/IP and NFS networking protocols on the OpenVMS platform. TCP/IP Services for OpenVMS is integrated with the Open- VMS operating system installation. TCP/IP Services for OpenVMS provides interoperability and resource sharing among systems run- ning OpenVMS, UNIX, Windows NT, and other operating systems that support TCP/IP. TCP/IP provides a comprehensive suite of functions and applications that support industry-standard protocols for het- erogeneous network communications and resource sharing. TCP/IP Services incorporates the TCP/IP protocols stack from the latest version of HP Tru64 UNIX. TCP/IP Service for OpenVMS provides many new enhancements such as Secure Shell (SSH), FailSAFE IP (IP address failover), performance improvements with our new scaleable kernel and Secure POP (SSLfor POP). It also features continued enhancements for IPv6. For more 68 information about the enhancements to TCP/IP Services in this release, refer to the TCP/IP Services for OpenVMS Release Notes. 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 execu- tion, remote printing, mail, application development, Post Office Protocol (POP), SNMP Extensible agent (eSNMP), and Finger Utility. HP DECnet-Plus and HP DECnet Software HP DECnet for OpenVMS VAX and Alpha software is a System Inte- grated Product (SIP) that is licensed separately from the OpenVMS operating system. Refer to the DECnet for OpenVMS VAX and Alpha Software Product Description (SPD 48.48.xx) for further informa- tion about supported communications devices and software features. HP DECnet-Plus (formerly DECnet/OSI) is licensed separately from the OpenVMS operating system. The license for DECnet for OpenVMS VAX and Alpha 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. Refer to the DECnet-Plus for OpenVMS Alpha Software Product Description (SPD 50.45.xx) and the DECnet-Plus for Open- VMS VAX Software Product Description (SPD 25.03.xx)) for further information about supported hardware configurations and software features. HP RMS Journaling for OpenVMS HP provides the HP RMS Journaling for OpenVMS Alpha and VAX prod- ucts as separately licensed SIPs that enable 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: o 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, 69 or corrupted. RMS Journaling recovers the file by applying the journaled modifications to a backup copy, thereby restoring its final state. Application modifications are not necessary to use after-image journaling. o 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. This is useful if a file is updated with incorrect or bad data. Ap- plication modifications are not necessary to use before-image journaling. o Recovery-unit journaling. Allows users to maintain transaction integrity. A transaction can be defined as a series of file up- dates 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. This allows com- plex transactions to be completed as an atomic event-partially completed transactions can be avoided. Recovery-unit journaling requires application modification. The binary kit for RMS Journaling ships with the OpenVMS Alpha and VAX distribution kits. To run the software, customers must purchase a license and documentation. Refer to the RMS Journaling for OpenVMS Software Product Description (SPD 27.58.xx) for more information. HP DECram for OpenVMS HP 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. 70 Because main memory is allocated for the DECram device, extra memory is generally required. The OpenVMS system manager can des- ignate the amount of memory dedicated to the DECram devices and the files that will be stored on it. In DECram for OpenVMS Version 3.0, DECram's capability is extended to use OpenVMS Galaxy shared memory to create an OpenVMS shared memory disk. This allows customers to take advantage of OpenVMS Galaxy shared memory with no modifications to any of their appli- cations. DECram for OpenVMS Version 3.0 is supported on OpenVMS Alpha Ver- sion 7.2-1H1 or higher. DECram for OpenVMS Version 2.3 will con- tinue to be available and supported on OpenVMS Alpha Versions 7.1, 7.2, and 7.3, and on OpenVMS VAX Version 6.2 or higher. DECram Version 3.0 cannot run on an OpenVMS VAX system; however, the RAMdisk can be accessed by OpenVMS VAX systems in an OpenVMS Cluster system. Refer to the DECram for OpenVMS Software Product Description (SPD 34.26.xx) for more information. 71 HP DECwindows Motif for OpenVMS HP offers a separately licensed layered product called HP DECwin- dows Motif for OpenVMS. 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 envi- ronment. DECwindows Motif displays the OSF/Motif user interface. Because both Motif and XUI are based on X.org X Window System, ap- plications written on either toolkit will run regardless of which environment the user selects. Refer to the HP DECwindows Motif for OpenVMS Software Product Description (SPD 42.19.xx) for more information. Note: Licenses for DECwindows Motif for OpenVMS sold after June 30, 2002 no longer include rights to use Adobe[R] Dis- play PostScript[R] and do not permit the use of Adobe[R] Display PostScript[R] on prior versions of DECwindows Motif for OpenVMS. DECwindows Motif Version 1.2-5 for OpenVMS Alpha and higher de- liver the New Desktop environment for OpenVMS Alpha systems, which is derived from the Common Desktop Environment (CDE) technology. CDE provides and defines a consistent user interface for end users and a consistent development environment for application develop- ers across multiple platforms. The OpenVMS software installation procedure contains an optional step to install the DECwindows Motif for OpenVMS workstation and font support, which is required to run DECwindows Motif for Open- VMS. Refer to the OpenVMS Alpha Version 7.3 Upgrade and Instal- lation Manual or OpenVMS VAX Version 7.3 Upgrade and Installation Manual for details concerning the optional installation of the DECwindows Motif for OpenVMS device support. CONFORMANCE TO STANDARDS OpenVMS is based on the following public, national, and interna- tional standards. Distributed Computing Environment (DCE) Support 72 The DCE for the OpenVMS product family provides a set of the dis- tributed 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 com- puting 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 applica- tions. 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: o DCE Run-time Services for OpenVMS, which is required for all systems participating in the DCE cell. The DCE Run-time Ser- vices include DCE client functions as well as DCE administra- tion tools. DCE Run-time Services allow client/server applica- tions to interoperate over DECnet, TCP/IP, and UDP/IP network protocols. o DCE Application Developers' Kit for OpenVMS, which is required for developers of distributed applications but is optional for other users. The DCE Application Developers' Kit provides programmers with an Interface Definition Language (IDL), an easy-to-use, ANSI C-based language for writing remote procedure calls. o DCE Cell Directory Service (CDS), one of which is required for each DCE cell. The DCE CDS is a central repository that con- tains information about the location of resources in the DCE cell. It allows access to resources by a single name, regard- less of their physical location. 73 o DCE Security Server, one of which is required for each DCE. The DCE Security Server protects resources from illegal access and provides secure communications within and between DCE cells. 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. Refer to the Distributed Computing Environment (DCE) for OpenVMS Software Product Descrip- tion (SPD 43.05.xx) for more detailed information. 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. Standards Supported by OpenVMS The OpenVMS operating system is based on the following public, na- tional, 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. o ANSI X3.4-1986: American Standard Code for Information Interchange o ANSI X3.22-1973: Recorded Magnetic Tape (800 BPI, NRZI) o ANSI X3.27-1987: File Structure and Labeling of Magnetic Tapes for Information Interchange o ANSI X3.298: Limited support. Information Technology-AT Attachment-3 Interface (ATA-3) 74 o ANSI X3.39-1986: Recorded Magnetic Tape (1600 BPI, PE) o ANSI X3.40-1983: Unrecorded Magnetic Tape o ANSI X3.41-1974: Code Extension Techniques for Use with 7-bit ASCII o ANSI X3.42-1975: Representation of Numeric Values in Character Strings o ANSI X3.54-1986: Recorded Magnetic Tape (6250 BPI, GCR) o ANSI X3.131-1986 (SCSI I): Small Computer System Interface o ANSI X3.131-1994 (SCSI II): Small Computer System Interface o ANSI/IEEE 802.2-1985: Logical Link Control o ANSI/IEEE 802.3-1985: Carrier Sense Multiple Access with Collision Detection o 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. o FIPS 3-1/ANSI X3.22-1973: Recorded Magnetic Tape Information Interchange (800 CPI, NRZI) o FIPS 16-1/ANSI X3.15-1976: Bit Sequencing of the Code for In- formation Interchange in Serial-by-Bit Data Transmission Note: FED STD 1010 adopts FIPS 16-1. o 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. 75 o FIPS 25/ANSI X3.39-1986: Recorded Magnetic Tape for Information Interchange (1600 CPI, Phase Encoded) o 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. o FIPS 50/ANSI X3.54-1986: Recorded Magnetic Tape for Information Interchange, 6250 CPI (246 CPMM), Group Coded Recording o FIPS 79/ANSI X3.27-1987: Magnetic Tape Labels and File Struc- ture for Information Interchange o FIPS 86/ANSI X3.64-1979: Additional Controls for Use with Amer- ican 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. o ISO 646: ISO 7-bit Coded Character Set for Information Exchange o ISO 1001: File Structure and Labeling of Magnetic Tapes for Information Interchange o ISO 1863: Information Processing - 9-track, 12, 7 mm (0.5 in) wide magnetic tape for information interchange recorded at 32 rpmm (800 rpi) o 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 o ISO 2022: Code Extension Techniques for Use with ISO 646 o ISO 3307: Representations of Time of the Day 76 o 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 o ISO 4873: 8-Bit Code for Information Interchange - Structure and Rules for Implementation o ISO 5652: Recorded Magtape (6250) o ISO 6429: Control Functions for Coded Character Sets o ISO 9316: 1989 (SCSI-1) Small Computer System Interface o ISO 9660: Information Processing - Volume and file structure of CD-ROM for information exchange o ISO 10288: 1994 (SCSI-2) Small Computer System Interface INSTALLATION OpenVMS Alpha and OpenVMS VAX are distributed as a binary kit on CD-ROM. Procedures for setting up the system disk from media and for preparing the system for day-to-day operations are provided. The procedures use the POLYCENTER Software Installation utility to configure and install the OpenVMS Alpha operating system. These procedures are described in the HP OpenVMS Alpha Version 7.3-2 Upgrade and Installation Manual and the OpenVMS VAX Version 7.3 Ugrade and Installation Manual. Computer-specific information is contained in the upgrade and installation supplements for each family of VAX computers. OpenVMS VAX is distributed as binary kits on CD-ROM and tape. OpenVMS VAX Version 7.3 is the last OpenVMS release for which TK50 and magnetic tape media will be distributed. Future OpenVMS VAX releases will be distributed on CD-ROM only. Procedures for set- ting up the system disk from a kit and for preparing the system for day-to-day operations are provided. The procedures are de- scribed in the OpenVMS VAX Version 7.3 Upgrade and Installation Manual. Computer-specific information is contained in the upgrade and installation supplements for each family of VAX computers. 77 POLYCENTER Software Installation The POLYCENTER Software Installation utility simplifies the in- stallation and management of OpenVMS products. It is used to install, configure, reconfigure, and deinstall software prod- ucts that have been prepared with the utility. In addition, the POLYCENTER utility provides a database to track the installation, reconfiguration, and deinstallation of software. For products installed with other installation technologies, the POLYCENTER utility provides a mechanism for adding information about them into the product database. The POLYCENTER utility also provides the ability to manage dependencies between products during the installation process. For software providers, the POLYCENTER Software Installation util- ity simplifies the task of packaging software by providing a sim- ple, declarative language for describing material for the in- stallation kit and defining how it is installed. The POLYCENTER 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 directo- ries), and anticipate and resolve conflict before it occurs. The POLYCENTER utility also significantly simplifies the packaging of multiple software products into one logical product suite. For OpenVMS Alpha, you use the POLYCENTER Software Installation utility to install the operating system and to install layered products that are compliant with the POLYCENTER utility. For OpenVMS VAX, you use the POLYCENTER Software Installation utility to install layered products that are compliant with the POLYCENTER utility. VMSINSTAL 78 OpenVMS includes the VMSINSTAL facility to handle the installa- tion of optional HP supplied software products that have not been converted to use the POLYCENTER Software Installation utility. OpenVMS VAX also includes the VMSINSTAL facility to automate oper- ating system software updates. 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 Alpha DISK SPACE REQUIREMENTS Operating System Disk Space Requirements The disk space requirements for OpenVMS Alpha vary according to which options are installed: 79 ____________________Space__________________________________________ File_Category_______Used______Running_Total________________________ Minimum OpenVMS 381 381 MB files MB Optional OpenVMS 241 622 MB files MB DECwindows 142 764 MB Support MB Paging file 38 MB 802 MB (required) Swap file (sug- 1 MB 803 MB gested) Dump file (op- 28 MB 831 MB tional) Decompressed 10 MB 841 MB Help files (optional) Full DECwindows 180 1021 MB Motif (optional) MB Safeguard for 50 MB 1071 MB upgrading__________________________________________________________ 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 HP 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 in- stallation. For most applications, this is not a realistic OpenVMS environment. 80 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 dupli- cated on the system disk or located on some other disk. DECwindows Motif for OpenVMS Alpha Disk Space Requirements To support OpenVMS Alpha and DECwindows Motif for OpenVMS Alpha, HP recommends a system disk of greater than 550 MB. However, you can install a subset of DECwindows Motif. The disk space required for the installation of DECwindows Motif is 159 MB. The permanent amount of space used is 145 MB. An additional 33 MB is needed to install the DECwindows X11 Display Server and associated files. (The DECwindows X11 Display Server and associated files are in- cluded in the OpenVMS Alpha operating system media.) These disk space requirements are in addition to the disk space required for the OpenVMS Alpha operating system, as indicated in the OpenVMS Alpha Disk Space Requirements table. Installation of the DECwindows Motif layered product gives cus- tomers the option of installing any or all of the following compo- nents: o Run-time support base kit - 33 MB. This section provides sup- port for running DECwindows Motif for OpenVMS Alpha applica- tions on Alpha compute servers and is a required part of the installation. o New Desktop - 24 MB. This is an optional component that allows use of the New Desktop environment. It includes applications and application programming interfaces (APIs). 81 o DECwindows desktop - 11 MB. This component is also optional, but you should install either the New Desktop or the DECwindows desktop to create a usable system. 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. o Programming support - 32 MB. This section includes support for the C, C++, Fortran, and Pascal programming languages. If you install a subset of languages, the amount of disk space required will be less. o Example files - approximately 26 MB. o Translated image support - approximately 20 MB. Layered Product Disk Space Requirements In addition to the disk space used directly by HP or third-party layered products, there may be additional space used to store in- formation 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 pos- sibility of recovering unused space already existing in those li- brary files. Unusually large modules contributed by layered prod- ucts can also affect the amount of space required for upgrading to a new version of the OpenVMS Alpha operating system. OpenVMS VAX DISK SPACE REQUIREMENTS Disk Space Requirements (Block Cluster Size = 3) To support the complete OpenVMS VAX system, HP recommends a system disk of greater than 150 MB. When you use a smaller disk, addi- tional tailoring is required before installing some of the OpenVMS VAX options. This does not include the dump file space. Refer to the OpenVMS VAX Version 7.3 Upgrade and Installation Manual for information on tailoring. Operating System Disk Space Requirements 82 The disk space requirements for OpenVMS VAX vary according to which options are installed. ___________________________________________________________________ Space File_Category_______Used______Running_Total________________________ Minimum OpenVMS 32.0 32.0 MB files MB Optional OpenVMS 52.0 84.0 MB files MB DECwindows 14.0 98.0 MB Support MB Paging file 6.0 104.0 MB (after installa- MB tion) Swap file (sug- 1.2 105.2 MB gested) MB Dump file (op- 6.2 111.4 MB tional) MB Decompressed 7.0 118.4 MB Help files MB (optional) Safeguard for 25.0 143.4 MB upgrading MB Variable ad- 3.3 146.7 MB ditional space MB (additional files, IN- DEXF.SYS,_etc.)____________________________________________________ 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 HP and other layered products will work in this minimum configuration. 83 The data in the table was created from an installation on a VAXserver 2000 with 6 MB of memory and an RD54 disk. Additional memory adds to the space required for page, swap, and dump files, and the variable additional space increases with larger memory and disk. DECwindows Motif for OpenVMS VAX Disk Space Requirements To support OpenVMS VAX and the DECwindows Motif for OpenVMS VAX layered product, HP recommends a system disk of greater than 300 MB. The disk space required for the installation of DECwindows Motif is 60 MB. The permanent amount of space used is 54 MB. An additional 16 MB are needed to install the DECwindows X11 Display Server and associated files. (The DECwindows X11 Display Server and associated files are included in the OpenVMS VAX Version 7.3 media.) These disk space requirements are in addition to the disk space required for the OpenVMS VAX Version 7.3 operating system, as indicated in the OpenVMS VAX Disk Space Requirements table. Installation of the DECwindows Motif layered product gives cus- tomers the option of installing any or all of the following compo- nents: o Run-time support files base kit - 41 MB. This section provides support for running DECwindows Motif for OpenVMS VAX appli- cations on VAX compute servers and is a required part of the installation. It includes the DECwindows desktop applications and libraries. o Programming support - 7 MB. This section includes support for the C, C++, Fortran, Pascal, and VAX C programming languages. If a subset of languages is installed, the amount of disk space required is less. o Example files - approximately 7 MB. Note that the individual sizes add up to more than the total be- cause some components are shared by multiple portions of the envi- ronment. 84 MEMORY SPACE REQUIREMENTS OpenVMS Alpha Memory Space Requirements The minimum amount of memory required to install, boot, and log in to an OpenVMS Alpha system is 64 MB. Additional memory may be required to ensure satisfactory performance for either of the following: o Particular applications or number of users o Particular hardware configurations Refer to specific layered product documentation for their memory requirements. OpenVMS VAX Memory Space Requirements The minimum amount of memory required to install, boot, and log in to an OpenVMS VAX system is 14 MB. To ensure satisfactory perfor- mance for particular applications or number of users, additional memory may be required. Refer to specific layered product documen- tation for their memory requirements. DISTRIBUTION AND BACKUP MEDIA OpenVMS Alpha OpenVMS Alpha is available on CD-ROM only. The OpenVMS Alpha Ver- sion 7.3-2 binary CD-ROM contains the operating system binaries and selected documentation in text and PostScript formats. The OpenVMS Version 7.3-2 Documentation CD-ROMs contain all OpenVMS manuals in HTML and PDF formats. Associated product manuals are in HTML and selected product and archived manuals are in PDF format. Two separate versions of the Documentation CD-ROM are provided: one is a Files-11 formatted CD-ROM; the other is an ISO 9660 formatted CD-ROM. The contents of the two CD-ROMs are virtually identical, though each CD-ROM contains tools for viewing online documents on its target platform. For more information about these 85 CD-ROMs and their contents, see the Guide to OpenVMS Alpha Version 7.3-2 CD-ROMs. The OpenVMS Alpha operating system is also available as part of the OpenVMS Alpha Software Products Library CD-ROM offering. OpenVMS VAX OpenVMS VAX is available on CD-ROM, TK50, or 9-track 6250 BPI magnetic tape media. The 9-track 6250 BPI magnetic tape media is available only through the OpenVMS VAX media and hardcopy doc- umentation update service. OpenVMS VAX Version 7.3 is the last OpenVMS Release for which TK50 and magnetic tape media will be distributed. The OpenVMS VAX Version 7.3 Binary CD-ROM contains the OpenVMS VAX Version 7.3 save sets, OpenVMS VAX Version 7.3 standalone BACKUP, and selected OpenVMS documentation n text and PostScript formats. The OpenVMS Version 7.3 Documentation CD-ROM contains all OpenVMS manuals in HTML and PDF formats. Associated product manuals are in HTML and selected product and archived manuals are in PDF format. The OpenVMS Documentation CD-ROM is an ISO 9660 formatted CD-ROM that can be mounted and read on OpenVMS systems, Windows systems, and Macintosh systems. The TK50 streaming tape contains the OpenVMS VAX Version 7.3 save sets and OpenVMS VAX Version 7.3 standalone BACKUP. The 9-track 6250 BPI magnetic tape contains the OpenVMS VAX Ver- sion 7.3 save sets. The OpenVMS VAX operating system is also available as part of the OpenVMS VAX Software Products Library CD-ROM offering. 86 DOCUMENTATION For OpenVMS Version 7.3-2, documentation is available in the fol- lowing formats: Printed Books OpenVMS printed documentation is available in two sets: the Open- VMS Full Documentation Set and the OpenVMS Base Documentation Set. The Full Documentation Set is for users who need extensive ex- planatory 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, ad- dressing the needs of general users and system managers of small, standalone systems. Manuals such as the Release Notes, New Fea- tures, and the DCL Dictionary are included in the Base Set. Online Books For OpenVMS Version 7.3-2 online documentation is provided on two CD-ROMs to meet the needs of users on multiple formats. One CD- ROM is Files-11 formatted for use on OpenVMS systems; the second is ISO 9660 formatted for users of Windows and Macintosh systems. The contents of the two CD-ROMs is virtually identical, with the exception of tools supplied for viewing files on the media. The Files-11 CD-ROM includes the Secure Web Browser (based on Mozilla) and a command procedure to launch the browser and view the docu- mentation. The ISO 9660 CD-ROM includes the Adobe Acrobat Reader Version 5.0 for users who want to read PDF files on that CD-ROM. The OpenVMS Version 7.3-2 Online Documentation CD-ROMs contain all OpenVMS manuals in HTML and PDF formats. Associated product manu- als are also available in HTML and selected product and archived manuals are available in PDF format. 87 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. SOURCE LISTINGS OpenVMS Alpha and VAX Operating System Source Listings are avail- able on CD-ROM. These discs contain source listing files and the Alpha specific debug symbol files that make up the OpenVMS oper- ating system. HP provides source listings for key modules of the OpenVMS operating system that are appropriate for end users or application developers. The debug symbol files (DSF) on the Open- VMS Alpha Source Listings CD-ROM contain information used by the OpenVMS Alpha System-Code Debugger. Certain company confidential source listings and debug symbol files, however, are excluded from the CD-ROM. The orderable CD-ROM kit includes the license required to view these files on a standalone system or an OpenVMS Cluster system. If users want to make these files available to another system (possibly at a remote site), they must purchase another kit. 88 ORDERING INFORMATION Alpha Software Licenses QL-MT1A*-6* OpenVMS Alpha Operating System Base License QL-MT1A*-7* OpenVMS Alpha Operating System Base Update License QL-MT1A9-6* OpenVMS Alpha Operating System Symmetric Multipro- cessing (SMP) Base Extension License QL-MT1A9-7* OpenVMS Alpha Operating System Symmetric Multipro- cessing (SMP) Base Extension Update License QL-MT2A9-** OpenVMS Alpha Individual User License (No Longer Available...order the Concurrent Use License or Unlimited User License) QL-MT2A*-AA OpenVMS Alpha Unlimited User License QL-MT2A*-Y* OpenVMS Alpha Individual User Update License QL-MT3A*-B* OpenVMS Alpha Distributed Interactive User License (No Longer Available...order the Concurrent Use License) QL-MT3A*-Y* OpenVMS Alpha Distributed Interactive User Update License QL-MT3A*-3* OpenVMS Concurrent Use License QL-MT3A*-5* OpenVMS Concurrent Use Update License VAX Software Licenses QL-001A*-** VAX VMS Operating System License and Update Li- cense for OpenVMS QL-005A*-6* OpenVMS VAX Operating System Base License QL-005A*-7* OpenVMS VAX Operating System Base Update License QL-005A9-6* OpenVMS VAX Operating System Symmetric Multipro- cessing (SMP) Base Extension License QL-005A9-7* OpenVMS VAX Operating System Symmetric Multipro- cessing (SMP) Base Extension Update License 89 QL-XULA9-** OpenVMS VAX Individual User License (No Longer Available...order the Concurrent Use License or Unlimited User License) QL-XULA*-AA OpenVMS VAX Unlimited User License QL-XULA*-Y* OpenVMS VAX Interactive User Update License QL-09SA*-** OpenVMS VAX Distributed Interactive User License (No Longer Available...order the Concurrent Use License) QL-09SA*-Y* OpenVMS VAX Distributed Interactive User Update License QL-MT3A*-3* OpenVMS Concurrent Use License QL-MT3A*-5* OpenVMS Concurrent Use Update License Alpha and VAX CD-ROM Media and Online Documentation QA-MT1AA-H8 OpenVMS Alpha software and online documentation CD-ROM QA-MT1AG-H8 OpenVMS Alpha Version 6.2-1H3 software and on- line documentation CD-ROM. This includes Version 6.2-1H1 and Version 6.2-1H2. (QA-MT1AA-H8.6.2 is required) QA-MT1AT-H8 OpenVMS Alpha Version 7.2-1 software and online documentation CD-ROM QA-MT1AU-H8 OpenVMS Alpha Version 7.2-2 software and online documentation CD-ROM QA-XULAA-H8 OpenVMS VAX software and online documentation CD-ROM QA-MT3AA-H8 OpenVMS VAX/Alpha software and online documenta- tion CD-ROM QA-MT3AE-G8 OpenVMS VAX/Alpha online documentation CD-ROM 90 VAX Media and Hardcopy Documentation QA-09SAA-H8 OpenVMS VAX Software CD-ROM and Base Documentation Set QA-09SAA-H5 OpenVMS VAX Software TK50 and Base Documentation Set QA-001AA-H8 OpenVMS VAX Software CD-ROM and Full Documentation Set QA-001AA-H5 OpenVMS VAX Software TK50 and Full Documentation Set Hardcopy Documentation Sets QA-09SAA-GZ OpenVMS Base Documentation Set QA-001AA-GZ OpenVMS Full Documentation Set Source Listings Kits QB-MT1AB-E8 OpenVMS Alpha Listings CD-ROM Kit and License QB-001AB-E8 OpenVMS VAX Listings CD-ROM Kit and License OpenVMS Alpha Software Products Library CD-ROM Offerings QA-5FX8A-A8 OpenVMS Alpha Software Layered Products and Op- erating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QA-4KM8A-G8 OpenVMS Alpha Online Documentation Library QA-5G98A-H8 OpenVMS Alpha Software Layered Products and Op- erating System Library Package (Software Layered Product binaries and online documentation, com- plete Operating System kit) QA-03XAA-H8 OpenVMS Alpha Software Library Package (Software Layered Product binaries and online documentation) 91 OpenVMS VAX Software Products Library CD-ROM Offerings QA-VWJ8A-H8 OpenVMS VAX Software Layered Products and Oper- ating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QA-VYR8A-G8 OpenVMS VAX Online Documentation Library QA-YL48A-H8 OpenVMS VAX Software Layered Products and Operat- ing System Library Package (Software Layered Prod- uct binaries and online documentation, complete Operating System kit) QA-5G88A-H8 OpenVMS VAX Software Library Package (Software Layered Product binaries and online documentation) Software Update Distribution Services Provides an automatic distribution of software media and documen- tation update. Choices include: o Media and Documentation Distribution o Documentation Distribution o Consolidated Software Engineering Change Order Distribution o Consolidated Distribution of Software Binaries o Consolidated Distribution with Software Binaries and Documenta- tion o Consolidated Online Documentation For additional ordering and pricing information, contact your local HP account representative. CD-ROM Media and Online Documentation Update Service 92 QT-MT1AA-E8 OpenVMS Alpha software and online documentation CD-ROM QT-XULAA-E8 OpenVMS VAX software and online documentation CD-ROM QT-MT3AA-E8 OpenVMS VAX and Alpha software and online documen- tation CD-ROM Hardcopy Documentation Only Update Service QT-09SAA-KZ OpenVMS Base Documentation Set QT-001AA-KZ OpenVMS Full Documentation Set OpenVMS VAX Media and Hardcopy Documentation Update Service QT-09SA*-E* With Base Documentation Set QT-001A*-E* With Full Documentation Set OpenVMS Source Listings Service QT-MT1AB-Q8 OpenVMS Alpha Source Listings Service QT-001AB-Q8 OpenVMS VAX Source Listings Service * Denotes variant fields. For additional information on available licenses, services, and media, refer to the appropriate HP price book. OpenVMS Alpha Software Products Library CD-ROM Service QT-5FX8A-C8 OpenVMS Alpha Software Layered Products and Op- erating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QT-4KM8A-C8 OpenVMS Alpha Online Documentation Library QT-5G98A-C8 OpenVMS Alpha Software Layered Products and Op- erating System Library Package (Software Layered Product binaries and online documentation, com- plete Operating System kit) QT-03XAA-C8 OpenVMS Alpha Software Library Package (Software Layered Product binaries and online documentation) 93 OpenVMS VAX Software Products Library CD-ROM Service QT-VWJ8A-C8 OpenVMS VAX Software Layered Products and Oper- ating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QT-VYR8A-C8 OpenVMS VAX Online Documentation Library QT-YL48A-C8 OpenVMS VAX Software Layered Products and Operat- ing System Library Package (Software Layered Prod- uct binaries and online documentation, complete Operating System kit) QT-5G88A-C8 OpenVMS VAX Software Library Package (Software Layered Product binaries and online documentation) SOFTWARE LICENSING The OpenVMS operating system software is furnished under the li- censing provisions of HP's Standard Terms and Conditions. Software License Information (Alpha Only) The OpenVMS Alpha operating system license includes the right to use OpenVMS Alpha licenses for multiple instances of OpenVMS on the first and then once again on each subsequent hard partition of a single AlphaServer ES80 or GS80/160/320/1280 system. The OpenVMS Alpha operating system license includes the right to use DECprint Supervisor (DCPS) for OpenVMS products (-Base, -Open, and -Plus). The HP DECprint Supervisor (DCPS) for OpenVMS has separate documentation, media kit, and service products. Refer to the DECprint Supervisor for OpenVMS Software Product Description (SPD 44.15.xx) for more information. The right to use the DCE Run-time Services is included with the OpenVMS base operating system license. Refer to the Distributed Computing Environment (DCE) Software Product Description) (SPD 43.05.xx) for more detailed information about the DCE for OpenVMS product family. 94 The right to use Capacity On Demand for OpenVMS is included with the OpenVMS Base Operating System license. 95 The following technologies are licensed as part of the OpenVMS Alpha operating system: 96 97 ___________________________________________________________________ Attunity Con- SPD 80.58.xx nect "On Plat- form" Package for OpenVMS Alpha COM for OpenVMS SPD 70.45.xx Alpha BridgeWorks SPD 80.58.xx Software Develop- SPD 80.58.xx ment Kit (SDK) for OpenVMS Alpha, for the Java Platform Secure Web Browser SPD 80.58.xx for OpenVMS Alpha Secure Web Server SPD 80.58.xx for OpenVMS Alpha ECP Data Collector SPD 80.88.00 for OpenVMS ECP Performance SPD 80.89.00 Analyzer for OpenVMS Extensible Markup SPD 80.58.xx Language (XML) Technology NetBeans for SPD 80.58.xx OpenVMS Alpha OpenVMS Enter- SPD 40.77.xx prise Directory for e-Business (LDAPv3/X.500) Reliable Transac- SPD 51.04.xx tion Router (Alpha and VAX) SOAP Toolkit for SPD 80.58.xx OpenVMS_Alpha______________________________________________________ 98 The following are separately licensed products: ___________________________________________________________________ Product_Name__________Related_Software_Product_Description_(SPD)___ Advanced Server SPD 30.50.xx for OpenVMS DECnet-Plus for SPD 25.03.xx OpenVMS VAX DECnet-Plus for SPD 50.45.xx OpenVMS Alpha DECnet for OpenVMS SPD 48.48.xx VAX and Alpha DECram for OpenVMS SPD 34.26.xx DECwindows Motif SPD 42.19.xx for OpenVMS Galaxy Software SPD 70.44.xx Architecture on OpenVMS Alpha PATHWORKS for SPD 30.50.xx OpenVMS (Advanced Server) OpenVMS Cluster SPD 29.78.xx Software RMS Journaling for SPD 27.58.xx OpenVMS TCP/IP Services SPD 46.46.xx for OpenVMS Volume Shadowing SPD 27.29.xx for_OpenVMS________________________________________________________ Software License Information (VAX Only) The OpenVMS VAX operating system uses one of two different cate- gories of licenses depending on the hardware and software config- urations used and currently supported. This information is also provided in the applicable country's Price List. 99 These are the two categories of operating system licenses for OpenVMS VAX: o VAX VMS Licensing o OpenVMS VAX Licensing System Support Services HP provides the proper license type with the purchase of the sys- tem. Not all license types are available for every system model. VAX VMS License Information Note: Effective February 6, 1995, the VAX VMS (UPI001) licenses no longer include the rights for the Oracle[R] Rdb Run-Time Option for OpenVMS VAX, and do not permit use of Rdb Run-Time on prior versions of OpenVMS VAX. Each of the following licenses are for a specified hardware sys- tem, which is either the system the license was originally shipped with or the system on which the license was first used: o Operating System Base License (QL-001**-**) o Operating System User License for OpenVMS VAX (QL-001**-**) o Traditional License for OpenVMS VAX (QL-001**-**) There are four types of VAX VMS licenses: All use the LMF Product Name of VAX-VMS. 1. Traditional License (QL-001A*-**) This type of license provides unlimited use to the users on a defined system. VAX VMS traditional licenses are sized to capacity according to system type. 2. Multi-User License (QL-001A*-**) 100 This type of license provides use according to a specified num- ber of concurrent users. This is an activity-based license. The Multi-User License provides the customer with the right to use the operating system up to the limit of users specified in the li- cense. An operating system user is a person who is logged in to the system and is using the system interactively. This license is only available on limited system models, primarily MicroVAX and VAX 4000 systems. The customer can increase interactive use of VAX systems licensed with the Multi-User License by the addition of OpenVMS User Li- censes* (for one or more users). Refer to the section on Ordering Information for further information. 3. VAX VMS Workstation License (QL-001A*-**) This type of license provides use for a single user on a VAX work- station. This license type allows one direct login for the single user and one additional login for system management purposes only. Additional interactive use of VAX workstations licensed with the VAX VMS Workstation License requires the addition of an OpenVMS User License* (for one or more users). Refer to the section on Ordering Information for further information. 4. File and Application Server License (QL-001A*-**) This type of license provides for the noninteractive use of Open- VMS. OpenVMS VAXserver systems are sold with a File and Application Server License. The intent of an OpenVMS VAXserver is to provide file, print, application, and compute services to clients who have submitted their requests remotely (for example via network/remote submit/batch jobs, and so forth). This license type also allows one direct login for system management purposes only. Additional interactive use of OpenVMS VAXserver systems licensed with the File and Application Server License requires the addition of an OpenVMS User License (for one or more users). Refer to the section on Ordering Information for further information. 101 These licenses grant the right to use the same version of the operating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. Notes: Not all VAX VMS license types are available for all versions of VMS, OpenVMS, or all VAX models. The OpenVMS VAX Individual Use Licenses are not supported by the VMS or OpenVMS VAX operating system releases prior to Version 5.5. OpenVMS VAX License Information There are five types of OpenVMS VAX licenses: 1. OpenVMS VAX Operating System Base License (QL-005A*-**) LMF Product Name: BASE-VMS-250136 OpenVMS VAX Operating System Base License grants the right to unrestricted, noninteractive use of the OpenVMS VAX operating sys- tem for the execution of remotely submitted requests for batch, print, application, and computing services, on a designated, sin- gle processor. This license authorizes one direct login for system management purposes only. The OpenVMS VAX Base License does not include the license right for the Oracle Rdb Run-Time Option for OpenVMS VAX. The Operating System Base License is a prerequisite for all Inter- active User Licenses and all SMP Base Extension Licenses. Interactive use of systems licensed with an OpenVMS VAX Operat- ing System Base License requires the addition of an OpenVMS User License (for one or more users). Refer to the section on Ordering Information for further information. This license grants the right to use the same version of the op- erating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. 102 The OpenVMS VAX Operating System Base License also includes the license for DECprint Supervisor for OpenVMS VAX. The DECprint Supervisor for OpenVMS VAX has separate documentation, media kits, and service products. Refer to SPD 44.15.xx for further details. 2. Symmetric Multiprocessing (SMP) Base Extension License (QL-005A9-6*) LMF Product Name: BASE-VMS-250136 SMP Base Extensions extend the Operating System Base License to enable symmetric multiprocessing capability on a select number of OpenVMS VAX systems supporting SMP. SMP Base Extensions are permanently tied to the Operating System Base License and cannot be separated from the Operating System Base License if an SMP board is removed from the system. SMP Extensions grant the right to use the same version of the operating system software as permitted for the corresponding Op- erating System Base License at the time when the SMP Extension is granted. 3. OpenVMS VAX Individual User License (QL-XULA*-**) LMF Product Name: VMS-USER The OpenVMS VAX Individual User License provides the right to interactively use the operating system by the specified or un- limited number of concurrent users on a designated, single processor. A user is an individual who is logged in to a pro- cessor and is interactively using the operating system soft- ware by means other than a login. An OpenVMS VAX Operating Sys- tem Base License or one of the five types of VAX VMS Licenses (QL-001A*-**) is a prerequisite for the OpenVMS User License. This license grants the right to use the same version of the op- erating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. 103 The OpenVMS VAX Operating System Base, the SMP Base Extension, and Interactive User licenses are not supported by the VMS or OpenVMS VAX operating system releases prior to OpenVMS VAX Version 5.5. 4. OpenVMS VAX Distributed Interactive User License (QL-09SA*-**) LMF Product Name: ADL-USER This license grants the right to interactive use of the OpenVMS VAX operating system, provided the appropriate Operating System Base License or one of the five types of VAX VMS Licenses has been previously installed on a VAX system. The Distributed Interactive User licenses are concurrent-use licenses and are available in any quantity, except unlimited. Distributed Interactive User licenses are mobile (and can be redesignated) and may be installed and used on a single OpenVMS VAX processor or shared in a single OpenVMS VAXcluster. A distributed interactive user is defined as an individual who is logged in to an OpenVMS VAX processor or OpenVMS VAXcluster system or is using the operating system software interactively by a means other than login. This license grants the right to use the same version of the op- erating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. 5. OpenVMS Concurrent Use License (VAX and Alpha) (QL-MT3A*-3*) LMF Product Name: OPENVMS-ALPHA-ADL This license grants the right to interactive use of the OpenVMS operating system, provided the appropriate OpenVMS Operating Sys- tem Base License is installed on an OpenVMS VAX processor, or on an OpenVMS Alpha processor, or on OpenVMS VAX processors if one of the five types of VAX VMS Licenses has been previously in- stalled on a VAX system. The OpenVMS Concurrent Use Licenses are 104 available in any quantity desired except unlimited. OpenVMS Con- current Use Licenses are mobile (and can be redesignated) and may be installed and used on a single OpenVMS VAX or OpenVMS Al- pha processor, shared in a single OpenVMS VAXcluster, or a single OpenVMS Alpha Cluster, or shared in a mixed-architecture OpenVMS Cluster. A user that enables a Concurrent Use License is defined as an individual who is logged in to an OpenVMS VAX processor, or an OpenVMS Alpha processor, or an OpenVMS VAXcluster, or an OpenVMS Alpha Cluster, or a mixed-architecture OpenVMS Cluster who is interactively using the OpenVMS operating system software by a means other than login. When an OpenVMS VAX SMP System upgrade is performed, the SMP Ex- tension to the OpenVMS Alpha Operating System License permits the use of all existing Distributed Interactive User Licenses on the upgraded system. The Operating System Base License provides the right to use only the OpenVMS features of the current or prior versions of the Open- VMS operating system. This license grants the right to use the same version of the op- erating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. 105 OpenVMS Alpha License Information There are five types of OpenVMS licenses available on Alpha pro- cessors: 1. Operating System Base License (QL-MT1A*-6*) LMF Product Name: OpenVMS-ALPHA This license grants the right to noninteractive use of the remote batch, print, application, and computing services of the OpenVMS Alpha operating system on a single processor. This license autho- rizes one direct login for system management purposes only. For dual-processor systems (AlphaServer 8200, 8400 and AlphaServer GS60, GS60E, and GS140), the base license for these specific sys- tems grants the right to noninteractive use of the remote batch, print, application, and computing services of the OpenVMS Alpha operating system on a dual processor. The Operating System Base License is a prerequisite for OpenVMS User Licenses and SMP Base Extension Licenses. The Operating System Base License provides the right to use only the OpenVMS features of the current or prior versions of the Open- VMS Operating System. For the AlphaServer ES47, ES80, and GS1280 systems, the Base Li- cense part number does not not include an SMP license for the first CPU. For these systems, an SMP Extension is required for each CPU, including the first. The Operating System Base License, in combination with SMP Extensions, grants the right to use the operating system on a single, specified system model for purposes of executing remotely submitted requests for batch, print, and file services, as well as non-interactive display of information. 2. Symmetric Multiprocessing (SMP) Base Extension License (QL- MT1A9-6*) LMF Product Name: OpenVMS-ALPHA 106 SMP Base Extensions extend the Operating System Base License to enable symmetric multiprocessing capability on those OpenVMS Alpha systems supporting SMP. SMP Base Extensions are permanently tied to the Operating System Base License and may not be separated from the Operating System Base License if an SMP board is removed from the system. SMP Extensions grant the right to use the same version of the operating system software as permitted for the corresponding Op- erating System Base License at the time when the SMP Extension is granted. For the AlphaServer ES47, ES80, and GS1280 systems, each dual SMP Extension to an Operating System Base License grants the rights to an additional dual CPU system module. The required dual SMP licenses are bundled with each AlphaServer ES47, ES80, and GS1280 system board as an add-on part number. 3. Individual User License (QL-MT2A*-**) (No Longer Offered) LMF Product Name: OpenVMS-ALPHA-USER This license grants the right to interactive use of the OpenVMS Alpha operating system, provided the appropriate Operating System Base License has been previously installed on the OpenVMS Alpha system. The Individual User Licenses are available in any quantity desired or as an unlimited user license. Individual User Licenses can be redesignated and may be installed and used on a single OpenVMS Alpha processor only. They may not be shared in a single OpenVMS Cluster environment. A user is defined as an individual who is logged in to an OpenVMS Alpha processor or is interactively using the operating system software by means other than a login. This license grants the right to use the same version of the op- erating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. 107 4. OpenVMS Alpha Distributed Interactive User License (QL-MT3A*- **) (No Longer Offered) LMF Product Name: OpenVMS-ALPHA-ADL This license grants the right to interactive use of the OpenVMS Alpha operating system, provided the appropriate Operating System Base License has been previously installed on an Alpha system. The ADL Interactive User Licenses are concurrent-use licenses and are available in any quantity desired except unlimited. ADL Interac- tive User Licenses can be redesignated and may be installed and used on a single OpenVMS Alpha processor, or shared in a single OpenVMS Cluster environment. A distributed interactive user is defined as an individual who is logged in to an OpenVMS Alpha processor or OpenVMS Cluster or is interactively using the operating system software by means other than a login. This license grants the right to use the same version of the op- erating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. 5. OpenVMS Concurrent-Use License (for both VAX and Alpha) (QL- MT3A*-3*) LMF Product Name: OPENVMS-ALPHA-ADL This license grants the right to interactive use of the OpenVMS operating system, provided the appropriate OpenVMS Operating Sys- tem Base License in installed on an OpenVMS VAX processor, and/or on an OpenVMS Alpha processor, or on OpenVMS VAX processors if one of the five types of VAX VMS Licenses has been previously installed on a VAX system. The OpenVMS Concurrent-Use Licenses are available in any quantity desired except unlimited. OpenVMS Concurrent-Use Licenses are mobile (can be redesignated) and may be installed and used on a single OpenVMS VAX or OpenVMS Alpha processor, or shared in a single OpenVMS VAXcluster or a single 108 OpenVMS Cluster, or shared in a mixed-architecture OpenVMS Clus- ter. A user that enables a Concurrent-Use License is defined as an individual who is logged in to an OpenVMS VAX processor, or an OpenVMS Alpha processor, or an OpenVMS VAXcluster, or an OpenVMS Cluster, or a mixed OpenVMS Cluster and/or is interactively using the OpenVMS operating system software by means other than a login. When an Alpha SMP system upgrade is performed, the SMP Base Exten- sion to the OpenVMS Alpha Operating System License permits the use of all existing User Licenses on the upgraded system. This license grants the right to use the same version of the op- erating system software as permitted for the corresponding Op- erating System Base License at the time when the User License is installed. License Management Facility Support The OpenVMS operating system supports the OpenVMS License Manage- ment Facility (LMF). 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:). Several of the VAX VMS and OpenVMS VAX license types are based on the number of concurrent users, called an activity license. Ev- ery 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 re- ferred to as an OpenVMS user, as follows: o Each remote terminal connection is considered an activity. This is true even if users set host to their local nodes (SET HOST 0). o Each connection from a terminal server is considered an activ- ity. 109 o A multiple-window session on a workstation is considered one activity, regardless of the number of windows. o A batch job is not considered an activity. o A remote network connection (a connection other than a remote terminal connection) is not considered an activity. For more information about HP's licensing terms and policies, contact your HP account representative. SOFTWARE PRODUCT SERVICES A variety of service options are available from HP. System Support Services provides integrated hardware and software remedial sup- port, telephone advisory support, and the right-to-use new version of kernel software. For more information, contact your local HP account representative. SYSTEMS SUPPORTED Alpha Systems Supported This section lists the Alpha systems that are supported by OpenVMS Alpha Version 7.3-2. Refer to the appropriate page at the follow- ing website for details concerning Alpha hardware configurations and options: http://h18002.www1.hp.com/alphaserver/ TURBOchannel Bus-Based Systems o DEC 3000 Models 300/300L/300LX/300X o DEC 3000 Models 400/400S o DEC 3000 Models 500/500S/500X o DEC 3000 Models 600/600S o DEC 3000 Models 700/700LX 110 o DEC 3000 Models 800/800S o DEC 3000 Models 900/900LX DSSI Bus-Based Systems o DEC 4000 Model 600 o DEC 4000 Model 700 XMI Bus-Based Systems o AlphaServer 8400 (All chip speeds) o DEC 7000 Model 600 o DEC 10000 Model 600 PCI Bus-Based Systems o AlphaServer 300 (All chip speeds) o AlphaServer 400 (All chip speeds) o AlphaServer 800 (All chip speeds) o AlphaServer 1000 (All chip speeds) o AlphaServer 1000A (All chip speeds) o AlphaServer 1200 (All chip speeds) o AlphaServer 2000 (All chip speeds, except 5/375) o AlphaServer 2100 (All chip speeds, except 5/375) o AlphaServer 2100A (All chip speeds, except 5/375) o AlphaServer 2100A LP (All chip speeds) o AlphaServer 4000 (All chip speeds) o AlphaServer 4100 (All chip speeds) o AlphaServer 8200 (All chip speeds) o AlphaServer 8400 (All chip speeds) o AlphaServer DS10 111 o AlphaServer DS10L o AlphaServer DS15 o AlphaServer DS20 o AlphaServer DS20E o AlphaServer DS25 o AlphaServer ES40 o AlphaServer ES45 o AlphaServer ES47 Rack * o AlphaServer ES80 o AlphaServer GS60 o AlphaServer GS60E o AlphaServer GS80 o AlphaServer GS140 o AlphaServer GS160 o AlphaServer GS320 o AlphaServer GS1280 * o DIGITAL 2100 Server Model A500MP, A600MP o AlphaStation 200 (All chip speeds) o AlphaStation 250 (All chip speeds) o AlphaStation 255/233, 255/300 o AlphaStation 400 (All chip speeds) o AlphaStation 500/266, 500/333, 500/400, 500/500 o AlphaStation 600 (All chip speeds) o AlphaStation 600A (All chip speeds) o Digital Personal Workstation 433au, 500au, 600au 112 o AlphaStation DS15 o AlphaStation DS20e o AlphaStation DS25 o AlphaStation ES40 o AlphaStation ES47 Tower * o AlphaStation XP900/DS10 o AlphaStation XP1000 Note: * Minimum of OpenVMS Version 7.3-1 plus patch kit required. Please refer to the following web site to find the current EV7 Patch kit: http::// The following semiconductor microprocessor development reference boards are supported by OpenVMS Alpha: o Alpha 21064/21064A PCI reference board (EB64+) o Alpha 21164 PCI reference board (EB164) o Alpha PC64 reference board (APC64) Modular Computing Component o Alpha 4/233 PICMG SBC o Alpha 4/266 PICMG SBC o Alpha 5/366 PICMG SBC o Alpha 5/500 PICMG SBC o CompactPCI CS-1000 VAX Systems Supported 113 This section lists the VAX systems that are supported by OpenVMS VAX Version 7.3. Refer to the Systems and Options Catalog and the Network and Communications Buyers Guide for details concerning VAX hardware configurations and options. Q-bus Based Systems o MicroVAX 3300, VAXserver 3300 o MicroVAX 3400, VAXserver 3400 o MicroVAX 3500, VAXserver 3500, VAXstation 3500, VAXstation 3520, VAXstation 3540 o MicroVAX 3600, VAXserver 3600 o MicroVAX 3800, VAXserver 3800 o MicroVAX 3900, VAXserver 3900 o VAX 4000, Models 100, 200, 300, 400, 500, 600 o VAX 4000, Models 50, 100A, 105A, 106A, 108, 500A, 505A, 600A, 700A, 705A, o VAXserver 4000, Models 200, 300, 400, 500, 600 XMI Bus-Based Systems o VAX 6000 Series, Models 210, 220, 230, 240 o VAX 6000 Series, Models 310, 320, 330, 340, 350, 360 o VAX 6000 Series, Models 410, 420, 430, 440, 450, 460 o VAX 6000 Series, Models 510, 520, 530, 540, 550, 560 o VAX 6000 Series, Models 610, 620, 630, 640, 650, 660 o VAXserver 6000, Models 210, 220, 310, 320, 410, 420, 510, 520, 610, 620, 630 o VAX 7000, Models 610, 620, 630, 640, 650, 660, 710, 720, 730, 740, 750, 760, 810, 820, 830, 840, 850, 860 114 o VAX 10000, Models 610, 620, 630, 640, 650, 660 Special System-Specific Internal Bus o MicroVAX 3100, Models 10, 10E, 20, 20E, 30, 40, 80, 85, 88, 90, 95, 96, 98 o VAXserver 3100, Models 10, 10E, 20, 20E o VAXstation 4000, Models 60, 90, 95, 96 o VAXstation 4000-VLC o VAX 9000, Models 110, 110VP[5], 210, 210VP, 310, 310VP System Restrictions DECwindows Restrictions The following list describes version-specific restrictions. The DECwindows Motif environment is not supported on these systems. MicroVAX I and VAXstation I Systems OpenVMS Restrictions OpenVMS VAX Version 5.1-1 is the final version to support the following systems: VAX-11/725 OpenVMS VAX Version 6.2 is the final version to support the fol- lowing systems: VAX-11/730 VAX-11/750 VAX-11/751 VAX-11/780 VAX-11/782 ____________________ Vector processor (VP) 115 VAX-11/785 VAXft 110 VAXft 310 VAXft 410 VAXft 610 VAXft 810 MicroVAX I VAXstation I OpenVMS VAX Version 7.2 is the final version to support the fol- lowing systems: MicroVAX II VAXstation II/GPX, VAXstation II/QVSS VAXstation 2000, VAXstation 2000/GPX, VAXstation 2000/MFB MicroVAX 2000 OpenVMS VAX Version 7.3 is the final version to support the fol- lowing systems: VAX 8200, VAX 8250, VAXserver 8200, VAXserver 8250 VAX 8300, VAX 8350, VAXserver 8300, VAXserver 8350 VAX 8530, VAXserver 8530, VAX 8550, VAXserver 8550 VAX 8600, VAX 8650, VAXserver 8600, VAXserver 8650 VAX 8700, VAXserver 8700 VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840 VAXserver 8800, VAXserver 8810, VAXserver 8820, VAXserver 8830, VAXserver 8840, VAX 8842, VAX 8974, VAX 8978 VAX 9000, Models 110, 110VP, 210, 210VP, 310, 310VP VAX 9000, Models 320, 320VP, 330, 330VP, 340, 340VP VAX 9000, Models 410, 410VP, 420, 420VP, 430, 430VP, 440, 440VP OpenVMS Alpha Version 7.3-1 is the final version to support the following systems: o DEC 2000 Models 300/500 o Tadpole AlphaBook 1 116 APPENDIX A This appendix describes HP's terminals, disks, tapes, controllers, graphics, and network options. Some restrictions for specific devices are listed, if applicable. HP reserves the right to change the number and type of devices supported by OpenVMS Alpha, OpenVMS VAX, DECnet for OpenVMS VAX and Alpha, DECnet-Plus for OpenVMS, TCP/IP Services for OpenVMS, and OpenVMS Cluster software. The minimum hardware requirements for future versions and updates of these software products may be different from current hardware requirements. For configuration details about Alpha or VAX hardware, refer to the Systems and Options Catalog and the Network and Communications Buyers Guide. Refer to the following SPDs for detailed product information: DECnet for OpenVMS (SPD 48.48.xx), DECnet-Plus for OpenVMS (SPD 50.45.xx, 25.03.xx), TCP/IP Services for OpenVMS (SPD 46.46.xx), OpenVMS Cluster Software (SPD 29.78.xx), and Open3D for OpenVMS Alpha (SPD 45.08.xx). 117 Terminals and Terminal Line Interfaces To prevent input from overflowing a buffer, terminals use the ASCII control characters DC1 and DC3 for synchronization as de- fined by HP STD 111, Revision A. VXT windowing terminals support standard ANSI applications and X Windows Systems using the LAT transport protocol. The following terminals are supported by OpenVMS Alpha: VT200 VT300 VT400 series series series VT500 VXT2000 series series The following terminals are supported by OpenVMS VAX: VT52 VT100 LA series series VT300 VT1000 LQP02 series series VT200 VT500 series series Terminals on Professional 350, Rainbow 100, and DECmate II systems emulate VT100 terminals. Only limited support is available for the VT52. The VT131, when running an application, operates in block mode. When interacting with OpenVMS VAX and associated utilities, the VT131 operates only in VT100 (or interactive) mode and not in block mode. Note: The VT1000 is a monochrome windowing terminal that supports standard ANSI applications and the X Window System. The transport protocol supported is LAT for OpenVMS. The product supports 15- inch and 19-inch monitors. Disks 118 The following table lists the disk drives that are supported on OpenVMS Alpha and VAX, the bus the device is supported on, and the minimum required version of OpenVMS Alpha and/or VAX that supports the device. NS stands for not supported. ___________________________________________________________________ Min. Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ EF51R[3] 107 MB solid state DSSI NS 5.5- 2 EF52R[4] 205 MB solid state DSSI NS 5.5- 2 EF53[4] 267 MB solid state DSSI NS 5.5- 2 ESE-20[3] 120 MB solid state SDI NS ESE-52[3] 120 MB solid state SDI 1.0 5.5- 2 ESE-56 600 MB solid state SDI 1.5 5.5- 2 ESE-58 960 MB solid state SDI 1.5 5.5- 2 EZ31 134 MB solid state SCSI 6.2-1H3 NS 119 ______________________________________________________________Min._ Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ EZ32 268 MB solid state SCSI 6.2-1H3 NS EZ51R[3] 100 MB solid state SCSI 1.5 5.5- 2 EZ54R 467 MB solid state SCSI 1.5 5.5- 2 EZ58R 855 MB solid state SCSI 1.5 5.5- 2 EZ64 475 MB solid state SCSI 6.2-1H3 5.5- 2 EZ69 950 MB solid state SCSI 6.2-1H3 5.5- 2 DS-EZ41 134 MB solid state SCSI 6.2-1H3 6.2- 1H3 DS-EZ42 268 MB solid state SCSI 6.2-1H3 6.2- 1H3 DS-EZ705 536 MB solid state SCSI 6.2-1H3 6.2- 1H3 DS-EZ711 1.07 GB solid state SCSI 6.2-1H3 6.2- 1H3 DS-EZ716 1.6 GB solid state SCSI 6.2-1H3 6.2- 1H3 PBXRW-JC 2 GB wide fixed UltraSCSI 6.2-1H3 disk PBXRW-NB 4 GB wide fixed UltraSCSI 6.2-1H3 disk PBXRW-SA 9 GB wide fixed UltraSCSI 6.2-1H3 disk 120 ______________________________________________________________Min._ Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ PBXRZ-JC 2 GB narrow fixed SCSI 6.2-1H3 disk PBXRZ-NB 4 GB narrow fixed SCSI 6.2-1H3 disk PBXRZ-SA 9 GB narrow fixed SCSI 6.2-1H3 disk RA60[4] 205 MB removable SDI NS 6.1 RA70 280 MB fixed SDI NS 6.1 RA71 700 MB fixed disk SDI NS 5.4- 2 RA72 1 GB fixed disk SDI 1.0 5.4- 2 RA73 2 GB fixed disk SDI 1.0 5.5- 2 RA80[3] 128 MB fixed disk SDI NS 6.1 RA81 456 MB fixed disk SDI NS 6.1 RA82 622 MB fixed disk SDI NS 6.1 RA90 1.2 GB fixed disk SDI 1.0 6.1 RA92 1.5 GB fixed disk SDI 1.0 6.1 RC25[3] 2 disks each 26 Q-bus NS 6.1 MB (1 fixed and 1 removable) disk drive with shared spindle RD32[3] VAX 42 MB fixed Q-bus NS disk RD51[3] 10 MB fixed disk Q-bus NS 6.1 RD52[3] 31 MB fixed disk Q-bus NS 6.1 121 ______________________________________________________________Min._ Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RD53[3] 71 MB fixed disk Q-bus NS RD54[4] 159 MB fixed disk Q-bus NS RF30[4] 150 MB fixed disk DSSI NS 6.1 RF31 381 MB fixed disk DSSI 1.5 RF31F[1] 200 MB fixed disk DSSI NS 5.4- 2 RF31T 381 MB fixed disk DSSI 1.5 5.5- 2 122 ______________________________________________________________Min._ Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RF35 800 MB fixed disk DSSI 1.0 5.5 RF36 1.6 GB fixed disk DSSI 6.1 6.0 RF71 400 MB fixed disk DSSI 1.5 6.1 RF72 1 GB fixed disk DSSI 1.5 5.5- 2 RF74 3.5 GB fixed disk DSSI 6.1 6.0 RK06[3] 14 MB removable UNIBUS NS disk RK07[3] 28 MB removable UNIBUS NS disk RL02[3] 10 MB removable UNIBUS NS disk RRD40[3] 600 MB read-only Q-bus NS optical disk drive and SCSI RRD42 600 MB read-only SCSI 1.0 5.4- optical disk drive 2 RRD43 680 MB read-only SCSI 6.1 5.5- optical disk drive 2 RRD44 680 MB read-only SCSI 6.1 optical disk drive RRD45 600 MB 4x read-only SCSI 6.1 6.1 optical disk drive RRD46 600 MB 12x read- SCSI 6.2-1H3 5.5- only optical disk 2H4 drive RRD47 600 MB 32x read- SCSI 6.2-1H3 6.2- only optical disk 1H3 drive 123 ______________________________________________________________Min._ Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RRD50[3] 600 MB read-only Q-bus NS optical disk drive RX02[3] 512 KB diskette UNIBUS NS RX23 1.47 MB diskette SCSI NS RX23L 1.44 MB diskette SCSI 6.2-1H3 NS drive RX26 2.8 MB diskette I82077 1.5-1H1 drive RX26 2.8 MB diskette SCSI 1.0 5.5 drive RX33[3] 1.2 MB diskette Q-bus NS drive, requires minimum RQDX3 mi- crocode of Version 3.0 RX50[3] 400 KB diskette Q-bus NS RV20[3] 2 GB Write Once Q-bus, NS Read Many optical UNIBUS, disk drive VAXBI RV64[3] 2 GB Write Once Q-bus, NS Read Many optical UNIBUS, disk subsystem VAXBI RZ1BB 2 GB wide fixed UltraSCSI 6.2-1H3 disk RZ1CB 4 GB wide fixed UltraSCSI 6.2-1H3 disk RZ1DB 9 GB wide fixed UltraSCSI 6.2-1H3 disk 124 ______________________________________________________________Min._ Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RZ22[3] 52 MB fixed disk SCSI NS RZ23[3] 104 MB fixed disk SCSI NS RZ23L[3] 121 MB fixed disk SCSI 1.5 5.4- 1 RZ24[1] 209 MB fixed disk SCSI 1.5 6.1 RZ24L 245 MB fixed disk SCSI 1.0 5.4- 3 RZ25 425 MB fixed disk SCSI 1.0 5.4- 3 RZ25L 500 MB fixed disk SCSI 1.5 5.5- 2 RZ25M 540 MB fixed disk SCSI 6.1 6.1 RZ26 1.05 GB fixed disk SCSI 1.0 5.5- 2 RZ26B 1.05 GB fixed disk SCSI 1.5 6.0 RZ26L 1.0 GB fixed disk SCSI 1.5 5.5- 2 RZ26N 1.0 GB fixed disk SCSI 6.2 5.5- 2H4 RZ28 2.1 GB fixed disk SCSI 1.5 5.5- 2 RZ28B 2.1 GB fixed disk SCSI 1.5 6.0 RZ28D 2.1 GB fixed disk SCSI 6.2 6.2 RZ28L 2 GB narrow fixed SCSI 6.2-1H3 5.5- disk 2H4 RZ28M 2.1 GB fixed disk SCSI 6.2-1H3 5.5- 2H4 125 ______________________________________________________________Min._ Min. VAX Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RZ29B 4.3 GB fixed disk SCSI 6.1 5.5- 2H4 RZ29L 4 GB narrow fixed SCSI 6.2-1H3 5.5- disk 2H4 RZ35 852 MB fixed disk SCSI NS 5.4- 3 RZ40 9 GB narrow fixed SCSI Version 6.1 disk 6.2-1H3 RZ55 332 MB fixed disk SCSI 1.0 6.1 RZ56 665 MB fixed disk SCSI 1.0 6.1 RZ57[2] 1 GB fixed disk SCSI 1.5 5.4- 3 RZ58 1.35 GB fixed disk SCSI 1.0 5.5 RZ73 2 GB fixed disk SCSI 1.0 6.0 RZ2CC 4 GB fixed disk SCSI 7.1-1H2 RZ2DC 9 GB fixed disk SCSI 7.1-1H2 RZ1EF__________18_GB_fixed_disk_______SCSI________7.1-1H2__________ ____________________ Specific tailoring is required to use this device as an OpenVMS Al- pha or VAX system disk with the DECwindows Motif environment. Minimum revision firmware is V6000. Device cannot be used as an OpenVMS VAX system disk. Device cannot be used as an OpenVMS VAX system disk with DECwindows Motif environment. TSZ05 is not supported in Version 7.2. Last version supported was Alpha Version 6.1. 126 NOTE: The preceding list is not complete in terms of currently shipping disk and tape devices; that list changes frequently. Currently, supported disk and tape devices are reflected in the AlphaServer Supported Options Lists that can be found at the indi- vidual AlphaServer Web pages: http://h18002.www1.hp.com/alphaserver After clicking on the requested AlphaServer, you can access links from the left-hand columns under Technical Information and then under Supported Options. From there, you can sort by the type of option. Disk Options Supported by HP's Services Enterprise Integration Center (SEIC) (VAX Only) RF30- 150 MB removable (DSSI) RA[4] disk RF31-RA 381 MB removable (DSSI) disk RF71-RA 400 MB removable (DSSI) disk RF71-RA 1 GB removable (DSSI) disk RWZ01 594 MB optical (SCSI) (Version 5.4-3) removable disk Tapes The following table lists the tapes that are supported on OpenVMS Alpha and VAX, the bus the device is supported on, and the minimum required version of OpenVMS Alpha and/or VAX that supports the device. 127 _____________________________________________________________Min.__ Min. VAX Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TA78 1600/6250 BPI, STI 1.0 STI TU78 TA79 STI TU79 STI NS TA81 145 MB tape drive STI 1.0 TA90 1.2 GB tape car- STI 1.0 tridge subsystem. (5-inch 200 MB cartridge) TA90E 1.2 GB tape car- STI NS tridge subsys- tem. Compacts data records automati- cally TA91 High-performance STI NS 5.4-2 tape drive TE16 9-track magnetic M-BUS NS tape drive TF70 290 MB TK70 tape DSSI NS 5.4-2 cartridge drive TF85 2.6 GB streaming DSSI 6.1 5.5-2 tape cartridge drive TF857 18.2 GB tape car- DSSI 6.1 5.5-2 tridge loader TF86 6.0 GB DLT tape DSSI 6.1 6.1 cartridge TF867 42 GB DLT tape DSSI 6.1 6.1 loader 128 _____________________________________________________________Min.__ Min. VAX Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TK50 95 MB, 5 1/4-inch Q-bus NS streaming tape and SCSI cartridge drive TK70 296 MB, 5 1/4-inch Q-bus NS streaming tape cartridge drive TKZ09 5.0 GB, 8mm tape SCSI 1.5 NS drive TKZ9E 1-14 GB, 8mm tape SCSI 6.2-1H3 5.5-2 drive TKZ15 Exabyte 8505 8mm SCSI 6.1 6.1 tape drive TKZ20 2 GB, DC2000 tape SCSI 6.1 6.1 drive TKZ60 200/400 MB, SCSI 1.0 5.5-2 3480/3490 tape drive TKZ61 4.4 GB, 3480/3490 SCSI 6.1 5.5-2 tape loader TKZ62 24 GB, 3480/3490/3490E SCSI 6.1 5.5-2 tape loader TL893 18.4 TB, 4mm, DAT SCSI 6.2-1H3 NS tape drive TL894 3.3 TB, 4mm, DAT SCSI 6.2-1H3 NS tape drive TL896 12.3 TB, 4mm, DAT SCSI 6.2-1H3 NS tape drive TLZ04 1.2 GB, 4mm, DAT SCSI 1.0 tape drive 129 _____________________________________________________________Min.__ Min. VAX Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TLZ06 4 GB, 4mm, DAT tape SCSI 1.0 6.1 drive TLZ07 8 GB, 4mm, DAT tape SCSI 6.1 6.1 drive TLZ08 5.25-inch, 2 GB, SCSI NS 8mm tape drive TLZ09 4 GB, DAT tape SCSI 6.1 5.5- drive 2H4 TLZ10 12/24 GB, DAT tape SCSI 6.2-1H3 5.5-2 drive TLZ6L 4 GB, 3.5-inch, 4mm SCSI 6.1 DAT tape loader TLZ7L 8 GB, 3.5-inch, 4mm SCSI 6.1 6.1 DAT tape loader TLZ9L 32/64 GB, 3.5-inch, SCSI 6.2-1H3 4mm DAT tape loader TL812 1.92 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 TL822 10.4 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 TL826 7.0 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL890 1.12 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL891 700 GB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL893 18.4 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 130 _____________________________________________________________Min.__ Min. VAX Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ DS-TL894 3.3 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL895 6.7 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL896 12.3 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 TS05 9-track magnetic Q-bus NS tape drive TS11 9-track magnetic UNIBUS NS tape drive TSZ05 1600 bits/in tape SCSI 1.5 drive TSZ07 1600/6250 BPI tape SCSI 1.0 5.4-1 drive TU77 9-track magnetic M-BUS NS tape drive TU78 9-track magnetic M-BUS NS tape drive TU80 9-track magnetic UNIBUS NS tape drive TU81 9-track magnetic UNIBUS NS tape drive TU81-Plus Streaming 9-track Q-bus, NS magnetic tape drive UNIBUS, VAXBI TZ30 95 MB, half-height SCSI 1.0 DLT tape drive TZ85 2.6 GB DLT tape SCSI 1.0 drive 131 _____________________________________________________________Min.__ Min. VAX Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TZ857 18 GB, DLT tape SCSI 1.0 loader TZ86 6.0 GB, DLT tape SCSI 1.5 drive TZ867 42 GB, DLT tape SCSI 1.5 loader TZ87 20 GB, DLT tape SCSI 6.1 6.1 drive TZ875 100 GB, DLT tape SCSI 6.1 6.1 loader TZ877 140 GB, DLT tape SCSI 6.1 6.1 loader TZ88 20/40 GB, DLT tape SCSI 6.2 5.5- drive 2H4 TZ88N 40/80 GB, DLT tape SCSI 6.2 5.5- drive 2H4 TZ89N 35/70 GB, DLT tape SCSI 6.2-1H3 5.5- drive 2H4 TZ885 40/80 GB, DLT tape SCSI 6.2-1H2 5.5- loader 2H4 TZ887 40/80 GB, DLT tape SCSI 6.2-1H2 5.5- loader 2H4 TZK08 2.2 GB 8mm, tape SCSI 6.1 drive TZK10 320/525 MB, QIC SCSI 1.0 tape drive TZK11 2.0 GB, QIC tape SCSI 6.1 drive 132 _____________________________________________________________Min.__ Min. VAX Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TZS20 25/50 GB, AIT 8mm, SCSI 7.1 tape drive ESL9326 40/80 GB, DLT tape SCSI 7.2 library family ESL9198 40/80 GB, DLT tape SCSI 7.2 ______________library_family_______________________________________ NOTE: The preceding list is not complete in terms of currently shipping disk and tape devices; that list changes frequently. Currently, supported disk and tape devices are reflected in the AlphaServer Supported Options Lists that can be found at the indi- vidual AlphaServer Web pages: http://h18002.www1.hp.com/alphaserver After clicking on the requested AlphaServer, you can access links from the left-hand columns under Technical Information and then under Supported Options. From there, you can sort by the type of option. Networks Storage Servers HS111 StorageWorks FDDI StorageServer HS121 StorageWorks FDDI StorageServer HS211 StorageWorks FDDI StorageServer HS221 StorageWorks FDDI StorageServer HS241 StorageWorks FDDI StorageServer SWXNA StorageWorks FDDI StorageServer 133 InfoServer An integrated hardware and software system that sits directly on the Ethernet to provide CD-ROM, hard disk, magneto-optical, and tape access to OpenVMS clients in a LAN. It supports up to 14 SCSI devices and can be used for software distribution and ini- tial system load (ISL). For more information, refer to the InfoServer Software Product Description (SPD 33.20.xx.) Enterprise Storage Arrays SWXES StorageWorks Enterprise Storage Array 10000, 12000 SWXRA StorageWorks RAID Array 7000, 310, 450, 3000, 8000 EMA StorageWorks Enterprise Modular Array 1200, 1600 EVA StorageWorks Enterprise Virtual Array 3000, 5000 MSA StorageWorks Modular Storage Array 1000 Controllers and Adapters HSC40 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC50 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 4.1.) Refer to SPD 32.96.xx for supported configurations. HSC60 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC65 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. 134 HSC70 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC90 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC95 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSD05 DSSI to SCSI-2 FSE StorageWorks bus adapter. (Firmware must be at minimum Version X36.) HSD10 DSSI to SCSI-2 FSE StorageWorks bus adapter HSD30 DSSI based StorageWorks controller that supports up to three SCSI-2 FSE ports. (HSD firmware must be at minimum Version V15D.) HSD50 DSSI based StorageWorks controller that supports up to six SCSI-2 FSE ports. (HSD firmware must be at minimum Version 5.0D.) HSJ30 CI based StorageWorks controller that supports up to three SCSI-2 FSE ports. (HSJ firmware must be at minimum Version V15J.) HSJ40 CI based StorageWorks controller that supports up to six SCSI-2 FSE ports. (HSJ firmware must be at minimum Version V15J.) HSJ50 CI based StorageWorks controller that supports up to six SCSI-2 FSE ports. (HSJ firmware must be at minimum Version Version 5.0J-2 or later.) HSJ80 CI based StorageWorks controller that has 512 MB cache and dual CI host ports. (HSJ firmware must be at minimum ACS Version 8.5J-2 or later.) 135 HSZ20 Fast-wide differential SCSI based StorageWorks con- troller that supports up to three SCSI-2 FSE ports. (Alpha only) HSZ40- Fast-wide differential SCSI based StorageWorks con- Bx/Cx troller that supports up to six SCSI-2 FSE ports. (HSZ firmware must be at minimum Version V2.5Z.) (Alpha only) HSZ50 Fast-wide differential SCSI based StorageWorks con- troller that supports up to six SCSI-2 FSE ports. (HSZ firmware must be at minimum Version 5.0Z.) (Alpha only) HSZ70 UltraSCSI wide differential based StorageWorks controller that supports up to six UltraSCSI wide single-ended device ports and one host port. (Alpha only) HSZ80 UltraSCSI wide differential based StorageWorks controller that supports up to six UltraSCSI wide single-ended device ports and two host ports. (Alpha only) HSZ22 UltraSCSI wide differential based StorageWorks controller that supports up to two UltraSCSI wide single-ended device ports and two host ports. (Alpha only) HSG60 Fibre Channel based StorageWorks controller that supports up to two UltraSCSI wide single-ended de- vice ports and two host ports. (Alpha only; Version 7.2-1 and higher) HSG80 Fibre Channel based StorageWorks controller that supports up to six UltraSCSI wide single-ended de- vice ports and two host ports. (Alpha only; Version 7.2-1 and higher) 136 HSV110 Fibre Channel based StorageWorks virtualizing con- troller that supports Fibre Channel native device ports and two host ports. (Alpha only; Version 7.2-2 and higher) MDR StorageWorks Modular Data Router for connecting SCSI tape devices to a FC switch. (Alpha only) MSR StorageWorks Network Storage Router for connecting SCSI tape devices to a FC switch. (Alpha only) KDM70 Mass storage controller for XMI systems with eight SDI ports. KFESA Mass storage controller for EISA systems with one DSSI port. (Alpha only) KFESB Mass storage controller for EISA systems with one DSSI port. (Alpha only) KFMSB Mass storage controller for XMI systems with two DSSI ports. (Alpha only) KFPSA Mass storage controller for PCI systems with one DSSI port. (Alpha only; Version 6.2-1H2 minimum support) KZESC-AA Backplane RAID controller for EISA systems with one SCSI-2 FSE port. (Alpha only) KZESC-BA Backplane RAID controller for EISA systems with three SCSI-2 FSE ports. (Alpha only) KZMSA Mass storage controller for XMI systems with two SCSI ports. (Limited SCSI-2 support - Alpha only) KZPAA Mass storage adapter for PCI systems with one SCSI-2 FSE port. (Alpha only) KZPBA-CA Mass storage adapter for PCI based servers with one UltraSCSI port. Single-host support in Version 6.2-1H3, and Version 7.1-1H1 and higher. (Alpha only) 137 KZPBA-CB Mass storage adapter for PCI based servers with two UltraSCSI ports. Single host support in Version 6.2- 1H3, and multi-host support in Version 7.1-1H1 and higher. (Alpha only) KZPBA-CC Mass storage adapter for PCI-X based servers with two UltraSCSI ports. Multi-host support in Version 7.3 and higher. (Alpha only) KZPDA Mass storage adapter for PCI systems with one SCSI-2 FWSE port. (Alpha only) KZPEA Mass storage LVD adapter for PCI based servers with two Ultra3 SCSI ports. Single-host support only. Support for Version 7.2-2 and higher. (Alpha only) KZPSA Mass storage adapter for PCI systems with one SCSI-2 FWD port. (Alpha only; 26 per system maximum with Version 6.2-1H3 and Version 7.1) KZPSC-AA Backplane RAID controller for PCI systems with one SCSI-2 FSE port. (Alpha only) KZPSC-BA Backplane RAID controller for PCI systems with three SCSI-2 FSE ports. (Alpha only) KZPAC- One- and two-channel Backplane RAID controller for AA,CA,CB PCI systems. (Alpha only) KZPDC-BE, Smart Array Backplane RAID controller for PCI sys- DF tems with 2 or 4 Ultra SCSI ports. (Alpha only) KZPCM Mass storage/network adapter for PCI systems with one SCSI-2 FSE port, an Ethernet port to connect to IEEE 802.3 local area networks. (Alpha only; Version 6.2-1H1 minimum support) KZPCA Mass storage adapter for PCI based servers with one UltraSCSI, Ultra-2 port . (Alpha only) KGPSA-BC, Mass storage adapter for PCI-based servers with one CA, DA Fibre Channel port. (Alpha only; Version 7.2-1 and higher) 138 KZTSA Mass storage adapter for TURBOchannel systems with one SCSI-2 FWD port. (Alpha only) PB2HA-SA Mass storage controller for EISA systems with one SCSI port. (Limited SCSI-2 support. Alpha only on systems with no greater than 1 GB of memory.) PMAZB Mass storage adapter for TURBOchannel systems with two SCSI-2 single-ended ports. (Alpha only) PMAZC Mass storage adapter for TURBOchannel systems with two fast SCSI-2 FSE ports. (Alpha only) Hubs and Switches DWZZH-03 3-port SCSI hub DWZZH-05 5-port SCSI hub DSGGA-AA/B 8/16-port Fibre Channel switch DSGGD 16-port 2 GB Fibre Channel switch Controllers (VAX Only) HSZ10 SCSI based StorageWorks controller that supports up to two SCSI-2 ports. IDC Integrated Disk Controller for VAX-11/725 and VAX- 11/730 systems. IDTC Integral Disk and Tape Controller for VAX 8600 and VAX 8650 systems. LPA11-K Microprocessor controller for laboratory acquisi- tion I/O devices, accommodating up to two AD11-K, one AA11-K, one KW11-K, two AM11-Ks, and five DR11- K devices. One LPA11-K controller is supported per UNIBUS, and a maximum of two are supported per sys- tem. KDA50 Q-bus MSCP disk controller. The KDA50 disk con- troller supports up to four of the following drives: RA60, RA70, RA80, RA81, and RA82. 139 KDB50 VAXBI MSCP disk controller. The KDB50 disk con- troller supports up to four of the following drives: RA60, RA80, RA81, and RA82. KFQSA Q-bus to DSSI bus adapter. This adapter allows up to seven DSSI storage devices to attach to the DSSI bus. (Six DSSI storage devices are allowed in a multi-host configuration.) KLESI Q-bus, UNIBUS, and VAXBI tape controller for the TU81-Plus, RV20, or RC25. KRQ50 Q-bus controller for the RRD40/RRD50 compact disc reader. KZQSA Q-bus to SCSI bus adapter. This adapter allows up to seven SCSI storage devices to attach to the SCSI bus. Supported only for CD-ROM and specific tape devices. KFDDA VAX 4000 model 100 DSSI bus adapter. This adapter allows up to seven DSSI storage devices to attach to the DSSI bus. (Six DSSI storage devices are allowed in a multi-host configuration.) KFDDB VAX 4000 model 500/600/700 DSSI bus adapter. This adapter allows up to seven DSSI storage devices to attach to the DSSI bus. (Six DSSI storage devices are allowed in a multi-host configuration.) LP11 UNIBUS parallel high-speed line printer controller for the LPxx printers. LPV11 Q-bus parallel high-speed line printer controller. RK711 UNIBUS disk controller for RK07 disk drives. RL211 UNIBUS disk controller for the RL02 disk drive. 140 RQDXx Q-bus disk controller for MicroVAX and VAXstation systems. There is an RQDX1, RQDX2, and an RQDX3 controller. The RQDXx disk controller supports as many as four disk units, with each RX50 diskette drive counting as two units. Due to controller lim- itations, the system supports a maximum of four devices; the number of RD/RX devices the system supports depends on the enclosure. The RQDX3 disk controller is required for the RD54 and the RX33 drives. RX211 UNIBUS diskette controller for two RX02 drives. One RX211 diskette controller is supported per system. RUX50 UNIBUS diskette controller for RX50 drives. One RUX50 diskette controller is supported per system. TM03 MASSBUS tape controller for the TE16 and TU77 mag- netic tape drives. TM32 BI bus, 9-track tape controller only with large record support. TM78 MASSBUS tape controller for the TU78 magnetic tape drive. TQK50 Q-bus tape controller for the TK50 cartridge tape drive. TQK70 Q-bus tape controller for the TK70 cartridge tape drive. TS11 UNIBUS tape controller for the TS11 magnetic tape drive. TBK50 BI bus tape controller for the TK50 cartridge tape drive. TBK50 BI bus tape controller for the TK50 cartridge tape drive. TBK70 BI bus tape controller for the TK70 cartridge tape drive. 141 TUK50 UNIBUS tape controller for the TK50 cartridge tape drive. One TUK50 tape controller is supported per system. UDA50 UNIBUS MSCP disk controller. The UDA50 controller must have a minimum microcode version of REV 3. The UDA50 controller supports up to four of the following disk drives: RA60, RA80, RA81, and RA82. Asynchronous Terminal Controllers (Alpha Only) PBXDA- 4-port PCI asynchronous terminal controller AA PBXDA- 8-port PCI asynchronous terminal controller AB PBXDA- 16-port PCI asynchronous terminal controller AC Asynchronous Terminal Controllers (VAX Only) CXA16 16-line serial terminal multiplexer (DEC-423), maximum baud rate supported: 38400. (No modem control) (Q-bus) CXB16 16-line serial terminal multiplexer (RS422), maximum baud rate supported: 38400. (No modem control) (Q-bus) CXY08 8-line serial terminal multiplexer (RS232), maximum baud rate supported: 19200. (Full modem control) (Q-bus) DHB32 16-line asynchronous terminal controller for VAXBI, maximum baud rate supported: 19200. (VAXBI) DHF11 32-line asynchronous terminal controller (DEC 423), maximum baud rate supported: 19200. (No modem control) (Q-bus) 142 DHT32 8-line asynchronous terminal controller (DEC 423). (No modem control) (MicroVAX 2000) DHQ11 8-line asynchronous terminal controller (EIA RS-232-C or RS-423-A), maximum baud rate supported: 19200. (Full modem control) (Q-bus) DHU11 16-line asynchronous terminal controller (RS-232-C), maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control) (UNIBUS) DHV11 8-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control) (Q-bus) DMB32 8-line asynchronous terminal controller, maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control) (VAXBI) DMF32 8-line asynchronous terminal controller, maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control on first two lines) (UNIBUS) DMZ32 24-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Modem support dependent on configuration) (UNIBUS) DZ11 8-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: 9600. (Partial modem control) (UNIBUS) DZ32 8-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: 9600. (Partial modem control) (UNIBUS) DZQ11 4-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Partial modem control) (Q-bus) 143 DZV11 4-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Partial modem control) (Q-bus) Synchronous Controllers (Alpha Only) The X.25 for OpenVMS Alpha Systems software product contains the synchronous device drivers and is required when using synchronous communications options. Refer to SPD 47.37.xx for more informa- tion. SCC Integral Synchronous Communications controller on DEC 3000 systems DSYT1 2-port TURBOchannel/Synchronous Communications con- troller DNSES 2-port EISA/Synchronous Communications controller (Ver- sion 6.2-1H2 minimum support) PBXDI- 2- or 4-port ISA/Synchronous Communications controller Ax PBXDP- 2-, 4-, or 8-port PCI/Synchronous Communications con- Ax troller Synchronous Controllers (VAX Only) The optional VAX Wide Area Network Device Drivers component of the DECnet-Plus for OpenVMS software product contains the synchronous device drivers and is required when using synchronous communica- tion options. Refer to SPD 25.03.xx for more information. DMB32 Point-to-point synchronous interface. (VAXBI) DMC11 High-speed, local, point-to-point synchronous inter- face; retired device, no longer offered as an option. (UNIBUS) 144 DMF32 Point-to-point or multipoint synchronous interface. (UNIBUS) DMP11 Point-to-point or multipoint synchronous interface; (UNIBUS) retired device, no longer offered as an op- tion. DMR11 Remote, point-to-point, synchronous interface; (UNIBUS) replaces DMC11. DMV11 Point-to-point or multipoint synchronous interface. (Q-bus) DPV11 Synchronous, 1-line, half or full-duplex, point-to- point communication interface supporting DDCMP, HDLC, SDLC, or BISYNC protocols. DSB32 2-line, multiple protocol, synchronous adapter. (VAXBI) DSH32 1-line synchronous (full modem control) and 8-line asynchronous (no modem control) communications con- troller for the MicroVAX 2000. DEC423 devices are sup- ported. Maximum baud rates supported: OpenVMS VAX, 19.2 Kb/s (kilobits/second); 9.6 Kb/s for MicroVAX 2000, etc. DST32 Synchronous single-line support for DDCMP up to 9.6 Kb/s, full duplex for MicroVAX 2000 systems. Concurrent use with the DHT32 is not supported. DSV11 Synchronous, 2-line, half or full-duplex point-to-point communication interface supporting DDCMP (one or two lines up to 64 Kb/s). DSF32 DEC WANcontroller 620 - 2-line synchronous communica- tions controller designed specifically for the VAXft 3000 processors, supporting DDCMP. DDCMP is supported at speeds up to 64 Kb/s per line for a 2-line opera- tion. 145 Graphics Options PBXGK ELSA/GLoria Synergy+ graphics option that provides 2D acceleration for supported PCI-based Alpha Work- stations and Servers. PBXGD PowerStorm 300/500 graphics option that provides 3D acceleration or 3D acceleration with stereo viewing capabilities for supported PCI-based Alpha Worksta- tions and Servers. PBXGF 3DLabs OXYGEN VX1 graphics option that provides 2D acceleration for supported PCI-based Alpha Worksta- tions and Servers. PBXGG ATI RADEON 7500 2D and 3D, PCI and AGP graphics option. OpenGL 1.1 supports PowerStorm 350 and 300 graphics accelerators on the following platforms: o XP900 o XP1000 o DS10 o DS20 o DS20e o DS25 o ES40 o ES45 OpenGL 1.2 supports ATI RADEON 7500 3D PCI graphics accelerators on the following platforms: o DS10 o DS10L o DS20e 146 o DS25 o ES40 o ES45 o ES47 o ES80 o GS1280 OpenGL 1.2 supports ATI RADEON 7500 3D AGP graphics accelerators on the following platforms: o ES45 o ES47 o ES80 o GS1280 OpenGL is included with the OpenVMS Alpha operating system dis- tribution kit. A separate license is required to run 3D graphics software, license part number is QL-0ADA9-AA. For more information, refer to the Open3D for OpenVMS Alpha Soft- ware Product Description (SPD 45.08.xx), and the DECwindows Motif Software Product Description (SPD 42.19.xx). LAN Options (VAX and Alpha) DEFTA A network adapter that connects TURBOchannel systems to ANSI FDDI local area networks. (100 mb/s) DEFZA A network adapter that connects TURBOchannel systems to ANSI FDDI local area networks. Not supported as a cluster interconnect or boot device. (100 mb/s) DEMFA A network adapter that connects XMI systems to ANSI FDDI local area networks. (100 mb/s) 147 DEMNA A network adapter that connects XMI systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) PMAD A network adapter that connects TURBOchannel systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) LAN Options (Alpha Only) DEFAA A network adapter that connects FUTUREBUS+ systems to ANSI FDDI local area networks. (100 mb/s) DEFEA A network adapter that connects EISA systems to ANSI FDDI local area networks. (100 mb/s) DEFPA A network adapter that connects PCI systems to ANSI FDDI local area networks. (100 mb/s) DGLPB ATMworks 350 network adapter that connects PCI systems to ATM local area networks. Version 7.1-1H1 minimum. (155 mb/s-OC3) DGLPA ATMworks 351 network adapter that connects PCI systems to ATM local area networks. Version 7.1-1H1 minimum. (155 mb/s-OC3) DAPBA FORE Systems HE155 network adapter that connects PCI systems to ATM local area networks. Version 7.1-1H1 minimum. (155 mb/s-OC3) DAPCA FORE Systems HE622 network adapter that connects PCI systems to ATM local area networks. Version 7.1-1H1 minimum. (622 mb/s-OC12) DE205 A network adapter that connects ISA/EISA systems to both the Ethernet and IEEE 802.3 local area networks. (Version 6.2-1H2 minimum support or Version 6.2 with AXPLAN01_062 remedial kit.) (10 mb/s) 148 DE422 A network adapter that connects EISA systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DE425 A high-performance network adapter that connects EISA systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DE434 A high-performance network adapter that connects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DE435 A network adapter that connects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DE436 A quad channel network adapter that connects PCI sys- tems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DE450 A network adapter that connects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DE500- A network adapter that connects PCI systems to both the AA Ethernet and IEEE 802.3 local area networks. (Version 6.2-1H3 minimum support.) (10 or 100 mb/s) DE500- A network adapter that connects PCI systems to both the BA Ethernet and IEEE 802.3 local area networks. (Version 6.2-1H3 minimum support.) (10 or 100 mb/s) DE504- A quad channel network adapter that connects PCI sys- BA tems to both the Ethernet and IEEE 802.3 local area networks. (Version 7.1-1H1 minimum support.) (10 or 100 mb/s) DE500- A network adapter that connects PCI systems to both the FA Ethernet and IEEE 802.3 local area networks. (Version 7.1-1H1 minimum support.) (100 mb/s) DE500- A network adapter that connects PCI systems to both the XA Ethernet and IEEE 802.3 local area networks. (Version 6.2-1H2 minimum support.) (10 or 100 mb/s) 149 DE600- A network adapter that connects PCI systems to both the AA Ethernet and IEEE 802.3 local area networks. (Version 7.1-2 minimum support.) (10 or 100 mb/s) DE600- A network adapter that connects PCI systems to both the FA Ethernet and IEEE 802.3 local area networks. (Version 7.1-2 minimum support.) (100 mb/s) DE602- A dual channel network adapter that connects PCI sys- AA, BB, tems to both the Ethernet and IEEE 802.3 local area TA networks. (Version 7.1-2 minimum support.) (10 or 100 mb/s) DEGPA- A network adapter that connects PCI systems to both the SA Ethernet and IEEE 802.2 local area networks. (Version 7.1-2 minimum support.) (1000 mb/s) DEGPA- A network adapter that connects PCI systems to both the TA Ethernet and IEEE 802.2 local area networks. (Version 7.1-2 minimum support.) (10, 100, or 1000 mb/s) DEGXA- A network adapter that connects PCI systems to both the SA Ethernet and IEEE 802.2 local area networks. (Version 7.2-2 minimum support.) (10, 100, or 1000 mb/s) DEGXA- A network adapter that connects PCI systems to both the TA Ethernet and IEEE 802.2 local area networks. (Version 7.2-2 minimum support.) (10, 100, or 1000 mb/s) DW300 A network adapter that connects the EISA bus to a Token Ring local area network. (4 or 16 mb/s) PBXNP- A network adapter that connects PCI systems to a To- DA ken Ring local area network. (Version 6.2-1H3 minimum support.) (4 or 16 mb/s) PBXNP- A network adapter that connects PCI systems to a To- AA ken Ring local area network. (Version 6.2-1H3 minimum support.) (4 or 16 mb/s) DETRA A network adapter that connects the TURBOchannel sys- tems to a Token Ring local area network. (4 or 16 mb/s) 150 PB2CA- A network adapter that connects AA EISA systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) LAN Options (VAX Only) DEUNA A network adapter that connects UNIBUS systems to both Ethernet and IEEE 802.3 local area networks. (10 mb/s) DELUA A network adapter that connects UNIBUS systems to both the Ethernet to IEEE 802.3 local area networks. The minimum revision required is F1. (10 mb/s) DEBNA A network adapter that connects VAXBI systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DEBNI A network adapter that connects VAXBI systems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DESVA An embedded network adapter that connects VAX sys- tems to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DEQNA A network adapter that connects Q-bus systems to both the Ethernet and IEEE 802.3 local area networks. The minimum revision level required is K3. Supported for application use only. Not supported beyond Version 5.4-3. (10 mb/s) DELQA A network adapter that connects Q-bus systems to both the Ethernet and IEEE 802.3 local area networks. This is the replacement for DEQNA. The minimum revision level required is C3. (10 mb/s) DESQA A network adapter that connects Q-bus for S-BOX config- urations to both the Ethernet and IEEE 802.3 local area networks. (10 mb/s) DEFQA A network adapter that connects Q-bus systems to ANSI FDDI local area networks. (100 mb/s) 151 DGLTA- ATMworks 750 network adapter that connects TurboChannel FA systems to local area networks. (OC3) KFE52 Ethernet adapter for the VAXft 3000. Minimum of two adapters per system providing redundant connection to the Ethernet and the DSSI buses. CI Options (Alpha Only) CIPCA Native CI adapter for PCI AlphaServer systems with one CI port. (Alpha only-Version 6.2-1H2 minimum support) CIXCD-AC Native CI adapter for Alpha XMI systems. (Minimum microcode version Rev 1.0 is required.) CI Options (VAX Only) VAXcluster software can support multiple CI adapters per sys- tem. Refer to the VAXcluster Software Product Description (SPD 29.78.xx) for the supported configurations. CIBCI CI adapter for VAXBI systems. (Minimum microcode ver- sion REV 8.7 is required.) CIBCA- Native CI adapter for VAXBI systems. (Minimum microcode AA version REV 7.5 is required.) CIBCA- Native CI adapter for VAXBI systems. (Minimum microcode BA version REV 5.2 is required.) CIPCI CIXCD- Native CI adapter for VAX 9xxx XMI systems. (Minimum AA microcode version REV 1.0 is required.) CIXCD- Native CI adapter for VAX 6xxx XMI systems. (Minimum AB microcode version REV 1.0 is required.) Memory Channel Options (Alpha Only) CCMAA-AA PCI-based Memory Channel Controller CCMAA-BA PCI-based Memory Channel Controller 152 CCMHA-AA Memory Channel Hub With 4 Line Cards CCMLA-AA Memory Channel Line Card for use with Memory Channel Hub(CCMHA-AA) CCMAB-AA PCI-based Memory Channel 2 Controller CCMHB-AA Memory Channel 2 Hub with 4 Line Cards CCMLB-AA Memory Channel 2 Line Card for use with Memory Chan- nel 2 Hub (CCMHB-AA) Miscellaneous PC4XD-AA Parallel/serial port adapter. PMTCE TURBOchannel extender. Miscellaneous (VAX Only) CR11 Card reader. One CR11 card reader is supported per system. (UNIBUS) DRV11- General-purpose DMA interface. (Q-bus) WA DR11-W General-purpose, high-speed DMA interface - one DR11-W interface supported per UNIBUS. DR750 High-performance, general-purpose interface for the VAX-11/750. One DR750 interface is supported per sys- tem. This device cannot be used in conjunction with the CI750. DR780 High-performance, general-purpose interface for the VAX-11/780 and VAX-11/785. One DR780 interface is sup- ported per system. On the VAX 8600 and VAX 8650 as many as four per system are permitted provided that the M8297-YA is used. DWBUA XMI to UNIBUS adapter. DWMBA XMI to BI adapter; also the adapter used to connect the XMI to VAX expander cabinet. DWMVA XMI to VME adapter. 153 FP86-AA Floating point accelerator for the VAX 8600 and VAX 8650 systems. FV64A Vector processing option for the VAX 6000-400. H7112 Memory battery backup for VAX 8600 and VAX 8650 sys- tems. This is required for power-fail/recovery. RH780 MASSBUS controller for the VAX 8600 and VAX 8650 sys- tems. SBI System backplane interconnect and I/O bus for the VAX 8600 and VAX 8650 systems. VS40X 4-plane graphics coprocessor. WS01X VAXstation 3100 SPX graphics option. Abbreviations APMP Adaptive Partitioned Multi-Processing ATA-3 AT Attachment, Version 3 COM Component Object Model DLT Digital Linear Tape DSSI DIGITAL Storage Systems Interconnect EISA Extended Industry Standard Interconnect FDDI Fiber Distributed Data Interface FSE Fast Single Ended (SCSI) FWD Fast-Wide Differential (SCSI) IDE Integrated Device (or Drive) Electronics IEEE Institute of Electrical and Electronics Engineers I80277 Intel 82077 PC Compatible Floppy Interface MSCP Mass Storage Control Protocol NCS National Character Set PCI Peripheral Component Interconnect QIC Quarter Inch Cartridge RAID Redundant Array of Independent Disks RMC Remote Procedure Call 154 RMS Record Management Services SDI Standard Drive Interface SMP Symmetric Multiprocessing STI Standard Tape Interface TFF Terminal Fallback Facility TIE Translated Image Environment TMSCP Tape Mass Storage Control Protocol VLM Very Large Memory VVIEF VAX Vector Instruction Emulation Facility XMI Extended Memory Interconnect SOFTWARE WARRANTY Warranty for this software product is provided by HP with the purchase of a license for the products as defined in the Software Warranty Addendum to this SPD. The previous information is valid at time of release. Please con- tact your local HP office for the most up-to-date information. © 2003 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without no- tice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such prod- ucts and services. Nothing herein should be construed as consti- tuting an additional warranty. HP shall not be liable for techni- cal or editorial errors or omissions contained herein. Proprietary 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. 155 Adobe[R], Adobe[R] Acrobat[R], and Adobe[R] PostScript[R] are trademarks of Adobe Systems Incorporated. Intel[R] and Pen- tium[R] are trademarks or registered trademarks of Intel Corpo- ration or its subsidiaries in the United States and other coun- tries. Java[TM] is a U.S. trademark of Sun Microsystems, Inc. Microsoft[R], Windows[R], and Windows NT[R] are U.S. registered trademarks of Microsoft Corporation. UNIX[R] is a registered trademark of The OpenGroup. 156 157