Compaq Software Product Description ___________________________________________________________________ PRODUCT NAME: OpenVMS Operating System for Alpha and VAX, Version 7.2 SPD 25.01.55 Note: This SPD describes OpenVMS operating system software for the Alpha and VAX computer family. Except where explicitly noted, the features de- scribed in this SPD apply equally to both Alpha and VAX systems. Open- VMS Alpha and OpenVMS VAX operating system licenses and part numbers are architecture specific. Please refer to the Ordering Information section of this SPD for further details. DESCRIPTION OpenVMS is a general-purpose, multiuser operating system that runs in both production and development environments. OpenVMS Alpha supports Compaq Computer Corporation's Alpha series computers, while OpenVMS VAX supports VAX, MicroVAX, VAXstation, and VAXserver series comput- ers. OpenVMS software supports industry standards, facilitating ap- plication portability and interoperability. OpenVMS provides symmet- ric multiprocessing (SMP) support for multiprocessing Alpha and VAX systems. The OpenVMS Alpha operating system provides support for 64- bit virtual memory addressing and Very Large Memory (VLM). The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Ac- tual system performance depends on the type of computer, available phys- ical memory, and the number and type of active disk and tape drives. January 1999 The OpenVMS operating system has well-integrated networking, distributed computing, client/server, multiprocessing, and windowing capabilities. It contains extensive features that promote ease-of-use, improve the productivity of programmers, and facilitate system management. OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 are functional releases of the OpenVMS operating system for Compaq's Alpha and VAX systems respectively. OpenVMS Alpha Version 7.2 provides new features that are designed to provide the highest level of interoperability between OpenVMS and Win- dows NT. It also offers the Compaq Galaxy Software Architecture on Open- VMS which delivers greater levels of performance, scalability, avail- ability and extremely flexible operational capabilities by allowing multiple instances of OpenVMS to execute cooperatively in a single com- puter. In addition, OpenVMS Version 7.2 includes: o Seamless integration between OpenVMS and Windows NT o Component Object Model (COM) for OpenVMS o Java Development Kit (Alpha) o Netscape FastTrack Web Server for OpenVMS Alpha o Premier OpenVMS clustering, which includes increased cluster per- formance for large-scale databases, easier system management with clusterwide logical names, SCSI multipath failover support and Open- VMS Galaxy shared memory clusters o Extended File Specifications on OpenVMS Alpha, which includes: - Extended file naming - Deep directories o Improved TCP/IP Services for OpenVMS based on the UNIX kernel o Enhanced system management o Ongoing improvements to boost operating system performance, reli- ability, and availability o OpenVMS BACKUP performance improvements o Year 2000 Readiness 2 OpenVMS is an open software environment that supports key formal and de facto standards such as OSF/Motif and the OSF Distributed Comput- ing Environment (DCE), Java, and the Microsoft Component Object Model (COM). The right to use the DCE Runtime Services for OpenVMS, COM for OpenVMS Runtime Services and the Java Development Kit is included with the OpenVMS operating system base license. DECwindows Motif and COM for OpenVMS developer kit are available as separately orderable lay- ered products. Refer to the OpenVMS Version 7.2 New Features Manual for further de- tails on the new enhancements, features, and functions. YEAR 2000 READINESS This product is capable of accurately processing, providing, and/or receiving date data from, into and between the twentieth and the twenty- first centuries, and the years 1999 and 2000, including leap-year cal- culations, when used in accordance with the associated product doc- umentation and provided that all hardware, firmware and software used in combination with the product properly exchange accurate date data with the product. USER ENVIRONMENT Users can access the OpenVMS software by using the English-like DIG- ITAL Command Language (DCL), the command language for OpenVMS that is supplied with the system. DCL commands provide information about the system and initiate system utilities and user programs. DCL commands take the form of a command name followed by parameters and qualifiers. With the DIGITAL DCL command PIPE, individual DCL operations can be connected using a UNIX like command syntax. OpenVMS prompts users to enter required DCL parameters, making it easy for novice users. Users can enter DCL commands at a terminal or include them in command procedures. These command procedures can be run interactively or sub- mitted to a batch queue for later processing. 3 Information on DCL and OpenVMS utilities is available on line through the OpenVMS Help system. Online help includes summary information on all aspects of system operation. The following tools and utilities are integrated into the OpenVMS op- erating system. Text Processing The Extensible Versatile Editor (EVE), one of several text editors sup- plied by Compaq, is the default editor for OpenVMS. EVE allows users to insert, change, and delete text quickly. Written in the DIGITAL Text Processing Utility (DECTPU) language, EVE is a full-screen editor that allows users to scroll through text on a terminal screen. EVE provides an EDT-style keypad, allowing EDT users to move easily to EVE. EDT is also supported on OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2. Mail Utility The Mail utility allows users to send messages to any other user on the system. Multinode operation is available if a DECnet or TCP/IP prod- uct is installed and licensed on each participating node on the net- work. Command-Level Programming Command-level programming allows users to create special files, called command procedures, that contain a series of DCL commands. When users execute a command procedure, the system processes the commands in the command procedure consecutively. Users can also use special DCL com- mands to: o Assign symbolic names o Evaluate numerical and logical expressions o Accept parameters o Communicate interactively with the user invoking the command pro- cedure 4 o Perform conditional (IF-THEN-ELSE) and branching (GOTO) logic o Handle error conditions User Environment Tailoring Users can customize the computing environment with login command pro- cedures, shorthand commands, binding of commands to function keys, and command recall and editing. Terminal Fallback Facility (TFF) This facility allows Compaq 7-bit terminals to input and output the Compaq Multinational character set (MCS). Specific tables allow con- version for a number of different 7-bit National Replacement Charac- ter sets to MCS, such as French, German, Spanish, and Swedish. TFF also allows character composition on terminals that do not have the com- pose key. National Character Set (NCS) Utility This utility allows users to define non-ASCII string collating sequences and to define conversion functions. Conversion functions use conver- sion algorithms to change an input string; for example, to change low- ercase characters to uppercase. NCS also allows OpenVMS Record Man- agement Services (RMS) indexed files to be collated using user-specified collating sequences. PROGRAM DEVELOPMENT ENVIRONMENT OpenVMS includes a comprehensive set of tools for developing programs, including: run-time libraries (RTLs), a linker, a librarian, and a sym- bolic debugger. The assembly-level VAX MACRO-32 language is supplied with OpenVMS VAX. In addition, the Java Development Kit provides an environment in which to develop and deploy Java applications on Open- VMS Alpha. The following tools are available to the OpenVMS program- mer. Java Development Kit 5 The Java Development Kit (JDK) V1.1.6 is a set of building blocks con- taining basic development tools and a rich set of class libraries in- cluding o Java Compiler o Java Virtual Machine o Java Class Libraries o Java Applet Viewer o Java Debugger and other tools Language and Run-Time Library Support OpenVMS includes several RTLs that provide: o String manipulation o Parallel processing support o I/O routines o I/O conversion o Terminal-independent screen handling o Date and time formatting routines o Highly accurate mathematical functions o Signaling and condition handling o Other general-purpose functions With OpenVMS VAX, these routines can be called from programs written in such languages as VAX MACRO-32, VAX Ada, VAX BASIC, VAX BLISS-32 Implementation Language, VAX C, DEC C, DEC C++, VAX COBOL, VAX DIBOL, DEC Fortran, VAX Pascal, and VAX PL/I. With OpenVMS Alpha, these routines can be called from programs writ- ten in such languages as MACRO-32, MACRO-64, DEC Ada, DEC BASIC, DEC C, DEC C++, DEC COBOL, DEC Fortran, DEC Pascal, Java, and DEC PL/I. 6 Also included in OpenVMS Alpha are language-support libraries. While each language is different, all provide support for sequential file I/O, and most support direct and indexed file I/O. Language RTLs also provide support for I/O formatting, error handling, and in DEC For- tran, the ability to read unformatted files that contain data from other vendors. RTLs are provided to support translated images created from user-mode images built on OpenVMS VAX Version 4.0 through Version 5.5-2. Depend- ing on the method used to create the VAX image, these RTLs can be use- ful for images built on later versions of OpenVMS VAX, which do not use features that were developed since OpenVMS VAX Version 5.5-2. Translated image RTLs are used to support a few architectural features that differ between VAX and Alpha systems, such as VAX D-float and H- float. They also support programs converted to run on Alpha systems before native Alpha compilers were available for particular program- ming languages. Many Compaq languages adhere to the common calling standard. This means that routines written in any of these languages can directly call rou- tines written in any other language. Development of applications us- ing multiple languages is simple and straightforward. All user-accessible routines in the RTLs follow the OpenVMS Alpha or OpenVMS VAX calling standard and condition-handling conventions, and most are contained within shareable images. At a lower level, programs can call system services directly for se- curity, event flag, asynchronous system trap, logical name, record and file I/O, process control, timer, time conversion, condition handling, lock management, and memory management. Again, system services use the OpenVMS VAX or OpenVMS Alpha calling standard and condition-handling conventions. OpenVMS supports the execution of user-mode images created on earlier versions of OpenVMS. Typically, recompiling and relinking are not re- quired. MACRO Compiler (Alpha Only) 7 For migration purposes, the MACRO compiler is supplied with the Open- VMS Alpha software. With minor modifications, VAX MACRO-32 sources can be compiled for ex- ecution on Alpha. DECthreads OpenVMS includes a user-mode, multithreading capability called DEC- threads. DECthreads provides a POSIX 1003.1-1996 standard style threads interface. Additionally, DECthreads provides an interface that is the OpenVMS implementation of Distributed Computing Environment (DCE) threads as defined by the Open Software Foundation (OSF). DECthreads is a library of run-time routines that allows the user to create multiple threads of execution within a single address space. With DECthreads Kernel Threads features enabled, DECthreads provide for concurrent processing across all CPUs in a multiprocessor system by allowing a multithreaded application to have a thread executing on every CPU. Multithreading allows computation activity to overlap I/O activity. Synchronization elements, such as mutexes and condition vari- ables, are provided to help ensure that shared resources are accessed correctly. For scheduling and prioritizing threads, DECthreads pro- vides multiple scheduling policies. For debugging multithreaded ap- plications, DECthreads is supported by the OpenVMS Debugger. DECthreads also provides Thread Independent Services (TIS), which assist in the development of thread-safe APIs. Librarian Utility The Librarian utility permits storage of object modules, image files, macros, help text, or any general record-oriented information in cen- tral, easily accessible files. Object module and image file libraries are searched by the linker when the linker finds a reference it can- not resolve in one of its input files. Alpha macro libraries are searched by the MACRO-32 compiler and MACRO-64 assembler when either finds a macro name that is not defined in the input file. VAX macro libraries are searched by the MACRO-32 assembler when the assembler finds a macro that is not defined in the input 8 Hypersort Hypersort is a portable library of user-callable routines that pro- vide a high-performance sorting capability for Alpha systems Traceback Facility When an application is compiled and linked with traceback information, the Traceback facility translates stack frameOP addresses into rou- tine names and line numbers and displays a symbolic traceback when- ever a runtime error occurs in that application. Debugger The OpenVMS Debugger allows users to trace program execution, as well as display and modify register contents using the same symbols that are present in the source code. The debugger contains a Heap Analyzer feature that displays a graphic view of memory allocations and deallocations in real time. Alpha System-Code Debugger The OpenVMS Alpha System-Code Debugger is a kernel code debugger. It allows a system code developer to trace the execution of nonpageable system code at any Interrupt Priority Level (IPL). Based on the OpenVMS Alpha Debugger, the system-code debugger uses the same interface and most of the same command set. System Dump Analyzer (SDA) Utility In the event of a system failure, OpenVMS writes the contents of mem- ory to a preallocated dump file. This dump file can later be analyzed using SDA. System dumps can either be full memory dumps, where all mem- ory is written, or selective memory dumps, where only portions of mem- ory in use at the time of the system failure is written. The dump file can be located on any locally connected disk. On Alpha only, dump com- pression allows both full and selective dumps to be written to smaller files than required for uncompressed dumps. Full memory dumps, if not 9 compressed, require a dump file big enough to hold all memory. Selec- tive memory dumps write as much of the memory in use at the time of the system failure that will fit into the dump file. RMS File Utilities RMS file utilities allow users to analyze the internal structure of an RMS file and tune the I/O, memory, space and performance parame- ters of the file. The RMS file utilities can also be used to create, load, and reclaim space in an RMS file. Refer to the Operating Sys- tem Environment section of this SPD for more information on RMS. File Differences Utility This utility compares the contents of two files and lists those records that do not match. Translated Image Environment (TIE) (Alpha Only) OpenVMS Alpha provides an array of services that allow the operation of programs which have undergone binary translation from OpenVMS VAX images. These programs perform virtually all user-mode functions on OpenVMS Alpha and operate in combination with other programs (images) that have been translated from OpenVMS VAX or have been built using native compilers on OpenVMS Alpha. Without requiring special source code, the TIE resolves differences between the VAX and Alpha archi- tectures, including floating-point registers, condition codes, excep- tion handling, and ASTs. The TIE included with OpenVMS Alpha can run images that have been translated elsewhere. SYSTEM MANAGEMENT ENVIRONMENT OpenVMS provides a variety of features that aid the system manager in configuring and maintaining an optimal system. The following features are available to system managers. OpenVMS Management Station Version 3.0 10 The OpenVMS Management Station is a Windows PC-based tool that allows management of one or more OpenVMS Cluster systems from a single point of control. Three functional areas are now implemented in OpenVMS Man- agement Station: user account management, printer queue management, and storage configuration management. For user account management, Open- VMS Management Station supports account creation, modification, and deletion, as well as renaming accounts and displaying account attributes. The OpenVMS Management Station makes it possible to easily modify many accounts in a single operation. It provides a comprehensive interface to the user account management features. Printer queue management makes it possible for system managers to man- age all the printers, print queues, and jobs in their environment us- ing a centralized Windows GUI. This includes performing such tasks as monitoring one or more printers, adding and removing printers and their associated queues, examining and modifying queue and printer attributes, and requeuing or deleting jobs. In addition, printer configuration in- formation can be stored in a permanent database to ensure that the printer configuration is recreated easily and accurately at reboot. Storage configuration functionality, new in Version 3.0, provides for management of disk storage devices across multiple OpenVMS Cluster sys- tems. This enables creation, modification, deletion, and management of storage devices from a Windows interface. A wizard is included to make it easy to create a volume. A persistent database is provided that can automatically determine and configure your system's storage at system startup. The OpenVMS Man- agement Station mounts volumes much faster than is possible with DCL or command procedures so performance is enhanced. Version 3.0 of the OpenVMS Management Station is based on the Microsoft Management Console (MMC). MMC provides a common management framework for various administration programs. The OpenVMS Management Station is implemented as an MMC snap-in and includes all of the MMC compo- nents you need. 11 The OpenVMS Management Station Version 3.0 supports the following soft- ware: o OpenVMS Version 6.2 or higher o TCP/IP on both the client and server o For the PC client, Microsoft Windows NT Version 4.0 Service Pack 3 or higher, or Windows 95 or higher o Microsoft Internet Explorer Version 3.0 or higher Restrictions: The following restrictions apply to the OpenVMS Manage- ment Station: o Managing OpenVMS Cluster members as individual nodes is not sup- ported. OpenVMS Cluster systems are treated as indivisible enti- ties. o OpenVMS Cluster systems with multiple user authorization files are not supported. o Only the TCP/IP protocol is supported for communication between the PC client and the OpenVMS primary server. Both TCP/IP and DECnet- Plus are supported as transports between OpenVMS systems. DECamds DECamds Version 7.2 is available on the OpenVMS distribution kit. DE- Camds is a separately installable, real-time, high-performance, mul- tisystem monitoring utility. It is supported on any system running Open- VMS Version 7.1 or higher. With OpenVMS Version 7.1, the right to use DECamds was included under the terms and conditions of the OpenVMS op- erating system base license (both Alpha and VAX). DECamds provides system resource monitoring, investigation aid, and correction capability. This enables system managers to proactively and effectively manage multiple systems from a centralized DECwindows dis- play. 12 DECamds software includes an OpenVMS device driver, which is installed on every node on the LAN that is to be monitored. The software also includes two GUI applications that allow a system manager to perform monitoring functions. One is an X compliant, Motif application that can be installed on any OpenVMS Alpha or VAX workstation. The other is a Java application that can be installed in any NT Intel, NT Al- pha and OpenVMS Alpha Java environment. Batch and Print Queuing System OpenVMS provides an extensive batch and print capability that allows the creation of queues and the setup of spooled devices to process non- interactive workloads in parallel with timesharing or real-time jobs. The OpenVMS batch and print operations support two types of queues: generic queues and execution queues. A generic queue is an interme- diate queue that holds a job until an appropriate execution queue be- comes available to initiate the job. An execution queue is a queue through which the job (either print or batch) is actually processed. The system queues batch jobs for execution. The system manager can reg- ulate the number of queues and the number of streams per queue (the number of batch jobs in the queue that can execute concurrently). Both generic and execution batch queues can have different attributes, such as the maximum CPU time permitted, working set size, and prior- ity. Facilities are provided for starting and stopping queues and for starting and stopping jobs in a queue. Because multiple execution queues can be associated with a generic queue, OpenVMS VAX enables load bal- ancing across available CPUs in an OpenVMS Cluster system, increas- ing overall system throughput. Print queues, both generic and execution, together with queue manage- ment facilities, provide versatile print capabilities, including sup- port for various print file formats. The maximum number of process identifiers for queuing requests is 1024. Accounting Utility 13 For accounting purposes, OpenVMS keeps records of system resource us- age. These statistics include processor and memory utilization, I/O counts, print symbiont line counts, image activation counts, and pro- cess termination records. The OpenVMS Accounting utility allows you to generate various reports using this data. Audit Analysis Utility For security auditing purposes, OpenVMS selectively records critical, security-relevant events in the system security audit log file. These records contain the date and time the event occurred, the identity of the associated user process, and information specific to each event type. This information helps the system manager maintain system se- curity and deter possible intruders. The OpenVMS Audit Analysis util- ity allows you to generate various reports from this data. Autoconfigure/AUTOGEN Utilities The Autoconfigure and AUTOGEN utilities automatically configure the available devices in the system tables and set system parameters based on the peripheral and memory architecture. This eliminates the need for a traditional system generation process when the hardware config- uration is expanded or otherwise modified. The OpenVMS AUTOGEN command procedure sets several system parameters automatically by detecting the devices installed in a configuration. A feedback option allows you to generate a report of recommended pa- rameter settings based on previous usage patterns. Backup Utility The Backup utility provides both full-volume and incremental file back- ups for file-structured, mounted volumes and volume sets. Individual files, selected directory structures, or all files on a volume set can be backed up and restored. Files can be selected by various dates (such as creation or modification) and can be backed up to magnetic tape, magnetic disk, or Write Once Read Many (WORM) optical disk. The Backup utility can also be used to restore a save set or list the contents of a save set. 14 A BACKUP API has been added for invoking backup routines from an ex- ecutable procedure. The Backup Manager for OpenVMS provides a screen-oriented interface to the Backup utility that assists users in performing routine backup operations. The Backup Manager is menu driven and provides: o Access to the save, restore, and list operations without having to understand Backup command syntax o The ability to create, modify, recall, and delete Backup Manager templates that describe the Backup save operations The Backup Manager works on all supported OpenVMS configurations with a video terminal. It uses the Screen Management (SMG) RTL routines to provide a window-like user interface. The software does not assume any privilege on the part of its user beyond access to the files and de- vices being operated upon. Standalone BACKUP Utility (VAX Only) Standalone BACKUP provides a mechanism for system managers to back up and restore system disks. This utility can also be used during the in- stallation of the OpenVMS VAX operating system. Analyze Disk Structure Utility The Analyze Disk Structure utility compares the structure information on a disk volume with the contents of the disk, prints the structure information, and permits changes to that information. It can also be used to repair errors detected in the file structure of disks. Monitor Utility The Monitor utility enables the system manager to monitor different classes of systemwide performance data including: process activity, I/O activity, memory-management activity, vector-processing activity (VAX only), and two-phase, commit-transaction activity at specified intervals. The data can be displayed as it is gathered or saved in a file for later use. 15 License Management Facility (LMF) The License Management facility allows the system manager to enable software licenses and to determine which software products are licensed on an OpenVMS system. System Management Utility (SYSMAN) The System Management utility allows system managers to define a man- agement environment in which operations performed from the local Open- VMS system can be executed on all other OpenVMS systems in the envi- ronment. The environment can include OpenVMS Alpha and VAX systems con- figured in an OpenVMS Cluster or multiple systems networked through DECnet or DECnet-Plus. Operations OpenVMS allows for varying levels of privilege to be assigned to dif- ferent operators. Operators can use the OpenVMS Help Message utility to receive online descriptions of error messages. In addition, system- generated messages can be routed to different terminals based on their interest to the console operators, tape librarians, security admin- istrators, and system managers. Security Per-Thread Security Profiles OpenVMS Version 7.2 introduces thread-level security which allows for simplified multiprofile application development and improves overall performance while maintaining a high level of security. This feature allows each execution thread of a multithreaded process to run an in- dependent security profile without impacting the security profiles of other threads in the process. This feature, known as Per-thread security profiles, includes a new security structure, known as the Persona Security Block (PSB), which supersedes many process-wide structures and fields including the ARB, JIB username and account information, PHD privilege bits, and the PCB NOAUDIT cell. 16 A new SYSGEN parameter, ARB_SUPPORT, has been added to allow system managers to control the level by which the current security data in the PSB will be backported to these old privilege data cells. There are four levels of support ranging from NONE (ARB_SUPPPORT = 0) to FULL (ARB_SUPPORT = 3). External Authentication External authentication is an optional feature introduced in OpenVMS Version 7.1 that enables OpenVMS systems to authenticate designated users within a LAN Manager domain using their LAN Manager user name and password. Starting with OpenVMS Version 7.2, if you want to enable external au- thentication on your system, you need DECwindows Version 1.2-4 or later and any requirements outlined in the Advanced Server for OpenVMS Server and Installation Guide. See this manual and the OpenVMS Guide to Sys- tem Security for detailed information about using external authenti- cation. Users who are externally authenticated by their LAN Manager need only remember a single user name/password combination to gain access to their OpenVMS and LAN Manager accounts. In addition, the OpenVMS DCL com- mand SET PASSWORD has been enhanced to update the user's password in the LAN Manager domain database (as well as optionally synchronize the SYSUAF password). For externally authenticated users, the normal system authorization database (SYSUAF.DAT) is used to construct the OpenVMS process pro- file (UIC, privileges, quotas, and so on) and to apply specific lo- gin restrictions. However, there are two key differences between ex- ternally authenticated users and normal OpenVMS users. For externally authenticated users: o The password stored in the SYSUAF is not the password used to ver- ify the user at login time. 17 o The SYSUAF user name selected to be used for OpenVMS process iden- tification may not be the same as the LAN Manager user name that was used to authenticate the user at login. The system manager spec- ifies the LAN Manager to OpenVMS user name mapping for each user. Security APIs With OpenVMS Version 6.2, security APIs for intrusion detection, proxy access, and impersonation services were added on both the Alpha and VAX platforms to provide better security in client/server applications. With OpenVMS Version 7.2, new Security Persona services provide the ability to support alternate security models. Enhancements to the Open- VMS security persona services in Version 7.2 allow OpenVMSVMS appli- cations the ability to attach NT or any other Non-OpenVMS security cre- dentials to an OpenVMS security profile. Government Security Ratings As the following table illustrates, OpenVMS is committed to consis- tently delivering rated security in our base products. ___________________________________________________________________ Version_______________Rating____Evaluation_Date____________________ OpenVMS Alpha 7.1+ C2 2000 OpenVMS VAX 7.1+ C2 2000 OpenVMS Alpha 6.1 C2 1996 SEVMS Alpha 6.1 B1 1996 OpenVMS VAX 6.1 C2 1995 SEVMS VAX 6.1 B1 1995 OpenVMS VAX 6.0 C2 1993 SEVMS VAX 6.0 B1 1993 VAX/VMS 4.3 C2 1988 ___________________________________________________________________ +Currently_in_Rating_Maintenance_Phase_(RAMP)._____________________ 18 These ratings represent the National Computer Security Center vali- dation of the design of the OpenVMS and SEVMS operating systems against DoD 5200.28-STD Department of Defense Trusted Computer System Eval- uation Criteria. To obtain an evaluation summary, please visit the US NCSC at Trusted Product Evaluation Program (TPEP) homepage at http: //www.radium.ncsc.mil/tpep/. OpenVMS provides a rich set of tools to control user access to system- controlled data structures and devices that store information. Open- VMS employs a reference monitor concept that mediates all access at- tempts between subjects (such as user processes) and security-relevant system objects (such as files). OpenVMS also provides a system secu- rity audit log file that records the results of all object access at- tempts. The audit log can also be used to capture information regard- ing a wide variety of other security-relevant events. The system manager maintains user account information in the system user authorization file (SYSUAF). When creating user accounts with the Authorize utility, the system manager assigns the privileges and quo- tas associated with each user account. The system manager also assigns a user name, password, and unique user identification code (UIC) to each account. Additional identifiers can be assigned to each account, allowing users to belong to multiple overlapping groups or projects. The system manager can limit account use by the time of day, day of week, and type of access, such as local, remote, network, or batch. To log in and gain access to the system, the user must supply a valid user name and password. The password is encoded and does not appear on terminal displays. Users can change their password voluntarily, or the system manager can specify how frequently passwords change, along with minimum password length, and the use of randomly generated pass- words. OpenVMS provides a password dictionary filter that screens password choices for common words, and a user password history filter that pre- vents users from reusing passwords that they have used within the past year. In addition to these built-in filters, a site can design and in- stall its own filter to screen passwords according to a site-specific password policy. 19 The system password hash algorithm can also be replaced with a pri- vate algorithm for those sites that have contractual obligations to use specific public or private password encryption algorithms. The sys- tem manager can enable this feature on a per-user, per-password ba- sis. Login security includes break-in detection, which disables terminals when password guessing is detected. Users retain a secure login path, which can thwart Trojan horse attacks against local terminals. Addi- tionally, the system manager can associate a system password with dial- in terminal lines to prevent the display of any operating system-specific identification that might yield clues to possible attack methods. When a user logs in, the system displays a message stating when the last login for the account occurred and the number of failed attempts since the last successful login. Every security-relevant system object is labeled with the UIC of its owner along with a simple protection mask. The owner UIC consists of two fields: the user field and a group field. System objects also have a protection mask that allows read, write, execute, and delete access to the object's owner, group, privileged system users, and to all other users. The system manager can protect system objects with access con- trol lists (ACLs) that allow access to be granted or denied to a list of individual users, groups, or identifiers. ACLs can also be used to audit access attempts to critical system objects. OpenVMS applies full protection to the following system objects: o Capabilities (VAX only) o Common event flag clusters o Devices o Files o Group global sections o Logical name tables o Batch/print queues o Resource domains 20 o Security classes o System global sections o Volumes (ODS-2) o Volumes (ODS-5) OpenVMS provides security attribute defaults in the form of security profile templates. These templates are referenced whenever a new ob- ject is created and provide a means of associating default security information with each system object class, except for files. Protec- tion information for files is inherited from the previous version of an existing file, the parent directory, or the default protection of the creating process. Data scavenging protection can be enabled in the form of high-water marking and erase-on-delete attributes. These attributes ensure that the contents of a file cannot be read after the file has been deleted. The system manager can enforce file erasure on a per-volume basis. The system manager can also replace the disk erasure pattern with a pri- vate pattern for those sites that have contractual obligations to use a specific pattern. Security auditing is provided for the selective recording of security- related events. This auditing information can be directed to security operator terminals (alarms) or to the system security audit log file (audits). Each audit record contains the date and time of the event, the identity of the associated user process, and additional informa- tion specific to each event. OpenVMS provides security auditing for the following events: o Login and logout o Login failures and break-in attempts o Object creation, access, deaccess, and deletion; selectable by use of privilege, type of access, and on individual objects o Authorization database changes 21 o Network logical link connections for DECnet for OpenVMS, DECnet- Plus, DECwindows, IPC, and SYSMAN o Use of identifiers or privileges o Installed image additions, deletions, and replacements o Volume mounts and dismounts o Use of the Network Control Program (NCP) utility o Use or failed use of individual privileges o Use of individual process control system services o System parameter changes o System time changes and recalibrations Note: Because no system can provide complete security, Compaq cannot guarantee complete system security. However, Compaq continues to en- hance the security capabilities of its products. Customers are strongly advised to follow all industry-recognized security practices. Open- VMS recommended procedures are included in the OpenVMS Guide to Sys- tem Security. OPERATING SYSTEM ENVIRONMENT OpenVMS VAX Processes and Scheduling The basic unit of execution in OpenVMS VAX is the process. A process consists of individual address space and registers known as context, and code called an executable image. The context identifies the pro- cess and describes its current state. Executable images consist of sys- tem programs and user programs that have been compiled and linked. The maximum number of concurrent processes is 8,192 per OpenVMS VAX system. 22 Processes receive time to execute their images based on the priority. Thirty-two priorities are recognized on OpenVMS VAX, and 64 priori- ties are recognized on OpenVMS Alpha. Priorities 0 to 15 are for time- sharing processes and applications that are not time critical (four is the typical default for timesharing processes). Priorities 16 to 32 on VAX and 16 to 63 on Alpha are for real-time processes. Each time an event such as an I/O interrupt occurs, the system ser- vices the event first and then passes control to the highest prior- ity process ready to execute. The system automatically adjusts the pri- orities of processes in the range of 0 to 15 to favor I/O-bound and interactive processes. However, the system does not adjust the pri- ority of a process in the range of 16 to 31 for VAX or 16 to 63 for Alpha. Real-time processes can be assigned higher priorities to ensure that they receive processor time whenever they are ready to execute. Real- time processes are scheduled preemptively; that is, if a real-time pro- cess is ready to execute, it is given to the processor immediately, unless a process with a higher priority is ready to execute. OpenVMS uses paging and swapping to provide sufficient virtual mem- ory for concurrently executing processes. Paging and swapping are also provided for processes whose memory requirements exceed available phys- ical memory. The maximum working set size is 512 MB of memory for VAX and 4 GB for Alpha. Programmers can control memory management from within an image. An im- age executing in a real-time process, for example, can inhibit pag- ing or swapping of critical code and data. Peripheral devices can be managed by the system or allocated by in- dividual processes. At least one disk must be a system disk. Other disks can be designated as data disks for the general use of all users log- ging in to the system or for a specific group of users. The system con- trols interactive terminals and one or more printers. OpenVMS Alpha Processes and Scheduling 23 The basic unit of execution in OpenVMS Alpha is the kernel thread. A kernel thread consists of individual address space and registers known as context, and code called an executable image. The context identi- fies the kernel thread and describes its current state. Each process can have up to 16 kernel threads. Executable images consist of sys- tem programs and user programs that have been compiled and linked. The maximum number of concurrent processes is 16,384 per OpenVMS Al- pha system. Kernel threads receive processor time to execute their images based on the priority of the process. Thirty-two priorities are recognized on OpenVMS VAX, and 64 priorities are recognized on OpenVMS Alpha. Pri- orities 0 to 15 are for time-sharing processes and applications that are not time critical (four is the typical default for timesharing pro- cesses). Priorities 16 to 32 on VAX and 16 to 63 on Alpha are for real- time processes. Each time an event such as an I/O interrupt occurs, the system first services the event and then passes control to the highest priority ker- nel thread ready to execute. The system adjusts the priorities of ker- nel threads whose base priority is in the range of 0 to 15 to favor I/O-bound and interactive processes. However, the system does not ad- just the priority of a kernel thread in the range of 16 to 31 for VAX or 16 to 63 for Alpha. Real-time processes can be assigned higher priorities to ensure that they receive processor time whenever they are ready to execute. Real- time processes are scheduled preemptively; that is, if a real-time pro- cess is ready to execute, it is given to the processor immediately, unless a higher priority process is ready to execute. OpenVMS uses paging and swapping to provide sufficient virtual mem- ory for concurrently executing processes. Paging and swapping is also provided for processes whose memory requirements exceed available phys- ical memory. Programmers can control memory management from within an image. An im- age executing in a real-time process, for example, can inhibit pag- ing or swapping of critical code and data. 24 Peripheral devices can be managed by the system or allocated by in- dividual processes. At least one disk must be a system disk. Other disks can be designated as data disks for the general use of all users log- ging in to the system or for a specific group of users. The system con- trols interactive terminals and one or more printers. 64-Bit Virtual Addressing (Alpha Only) The OpenVMS Alpha operating system provides support for 64-bit vir- tual memory addressing. This capability makes the 8TB virtual address space, defined by the Alpha architecture, available to the OpenVMS Al- pha operating system and to application programs. Future hardware im- plementations will provide greater capacity. OpenVMS Alpha compilers and applications take advantage of 64-bit processing by using 64-bit data types. Refer to the SPDs for the OpenVMS Alpha compilers for fur- ther details. Note the application virtual address space defaults to a 32-bit implementation for compatibility and migration purposes. Very Large Memory (VLM) Features (Alpha Only) OpenVMS Alpha provides the following additional memory management VLM features beyond those provided by 64-bit virtual addressing: o Memory-resident global sections o Fast I/O for global sections o Shared page tables o Expandable global page table o Reserved memory registry Memory-resident global sections allow a database server to keep larger amounts of "hot" data cached in physical memory. The database server then accesses the data directly from physical memory without perform- ing I/O read operations from the database files on disk. With faster access to the data in physical memory, run-time performance increases dramatically. 25 As of OpenVMS Alpha Version 7.2, VLM applications that share a large memory-resident cache can use Fast I/O for memory shared by processes through global sections. Fast I/O improves the ability of a VLM ap- plication, such as a database server, to handle larger capacities and higher data throughput rates. By reducing the CPU costs per I/O re- quest, Fast I/O and memory-resident global sections dramatically in- crease performance for critical database server I/O operations. Shared page tables allow that same database server to reduce the amount of physical memory consumed within the system. Because multiple server processes share the same physical page tables that map the large database cache, an OpenVMS Alpha system can support more server processes. This increases overall system capacity and decreases response time to client requests. Also, with shared page tables, the database server startup time is dra- matically reduced because server processes can map memory-resident global sections hundreds of times faster than traditional global sections. With a multiple giga-byte global database cache, the server startup performance gains can be significant. The system parameters GBLPAGES and GBLPAGFIL are dynamic parameters. Users with the CMKRNL privilege can change these parameter values on a running system. Increasing the value of the GBLPAGES parameter al- lows the global page table to expand, on demand, up to the new max- imum size. The Reserved Memory Registry supports memory-resident global sections and shared page tables. Through its interface within the SYSMAN util- ity, the Reserved Memory Registry allows an OpenVMS system to be con- figured with large amounts of memory set aside for use within memory- resident sections or other privileged code. The Reserved Memory Reg- 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) 26 With OpenVMS VAX Version 6.0, physical address space was extended from 30 bits to 32 bits. The OpenVMS VAX operating system can provide 3.5 GB of physical memory and .5 GB of I/O and adapter space. This enables large applications and workloads to access the large amounts of phys- ical memory that they require. The following table lists the VAX pro- cessors that support this extended physical addressing. ___________________________________________________________________ Accessible Physical System___________Memory______I/O_and_Adapter_Space_________________ VAX 6000 1.25 GB .5 GB model 600 VAX 7000 3.5 GB .5 GB series VAX 10000 3.5 GB .5 GB series_____________________________________________________________ Vector Processing (VAX Only) A single data item with only one value is known as a scalar value. A group of related scalar values, or elements, with the same data type, is known as a vector. An extension to the VAX architecture defines an optional design for integrated vector processing that has been adopted by several VAX sys- tems. The VAX vector architecture includes sixteen 64-bit vector reg- isters (V0 through V15), each containing 64 elements, vector control registers, vector function units, and a set of vector instructions. VAX vector instructions transfer data between the vector registers and memory, perform integer and floating-point arithmetic; and execute pro- cessor control functions. A more detailed description of the VAX vector architecture, vector reg- isters, and vector instructions appears in the VAX MACRO and Instruc- tion Set Reference Manual. 27 The OpenVMS VAX operating system provides fully shared, multiprogram- ming support for VAX vector processing systems. By default, OpenVMS VAX loads vector support code when initializing vector-present sys- tems but does not load it when initializing vector-absent systems. Sys- tem managers can control this behavior by using the VECTOR_PROC sys- tem parameter. The presence of vector support code in a system has little effect on processes running in a scalar-only system, or scalar processes run- ning in a vector-present system. If many processes must compete si- multaneously for vector processor resources, the system manager can maintain good performance by adjusting system resources and process quotas. The OpenVMS VAX operating system makes the services of the vector pro- cessor available to system users by means of a software abstract known as a capability. A system manager can restrict the use of the vector processor to users holding a particular identifier by associating an ACL entry with the VECTOR object. The VAX Vector Instruction Emulation Facility (VVIEF) is a standard feature of the OpenVMS VAX operating system. It allows vectorized ap- plications to be written and debugged in a VAX system in which vec- tor processors are not available. VVIEF emulates the VAX vector pro- cessing environment, including the nonprivileged VAX vector instruc- tions and the OpenVMS VAX vector system services. Use of VVIEF is re- stricted to code in user mode. DECdtm Services The DECdtm services embedded in the OpenVMS operating system support fully distributed databases using a two-phase commit protocol. The DECdtm services provide the technology and features for distributed process- ing, ensuring both transaction and database integrity across multi- ple Compaq resource managers. Updates to distributed databases occur as a single all-or-nothing unit of work, regardless of where the data physically resides. This ensures the consistency of distributed data. 28 DECdtm services allow applications to define global transactions that can include calls to any number of Compaq data management products. Regardless of the mix of data management products used, the global trans- action either commits or aborts. OpenVMS is unique in providing trans- action processing functionality with base operating system services. DECdtm features include: o Embedded OpenVMS system services that support the DECtp architec- ture, providing the features and technology for distributed trans- action processing. o The ability for multiple disjoint resources to be updated atomat- ically. These resources can be either physically disjointed on dif- ferent clusters at separate sites, or logically disjointed in dif- ferent databases on the same node. o Robust application development. Applications can be written to en- sure that data is never in an inconsistent state, even in the event of system failures. o Ability to be called using any Compaq TP monitor or database prod- uct. This is useful for applications using several Compaq database products. Interprocess Communication OpenVMS provides the following facilities for applications that con- sist of multiple cooperating processes: o Mailboxes as virtual devices that allow processes to communicate with queued messages. o Shared memory sections on a single processor or an SMP system that permit multiple processes to access shared address space concur- rently. o Galaxywide sections on a Galaxy platform that permit multiple pro- cesses in multiple instances to access shared address space con- currently. o Common event flags that provide simple synchronization. 29 o A lock manager that provides a more comprehensive enqueue/dequeue facility with multilevel locks, values, and asynchronous system traps (ASTs). o Intracluster communication services through which two processes run- ning on the same system or on different OpenVMS Cluster nodes can establish a connection and exchange data. o Logical names through which one process can pass information to other processes running on the same system or on different OpenVMS Clus- ter nodes. o Network interprocess communication is available via TCP/IP Services and DECnet-PLUS (product licenses are required). Symmetric Multiprocessing (SMP) OpenVMS provides symmetric multiprocessing (SMP) support for both Al- pha and VAX multiprocessor systems. SMP is a form of tightly coupled multiprocessing in which all processors perform operations simulta- neously. The processors can perform operations in all OpenVMS access modes, such as user, supervisor, executive, and kernel. OpenVMS SMP configurations consist of multiple CPUs executing code from a single shared memory address space. Users and processes share a sin- gle copy of OpenVMS Alpha or OpenVMS VAX address space. SMP also pro- vides simultaneous shared access to common data in global sections to all processors. OpenVMS SMP selects the CPU where a process will run based on its priority. SMP support is an integral part of OpenVMS and is provided to the user transparently. Because an SMP system is a single system entity, it is configured into a network and OpenVMS Cluster configurations as a sin- gle node. Networking Facilities 30 OpenVMS provides device drivers for all Compaq local area network (LAN) adapters listed in the LAN Options section of Appendix A of this SPD. Application programmers can use the QIO system service to communicate with other systems connected via the LAN using either Ethernet or In- stitute of Electrical and Electronics Engineer (IEEE) 802.3 packet for- mat. Simultaneous use of Compaq Ethernet and the IEEE 802.3 protocols are supported on any Compaq LAN adapter. OpenVMS supports the standards defined by the ATM Forum's LANE Ver- sion 1.0 specifications for LAN emulation over an ATM network. By im- plementing an emulated LAN over an ATM network, you enable a group of ATM stations to act like a traditional LAN. LAN emulated over an ATM network allows you to run your existing applications basically unchanged, while the computers on which your applications are running are con- nected to the ATM network. OpenVMS implements the standards defined in RFC 1577 (Classical IP over ATM). This implementation introduces the necessary system interface for Classical IP (CLIP) over an ATM network, and enables CLIP and ARP protocols in an ATM network environment to be configured as a logi- cal IP subnetwork (LIS). Consult your IP product documentation for the status of support of IP over this interface. DECnet-Plus offers task-to-task communications, file management, down- line system and task loading, network command terminals, and network resource sharing capabilities as defined in the DIGITAL Network Ar- chitecture (DNA) Phase V protocols. DECnet-Plus provides the newest DECnet features such as extended addressing and downline-load perfor- mance enhancements. DECnet-Plus integrates DECnet and OSI protocols and now provides a linkage to TCP/IP using Request for Comments (RFC) 1006 and RFC 1859. DECnet and OSI applications can now be run over DEC- net (NSP), OSI (CLNS), and TCP/IP transports. DECnet for OpenVMS VAX and Alpha offers the networking capabilities as defined in the DIGITAL Network Architecture (DNA) Phase IV. For more information, refer to the DECnet-Plus and DECnet Software portion of the Associated Products section of this SPD. Terminal Server Products 31 Compaq's terminal server products provide terminal server access to OpenVMS. When used in an OpenVMS Cluster environment, terminal servers distribute users across the available Alpha and VAX systems at login time. OpenVMS can also establish a connection to other devices (such as print- ers) attached to such terminal servers. Reliability OpenVMS handles hardware errors as transparently as possible while main- taining data integrity and providing sufficient information to diag- nose errors. The system limits the effects of an error by first de- termining if the error is fatal. If the error occurs in system con- text, the current OpenVMS system shuts down. If the error is not fa- tal, the system recovers actions pertinent to the error and contin- ues the current operation. In all cases, information relevant to the error is written to the er- ror log file for later analysis. Hardware errors include the follow- ing categories: o Processor errors. These include processor soft errors, processor hard errors, processor machine checks, and adapter errors. o Memory errors. These can be unrecoverable (hard) errors or recov- erable (soft) errors. The system examines memory at startup time and does not use any bad pages. During system operation, the sys- tem corrects all single-bit memory errors for those systems with error correction code (ECC) memory. On OpenVMS VAX, an unrecover- able error causes the memory page on which the error occurred to be added to the bad page list. If the page has not been modified, system operation continues with a new copy of the page. o Correctable memory errors. A primary cause of these correctable mem- ory errors is alpha particle radiation. On some processors, when correctable memory errors occur, the memory controller corrects only the data returned to the CPU or I/O controller. The actual data in memory is left with the error intact. Subsequent read operations cause correction cycles to occur and, in most cases, an interrupt 32 to report the error. On many of these processors, OpenVMS monitors the occurrence of correctable memory errors and, in almost all cases, is able to remove the error condition by rewriting the data in mem- ory. Rewriting the data causes the data to be corrected in that mem- ory location. On OpenVMS VAX, if the cause of the error is not tran- sient, and the error condition persists, the operating system at- tempts to move the data from the existing page, which contains the error, to a new page. The original page is then retired from use. Other failures include: o Operating system errors (system-detected inconsistencies or archi- tectural errors in system context) o User errors o I/O errors The system logs all processor errors, all operating system errors de- tected through internal consistency checks, all double-bit memory er- rors (and a summary of corrected single-bit memory errors), and most I/O errors. If the system is shut down because of an unrecoverable hardware or soft- ware error, a dump of physical memory is written. The dump includes the contents of the processor registers. The OpenVMS System Dump An- alyzer (SDA) utility is provided for analyzing memory dumps. Power Failures (VAX Only) If the power fails, the system shuts down automatically. When power is restored, the system restarts automatically and resumes process- ing at the point of interruption under these circumstances: o If the system has a time-of-day clock and a memory battery backup unit o If the contents of memory are still valid o If the system is set to permit automatic rebooting 33 The system restarts device and communication lines and all I/O oper- ations in progress, including magnetic tape I/O operations. On request, programs can be notified of power restoration. An optional battery- operated hardware clock resets the date and time of day when the sys- tem restarts. If the system does not have a battery backup unit, or if the memory contents are not valid on power restoration, the sys- tem reboots automatically if it is set to permit automatic rebooting. If, for any reason, after a power failure the system disk does not come back on line within a specific time after the CPU regains power, the system shuts down. Input/Output The QIO system service and other related I/O services provide a di- rect interface to the operating system's I/O routines. These services are available from within most OpenVMS programming languages and can be used to perform low-level I/O operations efficiently with a min- imal amount of system overhead for time-critical applications. Device drivers execute I/O instructions to transfer data to and from a device and to communicate directly with an I/O device. Each type of I/O device requires its own driver. Compaq supplies drivers for all devices supported by the OpenVMS operating system and provides QIO sys- tem service routines to access the special features available in many of these devices. OpenVMS supports a variety of disk and tape peripheral devices, as well as terminals, networks, and mailboxes (virtual devices for interpro- cess communication), and more general I/O devices. With OpenVMS Alpha, users can write drivers for I/O devices that do not have inherent OpenVMS support. OpenVMS Alpha allows device drivers to be written in DEC C and MACRO-32. Documentation is available that describes how to write OpenVMS Alpha device drivers and how to con- vert existing OpenVMS VAX drivers to run on OpenVMS Alpha systems. The DEC C compiler for OpenVMS Alpha is an optional layered product. 34 With OpenVMS VAX, users can write their own drivers in MACRO-32 for I/O devices that do not have inherent OpenVMS support, as described in the appropriate documentation. I/O Performance Features Fast I/O provides a suite of additional system services that appli- cations can use to improve I/O throughput. The fast I/O services min- imize the CPU resources required to perform I/O. Fast Path provides a streamlined mainline code path through the I/O subsystem to improve both uniprocessor and multiprocessor I/O perfor- mance. On multiprocessor systems, Fast Path allows all CPU process- ing for specific I/O adapters to be handled by a specific CPU. This can significantly lower the demands on the primary CPU and increase the I/O throughput on multiprocessor systems with multiple I/O ports. The CI port and DSA disk drivers have been enhanced to take advantage of the Fast Path capability. No user application changes are needed to take advantage of Fast Path. Fast Path can be utilized by the $QIO system service or the Fast I/O services. Virtual I/O Cache OpenVMS provides a standalone or clusterwide, file-oriented disk cache. Applications benefit from the advantages of the virtual I/O cache with- out any special coding. The virtual I/O file-caching algorithm is cho- sen based on the type of clusterwide access currently in progress. Vir- tual I/O caching reduces current and potential I/O bottlenecks within OpenVMS systems. It reduces the number of I/Os to the disk subsystem, thereby reducing systemwide bottlenecks. Record Management Services (RMS) RMS is a set of I/O services that helps application programs to pro- cess and manage files and records. Although it is intended to provide a comprehensive software interface to mass storage devices, RMS also supports device-independent access to unit-record devices. 35 RMS supports sequential, relative, and indexed file organizations in fixed-length and variable-length record formats. RMS also supports byte stream formats for sequential file organization. RMS record access modes provide access to records in four ways: o Sequentially o Directly by key value o Directly by relative record number o Directly by record file address RMS also supports block I/O operations for various performance-critical applications that require user-defined file organizations and record formats. RMS promotes safe and efficient file sharing by providing multiple file access modes and automatic record locking (where applicable). RMS of- fers the options of enabling global buffers for buffer sharing by mul- tiple processes. RMS utilities aid file creation and record maintenance. These util- ities convert files from one organization and format to another; re- structure indexed files for storage and access efficiency; and reclaim data structures within indexed files. These utilities also generate appropriate reports. For systems that have DECnet for OpenVMS VAX and Alpha, or DECnet-Plus installed, RMS provides a subset of file and record management ser- vices to remote network nodes. Remote file operations are generally transparent to user programs. Commands such as EDIT, CREATE, COPY, TYPE, and PRINT allow users to manipulate RMS records within RMS files at the DCL command level. Disk and Tape Volumes 36 The system manager can organize disk volumes into volume sets. Vol- ume sets can contain a mix of disk device types and can be extended by adding volumes. Within a volume set, files of any organization type can span multiple volumes. Files can be allocated to the set as a whole (the default) or to specific volumes within the set. Optionally, the system manager can allocate portions of indexed files to specific ar- eas of a single disk or to specific volumes in a volume set. The system manager can place quotas on a disk to control the amount of space individual users can allocate. Quota assignment is made by UIC and can be controlled for each individual volume set in the sys- tem (or for each individual volume if the volume is not part of a set). The system manager can cache disk structure information in memory to reduce the I/O overhead required for file management services. Although not required to do so, users can preallocate space and control auto- matic allocation. For example, a file can be extended by a given num- ber of blocks, contiguously or noncontiguously, for optimal file sys- tem performance. The system applies software validity checks and checksums to criti- cal disk structure information. If a disk is improperly dismounted be- cause of user error or system failure, the system rebuilds the disk's structure information automatically the next time the disk is mounted. The system detects bad blocks and prevents their reuse once the files to which the blocks were allocated are deleted. On DIGITAL Storage Ar- chitecture (DSA) disks, the disk controller detects and replaces bad blocks automatically. The system provides 255 levels of named directories and subdirecto- ries whose contents are alphabetically ordered. Device and file spec- ifications follow Compaq conventions. Users can use logical names to abbreviate the specifications and to make application programs device and file name independent. Users can assign a logical name to an en- tire specification, to a portion of a specification, or to another log- ical name. 37 OpenVMS supports multivolume magnetic tape files with transparent vol- ume switching. Access positioning is done either by file name or by relative file position. ASSOCIATED PRODUCTS Compaq Galaxy Software Architecture on OpenVMS Alpha The Compaq Galaxy Software Architecture on OpenVMS Alpha is available as a separately licensed System Integrated Product (SIP). By running multiple instances of OpenVMS in a single computer, an Open- VMS Galaxy computing environment gives you quantum improvements in: o Compatibility-Existing applications run without changes. o Availability-Presents opportunities to upgrade software and expand system capacity without downtime. o Scalability-Offers scaling alternatives that improve performance of SMP and cluster environments. o Adaptability-Physical resources can be dynamically reassigned to meet changing workload demands. o Cost of ownership-Fewer computer systems reduce system management requirements, floor space, and more. For companies looking to improve their ability to manage unpredictable, variable, or growing IT workloads, OpenVMS Galaxy technology provides a flexible way to dynamically reconfigure and manage system resources. An OpenVMS Galaxy computing environment is ideal for high-availability applications, such as: o Database servers o Transaction processing systems o Data warehousing o Data mining 38 o Internet servers With OpenVMS Alpha Version 7.2, you can create an OpenVMS Galaxy com- puting environment that allows you to: o Run three instances of OpenVMS on an AlphaServer 8400 o Run two instances of OpenVMS on an AlphaServer 8200 o Run two instances of OpenVMS on an AlphaServer 4100 o Reassign CPUs between instances o Perform independent booting and shutdown of instances o Use shared memory for inter-instance communication o Cluster instances within an OpenVMS Galaxy using the shared mem- ory cluster interconnect o Cluster instances with non-Galaxy systems o Create applications using OpenVMS Galaxy APIs for resource manage- ment, event notification, locking for synchronization, and shared memory for global sections o Use the Galaxy Configuration Utility to view and control the Open- VMS Galaxy environment o Run a single-instance OpenVMS Galaxy on any Alpha system for ap- plication development Compaq Galaxy Software Architecture on OpenVMS Alpha requires Open- VMS Alpha Version 7.2 or later. For more information about OpenVMS Galaxy licensing requirements, re- fer to the Galaxy Software Architecture on OpenVMS Alpha Software Prod- uct Description (SPD 70.44.xx). For more information about how to create, manage, and use an OpenVMS Galaxy computing environment, refer to the OpenVMS Alpha Galaxy Guide. This book includes: o OpenVMS Galaxy hardware and configuration requirements 39 o Procedures for creating OpenVMS Galaxy computing environments on OpenVMS AlphaServer 8400, 8200, and 4100 systems o Complete details about how to use all of the OpenVMS Galaxy fea- tures and capabilities available in OpenVMS Alpha Version 7.2 COM for OpenVMS Component Object Model (COM) is a technology from Microsoft that al- lows developers to create distributed network objects. DIGITAL and Mi- crosoft jointly developed the COM specification. First released by Mi- crosoft on Windows NT as Network Object Linking and Embedding (NetOLE), and then renamed Distributed COM (DCOM), the COM specification now in- cludes network objects. COM is used to create distributed applications made up of reusable ob- jects. COM locates objects locally or in a network and uses the Re- mote Procedure Call (RPC) wire protocol to communicate between these objects across the network. COM on OpenVMS delivers connectivity and interoperability between Open- VMS and Windows NT systems. With COM for OpenVMS, programmers write distributed applications that run across a heterogeneous environment of systems. COM for OpenVMS is based on the Microsoft COM shipped on Windows NT V4.0 SP3 and implements many of the features of Microsoft COM including activation, automation, monikers, Type Libraries, and structured storage on OpenVMS. COM on OpenVMS requires OpenVMS Alpha Version 7.2 or higher. The binary kit for COM (both developer kit and run-time) ships with the OpenVMS Alpha distribution kit. COM is not available on VAX. To use the developer kit software, customers must purchase a license. For more information, see the COM for OpenVMS Software Product Descrip- tion (SPD 70.45.xx). Netscape FastTrack Server Version 3.01 for OpenVMS Alpha 40 Netscape FastTrack Server Version 3.01 for OpenVMS Alpha, a general- purpose Web server for creating, building, publishing, and serving Web pages and applications, is now bundled with the OpenVMS Alpha Version 7.2 operating system at no additional cost. FastTrack supersedes Netscape Communications and Commerce Servers for OpenVMS and includes an up- grade tool that migrates your configuration from the Communications or Commerce Servers to FastTrack. FastTrack is designed for users who require encrypted communications and scalable performance, and com- bines the reliability of an Internet standards-based Web engine with the ability to quickly and easily set up and publish a sophisticated Web site. FastTrack can be installed and run in a matter of minutes. With FastTrack's Web-based administration interface, users can man- age a Web site from any desktop in the organization. Highlights of FastTrack include: o Web engine based on the HTTP 1.1 standard. o Comprehensive management of users and groups, configurations, and access control. o Client authentication. o Flexible, fine-grained access controls on documents and directo- ries. o Support for the Lightweight Directory Access Protocol (LDAP), so that users and groups can be centrally managed across an organi- zation or even outside it. LDAP support enables administrators to easily manage users and groups, control access to information, change configurations, monitor activity and review log reports. Moreover, all these tasks can be done from an administrator's own Web browser no matter where on the network the administrator resides. Because LDAP is an Internet-standard protocol, administrators can connect to Netscape Directory Server or any LDAP directory outside their organization. o Distributed administration that allows administrative privileges to be shared by multiple people or a subset of capabilities to be delegated. 41 o An advanced platform for building crossware applications through its support of the latest versions of Java, JavaScript, and Live- Connect. o Centralized certificate management. o One-button publishing feature, allowing users to use Netscape Com- municator V4.0, Netscape Navigator Gold, or any other authoring tool that supports the HTTP-put method, to publish a document to a re- mote server with the click of a button. Increasingly, users are cre- ating documents for a single, remote Web site to which they do not necessarily have file system access. Now these users can publish directly to the appropriate Web server without having to use FTP or copy across NFS-mounted drives. o Support for Internet access control lists (ACLs), which restrict read and/or write access to the server. o Security features that restrict access to information stored on the server by: - Supporting Secure Sockets Layer (SSL) V3.0, the widely accepted In- ternet security standard that encrypts the information flow between the server and a Web client - Supporting client authentication to restrict access to documents, directories, and applications based on specific user name/password pairs, groups (collection of users), IP addresses, host names, or domain name client certificates - Supporting 40-bit and 128-bit encryption (128-bit encryption is avail- able for use in the U.S. and Canada only.) Netscape FastTrack Server for OpenVMS Alpha is included in the Open- VMS Alpha Version 7.2 release and is licensed under the OpenVMS li- cense, QL-MT1*. No additional license is required. Netscape FastTrack Version 3.01 for OpenVMS Alpha software is also available at no cost as a downloadable kit from http://www.openvms.digital.com. Netscape FastTrack Version 3.01 for OpenVMS Alpha requires OpenVMS V7.1 or later and DIGITAL TCP/IP Services for OpenVMS Version 4.2 or later. 42 Services for Netscape FastTrack Version 3.01 for OpenVMS Alpha are pro- vided under existing OpenVMS service agreements. Support is available from Compaq only. Java Development Kit Version 1.1.6 for OpenVMS Alpha Java applications can be written once and run on any operating sys- tem that implements the Java run-time environment, which consists pri- marily of the Java Virtual Machine (JVM). OpenVMS Alpha users can now access Java functionality via the Java Development Kit (JDK) Version 1.1.6, which is bundled with the OpenVMS Alpha Version 7.2 operating system. The JDK and Just-In-Time compiler-which significantly improves the run-time performance of Java applications-are also available from the Compaq Java home page as a downloadable kit for OpenVMS Alpha Ver- sion 7.1 or later systems. The Java Development Kit (JDK) Version 1.1.6 is a set of building blocks containing basic development tools and a rich set of class libraries that include: o Java Compiler o Java Virtual Machine o Java Class Libraries o Java Applet Viewer o Java Debugger and other tools Java Development Kit Version 1.1.6 for OpenVMS Alpha features include: o The Java Virtual Machine from JavaSoft o Just-In-Time (JIT) compiler, which will provide increased run-time performance over the interpreter-based Virtual Machine o A POSIX threads (pthreads) implementation which will provide in- creased performance on multiprocessor systems and increased robust interoperability with standards-conforming facilities such as DCE 43 o Two command line interface options which allow you to specify com- mand options using the Sun Microsystems JDK command line switches or traditional OpenVMS command line qualifiers o Flexible options for representing UNIX directory and file speci- fications on an OpenVMS system The Java Development Kit Version 1.1.6 for OpenVMS Alpha is licensed under the OpenVMS license, QL-MT1*. No additional license is required. The Java Development Kit Version 1.1.6 for OpenVMS Alpha requires Open- VMS Alpha Version 7.1 or later. Services for the Java Development Kit for OpenVMS Alpha are provided under existing OpenVMS service agreements. OpenVMS Cluster Software OpenVMS Cluster software is available for Alpha and VAX systems as a separately licensed System Integrated Product (SIP). It provides a highly integrated OpenVMS computing environment that is distributed over mul- tiple systems containing up to 96 nodes. OpenVMS Cluster systems and storage communicate using a combination of the following interconnects: o Memory Channel o CI o DIGITAL Storage Systems Interconnect (DSSI) o Fiber Distributed Data Interface (FDDI) o Ethernet o Small Computer System Interface (SCSI) o Shared Memory Cluster Interconnect (SMCI) (Galaxy only) In addition, when configured with suitable FDDI bridges, OpenVMS Clus- ter configurations can use DS3/T3 and asynchronous transfer mode (ATM) networking infrastructures. 44 Applications running on one or more nodes in an OpenVMS Cluster sys- tem share resources in a coordinated manner. While updating data, the OpenVMS Cluster software synchronizes access to shared resources, pre- venting multiple processes on any node in the cluster from uncoordi- nated access to shared data. This coordination ensures data integrity during concurrent update transactions. Application programs specify the level of OpenVMS Cluster file sharing that is required; access is then coordinated by the extended QIO processor (XQP) and Record Man- agement System (RMS). The OpenVMS queue manager controls the OpenVMS Cluster batch and print queues, which can be accessed by any node in the OpenVMS Cluster. Batch jobs submitted to OpenVMS Cluster queues are routed to any available CPU so that the batch load is shared. The Lock Manager provides synchronized services between systems in a cluster, for use by both system components such as RMS and XQP, and also for direct use by applications. p> Two or more Alpha and VAX com- puters connected to the same Memory Channel, CI, DSSI, or SCSI inter- connect must be configured as members of the same OpenVMS Cluster sys- tem. Mixed-architecture and mixed-version clusters that contain both Alpha systems and VAX systems are supported. OpenVMS Cluster systems provide a uniform computing environment that is highly scalable, highly available, and secure. OpenVMS Cluster soft- ware implements a single-security environment within a cluster con- figuration. The security subsystem ensures that all cluster-visible objects maintain consistent security profiles and that system secu- rity auditing controls operate clusterwide. Refer to the OpenVMS Cluster Software Product Description (SPD 29.78.xx) for more information. Volume Shadowing for OpenVMS Compaq provides Volume Shadowing for OpenVMS Alpha and VAX products for performing disk mirroring operations, using a redundant array of independent disks (RAID) 1 storage strategy. 45 Volume Shadowing for OpenVMS is available for Alpha and VAX systems as a separate licensed System Integration Product (SIP). Volume Shad- owing for OpenVMS provides high data availability for disk devices by ensuring against data loss that results from media deterioration or controller or device failure. This prevents storage subsystem compo- nent failures from interrupting system or application tasks. The system disk and Files-11 On-Disk Structure (ODS-2, ODS-5) data disks can be volume shadowed. Volume Shadowing for OpenVMS supports the clusterwide shadowing of Com- paq SCSI and DSA storage systems. Volume Shadowing for OpenVMS also supports shadowing of all MSCP served DSA disks and Compaq SCSI disks. All disks in a single shadow set must have the same number of logi- cal blocks. Shadow set members can be located on a single system or anywhere in an OpenVMS Cluster system. Disks can be configured on any MSCP or Compaq SCSI-compliant controller. Volume Shadowing for OpenVMS provides fault tolerance resulting from disk media errors or controller errors across the full range of Al- pha and VAX processors and configurations. Shadow set member units can be located on different controllers and OpenVMS Alpha and OpenVMS VAX MSCP servers, providing configuration flexibility and a high degree of data availability. Volume Shadowing for OpenVMS supports up to 10,000 single-member shadow sets, and up to 500 devices in multiple member (two or three member) shadow sets, on a standalone or OpenVMS Cluster system. Phase I of Volume Shadowing (also known as controller-based shadow- ing), which was available in the past on OpenVMS VAX, is no longer sup- ported. The binary kit for Volume Shadowing ships with the OpenVMS Alpha and VAX distribution kits. To run the software, customers must purchase a license. Refer to the Volume Shadowing for OpenVMS Software Prod- uct Description (SPD 27.29.xx) for more information. DECnet-Plus and DECnet Software 46 The DECnet for OpenVMS VAX and Alpha software is a System Integrated Product (SIP) that is licensed separately from the OpenVMS operating system. Refer to the DECnet for OpenVMS VAX and Alpha Software Prod- uct Description (SPD 48.48.xx) for further information on supported communications devices and software features. DECnet-Plus (formerly DECnet/OSI) is licensed separately from the Open- VMS operating system. The license for DECnet for OpenVMS VAX and Al- pha also grants the rights to use DECnet-Plus. Note that only one ver- sion of DECnet can be active on a single system at any one time. Re- fer to the DECnet-Plus for OpenVMS Alpha Software Product Description (SPD 50.45.xx) and the DECnet-Plus for OpenVMS VAX Software Product Description (SPD 25.03.xx)) for further information on supported hard- ware configurations and software features. DIGITAL TCP/IP Services for OpenVMS Internet networking is available through the DIGITAL TCP/IP Services for OpenVMS layered product. This product provides a comprehensive suite of TCP/IP protocols and industry-standard applications for heteroge- neous network communications and resource sharing. Features include Network File System (NFS), File Transfer Protocol (FTP), Dynamic Host Configuration Protocol, the Gateway Route Daemon (GATED), Remote Ter- minal Services (TELNET), and other features. Refer to the DIGITAL TCP/IP Services for OpenVMS Software Product Description (SPD 46.46.xx) for further information. DIGITAL TCP/IP Services for OpenVMS Version 5.0 runs on OpenVMS Ver- sion 7.2 and OpenVMS Version 7.1. RMS Journaling for OpenVMS Compaq provides the RMS Journaling for OpenVMS Alpha and VAX products as separately licensed SIPs that enable a system manager, user, or ap- plication to maintain the data integrity of RMS files in the event of a number of failure scenarios. These journaling products protect RMS file data from becoming lost or inconsistent. 47 RMS Journaling provides the following three types of journaling: o After-image journaling. Allows users to reapply modifications that have been made to a file. This type of journaling allows users to recover files that are inadvertently deleted, lost, or corrupted. RMS Journaling recovers the file by applying the journaled modi- fications to a backup copy, thereby restoring its final state. Ap- plication modifications are not necessary to use after-image jour- naling. o Before-image journaling. Allows users to reverse modifications that have been made to a file. This type of journaling allows users to return a file to a previously known state. This is useful if a file is updated with incorrect or bad data. Application modifications are not necessary to use before-image journaling. o Recovery-unit journaling. Allows users to maintain transaction in- tegrity. A transaction can be defined as a series of file updates on one or more files. If any failure occurs during the transaction, recovery-unit journaling rolls back the partially completed trans- action to its starting point. This allows complex transactions to be completed as an atomic event-partially completed transactions can be avoided. Recovery-unit journaling requires application mod- ification. The binary kit for RMS Journaling ships with the OpenVMS Alpha and VAX distribution kits. To run the software, customers must purchase a li- cense and documentation. Refer to the RMS Journaling for OpenVMS Soft- ware Product Description (SPD 27.58.xx) for more information. DECram for OpenVMS DECram for OpenVMS, a separately orderable layered product, is a disk device driver that improves I/O performance by allowing an OpenVMS sys- tem manager to create pseudo disks (RAMdisks) that reside in main mem- ory. Frequently accessed data can be accessed much faster from a DE- Cram device than from a physical disk device. These RAMdisks can be accessed through the file system just as physical disks are accessed, requiring no change to application or system software. 48 Because main memory is allocated for the DECram device, extra memory is generally required. The OpenVMS system manager can designate the amount of memory dedicated to the DECram device(s) and the files that will be stored on it. The maximum size of a single DECram device on Alpha is 32 GB. The maximum size of a single DECram device on VAX, or using versions of DECram prior to Version 2.3, is 524,280 blocks. Re- fer to the DECram for OpenVMS Software Product Description (SPD 34.26.xx) for more information. DECwindows Motif for OpenVMS Compaq offers a separately licensed layered product called DECwindows Motif for OpenVMS. This product provides support for both OSF/Motif, a standards-based graphical user interface, and the X user interface (XUI) in a single, run-time and development environment. DECwindows Motif displays the OSF/Motif user interface. Because both Motif and XUI are based on X Consortium's X Window System, applications writ- ten on either toolkit will run regardless of which environment the user selects. Refer to the DECwindows Motif for OpenVMS Software Product Description (SPD 42.19.xx) for more information. DECwindows Motif Version 1.2-5 for OpenVMS Alpha delivers the New Desk- top environment for OpenVMS Alpha systems, which is derived from the Common Desktop Environment (CDE) technology. CDE provides and defines a consistent user interface for end users and a consistent develop- ment environment for application developers across multiple platforms. The OpenVMS software installation procedure contains an optional step to install the DECwindows Motif for OpenVMS workstation and font sup- port, which is required to run the DECwindows Motif for OpenVMS lay- ered product. Refer to the OpenVMS Alpha Version 7.2 Upgrade and In- stallation Manual or OpenVMS VAX Version 7.2 Upgrade and Installation Manual for details concerning the optional installation of the DECwin- dows Motif for OpenVMS device support. Enhanced X Window System Display PostScript 49 The X Window System Display PostScript system provided with DECwin- dows Motif extends the native X graphical programming environment for DECwindows users. This system allows users to display text or images on workstations that support the XDPS extension. The DECwindows Mo- tif for OpenVMS layered product must be installed and licensed to use Display PostScript. The X Window System Display PostScript has two components: o Display PostScript server extension, which is provided with the dis- play server in the OpenVMS Alpha and OpenVMS VAX operating systems. A workstation is required to use this server. o Adobe client libraries, which are used by applications to perform PostScript operations, such as rotating and scaling fonts, gener- ating curves, and displaying PostScript documents. The Adobe client libraries are available in the DECwindows Motif for OpenVMS lay- ered product, as well as on third-party platforms, including IBM, Sun, and Silicon Graphics. X Display PostScript adds the following capabilities to the basic X11R6 Window System environment: o DECwindows fonts can be displayed at any size and rotation angle. o PostScript graphics are specified in a user-defined coordinate sys- tem, independent of monitor density. o Color or gray-scale rendition is automatically modified to take ad- vantage of the monitor type through either direct display, color dithering, or half-toning. o PostScript display routines can be downloaded to the server and ex- ecuted on command. o Sophisticated graphics primitives, such as precisely controlled Bezier curves, can be displayed. 50 The Display PostScript system also allows users to view PostScript files with such applications as DECwindows Mail and the CDA Viewer without generating hard copy. The Terms and Conditions for Display PostScript can be found in the DECwindows Motif for OpenVMS Software Product De- scription (SPD 42.19.xx). Monitoring Performance History (MPH) Software Monitoring Performance History (MPH) software is distributed with the OpenVMS Version 7.2 distribution kit and is installed separately. In- stall this software after installing or upgrading the system to Open- VMS Version 7.2. MPH is a tool that collects information (such as error logs, crash dump summaries, configuration, and performance data) from the system on which it is installed. This data is transmitted back to Compaq and is used to set standard requirements for future releases of OpenVMS, such as MeanTime Between Crash (MTBCr) and MeanTime Between System Interrup- tion (MTBSi). The disk size requirement for MPH installation is ap- proximately 1200 blocks. MPH requires 300 blocks of disk space per node after installation. MPH performs three main functions: o Captures updates to the error log o Captures the crash dump profile after the system reboots (if the crash dump is enabled and present) o Captures changes to the hardware configuration of a cluster/node All data is stored in the MPH copy area (MPH$COPY) and is transported to Compaq on a weekly or daily basis. MPH can use one of two transport mechanisms to copy data from the MPH$COPY area: o DSNLink: MPH data is transferred via DSNLink to the CSC. The files are then copied from the CSC to the Compaq processing site via Com- paq's internal network. 51 o Internet: MPH data is mailed via Internet directly to the Compaq processing site. CONFORMANCE TO STANDARDS OpenVMS is based on the following public, national, and international standards. Distributed Computing Environment (DCE) Support The DCE for the OpenVMS product family provides a set of the distributed computing features specified by the Open Software Foundation's (OSF) DCE, as well as tools for application developers. With DCE, the OSF has established a standard set of services and interfaces that facil- itate the creation, use, and maintenance of client/server applications. DCE for OpenVMS serves as the basis for an open computing environment where networks of multivendor systems appear as a single system to the user. Because DCE makes the underlying networks and operating systems transparent, application developers can easily build portable, inter- operable client/server applications. Users can locate and share in- formation safely and easily across the entire enterprise. DCE for Open- VMS supplies system managers with a set of tools to consistently man- age the entire distributed computing environment, while assuring the integrity of the enterprise. The DCE for OpenVMS product family currently consists of the follow- ing products: o DCE Run-time Services for OpenVMS, which is required for all sys- tems participating in the DCE cell. The Run-time Services include DCE client functions as well as DCE administration tools. DCE Run- time Services allow client/server applications to interoperate over DECnet, TCP/IP, and UDP/IP network protocols. o DCE Application Developers' Kit for OpenVMS, which is required for developers of distributed applications but is optional for other users. The DCE Application Developers' Kit provides programmers with an Interface Definition Language (IDL), an easy-to-use, ANSI C-based language for writing remote procedure calls. 52 o DCE Cell Directory Service (CDS), one of which is required for each DCE cell. The DCE CDS is a central repository that contains infor- mation about the location of resources in the DCE cell. It allows access to resources by a single name, regardless of their physi- cal location. o DIGITAL DCE Security Server, one of which is required for each DCE. The DCE Security Server protects resources from illegal access and provides secure communications within and between DCE cells. The right to use the DCE Run-time Services is bundled with the Open- VMS operating system base license. All other DCE products are avail- able as separate layered products. Refer to the DIGITAL Distributed Computing Environment (DCE) for OpenVMS Software Product Description (SPD 43.05.xx) for more detailed information. Support for OSF/Motif and X Window System Standards DECwindows Motif provides support for OSF/Motif, a standards-based graph- ical user interface, and the X Consortium's X Window System, Version 11, Release 6 (X11R6) server. Standards Supported by OpenVMS The OpenVMS operating system is based on the following public, national, and international standards. These standards are developed by the Amer- ican National Standards Institute (ANSI), U.S. Federal Government (re- sponsible for FIPS), Institute of Electrical and Electronics Engineers (IEEE), and the International Organization for Standardization (ISO). The following information may be useful in determining responsiveness to stated conformance requirements as enabled in particular commer- cial and/or government procurement solicitation documents. o ANSI X3.4-1986: American Standard Code for Information Interchange o ANSI X3.22-1973: Recorded Magnetic Tape (800 BPI, NRZI) o ANSI X3.27-1987: File Structure and Labeling of Magnetic Tapes for Information Interchange 53 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) o ANSI X3.40-1983: Unrecorded Magnetic Tape o ANSI X3.41-1974: Code Extension Techniques for Use with 7-bit ASCII o ANSI X3.42-1975: Representation of Numeric Values in Character Strings o ANSI X3.54-1986: Recorded Magnetic Tape (6250 BPI, GCR) o ANSI X3.131-1986 (SCSI I): Small Computer System Interface o ANSI X3.131-1994 (SCSI II): Small Computer System Interface o ANSI/IEEE 802.2-1985: Logical Link Control o ANSI/IEEE 802.3-1985: Carrier Sense Multiple Access with Collision Detection o FIPS 1-2: Code for Information Interchange, Its Representations, Subsets, and Extensions Note: 1-2 includes ANSI X3.4-1977(86)/FIPS 15; ANSI X3.32-1973/FIPS 36; ANSI X3.41-1974/FIPS 35; and FIPS 7. o FIPS 3-1/ANSI X3.22-1973: Recorded Magnetic Tape Information Interchange (800 CPI, NRZI) o FIPS 16-1/ANSI X3.15-1976: Bit Sequencing of the Code for Infor- mation Interchange in Serial-by-Bit Data Transmission Note: FED STD 1010 adopts FIPS 16-1. 54 o FIPS 22-1/ANSI X3.1-1976: Synchronous Signaling Rates Between Data Terminal and Data Communication Equipment Note: FED STD 1013 adopts FIPS 22-1. o FIPS 25/ANSI X3.39-1986: Recorded Magnetic Tape for Information In- terchange (1600 CPI, Phase Encoded) o FIPS 37/ANSI X3.36-1975: Synchronous High-Speed Data Signaling Rates Between Data Terminal Equipment and Data Communication Equipment Note: FED STD 1001 adopts FIPS 37. o FIPS 50/ANSI X3.54-1986: Recorded Magnetic Tape for Information In- terchange, 6250 CPI (246 CPMM), Group Coded Recording o FIPS 79/ANSI X3.27-1987: Magnetic Tape Labels and File Structure for Information Interchange o FIPS 86/ANSI X3.64-1979: Additional Controls for Use with Ameri- can National Standard Code for Information Interchange Note: Other FIPS are not applicable. Note: Information regarding interchangeability of ANSI and FED stan- dards with FIPS is contained in "ADP Telecommunications Standards Index," July 1988, published and maintained by the General Services Administration. o ISO 646: ISO 7-bit Coded Character Set for Information Exchange o ISO 1001: File Structure and Labeling of Magnetic Tapes for Infor- mation Interchange o ISO 1863: Information Processing - 9-track, 12, 7 mm (0.5 in) wide magnetic tape for information interchange recorded at 32 rpmm (800 rpi) o ISO 1864: Information Processing - Unrecorded 12, 7 mm (0.5 in) wide magnetic tape for information interchange - 35 ftpmm (800 ftpi) NRZI, 126 ftpmm (3 200) ftpi phase encoded and 356 ftmm (9 042 ftpi), NRZI o ISO 2022: Code Extension Techniques for Use with ISO 646 55 o ISO 3307: Representations of Time of the Day o ISO 3788: Information Processing - 9-track, 12, 7 mm (0.5 in) wide magnetic tape for information interchange recorded at 63 rpmm (1 600 rpt), phase encoded o ISO 4873: 8-Bit Code for Information Interchange - Structure and Rules for Implementation o ISO 5652: Recorded Magtape (6250) o ISO 6429: Control Functions for Coded Character Sets o ISO 9316: 1989 (SCSI-1) Small Computer System Interface o ISO 9660: Information Processing - Volume and file structure of CD- ROM for information exchange o ISO 10288: 1994 (SCSI-2) Small Computer System Interface INSTALLATION OpenVMS Alpha is distributed as a binary kit on CD-ROM. Procedures for setting up the system disk from media and for preparing the system for day-to-day operations are provided. The procedures use the POLYCENTER Software Installation utility to configure and install the OpenVMS Al- pha Version 7.2 operating system. These procedures are described in the OpenVMS Alpha Version 7.2 Upgrade and Installation Manual. OpenVMS VAX is distributed as binary kits on CD-ROM and tape. Proce- dures for setting up the system disk from a kit and for preparing the system for day-to-day operations are provided. The procedures are de- scribed in the OpenVMS VAX Version 7.2 Upgrade and Installation Man- ual. Computer-specific information is contained in the upgrade and in- stallation supplements for each family of VAX computers. POLYCENTER Software Installation 56 The POLYCENTER Software Installation utility simplifies the instal- lation and management of OpenVMS products. It is used to install, con- figure, reconfigure, and deinstall software products that have been prepared with the utility. In addition, the POLYCENTER utility pro- vides a database to track the installation, reconfiguration, and de- installation of software. For products installed with other instal- lation technologies, the POLYCENTER utility provides a mechanism for adding information about them into the product database. The POLYCEN- TER utility also provides the ability to manage dependencies between products during the installation process. For software providers, the POLYCENTER Software Installation utility simplifies the task of packaging software by providing a simple, declar- ative language for describing material for the installation kit and defining how it is installed. The POLYCENTER utility handles the func- tions, while the developer instructs the utility what to do. This sig- nificantly reduces the complexity and time to develop installation pro- cedures. The language allows the developer to easily specify depen- dencies on other software, manage objects in the execution environ- ment (such as files and directories), and anticipate and resolve con- flict before it occurs. The POLYCENTER utility also significantly sim- plifies the packaging of multiple software products into one logical product suite. For OpenVMS Alpha, you use the POLYCENTER Software Installation util- ity to install the operating system and to install layered products that are compliant with the POLYCENTER utility. For OpenVMS VAX, you use the POLYCENTER Software Installation util- ity to install layered products that are compliant with the POLYCEN- TER utility. VMSINSTAL OpenVMS includes the VMSINSTAL facility to handle the installation of optional Compaq supplied software products that have not been converted to use the POLYCENTER Software Installation utility. OpenVMS VAX also includes the VMSINSTAL facility to automate operating system software updates. 57 Test Package and Diagnostics OpenVMS includes a User Environment Test Package (UETP), which ver- ifies that the OpenVMS operating system is properly installed and ready for use on the customer's systems. You can run diagnostics on individual devices during normal system op- eration. Certain critical components can operate in degraded mode. OpenVMS Alpha DISK SPACE REQUIREMENTS Operating System Disk Space Requirements The disk space requirements for OpenVMS Alpha vary according to which options are installed: 58 ____________________Space__________________________________________ 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) Dump file (op- 28 MB 285 MB tional) Decompressed 15 MB 300 MB Help files (optional) Full DECwindows 90 MB 390 MB Motif V1.2-5 (optional) Safeguard for 50 MB 440 MB upgrading__________________________________________________________ Note: The minimum OpenVMS files listed in the table will allow you to run with minimal functionality. Not all OpenVMS commands and utili- ties will function fully as documented in this minimum configuration. Not all Compaq and other layered products will work in this minimum configuration. The minimum OpenVMS files are for a system configuration where all op- tional features have been declined during the initial installation. For most applications, this is not a realistic OpenVMS environment. 59 The paging, swap, and dump file requirements are the minimum for a sys- tem with 32 MB of main memory. Additional memory in most cases adds to the space needed for these files, as will particular needs of your application. With careful system management it is possible to use the paging file space as a temporary dump file. For an OpenVMS Cluster system disk, paging, swap, and dump files can- not be shared between nodes, so the files must either be duplicated on the system disk or located on some other disk. DECwindows Motif for OpenVMS Alpha Disk Space Requirements To support OpenVMS Alpha and DECwindows Motif for OpenVMS Alpha, Com- paq recommends a system disk of greater than 480 MB. However, you can install a subset of DECwindows Motif. The disk space required for the installation of DECwindows Motif is 90 MB. The permanent amount of space used is 89 MB. An additional 33 MB is needed to install the DECwin- dows X11 Display Server and associated files. (The DECwindows X11 Dis- play Server and associated files are included in the OpenVMS Alpha Ver- sion 7.2 media.) These disk space requirements are in addition to the disk space required for the OpenVMS Alpha Version 7.2 operating sys- tem, as indicated in the OpenVMS Alpha Disk Space Requirements table. Installation of the DECwindows Motif Version 1.2-5 layered product gives customers the option of installing any or all of the following com- ponents: o Run-time support base kit - 25 MB. This section provides support for running DECwindows Motif for OpenVMS Alpha applications on Al- pha compute servers and is a required part of the installation. o New Desktop - 21 MB. This is an optional component that allows use of the New Desktop environment. It includes applications and ap- plication programming interfaces (APIs). o DECwindows desktop - 4 MB. This component is also optional, but you should install either the New Desktop or the DECwindows desktop to create a usable system. The DECwindows desktop is the user inter- face that was included in previous versions of DECwindows Motif and 60 includes the DECwindows Session Manager, FileView, and the Motif Window Manager. o Programming support - 7 MB. This section includes support for the DEC C, DEC C++, DEC Fortran, and Pascal programming languages. If you install a subset of languages, the amount of disk space required will be less. o Example files - approximately 7 MB. o Translated image support - approximately 17 MB. Layered Product Disk Space Requirements In addition to the disk space used directly by Compaq or third-party layered products, there may be additional space used to store infor- mation from those products in OpenVMS help libraries, command tables, object libraries, and elsewhere. The amount of additional disk space required cannot be exactly predicted due to the possibility of recov- ering unused space already existing in those library files. Unusually large modules contributed by layered products can also affect the amount of space required for upgrading to a new version of the OpenVMS Al- pha operating system. OpenVMS VAX DISK SPACE REQUIREMENTS Disk Space Requirements (Block Cluster Size = 3) To support the complete OpenVMS VAX recommends a system disk of greater than 150 MB. When you use a smaller disk, additional tailoring is re- quired before installing some of the OpenVMS VAX options. This does not include the dump file space. Refer to the OpenVMS VAX Version 7.2 Upgrade and Installation Manual for information on tailoring. Operating System Disk Space Requirements The disk space requirements for OpenVMS VAX vary according to which options are installed. 61 ____________________Space__________________________________________ File_Category_______Used______Running_Total________________________ Minimum OpenVMS 32.0 32.0 MB files MB Optional OpenVMS 52.0 84.0 MB files MB DECwindows 14.0 98.0 MB Support MB Paging file 6.0 104.0 MB (after installa- MB tion) Swap file (sug- 1.2 105.2 MB gested) MB Dump file (op- 6.2 111.4 MB tional) MB Decompressed 7.0 118.4 MB Help files MB (optional) Safeguard for 25.0 143.4 MB upgrading MB Variable ad- 3.3 146.7 MB ditional space MB (additional files, IN- DEXF.SYS,_etc.)____________________________________________________ Note: The minimum OpenVMS files listed in the table will allow you to run with minimal functionality. Not all OpenVMS commands and utili- ties will function fully as documented in this minimum configuration. Not all Compaq and other layered products will work in this minimum configuration. The data in the table was created from an installation on a VAXserver 2000 with 6 MB of memory and an RD54 disk. 62 Additional memory adds to the space required for page, swap, and dump files, and the variable additional space increases with larger mem- ory and disk. DECwindows Motif for OpenVMS VAX Disk Space Requirements To support OpenVMS VAX and the DECwindows Motif for OpenVMS VAX lay- ered product, Compaq recommends a system disk of greater than 280 MB. The disk space required for the installation of DECwindows Motif is 36 MB. The permanent amount of space used is 36 MB. An additional 16 MB are needed to install the DECwindows X11 Display Server and asso- ciated files. (The DECwindows X11 Display Server and associated files are included in the OpenVMS VAX Version 7.2 media.) These disk space requirements are in addition to the disk space required for the Open- VMS VAX Version 7.2 operating system, as indicated in the OpenVMS VAX Disk Space Requirements table. Installation of the DECwindows Motif Version 1.2-5 layered product gives customers the option of installing any or all of the following com- ponents: o DECwindows Motif run-time support files base kit - 24 MB. This sec- tion provides support for running DECwindows Motif for OpenVMS VAX applications on VAX compute servers and is a required part of the installation. It includes the DECwindows desktop applications and libraries. o Programming support - 6 MB. This section includes support for the DEC C, DEC C++, DEC Fortran, Pascal, and VAX C programming languages. If a subset of languages is installed, the amount of disk space re- quired is less. o Example files - approximately 6 MB. Note that the individual sizes add up to more than the total because some components are shared by multiple portions of the environment. 63 MEMORY SPACE REQUIREMENTS OpenVMS Alpha Memory Space Requirements The minimum amount of memory required to install, boot, and log in to an OpenVMS Alpha system is 64 MB. To ensure satisfactory performance for particular applications or number of users, additional memory may be required. Refer to specific layered product documentation for their memory requirements. OpenVMS VAX Memory Space Requirements The minimum amount of memory required to install, boot, and log in to an OpenVMS VAX system is 14 MB. To ensure satisfactory performance for particular applications or number of users, additional memory may be required. Refer to specific layered product documentation for their memory requirements. DISTRIBUTION AND BACKUP MEDIA OpenVMS Alpha OpenVMS Alpha is available on CD-ROM only. The OpenVMS Alpha Version 7.2 Binary CD-ROM contains the operating system binaries and selected documentation in both text and Postscript format. The OpenVMS Version 7.2 Online Documentation CD-ROM contains all OpenVMS Documentation in HTML format. Archived manuals and selected layered product manuals re- main in Bookreader format. The OpenVMS Documentation CD-ROM is a dual- formatted system CD-ROM that can be mounted and read on both an Open- VMS system and a Windows 95 or Windows NT PC system. An InfoServer or local drive is required for upgrades and system disk backups. The OpenVMS Alpha operating system is also available as part of the OpenVMS Alpha Software Products Library CD-ROM offering. OpenVMS VAX 64 OpenVMS VAX is available on CD-ROM, TK50, or 9-track 6250 BPI magnetic tape media. The 9-track 6250 BPI magnetic tape media is available only through the OpenVMS VAX media and hardcopy documentation update ser- vice. The OpenVMS VAX Version 7.2 Binary CD-ROM contains the OpenVMS VAX Ver- sion 7.2 save sets, OpenVMS VAX Version 7.2 standalone BACKUP, and se- lected OpenVMS documentation in text and PostScript format. The Open- VMS Version 7.2 Online Documentation CD-ROM contains all OpenVMS Doc- umentation in HTML format. Archived manuals and selected layered prod- uct manuals remain in Bookreader format. The OpenVMS Documentation CD- ROM is a dual-formatted system CD-ROM that can be mounted and read on both an OpenVMS system and a Windows 95 or Windows NT PC system. The TK50 streaming tape contains the OpenVMS VAX Version 7.2 save sets and OpenVMS VAX Version 7.2 standalone BACKUP. The 9-track 6250 BPI magnetic tape contains the OpenVMS VAX Version 7.2 save sets. The OpenVMS VAX operating system is also available as part of the Open- VMS VAX Software Products Library CD-ROM offering. DOCUMENTATION OpenVMS documentation is common for Alpha and VAX. For OpenVMS Ver- sion 7.2, documentation is available in the following formats: Printed Books OpenVMS printed documentation is available in two sets: the OpenVMS Full Documentation Set and the OpenVMS Base Documentation Set. The Full Documentation Set is for users who need extensive explana- tory information on all major OpenVMS resources, complete reference information on system routines and utilities, detailed examples, Open- VMS Cluster guidelines, programming concepts, a master index, and in- formation on the Help Message utility. This set meets the needs of sys- tem managers and of system and application programmers. It includes the Base Documentation Set. 65 The Base Set includes the most commonly used OpenVMS manuals, address- ing the needs of general users and system managers of small standalone systems. Manuals, such as the Release Notes, New Features, and the DCL Dictionary are included in the Base Set. Each book in these sets is also separately orderable. A complete list- ing of all hardcopy manuals and their part numbers is in the Overview of OpenVMS Documentation. Online Books For Version 7.2, online documentation is distributed on the OpenVMS Documentation CD-ROM. Customers will receive the entire documentation set in HTML format. In addition, selected OpenVMS books, archived books, and selected manuals from affiliated products are available in PostScript and text formats. GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of this product may be different from the requirements for the cur- rent version. SOURCE LISTINGS OpenVMS Alpha and VAX Operating System Source Listings are available on CD-ROM. These discs contain source listing files and the Alpha spe- cific debug symbol files that make up the OpenVMS operating system. Compaq provides source listings for key modules of the OpenVMS oper- ating system that are appropriate for end users or application devel- opers. The debug symbol files (DSF) on the OpenVMS Alpha Source List- ings CD-ROM contain information used by the OpenVMS Alpha System-Code Debugger. Certain company confidential source listings and debug sym- bol files, however, are excluded from the CD-ROM. The orderable CD-ROM kit includes the license required to view these files on a standalone system or an OpenVMS Cluster system. If users want to make these files available to another system (possibly at a remote site), they must purchase another kit. 66 ORDERING INFORMATION Alpha Software Licenses QL-MT1A*-6* OpenVMS Alpha Operating System Base License QL-MT1A*-7* OpenVMS Alpha Operating System Base Update License QL-MT1A9-6* OpenVMS Alpha Operating System Symmetric Multipro- cessing (SMP) Base Extension License QL-MT1A9-7* OpenVMS Alpha Operating System Symmetric Multipro- cessing (SMP) Base Extension Update License QL-MT2A*-** OpenVMS Alpha Individual User License (No Longer Available...order the Concurrent Use License) QL-MT2A*-Y* OpenVMS Alpha Individual User Update License QL-MT3A*-B* OpenVMS Alpha Distributed Interactive User License (No Longer Available...order the Concurrent Use License) QL-MT3A*-Y* OpenVMS Alpha Distributed Interactive User Update License QL-MT3A*-3* OpenVMS Concurrent Use License QL-MT3A*-5* OpenVMS Concurrent Use Update License VAX Software Licenses QL-001A*-** VAX VMS Operating System License and Update Li- cense for OpenVMS QL-005A*-6* OpenVMS VAX Operating System Base License QL-005A*-7* OpenVMS VAX Operating System Base Update License QL-005A9-6* OpenVMS VAX Operating System Symmetric Multipro- cessing (SMP) Base Extension License QL-005A9-7* OpenVMS VAX Operating System Symmetric Multipro- cessing (SMP) Base Extension Update License QL-XULA*-** OpenVMS VAX Individual User License (No Longer Available...order the Concurrent Use License) QL-XULA*-Y* OpenVMS VAX Interactive User Update License 67 QL-09SA*-** OpenVMS VAX Distributed Interactive User License (No Longer Available...order the Concurrent Use License) QL-09SA*-Y* OpenVMS VAX Distributed Interactive User Update License QL-MT3A*-3* OpenVMS Concurrent Use License QL-MT3A*-5* OpenVMS Concurrent Use Update License Alpha and VAX CD-ROM Media and Online Documentation QA-MT1AA-H8 OpenVMS Alpha software and online documentation CD-ROM QA-MT1AG-H8 OpenVMS Alpha Version 6.2-1H3 software and on- line documentation CD-ROM. This includes Version 6.2-1H1 and Version 6.2-1H2. (QA-MT1AA-H8.6.2 is required) QA-MT1AD-H8 OpenVMS Alpha Version 7.1-1H2 software and on- line documentation CD-ROM. (QA-MT1AA-H8.7.1 is required) QA-MT1AR-H8 OpenVMS Alpha Version 7.1-2 software and online documentation CD-ROM QA-XULAA-H8 OpenVMS VAX software and online documentation CD-ROM QA-MT3AA-H8 OpenVMS VAX/Alpha software and online documenta- tion CD-ROM VAX Media and Hardcopy Documentation QA-09SAA-H8 OpenVMS VAX Software CD-ROM and Base Documentation Set QA-09SAA-H5 OpenVMS VAX Software TK50 and Base Documentation Set QA-001AA-H8 OpenVMS VAX Software CD-ROM and Full Documentation Set QA-001AA-H5 OpenVMS VAX Software TK50 and Full Documentation Set 68 Hardcopy Documentation Sets QA-09SAA-GZ OpenVMS Base Documentation Set QA-001AA-GZ OpenVMS Full Documentation Set Source Listings Kits QB-MT1AB-E8 OpenVMS Alpha Listings CD-ROM Kit and License QB-001AB-E8 OpenVMS VAX Listings CD-ROM Kit and License OpenVMS Alpha Software Products Library CD-ROM Offerings QA-5FX8A-H8 OpenVMS Alpha Software Layered Products and Op- erating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QA-4KL8A-A8 OpenVMS Alpha Software Products Library (Software Layered Product binaries only-no online documenta- tion) QA-4KM8A-G8 OpenVMS Alpha Online Documentation Library QA-5G98A-H8 OpenVMS Alpha Software Layered Products and Op- erating System Library Package (Software Layered Product binaries and online documentation, com- plete Operating System kit) QA-03XAA-H8 OpenVMS Alpha Software Library Package (Software Layered Product binaries and online documentation) OpenVMS VAX Software Products Library CD-ROM Offerings 69 QA-VWJ8A-A8 OpenVMS VAX Software Layered Products and Oper- ating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QA-5FW8A-H8 OpenVMS VAX Software Layered Products Library (Software Layered Product binaries only, no online documentation) QA-VYR8A-G8 OpenVMS VAX Online Documentation Library QA-YL48A-H8 OpenVMS VAX Software Layered Products and Operat- ing System Library Package (Software Layered Prod- uct binaries and online documentation, complete Operating System kit) QA-5G88A-H8 OpenVMS VAX Software Library Package (Software Layered Product binaries and online documentation) Software Update Distribution Services Provides an automatic distribution of software media and documenta- tion update. Choices include: o Media and Documentaion Distribution o Documentation Distribution o Consolidated Software Engineering Change Order Distribution o Consolidated Distribution of Software Binaries o Consolidated Distribution with Software Binaries and Documentation o Consolidated Online Documentation For additional ordering and pricing information, contact your local Compaq Account Representative. CD-ROM Media and Online Documentation Update Service 70 QT-MT1AA-E8 OpenVMS Alpha software and online documentation CD-ROM QT-XULAA-E8 OpenVMS VAX software and online documentation CD-ROM QT-MT3AA-E8 OpenVMS VAX and Alpha software and online documen- tation CD-ROM Hardcopy Documentation Only Update Service QT-09SAA-KZ OpenVMS Base Documentation Set QT-001AA-KZ OpenVMS Full Documentation Set OpenVMS VAX Media and Hardcopy Documentation Update Service QT-09SA*-E* With Base Documentation Set QT-001A*-E* With Full Documentation Set OpenVMS Source Listings Service QT-MT1AB-Q8 OpenVMS Alpha Source Listings Service QT-001AB-Q8 OpenVMS VAX Source Listings Service * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate Compaq price book. OpenVMS Alpha Software Products Library CD-ROM Service 71 QT-5FX8A-C8 OpenVMS Alpha Software Layered Products and Op- erating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QT-4KL8A-C8 OpenVMS Alpha Software Products Library (Soft- ware Layered Product binaries only, no online documentation) QT-4KM8A-C8 OpenVMS Alpha Online Documentation Library QT-5G98A-C8 OpenVMS Alpha Software Layered Products and Op- erating System Library Package (Software Layered Product binaries and online documentation, com- plete Operating System kit) QT-03XAA-C8 OpenVMS Alpha Software Library Package (Software Layered Product binaries and online documentation) OpenVMS VAX Software Products Library CD-ROM Service QT-VWJ8A-C8 OpenVMS VAX Software Layered Products and Oper- ating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit) QT-5FW8A-C8 OpenVMS VAX Software Layered Product Library (Software Layered Product binaries only, no online documentation) QT-VYR8A-C8 OpenVMS VAX Online Documentation Library QT-YL48A-C8 OpenVMS VAX Software Layered Products and Operat- ing System Library Package (Software Layered Prod- uct binaries and online documentation, complete Operating System kit) QT-5G88A-C8 OpenVMS VAX Software Library Package (Software Layered Product binaries and online documentation) 72 SOFTWARE LICENSING The OpenVMS operating system software is furnished under the licens- ing provisions of Compaq Computer Corporation's Standard Terms and Con- ditions. Software License Information (Alpha Only) The OpenVMS Alpha operating system license includes the license for DECprint Supervisor for OpenVMS, Base. The DECprint Supervisor (DCPS) for OpenVMS has separate documentation, media kit, and service prod- ucts. Refer to the DECprint Supervisor for OpenVMS Software Product Description (SPD 44.15.xx) for more information. The right to use the DCE Run-time Services, Netscape FastTrack and Java is included with the OpenVMS base operating system license. Refer to the DIGITAL Distributed Computing Environment (DCE) Software Product Description (SPD 43.05.xx) for more detailed information on the DCE for OpenVMS product family. The following are separately licensed products: 73 ___________________________________________________________________ DECnet-Plus for SPD 25.03.xx OpenVMS VAX DECnet-Plus for SPD 50.45.xx OpenVMS Alpha DECnet for OpenVMS SPD 48.48.xx VAX and Alpha DIGITAL TCP/IP for SPD 46.46.xx OpenVMS OpenVMS Cluster SPD 29.78.xx Software Volume Shadowing SPD 27.29.xx for OpenVMS RMS Journaling for SPD 27.58.xx OpenVMS Business Recovery SPD 35.05xx Server DECwindows Motif SPD 42.19.xx for OpenVMS DECram for OpenVMS SPD 34.26.xx Compaq Galaxy SPD 70.44.xx Software Architec- ture on OpenVMS Alpha Com for OpenVMS SPD 70.45.xx Alpha______________________________________________________________ Software License Information (VAX Only) The OpenVMS VAX operating system uses one of two different categories of licenses depending on the hardware and software configurations used and currently supported. This information is also provided in the ap- plicable country's Price List. 74 These are the two categories of operating system licenses for Open- VMS VAX: o VAX VMS Licensing o OpenVMS VAX Licensing System Support Services Compaq provides the proper license type with the purchase of the sys- tem. Not all license types are available for every system model. VAX VMS License Information Note: Effective February 6, 1995, the VAX VMS (UPI001) licenses no longer include the rights for the Oracle Rdb Run-Time option for OpenVMS VAX, and do not permit use of Rdb Run-time on prior versions of OpenVMS VAX. Each of the following licenses are for a specified hardware system, which is either the system the license was originally shipped with or the system on which the license was first used: o Operating System Base License (QL-001**-**) o Operating System User License for OpenVMS VAX (QL-001**-**) o Traditional License for OpenVMS VAX (QL-001**-**) There are four types of VAX VMS licenses: All use the LMF Product Name of VAX-VMS. 1. Traditional License (QL-001A*-**) This type of license provides unlimited use to the users on a defined system. VAX VMS traditional licenses are sized to capacity according to system type. 2. Multi-User License (QL-001A*-**) 75 This type of license provides use according to a specified number of concurrent users. This is an activity-based license. The Multi-User License provides the customer with the right to use the operating sys- tem up to the limit of users specified in the license. An operating system user is a person who is logged in to the system and is using the system interactively. This license is only available on limited system models, primarily MicroVAX and VAX 4000 systems. The customer can increase interactive use of VAX systems licensed with the Multi-User License by the addition of OpenVMS User Licenses* (for one or more users). Refer to the section on Ordering Information for further information. 3. VAX VMS Workstation License (QL-001A*-**) This type of license provides use for a single user on a VAX worksta- tion. This license type allows one direct login for the single user and one additional login for system management purposes only. Additional interactive use of VAX workstations licensed with the VAX VMS Workstation License requires the addition of an OpenVMS User Li- cense* (for one or more users). Refer to the section on Ordering In- formation for further information. 4. File and Application Server License (QL-001A*-**) This type of license provides for the noninteractive use of OpenVMS. OpenVMS based VAXserver systems are sold with a File and Application Server License. The intent of an OpenVMS based VAXserver is to pro- vide file, print, application, and compute services to clients who have submitted their requests remotely (for example via network/remote sub- mit/batch jobs, and so forth). This license type also allows one di- rect login for system management purposes only. Additional interactive use of OpenVMS VAXserver systems licensed with the File and Application Server License requires the addition of an OpenVMS User License* (for one or more users). Refer to the section on Ordering Information for further information. 76 These licenses grant the right to use the same version of the oper- ating system software as permitted for the corresponding Operating Sys- tem Base License at the time when the User License is installed. Notes: Not all VAX VMS license types are available for all versions of VMS, OpenVMS, or all VAX models. The OpenVMS VAX Individual Use Licenses are not supported by the VMS or OpenVMS VAX operating system releases prior to Version 5.5. OpenVMS VAX License Information There are five types of OpenVMS VAX licenses: 1. OpenVMS VAX Operating System Base License (QL-005A*-**) LMF Product Name: BASE-VMS-250136 OpenVMS VAX Operating System Base License grants the right to unre- stricted, noninteractive use of the OpenVMS VAX operating system for the execution of remotely submitted requests for batch, print, appli- cation, and computing services, on a designated, single processor. This license authorizes one direct login for system management purposes only. The OpenVMS VAX Base License does not include the license right for the Oracle Rdb Run-Time Option for OpenVMS VAX. The Operating System Base License is a prerequisite for all Interac- tive User Licenses and all SMP Base Extension Licenses. Interactive use of systems licensed with an OpenVMS VAX Operating Sys- tem Base License requires the addition of an OpenVMS User License (for one or more users). Refer to the section on Ordering Information for further information. This license grants the right to use the same version of the operat- ing system software as permitted for the corresponding Operating Sys- tem Base License at the time when the User License is installed. 77 The OpenVMS VAX Operating System Base License also includes the li- cense for DECprint Supervisor for OpenVMS VAX. The DECprint Supervi- sor for OpenVMS VAX has separate documentation, media kits, and ser- vice products. Refer to SPD 44.15.xx for further details. 2. Symmetric Multiprocessing (SMP) Base Extension License (QL-005A9-6*) LMF Product Name: BASE-VMS-250136 SMP Base Extensions extend the Operating System Base License to en- able symmetric multiprocessing capability on a select number of Open- VMS VAX systems supporting SMP. SMP Base Extensions are permanently tied to the Operating System Base License and cannot be separated from the Operating System Base License if an SMP board is removed from the system. SMP Extensions grant the right to use the same version of the oper- 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 The OpenVMS VAX Individual User License provides the right to inter- actively use the operating system by the specified or unlimited num- ber of concurrent users on a designated, single processor. A user is an individual who is logged in to a processor and is interactively us- ing the operating system software by means other than a login. An Open- VMS VAX Operating System Base License or one of the five types of VAX VMS Licenses (QL-001A*-**) is a prerequisite for the OpenVMS User Li- cense. This license grants the right to use the same version of the operat- ing system software as permitted for the corresponding Operating Sys- tem Base License at the time when the User License is installed. 78 The OpenVMS VAX Operating System Base, the SMP Base Extension, and In- teractive User licenses are not supported by the VMS or OpenVMS VAX operating system releases prior to OpenVMS VAX Version 5.5. 4. OpenVMS VAX Distributed Interactive User License (QL-09SA*-**) LMF Product Name: ADL-USER This license grants the right to interactive use of the OpenVMS VAX operating system, provided the appropriate Operating System Base Li- cense or one of the five types of VAX VMS Licenses has been previously installed on a VAX system. The Distributed Interactive User licenses are concurrent- use licenses and are available in any quantity, ex- cept unlimited. Distributed Interactive User licenses are mobile (re- designatable) and may be installed and used on a single OpenVMS VAX processor or shared in a single OpenVMS VAXcluster. A distributed interactive user is defined as an individual who is logged in to an OpenVMS VAX processor or OpenVMS VAXcluster system or is in- teractively using the operating system software by means other than a login. This license grants the right to use the same version of the operat- ing system software as permitted for the corresponding Operating Sys- 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-ADL This license grants the right to interactive use of the OpenVMS op- erating system, provided the appropriate OpenVMS Operating System Base License is installed on an OpenVMS VAX processor, or on an OpenVMS Al- pha processor, or on OpenVMS VAX processors if one of the five types of VAX VMS Licenses has been previously installed on a VAX system. The OpenVMS Concurrent-Use Licenses are available in any quantity desired except unlimited. OpenVMS Concurrent Use Licenses are mobile (redes- ignatable) and may be installed and used on a single OpenVMS VAX or 79 OpenVMS Alpha processor, or shared in a single OpenVMS VAXcluster, a single OpenVMS Cluster, or shared in a mixed OpenVMS Cluster. A user that enables a Concurrent Use License is defined as an indi- vidual who is logged in to an OpenVMS VAX processor, or an OpenVMS Al- pha processor, or an OpenVMS VAXcluster, or an OpenVMS Cluster, or a mixed OpenVMS Cluster and/or is interactively using the OpenVMS op- erating system software by means other than a login. When an OpenVMS VAX SMP System upgrade is performed, the SMP Exten- sion to the OpenVMS Alpha Operating System License permits the use of all existing Distributed Interactive User Licenses on the upgraded sys- tem. The Operating System Base License provides the right to use only the OpenVMS features of the current or prior versions of the OpenVMS op- erating system. This license grants the right to use the same version of the operat- ing system software as permitted for the corresponding Operating Sys- tem Base License at the time when the User License is installed. OpenVMS Alpha License Information There are five types of OpenVMS licenses available on Alpha proces- sors. 1. Operating System Base License (QL-MT1A*-6*) LMF Product Name: OpenVMS-ALPHA This license grants the right to noninteractive use of the remote batch, print, application, and computing services of the OpenVMS Alpha op- erating system on a single processor. This license authorizes one di- rect login for system management purposes only. For dual processor sys- tems (Compaq AlphaServer 8200, 8400 and the AlphaServer GS60 and GS140), the base license for these specific systems grants the right to non- interactive use of the remote batch, print, application, and comput- ing services of the OpenVMS Alpha operating system on a dual proces- sor. 80 The Operating System Base License is a prerequisite for OpenVMS User Licenses and SMP Base Extension Licenses. The Operating System Base License provides the right to use only the OpenVMS features of the current or prior versions of the OpenVMS Op- erating System. 2. Symmetric Multiprocessing (SMP) Base Extension License (QL-MT1A9- 6*) LMF Product Name: OpenVMS-ALPHA SMP Base Extensions extend the Operating System Base License to en- able symmetric multiprocessing capability on those OpenVMS Alpha sys- tems supporting SMP. SMP Base Extensions are permanently tied to the Operating System Base License and may not be separated from the Op- erating System Base License if an SMP board is removed from the sys- tem. SMP Extensions grant the right to use the same version of the oper- ating system software as permitted for the corresponding Operating Sys- tem Base License at the time when the SMP Extension is granted. 3. Individual User License (QL-MT2A*-**) (No Longer Offered) LMF Product Name: OpenVMS-ALPHA-USER This license grants the right to interactive use of the OpenVMS Al- pha operating system, provided the appropriate Operating System Base License has been previously installed on the OpenVMS Alpha system. The Individual User Licenses are available in any quantity desired or as an unlimited user license. Individual User Licenses are redesignatable and may be installed and used on a single OpenVMS Alpha processor only. They may not be shared in a single OpenVMS Cluster environment. A user is defined as an in- dividual who is logged in to an OpenVMS Alpha processor or is inter- actively using the operating system software by means other than a lo- gin. 81 This license grants the right to use the same version of the operat- ing system software as permitted for the corresponding Operating Sys- tem Base License at the time when the User License is installed. 4. OpenVMS Alpha Distributed Interactive User License (QL-MT3A*-**) (No Longer Offered) LMF Product Name: OpenVMS-ALPHA-ADL This license grants the right to interactive use of the OpenVMS Al- pha operating system, provided the appropriate Operating System Base License has been previously installed on an Alpha system. The ADL In- teractive User Licenses are concurrent-use licenses and are available in any quantity desired except unlimited. ADL Interactive User Licenses are redesignatable and may be installed and used on a single OpenVMS Alpha processor, or shared in a single OpenVMS Cluster environment. A distributed interactive user is defined as an individual who is logged in to an OpenVMS Alpha processor or OpenVMS Cluster or is interactively using the operating system software by means other than a login. This license grants the right to use the same version of the operat- ing system software as permitted for the corresponding Operating Sys- 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-ADL This license grants the right to interactive use of the OpenVMS op- erating system, provided the appropriate OpenVMS Operating System Base License in installed on an OpenVMS VAX processor, and/or on an Open- VMS Alpha processor, or on OpenVMS VAX processors if one of the five types of VAX VMS Licenses has been previously installed on a VAX sys- tem. The OpenVMS Concurrent Use licenses are available in any quan- tity desired except unlimited. OpenVMS Concurrent Use Licenses are mo- bile (redesignatable) and may be installed and used on a single Open- VMS VAX or OpenVMS Alpha processor, or shared in a single OpenVMS VAX- cluster, a single OpenVMS Cluster, or shared in a mixed OpenVMS Clus- ter. 82 A user that enables a Concurrent Use License is defined as an indi- vidual who is logged in to an OpenVMS VAX processor, or an OpenVMS Al- pha processor, or an OpenVMS VAXcluster, or an OpenVMS Cluster, or a mixed OpenVMS Cluster and/or is interactively using the OpenVMS op- erating system software by means other than a login. When an Alpha SMP System upgrade is performed, the SMP Base Extension to the OpenVMS Alpha Operating System License permits the use of all existing User Licenses on the upgraded system. This license grants the right to use the same version of the operat- ing system software as permitted for the corresponding Operating Sys- tem Base License at the time when the User License is installed. License Management Facility Support The OpenVMS operating system supports the Compaq License Management Facility (LMF). If an OpenVMS license is not registered and activated using LMF, only a single login is permitted for system management purposes through the system console (OPA0:). Several of the VAX VMS and OpenVMS VAX license types are based on the number of concurrent users, called an activity license. Every prod- uct has the option to define an activity as related to the LMF. Open- VMS Interactive User and ADL Interactive User Licenses define the num- ber of concurrent users who have activity licenses as defined by the LMF. OpenVMS defines activities, sometimes referred to as an OpenVMS user, as follows: o Each remote terminal connection is considered an activity. This is true even if users set host to their local nodes (SET HOST 0). o Each connection from a terminal server is considered an activity. o A multiple-window session on a workstation is considered one ac- tivity, regardless of the number of windows. o A batch job is not considered an activity. 83 o A remote network connection (a connection other than a remote ter- minal connection) is not considered an activity. For more information about Compaq's licensing terms and policies, con- tact your Compaq account representative. SOFTWARE PRODUCT SERVICES A variety of service options are available from Compaq. System Sup- port Services provides integrated hardware and software remedial sup- port, telephone advisory support, and the right-to-use new version of kernel software. For more information, contact your local Compaq ac- count representative. SOFTWARE WARRANTY This software is provided by Compaq with a 90 day conformance warranty in accordance with the Compaq warranty terms applicable to the license purchase. SYSTEMS SUPPORTED Alpha Systems Supported This section lists the Alpha systems that are supported by OpenVMS Al- pha Version 7.2. Refer to the Systems and Options Catalog and the Net- work and Communications Buyers Guide for details concerning Alpha hard- ware configurations and options. Maximum Memory Support OpenVMS supports the following memory for the systems listed: ___________________________________________________________________ Server_______________Memory________________________________________ AlphaServer 400 192 MB 84 ___________________________________________________________________ AlphaStation 400 192 MB AlphaStation 250 192 MB AlphaStation 200 192 MB DEC 4000 Model 2 GB 700 DEC 3000 Model 256 MB 300 DEC 3000 Model 512 MB 700 DEC 3000 Model 1 GB 900 DEC 2000 Model 256 MB 300________________________________________________________________ On all other AlphaServer and AlphaStation systems, OpenVMS supports the maximum physical memory configured. EISA Bus-Based Systems o DEC 2000 Models 300/500 TURBOchannel Bus-Based Systems o DEC 3000 Models 300/300L/300LX/300X o DEC 3000 Models 400/400S o DEC 3000 Models 500/500S/500X o DEC 3000 Models 600/600S o DEC 3000 Models 700/700LX o DEC 3000 Models 800/800S o DEC 3000 Models 900/900LX DSSI Bus-Based Systems o DEC 4000 Model 600 85 o DEC 4000 Model 700 XMI Bus-Based Systems o AlphaServer 8400 5/300, 5/350, 5/440 o DEC 7000 Model 600 o DEC 10000 Model 600 PCI Bus-Based Systems o AlphaServer 300 4/266 o AlphaServer 400 4/166, 4/233 o AlphaServer 800 5/333, 5/400, 5/500 o AlphaServer 1000 4/233, 4/266, 5/300 o AlphaServer 1000A 4/233, 4/266, 5/266, 5/333, 5/400, 5/500 o AlphaServer 1200 5/333 o AlphaServer 2000 4/233, 4/275, 5/250, 5/300 o AlphaServer 2100 4/200, 4/233, 4/266, 4/275, 5/250, 5/300 o AlphaServer 2100A 4/275, 5/250, 5/300 o AlphaServer 2100A LP 4/275, 5/250, 5/300 o AlphaServer 4000 5/300, 5/400 o AlphaServer 4100 5/300, 5/300E, 5/400, 5/466 o AlphaServer 8200 5/300, 5/350, 5/400, 5/440, 5/625 o AlphaServer 8400 5/300, 5/350, 5/400, 5/440, 5/625 o Compaq AlphaServer GS60 o Compaq AlphaServer GS140 o DIGITAL 2100 Server Model A500MP, A600MP o AlphaStation 200 4/100, 4/166, 4/233 o AlphaStation 250 4/266 86 o AlphaStation 255/233, 255/300 o AlphaStation 400 4/166, 4/233, 4/266 o AlphaStation 500/266, 500/333, 500/400, 500/500 o AlphaStation 600 5/266, 5/333 o AlphaStation 600A 5/550 The following are the Compaq semiconductor microprocessor development reference boards supported by OpenVMS Alpha. o Alpha 21064/21064A PCI reference board (EB64+) o Alpha 21164 PCI reference board (EB164) o Alpha PC64 reference board (APC64) Laptop Systems o Tadpole ALPHAbook 1 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-1000 VAX Systems Supported This section of the SPD lists the VAX systems that are supported by OpenVMS VAX Version 7.2. Refer to the Systems and Options Catalog and the Network and Communications Buyers Guide for details concerning VAX hardware configurations and options. Q-bus Based Systems o MicroVAX II 87 o MicroVAX 3300, VAXserver 3300 o MicroVAX 3400, VAXserver 3400 o MicroVAX 3500, VAXserver 3500, VAXstation 3500, VAXstation 3520, VAXstation 3540 o MicroVAX 3600, VAXserver 3600 o MicroVAX 3800, VAXserver 3800 o MicroVAX 3900, VAXserver 3900 o VAX 4000, Models 100, 200, 300, 400, 500, 600 o VAX 4000, Models 50, 100A, 105A, 106A, 108, 500A, 505A, 600A, 700A, 705A, o VAXserver 4000, Models 200, 300, 400, 500, 600 NMI Bus-Based Systems o VAX 8530, VAXserver 8530, VAX 8550, VAXserver 8550 o VAX 8700, VAXserver 8700 o VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840 o VAXserver 8800, VAXserver 8810, VAXserver 8820, VAXserver 8830, VAXserver 8840 XMI Bus-Based Systems o VAX 6000 Series, Models 210, 220, 230, 240 o VAX 6000 Series, Models 310, 320, 330, 340, 350, 360 o VAX 6000 Series, Models 410, 420, 430, 440, 450, 460 o VAX 6000 Series, Models 510, 520, 530, 540, 550, 560 o VAX 6000 Series, Models 610, 620, 630, 640, 650, 660 o VAXserver 6000, Models 210, 220, 310, 320, 410, 420, 510, 520, 610, 620, 630 88 o VAX 8530, VAX 8550, VAXserver 8530, VAXserver 8550 o VAX 8700, VAXserver 8700 o VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840 o VAXserver 8800, VAXserver 8810, VAXserver 8820, VAXserver 8830, VAXserver 8840, VAX 8842, VAX 8974, VAX 8978 o VAX 7000, Models 610, 620, 630, 640, 650, 660, 710, 720, 730, 740, 750, 760, 810, 820, 830, 840, 850, 860 o VAX 10000, Models 610, 620, 630, 640, 650, 660 VAXBI Bus-Based Systems o VAX 8200, VAX 8250, VAXserver 8200, VAXserver 8250 o VAX 8300, VAX 8350, VAXserver 8300, VAXserver 8350 SBI Bus-Based Systems o VAX 8600, VAX 8650, VAXserver 8600, VAXserver 8650 Special System-Specific Internal Bus o MicroVAX 2000 o MicroVAX 3100, Models 10, 10E, 20, 20E, 30, 40, 80, 85, 88, 90, 95, 96, 98 o VAXserver 3100, Models 10, 10E, 20, 20E o VAXstation 4000, Models 60, 90, 95, 96 o VAXstation 4000-VLC o VAX 9000, Models 110, 110VP[5], 210, 210VP, 310, 310VP ____________________ Vector processor (VP) 89 o VAX 9000, Models 320, 320VP, 330, 330VP, 340, 340VP o VAX 9000, Models 410, 410VP, 420, 420VP, 430, 430VP o VAX 9000, Models 440, 440VP System Restrictions The following list describes version-specific restrictions. The DECwin- dows Motif environment is not supported on these systems. MicroVAX I and VAXstation I Systems The final version of OpenVMS VAX that supports these systems is VMS Version 5.1-1. VAX-11/725 VMS V5.1 was the final version to support the VAX-11/725. 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 110 VAXft 310 VAXft 410 VAXft 610 VAXft 810 MicroVAX I VAXstation I 90 OpenVMS VAX Version 7.2 is the final version to support the follow- ing: MicroVAX II VAXstation II/GPX, VAXstation II/QVSS VAXstation 2000, VAXstation 2000/GPX, VAXstation 2000/MFB MicroVAX 2000 Appendix A This appendix describes Compaq Computer Corporation terminals, disks, tapes, controllers, graphics, and network options. Some restrictions for specific devices are listed, if applicable. Compaq reserves the right to change the number and type of devices sup- ported by OpenVMS Alpha, OpenVMS VAX, DECnet for OpenVMS VAX and Al- pha, DECnet-Plus for OpenVMS, DIGITAL TCP/IP Services for OpenVMS, and OpenVMS Cluster software. The minimum hardware requirements for fu- ture versions and updates of these software products may be differ- ent from current hardware requirements. For configuration details about Alpha or VAX hardware, refer to the Systems and Options Catalog and the Network and Communications Buyers Guide. Refer to the following SPDs for detailed product information: DECnet for OpenVMS (SPD 48.48.xx), DECnet-Plus for OpenVMS (SPD 50.45.xx, 25.03.xx), DIGITAL TCP/IP Services for OpenVMS (SPD 46.46.xx), Cluster Software (SPD 29.78.xx), and DIGITAL Open3D for OpenVMS Alpha (SPD 45.08.xx). Terminals and Terminal Line Interfaces To prevent input from overflowing a buffer, terminals use the ASCII control characters DC1 and DC3 for synchronization as defined by the Compaq DEC STD 111, Revision A. VXT windowing terminals support stan- dard ANSI applications and X Windows using the LAT transport proto- col. 91 The following table lists the terminals supported by OpenVMS Alpha: VT200 VT300 VT400 series series series VT500 VXT2000 series series The following table lists the terminals supported by OpenVMS VAX: VT52 VT100 LA series series VT300 VT1000 LQP02 series series VT200 VT500 series series Terminals on Professional 350, Rainbow 100, and DECmate II systems em- ulate VT100 terminals. Only limited support is available for the VT52. The VT131, when run- ning an application, operates in block mode. When interacting with Open- VMS VAX and associated utilities, the VT131 operates only in VT100 (or interactive) mode and not in block mode. Note: The VT1000 is a monochrome windowing terminal that supports stan- dard ANSI applications and the X Window System. The transport proto- col supported is LAT for VMS. The product supports 15-inch and 19-inch monitors. Disks The first column lists the disk drive. The second column describes the device. The third column lists the bus the device is supported on. The fourth column lists the minimum required version of OpenVMS Alpha that supports these devices. The fifth column lists the minimum required version of OpenVMS VAX that supports these devices. (NS stands for Not Supported.) 92 ______________________________________________________________VAX__ Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ EF51R[3] 107 MB solid state DSSI NS 5.5- 2 EF52R[4] 205 MB solid state DSSI NS 5.5- 2 EF53[4] 267 MB solid state DSSI NS 5.5- 2 ESE-20[3] 120 MB solid state SDI NS ESE-52[3] 120 MB solid state SDI 1.0 5.5- 2 ESE-56 600 MB solid state SDI 1.5 5.5- 2 ESE-58 960 MB solid state SDI 1.5 5.5- 2 EZ31 134 MB solid state SCSI 6.2-1H3 NS EZ32 268 MB solid state SCSI 6.2-1H3 NS EZ51R[3] 100 MB solid state SCSI 1.5 5.5- 2 EZ54R 467 MB solid state SCSI 1.5 5.5- 2 EZ58R 855 MB solid state SCSI 1.5 5.5- 2 EZ64 475 MB solid state SCSI 6.2-1H3 5.5- 2 EZ69 950 MB solid state SCSI 6.2-1H3 5.5- 2 DS-EZ41 134 MB solid state SCSI 6.2-1H3 6.2- 1H3 DS-EZ42 268 MB solid state SCSI 6.2-1H3 6.2- 1H3 93 ______________________________________________________________VAX__ Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ DS-EZ705 536 MB solid state SCSI 6.2-1H3 6.2- 1H3 DS-EZ711 1.07 GB solid state SCSI 6.2-1H3 6.2- 1H3 DS-EZ716 1.6 GB solid state SCSI 6.2-1H3 6.2- 1H3 PBXRW-JC 2 GB wide fixed UltraSCSI 6.2-1H3 disk PBXRW-NB 4 GB wide fixed UltraSCSI 6.2-1H3 disk PBXRW-SA 9 GB wide fixed UltraSCSI 6.2-1H3 disk PBXRZ-JC 2 GB narrow fixed SCSI 6.2-1H3 disk PBXRZ-NB 4 GB narrow fixed SCSI 6.2-1H3 disk PBXRZ-SA 9 GB narrow fixed SCSI 6.2-1H3 disk RA60[4] 205 MB removable SDI NS 6.1 RA70 280 MB fixed SDI NS 6.1 RA71 700 MB fixed disk SDI NS 5.4- 2 RA72 1 GB fixed disk SDI 1.0 5.4- 2 RA73 2 GB fixed disk SDI 1.0 5.5- 2 RA80[3] 128 MB fixed disk SDI NS 6.1 RA81 456 MB fixed disk SDI NS 6.1 RA82 622 MB fixed disk SDI NS 6.1 94 ______________________________________________________________VAX__ Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RA90 1.2 GB fixed disk SDI 1.0 6.1 RA92 1.5 GB fixed disk SDI 1.0 6.1 RC25[3] 2 disks each 26 Q-bus NS 6.1 MB (1 fixed and 1 removable) disk drive with shared spindle RD32[3] VAX 42 MB fixed Q-bus NS disk RD51[3] 10 MB fixed disk Q-bus NS 6.1 RD52[3] 31 MB fixed disk Q-bus NS 6.1 RD53[3] 71 MB fixed disk Q-bus NS RD54[4] 159 MB fixed disk Q-bus NS RF30[4] 150 MB fixed disk DSSI NS 6.1 RF31 381 MB fixed disk DSSI 1.5 RF31F[1] 200 MB fixed disk DSSI NS 5.4- 2 RF31T 381 MB fixed disk DSSI 1.5 5.5- 2 RF35 800 MB fixed disk DSSI 1.0 5.5 RF36 1.6 GB fixed disk DSSI 6.1 6.0 RF71 400 MB fixed disk DSSI 1.5 6.1 RF72 1 GB fixed disk DSSI 1.5 5.5- 2 RF74 3.5 GB fixed disk DSSI 6.1 6.0 RK06[3] 14 MB removable UNIBUS NS disk RK07[3] 28 MB removable UNIBUS NS disk 95 ______________________________________________________________VAX__ Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RL02[3] 10 MB removable UNIBUS NS disk RRD40[3] 600 MB read-only Q-bus NS optical disk drive and SCSI RRD42 600 MB read-only SCSI 1.0 5.4- optical disk drive 2 RRD43 680 MB read-only SCSI 6.1 5.5- optical disk drive 2 RRD44 680 MB read-only SCSI 6.1 optical disk drive RRD45 600 MB 4x read-only SCSI 6.1 6.1 optical disk drive RRD46 600 MB 12x read- SCSI 6.2-1H3 5.5- only optical disk 2H4 drive RRD47 600 MB 32x read- SCSI 6.2-1H3 6.2- only optical disk 1H3 drive RRD50[3] 600 MB read-only Q-bus NS optical disk drive RWZ01 594 MB optical SCSI 1.0 removable disk drive RWZ53 2.6 GB magneto SCSI 6.1 6.1 optical disk drive RX02[3] 512 KB diskette UNIBUS NS RX23 1.47 MB diskette SCSI NS RX23L 1.44 MB diskette SCSI 6.2-1H3 NS drive 96 ______________________________________________________________VAX__ Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RX26 2.8 MB diskette I82077 1.5-1H1 drive RX26 2.8 MB diskette SCSI 1.0 5.5 drive RX33[3] 1.2 MB diskette Q-bus NS drive, requires minimum RQDX3 microcode of V3.0 RX50[3] 400 KB diskette Q-bus NS RV20[3] 2 GB Write Once Q-bus, NS Read Many optical UNIBUS, disk drive VAXBI RV64[3] 2 GB Write Once Q-bus, NS Read Many optical UNIBUS, disk subsystem VAXBI RZ1BB 2 GB wide fixed UltraSCSI 6.2-1H3 disk RZ1CB 4 GB wide fixed UltraSCSI 6.2-1H3 disk RZ1DB 9 GB wide fixed UltraSCSI 6.2-1H3 disk RZ22[3] 52 MB fixed disk SCSI NS RZ23[3] 104 MB fixed disk SCSI NS RZ23L[3] 121 MB fixed disk SCSI 1.5 5.4- 1 RZ24[1] 209 MB fixed disk SCSI 1.5 6.1 RZ24L 245 MB fixed disk SCSI 1.0 5.4- 3 RZ25 425 MB fixed disk SCSI 1.0 5.4- 3 97 ______________________________________________________________VAX__ Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RZ25L 500 MB fixed disk SCSI 1.5 5.5- 2 RZ25M 540 MB fixed disk SCSI 6.1 6.1 RZ26 1.05 GB fixed disk SCSI 1.0 5.5- 2 RZ26B 1.05 GB fixed disk SCSI 1.5 6.0 RZ26L 1.0 GB fixed disk SCSI 1.5 5.5- 2 RZ26N 1.0 GB fixed disk SCSI 6.2 5.5- 2H4 RZ28 2.1 GB fixed disk SCSI 1.5 5.5- 2 RZ28B 2.1 GB fixed disk SCSI 1.5 6.0 RZ28D 2.1 GB fixed disk SCSI 6.2 6.2 RZ28L 2 GB narrow fixed SCSI 6.2-1H3 5.5- disk 2H4 RZ28M 2.1 GB fixed disk SCSI 6.2-1H3 5.5- 2H4 RZ29B 4.3 GB fixed disk SCSI 6.1 5.5- 2H4 RZ29L 4 GB narrow fixed SCSI 6.2-1H3 5.5- disk 2H4 RZ35 852 MB fixed disk SCSI NS 5.4- 3 RZ40 9 GB narrow fixed SCSI V6.2-1H3 6.1 disk RZ55 332 MB fixed disk SCSI 1.0 6.1 RZ56 665 MB fixed disk SCSI 1.0 6.1 98 ______________________________________________________________VAX__ Alpha Ver- Disk_Drive_____Description____________Bus_________Version_____sion_ RZ57[2] 1 GB fixed disk SCSI 1.5 5.4- 3 RZ58 1.35 GB fixed disk SCSI 1.0 5.5 RZ73 2 GB fixed disk SCSI 1.0 6.0 RZ2CC 4 GB fixed disk SCSI 7.1-1H2 RZ2DC 9 GB fixed disk SCSI 7.1-1H2 RZ1EF__________18_GB_fixed_disk_______SCSI________7.1-1H2__________ Disk Options Supported by Compaq's Services Enterprise Integration Cen- ter (SEIC) (VAX Only) RF30- 150 MB removable (DSSI) RA[4] disk RF31-RA 381 MB removable (DSSI) disk RF71-RA 400 MB removable (DSSI) disk RF71-RA 1 GB removable (DSSI) disk RWZ01 594 MB optical (SCSI) (V5.4-3) removable disk Tapes ____________________ Specific tailoring is required to use this device as an OpenVMS Al- pha or VAX system disk with the DECwindows Motif environment. Minimum revision firmware is V6000. Device cannot be used as an OpenVMS VAX system disk. Device cannot be used as an OpenVMS VAX system disk with DECwindows Motif environment. TSZ05 is not supported in V7.2. Last version supported was Alpha V6.1. 99 The first column lists the device name. The second column describes the device. The third column lists the bus the device is supported on. The fourth column lists the minimum required version of OpenVMS Al- pha, and the fifth column lists the minimum required version of Open- VMS VAX that supports these devices. (NS stands for Not Supported.) ___________________________________________________________________ VAX Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TA78 1600/6250 BPI, STI 1.0 STI TU78 TA79 STI TU79 STI NS TA81 145 MB tape drive STI 1.0 TA90 1.2 GB tape car- STI 1.0 tridge subsystem. (5-inch 200 MB cartridge) TA90E 1.2 GB tape car- STI NS tridge subsys- tem. Compacts data records automati- cally TA91 High-performance STI NS 5.4-2 tape drive TE16 9-track magnetic M-BUS NS tape drive TF70 290 MB TK70 tape DSSI NS 5.4-2 cartridge drive TF85 2.6 GB streaming DSSI 6.1 5.5-2 tape cartridge drive TF857 18.2 GB tape car- DSSI 6.1 5.5-2 tridge loader 100 _____________________________________________________________VAX___ Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TF86 6.0 GB DLT tape DSSI 6.1 6.1 cartridge TF867 42 GB DLT tape DSSI 6.1 6.1 loader TK50 95 MB, 5 1/4-inch Q-bus NS streaming tape and SCSI cartridge drive TK70 296 MB, 5 1/4-inch Q-bus NS streaming tape cartridge drive TKZ09 5.0 GB, 8mm tape SCSI 1.5 NS drive TKZ9E 1-14 GB, 8mm tape SCSI 6.2-1H3 5.5-2 drive TKZ15 Exabyte 8505 8mm SCSI 6.1 6.1 tape drive TKZ20 2 GB, DC2000 tape SCSI 6.1 6.1 drive TKZ60 200/400 MB, 3480 SCSI 1.0 5.5-2 /3490 tape drive TKZ61 4.4 GB, 3480/3490 SCSI 6.1 5.5-2 tape loader TKZ62 24 GB, 3480/3490 SCSI 6.1 5.5-2 /3490E tape loader TL893 18.4 TB, 4mm, DAT SCSI 6.2-1H3 NS tape drive TL894 3.3 TB, 4mm, DAT SCSI 6.2-1H3 NS tape drive TL896 12.3 TB, 4mm, DAT SCSI 6.2-1H3 NS tape drive 101 _____________________________________________________________VAX___ Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TLZ04 1.2 GB, 4mm, DAT SCSI 1.0 tape drive TLZ06 4 GB, 4mm, DAT tape SCSI 1.0 6.1 drive TLZ07 8 GB, 4mm, DAT tape SCSI 6.1 6.1 drive TLZ08 5.25-inch, 2 GB, SCSI NS 8mm tape drive TLZ09 4 GB, DAT tape SCSI 6.1 5.5- drive 2H4 TLZ10 12/24 GB, DAT tape SCSI 6.2-1H3 5.5-2 drive TLZ6L 4 GB, 3.5-inch, 4mm SCSI 6.1 DAT tape loader TLZ7L 8 GB, 3.5-inch, 4mm SCSI 6.1 6.1 DAT tape loader TLZ9L 32/64 GB, 3.5-inch, SCSI 6.2-1H3 4mm DAT tape loader TL812 1.92 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 TL822 10.4 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 TL826 7.0 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL890 1.12 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL891 700 GB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 102 _____________________________________________________________VAX___ Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ DS-TL893 18.4 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL894 3.3 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL895 6.7 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 DS-TL896 12.3 TB, DLT tape SCSI 6.2-1H3 6.2- library 1H3 TS05 9-track magnetic Q-bus NS tape drive TS11 9-track magnetic UNIBUS NS tape drive TSZ05 1600 bits/in tape SCSI 1.5 drive TSZ07 1600/6250 BPI tape SCSI 1.0 5.4-1 drive TU77 9-track magnetic M-BUS NS tape drive TU78 9-track magnetic M-BUS NS tape drive TU80 9-track magnetic UNIBUS NS tape drive TU81 9-track magnetic UNIBUS NS tape drive TU81-Plus Streaming 9-track Q-bus, NS magnetic tape drive UNIBUS, VAXBI TZ30 95 MB, half-height SCSI 1.0 DLT tape drive 103 _____________________________________________________________VAX___ Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TZ85 2.6 GB DLT tape SCSI 1.0 drive TZ857 18 GB, DLT tape SCSI 1.0 loader TZ86 6.0 GB, DLT tape SCSI 1.5 drive TZ867 42 GB, DLT tape SCSI 1.5 loader TZ87 20 GB, DLT tape SCSI 6.1 6.1 drive TZ875 100 GB, DLT tape SCSI 6.1 6.1 loader TZ877 140 GB, DLT tape SCSI 6.1 6.1 loader TZ88 20/40 GB, DLT tape SCSI 6.2 5.5- drive 2H4 TZ88N 40/80 GB, DLT tape SCSI 6.2 5.5- drive 2H4 TZ89N 35/70 GB, DLT tape SCSI 6.2-1H3 5.5- drive 2H4 TZ885 40/80 GB, DLT tape SCSI 6.2-1H2 5.5- loader 2H4 TZ887 40/80 GB, DLT tape SCSI 6.2-1H2 5.5- loader 2H4 TZK08 2.2 GB 8mm, tape SCSI 6.1 drive TZK10 320/525 MB, QIC SCSI 1.0 tape drive 104 _____________________________________________________________VAX___ Alpha Ver- Tape__________Description____________Bus_________Version_____sion__ TZK11 2.0 GB, QIC tape SCSI 6.1 drive TZS20 25/50 GB, AIT 8mm, SCSI 7.1 ______________tape_drive___________________________________________ Networks Storage Servers HS111 StorageWorks FDDI StorageServer HS121 StorageWorks FDDI StorageServer HS211 StorageWorks FDDI StorageServer HS221 StorageWorks FDDI StorageServer HS241 StorageWorks FDDI StorageServer SWXNA StorageWorks FDDI StorageServer InfoServer An integrated hardware and software system that sits directly on the Ethernet to provide CD-ROM, hard disk, magneto-optical, and tape access to OpenVMS clients in a LAN. It supports up to 14 SCSI devices and can be used for software distribution and ini- tial system load (ISL). For more information, refer to the InfoServer Software Product Description (SPD 33.20.xx.) Enterprise Storage Arrays SWXES StorageWorks Enterprise Storage Array 10000 SWXRA StorageWorks RAID Array 7000, 310, 450 Controllers and Adapters 105 HSC40 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC50 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 4.1.) Refer to SPD 32.96.xx for supported configurations. HSC60 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC65 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC70 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC90 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSC95 Hierarchical storage controller for MSCP served disks and TMSCP served tapes. (HSC software must be at minimum Version 8.1.) Refer to SPD 42.81.xx for supported configurations. HSD05 DSSI to SCSI-2 FSE StorageWorks bus adapter. (Firmware must be at minimum Version X36.) HSD10 DSSI to SCSI-2 FSE StorageWorks bus adapter 106 HSD30 DSSI based StorageWorks controller that supports up to three SCSI-2 FSE ports. (HSD firmware must be at minimum Version V15D.) HSD50 DSSI based StorageWorks controller that supports up to six SCSI-2 FSE ports. (HSD firmware must be at minimum Version V5.0D.) HSJ30 CI based StorageWorks controller that supports up to three SCSI-2 FSE ports. (HSJ firmware must be at minimum Version V15J.) HSJ40 CI based StorageWorks controller that supports up to six SCSI-2 FSE ports. (HSJ firmware must be at minimum Version V15J.) HSJ50 CI based StorageWorks controller that supports up to six SCSI-2 FSE ports. (HSJ firmware must be at minimum Version V5.0J-2 or later.) HSZ20 Fast wide differential SCSI based StorageWorks con- troller that supports up to three SCSI-2 FSE ports. (Alpha only) HSZ40-Bx Fast wide differential SCSI based StorageWorks con- /Cx troller that supports up to six SCSI-2 FSE ports. (HSZ firmware must be at minimum Version V2.5Z.) (Alpha only) HSZ50 Fast wide differential SCSI based StorageWorks con- troller that supports up to six SCSI-2 FSE ports. (HSZ firmware must be at minimum Version V5.0Z) (Alpha only) HSZ70 UltraSCSI wide differential based StorageWorks con- troller that supports up to six UltraSCSI wide sin- gle ended device ports and one host port. (Alpha only) 107 HSZ80 UltraSCSI wide differential based StorageWorks con- troller that supports up to six UltraSCSI wide sin- gle ended device ports and two host ports. (Alpha only) HSZ22 UltraSCSI wide differential based StorageWorks con- troller that supports up to two UltraSCSI wide sin- gle ended device ports and two host ports. (Alpha only) KDM70 Mass-storage controller for XMI systems with eight SDI ports. KFESA Mass-storage controller for EISA systems with one DSSI port. (Alpha only) KFESB Mass-storage controller for EISA systems with one DSSI port. (Alpha only) KFMSB Mass-storage controller for XMI systems with two DSSI ports. (Alpha only) KFPSA Mass-storage controller for PCI systems with one DSSI port. (Alpha only - Version 6.2-1H2 minimum support) KZESC-AA Backplane RAID controller for EISA systems with one SCSI-2 FSE port. (Alpha only) KZESC-BA Backplane RAID controller for EISA systems with three SCSI-2 FSE ports. (Alpha only) KZMSA Mass-storage controller for XMI systems with two SCSI ports. (Limited SCSI-2 support - Alpha only) KZPAA Mass-storage adapter for PCI systems with one SCSI-2 FSE port. (Alpha only) KZPBA-CA Mass-storage adapter for PCI based servers with one UltraSCSI port. Single host support in V6.2-1H3, and V7.1-1H1 and higher. (Alpha only) 108 KZPBA-CB Mass-storage adapter for PCI based servers with two UltraSCSI ports. Single host support in V6.2- 1H3, and multi-host support in V7.1-1H1 and higher. (Alpha only) KZPDA Mass-storage adapter for PCI systems with one SCSI-2 FWSE port. (Alpha only) KZPSA Mass-storage adapter for PCI systems with one SCSI-2 FWD port. (Alpha only - 26 per system maximum with Version 6.2-1H3 and Version 7.1) KZPSC-AA Backplane RAID controller for PCI systems with one SCSI-2 FSE port. (Alpha only) KZPSC-BA Backplane RAID controller for PCI systems with three SCSI-2 FSE ports. (Alpha only) KZPSM 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) KZTSA Mass-storage adapter for TURBOchannel systems with one SCSI-2 FWD port. (Alpha only) PB2HA-SA Mass-storage controller for EISA systems with one SCSI port. (Limited SCSI-2 support. Alpha only on systems with no greater than 1GB of memory.) PMAZB Mass-storage adapter for TURBOchannel systems with two SCSI-2 FSE ports. (Alpha only) PMAZC Mass-storage adapter for TURBOchannel systems with two fast SCSI-2 FSE ports. (Alpha only) Hubs and Switches DWZZH-03 3 port SCSI hub DWZZH-05 5 port SCSI hub 109 Controllers (VAX Only) HSZ10 SCSI based StorageWorks controller that supports up to two SCSI-2 ports. IDC Integrated Disk Controller for VAX-11/725 and VAX-11 /730 systems. IDTC Integral Disk and Tape Controller for VAX 8600 and VAX 8650 systems. LPA11-K Microprocessor controller for laboratory acquisi- tion I/O devices, accommodating up to two AD11-K, one AA11-K, one KW11-K, two AM11-Ks, and five DR11- K devices. One LPA11-K controller is supported per UNIBUS, and a maximum of two are supported per sys- tem. KDA50 Q-bus MSCP disk controller. The KDA50 disk con- troller supports up to four of the following drives: RA60, RA70, RA80, RA81, and RA82. KDB50 VAXBI MSCP disk controller. The KDB50 disk con- troller supports up to four of the following drives: RA60, RA80, RA81, and RA82. KFQSA Q-bus to DSSI bus adapter. This adapter allows up to seven DSSI storage devices to attach to the DSSI bus. (Six DSSI storage devices are allowed in a multi-host configuration.) KLESI Q-bus, UNIBUS, and VAXBI tape controller for the TU81-Plus, RV20, or RC25. KRQ50 Q-bus controller for the RRD40/RRD50 compact disc reader. KZQSA Q-bus to SCSI bus adapter. This adapter allows up to seven SCSI storage devices to attach to the SCSI bus. Supported only for CD-ROM and specific tape devices. 110 KFDDA VAX 4000 model 100 DSSI bus adapter. This adapter allows up to seven DSSI storage devices to attach to the DSSI bus. (Six DSSI storage devices are allowed in a multi-host configuration.) KFDDB VAX 4000 model 500/600/700 DSSI bus adapter. This adapter allows up to seven DSSI storage devices to attach to the DSSI bus. (Six DSSI storage devices are allowed in a multi-host configuration.) LP11 UNIBUS parallel high-speed line printer controller for the LPxx printers. LPV11 Q-bus parallel high-speed line printer controller. RK711 UNIBUS disk controller for RK07 disk drives. RL211 UNIBUS disk controller for the RL02 disk drive. RQDXx Q-bus disk controller for MicroVAX and VAXstation systems. There is an RQDX1, RQDX2, and an RQDX3 controller. The RQDXx disk controller supports as many as four disk units, with each RX50 diskette drive counting as two units. Due to controller lim- itations, the system supports a maximum of four devices; the number of RD/RX devices the system supports depends on the enclosure. The RQDX3 disk controller is required for the RD54 and the RX33 drives. RX211 UNIBUS diskette controller for two RX02 drives. One RX211 diskette controller is supported per system. RUX50 UNIBUS diskette controller for RX50 drives. One RUX50 diskette controller is supported per system. TM03 MASSBUS tape controller for the TE16 and TU77 mag- netic tape drives. TM32 BI bus, 9-track tape controller only with large record support. TM78 MASSBUS tape controller for the TU78 magnetic tape drive. 111 TQK50 Q-bus tape controller for the TK50 cartridge tape drive. TQK70 Q-bus tape controller for the TK70 cartridge tape drive. TS11 UNIBUS tape controller for the TS11 magnetic tape drive. TBK50 BI bus tape controller for the TK50 cartridge tape drive. TBK50 BI bus tape controller for the TK50 cartridge tape drive. TBK70 BI bus tape controller for the TK70 cartridge tape drive. TUK50 UNIBUS tape controller for the TK50 cartridge tape drive. One TUK50 tape controller is supported per system. UDA50 UNIBUS MSCP disk controller. The UDA50 controller must have a minimum microcode version of REV 3. The UDA50 controller supports up to four of the following disk drives: RA60, RA80, RA81, and RA82. Asynchronous Terminal Controllers (Alpha Only) PBXDA- 4-port PCI asynchronous terminal controller AA PBXDA- 8-port PCI asynchronous terminal controller AB Asynchronous Terminal Controllers (VAX Only) CXA16 16-line serial terminal multiplexer (DEC-423), maximum baud rate supported: 38400. (No modem control) (Q-bus) 112 CXB16 16-line serial terminal multiplexer (RS422), maximum baud rate supported: 38400. (No modem control) (Q-bus) CXY08 8-line serial terminal multiplexer (RS232), maximum baud rate supported: 19200. (Full modem control) (Q-bus) DHB32 16-line asynchronous terminal controller for VAXBI, maximum baud rate supported: 19200. (VAXBI) DHF11 32-line asynchronous terminal controller (DEC 423), maximum baud rate supported: 19200. (No modem control) (Q-bus) DHT32 8-line asynchronous terminal controller (DEC 423). (No modem control) (MicroVAX 2000) DHQ11 8-line asynchronous terminal controller (EIA RS-232-C or RS-423-A), maximum baud rate supported: 19200. (Full modem control) (Q-bus) DHU11 16-line asynchronous terminal controller (RS-232-C), maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control) (UNIBUS) DHV11 8-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control) (Q-bus) DMB32 8-line asynchronous terminal controller, maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control) (VAXBI) DMF32 8-line asynchronous terminal controller, maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Full modem control on first two lines) (UNIBUS) DMZ32 24-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Modem support dependent on configuration) (UNIBUS) 113 DZ11 8-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: 9600. (Partial modem control) (UNIBUS) DZ32 8-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: 9600. (Partial modem control) (UNIBUS) DZQ11 4-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Partial modem control) (Q-bus) DZV11 4-line asynchronous terminal controller (EIA RS-232- C or RS-423-A), maximum baud rate supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. (Partial modem control) (Q-bus) Synchronous Controllers-(Alpha Only) The X.25 for OpenVMS Alpha Systems software product contains the syn- chronous device drivers and is required when using synchronous com- munications options. Refer to SPD 47.37xx for more information. SCC Integral Synchronous Communications controller on DEC 3000 systems DSYT1 2-port TurboChannel/Synchronous Communications con- troller DNSES 2-port EISA/Synchronous Communications controller (Ver- sion 6.2-1H2 minimum support.) PBXDI- 2 or 4-port ISA/Synchronous Communications controller Ax PBXDP- 2, 4 or 8-port PCI/Synchronous Communications con- Ax troller Synchronous Controllers (VAX Only) 114 The optional VAX Wide Area Network Device Drivers component of the DECnet- Plus for OpenVMS software product contains the synchronous device drivers and is required when using synchronous communication options. Refer to SPD 25.03.xx for more information. DMB32 Point-to-point synchronous interface. (VAXBI) DMC11 High-speed, local, point-to-point synchronous inter- face; retired device, no longer offered as an option. (UNIBUS) DMF32 Point-to-point or multipoint synchronous interface. (UNIBUS) DMP11 Point-to-point or multipoint synchronous interface; (UNIBUS) retired device, no longer offered as an op- tion. DMR11 Remote, point-to-point, synchronous interface; (UNIBUS) replaces DMC11. DMV11 Point-to-point or multipoint synchronous interface. (Q-bus) DPV11 Synchronous, 1-line, half or full-duplex, point-to- point communication interface supporting DDCMP, HDLC, SDLC, or BISYNC protocols. DSB32 2-line, multiple protocol, synchronous adapter. (VAXBI) DSH32 1-line synchronous (full modem control) and 8-line asynchronous (no modem control) communications con- troller for the MicroVAX 2000. DEC423 devices are sup- ported. Maximum baud rates supported: OpenVMS VAX, 19.2 KbPS (kilobits/second); 9.6 kBPS for MicroVAX 2000, etc. DST32 Synchronous single-line support for DDCMP up to 9.6 KbPS, full duplex for MicroVAX 2000 systems. Concurrent use with the DHT32 is not supported. DSV11 Synchronous, 2-line, half or full-duplex point-to-point communication interface supporting DDCMP (one or two lines up to 64 KbPS). 115 DSF32 DEC WANcontroller 620 - 2-line synchronous communica- tions controller designed specifically for the VAXft 3000 processors, supporting DDCMP. DDCMP is supported at speeds up to 64 KbPS per line for a 2-line opera- tion. Graphics Options For the list of supported graphics options, refer to the DIGITAL Open3D for OpenVMS Alpha Software Product Description (SPD 45.08.xx), and the DECwindows Motif Software Product Description (SPD 42.19.xx) LAN Options (VAX and Alpha) DEFTA A high-performance network adapter that connects TURBOchannel systems to ANSI FDDI local area net- works. DEFZA A high-performance network adapter that connects TURBOchannel systems to ANSI FDDI local area net- works. (DMA receive only.) DEMFA A high-performance network adapter that connects XMI systems to ANSI FDDI local area networks. DEMNA A high-performance network adapter that connects XMI systems to both the Ethernet and IEEE 802.3 local area networks. PMAD A network adapter that connects TURBOchannel systems to both the Ethernet and IEEE 802.3 local area networks. LAN Options (Alpha Only) DEFAA A high-performance network adapter that connects FU- TUREBUS+ systems to ANSI FDDI local area networks. DEFEA A high-performance network adapter that connects EISA systems to ANSI FDDI local area networks. 116 DEFPA A high-performance network adapter that connects PCI systems to ANSI FDDI local area networks. DGLPB ATMworks 350 network adapter that connects PCI systems to ATM local area networks. Version 7.1-1H1 minimum. DGLPA ATMworks 351 network adapter that connects PCI systems to ATM local area networks. Version 7.1-1H1 minimum. DE205 A network adapter that connects ISA/EISA systems to both the Ethernet and IEEE 802.3 local area networks. (Alpha only-Version 6.2-1H2 mini- mum support or Version 6.2 with AXPLAN01_062 Remedial kit.) DE422 A network adapter that connects EISA systems to both the Ethernet and IEEE 802.3 local area networks. DE425 A high-performance network adapter that connects EISA systems to both the Ethernet and IEEE 802.3 local area networks. DE434 A high-performance network adapter that connects PCI systems to both the Ethernet and IEEE 802.3 local area networks. DE435 A network adapter that connects PCI systems to both the Ethernet and IEEE 802.3 local area networks. DE436 A high-performance network adapter that connects QUAD PCI systems to both the Ethernet and IEEE 802.3 local area networks. DE450 A network adapter that connects PCI systems to both the Ethernet and IEEE 802.3 local area networks. DE500- A 10 or 100 Mb performance network adapter that con- AA nects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (Alpha only-Version 6.2-1H3 mini- mum support.) 117 DE500- A 10 or 100 Mb performance network adapter that con- BA nects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (Alpha only-Version 6.2-1H3 mini- mum support.) DE504- A quad channel 10 or 100 Mb performance network adapter BA that connects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (Alpha only-Version 7.1-1H1 minimum support.) DE500- A 10 or 100 Mb performance network adapter that con- FA nects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (Alpha only-Version 7.1-1H1 mini- mum support.) DE500- A 10 or 100 Mb performance network adapter that con- XA nects PCI systems to both the Ethernet and IEEE 802.3 local area networks. (Alpha only-Version 6.2-1H2 mini- mum support.) DW300 A network adapter that connects the EISA bus to a Token Ring local area network. PBXNP- Racore network adapter that connects PCI systems to a DA Token Ring local area network. Version 6.2-1H3 minimum support. PBXNP- TC4048 network adapter that connects PCI systems to a AA Token Ring local area network. Version 6.2-1H3 minimum support. DETRA A network adapter that connects the TURBOchannel bus to a Token Ring local area network. PB2CA- A network adapter that connects AA EISA systems to both the Ethernet and IEEE 802.3 local area networks. LAN Options (VAX Only) DEUNA Ethernet to UNIBUS controller. 118 DELUA Ethernet to UNIBUS controller. The minimum revision level required is F1. DEBNA Ethernet to VAXBI communication controller. DEBNI Ethernet to VAXBI communication controller. DESVA Ethernet controller interface. DEQNA Ethernet controller to Q-bus. The minimum revision level required is K3. Supported for application use only. Not supported beyond Version 5.4-3. DELQA Ethernet controller to Q-bus. This is the replacement for DEQNA. The minimum revision level required is C3. DESQA Ethernet controller to Q-bus for S-BOX configurations. DEFQA FDDI to Q-bus controller KFE52 DSSI/Ethernet adapter for the VAXft 3000. Minimum of two adapters per system providing redundant connection to the Ethernet and the DSSI buses. CI Options (Alpha Only) CIPCA Native CI adapter for PCI AlphaServer systems with one CI port. (Alpha only-Version 6.2-1H2 minimum support) CIXCD-AC Native CI adapter for Alpha XMI systems. (Minimum microcode version REV 1.0 is required.) CI Options (VAX Only) VAXcluster software can support multiple CI adapters per system. Re- fer to the VAXcluster Software Product Description (SPD 29.78.xx) for the supported configurations. CIBCI CI adapter for VAXBI systems. (Minimum microcode ver- sion REV 8.7 is required.) CIBCA- Native CI adapter for VAXBI systems. (Minimum microcode AA version REV 7.5 is required.) 119 CIBCA- Native CI adapter for VAXBI systems. (Minimum microcode BA version REV 5.2 is required.) CIPCI CIXCD- Native CI adapter for VAX 9xxx XMI systems. (Minimum AA microcode version REV 1.0 is required.) CIXCD- Native CI adapter for VAX 6xxx XMI systems. (Minimum AB microcode version REV 1.0 is required.) Miscellaneous PC4XD-AA Parallel/serial port adapter. PMTCE TURBOchannel extender. Miscellaneous (VAX Only) CR11 Card reader. One CR11 card reader is supported per system. (UNIBUS) DRV11- General-purpose DMA interface. (Q-bus) WA DR11-W General-purpose, high-speed DMA interface - one DR11-W interface supported per UNIBUS. DR750 High-performance, general-purpose interface for the VAX-11/750. One DR750 interface is supported per sys- tem. This device cannot be used in conjunction with the CI750. DR780 High-performance, general-purpose interface for the VAX-11/780 and VAX-11/785. One DR780 interface is sup- ported per system. On the VAX 8600 and VAX 8650 as many as four per system are permitted provided that the M8297-YA is used. DWBUA XMI to UNIBUS adapter. DWMBA XMI to BI adapter; also the adapter used to connect the XMI to VAX expander cabinet. DWMVA XMI to VME adapter. 120 FP86-AA Floating point accelerator for the VAX 8600 and VAX 8650 systems. FV64A Vector processing option for the VAX 6000-400. H7112 Memory battery backup for VAX 8600 and VAX 8650 sys- tems. This is required for power-fail/recovery. RH780 MASSBUS controller for the VAX 8600 and VAX 8650 sys- tems. SBI System backplane interconnect and I/O bus for the VAX 8600 and VAX 8650 systems. VS40X 4-plane graphics coprocessor. WS01X VAXstation 3100 SPX graphics option. Abbreviations APMP Adaptive Partitioned Multi-Processing ATA-3 AT Attachment, Version 3 COM Component Object Model DLT Digital Linear Tape DSSI DIGITAL Storage Systems Interconnect EISA Extended Industry Standard Interconnect FDDI Fiber Distributed Data Interface FSE Fast Single Ended (SCSI) FWD Fast Wide Differential (SCSI) IDE Integrated Device (or Drive) Electronics IEEE Institute for Electrical and Electronics Engineers I80277 Intel 82077 PC Compatible Floppy Interface MSCP Mass Storage Control Protocol NCS National Character Set PCI Peripheral Component Interconnect QIC Quarter Inch Cartridge RAID Redundant Array of Independent Disks RMC Remote Procedure Call 121 RMS Record Management Services SDI Standard Drive Interface SMP Symmetic Multiprocessing STI Standard Tape Interface TFF Terminal Fallback Facility TIE Translated Image Environment TMSCP Tape Mass Storage Control Protocol VLM Very Large Memory VVIEF VAX Vector Instruction Emulation Facility XMI Extended Memory Interconnect This information is valid at time of release. Please contact your lo- cal Compaq office for the most up-to-date information. © 1999 Compaq Computer Corporation. All rights reserved. [R] Adobe, Display PostScript, and PostScript are registered trademarks of Adobe Systems, Inc. [R] IBM is a registered trademark of International Business Ma- chines Corporation. [R] IEEE and POSIX are registered trademarks of the Institute of Electrical and Electronics Engineers, Inc. [R] JAVA is a registered trademark of Sun Microsystems, Inc. [R] Microsoft and Windows NT are registered trademarks of Mi- crosoft Corporation. [R] Motif, OSF/Motif, OSF and OSF/1 are registered trademarks of Open Software Foundation, Inc. [R] Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation. [TM] Oracle Rdb is a trademark of Oracle Corporation. [R] Sun is a registered trademark of Sun Microsystems, Inc. 122 [R] UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. [TM] X/Open is a trademark of X/Open Company Limited. [TM] X Window System is a trademark of the Massachusetts Institute of Technology. [TM] The Compaq logo, Alpha, AlphaServer, AlphaStation, Bookreader, CI, Compaq, DEC, DEC Ada, DECamds, DEC BASIC, DEC Fortran, DECdtm, DECmate, DECnet, DECprint, DECthreads, DECscheduler, DECtp, DELNA, DEUNA, DIGITAL, DHB32, EDT, HSC, HSC40, HSC50, HSC60, HSC70, HSC90, InfoServer, KDM, LA, LAT, LQP02, Manage- WORKS, MicroVAX, MSCP, OpenVMS, OpenVMS Cluster, PATHWORKS, POLYCENTER, Q-bus, RA, RC, RC25, RK, RL, RM, RP, RRD42, RRD50, RX, RX02, RX211, RX23, RX33, RX50, RZ, SDI, STI, Stor- ageWorks, StorageServer, TA, TE, TE16, TK, TMSCP, TM, TS, TS05, TS11, TU,TURBOchannel, UNIBUS, VAX, VAX Ada, VAX BASIC, VAX BLISS-32, VAX C, VAX COBOL, VAX DIBOL, VAX FORTRAN, VAXBI, VAXft, VAX MACRO, VAX Pascal, VAX 8600, VAX 11/750, VAX 11/780, VAXserver, VAXstation, VMS, VMScluster, VT52, VT100, VT300, VT400, VT500, VT1000, VXT2000, and XUI are trademarks of Compaq Computer Corporation. 123