      Software Product  Description   C ___________________________________________________________________   F PRODUCT NAME:  Compaq OpenVMS Operating System for Alpha and VAX, Ver- sion 7.3 SPD 25.01.63   Note:   C This SPD describes Compaq OpenVMS Operating System software for the F Alpha and VAX computer family. Except where explicitly noted, the fea-D tures described in this SPD apply equally to both Alpha and VAX sys-F tems. OpenVMS Alpha and OpenVMS VAX operating system licenses and partC numbers are architecture specific. Please refer to the Ordering In- 2 formation section of this SPD for further details.   DESCRIPTION   E OpenVMS is a general-purpose, multiuser operating system that runs in D both production and development environments. OpenVMS Alpha supportsC Compaq Computer Corporation's Alpha series computers, while OpenVMS D VAX supports VAX, MicroVAX, VAXstation, and VAXserver series comput-C ers. OpenVMS software supports industry standards, facilitating ap- D plication portability and interoperability. OpenVMS provides symmet-C ric multiprocessing (SMP) support for multiprocessing Alpha and VAX D systems. The OpenVMS Alpha operating system provides support for 64-: bit virtual memory addressing and Very Large Memory (VLM).  C The OpenVMS operating system can be tuned to perform well in a wide I variety of environments. This includes combinations of compute-intensive, D I/O-intensive, client/server, real-time, and other environments. Ac-H tual system performance depends on the type of computer, available phys-D ical memory, and the number and type of active disk and tape drives.    C                                                          April 2001        H The OpenVMS operating system has well-integrated networking, distributedF computing, client/server, multiprocessing, and windowing capabilities.D It contains extensive features that promote ease-of-use, improve the> productivity of programmers, and facilitate system management.  8 OpenVMS Version 7.3 provides the following new features:  D o  Improved disaster tolerant capabilities with ATM and Gigabit Eth-E    ernet as cluster interconnects because of their inherent high per- +    formance and long distance capabilities.   D o  Greater system availability during backups with faster reintegra-'    tion of shadow members after copies.   B o  Enhanced OpenVMS support for the latest ENSA Storage offerings.  D o  Greater serviceability for the AlphaServer GS160/320 systems with    CPU Online Replace.  D o  Substantial application performance benefits can be realized with    the new Extended File Cache.   D o  Improved cluster, SMP and system performance through enhancementsD    to RMS and the clusterwide Lock Manager, as well as FastPath sup-9    port for Fibre Channel and SCSI storage architectures.   D o  OpenVMS adds industry standard Kerberos V5 security, which allowsE    VMS applications to communicate and authenticate with Windows 2000     domains and UNIX platforms.  C o  OpenVMS Intrusion Detection expands to be cluster-wide, reducing     chances of system break-ins.   C o  Enterprise Capacity and Performance (ECP) Data Collector and ECP C    Performance Analyzer are now included with the purchase of Open-     VMS Version 7.3.   I o  The OpenVMS license is expanded to include all of these new e-Business     technologies:  E -  Compaq Secure Web Server Version 1.0-1 for OpenVMS Alpha (based on     Apache).   ! -  Compaq COM for OpenVMS (Alpha)   "                                  2       C -  Extensible Markup Language (XML) Technology (XML parser and XSLT     stylesheet processor)  B -  Java 2 SDK, Standard Edition, Version 1.2.2-3 for OpenVMS Alpha  G -  Attunity Connect "On Platform" Package (native JDBC driver included)   > -  Reliable Transaction Router (RTR) for OpenVMS Alpha and VAX  = -  Compaq OpenVMS Enterprise Directory for e-Business (X.500)    -  Compaq BridgeWorks   D Now, with Version 2.0 of Compaq DECprint Supervisor (DCPS) for Open-D VMS, the right to use all DCPS products (-Base, -Open, and -Plus) isD bundled with the OpenVMS Operating System license. Media, documenta-' tion, and services are sold separately.   H Refer to the OpenVMS Version 7.3 New Features and Documentation OverviewD manual and the OpenVMS Version 7.3 Release Notes for further detailsB on the new enhancements, features, and functions for this release.   USER ENVIRONMENT  D Users can access the OpenVMS software by using the English-like DIG-E ITAL Command Language (DCL), the command language for OpenVMS that is D supplied with the system. DCL commands provide information about theD system and initiate system utilities and user programs. DCL commandsF take the form of a command name followed by parameters and qualifiers.E With the DCL command PIPE, individual DCL operations can be connected D using a UNIX like command syntax. OpenVMS prompts users to enter re-7 quired DCL parameters, making it easy for novice users.   E Users can enter DCL commands at a terminal or include them in command E procedures. These command procedures can be run interactively or sub- - mitted to a batch queue for later processing.   E Information on DCL and OpenVMS utilities is available on line through D the OpenVMS Help system. Online help includes summary information on  all aspects of system operation.  "                                  3       E The following tools and utilities are integrated into the OpenVMS op-  erating system.    Text Processing   G The Extensible Versatile Editor (EVE), one of several text editors sup- D plied by Compaq, is the default editor for OpenVMS. EVE allows usersG to insert, change, and delete text quickly. Written in the DIGITAL Text F Processing Utility (DECTPU) language, EVE is a full-screen editor thatF allows users to scroll through text on a terminal screen. EVE providesE an EDT-style keypad, allowing EDT users to move easily to EVE. EDT is C also supported on OpenVMS Alpha Version 7.3 and OpenVMS VAX Version  7.3.   Mail Utility  C The Mail utility allows users to send messages to any other user on H the system. Multinode operation is available if a DECnet or TCP/IP prod-D uct is installed and licensed on each participating node on the net- work.    Command-Level Programming   F Command-level programming allows users to create special files, calledE command procedures, that contain a series of DCL commands. When users E execute a command procedure, the system processes the commands in the D 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  D o  Communicate interactively with the user invoking the command pro-	    cedure   @ o  Perform conditional (IF-THEN-ELSE) and branching (GOTO) logic   o  Handle error conditions   User Environment Tailoring  "                                  4       E Users can customize the computing environment with login command pro- F cedures, shorthand commands, binding of commands to function keys, and command recall and editing.     Terminal Fallback Facility (TFF)  C This facility allows Compaq 7-bit terminals to input and output the D Compaq Multinational character set (MCS). Specific tables allow con-D version for a number of different 7-bit National Replacement Charac-G ter sets to MCS, such as French, German, Spanish, and Swedish. TFF also C allows character composition on terminals that do not have the com- 	 pose key.   $ National Character Set (NCS) Utility  H This utility allows users to define non-ASCII string collating sequencesD and to define conversion functions. Conversion functions use conver-F sion algorithms to change an input string; for example, to change low-C ercase characters to uppercase. NCS also allows OpenVMS Record Man- H agement Services (RMS) indexed files to be collated using user-specified collating sequences.   PROGRAM DEVELOPMENT ENVIRONMENT   F OpenVMS includes a comprehensive set of tools for developing programs,G including: run-time libraries (RTLs), a linker, a librarian, and a sym- D bolic debugger. The assembly-level VAX MACRO-32 language is suppliedE with OpenVMS VAX. In addition, the Java 2 SDK provides an environment_F in which to develop and deploy Java applications on OpenVMS Alpha. The8 following tools are available to the OpenVMS programmer.   Java 2 Software Development Kit   D The Java 2 SDK is a set of building blocks containing basic develop-- ment tools and a rich set of class libraries.i  % Language and Run-Time Library Support   + OpenVMS includes several RTLs that provide:t   o  String manipulation  "                                  5 e      o  Parallel processing support   o  I/O routines    o  I/O conversionl  ' o  Terminal-independent screen handlingp  $ o  Date and time formatting routines  ) o  Highly accurate mathematical functionsi  # o  Signaling and condition handlingq  " o  Other general-purpose functions  D With OpenVMS VAX, these routines can be called from programs writtenG in such languages as VAX MACRO-32, Compaq Ada, Compaq BASIC, VAX BLISS-,F 32 Implementation Language, VAX C, Compaq C, Compaq C++, Compaq COBOL,7 VAX DIBOL, Compaq Fortran, Compaq Pascal, and VAX PL/I.u  D With OpenVMS Alpha, these routines can be called from programs writ-C ten in such languages as MACRO-32, MACRO-64, Compaq Ada, Compaq BA-rD SIC, Compaq C, Compaq C++, Compaq COBOL, Compaq Fortran, Compaq Pas- cal, Java, and Compaq PL/I.f  D Also included in OpenVMS Alpha are language-support libraries. WhileC each language is different, all provide support for sequential filesE I/O, and most support direct and indexed file I/O. Language RTLs alsolF provide support for I/O formatting, error handling, and in Compaq For-H tran, the ability to read unformatted files that contain data from other vendors.  E RTLs are provided to support translated images created from user-modetF images built on OpenVMS VAX Version 4.0 through Version 5.5-2. Depend-F ing on the method used to create the VAX image, these RTLs can be use-C ful for images built on later versions of OpenVMS VAX, which do notsA use features that were developed since OpenVMS VAX Version 5.5-2.r    "                                  6    -  F Translated image RTLs are used to support a few architectural featuresE that differ between VAX and Alpha systems, such as VAX D-float and H-aC float. They also support programs converted to run on Alpha systemsrD before native Alpha compilers were available for particular program- ming languages.   G Many Compaq languages adhere to the common calling standard. This meansCF that routines written in any of these languages can directly call rou-D tines written in any other language. Development of applications us-5 ing multiple languages is simple and straightforward.   D All user-accessible routines in the RTLs follow the OpenVMS Alpha orD OpenVMS VAX calling standard and condition-handling conventions, and+ most are contained within shareable images.   D At a lower level, programs can call system services directly for se-F curity, event flag, asynchronous system trap, logical name, record andF file I/O, process control, timer, time conversion, condition handling,F lock management, and memory management. Again, system services use theD OpenVMS VAX or OpenVMS Alpha calling standard and condition-handling conventions.  E OpenVMS supports the execution of user-mode images created on earliereE versions of OpenVMS. Typically, recompiling and relinking are not re-s quired.    MACRO Compiler (Alpha Only)   E For migration purposes, the MACRO compiler is supplied with the Open-  VMS Alpha software.   F With minor modifications, VAX MACRO-32 sources can be compiled for ex- ecution on Alpha.o   Compaq POSIX Threads Library  C OpenVMS includes a user-mode, multithreading capability called Com-tH paq POSIX Threads Library. Compaq POSIX Threads Library provides a POSIXH 1003.1-1996 standard style threads interface. Additionally, Compaq POSIX  "                                  7    d  C Threads Library provides an interface that is the OpenVMS implemen-fD tation of Distributed Computing Environment (DCE) threads as defined& by the Open Software Foundation (OSF).  C Compaq POSIX Threads Library is a library of run-time routines thataE allows the user to create multiple threads of execution within a sin-tC gle address space. With Compaq POSIX Threads Library Kernel ThreadsrC features enabled, Compaq POSIX Threads Library provides for concur-iD rent processing across all CPUs in a symmetric multiprocessor systemE by allowing a multithreaded application to have a thread executing onaD every CPU. On an asymmetric (e.g. NUMA) system, a single process canD have a thread executing on all processors in the process's home RAD.C Multithreading allows computation activity to overlap I/O activity.lF Synchronization elements, such as mutexes and condition variables, areE provided to help ensure that shared resources are accessed correctly.pE For scheduling and prioritizing threads, Compaq POSIX Threads Library F provides multiple scheduling policies. For debugging multithreaded ap-D plications, Compaq POSIX Threads Library is supported by the OpenVMSD Debugger. Compaq POSIX Threads Library also provides Thread Indepen-C dent Services (TIS), which assist in the development of thread-safeo APIs.h   Visual Threads  D Visual Threads is a new tool available with OpenVMS Version 7.3 thatC lets you analyze your multithreaded applications. You can use it towF debug potential thread-related logic problems, even those hard-to-findG problems that only occur due to slight timing differences. You can alsooC use Visual Threads to pinpoint bottlenecks and performance problemsfC by using its rule-based analysis, statistics capabilities and visu-k alization techniques.T  I Visual Threads can be used with any application that uses a POSIX threadsh4 API (POSIX, DCE, or CMA API), or is written in Java.  . Visual Threads features include the following:  C o  Detects violation conditions based on the application of partic-lD    ular rules in your application. Several predefined rules look forC    deadlock conditions, programming errors, and performance issues.   "                                  8 i     D o  Lets you use templates to define your own rules to specify crite-     ria for violation conditions.  C o  Records events to a trace file so that you can play back and an-r    alyze them later.  G o  Dynamically displays events as they occur, with controls for search-     ing and filtering.c  G o  Suspends execution of the application when it detects violation con-tF    ditions. You can choose from several options at this point, includ-D    ing invoking the debugger in the appropriate context for your ap-
    plication.   E o  Dynamically monitors multithreading objects (threads, mutexes, and     so on) in real time.n  D o  Provides easy access to object-level statistics and current stateD    information, including use of resources (for example, the mutexes    a particular thread holds).  C o  Automatic analysis of lock contention and lock granularity, sta-t0    tistical hotspots, and processor utilization.  F o  Visualizes thread state over time, level of contention, and object-    level usage statistics.   Librarian Utilityi  E The Librarian utility permits storage of object modules, image files,tE macros, help text, or any general record-oriented information in cen-aE tral, easily accessible files. Object module and image file librarieswD are searched by the linker when the linker finds a reference it can-I not resolve in one of its input files. Alpha macro libraries are searchedsC by the MACRO-32 compiler and MACRO-64 assembler when either finds a E macro name that is not defined in the input file. VAX macro librariesiG are searched by the MACRO-32 assembler when the assembler finds a macroa! that is not defined in the input.o  	 HypersortM  "                                  9 d  d  C Hypersort is a portable library of user-callable routines that pro-G= vide a high-performance sorting capability for Alpha systems.e   Traceback Facility  F When an application is compiled and linked with traceback information,D the Traceback facility translates stack frame addresses into routineC names and line numbers and displays a symbolic traceback whenever ad) runtime error occurs in that application.    Debugger  E The OpenVMS Debugger allows users to trace program execution, as wellOC as display and modify register contents using the same symbols thatS are present in the source code.n  E The debugger contains a Heap Analyzer feature that displays a graphic : view of memory allocations and deallocations in real time.   Alpha System-Code Debugger  D The OpenVMS Alpha System-Code Debugger is a kernel code debugger. ItD allows a system code developer to trace the execution of nonpageableG system code at any Interrupt Priority Level (IPL). Based on the OpenVMStD Alpha Debugger, the system-code debugger uses the same interface and most of the same command set.   " System Dump Analyzer (SDA) Utility  E In the event of a system failure, OpenVMS writes the contents of mem-sE ory to a preallocated dump file. This dump file can later be analyzed2F using System Dump Analyzer (SDA). System dumps can either be full mem-H ory dumps, where all memory is written, or selective memory dumps, whereC only portions of memory in use at the time of the system failure isgD written. The dump file can be located on any locally connected disk.D On Alpha only, dump compression allows both full and selective dumpsD to be written to smaller files than required for uncompressed dumps.D Full memory dumps, if not compressed, require a dump file big enoughD to hold all memory. Selective memory dumps write as much of the mem-C ory in use at the time of the system failure that will fit into the 
 dump file.  "                                 10 t      Spinlock Tracing Utility  D The Spinlock Tracing Utility provides a mechanism for characterizingD spinlock usage and can collect performance data for a given spinlock on a per-CPU basis.   
 Process Dumps   D When an application fails, a copy of its registers and memory can beD written to a data file, which can be examined using the ANALYZE PRO-F CESS utility. This utility uses the same interface and commands as theE OpenVMS Debugger to allow registers and memory to be examined. On Al- F pha only, another process can initiate the writing of the memory dump.   RMS File Utilities  C Record Management Services (RMS) file utilities allow users to ana-mD lyze the internal structure of an RMS file and tune the I/O, memory,D space and performance parameters of the file. The RMS file utilitiesC can also be used to create, load, and reclaim space in an RMS file.gF Refer to the Operating System Environment section of this SPD for more information on RMS.s   File Differences Utility  G This utility compares the contents of two files and lists those recordss that do not match.  / Translated Image Environment (TIE) (Alpha Only)n  D OpenVMS Alpha provides an array of services that allow the operationD of programs which have undergone binary translation from OpenVMS VAXC images. These programs perform virtually all user-mode functions ondE OpenVMS Alpha and operate in combination with other programs (images)lC that have been translated from OpenVMS VAX or have been built usinguC native compilers on OpenVMS Alpha. Without requiring special sourceaC code, the TIE resolves differences between the VAX and Alpha archi-mE tectures, including floating-point registers, condition codes, excep-nD tion handling, and ASTs. The TIE included with OpenVMS Alpha can run+ images that have been translated elsewhere.   "                                 11 a      SYSTEM MANAGEMENT ENVIRONMENT   E OpenVMS provides a variety of features that aid the system manager inSE configuring and maintaining an optimal system. The following featuresb! are available to system managers.d  ' Compaq Availability Manager Version 1.4v  F Compaq Availability Manager is a system management tool that, from ei-D ther an OpenVMS Alpha or a Windows 2000 node, enables you to monitorG one or more OpenVMS nodes on an extended local area network (LAN). ThisiF tool helps system managers and analysts target a specific node or pro-D cess for detailed analysis. The Availability Manager collects systemC and process data from multiple OpenVMS nodes simultaneously. It an-sC alyzes the data and displays the output using a native Java GUI. Itr, is included in the OpenVMS distribution kit.  C The Availability Manager tool evolved from the OpenVMS only DECamdscH product and its Motif graphical user interface (GUI). Because the Avail-F ability Manager Data Analyzer requires a run-time environment, it doesE not run on OpenVMS VAX, which does not support Java. To perform real- > time system monitoring on VAX systems, one should use DECamds.  F Installation of Java Version 1.1.8 or later is required for the Avail-D ability Manager Version 1.4 client on an OpenVMS system. Compaq rec-F ommends using, at a minimum, the following hardware configuration: 500C MHz Alpha processor with 128 MB of memory. The Availability Manager D Version 1.4 kit for OpenVMS includes the Data Analyzer and Data Col- lector:T  E o  The Java Data Analyzer can be installed only on OpenVMS Alpha Ver-s4    sions 7.1, 7.1-2, 7.2, 7.2-1, and 7.2-1 variants.  D o  The Data Collector can be installed on OpenVMS VAX and Alpha Ver-9    sions 6.2, 7.1, 7.1-2, 7.2, 7.2-1, and 7.2-1 variants.n  E On a Windows system, Compaq recommends using, at a minimum, either ofo& the following hardware configurations:  C o  Windows NT or 2000-300 MHz Intel Pentium processor with 96 MB ofc	    memoryl  "                                 12 s  i  ; o  Windows NT-500 MHz Alpha processor with 128 MB of memory   D You can install the Availability Manager Data Analyzer on any systemC running Windows NT 4.0 SP3 or later or on Windows 2000. Please noteoF that you must reinstall Availability Manager Version 1.4 after upgrad- ing to Windows 2000.   DECamds Version 7.2-1B  D DECamds version 7.2-1B is available on the OpenVMS distribution kit.F DECamds is a separately installable, real time, high performance, mul-H tisystem monitoring utility. It is supported on any system running Open-E VMS Version 7.1 or higher. With OpenVMS Version 7.1, the right to use F DECamds was included under the terms and conditions of the OpenVMS op-G erating system base license for both Alpha and VAX. DECamds is the pre-b7 decessor of the newer application Availability Manager.l  C DECamds provides system resource monitoring, investigation aid, andiF correction capability. This enables system managers to proactively andF effectively manage multiple systems from a centralized DECwindows dis-F play. DECamds software includes an OpenVMS device driver, which is in-C stalled on every node on the LAN that is to be monitored. The soft-cE ware includes a Motif GUI application that allows a system manager toyD perform monitoring functions. The Motif application can be installedF on any OpenVMS Alpha or VAX workstation. DECamds is currently in main-C tenance mode. All new system management functionality requested forn= DECamds will be directed to our Availability Manager product..  0 Compaq Management Agents for OpenVMS Version 2.1  I Compaq Management Agents for OpenVMS Version 2.1 consists of a web serverhD for system management, with management agents that allow you to com-C municate with devices on their OpenVMS systems over the Internet oraE intranet. Compaq Management Agents for OpenVMS utilizes Web-based en-wE terprise management (WBEM) architecture. This is an architecture that E allows one to use a web browser to monitor many devices that are con-eF nected to a network. Devices can be computer systems, networked print-C ers, or network components such as router. WBEM uses a three-tierede    "                                 13 w     F architecture that includes a management server, devices managed by web agents, and a web browser.  G Compaq Management Agents for OpenVMS use SNMP and TCP/IP protocols thatrF allow the "management server" to communicate with OpenVMS devices. TheD management agents use common web-enabling components to provide reg-G istration, discovery, HTTP communications, and a home page for the man-tD aged devices. The management agents can send information directly toC the "management server" or they can create an HTML file to communi-a cate directly with a browser.M  C Compaq Management Agents for OpenVMS utilize Compaq Insight ManageryC XE on an NT server as the "management server/application." With thenE introduction of Compaq Insight Manager XE on an NT server, management I of all your Compaq platforms inclusive of OpenVMS from a single NT servereC becomes a possibility. Compaq Insight Manager XE, which is an exam-dG ple of a "management server/application," is a web-based interface thattC enables you to look across a heterogeneous computing services envi-iF ronment and access information about devices connected to the network.G Using the Insight Manager XE, one can obtain information about the con- G figuration of OpenVMS systems and their components or peripherals. Com-pC paq Management Agents for OpenVMS is an example of a Compaq InsightTF Manager XE web agent. Management Agents for OpenVMS provides the meansF of communication between OpenVMS devices and the web browser. The Com-C paq Insight Manager XE "management server" provides a single refer-eF ence point for data from all devices. The "management server" uses itsC connection with the web browser to display device data to the user.   & OpenVMS Management Station Version 3.0  D OpenVMS Management Station is a powerful, Microsoft Windows NT basedF management tool for system managers and others who perform system man-E agement tasks on OpenVMS systems. OpenVMS Management Station featureseC a powerful, intuitive user interface. System managers and help desk.G staff no longer need to remember complicated DCL syntax or command pro-yC cedures to manage their OpenVMS systems. OpenVMS Management Stationi$ makes system management much easier.      "                                 14 C  b  E Three functional areas are now implemented in OpenVMS Management Sta-sD tion: user account management, printer queue management, and storageC configuration management. For user account management, OpenVMS Man-rF agement Station supports account creation, modification, and deletion,G as well as renaming accounts and displaying account attributes. PrinteriD queue management makes it possible for system managers to manage allF printers, print queues, and jobs in their environment using a central-G ized Windows GUI. This includes monitoring one or more printers, addingeE or removing printers, and their associated queues, examining and mod-oD ifying queue and printer attributes, and requeuing or deleting jobs.  C The current release of OpenVMS Management Station adds storage man-DE agement support. OpenVMS Management Station now makes it easy for onenD to manage their disk storage devices across multiple OpenVMS ClusterH systems and OpenVMS Nodes. With OpenVMS Management Station one no longerD needs to maintain complicated command files to control their storageE environment. One can create, delete, and manage storage from an easy-eD to-use Windows interface. It provides a persistent database that canC automatically determine and configure your system's storage config-  uration at system startup.  C OpenVMS Management Station is now based on the Microsoft Management F Console (MMC). The Microsoft Management Console provides a common man-C agement framework for various administration programs. OpenVMS Man-hD agement Station is implemented as an MMC snap-in and includes all of the MMC components you need.   Features include:   D o  Storage Configuration Management-You can create, delete, and man-E    age a disk volume under one interface. Wizards make it easy to addo8    systems to be managed, create a volume, and so forth.  G o  Configuration Control Over Reboots- If you allow it to, OpenVMS Man-eC    agement Station preserves the disk configuration across reboots.tF    OpenVMS Management Station can mount and maintain your storage con-C    figuration without intervention. And, OpenVMS Management Station G    mounts volumes much faster than is possible with DCL or command pro-e'    cedures, so performance is enhanced.l  "                                 15 y  m  E o  Coexistence with Established Environment-You do not have to changelE    your existing DCL command procedures if you don't want to. You caniC    use the display capabilities of OpenVMS Management Station with-tF    out having to use the automated mount feature. In this way, you canF    give OpenVMS Management Station as little or as much control as you    are comfortable with.  E o  Remote Management Supported-You can use OpenVMS Management StationTG    to remotely manage your OpenVMS systems. Once you establish a TCP/IPEF    RAS connection, you can then use OpenVMS Management Station to man-5    age your OpenVMS systems from home or on the road.V   Note:.  E The version of MMC included in this baselevel requires files providedrE by Microsoft Internet Explorer. Version 3.02 or later of Internet Ex- D plorer must be present on the system. The OpenVMS Management StationH client supports only TCP/IP connections for primary servers, so at leastE one OpenVMS system must be running TCP/IP. If you are running Version.C 6.2 of OpenVMS and plan to manage shadow volumes, remedial kits areeD required. Additional TCP/IP stacks for OpenVMS have not been tested.E However, TCP/IP stacks that are 100% compliant with the QIO interface E for Compaq TCP/IP Services for OpenVMS should also work. Contact youre< TCP/IP vendor for additional information and support issues.  E Enterprise Capacity and Performance (ECP) Data Collector and ECP Per-i formance Analyzer   C Beginning with the release of OpenVMS Version 7.3, ECP Data Collec-mF tor and ECP Performance Analyzer Version 5.4, engineered and supportedD by Compaq, are licensed with the OpenVMS operating system and avail-4 able from the OpenVMS System Management web page at:  % http://www.openvms.compaq.com/openvmsO /system_management.html   E ECP Data Collector and ECP Performance Analyzer will be licensed withiF the OpenVMS Alpha and VAX Operating System Version 6.2 to Version 7.3.    "                                 16 s     C ECP Data Collector is a highly efficient, detailed performance dataiE collector and ECP Performance Analyze provides graphic historical re-VF porting of OpenVMS performance parameters. Satisfying the needs of En-F terprise Management, ECP Data Collector also contains an API that pro-E vides an interface for the access of collected performance data. ThiscF interface converts the contents of the .CPC data file generated by theD data collector into a formatted, comma-separated ASCII file that can= then be used for performance analysis and reporting programs.n    The ECP Data Collector provides:  H o  Robust data collection set-It collects more system metrics than other>    vendors (for example, over 250 VMS performance parameters).  G o  Flexible data collection-The sampling rate of data can be tuned down     to sub-second intervals.n  E o  Low overhead-Audited production systems now running have routinelyr=    shown that the collector has less than 1.5% impact on CPU.   & The ECP Performance Analyzer provides:  - o  Native OpenVMS product running under Motifn  2 o  Viewing of performance data in graphical format  . o  Analyzed data including CPU, Memory and I/O   o  User-selected sampling rate  E Software Support Service for these products is sold separately and isgF available on an incremental basis. Please contact your Compaq Services# representative for further details.i  " Class Scheduler for CPU Scheduling  C With OpenVMS Version 7.3, a new SYSMAN-based interface for definingoH and controlling scheduling classes has been added. This new class sched-D uler for both Alpha and VAX systems allows you to designate the per-F centage of CPU time that a system's users may receive by placing users into scheduling classes.  "                                 17        Batch and Print Queuing System  D OpenVMS provides an extensive batch and print capability that allowsG the creation of queues and the setup of spooled devices to process non-aE interactive workloads in parallel with timesharing or real-time jobs.i  C The OpenVMS batch and print operations support two types of queues:TC generic queues and execution queues. A generic queue is an interme-mE diate queue that holds a job until an appropriate execution queue be-vJ comes available to initiate the job. An execution queue is a queue through< which the job (either print or batch) is actually processed.  G The system queues batch jobs for execution. The system manager can reg-oC ulate the number of queues and the number of streams per queue (theaA number of batch jobs in the queue that can execute concurrently).e  F Both generic and execution batch queues can have different attributes,D such as the maximum CPU time permitted, working set size, and prior-E ity. Facilities are provided for starting and stopping queues and foraH starting and stopping jobs in a queue. Because multiple execution queuesE can be associated with a generic queue, OpenVMS VAX enables load bal- C ancing across available CPUs in an OpenVMS Cluster system, increas-m ing overall system throughput.  E Print queues, both generic and execution, together with queue manage-eE ment facilities, provide versatile print capabilities, including sup- $ port for various print file formats.  G The maximum number of process identifiers for queuing requests is 1024.a   Accounting Utility  E For accounting purposes, OpenVMS keeps records of system resource us-sC age. These statistics include processor and memory utilization, I/O E counts, print symbiont line counts, image activation counts, and pro-uC cess termination records. The OpenVMS Accounting utility allows youd, to generate various reports using this data.   Audit Analysis Utility  "                                 18 y  m  E For security auditing purposes, OpenVMS selectively records critical, E security-relevant events in the system security audit log file. TheseaE records contain the date and time the event occurred, the identity ofgC the associated user process, and information specific to each eventtC type. This information helps the system manager maintain system se-sE curity and deter possible intruders. The OpenVMS Audit Analysis util-o: ity allows you to generate various reports from this data.   Autoconfigure/AUTOGEN Utilities   C The Autoconfigure and AUTOGEN utilities automatically configure theoF available devices in the system tables and set system parameters basedC on the peripheral and memory architecture. This eliminates the needqE for a traditional system generation process when the hardware config-q* uration is expanded or otherwise modified.  D The OpenVMS AUTOGEN command procedure sets several system parametersD automatically by detecting the devices installed in a configuration.D A feedback option allows you to generate a report of recommended pa-2 rameter settings based on previous usage patterns.   Backup Utility  G The Backup utility provides both full-volume and incremental file back-cD ups for file-structured, mounted volumes and volume sets. IndividualF files, selected directory structures, or all files on a volume set canG be backed up and restored. Files can be selected by various dates (suchrC as creation or modification) and can be backed up to magnetic tape,gF magnetic disk, or Write Once Read Many (WORM) optical disk. The BackupC utility can also be used to restore a save set or list the contentsS of a save set.  D A BACKUP API has been added for invoking backup routines from an ex- ecutable procedure.   C The Backup Manager for OpenVMS provides a screen-oriented interfaceeE to the Backup utility that assists users in performing routine backupa; operations. The Backup Manager is menu driven and provides:,    "                                 19 O     E o  Access to the save, restore, and list operations without having tot#    understand Backup command syntaxt  C o  The ability to create, modify, recall, and delete Backup Manager-5    templates that describe the Backup save operationsg  E The Backup Manager works on all supported OpenVMS configurations withrE a video terminal. It uses the Screen Management (SMG) RTL routines to F provide a window-like user interface. The software does not assume anyD privilege on the part of its user beyond access to the files and de- vices being operated upon.  $ Standalone BACKUP Utility (VAX Only)  E Standalone BACKUP provides a mechanism for system managers to back upmF and restore system disks. This utility can also be used during the in-/ stallation of the OpenVMS VAX operating system.t   Analyze Disk Structure Utility  E The Analyze Disk Structure utility compares the structure information D on a disk volume with the contents of the disk, prints the structureD information, and permits changes to that information. It can also be> used to repair errors detected in the file structure of disks.   Monitor Utilityt  C The Monitor utility enables the system manager to monitor different C classes of systemwide performance data including: process activity, D I/O activity, memory-management activity, vector-processing activityC (VAX only), and two-phase, commit-transaction activity at specifiedeD intervals. The data can be displayed as it is gathered or saved in a file for later use.m  ! License Management Facility (LMF)i  C The License Management facility allows the system manager to enable G software licenses and to determine which software products are licensed  on an OpenVMS system.o  " System Management Utility (SYSMAN)  "                                 20 o  i  E The System Management utility allows system managers to define a man-PF agement environment in which operations performed from the local Open-D VMS system can be executed on all other OpenVMS systems in the envi-G ronment. The environment can include OpenVMS Alpha and VAX systems con-eC figured in an OpenVMS Cluster or multiple systems networked through  DECnet or DECnet-Plus.  
 Operations  E OpenVMS allows for varying levels of privilege to be assigned to dif-oD ferent operators. Operators can use the OpenVMS Help Message utilityF to receive online descriptions of error messages. In addition, system-F generated messages can be routed to different terminals based on theirC interest to the console operators, tape librarians, security admin-h istrators, and system managers.e   Security   Kerberos  D Kerberos Version 1.0 for OpenVMS Alpha and OpenVMS VAX, based on MITD Kerberos Version 5 Release 1.0.5, is included on the OpenVMS VersionF 7.3 distribution media. (Kerberos documentation provided by MIT is in-; cluded on the OpenVMS documentation CD-ROM in HTML format.)m  H Kerberos is a network authentication protocol designed to provide strongG authentication for client/server applications by using secret-key cryp-R	 tography.c  D The Kerberos for OpenVMS authentication system, based upon work doneD by Massachusetts Institute of Technology (MIT), is provided in three separate components:  ' o  Key Distribution Center (KDC) server-   o  Client subsystem         "                                 21 n  g  E o  Two application-programming interfaces, one written to comply withnG    the Generic Security Service Application Programming Interface (GSS-dG    API V2) specification as defined by RFC2078. The second API presentsoK    the Kerberos interface to the users. Both APIs are delivered as sharablem    images on OpenVMS.S  D Kerberos was created by the Massachusetts Institute of Technology asC a solution to network security problems. The Kerberos protocol usesnG strong cryptography so that a client can prove its identity to a serverhF (and vice versa) across an insecure network connection. After a clientD and server have used Kerberos to prove their identity, they can alsoI encrypt all of their communications to assure privacy and data integrity.   H General information about Kerberos is available from the following World Wide Web address:   http://web.mit.edu/kerberos/www/   Per-Thread Security Profiles  D Thread-level security allows for simplified multiprofile applicationE development and improves overall performance while maintaining a higheF level of security. This feature allows each execution thread of a mul-E tithreaded process to run an independent security profile without im- > pacting the security profiles of other threads in the process.  C This feature, known as Per-thread security profiles, includes a newtD security structure, known as the Persona Security Block (PSB), whichE supersedes many process-wide structures and fields including the ARB, E JIB username and account information, PHD privilege bits, and the PCBn
 NOAUDIT cell.   C A new SYSGEN parameter, ARB_SUPPORT, has been added to allow systemuC managers to control the level by which the current security data inoC the PSB will be backported to these old privilege data cells. There G are four levels of support ranging from NONE (ARB_SUPPPORT = 0) to FULL. (ARB_SUPPORT = 3).   External Authenticationi    "                                 22 o  i  C External authentication is an optional feature that enables OpenVMSgD systems to authenticate designated users within a LAN Manager domain/ using their LAN Manager user name and password.   F If you want to enable external authentication on your system, you needF DECwindows Version 1.2-4 or later and any requirements outlined in theC Compaq Advanced Server for OpenVMS Server Installation and Configu-hE ration Guide and the Compaq PATHWORKS for OpenVMS Server Installation C and Configuration Guide. See these manuals and the OpenVMS Guide tosE System Security for detailed information about using external authen-eC tication. For additional information on Advanced Server for OpenVMSiC and PATHWORKS for OpenVMS, refer to the Associated Products sectionn of this SPD.  E Users who are externally authenticated by their LAN Manager need onlysH remember a single user name/password combination to gain access to theirC OpenVMS and LAN Manager accounts. In addition, the OpenVMS DCL com-vD mand SET PASSWORD has been enhanced to update the user's password inF the LAN Manager domain database (as well as optionally synchronize the SYSUAF password).d  C For externally authenticated users, the normal system authorizationsC database (SYSUAF.DAT) is used to construct the OpenVMS process pro-rC file (UIC, privileges, quotas, and so on) and to apply specific lo-oD gin restrictions. However, there are two key differences between ex-E ternally authenticated users and normal OpenVMS users. For externallya authenticated users:  E o  The password stored in the SYSUAF is not the password used to ver-a    ify the user at login time.  E o  The SYSUAF user name selected to be used for OpenVMS process iden-fC    tification may not be the same as the LAN Manager user name thatEG    was used to authenticate the user at login. The system manager spec-cD    ifies the LAN Manager to OpenVMS user name mapping for each user.  
 Security APIse      "                                 23 s  s  F Security APIs for intrusion detection, proxy access, and impersonationE services are available on both the Alpha and VAX platforms to provideuC better security in client/server applications. With OpenVMS VersioneC 7.3, Intrustion Detection capabilities have now been expanded to ber clusterwide.  C The Security Persona services provide the ability to support alter-aC nate security models. OpenVMS security persona services allow Open-RF VMS applications the ability to attach NT or any other Non-OpenVMS se-2 curity credentials to an OpenVMS security profile.   Government Security Ratingse  C As the following table illustrates, OpenVMS is committed to consis- 6 tently delivering rated security in our base products.  C ___________________________________________________________________eC Version_______________Rating____Evaluation_Date____________________,  $ 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        1988C ___________________________________________________________________nC +Currently_in_ITSEC_Rating_________________________________________a  C These ratings represent the National Computer Security Center vali- G dation of the design of the OpenVMS and SEVMS operating systems againstoC DoD 5200.28-STD Department of Defense Trusted Computer System Eval-mE uation Criteria. To obtain an evaluation summary, please visit the USy> NCSC at Trusted Product Evaluation Program (TPEP) homepage at:    http://www.radium.ncsc.mil/tpep/  "                                 24 c  e  F OpenVMS provides a rich set of tools to control user access to system-D controlled data structures and devices that store information. Open-D VMS employs a reference monitor concept that mediates all access at-F tempts between subjects (such as user processes) and security-relevantD system objects (such as files). OpenVMS also provides a system secu-E rity audit log file that records the results of all object access at-eE tempts. The audit log can also be used to capture information regard-w5 ing a wide variety of other security-relevant events.e  C The system manager maintains user account information in the systemfF user authorization file (SYSUAF). When creating user accounts with theE Authorize utility, the system manager assigns the privileges and quo- F tas associated with each user account. The system manager also assignsC a user name, password, and unique user identification code (UIC) to E each account. Additional identifiers can be assigned to each account,aD allowing users to belong to multiple overlapping groups or projects.C The system manager can limit account use by the time of day, day ofnC week, and type of access, such as local, remote, network, or batch.S  E To log in and gain access to the system, the user must supply a validyC user name and password. The password is encoded and does not appearnE on terminal displays. Users can change their password voluntarily, oreE the system manager can specify how frequently passwords change, alongcE with minimum password length, and the use of randomly generated pass-a words.  C OpenVMS provides a password dictionary filter that screens passwordhF choices for common words, and a user password history filter that pre-G vents users from re-using passwords that they have used within the pastVF year. In addition to these built-in filters, a site can design and in-E stall its own filter to screen passwords according to a site-specific  password policy.  C The system password hash algorithm can also be replaced with a pri-fC vate algorithm for those sites that have contractual obligations to G use specific public or private password encryption algorithms. The sys-cC tem manager can enable this feature on a per-user, per-password ba-  sis.    "                                 25 s  u  D Login security includes break-in detection, which disables terminalsE when password guessing is detected. Users retain a secure login path, D which can thwart Trojan horse attacks against local terminals. Addi-G tionally, the system manager can associate a system password with dial-eI in terminal lines to prevent the display of any operating system-specific F identification that might yield clues to possible attack methods. WhenC a user logs in, the system displays a message stating when the lastVF login for the account occurred and the number of failed attempts since the last successful login.  D Every security-relevant system object is labeled with the UIC of itsD owner along with a simple protection mask. The owner UIC consists ofF two fields: the user field and a group field. System objects also haveE a protection mask that allows read, write, execute, and delete accesscG to the object's owner, group, privileged system users, and to all otheroE users. The system manager can protect system objects with access con-sE trol lists (ACLs) that allow access to be granted or denied to a list E of individual users, groups, or identifiers. ACLs can also be used toe1 audit access attempts to critical system objects.i  @ OpenVMS applies full protection to the following system objects:   o  Capabilities (VAX only)   o  Common event flag clusterss  
 o  Devices   o  Files   o  Group global sections   o  Logical name tables   o  Batch/print queuesu   o  Resource domains    o  Security classesu   o  System global sectionse   o  Volumes (ODS-2)  "                                 26 m      o  Volumes (ODS-5)  D OpenVMS provides security attribute defaults in the form of securityD profile templates. These templates are referenced whenever a new ob-C ject is created and provide a means of associating default securityoD information with each system object class, except for files. Protec-D tion information for files is inherited from the previous version ofD an existing file, the parent directory, or the default protection of the creating process.t  C Data scavenging protection can be enabled in the form of high-watertD marking and erase-on-delete attributes. These attributes ensure thatF the contents of a file cannot be read after the file has been deleted.F The system manager can enforce file erasure on a per-volume basis. TheD system manager can also replace the disk erasure pattern with a pri-E vate pattern for those sites that have contractual obligations to useV a specific pattern.n  F Security auditing is provided for the selective recording of security-E related events. This auditing information can be directed to securitySD operator terminals (alarms) or to the system security audit log fileD (audits). Each audit record contains the date and time of the event,D the identity of the associated user process, and additional informa- tion specific to each event.  < OpenVMS provides security auditing for the following events:   o  Login and logoutl  ' o  Login failures and break-in attemptsc  E o  Object creation, access, deaccess, and deletion; selectable by useD:    of privilege, type of access, and on individual objects  ! o  Authorization database changeso  C o  Network logical link connections for DECnet for OpenVMS, DECnet-d$    Plus, DECwindows, IPC, and SYSMAN  # o  Use of identifiers or privilegesa  9 o  Installed image additions, deletions, and replacementso  "                                 27        o  Volume mounts and dismounts  3 o  Use of the Network Control Program (NCP) utilitye  - o  Use or failed use of individual privilegesp  4 o  Use of individual process control system services   o  System parameter changesU  ) o  System time changes and recalibrationst  D Note: Because no system can provide complete security, Compaq cannotD guarantee complete system security. However, Compaq continues to en-G hance the security capabilities of its products. Customers are stronglyTC advised to follow all industry-recognized security practices. Open-mD VMS recommended procedures are included in the OpenVMS Guide to Sys-
 tem Security.    OPERATING SYSTEM ENVIRONMENT  $ OpenVMS VAX Processes and Scheduling  D The basic unit of execution in OpenVMS VAX is the process. A processD consists of individual address space and registers known as context,D and code called an executable image. The context identifies the pro-G cess and describes its current state. Executable images consist of sys-tB tem programs and user programs that have been compiled and linked.  C The maximum number of concurrent processes is 8,192 per OpenVMS VAXy system.n  E Processes receive time to execute their images based on the priority.nC Thirty-two priorities are recognized on OpenVMS VAX, and 64 priori- F ties are recognized on OpenVMS Alpha. Priorities 0 to 15 are for time-C sharing processes and applications (four is the typical default for_F timesharing processes). Priorities 16 to 32 on VAX and 16 to 63 on Al-  pha are for real-time processes.    "                                 28 .     C Each time an event such as an I/O interrupt occurs, the system ser- C vices the event first and then passes control to the highest prior-pG ity process ready to execute. The system automatically adjusts the pri-3C orities of processes in the range of 0 to 15 to favor I/O-bound and_C interactive processes. However, the system does not adjust the pri-_C ority of a process in the range of 16 to 31 for VAX or 16 to 63 forh Alpha.  D Real-time processes can be assigned higher priorities to ensure thatE they receive processor time whenever they are ready to execute. Real-eG time processes are scheduled preemptively; that is, if a real-time pro-iC cess is ready to execute, it is given to the processor immediately,P< unless a process with a higher priority is ready to execute.  C OpenVMS uses paging and swapping to provide sufficient virtual mem-cF ory for concurrently executing processes. Paging and swapping are alsoG provided for processes whose memory requirements exceed available phys-oE ical memory. The maximum working set size is 512 MB of memory for VAXc and 4 GB for Alpha.a  F Programmers can control memory management from within an image. An im-C age executing in a real-time process, for example, can inhibit pag- * ing or swapping of critical code and data.  C Peripheral devices can be managed by the system or allocated by in-tH dividual processes. At least one disk must be a system disk. Other disksE can be designated as data disks for the general use of all users log-eG ging in to the system or for a specific group of users. The system con-n5 trols interactive terminals and one or more printers.e  & OpenVMS Alpha Processes and Scheduling  D The basic unit of execution in OpenVMS Alpha is the kernel thread. AF kernel thread consists of individual address space and registers knownD as context, and code called an executable image. The context identi-D fies the kernel thread and describes its current state. Each processD can have up to 256 kernel threads. Executable images consist of sys-B tem programs and user programs that have been compiled and linked.    "                                 29 i  n  D The maximum number of concurrent processes is 16,384 per OpenVMS Al- pha system.u  C Kernel threads receive processor time to execute their images basedhD on the priority of the process. Thirty-two priorities are recognizedG on OpenVMS VAX, and 64 priorities are recognized on OpenVMS Alpha. Pri-hE orities 0 to 15 are for time-sharing processes and applications (fourtC is the typical default for timesharing processes). Priorities 16 toa< 32 on VAX and 16 to 63 on Alpha are for real-time processes.  D Each time an event such as an I/O interrupt occurs, the system firstG services the event and then passes control to the highest priority ker-rF nel thread ready to execute. The system adjusts the priorities of ker-C nel threads whose base priority is in the range of 0 to 15 to favor E I/O-bound and interactive processes. However, the system does not ad-nE just the priority of a kernel thread in the range of 16 to 31 for VAX  or 16 to 63 for Alpha.  D Real-time processes can be assigned higher priorities to ensure thatE they receive processor time whenever they are ready to execute. Real-iG time processes are scheduled preemptively; that is, if a real-time pro-AC cess is ready to execute, it is given to the processor immediately,t5 unless a higher priority process is ready to execute.n  C OpenVMS uses paging and swapping to provide sufficient virtual mem-pE ory for concurrently executing processes. Paging and swapping is alsosG provided for processes whose memory requirements exceed available phys-  ical memory.  F Programmers can control memory management from within an image. An im-C age executing in a real-time process, for example, can inhibit pag-c* ing or swapping of critical code and data.  C Peripheral devices can be managed by the system or allocated by in-tH dividual processes. At least one disk must be a system disk. Other disksE can be designated as data disks for the general use of all users log-.G ging in to the system or for a specific group of users. The system con-s5 trols interactive terminals and one or more printers.a  & 64-Bit Virtual Addressing (Alpha Only)  "                                 30 i  c  C The OpenVMS Alpha operating system provides support for 64-bit vir-eE tual memory addressing. This capability makes the 8TB virtual address F space, defined by the Alpha architecture, available to the OpenVMS Al-E pha operating system and to application programs. Future hardware im-RD plementations will provide greater capacity. OpenVMS Alpha compilersD and applications take advantage of 64-bit processing by using 64-bitF data types. Refer to the SPDs for the OpenVMS Alpha compilers for fur-F ther details. Note that the application virtual address space defaultsD to a 32-bit implementation for compatibility and migration purposes.  - Very Large Memory (VLM) Features (Alpha Only)o  E OpenVMS Alpha provides the following additional memory management VLMe< features beyond those provided by 64-bit virtual addressing:  " o  Memory-resident global sections   o  Fast I/O for global sectionsa   o  Shared page tablesn   o  Expandable global page tablee   o  Reserved memory registry   F Memory-resident global sections allow a database server to keep largerD amounts of "hot" data cached in physical memory. The database serverE then accesses the data directly from physical memory without perform-cD ing I/O read operations from the database files on disk. With fasterE access to the data in physical memory, run-time performance increasesi
 dramatically.p  D As of OpenVMS Alpha Version 7.2, VLM applications that share a largeE memory-resident cache can use Fast I/O for memory shared by processeslC through global sections. Fast I/O improves the ability of a VLM ap-rE plication, such as a database server, to handle larger capacities andoC higher data throughput rates. By reducing the CPU costs per I/O re-vD quest, Fast I/O and memory-resident global sections dramatically in-? crease performance for critical database server I/O operations.c  "                                 31       G Shared page tables allow that same database server to reduce the amountiF of physical memory consumed within the system. Because multiple serverI processes share the same physical page tables that map the large databaseCF cache, an OpenVMS Alpha system can support more server processes. ThisG increases overall system capacity and decreases response time to client 	 requests.   G Also, with shared page tables, the database server startup time is dra-aI matically reduced because server processes can map memory-resident globaleC sections hundreds of times faster than traditional global sections. G With a multiple gigabyte global database cache, the server startup per-o" formance gains can be significant.  D The system parameters GBLPAGES and GBLPAGFIL are dynamic parameters.D Users with the CMKRNL privilege can change these parameter values onD a running system. Increasing the value of the GBLPAGES parameter al-C lows the global page table to expand, on demand, up to the new max-e
 imum size.  E The Reserved Memory Registry supports memory-resident global sectionscE and shared page tables. Through its interface within the SYSMAN util-hE ity, the Reserved Memory Registry allows an OpenVMS system to be con-sE figured with large amounts of memory set aside for use within memory-eD resident sections or other privileged code. The Reserved Memory Reg-D istry also allows an OpenVMS system to be properly tuned through AU-< TOGEN, thus accounting for the preallocated reserved memory.  ' Extended Physical Addressing (VAX Only)r  C Physical address space is 32 bits. The OpenVMS VAX operating systemhI can provide 3.5 GB of physical memory and .5 GB of I/O and adapter space.eI This enables large applications and workloads to access the large amountscC of physical memory that they require. The following table lists the > VAX processors that support this extended physical addressing:            "                                 32         C _________________Accessible________________________________________s                  PhysicalhC System___________Memory______I/O_and_Adapter_Space_________________c  " VAX 6000         1.25 GB     .5 GB	 model 600j  " VAX 7000         3.5 GB      .5 GB series  " VAX 10000        3.5 GB      .5 GBC series______________________________________________________________   Vector Processing (VAX Only)  D A single data item with only one value is known as a scalar value. AE group of related scalar values, or elements, with the same data type,t is known as a vector.e  C An extension to the VAX architecture defines an optional design for F integrated vector processing that has been adopted by several VAX sys-E tems. The VAX vector architecture includes sixteen 64-bit vector reg-yD isters (V0 through V15), each containing 64 elements, vector controlC registers, vector function units, and a set of vector instructions.sF VAX vector instructions transfer data between the vector registers andG memory, perform integer and floating-point arithmetic, and execute pro-f cessor control functions.f  G A more detailed description of the VAX vector architecture, vector reg-eE isters, and vector instructions appears in the VAX MACRO and Instruc-t tion Set Reference Manual.  E The OpenVMS VAX operating system provides fully shared, multiprogram- C ming support for VAX vector processing systems. By default, OpenVMS C VAX loads vector support code when initializing vector-present sys-eG tems but does not load it when initializing vector-absent systems. Sys- D tem managers can control this behavior by using the VECTOR_PROC sys- tem parameter.  "                                 33       D The presence of vector support code in a system has little effect onC processes running in a scalar-only system, or scalar processes run-cC ning in a vector-present system. If many processes must compete si-sC multaneously for vector processor resources, the system manager can C maintain good performance by adjusting system resources and process  quotas.a  F The OpenVMS VAX operating system makes the services of the vector pro-F cessor available to system users by means of a software abstract knownD as a capability. A system manager can restrict the use of the vectorD processor to users holding a particular identifier by associating an! ACL entry with the VECTOR object.o  C The VAX Vector Instruction Emulation Facility (VVIEF) is a standardhE feature of the OpenVMS VAX operating system. It allows vectorized ap-nC plications to be written and debugged in a VAX system in which vec-eD tor processors are not available. VVIEF emulates the VAX vector pro-D cessing environment, including the nonprivileged VAX vector instruc-E tions and the OpenVMS VAX vector system services. Use of VVIEF is re-k stricted to code in user mode.   DECdtm Servicest  D The DECdtm services embedded in the OpenVMS operating system supportI fully distributed databases using a two-phase commit protocol. The DECdtmyE services provide the technology and features for distributed process-fC ing, ensuring both transaction and database integrity across multi- D ple Compaq resource managers. Updates to distributed databases occurE as a single all-or-nothing unit of work, regardless of where the datadE physically resides. This ensures the consistency of distributed data.u  E DECdtm services allow applications to define global transactions thatpC can include calls to any number of Compaq data management products.rI Regardless of the mix of data management products used, the global trans-aF action either commits or aborts. OpenVMS is unique in providing trans-D action processing functionality with base operating system services.        "                                 34        DECdtm features include:  D o  Embedded OpenVMS system services that support the DECtp architec-E    ture, providing the features and technology for distributed trans-d    action processing.e  G o  Ability for multiple disjoint resources to be updated automatically.eC    These resources can be either physically disjointed on differenteC    clusters at separate sites, or logically disjointed in differente    databases on the same node.  E o  Robust application development. Applications can be written to en- F    sure that data is never in an inconsistent state, even in the event    of system failures.  E o  Ability to be called using any Compaq TP monitor or database prod- E    uct. This is useful for applications using several Compaq database-    products.   Interprocess Communication  D OpenVMS provides the following facilities for applications that con-' sist of multiple cooperating processes:o  C o  Mailboxes as virtual devices that allow processes to communicatee    with queued messages.  E o  Shared memory sections on a single processor or an SMP system thattC    permit multiple processes to access shared address space concur-i
    rently.  E o  Galaxywide sections on a Galaxy platform that permit multiple pro-MC    cesses in multiple instances to access shared address space con-t
    currently.s  : o  Common event flags that provide simple synchronization.  D o  A lock manager that provides a more comprehensive enqueue/dequeueH    facility with multilevel locks, values, and asynchronous system traps
    (ASTs).  "                                 35 s  e  G o  Intracluster communication services through which two processes run-bD    ning on the same system or on different OpenVMS Cluster nodes can,    establish a connection and exchange data.  H o  Logical names through which one process can pass information to otherE    processes running on the same system or on different OpenVMS Clus- 
    ter nodes.M  F o  Network interprocess communication is available via TCP/IP Services3    and DECnet-PLUS (product licenses are required).n   Symmetric Multiprocessing (SMP)   E OpenVMS provides symmetric multiprocessing (SMP) support for both Al-tD pha and VAX multiprocessor systems. SMP is a form of tightly coupledC multiprocessing in which all processors perform operations simulta-cG neously. All processors perform operations in all OpenVMS access modes,c( user, supervisor, executive, and kernel.  G OpenVMS SMP configurations consist of multiple CPUs executing code fromoF a single shared memory address space. Users and processes share a sin-E gle copy of OpenVMS Alpha or OpenVMS VAX address space. SMP also pro-dE vides simultaneous shared access to common data in global sections tosD all processors. OpenVMS SMP selects the CPU where a process will runD based on its priority and in special cases as directed by the appli-D cation. OpenVMS uses a specialized scheduling algorithm when running+ a nonuniform memory access (NUMA) platform.s  F SMP support is an integral part of OpenVMS and is provided to the userE transparently. Because an SMP system is a single system entity, it isgF configured into a network and OpenVMS Cluster configurations as a sin-	 gle node.c   Networking Facilitiest  G OpenVMS provides device drivers for all Compaq local area network (LAN) E adapters listed in the LAN Options section of Appendix A of this SPD.eE Application programmers can use the QIO system service to communicateeE with other systems connected via the LAN using either Ethernet or In-rC stitute of Electrical and Electronics Engineers (IEEE) 802.3 packett  "                                 36 n     C format. Simultaneous use of Compaq Ethernet and the IEEE 802.3 pro-u/ tocols are supported on any Compaq LAN adapter.i  C OpenVMS supports the standards defined by the ATM Forum's LANE Ver-sE sion 1.0 specifications for LAN emulation over an ATM network. By im-eE plementing an emulated LAN over an ATM network, you enable a group of D ATM stations to act like a traditional LAN. LAN emulated over an ATMI network allows you to run your existing applications basically unchanged,eC while the computers on which your applications are running are con-m nected to the ATM network.  F DECnet-Plus offers task-to-task communications, file management, down-D line system and task loading, network command terminals, and networkC resource sharing capabilities as defined in the DIGITAL Network Ar-_C chitecture (DNA) Phase V protocols. DECnet-Plus provides the newest_E DECnet features such as extended addressing and downline-load perfor- C mance enhancements. DECnet-Plus integrates DECnet and OSI protocols E and now provides a linkage to TCP/IP using Request for Comments (RFC)_G 1006 and RFC 1859. DECnet and OSI applications can now be run over DEC-O- net (NSP), OSI (CLNS), and TCP/IP transports.i  C DECnet for OpenVMS VAX and Alpha offers the networking capabilitiestG as defined in the DIGITAL Network Architecture (DNA) Phase IV. For morehD information, refer to the DECnet-Plus and DECnet Software portion of, the Associated Products section of this SPD.   Terminal Server Products  C Compaq's terminal server products provide terminal server access toVF OpenVMS. When used in an OpenVMS Cluster environment, terminal serversD distribute users across the available Alpha and VAX systems at login time.f  H OpenVMS can also establish a connection to other devices (such as print-' ers) attached to such terminal servers.e   Reliabilityn      "                                 37 e  X  H OpenVMS handles hardware errors as transparently as possible while main-D taining data integrity and providing sufficient information to diag-C nose errors. The system limits the effects of an error by first de-sC termining if the error is fatal. If the error occurs in system con-oD text, the current OpenVMS system shuts down. If the error is not fa-C tal, the system recovers actions pertinent to the error and contin-e ues the current operation.  E In all cases, information relevant to the error is written to the er- D ror log file for later analysis. Hardware errors include the follow- ing categories:e  C o  Processor errors. These include processor soft errors, processors=    hard errors, processor machine checks, and adapter errors.s  D o  Memory errors. These can be unrecoverable (hard) errors or recov-C    erable (soft) errors. The system examines memory at startup time D    and does not use any bad pages. During system operation, the sys-C    tem corrects all single-bit memory errors for those systems with D    error correction code (ECC) memory. On OpenVMS VAX, an unrecover-C    able error causes the memory page on which the error occurred to D    be added to the bad page list. If the page has not been modified,:    system operation continues with a new copy of the page.  G o  Correctable memory errors. A primary cause of these correctable mem-pC    ory errors is alpha particle radiation. On some processors, whencG    correctable memory errors occur, the memory controller corrects only E    the data returned to the CPU or I/O controller. The actual data iniC    memory is left with the error intact. Subsequent read operations D    cause correction cycles to occur and, in most cases, an interruptE    to report the error. On many of these processors, OpenVMS monitors H    the occurrence of correctable memory errors and, in almost all cases,F    is able to remove the error condition by rewriting the data in mem-G    ory. Rewriting the data causes the data to be corrected in that mem- G    ory location. On OpenVMS VAX, if the cause of the error is not tran-iD    sient, and the error condition persists, the operating system at-E    tempts to move the data from the existing page, which contains theoD    error, to a new page. The original page is then retired from use.    "                                 38 d  s   Other failures include:f  E o  Operating system errors (system-detected inconsistencies or archi- %    tectural errors in system context)n   o  User errors  
 o  I/O errorsn  E The system logs all processor errors, all operating system errors de- E tected through internal consistency checks, all double-bit memory er- D rors (and a summary of corrected single-bit memory errors), and most I/O errors.n  H If the system is shut down because of an unrecoverable hardware or soft-C ware error, a dump of physical memory is written. The dump includeseD the contents of the processor registers. The OpenVMS System Dump An-< alyzer (SDA) utility is provided for analyzing memory dumps.   Power Failures (VAX Only).  C If the power fails, the system shuts down automatically. When powernC is restored, the system restarts automatically and resumes process-e; ing at the point of interruption under these circumstances:   D 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  5 o  If the system is set to permit automatic rebootingi  D The system restarts device and communication lines and all I/O oper-G ations in progress, including magnetic tape I/O operations. On request,mC programs can be notified of power restoration. An optional battery-sE operated hardware clock resets the date and time of day when the sys- C tem restarts. If the system does not have a battery backup unit, ortC if the memory contents are not valid on power restoration, the sys-lE tem reboots automatically if it is set to permit automatic rebooting.   "                                 39    c  G If, for any reason, after a power failure the system disk does not comeeD back on line within a specific time after the CPU regains power, the system shuts down.   Input/Output  C The QIO system service and other related I/O services provide a di-vE rect interface to the operating system's I/O routines. These servicesnD are available from within most OpenVMS programming languages and canC be used to perform low-level I/O operations efficiently with a min-n> imal amount of system overhead for time-critical applications.  D Device drivers execute I/O instructions to transfer data to and fromE a device and to communicate directly with an I/O device. Each type ofcC I/O device requires its own driver. Compaq supplies drivers for allnG devices supported by the OpenVMS operating system and provides QIO sys-nE tem service routines to access the special features available in manyo of these devices.l  G OpenVMS supports a variety of disk and tape peripheral devices, as wellpD as terminals, networks, and mailboxes (virtual devices for interpro-2 cess communication), and more general I/O devices.  C With OpenVMS Alpha, users can write drivers for I/O devices that doeF not have inherent OpenVMS support. OpenVMS Alpha allows device driversG to be written in Compaq C and MACRO-32. Documentation is available thatoC describes how to write OpenVMS Alpha device drivers and how to con- F vert existing OpenVMS VAX drivers to run on OpenVMS Alpha systems. TheC Compaq C compiler for OpenVMS Alpha is an optional layered product.h  C With OpenVMS VAX, users can write their own drivers in MACRO-32 foroC I/O devices that do not have inherent OpenVMS support, as described ! in the appropriate documentation.    I/O Performance Features  C Fast I/O provides a suite of additional system services that appli-rE cations can use to improve I/O throughput. The fast I/O services min-d0 imize the CPU resources required to perform I/O.  "                                 40 o  s  C Fast Path provides a streamlined mainline code path through the I/O E subsystem to improve both uniprocessor and multiprocessor I/O perfor-eC mance. On multiprocessor systems, Fast Path allows all CPU process-nC ing for specific I/O adapters to be handled by a specific CPU. This C can significantly lower the demands on the primary CPU and increaseEE the I/O throughput on multiprocessor systems with multiple I/O ports.MG Disk and port drivers for the CIXCD, CIPCA, KGPSA, and KZPBA ports havesD been enhanced to take advantage of the Fast Path capability. No userC application changes are needed to take advantage of Fast Path. FasttD Path can be utilized by the $QIO system service or the Fast I/O ser- vices.   Extended File Cache (XFC) Alphao  D The Extended File Cache (XFC) is a new virtual block data cache pro-G vided with OpenVMS Alpha Version 7.3. Similar to the Virtual I/O Cache,tG the XFC is a clusterwide, file system data cache. Both file system datal9 caches are compatible and coexist in the OpenVMS Cluster.a  E The XFC improves I/O performance with the following features that are)) not available with the Virtual I/O Cache:e   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  9 o  Control over whether cache memory is static or dynamicu   Virtual I/O CacheP  G OpenVMS provides a standalone or clusterwide, file-oriented disk cache.oG Applications benefit from the advantages of the virtual I/O cache with-hF out any special coding. The virtual I/O file-caching algorithm is cho-G sen based on the type of clusterwide access currently in progress. Vir- E tual I/O caching reduces current and potential I/O bottlenecks withinr  "                                 41 .  e  E OpenVMS systems. It reduces the number of I/Os to the disk subsystem,e( thereby reducing systemwide bottlenecks.    Record Management Services (RMS)  D RMS is a set of I/O services that helps application programs to pro-E cess and manage files and records. Although it is intended to provide D a comprehensive software interface to mass storage devices, RMS also: supports device-independent access to unit-record devices.  D RMS supports sequential, relative, and indexed file organizations inG fixed-length and variable-length record formats. RMS also supports byteI0 stream formats for sequential file organization.  ? RMS record access modes provide access to records in four ways:s   o  Sequentiallys   o  Directly by key value  % o  Directly by relative record numbern  " o  Directly by record file address  G RMS also supports block I/O operations for various performance-criticalrD applications that require user-defined file organizations and record formats.  G RMS promotes safe and efficient file sharing by providing multiple filesE access modes and automatic record locking (where applicable). RMS of-(F fers the options of enabling global buffers for buffer sharing by mul- tiple processes.  C RMS utilities aid file creation and record maintenance. These util--D ities convert files from one organization and format to another; re-F structure indexed files for storage and access efficiency; and reclaimC data structures within indexed files. These utilities also generate  appropriate reports.    "                                 42 e     F For systems that have DECnet for OpenVMS VAX and Alpha, or DECnet-PlusC installed, RMS provides a subset of file and record management ser-eC vices to remote network nodes. Remote file operations are generallye transparent to user programs.   C Commands such as EDIT, CREATE, COPY, TYPE, and PRINT allow users toOA manipulate RMS records within RMS files at the DCL command level.i   Disk and Tape Volumese  C The system manager can organize disk volumes into volume sets. Vol-tC ume sets can contain a mix of disk device types and can be extendedmF by adding volumes. Within a volume set, files of any organization typeG can span multiple volumes. Files can be allocated to the set as a wholeaD (the default) or to specific volumes within the set. Optionally, theE system manager can allocate portions of indexed files to specific ar-r< eas of a single disk or to specific volumes in a volume set.  C The system manager can place quotas on a disk to control the amountgC of space individual users can allocate. Quota assignment is made by D UIC and can be controlled for each individual volume set in the sys-G tem (or for each individual volume if the volume is not part of a set).e  D The system manager can cache disk structure information in memory toG reduce the I/O overhead required for file management services. Although D not required to do so, users can preallocate space and control auto-E matic allocation. For example, a file can be extended by a given num-nE ber of blocks, contiguously or noncontiguously, for optimal file sys-  tem performance.  C The system applies software validity checks and checksums to criti- F cal disk structure information. If a disk is improperly dismounted be-E cause of user error or system failure, the system rebuilds the disk'syF structure information automatically the next time the disk is mounted.E The system detects bad blocks and prevents their reuse once the fileseF to which the blocks were allocated are deleted. On DIGITAL Storage Ar-D chitecture (DSA) disks, the disk controller detects and replaces bad blocks automatically.     "                                 43 n  o  C The system provides 255 levels of named directories and subdirecto- E ries whose contents are alphabetically ordered. Device and file spec-lD ifications follow Compaq conventions. Users can use logical names toE abbreviate the specifications and to make application programs devicenD and file name independent. Users can assign a logical name to an en-G tire specification, to a portion of a specification, or to another log-p
 ical name.  F OpenVMS supports multivolume magnetic tape files with transparent vol-C ume switching. Access positioning is done either by file name or by  relative file position.   ; OpenVMS Alpha Support for New AlphaServer GS Series Systemsh  C OpenVMS Version 7.3 provides support for Compaq's AlphaServer GS80, / GS160 and GS320 systems. This support includes:   G o  OpenVMS support for hard and soft partitions (Galaxy) on AlphaServerd     GS80, GS160 and GS320 systems  B o  OpenVMS Resource Affinity Domain (RAD) support for applications  ) o  OpenVMS Support for CPU Online Replacen  , OpenVMS Support for Hard and Soft Partitions  D Hard partitioning is a physical separation of computing resources byD hardware-enforced access barriers. It is impossible to read or writeF across a hard partition boundary. There is no resource sharing between hard partitions.  E Soft partitioning is a separation of computing resources by software-iD controlled access barriers. Read and write access across a soft par-E tition boundary is controlled by the operating system. OpenVMS Galaxy * is an implementation of soft partitioning.  C The way that customers choose to partition their systems depends onrC their computing environments and application requirements. For more,C information about using hard partitions and OpenVMS Galaxy, see the , OpenVMS Alpha Partitioning and Galaxy Guide.  "                                 44 w  e  @ OpenVMS Application Support for Resource Affinity Domains (RADs)  C The large amount of physical memory in the AlphaServer GS80/160/320 G systems provides opportunities for extremely large databases to be com-hD pletely in memory. The nonuniform memory access (NUMA) system archi-F tecture of the new AlphaServer GS80/160/320 systems provides the band-C width to efficiently access this large amount of memory. NUMA is an,D attribute of a system in which the access time to any given physical$ memory is not the same for all CPUs.  C OpenVMS Alpha Version 7.3 includes NUMA awareness in OpenVMS memoryID management and process scheduling. This capability (application sup-E port for resource affinity domains) ensures that applications running G in a single instance of OpenVMS on multiple quad building blocks (QBBs)s= can execute as efficiently as possible in a NUMA environment.r  D The operating system treats the hardware as a set of resource affin-E ity domains (RADs). A RAD is a set of hardware components (CPUs, mem- M ory, and I/O) with common access characteristics. On AlphaServer GS80/160/320hC systems, a RAD corresponds to a Quad Building Block (QBB) in an Al-d& phaServer GS80, GS160 or GS320 system.  C For more information about using the OpenVMS RAD support for appli-aE cation features, see the OpenVMS Alpha Partitioning and Galaxy Guide.e  & OpenVMS Support for CPU Online Replace  C With OpenVMS Alpha Version 7.3, you can replace secondary CPUs on alG running system without rebooting, which provides increased system main-oE tainability and serviceability. This feature is supported only on Al-eD phaServer GS160/320 systems. Note that replacing the primary CPU re- quires rebooting.d   E-BUSINESS TECHNOLOGIES   E The Compaq OpenVMS e-Business Infrastructure Package provides key In-wC ternet and e-Business software technology that enhances the OpenVMSIF Alpha operating system. These technologies are licensed as part of the    "                                 45    i  C Compaq OpenVMS Alpha Operating System and are provided on the Open-hC VMS e-Business Infrastructure CD-ROM (Ordering number QA-6LYAA-H8).aE Additional details can be found in the OpenVMS e-Business Infrastruc-dF ture Package Software Product Description, SPD 80.58.00. Most of these) technologies can also be downloaded from:   2 http://www.openvms.compaq.com/ebusiness/index.html  1 Java 2 Software Development Kit for OpenVMS Alphat  D The Java 2 Software Development Kit (SDK) provides an environment inD which to develop and deploy Java applications on OpenVMS Alpha. JavaE applications can be written once and run on any operating system thatrE implements the Java run-time environment, which consists primarily ofk the Java Virtual Machine (JVM).(  D The Java 2 SDK is a set of building blocks containing basic develop-7 ment tools and a rich set of class libraries including:n   o  Java Compiler   o  Java Virtual Machine (JVM)e   o  Java Class LibrariesM   o  Java Applet Viewern    o  Java Debugger and other tools  D o  A POSIX threads (pthreads) implementation that provides increased(    performance on multiprocessor systems  C o  Flexible options for representing UNIX directory and file speci-e    fications on OpenVMS system  D Services for the Java 2 SDK for OpenVMS Alpha are provided under ex-3 isting OpenVMS Operating System service agreements.   * Compaq Secure Web Server for OpenVMS Alpha  "                                 46 r  o  C Compaq Secure Web Server for OpenVMS Alpha (CSWS) provides a power-fF ful, flexible web server based on the popular Apache Web Server 1.3.12C from the Apache Software Foundation and provides the following fea-t tures:    o  HTTP/1.1 compliance (RFC2616)  + o  All standard Apache extensions (modules)f   o  Perl support (mod_perl)   o  Java support (mod_jserv)t  E o  Secure Sockets Layer (SSL) support (mod_ssl) using OpenSSL and RSA     Crypto-C (BSAFE)z  * o  Digital certificates from VeriSign Inc.  D Services for Compaq Secure Web Server for OpenVMS Alpha are provided; under existing OpenVMS Operating System service agreements.r  & Attunity Connect "On Platform" Package  C Attunity Connect is object-oriented middleware that facilitates theaC development of applications that access, integrate, and update datadC from multiple, heterogeneous sources across a wide range of operat-o ing system platforms.e  C The Attunity Connect "On Platform" package for OpenVMS provides the,C ODBC, JDBC, and XML client APIs and ODBC, XML and Oracle8i adaptersiD for accessing data sources. Additional data adapters for OpenVMS Al-> pha and Attunity Connect are available directly from Attunity.  C The full Attunity Connect product provides ODBC, JDBC, XML, ADO anddC OLEDB client APIs and adapters for a large number of relational and D nonrelational data sources and support for a large number of popularC platforms including UNIX, Windows, OpenVMS, Tandem, and mainframes.   C Services for the Attunity Connect "On Platform" Package for OpenVMS I Alpha are provided under existing OpenVMS Operating System service agree-m ments.  + Extensible Markup Language (XML) Technologyg  "                                 47    t  I Using open source software from Apache Software Foundation, an XML parsereD and an XSLT stylesheet processor are provided that give applicationsC the ability to parse, generate, manipulate, validate, and transformn XML documents and data.e  D Services for the XML Technology for OpenVMS Alpha are provided under5 existing OpenVMS Operating System service agreements.c  A Compaq OpenVMS Enterprise Directory for e-Business (LDAPv3/X.500)y  D The Compaq OpenVMS Enterprise Directory for e-Business, based on theG X.500 standard, delivers robust and scaleable directory services acrosscG intranets, extranets and the Internet to customers, suppliers and part- C ners. It combines the best of both the industry standard LDAPv3 andtG X.500 capabilities. The former allows access by a myriad of LightweighteF Directory Access Protocol (LDAP) clients, user agents and applicationsE and the latter brings very high performance, resilience, advanced ac-l9 cess controls and easy replication across the enterprise.i  D Certified with Entrust/PKI 5, this directory ensures at sign on thatD all users may be authenticated with zero latency and that each gains: access only to those resources they are authorized to use.  D The OpenVMS Enterprise Directory for e-Business may contain informa-D tion on anything of interest, including people, systems, network re-D sources, applications, authentication certificates and databases. ItF is designed to be accessed by individual users, applications and soft-F ware developers. Both the established DAP interface and the LDAPv3 in-I terface may be accessed simultaneously by disparate applications, therebyw7 delivering full integration with existing environments.r  G The OpenVMS Enterprise Directory for e-Business is available with Open- D VMS Alpha Version 7.3 and is licensed with the OpenVMS Alpha operat-C ing system. It is also available on the OpenVMS Alpha Software Lay- C ered Products Library. Software Support Service for this product isSC sold separately. For further information, refer to the Compaq Open-iD VMS Enterprise Directory for e-Business Software Product Description (SPD 40.77.xx)   Reliable Transaction Routerd  "                                 48 a  y  F Reliable Transaction Router (RTR) is fault tolerant transactional mes-C saging middleware used to implement large, distributed applicationsaC using client/server technology. Reliable Transaction Router enablesrC computing enterprises to deploy distributed applications on OpenVMSo Alpha and VAX systems.  C Software Support Service for this product is sold separately. ReferyC to the Reliable Transaction Router for OpenVMS Software Product De-p4 scription (SPD 51.04.xx) for additional information.   Compaq BridgeWorks  C Compaq BridgeWorks is a distributed application development and de-rC ployment tool for OpenVMS 3GL applications. Compaq BridgeWorks con-eC sists of a GUI development tool on the Windows NT desktop, a server G manager component on OpenVMS, and extensive online help. Compaq Bridge-AF Works provides developers with an easy means to create distributed ap-C plications using OpenVMS as the enterprise server and Windows NT aslC the departmental server. Compaq BridgeWorks enables software devel-aC opers to develop components that encapsulate selected functionality2C in 3GL OpenVMS applications using an interactive PC environment. ItaD generates all the necessary files and code to build these componentsG into a three-tier, distributed connection. Components generated by Com-nE paq BridgeWorks use established standard technologies internally, in-e! cluding COM, DCE/RPC, C, and C++.a  C Compaq BridgeWorks does not directly assist with the development of C the clients; it provides the code that exposes the 3GL routine as alG component. The client can be developed using any COM-capable tool, such 6 as Visual Basic, Visual C++, and many scripting tools.  = Software Support Service for this product is sold separately.s   Compaq COM for OpenVMS            "                                 49 c  a  D Component Object Model (COM) is a technology from Microsoft that al-E lows developers to create distributed network objects. Digital Equip-sC ment Corporation and Microsoft jointly developed the COM specifica-rG tion. First released by Microsoft on Windows NT as Network Object Link-GD ing and Embedding (NetOLE), and then renamed Distributed COM (DCOM),3 the COM specification now includes network objects.u  F COM is used to create distributed applications made up of reusable ob-C jects. COM locates objects locally or in a network and uses the Re- D mote Procedure Call (RPC) wire protocol to communicate between these objects across the network.E  G COM on OpenVMS delivers connectivity and interoperability between Open-oD VMS and Windows NT systems. With Compaq COM for OpenVMS, programmersD write distributed applications that run across a heterogeneous envi-D ronment of systems. Compaq COM for OpenVMS is based on the MicrosoftD COM shipped on Windows NT Version 4.0 SP3 and implements many of theE features of Microsoft COM including activation, automation, monikers,i2 Type Libraries, and structured storage on OpenVMS.  < COM on OpenVMS requires OpenVMS Alpha Version 7.2 or higher.  C The binary kit for COM (both developer kit and run-time) ships withtF the OpenVMS Alpha distribution kit. COM is not available on VAX. Soft-F ware Support Service for this product is sold separately. For more in-C formation, see the Compaq COM for OpenVMS Software Product Descrip-i tion (SPD 70.45.xx).  + Netscape FastTrack Server for OpenVMS Alphar  F Netscape FastTrack Server Version 3.02 for OpenVMS Alpha is a general-F purpose Web server for creating, building, publishing, and serving Web pages and applications.i  G Netscape FastTrack Server is being replaced by Compaq Secure Web ServerlD (based upon Apache) for OpenVMS Alpha. FastTrack will continue to beD supported until December 31, 2001 on OpenVMS Version 7.1 and Version 7.2 systems.    "                                 50    l  E Services for the Netscape FastTrack Server for OpenVMS Alpha are pro-e0 vided under existing OpenVMS service agreements.   ASSOCIATED PRODUCTSe  ( Compaq Advanced Server for OpenVMS AlphaE Compaq Advanced Server for OpenVMS is supported on OpenVMS Alpha sys-eG tems only. Advanced Server V7.3 for OpenVMS is the only version of thatrC product supported on OpenVMS Alpha Version 7.3. The Advanced ServerqD for OpenVMS product evolved from the PATHWORKS for OpenVMS (Advanced Server).  G Advanced Server is an OpenVMS-based network operating system (NOS) com-tC patible with Microsoft networking technology. The software lets you.D establish Compaq OpenVMS systems as servers to provide Windows desk-G top users easy and efficient access to OpenVMS file and print services.rC Desktop users can use Microsoft products and utilities such as Win-y@ dows Explorer to access these resources shared over the network.  F Advanced Server for OpenVMS combines the networking strengths and richE application set of Windows NT with the proven availability, scalabil-eF ity, and security of OpenVMS. The software supports the Windows NT in-F tegration features of OpenVMS Alpha Version 7.3 and is compatible with@ Windows NT and Windows 2000 servers running in the same network.  C Advanced Server for OpenVMS can function as a file and print servereH for a small, isolated community of users or as the foundation of a largeF network distributed over a wide geographical area. The Advanced ServerC software also provides a flexible system for network administrationtD and security, for both wide area networks (WANs) and local area net-
 works (LANs).O  . Compaq PATHWORKS for OpenVMS (Advanced Server)  C Compaq PATHWORKS for OpenVMS (Advanced Server), also known as PATH-sF WORKS Advanced Server, runs on OpenVMS Alpha and VAX systems. The onlyG version supported on OpenVMS Alpha or VAX Version 7.3 is PATHWORKS Ver-nC sion 6.0D for OpenVMS (Advanced Server). PATHWORKS Advanced Server,t    "                                 51 m  e  D as with Advanced Server for OpenVMS, is an OpenVMS-based network op-E erating system compatible with, and enhancing, the Microsoft network-fG ing technology, and providing file and print services for Windows desk-oG top users. It is compatible with Windows NT servers running in the same  network.  4 Compaq Galaxy Software Architecture on OpenVMS Alpha  D Compaq Galaxy Software Architecture on OpenVMS Alpha is available as6 a separately licensed System Integrated Product (SIP).  E By running multiple instances of OpenVMS in a single computer or hardVD partition, an OpenVMS Galaxy computing environment gives you quantum improvements in:  ; o  Compatibility-Existing applications run without changes.d  E o  Availability-Presents opportunities to upgrade software and expande$    system capacity without downtime.  C o  Scalability-Offers scaling alternatives that improve performanceh#    of SMP and cluster environments.L  C o  Adaptability-Physical resources can be dynamically reassigned toh"    meet changing workload demands.  D o  Cost of ownership-Fewer computer systems reduce system management'    requirements, floor space, and more.y  G For companies looking to improve their ability to manage unpredictable,aE variable, or growing IT workloads, OpenVMS Galaxy technology providestF a flexible way to dynamically reconfigure and manage system resources.  F An OpenVMS Galaxy computing environment is ideal for high-availability applications, such as:   o  Database serversf  ! o  Transaction processing systems    o  Data warehousingi   o  Data mining  "                                 52 h  s   o  Internet servers   C With OpenVMS Alpha Version 7.3 and forward, you can create an Open- D VMS Galaxy computing environment that allows you to run multiple in-B stances of OpenVMS on AlphaServer systems, and also allows you to:  " o  Reassign CPUs between instances  8 o  Perform independent booting and shutdown of instances  5 o  Use shared memory for inter-instance communicationy  D o  Create a shared memory RAMdisk with Compaq DECram for OpenVMS Al-    pha Version 3.0  C o  Cluster instances within an OpenVMS Galaxy using the shared mem-c    ory cluster interconnectP  , o  Cluster instances with non-Galaxy systems  E o  Create applications using OpenVMS Galaxy APIs for resource manage-bD    ment, event notification, locking for synchronization, and shared    memory for global sections   E o  Use the Galaxy Configuration Utility to view and control the Open-e    VMS Galaxy environmentr  C o  Run a single-instance OpenVMS Galaxy on any Alpha system for ap-     plication development  C Compaq Galaxy Software Architecture on OpenVMS Alpha requires Open-o VMS Alpha Version 7.2 or later.f  E For more information about OpenVMS Galaxy licensing requirements, re- G fer to the Galaxy Software Architecture on OpenVMS Alpha Software Prod-  uct Description (SPD 70.44.xx).   D For more information about how to create, manage, and use an OpenVMSC Galaxy computing environment, refer to the OpenVMS Alpha Partition-a ing and Galaxy Guide.V   Compaq OpenVMS Cluster Softwarea  "                                 53 h     C Compaq OpenVMS Cluster software is available for Alpha and VAX sys-nF tems as a separately licensed System Integrated Product (SIP). It pro-D vides a highly integrated OpenVMS computing environment that is dis-9 tributed over multiple systems containing up to 96 nodes.n  C OpenVMS Cluster systems and storage communicate using a combination  of the following interconnects:p   o  Memory Channelt   o  CIr  . o  DIGITAL Storage Systems Interconnect (DSSI)  * o  Fiber Distributed Data Interface (FDDI)   o  Ethernetl  ) o  Small Computer System Interface (SCSI)   : o  Shared Memory Cluster Interconnect (SMCI) (Galaxy only)  7 o  Fibre Channel (Storage Only) Version 7.2-1 and abovee  F In addition, when configured with suitable FDDI bridges, OpenVMS Clus-F ter configurations can use DS3/T3 and asynchronous transfer mode (ATM) networking infrastructures.e  D Applications running on one or more nodes in an OpenVMS Cluster sys-E tem share resources in a coordinated manner. While updating data, thedF OpenVMS Cluster software synchronizes access to shared resources, pre-D venting multiple processes on any node in the cluster from uncoordi-E nated access to shared data. This coordination ensures data integritybC during concurrent update transactions. Application programs specify E the level of OpenVMS Cluster file sharing that is required; access isoD then coordinated by the extended QIO processor (XQP) and Record Man- agement System (RMS).   F The OpenVMS queue manager controls the OpenVMS Cluster batch and printG queues, which can be accessed by any node in the OpenVMS Cluster. BatchtD jobs submitted to OpenVMS Cluster queues are routed to any available% CPU so that the batch load is shared.o  "                                 54       D The Lock Manager provides synchronized services between systems in aC cluster, for use by both system components such as RMS and XQP, and $ also for direct use by applications.  F Two or more Alpha and VAX computers connected to the same Memory Chan-D nel, CI, DSSI, or SCSI interconnect must be configured as members ofE the same OpenVMS Cluster system. Mixed-architecture and mixed-versionlG clusters that contain both Alpha systems and VAX systems are supported.a  D OpenVMS Cluster systems provide a uniform computing environment thatH is highly scaleable, highly available, and secure. OpenVMS Cluster soft-C ware implements a single-security environment within a cluster con-tC figuration. The security subsystem ensures that all cluster-visiblerC objects maintain consistent security profiles and that system secu-O+ rity auditing controls operate clusterwide.r  E Refer to the Compaq OpenVMS Cluster Software Product Description (SPDo 29.78.xx) for more information.   # Compaq Volume Shadowing for OpenVMSS  C Compaq provides Volume Shadowing for OpenVMS Alpha and VAX productstD for performing disk mirroring operations, using a redundant array of, independent disks (RAID) 1 storage strategy.  G Compaq Volume Shadowing for OpenVMS is available for Alpha and VAX sys-VD tems as a separate licensed System Integration Product (SIP). VolumeF Shadowing for OpenVMS provides high data availability for disk devicesC by ensuring against data loss that results from media deteriorationeE or controller or device failure. This prevents storage subsystem com- > ponent failures from interrupting system or application tasks.  H The system disk and Files-11 On-Disk Structure (ODS-2, ODS-5) data disks can be volume shadowed.e  G Volume Shadowing for OpenVMS supports the clusterwide shadowing of Com-cC paq SCSI and DSA storage systems. Volume Shadowing for OpenVMS alsoqF supports shadowing of all MSCP served DSA disks and Compaq SCSI disks.C All disks in a single shadow set must have the same number of logi- C cal blocks. Shadow set members can be located on a single system or   "                                 55    w  E anywhere in an OpenVMS Cluster system. Disks can be configured on any ) MSCP or Compaq SCSI-compliant controller.e  D Volume Shadowing for OpenVMS provides fault tolerance resulting fromC disk media errors or controller errors across the full range of Al- F pha and VAX processors and configurations. Shadow set member units canE be located on different controllers and OpenVMS Alpha and OpenVMS VAXnC MSCP servers, providing configuration flexibility and a high degrees of data availability.f  G Volume Shadowing for OpenVMS supports up to 10,000 single-member shadoweD sets, and up to 500 devices in multiple member (two or three member)7 shadow sets, on a standalone or OpenVMS Cluster system.d  D The binary kit for Volume Shadowing ships with the OpenVMS Alpha andC VAX distribution kits. To run the software, customers must purchaseoD a license. Refer to the Compaq Volume Shadowing for OpenVMS Software8 Product Description (SPD 27.29.xx) for more information.  " Compaq TCP/IP Services for OpenVMS  C Compaq TCP/IP Services for OpenVMS, Version 5.1, (VAX and Alpha) is D Compaq's industry-standard implementation of the TCP/IP and NFS net-E working protocols on the OpenVMS platform. Compaq TCP/IP Services forhE OpenVMS is integrated with the OpenVMS operating system installation. D Compaq TCP/IP Services for OpenVMS provides interoperability and re-C source sharing among systems running OpenVMS, UNIX, Windows NT, andlC other operating systems that support TCP/IP. Version 5.1 provides aAH comprehensive suite of functions and applications that support industry-C standard protocols for heterogeneous network communications and re-SC source sharing. TCP/IP Services Version 5.1 incorporates the TCP/IPg3 protocols stack from Compaq Tru64 UNIX Version 5.1.   E Compaq TCP/IP Service for OpenVMS, Version 5.1, provides enhancementslD such as NFS V3, the ability to run NFS over TCP and an Anti-SPAM re-D lay for SMTP mail. This release also contains Internet Protocol Ver-C sion 6 (IPv6) support for Transmission Control Protocol (TCP), User C Datagram Protocol (UDP), raw sockets, and IPv6 support for commands D and utilities. This support is for those customers who want to startH using IPv6 today and for those who want to test or experiment with IPv6.  "                                 56 t  r  F This support is in addition to the IPv4 support already in TCP/IP Ser- vices for OpenVMS.  H Compaq TCP/IP Services for OpenVMS provides a full TCP/IP protocol suiteE including IP/Multicasting, Dynamic Load Balancing, Rlogin PROXY, net-vC work file access, remote terminal access, remote command execution,sD remote printing, mail, application development, Post Office Protocol8 (POP), SNMP Extensible agent (eSNMP) and Finger Utility.  C Compaq TCP/IP Services for OpenVMS, Version 5.1 ensures transparenteC backward compatibility with earlier versions of TCP/IP Services foruC OpenVMS and is supported on OpenVMS Alpha Versions 7.1, 7.2 and 7.3s* and OpenVMS VAX Versions 7.1, 7.2 and 7.3.  & Compaq DECnet-Plus and DECnet Software  G Compaq DECnet for OpenVMS VAX and Alpha software is a System IntegratedoD Product (SIP) that is licensed separately from the OpenVMS operatingE system. Refer to the Compaq DECnet for OpenVMS VAX and Alpha SoftwarexG Product Description (SPD 48.48.xx) for further information on supporteda- communications devices and software features.c  D Compaq DECnet-Plus (formerly DECnet/OSI) is licensed separately fromE the OpenVMS operating system. The license for Compaq DECnet for Open-bF VMS VAX and Alpha also grants the rights to use DECnet-Plus. Note thatF only one version of DECnet can be active on a single system at any oneF time. Refer to the Compaq DECnet-Plus for OpenVMS Alpha Software Prod-C uct Description (SPD 50.45.xx) and the Compaq DECnet-Plus for Open- D VMS VAX Software Product Description (SPD 25.03.xx)) for further in-E formation on supported hardware configurations and software features.e  ! Compaq RMS Journaling for OpenVMS   E Compaq provides the RMS Journaling for OpenVMS Alpha and VAX productsrF as separately licensed SIPs that enable a system manager, user, or ap-E plication to maintain the data integrity of RMS files in the event ofSD a number of failure scenarios. These journaling products protect RMS- file data from becoming lost or inconsistent.A    "                                 57 c  e  @ RMS Journaling provides the following three types of journaling:  E o  After-image journaling. Allows users to reapply modifications thateD    have been made to a file. This type of journaling allows users toD    recover files that are inadvertently deleted, lost, or corrupted.C    RMS Journaling recovers the file by applying the journaled modi-cE    fications to a backup copy, thereby restoring its final state. Ap- E    plication modifications are not necessary to use after-image jour-r
    naling.  F o  Before-image journaling. Allows users to reverse modifications thatD    have been made to a file. This type of journaling allows users toF    return a file to a previously known state. This is useful if a fileC    is updated with incorrect or bad data. Application modifications 4    are not necessary to use before-image journaling.  E o  Recovery-unit journaling. Allows users to maintain transaction in-lD    tegrity. A transaction can be defined as a series of file updatesF    on one or more files. If any failure occurs during the transaction,E    recovery-unit journaling rolls back the partially completed trans-nD    action to its starting point. This allows complex transactions toC    be completed as an atomic event-partially completed transactionsoE    can be avoided. Recovery-unit journaling requires application mod-y
    ification.   F The binary kit for RMS Journaling ships with the OpenVMS Alpha and VAXE distribution kits. To run the software, customers must purchase a li- E cense and documentation. Refer to the Compaq RMS Journaling for Open-PE VMS Software Product Description (SPD 27.58.xx) for more information.    Compaq DECram for OpenVMSr  C Compaq DECram for OpenVMS is a disk device driver that improves I/ObH performance by allowing an OpenVMS system manager to create pseudo disksC (RAMdisks) that reside in main memory. Frequently accessed data caneF be accessed much faster from a DECram device than from a physical diskC device. These RAMdisks can be accessed through the file system just E as physical disks are accessed, requiring no change to application ors system software.  "                                 58 n  r  D Because main memory is allocated for the DECram device, extra memoryC is generally required. The OpenVMS system manager can designate theiE amount of memory dedicated to the DECram device(s) and the files thatr will be stored on it.i  D In Compaq DECram for OpenVMS Version 3.0, DECram's capability is ex-F tended to use OpenVMS Galaxy shared memory to create a VMS shared mem-G ory disk. This will allow customers to take advantage of OpenVMS GalaxyfA shared memory with no modifications to any of their applications.e  C Compaq DECram for OpenVMS Version 3.0 is supported on OpenVMS AlphadE Version 7.2-1H1 or higher. Compaq DECram for OpenVMS Version 2.3 will E continue to be available and supported on OpenVMS Alpha Versions 7.1,a2 7.2 and 7.3 and OpenVMS VAX Version 6.2 or higher.  D DECram Version 3.0 cannot run on an OpenVMS VAX system, however, theD RAMdisk can be accessed by OpenVMS VAX systems in an OpenVMS Cluster system.   C Refer to the Compaq DECram for OpenVMS Software Product Description.$ (SPD 34.26.xx) for more information.  # Compaq DECwindows Motif for OpenVMSt  E Compaq offers a separately licensed layered product called DECwindowseD Motif for OpenVMS. This product provides support for both OSF/Motif,D a standards-based graphical user interface, and the X user interfaceC (XUI) in a single, run-time and development environment. DECwindowssC Motif displays the OSF/Motif user interface. Because both Motif andkC XUI are based on X Consortium's X Window System, applications writ-cG ten on either toolkit will run regardless of which environment the user H selects. Refer to the Compaq DECwindows Motif for OpenVMS Software Prod-4 uct Description (SPD 42.19.xx) for more information.  F Compaq DECwindows Motif Version 1.2-5 for OpenVMS Alpha and higher de-C livers the New Desktop environment for OpenVMS Alpha systems, whichhD is derived from the Common Desktop Environment (CDE) technology. CDED provides and defines a consistent user interface for end users and aD consistent development environment for application developers across multiple platforms.e  "                                 59 o  g  E The OpenVMS software installation procedure contains an optional step E to install the DECwindows Motif for OpenVMS workstation and font sup- D port, which is required to run the DECwindows Motif for OpenVMS lay-D ered product. Refer to the OpenVMS Alpha Version 7.3 Upgrade and In-E stallation Manual or OpenVMS VAX Version 7.3 Upgrade and InstallationqF Manual for details concerning the optional installation of the DECwin-& dows Motif for OpenVMS device support.   CONFORMANCE TO STANDARDS  E OpenVMS is based on the following public, national, and internationalq
 standards.  / Distributed Computing Environment (DCE) Support   C The Compaq DCE for the OpenVMS product family provides a set of the C distributed computing features specified by the Open Software Foun- E dation's (OSF) DCE, as well as tools for application developers. With F DCE, the OSF has established a standard set of services and interfacesC that facilitate the creation, use, and maintenance of client/serveroD applications. Compaq DCE for OpenVMS serves as the basis for an openE computing environment where networks of multivendor systems appear as F a single system to the user. Because DCE makes the underlying networksD and operating systems transparent, application developers can easilyC build portable, interoperable client/server applications. Users can3D locate and share information safely and easily across the entire en-D terprise. Compaq DCE for OpenVMS supplies system managers with a setD of tools to consistently manage the entire distributed computing en-: vironment, while assuring the integrity of the enterprise.  D Compaq DCE for OpenVMS currently consists of the following products:  D o  DCE Run-time Services for OpenVMS, which is required for all sys-D    tems participating in the DCE cell. The Run-time Services includeE    DCE client functions as well as DCE administration tools. DCE Run-pF    time Services allow client/server applications to interoperate over0    DECnet, TCP/IP, and UDP/IP network protocols.      "                                 60 t  i  E o  DCE Application Developers' Kit for OpenVMS, which is required fornC    developers of distributed applications but is optional for otherMG    users. The DCE Application Developers' Kit provides programmers with G    an Interface Definition Language (IDL), an easy-to-use, ANSI C-based//    language for writing remote procedure calls.n  F o  DCE Cell Directory Service (CDS), one of which is required for eachE    DCE cell. The DCE CDS is a central repository that contains infor-pD    mation about the location of resources in the DCE cell. It allowsC    access to resources by a single name, regardless of their physi-o    cal location.  E o  Compaq DCE Security Server, one of which is required for each DCE.fE    The DCE Security Server protects resources from illegal access andr?    provides secure communications within and between DCE cells.s  E The right to use the DCE Run-time Services is included with the Open-DD VMS operating system base license. All other DCE products are avail-G able as separate layered products. Refer to the Compaq Distributed Com-sF puting Environment (DCE) for OpenVMS Software Product Description (SPD( 43.05.xx) for more detailed information.  3 Support for OSF/Motif and X Window System Standardso  I DECwindows Motif provides support for OSF/Motif, a standards based graph-oC ical user interface. DECwindows Motif also provides support for theuD X Consortium's X Window System, Version 11, Release 6 (X11R6) server- and the Version 11, Release 5 (X11R5) client.d   Standards Supported by OpenVMS  H The OpenVMS operating system is based on the following public, national,G and international standards. These standards are developed by the Amer-eF ican National Standards Institute (ANSI), U.S. Federal Government (re-F sponsible for FIPS), Institute of Electrical and Electronics EngineersE (IEEE), and the International Organization for Standardization (ISO).oE The following information may be useful in determining responsiveness C to stated conformance requirements as enabled in particular commer-e: cial and/or government procurement solicitation documents.  - o  ANSI X3.4-1986: American Standard Code fors  "                                 61 f  l      Information Interchange  * o  ANSI X3.22-1973: Recorded Magnetic Tape    (800 BPI, NRZI)  / o  ANSI X3.27-1987: File Structure and Labelinge0    of Magnetic Tapes for Information Interchange    o  ANSI X3.298: Limited support.;    Information Technology-AT Attachment-3 Interface (ATA-3)   * o  ANSI X3.39-1986: Recorded Magnetic Tape    (1600 BPI, PE)c  , o  ANSI X3.40-1983: Unrecorded Magnetic Tape  - o  ANSI X3.41-1974: Code Extension Techniquesu    for Use with 7-bit ASCIIt  - o  ANSI X3.42-1975: Representation of Numerica    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 Interfacec  - o  ANSI X3.131-1994 (SCSI II): Small Computer.    System Interfacet  - o  ANSI/IEEE 802.2-1985: Logical Link Controlt  / o  ANSI/IEEE 802.3-1985: Carrier Sense Multiplee"    Access with Collision Detection  2 o  FIPS 1-2: Code for Information Interchange, Its+    Representations, Subsets, and Extensionsa  F    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: Recordedt8    Magnetic Tape Information Interchange (800 CPI, NRZI)  "                                 62 p  D  C o  FIPS 16-1/ANSI X3.15-1976: Bit Sequencing of the Code for Infor-c8    mation Interchange in Serial-by-Bit Data Transmission  '    Note: FED STD 1010 adopts FIPS 16-1..  E o  FIPS 22-1/ANSI X3.1-1976: Synchronous Signaling Rates Between Datai,    Terminal and Data Communication Equipment  '    Note: FED STD 1013 adopts FIPS 22-1.t  F o  FIPS 25/ANSI X3.39-1986: Recorded Magnetic Tape for Information In-&    terchange (1600 CPI, Phase Encoded)  G o  FIPS 37/ANSI X3.36-1975: Synchronous High-Speed Data Signaling RatesDC    Between Data Terminal Equipment and Data Communication Equipment   %    Note: FED STD 1001 adopts FIPS 37.o  F o  FIPS 50/ANSI X3.54-1986: Recorded Magnetic Tape for Information In-8    terchange, 6250 CPI (246 CPMM), Group Coded Recording  C o  FIPS 79/ANSI X3.27-1987: Magnetic Tape Labels and File Structurea    for Information Interchange  C o  FIPS 86/ANSI X3.64-1979: Additional Controls for Use with Ameri-m9    can National Standard Code for Information Interchange   '    Note: Other FIPS are not applicable.s  G    Note: Information regarding interchangeability of ANSI and FED stan-eD    dards with FIPS is contained in "ADP Telecommunications StandardsF    Index," July 1988, published and maintained by the General Services    Administration.  B o  ISO 646: ISO 7-bit Coded Character Set for Information Exchange  E o  ISO 1001: File Structure and Labeling of Magnetic Tapes for Infor-e    mation Interchangef  E o  ISO 1863: Information Processing - 9-track, 12, 7 mm (0.5 in) widetE    magnetic tape for information interchange recorded at 32 rpmm (800e    rpi)e  "                                 63 i  o  G o  ISO 1864: Information Processing - Unrecorded 12, 7 mm (0.5 in) wideaH    magnetic tape for information interchange - 35 ftpmm (800 ftpi) NRZI,G    126 ftpmm (3 200) ftpi phase encoded and 356 ftmm (9 042 ftpi), NRZIF  ; o  ISO 2022: Code Extension Techniques for Use with ISO 646n  / o  ISO 3307: Representations of Time of the Dayc  E o  ISO 3788: Information Processing - 9-track, 12, 7 mm (0.5 in) wide C    magnetic tape for information interchange recorded at 63 rpmm (1P    600 rpt), phase encoded  C o  ISO 4873: 8-Bit Code for Information Interchange - Structure and     Rules for Implementationd  $ o  ISO 5652: Recorded Magtape (6250)  7 o  ISO 6429: Control Functions for Coded Character Setsn  : o  ISO 9316: 1989 (SCSI-1) Small Computer System Interface  F o  ISO 9660: Information Processing - Volume and file structure of CD-    ROM for information exchangel  ; o  ISO 10288: 1994 (SCSI-2) Small Computer System Interface    INSTALLATION  F OpenVMS Alpha is distributed as a binary kit on CD-ROM. Procedures forF setting up the system disk from media and for preparing the system forE day-to-day operations are provided. The procedures use the POLYCENTER F Software Installation utility to configure and install the OpenVMS Al-C pha operating system. These procedures are described in the OpenVMS 2 Alpha Version 7.3 Upgrade and Installation Manual.  C OpenVMS VAX is distributed as binary kits on CD-ROM and tape. Open-CG VMS VAX Version 7.3 is the last OpenVMS release for which TK50 and Mag- F netic tape media will be distributed. Future OpenVMS VAX releases willC be distributed on CD-ROM only. Procedures for setting up the systemtF disk from a kit and for preparing the system for day-to-day operationsE are provided. The procedures are described in the OpenVMS VAX Version.E 7.3 Upgrade and Installation Manual. Computer-specific information ise  "                                 64 ,  d  C contained in the upgrade and installation supplements for each fam-r ily of VAX computers.     POLYCENTER Software Installation  C The POLYCENTER Software Installation utility simplifies the instal-BF lation and management of OpenVMS products. It is used to install, con-C figure, reconfigure, and deinstall software products that have been C prepared with the utility. In addition, the POLYCENTER utility pro-sD vides a database to track the installation, reconfiguration, and de-C installation of software. For products installed with other instal-gD lation technologies, the POLYCENTER utility provides a mechanism forE adding information about them into the product database. The POLYCEN-tD TER utility also provides the ability to manage dependencies between) products during the installation process.t  D For software providers, the POLYCENTER Software Installation utilityH simplifies the task of packaging software by providing a simple, declar-C ative language for describing material for the installation kit andPF defining how it is installed. The POLYCENTER utility handles the func-F tions, while the developer instructs the utility what to do. This sig-G nificantly reduces the complexity and time to develop installation pro- C cedures. The language allows the developer to easily specify depen-oC dencies on other software, manage objects in the execution environ--E ment (such as files and directories), and anticipate and resolve con- F flict before it occurs. The POLYCENTER utility also significantly sim-D plifies the packaging of multiple software products into one logical product suite.  E For OpenVMS Alpha, you use the POLYCENTER Software Installation util-uC ity to install the operating system and to install layered products / that are compliant with the POLYCENTER utility.r  C For OpenVMS VAX, you use the POLYCENTER Software Installation util-rD ity to install layered products that are compliant with the POLYCEN- TER utility.  	 VMSINSTALi    "                                 65 l  d  E OpenVMS includes the VMSINSTAL facility to handle the installation oftG optional Compaq supplied software products that have not been convertedrE to use the POLYCENTER Software Installation utility. OpenVMS VAX alsocE includes the VMSINSTAL facility to automate operating system softwareS updates.   Test Package and Diagnostics  C OpenVMS includes a User Environment Test Package (UETP), which ver-hG ifies that the OpenVMS operating system is properly installed and ready " for use on the customer's systems.  F You can run diagnostics on individual devices during normal system op-B eration. Certain critical components can operate in degraded mode.  % OpenVMS Alpha DISK SPACE REQUIREMENTSt  ( Operating System Disk Space Requirements  E The disk space requirements for OpenVMS Alpha vary according to whichA options are installed:                                      "                                 66 n  s    C ____________________Space__________________________________________ C File_Category_______Used______Running_Total________________________   $ Minimum OpenVMS      78 MB     78 MB files   $ Optional OpenVMS     106      184 MB files               MB  $ DECwindows           32 MB    216 MB Support   $ Paging file          38 MB    254 MB
 (required)  $ Swap file (sug-       3 MB    257 MB gested)A  $ Dump file (op-       28 MB    285 MB tional)P  $ Decompressed         15 MB    300 MB
 Help files
 (optional)  $ Full DECwindows      159      459 MB Motif Version       MB 1.2-6 (optional)  $ Safeguard for        50 MB    509 MBC upgrading__________________________________________________________   E Note: The minimum OpenVMS files listed in the table will allow you toAC run with minimal functionality. Not all OpenVMS commands and utili-IE ties will function fully as documented in this minimum configuration.aC Not all Compaq and other layered products will work in this minimumB configuration.  F The minimum OpenVMS files are for a system configuration where all op-C tional features have been declined during the initial installation.SC For most applications, this is not a realistic OpenVMS environment.C  "                                 67 l  i  G The paging, swap, and dump file requirements are the minimum for a sys-eC tem with 32 MB of main memory. Additional memory in most cases adds.E to the space needed for these files, as will particular needs of your5E application. With careful system management it is possible to use thea+ paging file space as a temporary dump file.   E For an OpenVMS Cluster system disk, paging, swap, and dump files can-6C not be shared between nodes, so the files must either be duplicatedr1 on the system disk or located on some other disk.1  A Compaq DECwindows Motif for OpenVMS Alpha Disk Space Requirementsa  E To support OpenVMS Alpha and DECwindows Motif for OpenVMS Alpha, Com- E paq recommends a system disk of greater than 550 MB. However, you can E install a subset of DECwindows Motif. The disk space required for thesC installation of DECwindows Motif is 159 MB. The permanent amount of J space used is 145 MB. An additional 33 MB is needed to install the DECwin-F dows X11 Display Server and associated files. (The DECwindows X11 Dis-F play Server and associated files are included in the OpenVMS Alpha op-D erating system media.) These disk space requirements are in additionE to the disk space required for the OpenVMS Alpha operating system, asn= indicated in the OpenVMS Alpha Disk Space Requirements table.i  H Installation of the DECwindows Motif Version 1.2-6 layered product givesC customers the option of installing any or all of the following com-i ponents:  C o  Run-time support base kit - 33 MB. This section provides support"E    for running DECwindows Motif for OpenVMS Alpha applications on Al-aB    pha compute servers and is a required part of the installation.  E o  New Desktop - 24 MB. This is an optional component that allows uselC    of the New Desktop environment. It includes applications and ap-e+    plication programming interfaces (APIs).n  C o  DECwindows desktop - 11 MB. This component is also optional, butiD    you should install either the New Desktop or the DECwindows desk-D    top to create a usable system. The DECwindows desktop is the user    "                                 68 a  f  E    interface that was included in previous versions of DECwindows Mo-0E    tif and includes the DECwindows Session Manager, FileView, and theC    Motif Window Manager.  E o  Programming support - 32 MB. This section includes support for the D    Compaq C, Compaq C++, Compaq Fortran, and Pascal programming lan-C    guages. If you install a subset of languages, the amount of disk(    space required will be less.   ' o  Example files - approximately 26 MB.e  2 o  Translated image support - approximately 20 MB.  ' Layered Product Disk Space Requirements   D In addition to the disk space used directly by Compaq or third-partyD layered products, there may be additional space used to store infor-E mation from those products in OpenVMS help libraries, command tables,iD object libraries, and elsewhere. The amount of additional disk spaceE required cannot be exactly predicted due to the possibility of recov-oE ering unused space already existing in those library files. Unusually H large modules contributed by layered products can also affect the amountC of space required for upgrading to a new version of the OpenVMS Al-d pha operating system.-  # OpenVMS VAX DISK SPACE REQUIREMENTSs  0 Disk Space Requirements (Block Cluster Size = 3)  D To support the complete OpenVMS VAX system, Compaq recommends a sys-C tem disk of greater than 150 MB. When you use a smaller disk, addi-MF tional tailoring is required before installing some of the OpenVMS VAXF options. This does not include the dump file space. Refer to the Open-C VMS VAX Version 7.3 Upgrade and Installation Manual for informationh
 on tailoring.y  ( Operating System Disk Space Requirements      "                                 69 .  .  C The disk space requirements for OpenVMS VAX vary according to which  options are installed.  C ___________________________________________________________________e                     SpaceVC File_Category_______Used______Running_Total________________________S  & 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 (additionald
 files, IN-C DEXF.SYS,_etc.)____________________________________________________r  E Note: The minimum OpenVMS files listed in the table will allow you toiC run with minimal functionality. Not all OpenVMS commands and utili-eE ties will function fully as documented in this minimum configuration.iC Not all Compaq and other layered products will work in this minimumi configuration.  "                                 70 t  n  E The data in the table was created from an installation on a VAXserverv* 2000 with 6 MB of memory and an RD54 disk.  E Additional memory adds to the space required for page, swap, and dump C files, and the variable additional space increases with larger mem-e
 ory and disk.   ? Compaq DECwindows Motif for OpenVMS VAX Disk Space Requirementsf  D To support OpenVMS VAX and the DECwindows Motif for OpenVMS VAX lay-E ered product, Compaq recommends a system disk of greater than 300 MB.iC The disk space required for the installation of DECwindows Motif iseD 60 MB. The permanent amount of space used is 54 MB. An additional 16D MB are needed to install the DECwindows X11 Display Server and asso-E ciated files. (The DECwindows X11 Display Server and associated files D are included in the OpenVMS VAX Version 7.3 media.) These disk spaceE requirements are in addition to the disk space required for the Open-pE VMS VAX Version 7.3 operating system, as indicated in the OpenVMS VAXN Disk Space Requirements table.  H Installation of the DECwindows Motif Version 1.2-6 layered product givesC customers the option of installing any or all of the following com-  ponents:  F o  Run-time support files base kit - 41 MB. This section provides sup-D    port for running DECwindows Motif for OpenVMS VAX applications onE    VAX compute servers and is a required part of the installation. Itg>    includes the DECwindows desktop applications and libraries.  D o  Programming support - 7 MB. This section includes support for theC    Compaq C, Compaq C++, Compaq Fortran, Pascal, and VAX C program-oD    ming languages. If a subset of languages is installed, the amount"    of disk space required is less.  & o  Example files - approximately 7 MB.  D Note that the individual sizes add up to more than the total becauseC some components are shared by multiple portions of the environment.     "                                 71 i      MEMORY SPACE REQUIREMENTS   ' OpenVMS Alpha Memory Space Requirementsn  E The minimum amount of memory required to install, boot, and log in to C 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 configurationsi  D Refer to specific layered product documentation for their memory re- quirements.n  % OpenVMS VAX Memory Space Requirements_  E The minimum amount of memory required to install, boot, and log in to F an OpenVMS VAX system is 14 MB. To ensure satisfactory performance forD particular applications or number of users, additional memory may beC required. Refer to specific layered product documentation for theirr memory requirements.   DISTRIBUTION AND BACKUP MEDIAM  
 OpenVMS Alpha   D OpenVMS Alpha is available on CD-ROM only. The OpenVMS Alpha VersionE 7.3 Binary CD-ROM contains the operating system binaries and selectedrE documentation in both text and PostScript format. The OpenVMS VersionlE 7.3 Online Documentation CD-ROM contains all OpenVMS manuals in .HTMLrF and .PDF formats. Associated product manuals are in .HTML and selected0 product and archived manuals are in .PDF format.  G The OpenVMS Documentation CD-ROM is a dual-formatted system CD-ROM thattE can be mounted and read on both an OpenVMS system and a Windows 95 or F Windows NT PC system. An InfoServer or local drive is required for up- grades and system disk backups.   C The OpenVMS Alpha operating system is also available as part of thes8 OpenVMS Alpha Software Products Library CD-ROM offering.  "                                 72 t  e   OpenVMS VAXD  F OpenVMS VAX is available on CD-ROM, TK50, or 9-track 6250 BPI magneticF tape media. The 9-track 6250 BPI magnetic tape media is available onlyD through the OpenVMS VAX media and hardcopy documentation update ser-C vice. OpenVMS VAX Version 7.3 is the last OpenVMS release for whicht1 TK50 and Magnetic tape media will be distributed.X  G The OpenVMS VAX Version 7.3 Binary CD-ROM contains the OpenVMS VAX Ver-eF sion 7.3 save sets, OpenVMS VAX Version 7.3 standalone BACKUP, and se-E lected OpenVMS documentation in text and PostScript format. The Open- E VMS Version 7.3 Online Documentation CD-ROM contains all OpenVMS man-nG uals in .HTML and .PDF formats. Associated product manuals are in .HTML = and selected product and archived manuals are in .PDF format.   G The OpenVMS Documentation CD-ROM is a dual-formatted system CD-ROM thatRE can be mounted and read on both an OpenVMS system and a Windows 95 orr Windows NT PC system.i  F The TK50 streaming tape contains the OpenVMS VAX Version 7.3 save sets. and OpenVMS VAX Version 7.3 standalone BACKUP.  C The 9-track 6250 BPI magnetic tape contains the OpenVMS VAX Version  7.3 save sets.  G The OpenVMS VAX operating system is also available as part of the Open-a2 VMS VAX Software Products Library CD-ROM offering.  
 DOCUMENTATION   D For OpenVMS Version 7.3, documentation is available in the following formats:  
 Printed Booksa  C OpenVMS printed documentation is available in two sets: the OpenVMS > Full Documentation Set and the OpenVMS Base Documentation Set.      "                                 73 t  a  C The Full Documentation Set is for users who need extensive explana-fC tory information on all major OpenVMS resources, complete referenceuF information on system routines and utilities, detailed examples, Open-E VMS Cluster guidelines, programming concepts, a master index, and in-eG formation on the Help Message utility. This set meets the needs of sys-aC tem managers and of system and application programmers. It includes0 the Base Documentation Set.S  F The Base Set includes the most commonly used OpenVMS manuals, address-F ing the needs of general users and system managers of small standaloneF systems. Manuals, such as the Release Notes, New Features, and the DCL( Dictionary are included in the Base Set.  F Each book in these sets is also separately orderable. A complete list-D ing of all hardcopy manuals and their part numbers is in the OpenVMS; Version 7.3 New Features and Documentation Overview manual.t   Online Books  E For Version 7.3, online documentation is provided on the OpenVMS Doc-oF umentation CD-ROM, an ISO9660 CD-ROM that can be read on OpenVMS, Win- dows, and Macintosh systems.  F The OpenVMS Version 7.3 Online Documentation CD-ROM contains all Open-E VMS manuals in .HTML and .PDF formats. Associated product manuals arenC in .HTML and selected product and archived manuals are in .PDF for-u mat.   GROWTH CONSIDERATIONSt  E The minimum hardware and software requirements for any future version C of this product may be different from the requirements for the cur- 
 rent version.n              "                                 74 n      SOURCE LISTINGS   D OpenVMS Alpha and VAX Operating System Source Listings are availableF on CD-ROM. These discs contain source listing files and the Alpha spe-C cific debug symbol files that make up the OpenVMS operating system. D Compaq provides source listings for key modules of the OpenVMS oper-E ating system that are appropriate for end users or application devel- E opers. The debug symbol files (DSF) on the OpenVMS Alpha Source List- E ings CD-ROM contain information used by the OpenVMS Alpha System-CodeiE Debugger. Certain company confidential source listings and debug sym-w1 bol files, however, are excluded from the CD-ROM.   D The orderable CD-ROM kit includes the license required to view theseC files on a standalone system or an OpenVMS Cluster system. If users C want to make these files available to another system (possibly at a - remote site), they must purchase another kit.B   ORDERING INFORMATION   Alpha Software Licenses                                         "                                 75 h  i    ; QL-MT1A*-6*     OpenVMS Alpha Operating System Base Licensei  B QL-MT1A*-7*     OpenVMS Alpha Operating System Base Update License  B QL-MT1A9-6*     OpenVMS Alpha Operating System Symmetric Multipro-4                 cessing (SMP) Base Extension License  B QL-MT1A9-7*     OpenVMS Alpha Operating System Symmetric Multipro-;                 cessing (SMP) Base Extension Update Licenseo  @ QL-MT2A9-**     OpenVMS Alpha Individual User License (No Longer?                 Available...order the Concurrent Use License or '                 Unlimited User License)i  4 QL-MT2A*-AA     OpenVMS Alpha Unlimited User License  < QL-MT2A*-Y*     OpenVMS Alpha Individual User Update License  B QL-MT3A*-B*     OpenVMS Alpha Distributed Interactive User License?                 (No Longer Available...order the Concurrent Use                  License)  A QL-MT3A*-Y*     OpenVMS Alpha Distributed Interactive User Updaten                 License   . QL-MT3A*-3*     OpenVMS Concurrent Use License  5 QL-MT3A*-5*     OpenVMS Concurrent Use Update LicenseD   VAX Software Licensesv  ? QL-001A*-**     VAX VMS Operating System License and Update Li-.!                 cense for OpenVMSm  9 QL-005A*-6*     OpenVMS VAX Operating System Base Licensep  @ QL-005A*-7*     OpenVMS VAX Operating System Base Update License  @ QL-005A9-6*     OpenVMS VAX Operating System Symmetric Multipro-4                 cessing (SMP) Base Extension License  @ QL-005A9-7*     OpenVMS VAX Operating System Symmetric Multipro-;                 cessing (SMP) Base Extension Update Licensen  > QL-XULA9-**     OpenVMS VAX Individual User License (No Longer?                 Available...order the Concurrent Use License or '                 Unlimited User License)   "                                 76 r  .    2 QL-XULA*-AA     OpenVMS VAX Unlimited User License  ; QL-XULA*-Y*     OpenVMS VAX Interactive User Update Licensea  @ QL-09SA*-**     OpenVMS VAX Distributed Interactive User License?                 (No Longer Available...order the Concurrent Use                  License)  ? QL-09SA*-Y*     OpenVMS VAX Distributed Interactive User Updatee                 Licenseo  . QL-MT3A*-3*     OpenVMS Concurrent Use License  5 QL-MT3A*-5*     OpenVMS Concurrent Use Update License   3 Alpha and VAX CD-ROM Media and Online Documentationa  ? QA-MT1AA-H8     OpenVMS Alpha software and online documentationl                 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)i  > QA-MT1AD-H8     OpenVMS Alpha Version 7.1-1H2 software and on->                 line documentation CD-ROM. (QA-MT1AA-H8.7.1 is                 required)o  ? QA-MT1AR-H8     OpenVMS Alpha Version 7.1-2 software and online $                 documentation CD-ROM  ? QA-MT1AT-H8     OpenVMS Alpha Version 7.2-1 software and onlinem$                 documentation CD-ROM  A QA-MT1AU-H8     OpenVMS Alpha Version 7.2-1H1 software and online $                 documentation CD-ROM  = QA-XULAA-H8     OpenVMS VAX software and online documentationV                 CD-ROM  @ QA-MT3AA-H8     OpenVMS VAX/Alpha software and online documenta-                 tion CD-ROMP  = QA-MT3AE-G8     OpenVMS VAX/Alpha online documentation CD-ROMC  "                                 77 M     $ VAX Media and Hardcopy Documentation  B QA-09SAA-H8     OpenVMS VAX Software CD-ROM and Base Documentation                 Setn  @ QA-09SAA-H5     OpenVMS VAX Software TK50 and Base Documentation                 Set   B QA-001AA-H8     OpenVMS VAX Software CD-ROM and Full Documentation                 Setl  @ QA-001AA-H5     OpenVMS VAX Software TK50 and Full Documentation                 Setn   Hardcopy Documentation Setsa  . 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 License5  ; QB-001AB-E8     OpenVMS VAX Listings CD-ROM Kit and Licensem  8 OpenVMS Alpha Software Products Library CD-ROM Offerings  ? QA-5FX8A-A8     OpenVMS Alpha Software Layered Products and Op-t@                 erating System Library (Software Layered Product?                 binaries only-no online documentation, complete %                 Operating System kit)3  : QA-4KM8A-G8     OpenVMS Alpha Online Documentation Library  ? QA-5G98A-H8     OpenVMS Alpha Software Layered Products and Op-p@                 erating System Library Package (Software Layered?                 Product binaries and online documentation, com-n+                 plete Operating System kit)a  @ QA-03XAA-H8     OpenVMS Alpha Software Library Package (SoftwareB                 Layered Product binaries and online documentation)  "                                 78    o  6 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)a  8 QA-VYR8A-G8     OpenVMS VAX Online Documentation Library  A QA-YL48A-H8     OpenVMS VAX Software Layered Products and Operat-iB                 ing System Library Package (Software Layered Prod-?                 uct binaries and online documentation, completel%                 Operating System kit)   > QA-5G88A-H8     OpenVMS VAX Software Library Package (SoftwareB                 Layered Product binaries and online documentation)  % Software Update Distribution Servicesn  C Provides an automatic distribution of software media and documenta-u tion update. Choices include:e  ' o  Media and Documentation Distributionc   o  Documentation Distributiono  > o  Consolidated Software Engineering Change Order Distribution  1 o  Consolidated Distribution of Software Binariesr  E o  Consolidated Distribution with Software Binaries and Documentatione  $ o  Consolidated Online Documentation  C For additional ordering and pricing information, contact your local  Compaq Account Representative.  4 CD-ROM Media and Online Documentation Update Service  ? QT-MT1AA-E8     OpenVMS Alpha software and online documentationa                 CD-ROM  = QT-XULAA-E8     OpenVMS VAX software and online documentationm                 CD-ROM  B QT-MT3AA-E8     OpenVMS VAX and Alpha software and online documen-                 tation CD-ROMn  "                                 79 S  c  * 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 SetT  + QT-001A*-E*     With Full Documentation Sete   OpenVMS Source Listings ServiceI  5 QT-MT1AB-Q8     OpenVMS Alpha Source Listings Servicen  3 QT-001AB-Q8     OpenVMS VAX Source Listings Servicee  F *  Denotes variant fields. For additional information on available li-E    censes, services, and media, refer to the appropriate Compaq price     book.  6 OpenVMS Alpha Software Products Library CD-ROM Service  ? QT-5FX8A-C8     OpenVMS Alpha Software Layered Products and Op-i@                 erating System Library (Software Layered Product?                 binaries only-no online documentation, completeo%                 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-e+                 plete Operating System kit)   @ QT-03XAA-C8     OpenVMS Alpha Software Library Package (SoftwareB                 Layered Product binaries and online documentation)  4 OpenVMS VAX Software Products Library CD-ROM Service  "                                 80    c    ? 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)   8 QT-VYR8A-C8     OpenVMS VAX Online Documentation Library  A QT-YL48A-C8     OpenVMS VAX Software Layered Products and Operat- B                 ing System Library Package (Software Layered Prod-?                 uct binaries and online documentation, completee%                 Operating System kit)s  > QT-5G88A-C8     OpenVMS VAX Software Library Package (SoftwareB                 Layered Product binaries and online documentation)   SOFTWARE LICENSING  D The OpenVMS operating system software is furnished under the licens-G ing provisions of Compaq Computer Corporation's Standard Terms and Con- E ditions. The OpenVMS Version 7.3 Online Documentation CD-ROM contains F all OpenVMS manuals in .HTML and .PDF formats. Associated product man-G uals are in .HTML and selected product and archived manuals are in .PDFs  ) Software License Information (Alpha Only)3  D The OpenVMS Alpha operating system license includes the right to useE OpenVMS Alpha licenses for multiple instances of OpenVMS on the first E and then once again on each subsequent hard partition of a single Al-  phaServer GS80/160/320 system.  D The OpenVMS Alpha operating system license includes the right to useE Compaq DECprint Supervisor (DCPS) for OpenVMS products (-Base, -Open,pC and -Plus). The DECprint Supervisor (DCPS) for OpenVMS has separateeC documentation, media kit, and service products. Refer to the CompaqmK DECprint Supervisor for OpenVMS Software Product Description (SPD 44.15.xx)n for more information.n      "                                 81       E The right to use the DCE Run-time Services is included with the Open- G VMS base operating system license. Refer to the Compaq Distributed Com- D puting Environment (DCE) Software Product Description (SPD 43.05.xx)D for more detailed information on the DCE for OpenVMS product family.  G The right to use Compaq Capacity On Demand for OpenVMS is included withA* the OpenVMS base operating system license.  D The following technologies are licensed as part of the OpenVMS Alpha operating system:                                                             "                                 82 o  r    C ___________________________________________________________________t  " Attunity Con-         SPD 80.58.xx nect "On Plat- form" Package forl
 OpenVMS Alpha   " Compaq COM for        SPD 70.45.xx
 OpenVMS Alpha-  " Compaq BridgeWorks    SPD 80.58.xx  " Compaq Secure Web     SPD 80.58.xx Server for OpenVMS Alpha   " ECP Data Collector    SPD 80.88.00 for OpenVMS   " ECP Performance       SPD 80.89.00 Analyzer for OpenVMSs  " Extensible Markup     SPD 80.58.xx Language (XML)
 Technology  " Java 2 Software       SPD 80.58.xx Development Kit  for OpenVMS Alphap  " Netscape FastTrack    SPD 80.58.xx Server for OpenVMS Alphao  " OpenVMS Enter-        SPD 40.77.xx prise Directorys for e-Business (LDAPv3/X.500)  " Reliable Transac-     SPD 51.04.xx tion Router (AlphaC and_VAX)___________________________________________________________u  / The following are separately licensed products:t  "                                 83         C ___________________________________________________________________t  " Compaq Advanced       SPD 30.50.xx Server for OpenVMS  " Compaq DECnet-Plus    SPD 25.03.xx for OpenVMS VAX   " Compaq DECnet-Plus    SPD 50.45.xx for OpenVMS AlphaD  " Compaq DECnet for     SPD 48.48.xx OpenVMS VAX and- Alpha   " Compaq DECram for     SPD 34.26.xx OpenVMS0  " Compaq DECwindows     SPD 42.19.xx Motif for OpenVMSi  " Compaq Galaxy         SPD 70.44.xx Software Architec- ture on OpenVMS  Alphac  " Compaq PATHWORKS      SPD 30.50.xx for OpenVMS (Ad- vanced Server)  " Compaq OpenVMS        SPD 29.78.xx Cluster Software  " Compaq RMS Jour-      SPD 27.58.xx naling for OpenVMS  " Compaq TCP/IP         SPD 46.46.xx Services for OpenVMSi  " Compaq Volume         SPD 27.29.xx
 Shadowing fornC OpenVMS____________________________________________________________   ' Software License Information (VAX Only)n  "                                 84 M  f  E The OpenVMS VAX operating system uses one of two different categoriestF of licenses depending on the hardware and software configurations usedE and currently supported. This information is also provided in the ap-  plicable country's Price List.  C These are the two categories of operating system licenses for Open-H VMS VAX:   o  VAX VMS Licensing   o  OpenVMS VAX Licensing   System Support Servicesb  E Compaq provides the proper license type with the purchase of the sys-n@ tem. Not all license types are available for every system model.   VAX VMS License Informationl  I Note: Effective February 6, 1995, the VAX VMS (UPI001) licenses no longeriF include the rights for the Oracle Rdb Run-Time option for OpenVMS VAX,G and do not permit use of Rdb Run-time on prior versions of OpenVMS VAX.H  C Each of the following licenses are for a specified hardware system, E which is either the system the license was originally shipped with ors/ 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**-**)  4 o  Traditional License for OpenVMS VAX (QL-001**-**)  ) There are four types of VAX VMS licenses:y  ( All use the LMF Product Name of VAX-VMS.  $ 1. Traditional License (QL-001A*-**)  E This type of license provides unlimited use to the users on a definedLD system. VAX VMS traditional licenses are sized to capacity according to system type.t  # 2. Multi-User License (QL-001A*-**)r  "                                 85 i  o  D This type of license provides use according to a specified number ofC concurrent users. This is an activity-based license. The Multi-UseroF License provides the customer with the right to use the operating sys-C tem up to the limit of users specified in the license. An operatingiC system user is a person who is logged in to the system and is usingeC the system interactively. This license is only available on limitedt7 system models, primarily MicroVAX and VAX 4000 systems.   F The customer can increase interactive use of VAX systems licensed withE the Multi-User License by the addition of OpenVMS User Licenses* (forMD one or more users). Refer to the section on Ordering Information for further information.  , 3. VAX VMS Workstation License (QL-001A*-**)  E This type of license provides use for a single user on a VAX worksta- C tion. This license type allows one direct login for the single usere= and one additional login for system management purposes only.K  D Additional interactive use of VAX workstations licensed with the VAXD VMS Workstation License requires the addition of an OpenVMS User Li-D cense* (for one or more users). Refer to the section on Ordering In-" formation for further information.  4 4. File and Application Server License (QL-001A*-**)  D This type of license provides for the noninteractive use of OpenVMS.  D OpenVMS based VAXserver systems are sold with a File and ApplicationC Server License. The intent of an OpenVMS based VAXserver is to pro-hG vide file, print, application, and compute services to clients who havehF submitted their requests remotely (for example via network/remote sub-D mit/batch jobs, and so forth). This license type also allows one di-/ rect login for system management purposes only.t  E Additional interactive use of OpenVMS VAXserver systems licensed withbC the File and Application Server License requires the addition of anpC OpenVMS User License* (for one or more users). Refer to the section 0 on Ordering Information for further information.  "                                 86 r  n  C These licenses grant the right to use the same version of the oper-eG ating system software as permitted for the corresponding Operating Sys-t@ tem Base License at the time when the User License is installed.  F Notes: Not all VAX VMS license types are available for all versions of  VMS, OpenVMS, or all VAX models.  D 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:i  : 1. OpenVMS VAX Operating System Base License (QL-005A*-**)  ! LMF Product Name: BASE-VMS-250136n  C OpenVMS VAX Operating System Base License grants the right to unre-iD stricted, noninteractive use of the OpenVMS VAX operating system forE the execution of remotely submitted requests for batch, print, appli-oG cation, and computing services, on a designated, single processor. This)H license authorizes one direct login for system management purposes only.  C The OpenVMS VAX Base License does not include the license right fort/ the Oracle Rdb Run-Time Option for OpenVMS VAX.i  D The Operating System Base License is a prerequisite for all Interac-7 tive User Licenses and all SMP Base Extension Licenses.   F Interactive use of systems licensed with an OpenVMS VAX Operating Sys-F tem Base License requires the addition of an OpenVMS User License (forD one or more users). Refer to the section on Ordering Information for further information.  D This license grants the right to use the same version of the operat-E ing system software as permitted for the corresponding Operating Sys-t@ tem Base License at the time when the User License is installed.    "                                 87 -  n  C The OpenVMS VAX Operating System Base License also includes the li-eD cense for DECprint Supervisor for OpenVMS VAX. The DECprint Supervi-D sor for OpenVMS VAX has separate documentation, media kits, and ser-9 vice products. Refer to SPD 44.15.xx for further details.   1 2. Symmetric Multiprocessing (SMP) Base Extensionn    License (QL-005A9-6*)  ! LMF Product Name: BASE-VMS-250136s  C SMP Base Extensions extend the Operating System Base License to en-tE able symmetric multiprocessing capability on a select number of Open-nC VMS VAX systems supporting SMP. SMP Base Extensions are permanentlyCF tied to the Operating System Base License and cannot be separated fromE the Operating System Base License if an SMP board is removed from thes system.t  C SMP Extensions grant the right to use the same version of the oper- G ating system software as permitted for the corresponding Operating Sys- ? tem Base License at the time when the SMP Extension is granted._  & 3. OpenVMS VAX Individual User License    (QL-XULA*-**)   LMF Product Name: VMS-USER  D The OpenVMS VAX Individual User License provides the right to inter-D actively use the operating system by the specified or unlimited num-D ber of concurrent users on a designated, single processor. A user isF an individual who is logged in to a processor and is interactively us-G ing the operating system software by means other than a login. An Open-rE VMS VAX Operating System Base License or one of the five types of VAXFE VMS Licenses (QL-001A*-**) is a prerequisite for the OpenVMS User Li-  cense.  D This license grants the right to use the same version of the operat-E ing system software as permitted for the corresponding Operating Sys-_@ tem Base License at the time when the User License is installed.    "                                 88       F The OpenVMS VAX Operating System Base, the SMP Base Extension, and In-C teractive User licenses are not supported by the VMS or OpenVMS VAXe; operating system releases prior to OpenVMS VAX Version 5.5.p  3 4. OpenVMS VAX Distributed Interactive User Licensep    (QL-09SA*-**)   LMF Product Name: ADL-USER  C This license grants the right to interactive use of the OpenVMS VAXnD operating system, provided the appropriate Operating System Base Li-F cense or one of the five types of VAX VMS Licenses has been previouslyD installed on a VAX system. The Distributed Interactive User licensesE are concurrent-use licenses and are available in any quantity, exceptqD unlimited. Distributed Interactive User licenses are mobile (and canF be redesignated) and may be installed and used on a single OpenVMS VAX3 processor or shared in a single OpenVMS VAXcluster._  H A distributed interactive user is defined as an individual who is loggedE in to an OpenVMS VAX processor or OpenVMS VAXcluster system or is in- C teractively using the operating system software by means other thane a login.  D This license grants the right to use the same version of the operat-E ing system software as permitted for the corresponding Operating Sys-e@ tem 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-ADLe  C This license grants the right to interactive use of the OpenVMS op-lF erating system, provided the appropriate OpenVMS Operating System BaseF License is installed on an OpenVMS VAX processor, or on an OpenVMS Al-D pha processor, or on OpenVMS VAX processors if one of the five typesF of VAX VMS Licenses has been previously installed on a VAX system. TheE OpenVMS Concurrent-Use Licenses are available in any quantity desirediE except unlimited. OpenVMS Concurrent-Use Licenses are mobile (and canaF be redesignated) and may be installed and used on a single OpenVMS VAX  "                                 89 1  *  E or OpenVMS Alpha processor, or shared in a single OpenVMS VAXcluster, ? a single OpenVMS Cluster, or shared in a mixed OpenVMS Cluster.o  C A user that enables a Concurrent-Use License is defined as an indi-MF vidual who is logged in to an OpenVMS VAX processor, or an OpenVMS Al-D pha processor, or an OpenVMS VAXcluster, or an OpenVMS Cluster, or aC mixed OpenVMS Cluster and/or is interactively using the OpenVMS op-M4 erating system software by means other than a login.  C When an OpenVMS VAX SMP System upgrade is performed, the SMP Exten- E sion to the OpenVMS Alpha Operating System License permits the use ofiG all existing Distributed Interactive User Licenses on the upgraded sys-s tem.  D The Operating System Base License provides the right to use only theD OpenVMS features of the current or prior versions of the OpenVMS op- erating system.   D This license grants the right to use the same version of the operat-E ing system software as permitted for the corresponding Operating Sys-i@ tem Base License at the time when the User License is installed.  ! OpenVMS Alpha License Information   C There are five types of OpenVMS licenses available on Alpha proces-i sors:r  . 1. Operating System Base License (QL-MT1A*-6*)   LMF Product Name: OpenVMS-ALPHAh  H This license grants the right to noninteractive use of the remote batch,C print, application, and computing services of the OpenVMS Alpha op-nE erating system on a single processor. This license authorizes one di-iG rect login for system management purposes only. For dual processor sys- D tems (Compaq AlphaServer 8200, 8400 and the AlphaServer GS60, GS60E,H and GS140), the base license for these specific systems grants the rightG to noninteractive use of the remote batch, print, application, and com- D puting services of the OpenVMS Alpha operating system on a dual pro- cessor.   "                                 90 i  a  D The Operating System Base License is a prerequisite for OpenVMS User) Licenses and SMP Base Extension Licenses.,  D The Operating System Base License provides the right to use only theD OpenVMS features of the current or prior versions of the OpenVMS Op- erating System.   D 2. Symmetric Multiprocessing (SMP) Base Extension License (QL-MT1A9-    6*)   LMF Product Name: OpenVMS-ALPHA   C SMP Base Extensions extend the Operating System Base License to en-sE able symmetric multiprocessing capability on those OpenVMS Alpha sys-uD tems supporting SMP. SMP Base Extensions are permanently tied to theC Operating System Base License and may not be separated from the Op-sD erating System Base License if an SMP board is removed from the sys- tem.  C SMP Extensions grant the right to use the same version of the oper-eG ating system software as permitted for the corresponding Operating Sys-S? tem Base License at the time when the SMP Extension is granted.r  ( 3. Individual User License (QL-MT2A*-**)       (No Longer Offered)p  $ LMF Product Name: OpenVMS-ALPHA-USER  C This license grants the right to interactive use of the OpenVMS Al-tD pha operating system, provided the appropriate Operating System BaseF License has been previously installed on the OpenVMS Alpha system. TheD Individual User Licenses are available in any quantity desired or as an unlimited user license.  E Individual User Licenses can be redesignated and may be installed andfE used on a single OpenVMS Alpha processor only. They may not be sharedpD in a single OpenVMS Cluster environment. A user is defined as an in-D dividual who is logged in to an OpenVMS Alpha processor or is inter-F actively using the operating system software by means other than a lo- gin.  "                                 91    r  D This license grants the right to use the same version of the operat-E ing system software as permitted for the corresponding Operating Sys-s@ tem Base License at the time when the User License is installed.  C 4. OpenVMS Alpha Distributed Interactive User License (QL-MT3A*-**)r       (No Longer Offered)   # LMF Product Name: OpenVMS-ALPHA-ADLm  C This license grants the right to interactive use of the OpenVMS Al-oD pha operating system, provided the appropriate Operating System BaseE License has been previously installed on an Alpha system. The ADL In-eE teractive User Licenses are concurrent-use licenses and are availablepG in any quantity desired except unlimited. ADL Interactive User LicensespC can be redesignated and may be installed and used on a single Open-aC VMS Alpha processor, or shared in a single OpenVMS Cluster environ-t ment.4  H A distributed interactive user is defined as an individual who is loggedG in to an OpenVMS Alpha processor or OpenVMS Cluster or is interactively @ using the operating system software by means other than a login.  D This license grants the right to use the same version of the operat-E ing system software as permitted for the corresponding Operating Sys-C@ tem Base License at the time when the User License is installed.  E 5. OpenVMS Concurrent-Use License (for both VAX and Alpha) (QL-MT3A*-     3*)  # LMF Product Name: OPENVMS-ALPHA-ADLt  C This license grants the right to interactive use of the OpenVMS op-tF erating system, provided the appropriate OpenVMS Operating System BaseD License in installed on an OpenVMS VAX processor, and/or on an Open-D VMS Alpha processor, or on OpenVMS VAX processors if one of the fiveE types of VAX VMS Licenses has been previously installed on a VAX sys-tC tem. The OpenVMS Concurrent-Use Licenses are available in any quan-rF tity desired except unlimited. OpenVMS Concurrent-Use Licenses are mo-D bile (can be redesignated) and may be installed and used on a singleC OpenVMS VAX or OpenVMS Alpha processor, or shared in a single Open-pD VMS VAXcluster, a single OpenVMS Cluster, or shared in a mixed Open- VMS Cluster.  "                                 92 e  i  C A user that enables a Concurrent-Use License is defined as an indi-tF vidual who is logged in to an OpenVMS VAX processor, or an OpenVMS Al-D pha processor, or an OpenVMS VAXcluster, or an OpenVMS Cluster, or aC mixed OpenVMS Cluster and/or is interactively using the OpenVMS op- 4 erating system software by means other than a login.  E When an Alpha SMP System upgrade is performed, the SMP Base ExtensioneD to the OpenVMS Alpha Operating System License permits the use of all. existing User Licenses on the upgraded system.  D This license grants the right to use the same version of the operat-E ing system software as permitted for the corresponding Operating Sys-v@ tem Base License at the time when the User License is installed.  # License Management Facility Supporte  C The OpenVMS operating system supports the Compaq License Managemente Facility (LMF).o  E If an OpenVMS license is not registered and activated using LMF, onlyeF a single login is permitted for system management purposes through the system console (OPA0:).e  E Several of the VAX VMS and OpenVMS VAX license types are based on theMC number of concurrent users, called an activity license. Every prod-iE uct has the option to define an activity as related to the LMF. Open-tF VMS Interactive User and ADL Interactive User Licenses define the num-D ber of concurrent users who have activity licenses as defined by theD LMF. OpenVMS defines activities, sometimes referred to as an OpenVMS user, as follows:e  E o  Each remote terminal connection is considered an activity. This islA    true even if users set host to their local nodes (SET HOST 0).   D o  Each connection from a terminal server is considered an activity.  C o  A multiple-window session on a workstation is considered one ac-m/    tivity, regardless of the number of windows.e  - o  A batch job is not considered an activity.o  "                                 93 o  o  E o  A remote network connection (a connection other than a remote ter- 3    minal connection) is not considered an activity.p  F For more information about Compaq's licensing terms and policies, con-( tact your Compaq Account Representative.   SOFTWARE PRODUCT SERVICESr  C A variety of service options are available from Compaq. System Sup- E port Services provides integrated hardware and software remedial sup- E port, telephone advisory support, and the right-to-use new version ofrD kernel software. For more information, contact your local Compaq Ac- count Representative.e   SYSTEMS SUPPORTEDl   Alpha Systems Supportedn  F This section lists the Alpha systems that are supported by OpenVMS Al-D pha Version 7.3. Refer to the appropriate page at the following web-F site for details concerning Alpha hardware configurations and options:0 http://www.compaq.com/alphaserver/configure.html   TURBOchannel Bus-Based Systems  & o  DEC 3000 Models 300/300L/300LX/300X   o  DEC 3000 Models 400/400Si    o  DEC 3000 Models 500/500S/500X   o  DEC 3000 Models 600/600Sd   o  DEC 3000 Models 700/700LX   o  DEC 3000 Models 800/800Sr   o  DEC 3000 Models 900/900LX   DSSI Bus-Based Systems   o  DEC 4000 Model 600V  "                                 94 g  t   o  DEC 4000 Model 700m   XMI Bus-Based Systems   % o  AlphaServer 8400 (All chip speeds)c   o  DEC 7000 Model 600s   o  DEC 10000 Model 600   PCI Bus-Based Systemsn  $ o  AlphaServer 300 (All chip speeds)  $ o  AlphaServer 400 (All chip speeds)  $ o  AlphaServer 800 (All chip speeds)  % o  AlphaServer 1000 (All chip speeds)e  & o  AlphaServer 1000A (All chip speeds)  % o  AlphaServer 1200 (All chip speeds)h  3 o  AlphaServer 2000 (All chip speeds, except 5/375)n  3 o  AlphaServer 2100 (All chip speeds, except 5/375)l  4 o  AlphaServer 2100A (All chip speeds, except 5/375)  ) o  AlphaServer 2100A LP (All chip speeds)e  % o  AlphaServer 4000 (All chip speeds)e  % o  AlphaServer 4100 (All chip speeds),  % o  AlphaServer 8200 (All chip speeds)n  % o  AlphaServer 8400 (All chip speeds)i   o  Compaq AlphaServer DS10   o  Compaq AlphaServer DS10Lm   o  Compaq AlphaServer DS20   o  Compaq AlphaServer DS20Et   o  Compaq AlphaServer ES40  "                                 95        o  Compaq AlphaServer GS60   o  Compaq AlphaServer GS60Ee   o  Compaq AlphaServer GS80   o  Compaq AlphaServer GS140    o  Compaq AlphaServer GS160r   o  Compaq AlphaServer GS320d  + o  DIGITAL 2100 Server Model A500MP, A600MPo  % o  AlphaStation 200 (All chip speeds)e  % o  AlphaStation 250 (All chip speeds)c    o  AlphaStation 255/233, 255/300  % o  AlphaStation 400 (All chip speeds)c  2 o  AlphaStation 500/266, 500/333, 500/400, 500/500  % o  AlphaStation 600 (All chip speeds)   & o  AlphaStation 600A (All chip speeds)   o  DPWau 433au, 500au, 600au   o  Compaq AlphaStation DS20e   o  Compaq AlphaStation ES40t  ! o  Compaq AlphaStation XP900/DS10    o  Compaq AlphaStation XP1000s  E The following are the Compaq semiconductor microprocessor developmente, reference boards supported by OpenVMS Alpha:  1 o  Alpha 21064/21064A PCI reference board (EB64+)s  * o  Alpha 21164 PCI reference board (EB164)  % o  Alpha PC64 reference board (APC64)   "                                 96 a  s  " Compaq 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-1000t   VAX Systems Supporteda  C This section of the SPD lists the VAX systems that are supported by E OpenVMS VAX Version 7.3. Refer to the Systems and Options Catalog andeF the Network and Communications Buyers Guide for details concerning VAX$ hardware configurations and options.   Q-bus Based Systems    o  MicroVAX II    o  MicroVAX 3300, VAXserver 3300    o  MicroVAX 3400, VAXserver 3400  C o  MicroVAX 3500, VAXserver 3500, VAXstation 3500, VAXstation 3520,g    VAXstation 3540    o  MicroVAX 3600, VAXserver 3600    o  MicroVAX 3800, VAXserver 3800    o  MicroVAX 3900, VAXserver 3900  0 o  VAX 4000, Models 100, 200, 300, 400, 500, 600  F o  VAX 4000, Models 50, 100A, 105A, 106A, 108, 500A, 505A, 600A, 700A,    705A,  1 o  VAXserver 4000, Models 200, 300, 400, 500, 600    XMI Bus-Based Systemsi  - o  VAX 6000 Series, Models 210, 220, 230, 240V  "                                 97 e     7 o  VAX 6000 Series, Models 310, 320, 330, 340, 350, 360a  7 o  VAX 6000 Series, Models 410, 420, 430, 440, 450, 460i  7 o  VAX 6000 Series, Models 510, 520, 530, 540, 550, 560r  7 o  VAX 6000 Series, Models 610, 620, 630, 640, 650, 660e  F o  VAXserver 6000, Models 210, 220, 310, 320, 410, 420, 510, 520, 610,    620, 630o  E o  VAX 7000, Models 610, 620, 630, 640, 650, 660, 710, 720, 730, 740,u)    750, 760, 810, 820, 830, 840, 850, 860a  1 o  VAX 10000, Models 610, 620, 630, 640, 650, 660s  $ Special System-Specific Internal Bus  . o  MicroVAX 3100, Models 10, 10E, 20, 20E, 30,!    40, 80, 85, 88, 90, 95, 96, 98i  * o  VAXserver 3100, Models 10, 10E, 20, 20E  ) o  VAXstation 4000, Models 60, 90, 95, 96e   o  VAXstation 4000-VLC  . o  VAX 9000, Models 110, 110VP[5], 210, 210VP,
    310, 310VP    System Restrictions    DECwindows Restrictionso  G The following list describes version-specific restrictions. The DECwin-e9 dows Motif environment is not supported on these systems.c  # MicroVAX I and VAXstation I Systemsr   OpenVMS Restrictions   ____________________    Vector  processor (VP)   "                                 98 g  t  D The final version of OpenVMS VAX that supports the following systems is VMS Version 5.1-1.e  
 VAX-11/725  D OpenVMS VAX Version 6.2 was the final version to support the follow- ing:  
 VAX-11/730
 VAX-11/750
 VAX-11/751
 VAX-11/780
 VAX-11/782
 VAX-11/785	 VAXft 110V	 VAXft 310n	 VAXft 410n	 VAXft 610 	 VAXft 810n
 MicroVAX I VAXstation I  C OpenVMS VAX Version 7.2 is the final version to support the follow-e ing:   MicroVAX IIV% VAXstation II/GPX, VAXstation II/QVSSe9 VAXstation 2000, VAXstation 2000/GPX, VAXstation 2000/MFBi
 MicroVAX 2000A  E OpenVMS VAX Version 7.3 is the last version to support the following:r  2 VAX 8200, VAX 8250, VAXserver 8200, VAXserver 82502 VAX 8300, VAX 8350, VAXserver 8300, VAXserver 83502 VAX 8530, VAXserver 8530, VAX 8550, VAXserver 85502 VAX 8600, VAX 8650, VAXserver 8600, VAXserver 8650 VAX 8700, VAXserver 87000 VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840I VAXserver 8800, VAXserver 8810, VAXserver 8820, VAXserver 8830, VAXserver " 8840, VAX 8842, VAX 8974, VAX 8978  "                                 99 t     3 VAX 9000, Models 110, 110VP, 210, 210VP, 310, 310VPe3 VAX 9000, Models 320, 320VP, 330, 330VP, 340, 340VPa? VAX 9000, Models 410, 410VP, 420, 420VP, 430, 430VP, 440, 440VPs  C OpenVMS Alpha Version 7.3-1 is the last version to support the fol-m lowing:    o  DEC 2000 Models 300/500   o  Tadpole ALPHAbook 1                                                            #                                 100  i  s  
 APPENDIX A  E This appendix describes Compaq Computer Corporation terminals, disks,nD tapes, controllers, graphics, and network options. Some restrictions/ for specific devices are listed, if applicable.g  G Compaq reserves the right to change the number and type of devices sup-(C ported by OpenVMS Alpha, OpenVMS VAX, Compaq DECnet for OpenVMS VAXbE and Alpha, Compaq DECnet-Plus for OpenVMS, Compaq TCP/IP Services forvF OpenVMS, and Compaq OpenVMS Cluster Software. The minimum hardware re-E quirements for future versions and updates of these software productsnC may be different from current hardware requirements. For configura-iF tion details about Alpha or VAX hardware, refer to the Systems and Op-> tions Catalog and the Network and Communications Buyers Guide.  D Refer to the following SPDs for detailed product information: CompaqF DECnet for OpenVMS (SPD 48.48.xx), Compaq DECnet-Plus for OpenVMS (SPDG 50.45.xx, 25.03.xx), Compaq TCP/IP Services for OpenVMS (SPD 46.46.xx),oC Compaq Cluster Software (SPD 29.78.xx), and Compaq Open3D for Open-  VMS Alpha (SPD 45.08.xx).j  & Terminals and Terminal Line Interfaces  C To prevent input from overflowing a buffer, terminals use the ASCIInD control characters DC1 and DC3 for synchronization as defined by theE Compaq DEC STD 111, Revision A. VXT windowing terminals support stan-nC dard ANSI applications and X Windows using the LAT transport proto-  col.  C The following table lists the terminals supported by OpenVMS Alpha:o  * VT200          VT300          VT400 series series         seriesd   VT500          VXT2000 series         seriesy        #                                 101r e  l  A The following table lists the terminals supported by OpenVMS VAX:   ' VT52           VT100          LA seriesl                series   # VT300          VT1000         LQP02t series         seriese   VT200          VT500 series         seriesi  F Terminals on Professional 350, Rainbow 100, and DECmate II systems em- ulate VT100 terminals.  D Only limited support is available for the VT52. The VT131, when run-H ning an application, operates in block mode. When interacting with Open-F VMS VAX and associated utilities, the VT131 operates only in VT100 (or( interactive) mode and not in block mode.  G Note: The VT1000 is a monochrome windowing terminal that supports stan-BD dard ANSI applications and the X Window System. The transport proto-F col supported is LAT for VMS. The product supports 15-inch and 19-inch	 monitors.e   Disks   F The first column lists the disk drive. The second column describes theF device. The third column lists the bus the device is supported on. TheF fourth column lists the minimum required version of OpenVMS Alpha thatC supports these devices. The fifth column lists the minimum required F version of OpenVMS VAX that supports these devices. (NS stands for Not Supported.)i  C ___________________________________________________________________tA                                                               VAX B                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_a  B EF51R[3]       107 MB solid state     DSSI        NS          5.5-?                                                               2   #                                 102a l  S    C ______________________________________________________________VAX__ B                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_   B EF52R[4]       205 MB solid state     DSSI        NS          5.5-?                                                               2   B EF53[4]        267 MB solid state     DSSI        NS          5.5-?                                                               2s  4 ESE-20[3]      120 MB solid state     SDI         NS  B ESE-52[3]      120 MB solid state     SDI         1.0         5.5-?                                                               2S  B ESE-56         600 MB solid state     SDI         1.5         5.5-?                                                               2r  B ESE-58         960 MB solid state     SDI         1.5         5.5-?                                                               2e  @ EZ31           134 MB solid state     SCSI        6.2-1H3     NS  @ EZ32           268 MB solid state     SCSI        6.2-1H3     NS  B EZ51R[3]       100 MB solid state     SCSI        1.5         5.5-?                                                               2S  B EZ54R          467 MB solid state     SCSI        1.5         5.5-?                                                               2t  B EZ58R          855 MB solid state     SCSI        1.5         5.5-?                                                               2   B EZ64           475 MB solid state     SCSI        6.2-1H3     5.5-?                                                               2e  B EZ69           950 MB solid state     SCSI        6.2-1H3     5.5-?                                                               2   B DS-EZ41        134 MB solid state     SCSI        6.2-1H3     6.2-A                                                               1H30  B DS-EZ42        268 MB solid state     SCSI        6.2-1H3     6.2-A                                                               1H3,  B DS-EZ705       536 MB solid state     SCSI        6.2-1H3     6.2-A                                                               1H3e  #                                 103  ,  0    C ______________________________________________________________VAX__6B                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_r  B DS-EZ711       1.07 GB solid state    SCSI        6.2-1H3     6.2-A                                                               1H33  B DS-EZ716       1.6 GB solid state     SCSI        6.2-1H3     6.2-A                                                               1H3e  9 PBXRW-JC       2 GB wide fixed        UltraSCSI   6.2-1H3                 disk9  9 PBXRW-NB       4 GB wide fixed        UltraSCSI   6.2-1H3                 diske  9 PBXRW-SA       9 GB wide fixed        UltraSCSI   6.2-1H3M                disk2  9 PBXRZ-JC       2 GB narrow fixed      SCSI        6.2-1H3o                diskh  9 PBXRZ-NB       4 GB narrow fixed      SCSI        6.2-1H3                 diske  9 PBXRZ-SA       9 GB narrow fixed      SCSI        6.2-1H3a                diskm  A RA60[4]        205 MB removable       SDI         NS          6.1s  A RA70           280 MB fixed           SDI         NS          6.1e  B RA71           700 MB fixed disk      SDI         NS          5.4-?                                                               2   B RA72           1 GB fixed disk        SDI         1.0         5.4-?                                                               2   B RA73           2 GB fixed disk        SDI         1.0         5.5-?                                                               2n  A RA80[3]        128 MB fixed disk      SDI         NS          6.1n  A RA81           456 MB fixed disk      SDI         NS          6.1p  A RA82           622 MB fixed disk      SDI         NS          6.1   A RA90           1.2 GB fixed disk      SDI         1.0         6.13  A RA92           1.5 GB fixed disk      SDI         1.0         6.10  #                                 104A r       C ______________________________________________________________VAX__8B                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_   A RC25[3]        2 disks each 26        Q-bus       NS          6.11                MB (1 fixed and                 1 removable) disk                 drive with shared                spindle  4 RD32[3]        VAX 42 MB fixed        Q-bus       NS                disko  A RD51[3]        10 MB fixed disk       Q-bus       NS          6.1o  A RD52[3]        31 MB fixed disk       Q-bus       NS          6.1   4 RD53[3]        71 MB fixed disk       Q-bus       NS  4 RD54[4]        159 MB fixed disk      Q-bus       NS  A RF30[4]        150 MB fixed disk      DSSI        NS          6.1   5 RF31           381 MB fixed disk      DSSI        1.5e  B RF31F[1]       200 MB fixed disk      DSSI        NS          5.4-?                                                               2o  B RF31T          381 MB fixed disk      DSSI        1.5         5.5-?                                                               2e  A RF35           800 MB fixed disk      DSSI        1.0         5.5a  A RF36           1.6 GB fixed disk      DSSI        6.1         6.0   A RF71           400 MB fixed disk      DSSI        1.5         6.1A  B RF72           1 GB fixed disk        DSSI        1.5         5.5-?                                                               2   A RF74           3.5 GB fixed disk      DSSI        6.1         6.04  4 RK06[3]        14 MB removable        UNIBUS      NS                diskP  4 RK07[3]        28 MB removable        UNIBUS      NS                disk)  4 RL02[3]        10 MB removable        UNIBUS      NS                diske  #                                 105p f       C ______________________________________________________________VAX__dB                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_s  4 RRD40[3]       600 MB read-only       Q-bus       NS.                optical disk drive     and SCSI  B RRD42          600 MB read-only       SCSI        1.0         5.4-?                optical disk drive                             2r  B RRD43          680 MB read-only       SCSI        6.1         5.5-?                optical disk drive                             22  5 RRD44          680 MB read-only       SCSI        6.1e!                optical disk drive   A RRD45          600 MB 4x read-only    SCSI        6.1         6.1 !                optical disk drivea                                          #                                 106l t  s    C ______________________________________________________________VAX__oB                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_v  B RRD46          600 MB 12x read-       SCSI        6.2-1H3     5.5-A                only optical disk                              2H4e                drive  B RRD47          600 MB 32x read-       SCSI        6.2-1H3     6.2-A                only optical disk                              1H3t                drive  4 RRD50[3]       600 MB read-only       Q-bus       NS!                optical disk drive.  5 RWZ01          594 MB optical         SCSI        1.0                 removable diske                drive  A RWZ53          2.6 GB magneto         SCSI        6.1         6.1r!                optical disk drivet  4 RX02[3]        512 KB diskette        UNIBUS      NS  4 RX23           1.47 MB diskette       SCSI        NS  @ RX23L          1.44 MB diskette       SCSI        6.2-1H3     NS                drive  9 RX26           2.8 MB diskette        I82077      1.5-1H1u                drive  A RX26           2.8 MB diskette        SCSI        1.0         5.5                 drive  4 RX33[3]        1.2 MB diskette        Q-bus       NS                drive, requires                 minimum RQDX3 mi-!                crocode of Version_                3.0  4 RX50[3]        400 KB diskette        Q-bus       NS  4 RV20[3]        2 GB Write Once        Q-bus,      NS-                Read Many optical      UNIBUS,o+                disk drive             VAXBI   #                                 107          C ______________________________________________________________VAX__ B                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_S  4 RV64[3]        2 GB Write Once        Q-bus,      NS-                Read Many optical      UNIBUS, +                disk subsystem         VAXBI6  9 RZ1BB          2 GB wide fixed        UltraSCSI   6.2-1H3                 disk   9 RZ1CB          4 GB wide fixed        UltraSCSI   6.2-1H3i                disk   9 RZ1DB          9 GB wide fixed        UltraSCSI   6.2-1H3                 diske  4 RZ22[3]        52 MB fixed disk       SCSI        NS  4 RZ23[3]        104 MB fixed disk      SCSI        NS  B RZ23L[3]       121 MB fixed disk      SCSI        1.5         5.4-?                                                               1   A RZ24[1]        209 MB fixed disk      SCSI        1.5         6.1I  B RZ24L          245 MB fixed disk      SCSI        1.0         5.4-?                                                               3I  B RZ25           425 MB fixed disk      SCSI        1.0         5.4-?                                                               3I  B RZ25L          500 MB fixed disk      SCSI        1.5         5.5-?                                                               2I  A RZ25M          540 MB fixed disk      SCSI        6.1         6.1   B RZ26           1.05 GB fixed disk     SCSI        1.0         5.5-?                                                               2   A RZ26B          1.05 GB fixed disk     SCSI        1.5         6.0   B RZ26L          1.0 GB fixed disk      SCSI        1.5         5.5-?                                                               2I  B RZ26N          1.0 GB fixed disk      SCSI        6.2         5.5-A                                                               2H4   #                                 108_ _  _    C ______________________________________________________________VAX__ B                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_I  B RZ28           2.1 GB fixed disk      SCSI        1.5         5.5-?                                                               2C  A RZ28B          2.1 GB fixed disk      SCSI        1.5         6.0   A RZ28D          2.1 GB fixed disk      SCSI        6.2         6.2r                                                          #                                 109-         C ______________________________________________________________VAX__.B                                                   Alpha       Ver-C Disk_Drive_____Description____________Bus_________Version_____sion_a  B RZ28L          2 GB narrow fixed      SCSI        6.2-1H3     5.5-A                disk                                           2H4d  B RZ28M          2.1 GB fixed disk      SCSI        6.2-1H3     5.5-A                                                               2H4   B RZ29B          4.3 GB fixed disk      SCSI        6.1         5.5-A                                                               2H4   B RZ29L          4 GB narrow fixed      SCSI        6.2-1H3     5.5-A                disk                                           2H4   B RZ35           852 MB fixed disk      SCSI        NS          5.4-?                                                               3   A RZ40           9 GB narrow fixed      SCSI        Version     6.1.9                disk                               6.2-1H3   A RZ55           332 MB fixed disk      SCSI        1.0         6.1   A RZ56           665 MB fixed disk      SCSI        1.0         6.1   B RZ57[2]        1 GB fixed disk        SCSI        1.5         5.4-?                                                               3   A RZ58           1.35 GB fixed disk     SCSI        1.0         5.5   A RZ73           2 GB fixed disk        SCSI        1.0         6.0i  9 RZ2CC          4 GB fixed disk        SCSI        7.1-1H2i  9 RZ2DC          9 GB fixed disk        SCSI        7.1-1H2   C RZ1EF__________18_GB_fixed_disk_______SCSI________7.1-1H2__________e   ____________________E  Specific  tailoring is required to use this device as an OpenVMS Al-x  ?   pha or VAX system disk with the DECwindows Motif environment.   %  Minimum  revision firmware is V6000.   6  Device  cannot be used as an OpenVMS VAX system disk.E  Device  cannot be used as an OpenVMS VAX system disk with DECwindows      Motif environment.D  TSZ05  is not supported in Version 7.2.  Last version supported was     Alpha Version 6.1.  #                                 110e i       D Note: The preceding list is not complete in terms of currently ship-G ping disk and tape devices, as that list changes frequently. Currently, E supported disk and tape devices are reflected in the AlphaServer Sup- D ported Options Lists that can be found at the individual AlphaServer
 WEB pages:  . http://www.compaq.com/alphaserver/servers.html  F After clicking on the requested AlphaServer, one can access links fromE the left hand columns under Technical Information under Supported Op- E tions. From there, you can sort by type of option and have it display. disks, tapes, etc.  G Disk Options Supported by Compaq's Services Enterprise Integration Cen-i ter (SEIC) (VAX Only)   % RF30-      150 MB removable    (DSSI)B RA[4]      disk   % RF31-RA    381 MB removable    (DSSI)K            diskB  % RF71-RA    400 MB removable    (DSSI)             diskL  % RF71-RA    1 GB removable      (DSSI)S            disk   5 RWZ01      594 MB optical      (SCSI) (Version 5.4-3)             removable disk_   Tapes_  C The first column lists the device name. The second column describes F the device. The third column lists the bus the device is supported on.C The fourth column lists the minimum required version of OpenVMS Al- E pha, and the fifth column lists the minimum required version of Open-RC VMS VAX that supports these devices. (NS stands for Not Supported.)   #                                 111          C _____________________________________________________________VAX___ A                                                  Alpha       Ver- C Tape__________Description____________Bus_________Version_____sion__   4 TA78          1600/6250 BPI,         STI         1.0               STI TU78  3 TA79          STI TU79               STI         NSa  4 TA81          145 MB tape drive      STI         1.0  4 TA90          1.2 GB tape car-       STI         1.0               tridge subsystem._               (5-inch 200 MB               cartridge)  3 TA90E         1.2 GB tape car-       STI         NSn               tridge subsys-                tem. Compacts data               records automati-.               cally   B TA91          High-performance       STI         NS          5.4-2               tape drive  3 TE16          9-track magnetic       M-BUS       NS-               tape drive  B TF70          290 MB TK70 tape       DSSI        NS          5.4-2               cartridge drive   B TF85          2.6 GB streaming       DSSI        6.1         5.5-2               tape cartridge               drive   B 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               cartridgeN  @ TF867         42 GB DLT tape         DSSI        6.1         6.1               loader  #                                 112          C _____________________________________________________________VAX___ A                                                  Alpha       Ver- C Tape__________Description____________Bus_________Version_____sion__   3 TK50          95 MB, 5 1/4-inch      Q-bus       NS -               streaming tape         and SCSIm               cartridge drivee  3 TK70          296 MB, 5 1/4-inch     Q-bus       NSk               streaming tape               cartridge drive   ? TKZ09         5.0 GB, 8mm tape       SCSI        1.5         NSo               drive   B 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_  B TKZ60         200/400 MB,            SCSI        1.0         5.5-2               3480/3490 tape               drive   B TKZ61         4.4 GB, 3480/3490      SCSI        6.1         5.5-2               tape loader   B TKZ62         24 GB, 3480/3490/3490E SCSI        6.1         5.5-2               tape loader   ? TL893         18.4 TB, 4mm, DAT      SCSI        6.2-1H3     NSH               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  4 TLZ04         1.2 GB, 4mm, DAT       SCSI        1.0               tape drive  #                                 113  .       C _____________________________________________________________VAX___ A                                                  Alpha       Ver-5C 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   3 TLZ08         5.25-inch, 2 GB,       SCSI        NS                8mm tape drive  A TLZ09         4 GB, DAT tape         SCSI        6.1         5.5- @               drive                                          2H4  B TLZ10         12/24 GB, DAT tape     SCSI        6.2-1H3     5.5-2               driveG  4 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   8 TLZ9L         32/64 GB, 3.5-inch,    SCSI        6.2-1H3!               4mm DAT tape loader   A TL812         1.92 TB, DLT tape      SCSI        6.2-1H3     6.2-_@               library                                        1H3  A TL822         10.4 TB, DLT tape      SCSI        6.2-1H3     6.2-_@               library                                        1H3  A TL826         7.0 TB, DLT tape       SCSI        6.2-1H3     6.2- @               library                                        1H3  A DS-TL890      1.12 TB, DLT tape      SCSI        6.2-1H3     6.2-I@               library                                        1H3  A DS-TL891      700 GB, DLT tape       SCSI        6.2-1H3     6.2-_@               library                                        1H3  A DS-TL893      18.4 TB, DLT tape      SCSI        6.2-1H3     6.2- @               library                                        1H3  #                                 114     I    C _____________________________________________________________VAX___ A                                                  Alpha       Ver- C Tape__________Description____________Bus_________Version_____sion__   A DS-TL894      3.3 TB, DLT tape       SCSI        6.2-1H3     6.2- @               library                                        1H3  A DS-TL895      6.7 TB, DLT tape       SCSI        6.2-1H3     6.2- @               library                                        1H3  A DS-TL896      12.3 TB, DLT tape      SCSI        6.2-1H3     6.2- @               library                                        1H3  3 TS05          9-track magnetic       Q-bus       NSx               tape drive  3 TS11          9-track magnetic       UNIBUS      NS                tape drive  4 TSZ05         1600 bits/in tape      SCSI        1.5               drive6  B TSZ07         1600/6250 BPI tape     SCSI        1.0         5.4-1               drive   3 TU77          9-track magnetic       M-BUS       NS                tape drive  3 TU78          9-track magnetic       M-BUS       NSC               tape drive  3 TU80          9-track magnetic       UNIBUS      NS.               tape drive  3 TU81          9-track magnetic       UNIBUS      NSZ               tape drive  3 TU81-Plus     Streaming 9-track      Q-bus,      NSf,               magnetic tape drive    UNIBUS,*                                      VAXBI  4 TZ30          95 MB, half-height     SCSI        1.0               DLT tape drive  4 TZ85          2.6 GB DLT tape        SCSI        1.0               drive   #                                 115     t    C _____________________________________________________________VAX___iA                                                  Alpha       Ver- C Tape__________Description____________Bus_________Version_____sion__   4 TZ857         18 GB, DLT tape        SCSI        1.0               loader  4 TZ86          6.0 GB, DLT tape       SCSI        1.5               driveg  4 TZ867         42 GB, DLT tape        SCSI        1.5               loader  @ TZ87          20 GB, DLT tape        SCSI        6.1         6.1               driver  @ TZ875         100 GB, DLT tape       SCSI        6.1         6.1               loader  @ TZ877         140 GB, DLT tape       SCSI        6.1         6.1               loader  A TZ88          20/40 GB, DLT tape     SCSI        6.2         5.5- @               drive                                          2H4  A TZ88N         40/80 GB, DLT tape     SCSI        6.2         5.5-I@               drive                                          2H4  A TZ89N         35/70 GB, DLT tape     SCSI        6.2-1H3     5.5- @               drive                                          2H4  A TZ885         40/80 GB, DLT tape     SCSI        6.2-1H2     5.5-4@               loader                                         2H4  A TZ887         40/80 GB, DLT tape     SCSI        6.2-1H2     5.5-l@               loader                                         2H4  4 TZK08         2.2 GB 8mm, tape       SCSI        6.1               drive   4 TZK10         320/525 MB, QIC        SCSI        1.0               tape drive  4 TZK11         2.0 GB, QIC tape       SCSI        6.1               drive   #                                 116          C _____________________________________________________________VAX___ A                                                  Alpha       Ver-eC Tape__________Description____________Bus_________Version_____sion__A  4 TZS20         25/50 GB, AIT 8mm,     SCSI        7.1               tape drive  4 ESL9326       40/80 GB, DLT tape     SCSI        7.2               library family  4 ESL9198       40/80 GB, DLT tape     SCSI        7.2C ______________library_family_______________________________________5  D Note: The preceding list is not complete in terms of currently ship-G ping disk and tape devices, as that list changes frequently. Currently,CE supported disk and tape devices are reflected in the AlphaServer Sup- D ported Options Lists that can be found at the individual AlphaServer
 WEB pages:  . http://www.compaq.com/alphaserver/servers.html  F After clicking on the requested AlphaServer, one can access links fromE the left hand columns under Technical Information under supported op- E tions. From there, you can sort by type of option and have it display  disks, tapes, etc.   Networks Storage Servers  - HS111         StorageWorks FDDI StorageServer   - HS121         StorageWorks FDDI StorageServer.  - HS211         StorageWorks FDDI StorageServer   - HS221         StorageWorks FDDI StorageServerF  - HS241         StorageWorks FDDI StorageServer1  - SWXNA         StorageWorks FDDI StorageServer   #                                 117_ _  _    B 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 OpenVMSKA               clients in a LAN. It supports up to 14 SCSI devicest@               and can be used for software distribution and ini-A               tial system load (ISL). For more information, refer A               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   Controllers and Adapters  = HSC40         Hierarchical storage controller for MSCP servedtA               disks and TMSCP served tapes. (HSC software must be @               at minimum Version 8.1.) Refer to SPD 42.81.xx for'               supported configurations.r  = HSC50         Hierarchical storage controller for MSCP served A               disks and TMSCP served tapes. (HSC software must be4@               at minimum Version 4.1.) Refer to SPD 32.96.xx for'               supported configurations.S  = HSC60         Hierarchical storage controller for MSCP served A               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 A               disks and TMSCP served tapes. (HSC software must be @               at minimum Version 8.1.) Refer to SPD 42.81.xx for'               supported configurations.       #                                 118_ c  t    = HSC70         Hierarchical storage controller for MSCP servedBA               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 servediA               disks and TMSCP served tapes. (HSC software must be5@               at minimum Version 8.1.) Refer to SPD 42.81.xx for'               supported configurations.   = HSC95         Hierarchical storage controller for MSCP served A               disks and TMSCP served tapes. (HSC software must bee@               at minimum Version 8.1.) Refer to SPD 42.81.xx for'               supported configurations.   : HSD05         DSSI to SCSI-2 FSE StorageWorks bus adapter.8               (Firmware must be at minimum Version X36.)  9 HSD10         DSSI to SCSI-2 FSE StorageWorks bus adapter   A HSD30         DSSI based StorageWorks controller that supports up0A               to three SCSI-2 FSE ports. (HSD firmware must be ati$               minimum Version V15D.)  A HSD50         DSSI based StorageWorks controller that supports up3?               to six SCSI-2 FSE ports. (HSD firmware must be at ,               minimum Version Version 5.0D.)  ? HSJ30         CI based StorageWorks controller that supports up A               to three SCSI-2 FSE ports. (HSJ firmware must be at $               minimum Version V15J.)  ? HSJ40         CI based StorageWorks controller that supports upS?               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_7               minimum Version Version 5.0J-2 or later.)   A HSZ20         Fast wide differential SCSI based StorageWorks con-_A               troller that supports up to three SCSI-2 FSE ports.S               (Alpha only)  #                                 119          A HSZ40-        Fast wide differential SCSI based StorageWorks con-2? Bx/Cx         troller that supports up to six SCSI-2 FSE ports. >               (HSZ firmware must be at minimum Version V2.5Z.)               (Alpha only)  A HSZ50         Fast wide differential SCSI based StorageWorks con- ?               troller that supports up to six SCSI-2 FSE ports.d>               (HSZ firmware must be at minimum Version Version                5.0Z) (Alpha only)  A HSZ70         UltraSCSI wide differential based StorageWorks con- A               troller that supports up to six UltraSCSI wide sin- >               gle ended device ports and one host port. (Alpha               only)   A HSZ80         UltraSCSI wide differential based StorageWorks con-NA               troller that supports up to six UltraSCSI wide sin- ?               gle ended device ports and two host ports. (Alphac               only)U  A HSZ22         UltraSCSI wide differential based StorageWorks con-cA               troller that supports up to two UltraSCSI wide sin-,?               gle ended device ports and two host ports. (AlphaM               only)S  > HSG60         Fibre Channel based StorageWorks controller that@               supports up to two UltraSCSI wide single ended de-B               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-B               vice ports and two host ports. (Alpha only - Version               7.2-1 and higher)   > MDR           Compaq StorageWorks Modular Data Router for con->               necting SCSI tape devices to a FC switch. (Alpha               only)Z  @ KDM70         Mass-storage controller for XMI systems with eight               SDI ports.  #                                 120  6       ? KFESA         Mass-storage controller for EISA systems with one %               DSSI port. (Alpha only)   ? KFESB         Mass-storage controller for EISA systems with one2%               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)  A 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 2               three SCSI-2 FSE ports. (Alpha only)  > KZMSA         Mass-storage controller for XMI systems with two?               SCSI ports. (Limited SCSI-2 support - Alpha only)S  B KZPAA         Mass-storage adapter for PCI systems with one SCSI-2$               FSE port. (Alpha only)  = KZPBA-CA      Mass-storage adapter for PCI based servers with1@               one UltraSCSI port. Single host support in Version=               6.2-1H3, and Version 7.1-1H1 and higher. (Alpha_               only)   A KZPBA-CB      Mass-storage adapter for PCI based servers with two_B               UltraSCSI ports. Single host support in Version 6.2-@               1H3, and multi-host support in Version 7.1-1H1 and"               higher. (Alpha only)  B KZPDA         Mass-storage adapter for PCI systems with one SCSI-2%               FWSE port. (Alpha only)   B 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)t  #                                 121h n  i    B KZPSC-BA      Backplane RAID controller for PCI systems with three,               SCSI-2 FSE ports. (Alpha only)  ? KZPAC-        One and two channel Backplane RAID controller forh' AA,CA,CB      PCI systems. (Alpha only)i  ? 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)  A KZPCA         Mass-storage adapter for PCI based servers with onee4               UltraSCSI, Ultra-2 port . (Alpha only)  A KGPSA         Mass-storage adapter for PCI-based servers with one A               Fibre Channel port. (Alpha only - Version 7.2-1 ande               higher)a  @ KZTSA         Mass-storage adapter for TURBOchannel systems with/               one SCSI-2 FWD port. (Alpha only)   ? PB2HA-SA      Mass-storage controller for EISA systems with onet?               SCSI port. (Limited SCSI-2 support. Alpha only ons:               systems with no greater than 1GB of memory.)  @ PMAZB         Mass-storage adapter for TURBOchannel systems with0               two SCSI-2 FSE ports. (Alpha only)  @ PMAZC         Mass-storage adapter for TURBOchannel systems with5               two fast SCSI-2 FSE ports. (Alpha only)g   Hubs and Switches0   DWZZH-03      3 port SCSI hubl   DWZZH-05      5 port SCSI hub   , DSGGA-AA/B    8/16 port Fibre Channel switch   Controllers (VAX Only)  A HSZ10         SCSI based StorageWorks controller that supports upV"               to two SCSI-2 ports.  #                                 122o r       @ IDC           Integrated Disk Controller for VAX-11/725 and VAX-               11/730 systems.t  @ IDTC          Integral Disk and Tape Controller for VAX 8600 and               VAX 8650 systems.   ? LPA11-K       Microprocessor controller for laboratory acquisi-o?               tion I/O devices, accommodating up to two AD11-K,eA               one AA11-K, one KW11-K, two AM11-Ks, and five DR11-n@               K devices. One LPA11-K controller is supported perA               UNIBUS, and a maximum of two are supported per sys-s               tem.  = KDA50         Q-bus MSCP disk controller. The KDA50 disk con- B               troller supports up to four of the following drives:/               RA60, RA70, RA80, RA81, and RA82.   = KDB50         VAXBI MSCP disk controller. The KDB50 disk con-oB               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 A               to seven DSSI storage devices to attach to the DSSIc=               bus. (Six DSSI storage devices are allowed in ad(               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.d  ? KZQSA         Q-bus to SCSI bus adapter. This adapter allows up1A               to seven SCSI storage devices to attach to the SCSIs>               bus. Supported only for CD-ROM and specific tape               devices.  ? KFDDA         VAX 4000 model 100 DSSI bus adapter. This adapterFB               allows up to seven DSSI storage devices to attach toA               the DSSI bus. (Six DSSI storage devices are allowedo-               in a multi-host configuration.)i  #                                 123S b  d    ? 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 devicesl9               are allowed in a multi-host configuration.)t  @ 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.s  ? RQDXx         Q-bus disk controller for MicroVAX and VAXstationa=               systems. There is an RQDX1, RQDX2, and an RQDX3 ?               controller. The RQDXx disk controller supports as_>               many as four disk units, with each RX50 disketteA               drive counting as two units. Due to controller lim- =               itations, the system supports a maximum of foure=               devices; the number of RD/RX devices the system ?               supports depends on the enclosure. The RQDX3 diskn>               controller is required for the RD54 and the RX33               drives.l  A RX211         UNIBUS diskette controller for two RX02 drives. Onep@               RX211 diskette controller is supported per system.  = RUX50         UNIBUS diskette controller for RX50 drives. One7@               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.e  @ 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.  #                                 124s ,       ? 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.  @ 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 controllerk=               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)  6 PBXDA-     4-port PCI asynchronous terminal controller AA  6 PBXDA-     8-port PCI asynchronous terminal controller AB  7 PBXDA-     16-port PCI asynchronous terminal controllerw AC  , Asynchronous Terminal Controllers (VAX Only)  A CXA16      16-line serial terminal multiplexer (DEC-423), maximum &            baud rate supported: 38400.%            (No modem control) (Q-bus)C  ? CXB16      16-line serial terminal multiplexer (RS422), maximum6&            baud rate supported: 38400.%            (No modem control) (Q-bus)e  #                                 125     I    > CXY08      8-line serial terminal multiplexer (RS232), maximum&            baud rate supported: 19200.'            (Full modem control) (Q-bus)Z  > DHB32      16-line asynchronous terminal controller for VAXBI,6            maximum baud rate supported: 19200. (VAXBI)  > DHF11      32-line asynchronous terminal controller (DEC 423),A            maximum baud rate supported: 19200. (No modem control)s            (Q-bus)  A DHT32      8-line asynchronous terminal controller (DEC 423). (Nos)            modem control) (MicroVAX 2000),  @ DHQ11      8-line asynchronous terminal controller (EIA RS-232-CB            or RS-423-A), maximum baud rate supported: 19200. (Full!            modem control) (Q-bus)   ? DHU11      16-line asynchronous terminal controller (RS-232-C),p<            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 baudA            rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. '            (Full modem control) (VAXBI)i  @ DMF32      8-line asynchronous terminal controller, maximum baudA            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: OpenVMSA            VAX, 19200; DECnet-VAX, 9600. (Modem support dependenta%            on configuration) (UNIBUS)   ? DZ11       8-line asynchronous terminal controller (EIA RS-232-t=            C or RS-423-A), maximum baud rate supported: 9600.t+            (Partial modem control) (UNIBUS)s  #                                 126w         ? DZ32       8-line asynchronous terminal controller (EIA RS-232- =            C or RS-423-A), maximum baud rate supported: 9600.r+            (Partial modem control) (UNIBUS)   ? DZQ11      4-line asynchronous terminal controller (EIA RS-232-l?            C or RS-423-A), maximum baud rate supported: OpenVMS @            VAX, 19200; DECnet-VAX, 9600. (Partial modem control)            (Q-bus)  ? 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)  E The X.25 for OpenVMS Alpha Systems software product contains the syn-uC chronous device drivers and is required when using synchronous com-X? munications options. Refer to SPD 47.37xx for more information.u  @ SCC        Integral Synchronous Communications controller on DEC            3000 systems   > DSYT1      2-port TurboChannel/Synchronous Communications con-            troller  B DNSES      2-port EISA/Synchronous Communications controller (Ver-)            sion 6.2-1H2 minimum support.)e  @ PBXDI-     2 or 4-port ISA/Synchronous Communications controller Ax  = PBXDP-     2, 4 or 8-port PCI/Synchronous Communications con-e Ax         troller  " Synchronous Controllers (VAX Only)  G The optional VAX Wide Area Network Device Drivers component of the Com-rE paq DECnet-Plus for OpenVMS software product contains the synchronous C device drivers and is required when using synchronous communication54 options. Refer to SPD 25.03.xx for more information.  #                                 127  A       8 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)   > DMF32      Point-to-point or multipoint synchronous interface.            (UNIBUS)t  > DMP11      Point-to-point or multipoint synchronous interface;?            (UNIBUS) retired device, no longer offered as an op-i            tion.  B 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.t  B DSB32      2-line, multiple protocol, synchronous adapter. (VAXBI)  = DSH32      1-line synchronous (full modem control) and 8-line >            asynchronous (no modem control) communications con-A            troller for the MicroVAX 2000. DEC423 devices are sup- B            ported. Maximum baud rates supported: OpenVMS VAX, 19.2>            KbPS (kilobits/second); 9.6 kBPS for MicroVAX 2000,            etc.d  > DST32      Synchronous single-line support for DDCMP up to 9.6B            KbPS, full duplex for MicroVAX 2000 systems. Concurrent/            use with the DHT32 is not supported.h  B DSV11      Synchronous, 2-line, half or full-duplex point-to-point?            communication interface supporting DDCMP (one or two              lines up to 64 KbPS).  #                                 128  N  S    @ DSF32      DEC WANcontroller 620 - 2-line synchronous communica-?            tions controller designed specifically for the VAXftn@            3000 processors, supporting DDCMP. DDCMP is supported?            at speeds up to 64 KbPS per line for a 2-line opera-             tion.   Graphics Options  @ PBXGK         ELSA/GLoria Synergy+ graphics option that providesA               2D acceleration for supported PCI-based Alpha Work- #               stations and Servers.   B PBXGD         PowerStorm 300/3500 graphics option that provides 3DA               acceleration or 3D acceleration with stereo viewingRA               capabilities for supported PCI-based Alpha Worksta-h                tions and Servers.  @ PBXGF-AB      3DLabs OXYGEN VX1 graphics option that provides 2DA               acceleration for supported PCI-based Alpha Worksta-                 tions and Servers.  C OpenGL 1.1 supports PowerStorm 350 and 300 graphics accelerators ons the following platforms:   o  XP900  	 o  XP1000e   o  DS10    o  DS206   o  DS20e   o  ES40   C OpenGL 1.1 is included with the OpenVMS Alpha operating system dis-e tribution kit.  H For more information, refer to the Compaq Open3D for OpenVMS Alpha Soft-F ware Product Description (SPD 45.08.xx), and the Compaq DECwindows Mo-/ tif Software Product Description (SPD 42.19.xx)   #                                 129  e  n   LAN Options (VAX and Alpha)t  B DEFTA         A network adapter that connects TURBOchannel systems>               to ANSI FDDI local area networks.(100 mbits/sec)  B DEFZA         A network adapter that connects TURBOchannel systemsB               to ANSI FDDI local area networks. Not supported as aB               cluster interconnect or boot device. (100 mbits/sec)  A DEMFA         A network adapter that connects XMI systems to ANSI 7               FDDI local area networks. (100 mbits/sec)o  A DEMNA         A network adapter that connects XMI systems to bothtB               the Ethernet and IEEE 802.3 local area networks. (10               mbits/sec)  - PMAD          A network adapter that connectst@               TURBOchannel systems to both the Ethernet and IEEE7               802.3 local area networks. (10 mbits/sec)    LAN Options (Alpha Only)  @ DEFAA      A network adapter that connects FUTUREBUS+ systems to9            ANSI FDDI local area networks. (100 mbits/sec)l  ? DEFEA      A network adapter that connects EISA systems to ANSIB4            FDDI local area networks. (100 mbits/sec)  > DEFPA      A network adapter that connects PCI systems to ANSI4            FDDI local area networks. (100 mbits/sec)  A DGLPB      ATMworks 350 network adapter that connects PCI systemsm?            to ATM local area networks. Version 7.1-1H1 minimum.x            (155 mbits/sec-OC3)  A DGLPA      ATMworks 351 network adapter that connects PCI systems ?            to ATM local area networks. Version 7.1-1H1 minimum.l            (155 mbits/sec-OC3)  ? DAPBA      FORE Systems HE155 network adapter that connects PCI >            systems to ATM local area networks. Version 7.1-1H1'            minimum. (155 mbits/sec-OC3)   #                                 130( B       ? DAPCA      FORE Systems HE622 network adapter that connects PCI >            systems to ATM local area networks. Version 7.1-1H1(            minimum. (622 mbits/sec-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            mbits/sec)   * DE422      A network adapter that connectsA            EISA systems to both the Ethernet and IEEE 802.3 localS(            area networks. (10 mbits/sec)  @ DE425      A high-performance network adapter that connects EISAA            systems to both the Ethernet and IEEE 802.3 local areab#            networks. (10 mbits/sec)   ? DE434      A high-performance network adapter that connects PCI(A            systems to both the Ethernet and IEEE 802.3 local areau#            networks. (10 mbits/sec)p  > DE435      A network adapter that connects PCI systems to both?            the Ethernet and IEEE 802.3 local area networks. (10r            mbits/sec)   @ DE436      A quad channel network adapter that connects PCI sys->            tems to both the Ethernet and IEEE 802.3 local area#            networks. (10 mbits/sec)r  * DE450      A network adapter that connects@            PCI systems to both the Ethernet and IEEE 802.3 local(            area networks. (10 mbits/sec)  B 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 mbits/sec)  B 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 mbits/sec)  #                                 131o (  B    @ DE504-     A quad channel network adapter that connects PCI sys-> BA         tems to both the Ethernet and IEEE 802.3 local areaB            networks. (Version 7.1-1H1 minimum support.) (10 or 100            mbits/sec)   B DE500-     A network adapter that connects PCI systems to both the@ FA         Ethernet and IEEE 802.3 local area networks. (Version4            7.1-1H1 minimum support.) (100 mbits/sec)  B 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 mbits/sec)  B DE600-     A network adapter that connects PCI systems to both the@ AA         Ethernet and IEEE 802.3 local area networks. (Version8            7.1-2 minimum support.) (10 or 100 mbits/sec)  B DE600-     A network adapter that connects PCI systems to both the@ FA         Ethernet and IEEE 802.3 local area networks. (Version2            7.1-2 minimum support.) (100 mbits/sec)  @ DE602-     A dual channel network adapter that connects PCI sys-> AA         tems to both the Ethernet and IEEE 802.3 local area@            networks. (Version 7.1-2 minimum support.) (10 or 100            mbits/sec)N  B DEGPA-     A network adapter that connects PCI systems to both the@ SA         Ethernet and IEEE 802.2 local area networks. (Version3            7.1-2 minimum support.) (1000 mbits/sec)p  B 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 mbits/sec)o  B DW300      A network adapter that connects the EISA bus to a Token7            Ring local area network. (4 or 16 mbits/sec)   ? PBXNP-     A network adapter that connects PCI systems to a To-N@ DA         ken Ring local area network. (Version 6.2-1H3 minimum(            support.) (4 or 16 mbits/sec)  #                                 132  t  .    ? 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 mbits/sec)  @ DETRA      A network adapter that connects the TURBOchannel sys-<            tems to a Token Ring local area network. (4 or 16            mbits/sec)L  * PB2CA-     A network adapter that connectsA AA         EISA systems to both the Ethernet and IEEE 802.3 localn(            area networks. (10 mbits/sec)   LAN Options (VAX Only)  < DEUNA      A network adapter that connects UNIBUS systems to@            both Ethernet and IEEE 802.3 local area networks. (10            mbits/sec)p  A 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 mbits/sec)  @ DEBNA      A network adapter that connects VAXBI systems to both?            the Ethernet and IEEE 802.3 local area networks. (10a            mbits/sec)-  @ DEBNI      A network adapter that connects VAXBI systems to both?            the Ethernet and IEEE 802.3 local area networks. (10             mbits/sec)   = DESVA      An embedded network adapter that connects VAX sys-c>            tems to both the Ethernet and IEEE 802.3 local area#            networks. (10 mbits/sec)p  @ DEQNA      A network adapter that connects Q-bus systems to both?            the Ethernet and IEEE 802.3 local area networks. Theo?            minimum revision level required is K3. Supported forv=            application use only. Not supported beyond Versionh             5.4-3. (10 mbits/sec)  #                                 133m 0  0    @ 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 revisionv/            level required is C3. (10 mbits/sec)o  B DESQA      A network adapter that connects Q-bus for S-BOX config-B            urations to both the Ethernet and IEEE 802.3 local area#            networks. (10 mbits/sec)h  @ DEFQA      A network adapter that connects Q-bus systems to ANSI4            FDDI local area networks. (100 mbits/sec)  B DGLTA-     ATMworks 750 network adapter that connects TurboChannel0 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. (MinimumU5               microcode version REV 1.0 is required.)e   CI Options (VAX Only)   D VAXcluster software can support multiple CI adapters per system. Re-E fer to the VAXcluster Software Product Description (SPD 29.78.xx) for  the supported configurations.e  @ CIBCI      CI adapter for VAXBI systems. (Minimum microcode ver-%            sion REV 8.7 is required.)   B CIBCA-     Native CI adapter for VAXBI systems. (Minimum microcode( AA         version REV 7.5 is required.)  B CIBCA-     Native CI adapter for VAXBI systems. (Minimum microcode( BA         version REV 5.2 is required.)  #                                 134p n  A     CIPCI   ? CIXCD-     Native CI adapter for VAX 9xxx XMI systems. (Minimum 2 AA         microcode version REV 1.0 is required.)  ? CIXCD-     Native CI adapter for VAX 6xxx XMI systems. (Minimumo2 AB         microcode version REV 1.0 is required.)  # Memory Channel Options (Alpha Only)r  1 CCMAA-AA      PCI-based Memory Channel Controllero  1 CCMAA-BA      PCI-based Memory Channel Controllero  2 CCMHA-AA      Memory Channel Hub With 4 Line Cards  B CCMLA-AA      Memory Channel Line Card for use with Memory Channel               Hub(CCMHA-AA)G  3 CCMAB-AA      PCI-based Memory Channel 2 Controller   4 CCMHB-AA      Memory Channel 2 Hub with 4 Line Cards  B CCMLB-AA      Memory Channel 2 Line Card for use with Memory Chan-"               nel 2 Hub (CCMHB-AA)  
 Miscellaneous   + PC4XD-AA      Parallel/serial port adapter.i  $ PMTCE         TURBOchannel extender.   Miscellaneous (VAX Only)  = CR11       Card reader. One CR11 card reader is supported per2            system. (UNIBUS)t  1 DRV11-     General-purpose DMA interface. (Q-bus). WA  A DR11-W     General-purpose, high-speed DMA interface - one DR11-WA*            interface supported per UNIBUS.  > DR750      High-performance, general-purpose interface for the@            VAX-11/750. One DR750 interface is supported per sys-B            tem. This device cannot be used in conjunction with the            CI750.   #                                 135     S    > DR780      High-performance, general-purpose interface for theA            VAX-11/780 and VAX-11/785. One DR780 interface is sup- =            ported per system. On the VAX 8600 and VAX 8650 asrB            many as four per system are permitted provided that the            M8297-YA is used.  ! DWBUA      XMI to UNIBUS adapter.(  B DWMBA      XMI to BI adapter; also the adapter used to connect the'            XMI to VAX expander cabinet.E   DWMVA      XMI to VME adapter.  > FP86-AA    Floating point accelerator for the VAX 8600 and VAX            8650 systems.  9 FV64A      Vector processing option for the VAX 6000-400.   ? H7112      Memory battery backup for VAX 8600 and VAX 8650 sys-t:            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.a  ( VS40X      4-plane graphics coprocessor.  / WS01X      VAXstation 3100 SPX graphics option.r  
 Abbreviations6  0 APMP       Adaptive Partitioned Multi-Processing  # ATA-3      AT Attachment, Version 3s  ! COM        Component Object ModelE   DLT        Digital Linear Tape  / DSSI       DIGITAL Storage Systems Interconnecto  2 EISA       Extended Industry Standard Interconnect  + FDDI       Fiber Distributed Data Interfacen  # FSE        Fast Single Ended (SCSI)y  ( FWD        Fast Wide Differential (SCSI)  #                                 136o .  e    3 IDE        Integrated Device (or Drive) Electronicsi  < IEEE       Institute of Electrical and Electronics Engineers  5 I80277     Intel 82077 PC Compatible Floppy Interfacea  ( MSCP       Mass Storage Control Protocol  ! NCS        National Character SetE  , PCI        Peripheral Component Interconnect  ! QIC        Quarter Inch Cartridge   / RAID       Redundant Array of Independent Disks     RMC        Remote Procedure Call  % RMS        Record Management Servicesa  # SDI        Standard Drive Interfaceh  $ SMP        Symmetric Multiprocessing  " STI        Standard Tape Interface  % TFF        Terminal Fallback Facilityb  ' TIE        Translated Image Environmenta  - TMSCP      Tape Mass Storage Control Protocolh   VLM        Very Large Memory  4 VVIEF      VAX Vector Instruction Emulation Facility  ' XMI        Extended Memory Interconnect    SOFTWARE WARRANTYc  F Warranty for this software product is provided by Compaq with the pur-C chase of a license for the products as defined in the Software War-1 ranty Addendum to this SPD.   D The previous information is valid at time of release. Please contact= your local Compaq office for the most up-to-date information.   "  2001 Compaq Computer Corporation  #                                 137a r  a  D Compaq, AlphaServer, MicroVAX, POLYCENTER, PowerStorm, StorageWorks,E VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark0D Offic. OpenVMS, DECnet, DECwindows, Tru64, and VAXcluster are trade-I marks of Compaq Information Technologies Group, L.P. in the United StatessF and other countries. Microsoft, Visual Basic, Visual C++, Windows, andG Windows NT are trademarks of Microsoft Corporation in the United States C and other countries. Intel and Pentium are trademarks of Intel Cor- D poration in the United States and other countries. Motif, OSF/1, andD UNIX are trademarks of The Open Group in the United States and other
 countries.  C All other product names mentioned herein may be trademarks of theirt respective companies.h  F Confidential computer software. Valid license from Compaq required forG possession, use or copying. Consistent with FAR 12.211 and 12.212, Com- E mercial Computer Software, Computer Software Documentation, and Tech- C nical Data for Commercial Items are licensed to the U.S. Government + under vendor's standard commercial license.t  E Compaq shall not be liable for technical or editorial errors or omis- D sions contained herein. The information in this document is providedC "as is" without warranty of any kind and is subject to change with-rC out notice. The warranties for Compaq products are set forth in thetE express limited warranty statements accompanying such products. Noth-oF ing herein should be construed as constituting an additional warranty.                            #                                 138s X  s                                                                                  #                                 139A