                          Software           Product            Description   M           ___________________________________________________________________   P           PRODUCT NAME:  OpenVMS Operating System for VAX and Alpha, Version 6.2           SPD's 25.01.42  N           Note: This Software Product Description describes OpenVMS Operating N           System Software for the Alpha and VAX computer family. Except where N           explicitly noted the features described in this SPD apply equally toO           Alpha and VAX systems. OpenVMS Alpha and OpenVMS VAX operating system N           licenses and part numbers are architecture specific; please refer toK           the Ordering Information section of this SPD for further details.              DESCRIPTION   N           OpenVMS is a general-purpose multiuser operating system that runs inN           both production and development environments. OpenVMS Alpha supportsO           Digital Equipment Corporation's Alpha series computers, while OpenVMS N           VAX supports VAX, MicroVAX, VAXstation, and VAXserver series comput-M           ers. OpenVMS software supports industry standards, facilitating ap- N           plication portability and interoperability. OpenVMS provides symmet-M           ric multiprocessing (SMP) support for multiprocessing Alpha and VAX            systems.  M           The OpenVMS operating system can be tuned to perform well in a wide N           variety of applications, including compute-intensive, I/O-intensive,M           client/server, real-time, and combinations of those and other envi- N           ronments. Actual performance depends on the type of computer, avail-O           able physical memory, and the number and type of disk and tape drives            on the           system.   L           OpenVMS has well-integrated networking, distributed computing and N           client/server, multiprocessing, and windowing capabilities. OpenVMS L           contains extensive features that promote ease-of-use, improve the H           productivity of programmers, and facilitate system management.    M                                         DIGITAL                      May 1995            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M           OpenVMS is an open software environment that supports key standards O           such as OSF/Motif, POSIX, XPG4, and the OSF Distributed Computing En- N           vironment (DCE). The right to use POSIX for OpenVMS and the DCE Run-N           time Services for OpenVMS is bundled with the OpenVMS operating sys-O           tem base license. DECwindows Motif is available exclusively as a sep-             arate layered product.  P           OpenVMS Alpha Version 6.2 and OpenVMS VAX V6.2 are functional releasesM           of the OpenVMS operating system for Digital's Alpha and VAX systems I           respectively. These releases include a number of new features,  K           enhancements and expanded hardware support. Refer to the OpenVMS  6           Version 6.2 New Features Manual for details.  O           OpenVMS Alpha compilers and applications take advantage of 64 bits by O           using 64-bit data types. Consult the Software Product Descriptions of M           OpenVMS Alpha compilers for further details. Note that application  ?           virtual address space is a 32-bit implementation for  /           compatibility and migration purposes.              User Environment  M           Users can access OpenVMS software by using the English-like DIGITAL K           Command Language (DCL), the command language for OpenVMS that is  P           supplied with the system. DCL commands take the form of a command nameN           followed by parameters and qualifiers. DCL commands provide informa-M           tion about the system, initiate system utilities, and initiate user P           programs. OpenVMS prompts users to enter required DCL parameters, mak-'           ing it easy for novice users.   O           Users can enter DCL commands at a terminal or include them in command N           procedures. Command procedures can be run interactively or submitted2           to a batch queue for deferred execution.  O           Information on DCL and OpenVMS utilities is available through the on- P           line OpenVMS Help system. Online Help includes summary operational in-7           formation on all aspects of system operation.   M           A number of tools and utilities are integrated into the OpenVMS op- '           erating system. They include:     ,                                            2           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42               Text Processing   M           The Extensible Versatile Editor (EVE), one of several text editors  M           supplied by Digital, is the default editor for OpenVMS. EVE allows  N           users to insert, change, and delete text quickly. Written in the DECJ           Text Processing Utility language (DECTPU), EVE is a full-screen O           editor that allows users to scroll through text on a terminal screen. N           EVE provides an EDT-style keypad, allowing EDT users to move to EVE I           easily. EDT is also supported on OpenVMS Alpha Version 6.2 and  "           OpenVMS VAX Version 6.2.             Mail Utility  M           The Mail utility allows users to send messages to any other user on N           the system. Multinode operation is available if DECnet or DECnet/OSI           is installed andH           licensed on each participating node on the configured network.  #           Command-Level Programming   O           Command-level programming allows users to create special files called N           command procedures that contain a series of DCL commands. When usersM           execute a command procedure, the system consecutively processes the P           commands in the command procedure. Users can also use special DCL com-P           mands to assign symbolic names, evaluate numerical and logical expres-O           sions, accept parameters, communicate interactively with the user in- N           voking the command procedure, perform conditional (IF-THEN-ELSE) and>           branching (GOTO) logic, and handle error conditions.  $           User Environment Tailoring  O           Users can customize the computing environment with user login command O           procedures, shorthand commands, binding of commands to function keys, )           and command recall and editing.   *           Terminal Fallback Facility (TFF)          ,                                            3           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           This facility allows Digital 7-bit terminals to input and output theN           DEC Multinational character set (MCS). Specific tables allow conver-M           sion for a number of different 7-bit National Replacement Character N           sets, such as French, German, Spanish, and Swedish, to MCS. TFF alsoM           allows character composition on terminals that do not have the com-            pose key.   .           National Character Set (NCS) Utility  P         This utility allows users to define non-ASCII string collating sequencesN           and to define conversion functions. Conversion functions use conver-P           sion algorithms to change an input string; for example, to change low-N           ercase characters to uppercase. NCS also allows RMS indexed files to?           be collated using user-specified collating sequences.   )           Program Development Environment   P           OpenVMS includes a comprehensive set of tools for developing programs,P           including run-time libraries (RTLs), a linker, a librarian, and a sym-P           bolic debugger. The assembly-level VAX MACRO language is supplied withM           OpenVMS VAX. Tools available to the OpenVMS programmer include the             following:  /           Language and Run-Time Library Support   P           OpenVMS includes several run-time libraries (RTLs) that provide stringN           manipulation, parallel processing support, I/O routines, I/O conver-N           sion, terminal-independent screen handling, date and time formattingN           routines, highly accurate mathematical functions, signaling and con-?           dition handling, and other general-purpose functions.   O           On OpenVMS VAX, these routines can be called from programs written in N           such languages as VAX MACRO, VAX Ada, VAX BASIC, VAX BLISS-32 Imple-O           mentation Language, VAX C, DEC C, DEC C++, VAX COBOL, VAX DIBOL, VAX  6           FORTRAN, VAX Pascal, VAX PL/I, and VAX SCAN.          ,                                            4           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           On OpenVMS Alpha, these routines can be called from programs writtenP           in such languages as MACRO-64, DEC Ada, DEC BASIC, DEC C, DEC C++, DEC7           COBOL, DEC Fortran, DEC Pascal, and DEC PL/1.   M          Also included in OpenVMS Alpha are language-support libraries. While L          each language is different, all provide support for sequential fileP          I/O and most support direct and indexed file I/O as well. Language RTLsL          also provide support for I/O formatting, error handling, and in DECL          Fortran, the ability to read unformatted files containing data from          other vendors.   N           Run-Time Libraries are provided to support Translated Images createdM           from user mode images built on OpenVMS VAX Version 4.0 through Ver- L           sion 5.5-2. Depending on the method used to create the VAX image, K           these Run-Time Libraries may be useful for images built on later  H           versions of OpenVMS VAX, which do not use features which were 4           developed since OpenVMS VAX Version 5.5-2.  O           Translated Images Run-Time Libraries are used to support a few archi- O           tectural features (such as VAX D-float and H-float), which differ be- O           tween VAX and Alpha systems, and support programs converted to run on M           Alpha systems before native Alpha compilers were available for par- (           ticular programming languages.  N           Many Digital languages (including those listed previously) adhere toN           the common calling standard, meaning that routines written in any ofN           these languages can directly call routines written in any other lan-M           guage. Development of applications using multiple languages is sim- "           ple and straightforward.  L           All user accessible routines in the Run-Time Libraries follow the N           OpenVMS Alpha or OpenVMS VAX calling standard and condition-handlingF           conventions, and most are contained within shareable images.  N           At a lower level, programs can call system services directly for se-P           curity, event flag, asynchronous system trap, logical name, record andP           file I/O, process control, timer, time conversion, condition handling,M           lock management, and memory management services. Again, system ser- J           vices use the OpenVMS VAX or OpenVMS Alpha calling standard and )           condition-handling conventions.   ,                                            5           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           OpenVMS supports execution of user mode images created on earlier ver-Q           sions of OpenVMS. Recompiling and relinking typically are not required.   #           Macro-32 Compiler - Alpha   N           The Macro-32 compiler for OpenVMS Alpha is supplied with OpenVMS Al-.           pha software for migration purposes.             DECthreads  O           OpenVMS includes a user-mode multithreading capability referred to as M           DECthreads. DECthreads provides an implementation of draft 4 of the P           proposed POSIX 1003.4a standard and is Digital's implementation of theP           Distributed Computing Environment (DCE) Threads as defined by the OpenP           Software Foundation. DECthreads is a library of run-time routines thatO           allows the user to create multiple threads of execution within a sin- M           gle address space. Multithreading capability allows computation ac- N           tivity to be overlapped with I/O activity. Synchronization elements,N           such as mutexes and condition variables, are provided to help ensureP           that shared resources are accessed correctly. DECthreads also providesO           multiple scheduling policies for scheduling and prioritizing threads. O           DECthreads is supported by the OpenVMS debugger, to aid in the debug- -           ging of multithreaded applications.              Librarian Utility   O           The Librarian utility permits storage of object modules, image files, O           macros, Help text, or any general record-oriented information in cen- O           tral, easily accessible files. Object module and image file libraries N           are searched by the linker when the linker finds a reference it can-K           not resolve in one of its input files. Alpha macro libraries are  O           searched by the Macro-32 compiler and Macro-64 assembler when either  N           finds a macro name that is not defined in the input file. VAX macro M           libraries are searched by the assembler when the assembler finds a  6           macro that is not defined in the input file.             Debugger        ,                                            6           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           The OpenVMS Debugger allows users to trace program execution as wellM           as display and modify register contents using the same symbols that )           are present in the source code.   $           Alpha System-Code Debugger  M          The OpenVMS Alpha System-Code Debugger is a kernel code debugger. It M          allows a system code developer to trace the execution of nonpageable P          system code at any IPL (Interrupt Priority Level). Based on the OpenVMSM          Alpha Debugger, the system-code debugger uses the same interface and ,          a majority of the same command set.             System Dump Analyzer  N           In the event of a system failure, OpenVMS will write the contents ofN           memory to a pre-allocated dump file. This dump file can later be an-N           alyzed using the System Dump Analyzer (SDA). System dumps can eitherN           be full memory dumps, where all memory is written, or selective mem-M           ory dumps, where only memory in use at the time of the system fail- M           ure is written. Full memory dumps require a dump file big enough to P           hold all memory. Selective memory dumps will write as much of the mem-M           ory in use at the time of the system failure that will fit into the A           dump file, which can therefore be much smaller in size.   O           OpenVMS for Alpha supports selective dumps on systems configured with O           any supported amount of memory. Full dumps are only supported on sys- 4           tems configured with up to 4 GB of memory.             RMS File Utilities  M           RMS file utilities allow users to analyze the internal structure of M           an RMS file and to determine the most appropriate set of parameters P           for an RMS file. These utilities can also be used to create, load, andN           reclaim space in an RMS file. Refer to the Operating System Environ-M           ment section of this Software Product Description for more informa-            tion on RMS.  !          File Differences Utility   P          This utility compares the contents of two files and lists those records          that do not match.   ,                                            7           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    .           Translated Image Environment - Alpha  O           OpenVMS Alpha provides an array of services to allow the operation of N           programs that have undergone binary translation from OpenVMS VAX im-O           ages. These programs can perform virtually all user-mode functions on_P           OpenVMS Alpha, and can operate in combination with other programs (im-M           ages) that have been translated from OpenVMS VAX or have been built0M           using native compilers on OpenVMS Alpha. Without requiring special rM           source code, the Translated Image Environment resolves differences  L           between the VAX and Alpha architectures, including floating-point M           registers, condition codes, exception handling, ASTs, and so forth.i  N           The Translated Image Environment included with OpenVMS Alpha is suf-M           ficient to run such images that have been translated elsewhere. ThetM           DECmigrate for OpenVMS AXP layered product can be used to translateiN           user mode OpenVMS VAX images. For additional information on the pre-O           cise characteristics of programs suitable for binary translation, re-hI           fer to the DECmigrate for OpenVMS AXP Systems Software Product A%           Description (SPD 39.44.xx).   '           System Management Environmentd  M           OpenVMS provides a variety of features to aid the system manager inaO           configuring and maintaining an optimal system. Features available for 3           the system manager include the following:   )           OpenVMS Management Station V1.0   O           The new OpenVMS Management Station enables user account management onuP           one or more VMScluster systems from a single Windows-based PC. It pro-P           vides the ability to perform management tasks across multiple systems,M           making it possible to easily modify many accounts in a single oper-pO           ation. It provides a comprehensive interface to the user account man-nP           agement features of AUTHORIZE, DISKQUOTA, and some DCL directory main-P           tenance commands, transparently enabling the steps of adding a UAF en-M           try, granting rights identifiers, creating a directory, disk quota,y          ,                                            8           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           and mail profile. In addition, the Management Station also allows cre-M           ation of network proxy records and supports storing personal infor- N           mation such as phone number, location, and site-specific identifica-           tion.n  N           The Management Station supports the account management operations ofN           account creation, modification, and deletion as well as renaming ac-3           counts and displaying account attributes.a  M           The following are V1.0 restrictions with regard to managing OpenVMSn           systems:  M           o  Managing OpenVMS Cluster members as individual nodes is not sup-lM              ported. OpenVMS Cluster systems are treated as indivisible enti-fN              ties; an operation cannot be performed on particular cluster mem-              bers.  O           o  OpenVMS Clusters with multiple user authorization files (UAFs) arel              not supported.a  P           o  The PCs currently support DECnet Phase IV only. However, due to theP              built-in backward compatability between DECnet/OSI and DECnet PhaseM              IV this does not impose any restrictions on operations between arO              PC client and the server, as long as the node addresses are withintP             the Phase IV address space (maximum 63 areas with maximum 1023 nodes              per area).a  M          The Management Station is a client/server application based on PATH- P          WORKS ManageWORKS. The PC client requires Microsoft[R] Windows[TM] V3.1P          (or Microsoft Windows for Workgroups V3.11) and PATHWORKS V5.0A or V5.1M          for DOS and Windows client which includes ManageWORKS. The PATHWORKSrM          server is not required. The Management Station server component mustoL          be installed on OpenVMS VAX Version 6.1 or higher, or OpenVMS AlphaO          Version 6.2 or higher. The Management Station software is included un-v'           der the OpenVMS base license.e              InfoServer Tape Backup  O           With Version 6.1 of the OpenVMS operating system, system managers can N           now back up and restore the system disk to tapes connected to an In-           foServer system.  ,                                            9 l  n      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    (           Batch and Print Queuing System  N           OpenVMS provides an extensive batch and print capability that allowsM           the creation of queues and the setup of spooled devices in order toeP           process noninteractive workloads in parallel with timesharing or real-           time jobs.  M           The OpenVMS batch and print operations support two types of queues:tM           generic queues and execution queues. A generic queue is an interme-UO           diate queue that holds a job until an appropriate execution queue be-xM           comes available to initiate the job. An execution queue is a queue EN           through which the job (either print or batch) is actually processed            or executed.  P          The system queues batch jobs for execution. The system manager can reg-M          ulate the number of queues and the number of streams per queue (that D          is, the number of batch jobs in the queue that can execute           concurrently).   N         Both generic and execution batch queues can have different attributes,L         such as the maximum CPU time permitted, working set size, and prior-M         ity. Facilities are provided for starting and stopping queues and foroP         starting and stopping jobs in a queue. Because multiple execution queuesO           can be associated with a generic queue, OpenVMS VAX enables load bal-aO           ancing across available CPUs in a VMScluster system, increasing over-r            all system throughput.  O           Print queues, both generic and execution, together with queue manage- O           ment facilities, provide versatile print capabilities, including sup-r7           port of ANSI and PostScript[R] file printing.              Accounting Utility  O           For accounting purposes, OpenVMS keeps records of system resource us- M           age. These statistics include processor and memory utilization, I/OsO           counts, print symbiont line counts, image activation counts, and pro-iN           cess termination records. The OpenVMS Accounting utility allows var-7           ious reports to be generated using this data.e              Audit Analysis Utility    -                                            10u n  u      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M          For security auditing purposes, OpenVMS selectively records critical N          security-relevant events in the system security audit log file. TheseN          records contain the date and time the event occurred, the identity ofL          the associated user process, and information specific to each eventN          type. This information is intended to aid the system manager in main-M          taining system security and to deter possible intruders. The OpenVMS P          Audit Analysis utility allows various reports to be generated from this          data.  )           Autoconfigure/AUTOGEN Utilities   L          OpenVMS provides utilities to automatically configure the availableL          devices into the system tables and to set system operational param-O          eters based on the detected peripheral and memory configuration. ThereiP          is no need for a traditional "system generation" process when the hard->          ware configuration is expanded or otherwise modified.  N          The OpenVMS Alpha AUTOGEN command procedure automatically sets a num-M          ber of system parameters by detecting devices installed in a config-nL          uration. A feedback option can be used to generate a report of rec-F          ommended parameter settings based on previous usage patterns.            Backup Utilityp  K         The Backup utility provides full volume and incremental file backupcO         for file-structured, mounted volumes and volume sets. Individual files,oK         selected directory structures, or all files on a volume set can be cG         backed up and restored. Files can be selected by various dates AK         (creation, modification, etc.). Files can be backed up to magnetic AN         tape, magnetic disk, or WORM (Write Once Read Many) optical disk. The N         Backup utility can be used to restore a save set or list the contents          of a save set.  P           Backup Manager for OpenVMS provides a screen-oriented interface to theM           Backup utility which assists users in performing routine Backup op-            erations.M          -                                            11  O  ,      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    5           Backup Manager is menu-driven and provides:a  O           o  Access to Backup's save, restore, and list operations without hav-p4              ing to understand Backup command syntax  L          o  The ability to create, modify, recall and delete Backup Manager 8            "templates" describing Backup save operations  O           Backup Manager will work on all supported OpenVMS configurations withoO           a video terminal. It uses the Screen Management (SMG) RTL routines to M           provide a window- like user interface. The software does not assumeeO           any particular privilege on the part of its user beyond access to the 0           files and devices being operated upon.  )           Standalone Backup Utility - VAXs  M           Standalone BACKUP provides a mechanicsm for system managers to backrN           up and restore system disks. Standalone BACKUP can also be used dur-C           ing the installation of the OpenVMS VAX operating system.   (           Analyze Disk Structure Utility  O           The Analyze Disk Structure utility compares the structure information N           on a disk volume with the contents of the disk, prints the structureN           information, and permits changes to that information. It also can beP          used to repair errors that are detected in the file structure of disks.             Monitor Utilityi  M           The Monitor utility permits the system manager to monitor differentpM           classes of systemwide performance data, including process activity,.N           I/O activity, memory management activity, vector processing activityN           (VAX), and two phase commit transaction activity at specified inter-N           vals. The data may be displayed as it is gathered or saved in a file           for later use.  +           License Management Facility (LMF)-  P           The License Management Facility (LMF) allows the system manager to en-M           able software licenses and to determine which software products are,(           licensed on an OpenVMS system.  -                                            12  e  s      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    ,           System Management Utility (SYSMAN)  L         SYSMAN allows the system manager to define a system management envi-N         ronment so that operations performed from the local OpenVMS system canL         be executed on all other OpenVMS systems in the defined environment.L         The environment may include OpenVMS Alpha and VAX systems configuredP         in a VMScluster, or multiple systems networked via DECnet or DECnet/OSI.             Operations  M         OpenVMS enables varying levels of privilege to be assigned to differ-uK         ent operators. In addition, system-generated messages can be routedtK         to different terminals based on their interest to the console oper-XM         ators, tape librarians, security administrators, and system managers. K         Operators can use the OpenVMS Help Message utility to obtain onlinee$         error messages descriptions.           Security  N         Digital achieved a C2 security rating for OpenVMS VAX 6.0 and a B1 se-M         curity rating for SEVMS VAX V6.0 in 1993 and is currently participat- L         ing in a Ratings Maintenance Phase (RAMP) with the National ComputerL         Security Center (NCSC) to obtain C2 and B1 security ratings for Ver-P         sion 6.1 of OpenVMS and SEVMS, respectively, on both Alpha and VAX plat-K         forms. Digital expects to achieve C2 and B1 ratings for OpenVMS VAXiK         V6.1 and SEVMS VAX V6.1 in mid 1995. Digital completed the NCSC Fu-iO         ture Change Review Board (FCRB) process, presenting its plans for RAMP-rN         ing to Version 6.1 of OpenVMS and SEVMS on the Alpha platform. The en-P         tire RAMP process should be completed in the Fall of 1995. Digital plansK         to continue to maintain C2 and B1 ratings on future versions of thed,         OpenVMS and SEVMS operating systems.  P         The ratings represent NCSC validation of the design of OpenVMS and SEVMSP         operating systems against DoD 5200.28-STD "Department of Defense TrustedM         Computer System Evaluation Criteria". To obtain an in-depth, 230-pageeN         report on the security of these systems, contact the NCSC at (410)859-N         4452 and ask for a copy of the "Final Evaluation Report Digital Equip-K         ment Corporation OpenVMS VAX and SEVMS VAX Version 6.0," CSC-EPL-93 $         /002, C-Evaluation No.14-94.-                                            13d p         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O           For OpenVMS V6.2 security API's for Intrusion detection, Proxy accessaN           and Impersonation services have been added on both the Alpha and VAXN           platform to allow for better security in your Client/Server applica-           tions.  K         OpenVMS provides a rich set of mechanisms to control user access toaM         system-controlled data structures and devices that store information.OL         OpenVMS employs a Reference Monitor concept that enforces the systemO         security policy by mediating all access attempts between subjects, suchnO         as user processes, and security-relevant system objects, such as files.eK         OpenVMS also provides a system security audit log file that option-eM         ally records the results of all object access attempts. The audit logaK         can also be used to capture information regarding a wide variety ofe'         other security-relevant events.l  K         User account information is maintained by the system manager in thelL         system user authorization file (SYSUAF). When creating user accountsM         with the Authorize utility, the system manager assigns the privilegeshM         and quotas associated with each user account. The system manager alsohP         assigns a user name, password, and unique user identification code (UIC)K         to each account. Optionally, additional identifiers can be assigned K         to each account, permitting users to belong to multiple overlappinghM         groups or projects. Account use may be limited by time of day, day ofiL         week, and type of access (such as local, remote, network, or batch).  M         To log in and gain access to the system, the user must supply a validfK         user name and password. The password is encoded and does not appear M         on terminal displays. Users can change their password voluntarily, orcK         the system manager can selectively enforce how frequently passwordsoK         change, along with minimum password length, or optional use of ran-s"         domly generated passwords.  P         Additionally, OpenVMS provides a password dictionary filter that screensK         password choices for common words, and a user password history fil- K         ter that prevents users from reusing passwords that they have used  L         within the last year. In addition to these built-in filters, a site L         can design and install its own filter to screen passwords against a &         site-specific password policy.      -                                            14     n      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M           The system password hash algorithm can also be replaced with a pri-iM           vate algorithm for those sites that have contractual obligations todM           use specific public or private password encryption algorithms. ThishC           feature can be enabled on a per-user, per-password basis.e  M         Login security includes break-in detection, which allows terminals tohP         be disabled when password guessing is detected, and a secure login path,K         which can be used to thwart Trojan horse attacks against local ter-EL         minals. Additionally, a system password may be associated with dial-M         in terminal lines to prevent the display of any operating system spe- N         cific identification that might yield clues to possible attack method-N         ologies. When a user logs in, the system also displays a message stat-K         ing when the last login for the account occurred and the number of  B         failed attempts to log in since the last successful login.  L         Every security-relevant system object is labeled with the UIC of itsL         owner (normally the user who created the object) along with a simpleM         protection mask. The owner UIC consists of two fields, the user fieldeO         and a group field. System objects also have associated with them a pro- K         tection mask that allows read, write, execute, and delete access tonL         be selectively granted to the object's owner, group, privileged sys-N         tem users, to all other users. In addition, system objects can be pro-K         tected with access control lists to allow access to be selectively HD         granted or denied to a list of individual users, groups, or K         identifiers. Access control lists can also be used to audit access a,         attempts to critical system objects.  J           OpenVMS applies full protection to the following system objects:  $           o  Capabilities (VAX only)  '           o  Common Event Flag Clusters2             o  Devices             o  Files  "           o  Group Global Sections              o  Logical Name Tables             o  Batch/Print Queuesn  -                                            15, c  o      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42               o  Resource Domainso             o  Security Classesr  #           o  System Global Sectionse             o  Volumes (ODS-2)  L         In addition to the protection mechanisms previously described, Open-K         VMS provides a security attribute defaulting mechanism, in the form M         of security template profiles. These template profiles are referenced K         whenever a new object is created and provide a means of associating P         default security information with each system object class except files.L         Protection information for files is inherited from the previous ver-L         sion of an existing file, the parent directory, or the creating pro-!         cess' default protection.r  O         Data scavenge protection can be enabled selectively in the form of fileEK         high-water marking and erase on delete attributes. These attributesnO         ensure that file contents cannot be read after a file has been deleted.sL         The system manager can also enforce file erasure on a per-volume ba-N         sis. The disk erasure pattern can also be replaced with a private pat-L         tern for those sites that have contractual obligations to use a spe-         cific pattern.  O           Security auditing is provided to allow for the selective recording ofPN           security related events. This auditing information can be separatelyO           directed to security operator terminals (alarms) or to the system se-eM           curity audit log file (audits). Each audit record contains the daterM           and time of the event, the identity of the associated user process,w<           and additional information specific to each event.  F           OpenVMS provides security auditing for the following events:             o  Login and logoutm  1           o  Login failures and break-in attemptsy  O           o  Object creation, access, deaccess, and deletion, selectable by use J              of privilege, type of access, and on individual objects (ACL)  +           o  Authorization database changes   -                                            16            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           o  Network logical link connections and terminations for DECnet-VAX,?              DECnet/OSI, DECwindows, IPC, and SYSMAN (VAX only)   -           o  Use of identifiers as privileges   C           o  Installed image additions, deletions, and replacementsu  (           o  Volume mounts and dismounts  B           o  Use of the Network Control Program utility (VAX only)  7           o  Use or failed use of individual privilegesi  >           o  Use of individual process control system services  %           o  System parameter changesa  3           o  System time changes and recalibrationsT  P           Note: No system can provide complete security and Digital cannot guar-P           antee system security. However, Digital continually strives to enhanceO           the security capabilities of its products. Customers are strongly ad- A           vised to follow industry recognized security practices.t  &           Operating System Environment  "           Processes and Scheduling  M         The basic unit of execution in OpenVMS is the process. A process con- K         sists of individual address space and registers known as "context,"cN         and code called an "executable image." The context identifies the pro-O         cess and describes its current state. Executable images consist of sys-cJ         tem programs and user programs that have been compiled and linked.  L         The maximum number of concurrent processes is 8192 per OpenVMS Alpha         or OpenVMS VAX system.  M         Processes receive processor time to execute their images based on thegN         priority of the process. Thirty-Two priorities are recognized on Open-O         VMS VAX and sixty-four priorities are recognized on OpenVMS Alpha: pri-rL         orities 0 to 15 are for time-sharing processes and applications that  -                                            17  e  t      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O         are not time critical (four is the typical default for timesharing pro- M         cesses), and priorities 16 to 32 on VAX and 16 to 63 on Alpha are forn         real-time processes.  L         Each time an event such as an I/O interrupt occurs, the system firstO         services the event and then passes control to the highest priority pro-yK         cess ready to execute. The system automatically adjusts the priori-oK         ties of processes whose base priority is in the range of 0 to 15 tooN         favor I/O-bound and interactive processes, but the system will not ad-M         just the priority of a process in the range of 16 to 31 for VAX or 16e         to 63 for Alpha.  L         Real-time processes can be assigned higher priorities to ensure thatM         they receive processor time whenever they are ready to execute. Real-VO         time processes are scheduled preemptively; that is, if a real-time pro-iL         cess is ready to execute, it is given the processor immediately, un-L         less a real-time process with a higher priority is ready to execute.  N         OpenVMS uses paging and swapping mechanisms to provide sufficient vir-M         tual memory for multiple concurrently executing processes. Also, pag-AL         ing and swapping is provided for processes whose memory requirementsM         exceed available physical memory. The maximum working set size is 512a'         MB of memory for Alpha and VAX.t  K         Programmers can exercise control over memory management from within.M         an image. An image executing in a real-time process, for example, can =         inhibit paging or swapping of critical code and data.t  K         Peripheral devices can be managed by the system or allocated by in-cP         dividual processes. At least one disk must be a system disk. Other disksM         can be designated as data disks for the general use of all users log-iO         ging in to the system or for a specific group of users. The system con-n=         trols interactive terminals and one or more printers.   *         Extended Physical Addressing - VAX  N         With OpenVMS VAX Version 6.0, physical address space was extended fromL         30 bits to 32 bits. The OpenVMS VAX operating system can provide 3.5K         GB of physical memory, and .5 GB of I/O and adapter space. This ca- L         pability enables large applications and workloads to access the huge  -                                            18            J         OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O         amounts of physical memory that they require. The following table listscJ         the VAX processors that support this extended physical addressing:  M           ___________________________________________________________________ %                            Accessible #                            PhysicalwM           System___________Memory______I/O_and_Adapter_Space_________________n  ,           VAX 6000         1.25 GB     .5 GB           model 600   ,           VAX 7000         3.5 GB      .5 GB           series  ,           VAX 10000        3.5 GB      .5 GBM           series_____________________________________________________________s  !           Vector Processing - VAXd  K         A single data item, having one value, is known as a scalar value. AiO         group of related scalar values, or elements, all of the same data type,h         is known as a vector.   K         An extension to the VAX architecture defines an optional design forcN         integrated vector processing that has been adopted by several VAX sys-M         tems. The VAX vector architecture includes sixteen 64-bit vector reg-rL         isters (V0 through V15), each containing 64 elements; vector controlK         registers; vector function units; and a set of vector instructions.lN         VAX vector instructions transfer data between the vector registers andO         memory, perform integer and floating-point arithmetic, and execute pro-i!         cessor control functions.y  O         A more detailed description of the VAX vector architecture, vector reg-mM         isters, and vector instructions appears in the VAX MACRO and Instruc-i"         tion Set Reference Manual.  P         The OpenVMS VAX operating system provides fully shared, multiprogrammingP         support for VAX vector processing systems. By default, OpenVMS VAX loadsN         vector support code when initializing vector-present systems, but doesM         not load it when initializing vector-absent systems. A system manager   -                                            19r n  y      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           can control this behavior by using the system parameter VECTOR_PROC,8           as described in the OpenVMS VAX documentation.  N           The presence of vector support code in a system has little effect onM           processes running in a scalar-only system, or scalar processes run-nM           ning in a vector-present system. If many processes must compete si-dM           multaneously for vector processor resources in a system, the systemaM           manager can maintain good performance by adjusting system resources K           and process quotas as indicated in the OpenVMS VAX documentation.i  P           The OpenVMS VAX operating system makes the services of the vector pro-P           cessor available to system users by means of a software abstract knownN           as a capability. A system manager can restrict the use of the vectorN           processor to users holding a particular identifier by associating anL           access control list (ACL) entry with the CAPABILITY object VECTOR.  M           The VAX Vector Instruction Emulation Facility (VVIEF) is a standardtP           feature of the OpenVMS VAX operating system that allows vectorized ap-M           plications to be written and debugged in a VAX system in which vec-AN           tor processors are not available. VVIEF emulates the VAX vector pro-N           cessing environment, including the nonprivileged VAX vector instruc-O           tions and the OpenVMS VAX vector system services, as described by thelM           OpenVMS VAX documentation. Use of VVIEF is restricted to user mode a           code.              DECdtm Servicesd  N           The DECdtm services embedded in the OpenVMS operating system supportN           fully distributed databases using a "two-phase commit" protocol. TheM           DECdtm services provide the technology and features for distributedeM           processing, ensuring both transaction and database integrity acrossfN           multiple Digital resource managers. Updates to distributed databasesN           occur as a single "all or nothing" unit of work, regardless of whereN           the data physically resides. This ensures consistency of distributed           data.   O         DECdtm services allow applications to define "global transactions" that M         may include calls to any of a number of Digital data management prod- P         ucts. Regardless of the mix of data management products used, the global      -                                            20' o  n      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O           transaction will either commit or abort. OpenVMS is unique in provid- P           ing transaction processing functionality as base operating system ser-           vices.  "           DECdtm features include:  K         o  Embedded OpenVMS system services support the DECtp architecture, L            providing features and the technology for distributed transaction            processing.  M         o  Allows multiple disjoint resources to be updated atomically. These-N            resources can be either physically disjointed (for example, on dif-K            ferent CPUs) or logically disjointed (for example, in different l&            databases on the same CPU).  O         o  Encourages robust application development. Applications can be writ- M            ten to ensure that data is never in an inconsistent state, even inn(            the event of system failures.  O         o  Can be called using any Digital TP monitor or database product. ThisiN            is useful for applications using several Digital database products.  $           Interprocess Communication  O           OpenVMS provides a number of facilities for applications that consistr,           of multiple cooperating processes.  L         o  Mailboxes are virtual devices that allow processes to communicate             with queued messages.  M         o  Shared memory sections on a single processor or a symmetrical mul- O            tiprocessing (SMP) system permit multiple processes to access sharedt&            address space concurrently.  =         o  Common event flags provide simple synchronization.   M         o  The lock manager provides a more comprehensive enqueue/dequeue fa-nL            cility with multilevel locks, values, and ASTs (asynchronous sys-            tem traps).  #           Symmetric Multiprocessingo  -                                            21  g         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N         OpenVMS provides symmetric multiprocessing (SMP) support for Alpha andK         VAX multiprocessor systems. SMP is a form of tightly coupled multi-eM         processing in which all processors perform operations simultaneously. P         The processors can perform operations in all OpenVMS access modes (user,+         supervisor, executive, and kernel).   O         OpenVMS SMP configurations consist of multiple central processing units K         executing code from a single shared memory address space. Users andpO         processes share a single copy of OpenVMS Alpha or OpenVMS VAX. SMP alsoaM         provides simultaneous shared access to common data in global sectionseO         to all processors. OpenVMS SMP dynamically selects the CPU where a pro-n0         cess will run based on process priority.  L         SMP support is an integral part of OpenVMS and is provided transpar-K         ently to the user. Because an SMP system is a single system entity,sO         it is configured into a network and VMScluster configurations as a sin-o         gle node.e           Networking Facilities   K         OpenVMS provides device drivers for all Digital LAN adapters listed N         in the LAN Options section of Appendix A of this SPD. Application pro-N         grammers can use the QIO system service to communicate with other sys-M         tems connected via the LAN using either Ethernet or IEEE 802.3 packet M         format. Simultaneous use of Digital Ethernet and IEEE 802.3 protocols 1         are supported on any Digital LAN adapter.   M         DECnet/OSI offers task-to-task communications, file management, down-fL         line system and task loading, network command terminals, and networkK         resource sharing capabilities as defined in the Digital Network Ar- O         chitecture (DNA) Phase V protocols. DECnet/OSI provides the newest DEC-aK         net features such as Extended Addressing, and downline load perfor-eN         mance enhancements. DECnet/OSI integrates DECnet and OSI protocols andK         now provides a linkage to TCP/IP using RFC 1006 and RFC 1006+. DEC-bN         net and OSI applications can now be run over DECnet (NSP), OSI (CLNS),!         and/or TCP/IP transports.a          -                                            22r A  s      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O           DECnet for OpenVMS Alpha and DECnet-VAX offer the networking capabil-eN           ities as defined in the Digital Network Architecture (DNA) Phase IV.O           For more information, refer to the DECnet Software description in thea2           ASSOCIATED PRODUCTS section of this SPD.  "           Terminal Server Products  P           Digital's terminal server products can be used for terminal server ac-M           cess to OpenVMS. When used in a VMScluster system environment, ter-oO           minal servers automatically distribute users at login time across the *           available Alpha and VAX systems.  L           OpenVMS can also establish a connection to other devices (such as 6           printers) attached to such terminal servers.             Reliabilityr  O           The system handles hardware errors as transparently as possible whilenP           maintaining data integrity and providing sufficient information to di-P           agnose the cause of the error. The system limits the effects of an er-M           ror by first determining if the error is fatal. If the error occursnM           in system context, then the current OpenVMS system is shut down. IfcN           the error is not fatal, then recovery actions pertinent to the error>           are executed and the current operation is continued.  N           In all cases, information relevant to the error is collected and putO           in the error log file for later analysis. Hardware errors include thee           following categories:.  M           o  Processor errors. These include processor soft errors, processorfG              hard errors, processor machine checks, and adapter errors.i  N           o  Memory errors. These can be unrecoverable (hard) errors or recov-M              erable (soft) errors. The system examines memory at startup timenM              and does not use any pages found to be bad. During system opera-oN              tion, the system transparently corrects all single-bit memory er-O              rors for those systems with Error Correction Code (ECC) memory. On P              OpenVMS VAX, an unrecoverable error causes the memory page on whichM              the error occurred to be added to the bad page list. If the page N              has not been modified, system operation continues with a new copy              of the page.n  -                                            23s           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O         o  Correctable memory errors. A primary cause of these correctable mem- K            ory errors is Alpha particle radiation. On some processors, when.O            correctable memory errors occur, the memory controller corrects onlyfM            the data returned to the CPU or I/O controller. The actual data in K            memory is left with the error intact. Subsequent read operationsiL            will cause correction cycles to occur and in most cases an inter-N            rupt to report the error. On many of these processors, OpenVMS mon-N            itors the occurrence of correctable memory errors and in almost allL            cases is able to remove the error condition by rewriting the dataK            in memory. Rewriting the data causes the data to be corrected in L            the memory location. On OpenVMS VAX, if the cause of the error isN            not transient, and the error condition persists, the operating sys-N            tem will attempt to move the data from the existing page which con-K            tains the error to a new page. The original page is then retired             from use.  !           Other failures include:c  O           o  Operating system errors (system-detected inconsistencies or archi-s/              tectural errors in system context)              o  User errors             o  I/O errorsl  M         The system logs all processor errors, all operating system errors de-rM         tected through internal consistency checks, all double-bit memory er-sL         rors (and a summary of corrected single-bit memory errors), and most         I/O errors.p  P         If the system is shut down because of an unrecoverable hardware or soft-K         ware error, a dump of physical memory is written. The dump includesoL         the contents of the processor registers. The OpenVMS System Dump An->         alyzer utility is provided for analyzing memory dumps.             Power Failures - VAX          -                                            24            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N         If power fails, the system shuts down automatically. When power is re-K         stored, the system restarts automatically and resumes processing at K         the point of interruption if the system has a time-of-day clock and P         a memory battery backup unit, if the contents of memory are still valid,?         and if the system is set to permit automatic rebooting.r  K         The system restarts devices and communications lines. All I/O oper-hH         ations in progress, including magnetic tape I/O operations, are N         restarted. On request, programs can be notified of power restoration. M         An optional battery-operated hardware clock resets the date and time  G         of day when the system restarts. If the system does not have a aN         battery backup unit, or if the memory contents are not valid on power K         restoration, the system will reboot automatically if the system is h*         set to permit automatic rebooting.  O         If, for any reason, after a power failure the system disk does not come-L         back on line within a specific time after the CPU regains power, the         system shuts down.           Input/Output  K         The QIO system service provides a direct interface to the operatingxL         system's I/O routines. These services are available from within mostN         OpenVMS programming languages and can be used to perform low-level I/OK         operations efficiently with a minimal amount of system overhead for #         time-critical applications.l  L         Device drivers execute I/O instructions to transfer data to and fromM         a device and to communicate directly with an I/O device. Each type oftL         I/O device requires its own driver. Digital supplies drivers for allO         devices supported by the OpenVMS operating system and provides QIO sys-yL         tem service routines to access the special device-dependent features+         available in many of these devices.t  O         OpenVMS supports a variety of disk and tape peripheral devices, as welltL         as terminals, networks, and mailboxes (virtual devices for interpro-:         cess communication), and more general I/O devices.        -                                            25i           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    L         On OpenVMS Alpha, users can write device drivers for I/O devices forO         which the operating system does not provide drivers. OpenVMS Alpha Ver-1N         sion 6.2 supports the Step 2 device driver interface, which allows de-L         vice drivers to be written in DEC C and MACRO-32. OpenVMS Alpha doc-M         umentation is available that describes how to write OpenVMS Alpha de-sL         vice drivers and how to convert existing OpenVMS VAX and OpenVMS Al-M         pha Step 1 device drivers to OpenVMS Alpha Step 2 device drivers. The O         DEC C compiler for OpenVMS Alpha is an optional orderable layered prod-_         uct.  L         On OpenVMS VAX, users can write their own device drivers in MACRO-32P         for I/O devices for which the operating system does not provide drivers.M         The OpenVMS VAX Device Support Manual and the OpenVMS VAX Device Sup-_L         port Reference Manual in the OpenVMS Full Documentation Set describe$         how to write device drivers.  (         Record Management Services (RMS)  L         Record Management Services (RMS) is a set of I/O services that helpsN         application programs to process and manage files and records. AlthoughK         it is primarily intended to provide a comprehensive software inter-bN         face to mass storage devices, RMS also supports device-independent ac-$         cess to unit-record devices.  L         RMS supports sequential, relative, and indexed file organizations inO         fixed-length and variable-length record formats. RMS also supports byter8         stream formats for sequential file organization.  K         RMS record access modes provide access to records in four ways: se- K         quentially, directly by key value, directly by relative record num-tM         ber, and directly by record file address. RMS also supports block I/OnM         operations for various performance-critical applications that may re- A         quire user-defined file organizations and record formats.t  O         RMS promotes safe and efficient file sharing by providing multiple fileSM         access modes, automatic record locking where applicable, and optionals-         buffer sharing by multiple processes.n    -                                            26            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M           RMS utilities aid file creation and record maintenance. These util-yN           ities convert files from one organization and format to another, re-P           structure indexed files for storage and access efficiency, and reclaimO           data structures within indexed files. The utilities also generate ap-r           propriate reports.  P         For systems that have DECnet-VAX, DECnet for OpenVMS Alpha or DECnet/OSIK         installed, RMS provides a subset of file and record management ser-aN         vices to remote network nodes. Network remote file operations are gen-,         erally transparent to user programs.  M         DCL commands such as EDIT, CREATE, COPY, TYPE, and PRINT allow manip- L         ulation of RMS files and records within RMS files at the DCL command         level.           Virtual I/O Cachel  O         OpenVMS provides a standalone or clusterwide, file-oriented disk cache.eM         Applications automatically benefit from the advantages of the virtuallP         I/O cache without any special coding. The virtual I/O cache file-cachingL         algorithm is dynamically chosen based on the type of clusterwide ac-K         cess currently in progress. Virtual I/O caching reduces current andtM         potential I/O bottlenecks within OpenVMS systems. It reduces the num-oM         ber of I/Os to the disk subsystem, thereby reducing a systemwide bot-i         tleneck.           Disk and Tape Volumest  L         Disk volumes can be organized into volume sets. Volume sets can con-N         tain a mix of disk device types and can be extended by adding volumes.K         Within a volume set, files of any organization type can span multi-mO         ple volumes. Files can be allocated to the set as a whole (the default)iN         or to specific volumes within the set. Optionally, portions of indexedK         files can be allocated to specific areas of a single disk volume org,         to specific volumes in a volume set.  K         Disk quotas can be placed to control the amount of space individualtK         users can allocate. Quota assignment is made by user identificationrM         code and can be controlled for each individual volume set in the sys- O         tem (or for each individual volume if the volume is not part of a set).   -                                            27n d  a      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           Disk structure information can be cached in memory to reduce the I/OO           overhead required for file management services. Although not requiredXM           to do so, users can preallocate space and control automatic alloca-tP           tion. For example, a file can be extended by a given number of blocks,N           contiguously or noncontiguously, for optimal file system performance           in specific cases.  K         The system applies software validity checks and checksums to criti-pN         cal disk structure information. If a disk is improperly dismounted be-K         cause of user error or system failure, the system automatically re-cR         builds the disk's structure information the next time the disk is mounted.O         The system detects bad blocks dynamically and prevents their reuse onceeL         the files to which the blocks were allocated are deleted. On DIGITALM         Storage Architecture (DSA) disks, the disk controller dynamically de-a4         tects and replaces bad blocks automatically.  L          The system provides eight levels of named directories and subdirec-O         tories whose contents are alphabetically ordered. Device and file spec- K         ifications follow Digital conventions. Logical names can be used toiM         abbreviate the specifications and to make application programs deviceoK         and file name independent. A logical name can be assigned to an en-aO         tire specification, to a portion of a specification, or to another log-s         ical name.  N         OpenVMS supports multivolume magnetic tape files with transparent vol-K         ume switching. Access positioning is done either by file name or by          relative file position.   5         Monitoring Performance History Software (MPH)i  M         Monitoring performance History (MPH) software is distributed with the K         OpenVMS distribution kit and is installed seperately. MPH is a tool N         which collects error logs, crash dump summaries and configuration dataO         from the system on which it is installed. This data is transmitted back O         to Digital and is used to set standard requirements for future releasesmM         of OpenVMS, such as Mean Time Between Crash (MTBCr) and Mean Time Be-sM         tween System Interruption (MTBSi). The disk space requirement for MPHlM         installation is approximately 1200 blocks. MPH requires 300 blocks ofr      -                                            28     u      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M           disk space per node after installation. For more information pleaseo9           refer to the OpenVMS Version 6.2 Release Notes.g               ASSOCIATED PRODUCTS             OpenVMS Cluster Software  L         OpenVMS Cluster Software is available for Alpha and VAX systems as aK         separately licensed System Integrated Product. It provides a highlylO         integrated OpenVMS computing environment distributed over multiple sys-eL         tems. This environment is called a VMScluster system and may contain         up to 96 nodes.i  K         VMScluster systems communicate using any combination of the follow-aL         ing interconnects; CI, DSSI, FDDI, Ethernet, and SCSI. Additionally,M         when configured with suitable FDDI bridges, VMScluster configurationsL>         may utilize DS3/T3 and ATM networking infrastructures.  L         Applications running on one or more nodes in a VMScluster system ac-O         cess shared resources in a coordinated manner. VMScluster software com- K         ponents synchronize access to shared resources, preventing multiple P         processes on any node in the VMScluster from interfering with each otherK         when updating data. This coordination ensures data integrity duringaO         multiple concurrent update transactions. Application programs can spec-bL         ify the level of VMScluster file sharing that is required; access isO         then coordinated by the OpenVMS Extended QIO Processor (XQP) and RecordE"         Management Services (RMS).  M         The OpenVMS queue manager controls VMScluster batch and print queues,oM         which can be accessed by any VMScluster node. Batch jobs submitted to.K         VMScluster queues are routed to any available CPU so that the batchI         load is shared.T  L         The Lock Manager provides synchronized services between systems in aK         cluster, for use both by system components such as RMS and XQP, and',         also for direct use by applications.        -                                            29     t      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M        Two or more Alpha and VAX computers connected to the same Computer In-TM        terconnect (CI), DIGITAL Storage Systems Interconnect (DSSI), or Small L        Computer Systems Interconnect (SCSI) must be configured as members of"        the same VMScluster system.  J        Mixed-architecture and mixed-version clusters containing both Alpha-        systems and VAX systems are supported.   P        VMScluster systems provide a uniform computing environment that is highlyK        scalable, highly available, and secure. OpenVMS Cluster Software im-rM        plements a single security environment within a cluster configuration.rL        The security subsystem ensures that all cluster-visible objects main-J        tain consistent security profiles and that system security auditing$        controls operate clusterwide.  K        Refer to the OpenVMS Cluster Software SPD (29.78.xx) for more infor-t        mation.          DECamds  O           DECamds Version 6.2 is available on the OpenVMS distribution kit. DE- M           Camds is a separately installable real-time high performance multi-tP           system monitoring utility. It is supported on any system running Open-O           VMS Version 6.2. The right to use DECamds is included under the termsaM           and conditions of the OpenVMS Cluster Software products (both Alpha            and VAX).r  N           DECamds provides system resource availability monitoring, investiga-N           tion aid, and correction capability. This enables system managers toM           proactively and effectively manage multiple systems from a central-e0           ized, mouse-driven DECwindows display.  O           DECamds software comprises an OpenVMS device driver which runs on ev- N           ery node that is being monitored, and console software which runs on6           the centralized X-Window monitoring station.  &           Volume Shadowing for OpenVMS        -                                            30n i         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O           Digital provides the Volume Shadowing for OpenVMS Alpha and VAX prod- M           ucts for performing disk mirroring operations, using a RAID 1 stor- M           age strategy implementation. In this description, every use of Vol- M           ume Shadowing for OpenVMS means both the Volume Shadowing for Open-mM           VMS Alpha product and the Volume Shadowing for OpenVMS VAX product.e  N         Volume Shadowing for OpenVMS is a System Integrated Product (SIP) thatO         is separately licensed. Volume Shadowing for OpenVMS provides high data K         availability for disk devices by ensuring against data loss result-iO         ing from media deterioration or controller or device failure. This pre- K         vents storage subsystem component failures from interrupting system "         or application operations.  N         The system disk and Files-11 On-Disk Structure 2 (ODS2) data disks can         be volume shadowed.   O         The Volume Shadowing for OpenVMS product supports shadowing of all MSCPiK         compliant DSA disks and all Digital SCSI disks. All disks in a sin- O         gle shadow set must have the same number of logical blocks and the same-M         physical geometry. Shadow set members can be located on a single sys--N         tem or anywhere in a VMScluster system. Disks can be configured on any2         MSCP or Digital SCSI compliant controller.  L         Volume Shadowing for OpenVMS provides fault tolerance resulting fromK         disk media errors or controller errors across the full range of Al-UN         pha and VAX processors and configurations. Shadow set member units canS         be located on different controllers and OpenVMS Alpha and VAX MSCP servers, L         providing configuration flexibility and a high degree of data avail-         ability.  K         Volume Shadowing for OpenVMS supports an unlimited number of singlecK         member shadow sets and up to 400 disks in multi-member (2 or 3 mem-s>         ber) shadow sets on a standalone or VMScluster system.  K         Phase I of Volume Shadowing (also known as Controller-Based Shadow-yN         ing) which was available in the past on OpenVMS VAX, is no longer sup-         ported.         -                                            31     n      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           The binary kit for Volume Shadowing ships with the OpenVMS Alpha andP           VAX distribution kits. To run the software, customers need to purchaseN           a license and documentation. Refer to the Volume Shadowing for Open-O           VMS Software Product Description (SPD 47.04.xx) for more information.   &         DECnet/OSI and DECnet Software  O         DECnet software is a System Integrated Product (SIP) that is separately K         licensed from the OpenVMS operating system. Refer to the DECnet foreL         OpenVMS VAX and Alpha SPD (48.48.xx) for further information on sup-<         ported communications devices and software features.  L         DECnet/OSI is available as a layered product. The license for DECnetO         for OpenVMS Alpha and DECnet/VAX will also grant the rights to use DEC- M         net/OSI. Note that only one version of DECnet may be active on a sin- K         gle system at any one time. Refer to the DECnet/OSI for OpenVMS Al-eN         pha Software Product Description (SPD 50.45.xx) and the DECnet/OSI forK         OpenVMS VAX Software Product Description (SPD 25.03.xx) for further O         information on supported hardware configurations and software features.e           DEC TCP/IP Softwaret  L         Internet networking is available through the DEC TCP/IP Services forN         OpenVMS layered product. This product provides TCP/IP networking (use-K         ful with DECwindows), Network File System (NFS), File Transfer Pro-cK         tocol (FTP), Remote Terminal Services (TELNET), and other features.tK         Refer to the DEC TCP/IP Services for OpenVMS Alpha Software ProductnP         Description (SPD 46.46.xx) and DEC TCP/IP Services for OpenVMS VAX Soft-H         ware Product Description (SPD 25.A4.xx) for further information.  "         RMS Journaling for OpenVMS  K         Digital provides the RMS Journaling for OpenVMS Alpha and VAX prod- N         ucts as separately licensed System Integrated Products (SIPs) that en-L         able a system manager, user, or application to maintain the data in-K         tegrity of RMS files in the event of a number of failure scenarios.rL         These products protect RMS file data from becoming lost or inconsis-
         tent.       -                                            32  s         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    H         RMS Journaling provides the following three types of journaling:  K         o  After-image journaling. Provides the ability to "redo" modifica- K            tions that have been made to a file. This type of journaling al-pL            lows users to recover files that are inadvertently deleted, lost,O            or corrupted. RMS Journaling recovers the file by applying the jour-aL            naled modifications to a backup copy, thereby restoring its finalL            state. No application modifications are necessary in order to use"            after-image journaling.  L         o  Before-image journaling. Provides the ability to "undo" modifica-L            tions that have been made to a file. This type of journaling pro-M            vides the ability to return a file to a previous known state. ThispN            is useful in the event that a file is updated with erroneous or badK            data. No application modifications are necessary in order to use(#            before-image journaling.v  L         o  Recovery unit journaling. Provides the ability to maintain trans-M            action integrity. A transaction may be defined as a series of manydO            file updates, on one or more files. In the event of any failure dur-sK            ing the transaction, recovery unit journaling will roll back theeM            partially completed transaction to its starting point. This allows L            complex transactions to be completed as an atomic event-partiallyN            completed transactions can be avoided. Recovery unit journaling re-+            quires application modification.   N         The binary kit for RMS Journaling ships with the OpenVMS Alpha and VAXL         distribution kits. To run the software, customers need to purchase aP         license and documentation. Refer to the RMS Journaling for OpenVMS Soft-E         ware Product Description (SPD 47.03.xx) for more information.d           DECram for OpenVMS  M         DECram for OpenVMS, a separately orderable layered product, is a diskmO         device driver that lets a system manager create pseudo disks (RAMdisks)aK         that reside in main memory for the purpose of improving I/O perfor-2K         mance. Frequently accessed data can be accessed much faster from a oM         DECram device than from a physical disk device. These RAMdisks can betM         accessed through the file system just as physical disks are accessed,o>         requiring no change to application or system software.  -                                            33  a  r      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           Since main memory is allocated for the DECram device, an amount of ex-M           tra memory is generally required. The amount of memory dedicated issM           selectable. The system manager designates the amount of memory ded- M           icated to the DECram device(s) and the files that will be stored on M           it. The maximum size of a DECram device is 524,280 blocks. Refer tolP           the DECram for OpenVMS Software Product Description (SPD 34.26.xx) for           more information.n  )           DECwindows Motif[R] for OpenVMSe  N           Digital offers a separately orderable layered product called DECwin-O           dows Motif for OpenVMS, which provides support for both OSF/Motif[R],/N           a standards-based graphical user interface, and the X user interfaceM           (XUI) in a single run-time and development environment. By default,uN           DECwindows Motif displays the OSF/Motif user interface. Because bothN           Motif and XUI are based on MIT's X Window System, applications writ-Q           ten to either toolkit will run regardless of which environment the userkM           selects. Refer to the DECwindows Motif for OpenVMS Software Producta:           Description (SPD 42.19.xx) for more information.  O           The OpenVMS software installation procedure contains an optional step O           to allow installation of the DECwindows Motif for OpenVMS workstation M           and font support, which is required to run the DECwindows Motif for M           OpenVMS layered product. Refer to the OpenVMS Alpha Version 6.2 Up- N           grade and Installation Manual or OpenVMS VAX Version 6.2 Upgrade andN           Installation Manual for details concerning the optional installationJ           of the prerequisite DECwindows Motif for OpenVMS device support.  8           Enhanced X Window System Display PostScript[R]  M           The X Window System Display PostScript system provided with DECwin- O           dows Motif extends the native X graphical programming environment fortN           DECwindows users displaying text or images on workstations that sup-L           port the XDPS extension. The DECwindows Motif for OpenVMS layered I           product must be installed and licensed in order to use Display s           PostScript.c        -                                            34x l  a      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    B         The X Window System Display PostScript has two components:  O         o  Display PostScript server extension, which is provided with the dis-pN            play server in the OpenVMS Alpha and OpenVMS VAX operating systems.8            A workstation is required to use this server.  L         o  Adobe[R] client libraries, which are used by applications to per-O            form PostScript operations, such as rotating and scaling fonts, gen-rP            erating curves, and displaying PostScript documents. The Adobe clientK            libraries are available in the DECwindows Motif for OpenVMS lay-rO            ered product, as well as on third-party platforms, including IBM[R], (            Sun[R], and Silicon Graphics.  M         X Display PostScript adds the following capabilities to the basic X11y"         Window System environment:  O           o  All DECwindows fonts can be displayed at any size and rotation an-               gle.i  N           o  Display PostScript graphics are specified in a user-defined coor-:              dinate system independent of monitor density.  P           o  Color or gray-scale rendition is automatically modified to take ad-M              vantage of the monitor type through either direct display, colorn'              dithering, or half-toning.i  P           o  Display PostScript display routines can be downloaded to the server%              and executed on command.w  M           o  Sophisticated graphics primitives, such as precisely controlled d-              Bezier curves, can be displayed.d  ?           o  Any display can be scaled and rotated arbitrarily.r  M           The Display PostScript system also allows users to view PostScript wM           files with such applications as DECwindows Mail and the CDA Viewer  J           without generating hard copy. (Terms and Conditions for Display O           PostScript can be found in the DECwindows Motif for OpenVMS Software I-           Product Description (SPD 42.19.xx).     -                                            350 o  .      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    "           CONFORMANCE TO STANDARDS  O           OpenVMS is based on the following public, national, and internationald           standards:             POSIX Supporto  M           OpenVMS supports a large number of industry standards, facilitatingIN           application portability and interoperability. This standards supportM           includes POSIX (Portable Operating System Interface). POSIX defines M           a set of interface standards for various parts of an operating sys-mP           tem. The POSIX standards have been generated by the Institute of Elec-N           trical and Electronics Engineers (IEEE) and are supported by organi-M           zations such as the International Organization for Standardization             (ISO).  P           The OpenVMS environment with POSIX for OpenVMS and DEC C installed in-M           cludes standards support for the system application programming in-dM           terface (POSIX 1003.1), shell and utilities (1003.2), and real-time 1           programming (1003.1b, ex 1003.4 draft).e  M           The OpenVMS environment, in conjunction with POSIX for OpenVMS Ver-yM           sion 2.0 and DEC C, has been certified by the National Institute ofnM           Standards and Technology (NIST) as conforming to the Federal Infor-t2           mation Processing Standard (FIPS 151-2).  $           XPG4 BASE Profile Branding  M           The OpenVMS environment, with POSIX for OpenVMS Version 2.0 and DECsM           C installed, extends the support for POSIX standards to include thepM           X/Open BASE specifications defined in the X/Open Portability Guide,SO           Issue 4 (XPG4). The XPG4 BASE specifications extend the system appli-sM           cation programming interface and shell and utilities offered in thetO           IEEE POSIX standards. XPG4 also includes standards-based internation-            alization support.  M           The OpenVMS environment, with POSIX for OpenVMS Version 2.0 and DEC E           C installed was awarded the X/Open XPG4 BASE Profile Brand.       -                                            36            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M         Platforms and components that successfully complete the branding pro-XP         cess and pass X/Open Verification Test Suite for XPG4 (VSX4) are awardedL         the X/Open XPG4 BASE Profile Brand. Components must pass a series ofL         more than 11500 tests in VSX4 to earn the X/Open BASE Profile Brand.L         These tests ensure that the OpenVMS environment with POSIX for Open-M         VMS Version 2.0 and DEC C installed supports the essential set of in- -         terfaces necessary in an open system.   K         The inclusion of XPG4 BASE support in the OpenVMS environment gives K         application developers a broader set of standards-based portabilityaO         features to incorporate into their applications. Most applications thatiK         strictly conform to the POSIX and XPG4 specifications can be devel-gK         oped on an OpenVMS system with POSIX for OpenVMS and the DEC C com- N         piler, and then ported without modification to any other platform thatG         also supports the same POSIX standards and XPG4 specifications.   9           Distributed Computing Environment (DCE) Supporti  M           The Distributed Computing Environment (DCE) for the OpenVMS productnO           family provides a set of the distributed computing features specifiedcM           by the Open Software Foundation's (OSF) Distributed Computing Envi-eM           ronment, as well as tools for application developers. With DCE, theeP           OSF has established a standard set of services and interfaces that fa-M           cilitate the creation, use, and maintenance of client/server appli-vN           cations. The DCE for OpenVMS serves as the basis for an open comput-P           ing environment where networks of multivendor systems appear as a sin-O           gle system to the user. Because DCE makes the underlying networks andeP           operating systems transparent, application developers can easily buildN           portable, interoperable client/server applications. Users can locateO           and share information safely and easily across the entire enterprise.oM           The DCE for OpenVMS supplies system managers with a set of tools toMP           consistently manage the entire distributed computing environment while3           assuring the integrity of the enterprise.t  N           The DCE for OpenVMS product family currently consists of the follow-           ing products.h          -                                            37o e  a      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M           o  DCE Runtime Services for OpenVMS, which is required for all sys-rM              tems participating in the DCE cell. The DCE Runtime Services in- M              cludes DCE client functions as well as DCE administration tools.oM              The DCE Runtime Services provides client/server applications thesM              ability to interoperate over DECnet, TCP/IP, and UDP/IP network y              protocols.-  P           o  DCE Application Developers' Kits for OpenVMS, which is required forM              developers of distributed applications but is optional for otheroM              users. The DCE Application Developers' Kit provides programmers  O              with an Interface Definition Language (IDL), an easy-to-use, ANSI sA              C-based language for writing remote procedure calls.   O           o  DCE Cell Directory Server (CDS), one of which is required for each N              DCE cell. The DCE CDS is a central repository containing informa-P              tion about the location of resources in the DCE cell. It allows ac-M              cess to resources by a single name, regardless of physical loca-c              tion.  P           o  Digital DCE Security Server, one of which is required for each DCE.O              The DCE Security Server protects resources from illegal access anddI              provides secure communications within and between DCE cells.V  M           The right-to-use the DCE Runtime Services is bundled with the Open-4N           VMS operating system base license. All other DCE products are avail-M           able as separate layered products. Refer to the Digital DistributednN           Computing Environment (DCE) for OpenVMS Software Product Description7           (SPD 43.05.xx) for more detailed information.   =           Support for OSF/Motif and X Window System Standardsp  M           DECwindows Motif provides support for OSF/Motif, a standards-based hL           graphical user interface, and the X Consortium's X Window System, /           Version 11, Release 5 (X11R5) server.m  (           Standards Supported by OpenVMS        -                                            38-           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           The OpenVMS operating system is based on the public, national, and in-N           ternational standards listed below. These standards are developed byM           the American National Standards Institute (ANSI), U.S. Federal Gov-fO           ernment (responsible for FIPS), Institute of Electrical and Electron-aP           ics Engineers (IEEE), and the International Organization for Standard-M           ization (ISO). The following information may be useful in determin-eM           ing responsiveness to stated conformance requirements as enabled inaO           particular commercial and/or government procurement solicitation doc-l           uments.t  7           o  ANSI X3.4-1986: American Standard Code forf$              Information Interchange  4           o  ANSI X3.22-1973: Recorded Magnetic Tape              (800 BPI, NRZI)  9           o  ANSI X3.27-1987: File Structure and LabelingS:              of Magnetic Tapes for Information Interchange  4           o  ANSI X3.39-1986: Recorded Magnetic Tape              (1600 BPI, PE)T  6           o  ANSI X3.40-1983: Unrecorded Magnetic Tape  7           o  ANSI X3.41-1974: Code Extension TechniquesF%              for Use with 7-bit ASCII   7           o  ANSI X3.42-1975: Representation of Numericc(              Values in Character Strings  4           o  ANSI X3.54-1986: Recorded Magnetic Tape              (6250 BPI, GCR)  6           o  ANSI X3.131-1986 (SCSI I): Small Computer              System Interfacei  7           o  ANSI X3.131-1994 (SCSI II): Small Computern              System Interfaced  7           o  ANSI/IEEE 802.2-1985: Logical Link Controlr  9           o  ANSI/IEEE 802.3-1985: Carrier Sense Multipleo,              Access with Collision Detection  -                                            39f i  e      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    <           o  FIPS 1-2: Code for Information Interchange, Its5              Representations, Subsets, and Extensionsy  P              Note: 1-2 includes ANSI X3.4-1977(86)/FIPS 15; ANSI X3.32-1973/FIPS5              36; ANSI X3.41-1974/FIPS 35; and FIPS 7.A  /           o  FIPS 3-1/ANSI X3.22-1973: RecordedoB              Magnetic Tape Information Interchange (800 CPI, NRZI)  M           o  FIPS 16-1/ANSI X3.15-1976: Bit Sequencing of the Code for Infor-nB              mation Interchange in Serial-by-Bit Data Transmission  1              Note: FED STD 1010 adopts FIPS 16-1.d  O           o  FIPS 22-1/ANSI X3.1-1976: Synchronous Signaling Rates Between Datai6              Terminal and Data Communication Equipment  1              Note: FED STD 1013 adopts FIPS 22-1.m  P           o  FIPS 25/ANSI X3.39-1986: Recorded Magnetic Tape for Information In-0              terchange (1600 CPI, Phase Encoded)  L           o  FIPS 37/ANSI X3.36-1975: Synchronous High-Speed Data Signaling J              Rates Between Data Terminal Equipment and Data Communication               Equipment/              Note: FED STD 1001 adopts FIPS 37.r  P           o  FIPS 50/ANSI X3.54-1986: Recorded Magnetic Tape for Information In-B              terchange, 6250 CPI (246 CPMM), Group Coded Recording  M           o  FIPS 79/ANSI X3.27-1987: Magnetic Tape Labels and File Structureo(              for Information Interchange  M           o  FIPS 86/ANSI X3.64-1979: Additional Controls for Use with Ameri-bC              can National Standard Code for Information Interchangep  K           o  FIPS 151-2: Portable Operating System Interface (POSIX 1003.1)c  1              Note: Other FIPS are not applicable.a  I           o  POSIX 1003.1, 1990: System application programming interfacei  1           o  POSIX 1003.1b, Real Time Programmingn  -                                            40i i  i      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    .           o  POSIX 1003.2, Shell and Utilities  L              Note: Information regarding interchangeability of ANSI and FED I              standards with FIPS is contained in "ADP Telecommunications rJ              Standards Index," July 1988, published and maintained by the -              General Services Administration.   L           o  ISO 646: ISO 7-bit Coded Character Set for Information Exchange  O           o  ISO 1001: File Structure and Labeling of Magnetic Tapes for Infor-d              mation Interchangee  O           o  ISO 1863: Information Processing - 9-track, 12, 7 mm (0.5 in) wideiO              magnetic tape for information interchange recorded at 32 rpmm (800f              rpi)   M           o  ISO 1864: Information Processing - Unrecorded 12, 7 mm (0.5 in) yL              wide magnetic tape for information interchange - 35 ftpmm (800 K              ftpi) NRZI, 126 ftpmm (3 200) ftpi phase encoded and 356 ftmm i              (9 042 ftpi), NRZIo  E           o  ISO 2022: Code Extension Techniques for Use with ISO 646e  9           o  ISO 3307: Representations of Time of the Dayd  O           o  ISO 3788: Information Processing - 9-track, 12, 7 mm (0.5 in) wide M              magnetic tape for information interchange recorded at 63 rpmm (1f$              600 rpt), phase encoded  M           o  ISO 4873: 8-Bit Code for Information Interchange - Structure ande%              Rules for Implementationl  .           o  ISO 5652: Recorded Magtape (6250)  A           o  ISO 6429: Control Functions for Coded Character Sets[  D           o  ISO 9316: 1989 (SCSI-1) Small Computer System Interface  P           o  ISO 9660: Information Processing - Volume and file structure of CD-)              ROM for information exchangey  E           o  ISO 10288: 1994 (SCSI-2) Small Computer System Interface   -                                            41-           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42             INSTALLATION  N         OpenVMS Alpha is distributed as a binary kit on CD-ROM. Procedures forN         setting up the system disk from media and for preparing the system forO         day-to-day operations are provided. The procedures use POLYCENTER Soft-oL         ware Installation utility to configure and install the OpenVMS AlphaK         Version 6.2 operating system. These procedures are described in thehK         OpenVMS Alpha Version 6.2 Upgrade and Installation Manual and coverO         letter.n  L         OpenVMS VAX is distributed as binary kits on CD-ROM and tape. Proce-M         dures for setting up the system disk from a kit and for preparing thevO         system for day-to-day operations are easy and straightforward. The pro- L         cedures are described in the OpenVMS VAX Version 6.2 Upgrade and In-L         stallation Manual. Computer-specific information is contained in theK         upgrade and installation supplements for each family of VAX comput--         ers.  (         POLYCENTER Software Installation  M         The POLYCENTER Software Installation utility is now included in Open-oM         VMS. The POLYCENTER Software Installation utility is distributed with P         the OpenVMS Version 6.2 distribution kit, and the right to use the POLY-M         CENTER software is bundled with the OpenVMS operating system base li-sM         cense. The POLYCENTER Software Installation utility is a new technol-oL         ogy that simplifies the installation and management of OpenVMS prod-
         ucts.y  N         For system managers, the POLYCENTER Software Installation utility pro-L         vides DIGITAL Command Language (DCL) and DECwindows Motif interfacesK         which can be used to install, configure, reconfigure, and deinstall K         software products that have been prepared with the POLYCENTER Soft- L         ware Installation utility. In addition, the POLYCENTER software pro-L         vides a database to track the installation, reconfiguration, and de-K         installation of software. For products installed with other instal-hN         lation technologies, the POLYCENTER Software Installation utility pro-K         vides a mechanism for adding information about them to the POLYCEN- L         TER database. The POLYCENTER Software Installation utility also pro-    -                                            42y m  d      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    L         vides the ability to manage dependencies between products during the         installation process.   K         For software providers, the POLYCENTER software simplifies the task M         of packaging software by providing a simple, declarative language forwK         describing material for the installation kit and defining how it islK         installed. The POLYCENTER Software Installation utility handles thelL         functions; the developer instructs the utility what to do. This sig-O         nificantly reduces the complexity and time to develop installation pro-tK         cedures. The language allows the developer to easily specify depen-rL         dencies on other software, manage certain "objects" in the executionK         environment (such as files and directories), and anticipate and re- M         solve conflict before it occurs. The POLYCENTER software also signif- K         icantly simplifies the packaging of multiple software products into.         one logical product.           VMSINSTAL   N         OpenVMS VAX includes the VMSINSTAL facility to automate operating sys-O         tem software updates, as well as to handle the installation of optionalnM         Digital-supplied software products. OpenVMS Alpha includes the VMSIN-nM         STAL facility to handle the installation of optional Digital-suppliedO:         software products that have not converted to PCSI.  $         Test Package and Diagnostics  K         OpenVMS includes a User Environment Test Package (UETP), which ver-bO         ifies that the OpenVMS operating system is properly installed and readyr*         for use on the customer's systems.  M         Diagnostics can be run on individual devices during normal system op- J         eration. Certain critical components can operate in degraded mode.  -         OpenVMS Alpha DISK SPACE REQUIREMENTSs  0         Operating System Disk Space Requirements          -                                            43m           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O           The disk space requirements for OpenVMS Alpha vary according to whichc            options are installed:  M           ___________________________________________________________________r%                                 SpacedM           File_Category_________Used_________Running_Total___________________   3           Minimum OpenVMS        80 MB        80 MBs           Filest  3           Other OpenVMS          89 MB       169 MBd           Files   3           Paging File (re-       38 MB       207 MBi           quired)   3           Swap File (sug-         3 MB       210 MB            gested)   3           Dump File (op-         28 MB       238 MBi           tional)h  3           Decompressed Help      15 MB       253 MBs           Files (optional)  3           Full DECwindows        65 MB       318 MB            Motif V1.2-3           (optional)  3           Safeguard for          50 MB       368 MBnM           upgrading__________________________________________________________   O           The Minimum OpenVMS Files listed above are for a system configuration O           where all optional features have been declined during the initial in-nP           stallation. For most applications, this is not a realistic OpenVMS en-           vironment.  P           The Paging, Swap, and Dump file requirements above are the minimum forM           a system with 32 MB of main memory. Additional memory in most casestP           will add to the space needed for these files, as will particular needsO           of your application. With careful system management it is possible toa9           use Paging file space as a temporary dump file.E  -                                            44  p  c      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           For a VMScluster system disk, Paging, Swap, and Dump files cannot beM           shared between nodes so the files must either be duplicated on the V4           system disk or located on some other disk.  D           DECwindows Motif for OpenVMS Alpha Disk Block Requirements  N           To support OpenVMS Alpha and the DECwindows Motif for OpenVMS Alpha,N           a system disk of greater than 380 MB is recommended, however, a sub-O           set of DECwindows Motif can be installed. The disk space required forpN           the installation of DECwindows Motif is 64 MB. The permancent amountN           of space used is 62 MB. An additional 33 MB is needed to install theM           DECwindow X11 Display Server and associated files. (These DECwindowaM           X11 Display Server and associated files are included in the OpenVMSiN           Alpha Version 6.2 media.) These disk space requirements are in addi-P           tion the disk space required for the OpenVMS Alpha V6.2 operating sys-N           tem as indicated in the OpenVMS Alpha DISK SPACE REQUIREMENTS table.  M           Installation of the DECwindows Motif Version 1.2-3 layered product rO           gives customers the option of installing any or all of the following t           components:e  M           o  User environment and applications - 34 MB. This section providesaM              support for running DECwindows Motif applications on VAX computes              servers.   N           o  Programming support - 7 MB. This section includes support for theH              DEC C, DEC C++, DEC Fortran, Pascal, and VAX C programming M              languages. If a subset of languages is installed, the amount of  .              disk space required will be less.  0           o  Example files - approximately 7 MB.  <           o  Translated Image Support - approximately 17 MB.  /         Layered Product Disk Space Requirementso  M         In addition to the disk space used directly by Digital or third-partyeL         layered products (as specified in documentation for those products),P         there may be additional space used to store information from those prod-L         ucts in OpenVMS Help Libraries, Command Tables, Object Libraries andL         elsewhere. The exact amount of additional disk space required cannot  -                                            45M w  h      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           be totally predicted due to the possibility of recovering unused spaceO           already existing in those library files. Unusually large modules con- N           tributed by layered products can also affect the amount of space re-N           quired for upgrading to a new version of the OpenVMS Alpha operating           system.l    +         OpenVMS VAX DISK SPACE REQUIREMENTS   8         Disk Space Requirements (Block Cluster Size = 3)  K         To support the complete OpenVMS VAX operating system environment, a,N         system disk of greater than 100 MB is recommended. When a smaller diskK         is used, additional tailoring is required prior to installing some SN         OpenVMS VAX options. This does not include the dump file space. Refer K         to the OpenVMS VAX Version 6.2 Upgrade and Installation Manual for -!         information on tailoring.b  2           Operating System Disk Space Requirements  M           The disk space requirements for OpenVMS VAX vary according to whichr            options are installed:                                      -                                            46r i         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________p%                                 Space M           File_Category_________Used_________Running_Total___________________   3           OpenVMS Files          83 MB        83 MB   3           Paging File (after      6 MB        89 MB            installation)   5           Swap File (sug-         1.2 MB      90.2 MBm           gested)   5           Dump File (op-          6.2 MB      96.4 MBn           tional)n  5           Decompressed Help       7  MB      103.4 MBn           Files (optional)  5           Safeguard for          25 MB       128.4 MB            upgradingA  5           Variable ad-            3.3 MB     131.7 MBf           ditional space           (additional files,M           INDEXF.SYS,_etc.)__________________________________________________   M           The above data was created from an installation on a VAXServer 2000 /           with 6 MB of memory and an RD54 disk.i  N           Additional memory will add to the space required for Page, Swap, andP           Dump files and the variable additional space will increase with larger           memory and disk.  ?        DECwindows Motif for OpenVMS VAX Disk Block Requirementso  dK        To support OpenVMS VAX and the DECwindows Motif for OpenVMS VAX lay- M        ered product, a system disk of greater than 175 MB is recommended. ThetM        disk space required for the installation of DECwindows Motif is 39 MB.(K        The permanent amount of space used is 34 MB. An additional 16 MB are P        needed to install the DECwindows X11 Display Server and associated files.M        (These DECwindows X11 Display Server and associated files are included K        in the OpenVMS VAX Version 6.2 media.) These disk space requirementsML        are in addition to the 78 MB required for the other components of the  -                                            47f i         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O         OpenVMS VAX operating system environment. Refer to the OpenVMS VAX Ver-/O         sion 6.2 Upgrade and Installation Manual for details on tailoring smallcJ         system disks in order to support the DECwindows Motif environment.  P         Installation of the DECwindows Motif Version 1.2-3 layered product givesK         customers the option of installing any or all of the following com-t         ponents:  K         o  User environment and applications - 22 MB. This section providesIK            support for running DECwindows Motif applications on VAX compute             servers.N  L         o  Programming support - 6 MB. This section includes support for theP            DEC C, DEC C++, DEC Fortran, Pascal, and VAX C programming languages.N            If a subset of languages is installed, the amount of disk space re-            quired will be less.1  .         o  Example files - approximately 6 MB.  L         Note that the individual sizes add up to more than the total becauseK         some components are shared by multiple portions of the environment.   "          MEMORY SPACE REQUIREMENTS  1           OpenVMS Alpha Memory Space Requirements   O           The minimum amount of memory required to install, boot, and log in to-N           an OpenVMS Alpha system is 32 MB. To ensure satisfactory performanceP           for particular applications or numbers of users, additional memory mayO           be required. Refer to specific layered product documentation for mem-d           ory requirements.n  /           OpenVMS VAX Memory Space RequirementsG  O           The minimum amount of memory supported for an OpenVMS VAX environmentaM           is dependent upon the specific system(s) being used and the overallPP           type of configuration and application requirements. The minimum amountM           of memory supported for a standalone VAX system running OpenVMS VAXPO           Version 6.2 is 4 MB. The minimum amount of memory supported for a VAXP?           workstation running OpenVMS VAX Version 6.2 is 12 MB.   -                                            48  S  1      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           The following tables give examples of the minimum amount of memory re-N           quired for a system user to install, boot, and log in to OpenVMS VAXN           Version 6.2. Specific requirements will depend upon the type of sys-M           tem being used and what other software is installed. To ensure sat-xN           isfactory performance of applications, additional memory will be re-           quired.   M           ___________________________________________________________________ M           Component_____________________Necessary_Memory_____________________   .           OpenVMS VAX Version 6.2       4.0 MB  .           DECnet-VAX                     .5 MB  .           VAXcluster                    1.5 MB  .           DECwindows Motif with         1.5 MB!           remote execution of ap-O!           plications (X11 Displaye           Server only)  .           DECwindows Motif with         5.0 MB            local execution of ap-           plications (Includes            X11 Display Server and"           DECwindows Motif layeredM           product)___________________________________________________________e  O           The following example configurations are based on the previous table:3  M           ___________________________________________________________________eM           System________________________Minimum_Supported_Memory_____________r  -           OpenVMS VAX Version 6.2,       6 MBt           DECwindows Motif with             applications executing           remotely, and DECnet           (standalone system)p      -                                            49f C  d      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________ M           System________________________Minimum_Supported_Memory_____________9  -           OpenVMS VAX V6.2, DECwin-     12 MB "           dows Motif with applica-"           tions executing locally,M           VAXcluster_and_DECnet______________________________________________N  K        Note: These are the minimum memory requirements. More memory will berP        required for satisfactory performance of the operating system and DECwin-K        dows Motif applications. The performance and memory usage of DECwin-LK        dows Motif systems is particularly sensitive to system configurationeK        and window and application usage. Remote execution of an applicationsM        requires an additional system that runs the application while the dis-a?        play of the application occurs on the local workstation.t  N         Please refer to specific layered product Software Product Descriptions&         for their memory requirements.  O         Please refer to the OpenVMS VAX documentation for more information con- +         cerning performance considerations.S  %         DISTRIBUTION AND BACKUP MEDIA              OpenVMS Alpha:  N           OpenVMS Alpha is available on CD-ROM only. The OpenVMS Alpha VersionP           6.2 Binary CD-ROM contains the OpenVMS Alpha Version 6.2 save sets andP           selected documentation in text and Postscript format. The OpenVMS Ver-N           sion 6.2 Online Documentation CD-ROM contains all OpenVMS Documenta-O           tion in Bookreader format. An InfoServer or local drive is needed foru+           upgrades and system disk backups.l             OpenVMS VAX:  N           OpenVMS VAX is available on CD-ROM, TK50, or Magnetic tape distribu-           tion media.           -                                            50f e  S      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P          The OpenVMS VAX Version 6.2 Binary CD-ROM contains the OpenVMS VAX Ver-P           sion 6.2 save sets, OpenVMS VAX Version 6.2 standalone BACKUP, and se-O           lected OpenVMS documentation in text and PostScript format. The Open-oO           VMS Version 6.2 Online Documentation CD-ROM contains all OpenVMS Doc--*           umentation in Bookreader format.  P           The TK50 Streaming Tape contains the OpenVMS VAX Version 6.2 save sets8           and OpenVMS VAX Version 6.2 standalone BACKUP.  M           The 9-track 1600 BPI Magnetic tape contains the OpenVMS VAX Version            6.2 save sets.  P          The OpenVMS VAX operating system is also available as part of the Open-I           VMS VAX Consolidated Software Distribution (ConDIST) on CD-ROM.              GROWTH CONSIDERATIONSy  O           The minimum hardware and software requirements for any future versionnM           of this product may be different from the requirements for the cur-            rent version.i             DOCUMENTATIONr  O           For OpenVMS Version 6.2, there will be one Documentation Set for bothaP           the Alpha and VAX platforms. Most manuals will be common to both plat-I           forms, although there are still some platform-specific manuals.l  ?           OpenVMS offers documentation in a variety of formats:i  H           o  Online books (viewed using the DECwindows Motif Bookreader)  M           For Version 6.2, online documentation will be distributed on a sep-pP           arate CD-ROM that will ship with the OpenVMS Binary CD-ROMs. CustomersN           will automatically receive the entire OpenVMS documentation offeringO           in Bookreader format on the Documentation CD-ROM. Viewing online doc-oN           umentation in Bookreader requires that DECwindows Motif be installedO           on the system and that a valid DECwindows Motif license be registered            and loaded.e  %           o  Printed books (hardcopy)   -                                            51  d  t      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N          OpenVMS hardcopy documentation is made up of two offerings: the Open-M          VMS Full Documentation Set and the OpenVMS Base Documentation Set. A.P          complete listing of all hardcopy manuals and their part numbers is con-9          tained in the Overview of OpenVMS Documentation.t            Full Documentation Sete  L          The Full Documentation Set is for users who need extensive explana-M          tory information on all major OpenVMS components, complete reference P          information on system routines and utilities, detailed examples, guide-L          lines for VMScluster systems, programming concepts, a master index,N          and information on the Help Message utility. This set meets the needsM          of system managers and of system and application programmers. It in- +          cludes the Base Documentation Set.             Base Documentation Setc  O          The Base Set includes the most commonly used OpenVMS manuals, address-_O          ing the needs of general users and system managers of small standalone O          systems. Manuals, such as the Release Notes, New Features, and the DCL 1          Dictionary are included in the Base Set.   >          Each book in these sets is also separately orderable.            o  Printable files   P         In addition to the online and hardcopy manuals, several OpenVMS archivedK         books will be offered as PostScript files on the OpenVMS Documenta-lK         tion CD-ROM. For a complete listing of OpenVMS archived books refersL         to the Overview of OpenVMS Documentation. These books can be orderedK         separately and on demand through the Software Supply Business (SSB)t         group.  L         Printable PostScript and text files will also be offered for the Re-3         lease Notes, Installation Guides, and SPDs.   L         You may print the electronic Software documentation accompanying theL         Software as reasonably necessary to exercise your license to use the         Software.i    -                                            52O V  e      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42             SOURCE LISTINGS   O         OpenVMS Operating System Source Listings are available on CD-ROM. These L         discs contain all source listings files and the Alpha specific debugM         symbol tables that make up the OpenVMS operating system. Digital pro- O         vides source listings for all key modules of the OpenVMS operating sys- M         tem that are appropriate for end users or application developers. TheVL         debug symbol files (DSF) on the OpenVMS Alpha Source Listings CD-ROMK         contain information used by the OpenVMS Alpha System-Code Debugger. L         Certain company confidential source listings and debug symbol files,.         however, are excluded from the CD-ROM.  L         The orderable CD-ROM kit includes the license required to view theseM         files on a standalone system or a VMScluster system. If users want totQ         make these files available to another system (possibly at a remote site),a/         they will need to purchase another kit.   L         A source license agreement must be signed for all kits. Contact your:         local Digital representative for more information.           ORDERING INFORMATION  !           Alpha Software Licenses   E           QL-MT1A*-6*     OpenVMS Alpha Operating System Base Licensee  L           QL-MT1A9-6*     OpenVMS Alpha Operating System Symmetric Multipro->                           cessing (SMP) Base Extension License  J           QL-MT2A*-**     OpenVMS Alpha Individual User License (No Longer$                           Available)  L           QL-MT3A*-B*     OpenVMS Alpha Distributed Interactive User License/                           (No Longer Available)i  8           QL-MT3A*-3*     OpenVMS Concurrent Use License             VAX Software Licensesi      -                                            53e           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      F           QL-001A*-**     VAX VMS Operating System License for OpenVMS  C           QL-005A*-6*     OpenVMS VAX Operating System Base Licensen  J           QL-005A9-6*     OpenVMS VAX Operating System Symmetric Multipro->                           cessing (SMP) Base Extension License  H           QL-XULA*-**     OpenVMS VAX Individual User License (No Longer$                           Available)  J           QL-09SA*-AA     OpenVMS VAX Distributed Interactive User License/                           (No Longer Available)o  8           QL-MT3A*-3*     OpenVMS Concurrent Use License  =           Alpha and VAX CD-ROM Media and Online Documentation   I           QA-MT1AA-H8     OpenVMS Alpha software and online documentationp                            CD-ROM  G           QA-XULAA-H8     OpenVMS VAX software and online documentatione                            CD-ROM  J           QA-MT3AA-H8     OpenVMS VAX/Alpha software and online documenta-%                           tion CD-ROM5  .           VAX Media and Hardcopy Documentation  5           QA-09SA*-H*     With Base Documentation Sete  5           QA-001A*-H*     With Full Documentation Setl  -           Digital Alpha Layered Product Mediac  K           QA-03XAA-H8     Digital CD-ROM Software Library for OpenVMS Alpha   @           Digital VAX Operating System and Layered Product Media  K           QA-VWJ8A-A8     OpenVMS VAX Consolidated Software Distribution ono&                           Compact Disc  %           Hardcopy Documentation Setst  8           QA-09SAA-GZ     OpenVMS Base Documentation Set  8           QA-001AA-GZ     OpenVMS Full Documentation Set  -                                            54  e         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42               Source Listings Kits  E           QB-MT1AB-E8     OpenVMS Alpha Listings CD-ROM Kit & License   C           QB-001AB-E8     OpenVMS VAX Listings CD-ROM Kit & Licensei  #           Software Product Servicesa  L           QT-MT1A*-**     OpenVMS Alpha Base System Software Support Service  I           QT-MT2A*-**     OpenVMS Alpha Interactive User Software Support !                           Servicef  K           QT-001A*-**     VAX VMS Operating System Software Support Service_  L           QT-005A*-**     OpenVMS VAX Operating System Base Software Support!                           Service_  G           QT-XULA*-**     OpenVMS VAX Interactive User Software Support !                           Service   K           QT-09SA*-**     OpenVMS VAX Distributed Interactive User Software )                           Support Service0  N           A variety of integrated and  la carte hardware and software productN           services are available. For additional information, contact your lo-7           cal Digital office or Digital representative.              CD-ROM7           Media and Online Documentation Update Service   I           QT-MT1AA-E8     OpenVMS Alpha software and online documentationa                            CD-ROM  G           QT-XULAA-E8     OpenVMS VAX software and online documentationv                            CD-ROM  J           QT-MT3AA-E8     OpenVMS VAX/Alpha software and online documenta-%                           tion CD-ROMt  <           Digital Alpha Layered Product Media Update Service  K           QT-03XAA-C8     Digital CD-ROM Software Library for OpenVMS Alphad  I           Digital VAX Operating System and Layered Product Update Serviced  K           QT-VWJ8A-C8     OpenVMS VAX Consolidated Software Distribution on                             CD-ROM  -                                            55  d         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    4           Hardcopy Documentation Only Update Service  >           QT-MT1AB-KZ     OpenVMS Alpha Base Documentation Set  >           QT-MT1AH-KZ     OpenVMS Alpha Full Documentation Set  E           OpenVMS VAX Media and Hardcopy Documentation Update Servicee  5           QT-09SA*-E*     With Base Documentation Seti  5           QT-001A*-E*     With Full Documentation Set   )           OpenVMS Source Listings Service4  ?           QT-MT1AB-Q8     OpenVMS Alpha Source Listings Servicep  =           QT-001AB-Q8     OpenVMS VAX Source Listings Servicet  P           *  Denotes variant fields. For additional information on available li-P              censes, services, and media, refer to the appropriate Digital price              book.             SOFTWARE LICENSING  N           The OpenVMS operating system software is furnished under the licens-N           ing provisions of Digital Equipment Corporation's Standard Terms and           Conditions.   M           The OpenVMS Alpha operating system license includes the license forfO           DECprint Supervisor for OpenVMS, Base. The DECprint Supervisor (DCPS) N           for OpenVMS has separate documentation, media kit, and service prod-M           ucts. Refer to the DECprint Supervisor for OpenVMS Software Product :           Description (SPD 44.15.xx) for more information.  M          The right-to-use POSIX for OpenVMS is included with the OpenVMS base-P          operating system license. Refer to the POSIX for OpenVMS Software Prod-=          uct Description (SPD 38.82.xx) for more information.p  N           The right-to-use the DCE Runtime Services is included with the Open-M           VMS base operating system license. Refer to the Digital DistributedeM           Computing Environment (DCE) SPD 43.05.xx for more detailed informa-e5           tion on the DCE for OpenVMS product family.   -                                            56, d  o      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           The System Integrated Products DECnet for OpenVMS Alpha and DECnet-VAXO           are separately licensed products. Refer to the DECnet for OpenVMS VAXnO           and Alpha Software Product Description (SPD 48.48.xx) for more infor-            mation.   J           The System Integrated Products (SIPs), OpenVMS Cluster Software K           (29.78.xx), Volume Shadowing for OpenVMS (SPD 47.04.xx), and RMS  H           Journaling for OpenVMS (SPD 47.03.xx) are separately licensed N           products. Refer to the appropriate Software Product Description for            more information.   M           DECwindows Motif for OpenVMS is a separately licensed layered prod-sM           uct. Refer to the DECwindows Motif for OpenVMS Software Product De-i8           scription (SPD 42.19.xx) for more information.  O           DECram for OpenVMS is a separately licensed layered product. Refer touP           the DECram for OpenVMS Software Product Description (SPD 34.26.xx) for           more information.n  L          DECmigrate for OpenVMS AXP Systems is a separately licensed layeredP          product. Refer to the DECmigrate for OpenVMS AXP Systems Software Prod-=          uct Description (SPD 39.44.xx) for more information._  ,           Software License Information - VAX  O           The OpenVMS VAX operating system uses one of two different categories P           of licenses depending on the hardware and software configurations usedO           and currently supported. This information is also provided in the ap-l(           plicable country's Price List.  M           These are the two categories of operating system licenses for Open-            VMS VAX:             1. VAX VMS Licensing"           2. OpenVMS VAX Licensing  P           Digital provides the proper license type with the purchase of the sys-J           tem. Not all license types are available for every system model.  %           VAX VMS License Information_    -                                            57_ _  _      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    L         The VAX VMS licenses include the rights for the DEC Rdb Run-Time Op-K         tion for OpenVMS VAX. This allows the running of an application de- L         veloped using DEC Rdb for OpenVMS VAX software. However, DEC Rdb forM         OpenVMS VAX has separate media and documentation. In addition, should O         a user want to perform Rdb development, a separate license must be pur-_>         chased. Refer to SPD 25.59.xx for further information.  K         Effective February 6, 1995, the VAX VMS (UPI001) licenses no longer O         include the rights for the Digital RDB Run-Time option for OpenVMS VAX,cN         and do not permit use of RDB Runtime on prior versions of OpenVMS VAX.  P         Each of the following license are for a specified hardware system, whichK         is either the system the license was originally shipped with or theo3         system on which the license was first used:   8           o  Operating System Base License (QL-001**-**)  H           o  Operating System User License for OpenVMS VAX (QL-001**-**)  >           o  Traditional License for OpenVMS VAX (QL-001**-**)  3           There are four types of VAX VMS licenses:   .           1. Traditional License (QL-001A*-**)  O           This type of license provides unlimited use to the users on a definedsN           system. VAX VMS traditional licenses are sized to capacity according           to system type.i  -           2. Multi-User License (QL-001A*-**)s  N           This type of license provides use according to a specified number ofM           concurrent users. This is an activity-based license. The Multi-useriP           License provides the customer with the right to use the operating sys-M           tem up to the limit of users specified in the license. An operating P           system "user" is a person who is logged in to the system and/or is us-N           ing the system interactively. This license is only available on lim-F           ited system models, primarily MicroVAX and VAX 4000 systems.      -                                            58  0  r      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M           Interactive use of VAX systems licensed with the Multi-user LicensedM           may be increased by the addition of OpenVMS User Licenses* (for one O           or more users). Refer to the section on Ordering Information for fur-e           ther information.a  6           3. VAX VMS Workstation License (QL-001A*-**)  O           This type of license provides use for a single user on a VAX Worksta-OM           tion. This license type allows one direct login for the single user L           and then one additional login for system management purposes only.  N           Additional interactive use of VAX Workstations licensed with the VAXN           VMS Workstation License requires the addition of an OpenVMS User Li-N           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*-**)  N           This type of license provides for the noninteractive use of OpenVMS.  N           OpenVMS based VAXservers are sold with a File and Application ServerO           License. The intent of an OpenVMS based VAXserver is to provide file,nN           print, application, and compute "services" to "clients" who have re-N           motely submitted their requests (for example via network/remote sub-N           mit/batch jobs, and so forth). This license type also allows one di-9           rect login for system management purposes only.   P          Additional interactive use of OpenVMS VAXservers licensed with the FileP          and Application Server License requires the addition of an OpenVMS UserO          License* (for one or more users). Refer to the section on Ordering In-t+          formation for further information.t  N           The Operating System Base License provides the right to use only the@           OpenVMS Alpha features of the current version license.  N           Not all VAX VMS license types are available for all versions of VMS,$           OpenVMS or all VAX models.  M           *  The OpenVMS VAX Individual Use licenses are not supported by the O              VMS or OpenVMS VAX operating system releases prior to Version 5.5.X  )           OpenVMS VAX License Information   -                                            59w f  i      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    7           There are four types of OpenVMS VAX licenses:   7           1. OpenVMS VAX O/S Base License (QL-005A*-**)v  +           LMF Product Name: BASE-VMS-250136   M           OpenVMS VAX O/S Base License grants the right to unrestricted, non-xO           interactive use of the OpenVMS VAX operating system for the executionlP           of remotely submitted requests for batch, print, application, and com-N           puting services, on a designated, single processor. This license au-H           thorizes one direct login for system management purposes only.  M           The OpenVMS VAX Base License does not include the license right forgN           the DEC Rdb Run-Time Option for OpenVMS VAX. The DEC Rdb for OpenVMS7           VAX Run-Time License is available separately.m  N           The Operating System Base License is a prerequisite for all Interac-A           tive User Licenses and all SMP Base Extension Licenses.u  M          Interactive use of systems licensed with an OpenVMS VAX O/S Base Li-rP          cense requires the addition of an OpenVMS User License (for one or moreM          users). Refer to the section on Ordering Information for further in-n          formation.s  M          The Operating System Base License provides the right to use only thet?          OpenVMS Alpha features of the current version license.n  P          The OpenVMS VAX O/S Base License also includes the license for DECprintL          Supervisor for OpenVMS VAX. The DECprint Supervisor for OpenVMS VAXL          has separate documentation, media kits, and service products. Refer-          to SPD 44.15.xx for further details.   ;           2. Symmetric Multiprocessing (SMP) Base Extension "              License (QL-005A9-6*)  +           LMF Product Name: BASE-VMS-250136a  M           SMP Base Extensions extend the O/S Base License to enable symmetriciN           multiprocessing capability on a select number of OpenVMS VAX systemsM           supporting SMP. SMP Base Extensions are permanently tied to the O/SO  -                                            60m u         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    8           Base License and may not be separated from theF           O/S Base License if an SMP board is removed from the system.  M           SMP Extensions grant the right to use the same version of the oper-aO           ating system software as permitted for the corresponding O/S Base Li-l>           cense at the time when the SMP Extension is granted.  0           3. OpenVMS VAX Individual User License              (QL-XULA*-**)               (No Longer Offered)  $           LMF Product Name: VMS-USER  N           The OpenVMS VAX Individual User License provides the right to inter-N           actively use the operating system by the specified or unlimited num-N           ber of concurrent users on a designated, single processor. A user isO           an individual who is logged in to a processor and/or is interactivelyaM           using the operating system software by means other than a login. An N           OpenVMS VAX O/S Base License or one of the four types of VAX VMS Li-N           censes (QL-001A*-**) is a prerequisite for the OpenVMS User License.  N           The Operating System Base License provides the right to use only the@           OpenVMS Alpha features of the current version license.  P           The OpenVMS VAX O/S Base, the SMP Base Extension, and Interactive UserM           licenses are not supported by the VMS or OpenVMS VAX operating sys-a8           tem releases prior to OpenVMS VAX Version 5.5.  =           4. OpenVMS VAX Distributed Interactive User LicenseA              (QL-09SA*-**)               (No Longer Offered)  $           LMF Product Name: ADL-USER  M           This license grants the right to interactive use of the OpenVMS VAX N           operating system, provided the appropriate Operating System Base Li-P           cense or one of the four types of VAX VMS Licenses has been previouslyN           installed on a VAX system. The Distributed Interactive User licensesO           are concurrent use licenses and are available in any quantity desired     -                                            61L L  *      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O         except unlimited. Distributed Interactive User licenses are mobile (re- K         designatable) and may be installed and used on a single OpenVMS VAX <         processor, or shared in a single OpenVMS VAXcluster.  P         A Distributed Interactive user is defined as an individual who is loggedL         in to OpenVMS VAX processor or OpenVMS VAXcluster and/or is interac-L         tively using the operating system software by means other than a lo-         gin.  D           5. OpenVMS Concurrent Use License (For both VAX and Alpha)              (QL-MT3A*-3*)  2           LMF Product Name: OPENVMS-ALPHA-USER-ADL  M           This license grants the right to interactive use of the OpenVMS op- P           erating system, provided the appropriate OpenVMS Operating System BaseN           License in installed on an OpenVMS VAX processor, and/or on an Open-N           VMS Alpha processor, or on OpenVMS VAX processors if one of the fourO           types of VAX VMS Licenses has been previously installed on a VAX sys-nM           tem. The OpenVMS Concurrent Use licenses are available in any quan-nP           tity desired except unlimited. OpenVMS Concurrent Use licenses are mo-O           bile (redesignatable) and may be installed and used on a single Open- P           VMS VAX or OpenVMS Alpha processor, or shared in a single OpenVMS VAX-M           cluster, a single OpenVMS Alpha Cluster, or shared in a mixed Open-B            VMS VAX/Alpha Cluster.  M           A user that enables a Concurrent Use license is defined as an indi- O           vidual who is logged into an OpenVMS VAX processor, or an OpenVMS Al-nO           pha processor, or an OpenVMS VAXcluster, or an OpenVMS Alpha Cluster,MP           or a mixed OpenVMS VAX/Alpha Cluster and/or is interactively using theH           OpenVMS operating system software by means other than a login.  M           When an OpenVMS VAX SMP System upgrade is performed, the SMP Exten-tM           sion to the OpenVMS AXP Operating System License permits the use ofnM           all existing Distributed Interactive User Licenses on the upgraded             system.p  N           The Operating System Base License provides the right to use only the@           OpenVMS Alpha features of the current version license.      -                                            62a b         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           The OpenVMS VAX Distributed Interactive Use licenses are not supportedN           by the VMS or OpenVMS VAX operating system releases prior to OpenVMS           VAX Version 6.0.  +           OpenVMS Alpha License Informationn  M           There are four types of OpenVMS licenses available on Alpha proces-            sors.E  6         1. Operating System Base License (QL-MT1A*-6*)  '         LMF Product Name: OpenVMS-ALPHA   P         This license grants the right to noninteractive use of the remote batch,K         print, application, and computing services of the OpenVMS Alpha op- M         erating system on a single processor. This license authorizes one di- 7         rect login for system management purposes only.   L         The Operating System Base License is a prerequisite for OpenVMS User1         Licenses and SMP Base Extension Licenses.r  L         The Operating System Base License provides the right to use only the>         OpenVMS Alpha features of the current version license.  L         2. Symmetric Multiprocessing (SMP) Base Extension License (QL-MT1A9-             6*)   '         LMF Product Name: OpenVMS-ALPHAn  K         SMP Base Extensions extend the Operating System Base License to en- M         able symmetric multiprocessing capability on those OpenVMS Alpha sys-eL         tems supporting SMP. SMP Base Extensions are permanently tied to theK         Operating System Base License and may not be separated from the Op- L         erating System Base License if an SMP board is removed from the sys-         tem.  K         SMP Extensions grant the right to use the same version of the oper- O         ating system software as permitted for the corresponding Operating Sys-tG         tem Base License at the time when the SMP Extension is granted.i  1          3. Individual User License (QL-MT2A*-**) #                 (No Longer Offered)p  .           LMF Product Name: OpenVMS-ALPHA-USER  -                                            63p M  B      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    M           This license grants the right to interactive use of the OpenVMS Al-fN           pha operating system, provided the appropriate Operating System BaseP           License has been previously installed on the OpenVMS Alpha system. TheN           Individual User Licenses are available in any quantity desired or as$           an unlimited user license.  N           Individual User Licenses are redesignatable and may be installed andO           used on a single OpenVMS Alpha processor only. They may not be shared.N           in a single OpenVMS Alpha VMScluster environment. An Individual userN           is defined as an user who is logged in an OpenVMS Alpha processor orM           is interactively using the operating system software by means other            than a login.y  N           This license grants the right to use the same version of the operat-O           ing system software as permitted for the corresponding Operating Sys-nO           tem Base License at the time when the Interactive User License is in-P           stalled.  M           4. OpenVMS Alpha Distributed Interactive User License (QL-MT3A*-**)a#                 (No Longer Offered)S  -           LMF Product Name: OpenVMS-ALPHA-ADLf  M           This license grants the right to interactive use of the OpenVMS Al-.N           pha operating system, provided the appropriate Operating System BaseO           License has been previously installed on an Alpha system. The ADL In-sM           teractive User Licenses, are concurrent use licenses and are avail-rM           able in any quantity desired except unlimited. ADL Interactive User M           Licenses are redesignatable and may be installed and used on a sin-aK           gle OpenVMS Alpha processor, or shared in a single OpenVMS Alpha f!           VMScluster environment.6  P         A Distributed Interactive user is defined as an individual who is loggedK         in an OpenVMS Alpha processor or OpenVMS Alpha VMScluster or is in- K         teractively using the operating system software by means other thanx         a login.  L         This license grants the right to use the same version of the operat-M         ing system software as permitted for the corresponding Operating Sys-eM         tem Base License at the time when the ADL Interactive User License isr         installed.  -                                            64     c      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    O           5. OpenVMS Concurrent Use License (For both VAX and Alpha) (QL-MT3A*-               3*)  2           LMF Product Name: OPENVMS-ALPHA-USER-ADL  M           This license grants the right to interactive use of the OpenVMS op-eP           erating system, provided the appropriate OpenVMS Operating System BaseN           License in installed on an OpenVMS VAX processor, and/or on an Open-N           VMS Alpha processor, or on OpenVMS VAX processors if one of the fourO           types of VAX VMS Licenses has been previously installed on a VAX sys-eM           tem. The OpenVMS Concurrent Use licenses are available in any quan- P           tity desired except unlimited. OpenVMS Concurrent Use licenses are mo-O           bile (redesignatable) and may be installed and used on a single Open-oP           VMS VAX or OpenVMS Alpha processor, or shared in a single OpenVMS VAX-M           cluster, a single OpenVMS Alpha Cluster, or shared in a mixed Open-A            VMS VAX/Alpha Cluster.  M           A user that enables a Concurrent Use license is defined as an indi-cO           vidual who is logged into an OpenVMS VAX processor, or an OpenVMS Al- O           pha processor, or an OpenVMS VAXcluster, or an OpenVMS Alpha Cluster,hP           or a mixed OpenVMS VAX/Alpha Cluster and/or is interactively using theH           OpenVMS operating system software by means other than a login.  O           When an Alpha SMP System upgrade is performed, the SMP Base ExtensionfN           to the OpenVMS Alpha Operating System License permits the use of allH           existing ADL Interactive User Licenses on the upgraded system.  -           License Management Facility Support   P           The OpenVMS operating system supports Digital's License Management Fa-           cility (LMF).r  M           If an OpenVMS license is not registered and activated using the Li- N           cense Management Facility, then only a single login is permitted forH           system management purposes through the system console (OPA0:).  O           Several of the VAX VMS and OpenVMS VAX license types are based on thetM           number of concurrent users, called an activity license. Every prod-iM           uct has the option to define an activity as related to the License sP           Management Facility. OpenVMS Interactive User and ADL Interactive User  -                                            65i           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           Licenses define the number of concurrent users that are activity li-M           censes as defined by the LMF. OpenVMS defines activities, sometimesV7           referred to as an OpenVMS "user", as follows:   O           o  Each remote terminal connection is considered an activity. This isrK              true even if users set host to their local nodes (SET HOST 0).   N           o  Each connection from a terminal server is considered an activity.  M           o  A multiple-window session on a workstation is considered one ac- 9              tivity, regardless of the number of windows.o  7           o  A batch job is not considered an activity.   N           o  A remote network connection that is a connection other than a re-E              mote terminal connection, is not considered an activity.   O         For more information about Digital's licensing terms and policies, con-r1         tact your Digital account representative.   !         SOFTWARE PRODUCT SERVICES   M         A variety of service options are available from Digital. For more in-tE         formation, contact your local Digital account representative.            SOFTWARE WARRANTYa  O         Warranty for this software product is provided by Digital with the pur-nN         chase of a license for the product as defined in the Software WarrantyO         Addendum of this SPD and the applicable Digital Standard Terms and Con-t         ditions.  >         SYSTEMS SUPPORTED BY OpenVMS Alpha and VAX Version 6.2           Alpha Systems Supported   M         This section of the SPD lists the Alpha systems that are supported by K         OpenVMS Alpha Version 6.2. Refer to the Systems and Options CatalogpL         and the Network and Communications Buyers Guide for details concern-6         ing Alpha hardware configurations and options.  -                                            66r i  t      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42                Maximum Memory Support  G           OpenVMS supports the following memory for the systems listed:v  M           ___________________________________________________________________ M           Server_______________Memory________________________________________   %           AlphaServer 8200      14 GBr  %           AlphaServer 8400      14 GB   %           AlphaServer 2100       2 GB   %           AlphaServer 2000     640 MBw  %           AlphaServer 1000     512 MBn  %           AlphaServer 400      192 MB   %           AlphaStation 400     192 MBp  %           AlphaStation 250     192 MB   %           AlphaStation 200     192 MB-  %           DEC 7000 Model        14 GBV
           700   %           DEC 4000 Model         2 GBt
           700u  %           DEC 3000 Model       256 MB 
           300V  %           DEC 3000 Model       512 MBl
           700r  %           DEC 3000 Model         1 GBn
           900   %           DEC 2000 Model       256 MB M           300________________________________________________________________o  N           On all other AlphaServer and AlphaStation systems, OpenVMS will sup-6           port the maximum physical memory configured.              EISA Bus Based Systems  $           o  DEC 2000 Models 300/500  -                                            67            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    (           TurboChannel Bus Based Systems  +           o  DEC 3000 Models 300/300L/300LX   %           o  DEC 3000 Models 400/400Sr  *           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 600A             o  DEC 4000 Model 700n             XMI Bus Based SystemsV  #           o  AlphaServer 8400 5/300i             o  DEC 7000 Model 600i              o  DEC 10000 Model 600             PCI Bus Based Systemsh  #           o  AlphaServer 8200 5/300a  -           o  Digital 2100 Server Model A500MP.  -           o  Digital 2100 Server Model A600MPc  #           o  AlphaServer 2100 4/233   #           o  AlphaServer 2000 4/233   #           o  AlphaServer 1000 4/2003  "           o  AlphaServer 400 4/166  #           o  AlphaStation 400 4/266m  #           o  AlphaStation 250 4/233i  -                                            68            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    #           o  AlphaStation 200 4/233   #           o  AlphaStation 200 4/166t  #           o  AlphaStation 200 4/1000  M           The following are the Digital Semiconductor Microprocessor Develop- ;           ment Reference Boards supported by OpenVMS Alpha.   ;           o  Alpha 21064/21064A PCI Reference Board (EB64+)o  .           o  AlphaPC64 Reference Board (APC64)             VAX Systems SupportedB  M           This section of the SPD lists the VAX systems that are supported by O           OpenVMS VAX Version 6.2. Refer to the Systems and Options Catalog and P           the Network and Communications Buyers Guide for details concerning VAX.           hardware configurations and options.             Q-bus Based Systemsy             o  MicroVAX II  8           o  VAXstation II/GPX[1], VAXstation II/QVSS[2]  ;           o  MicroVAX 3200, VAXserver 3200, VAXstation 3200   *           o  MicroVAX 3300, VAXserver 3300  *           o  MicroVAX 3400, VAXserver 3400  M           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  5           o  VAX 4000, Models 100, 200, 300, 500, 600              ____________________  1         [1] Graphics Processing Accelerator (GPX)   )         [2] Q-bus Video Sub System (QVSS)t  -                                            69            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    8           o  VAX 4000, Models 50, 100A, 500A, 600A, 700A  ;           o  VAXserver 4000, Models 200, 300, 400, 500, 600f             NMI Bus Based Systemse  0           o  VAX 8530, VAXserver 8530, VAX 8550,              VAXserver 8550p  %           o  VAX 8700, VAXserver 8700r  4           o  VAX 8800, VAX 8810, VAX 8820, VAX 8830,              VAX 8840   M           o  VAXserver 8800, VAXserver 8810, VAXserver 8820, VAXserver 8830, s              VAXserver 8840c             XMI Bus Based Systemso  7           o  VAX 6000 Series, Models 210, 220, 230, 240i  <           o  VAX 6000 Series, Models 310, 320, 330, 340, 360  A           o  VAX 6000 Series, Models 410, 420, 430, 440, 450, 460   A           o  VAX 6000 Series, Models 510, 520, 530, 540, 550, 560   A           o  VAX 6000 Series, Models 610, 620, 630, 640, 650, 660a  J           o  VAXserver 6000, Models 210, 220, 310, 320, 410, 420, 510, 520  0           o  VAX 8530, VAX 8550, VAXserver 8530,              VAXserver 8550   %           o  VAX 8700, VAXserver 8700p  4           o  VAX 8800, VAX 8810, VAX 8820, VAX 8830,              VAX 8840i  M           o  VAXserver 8800, VAXserver 8810, VAXserver 8820, VAXserver 8830,                VAXserver 8840   :           o  VAX 7000, Models 610, 620, 630, 640, 650, 660  -                                            70A           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    ;           o  VAX 10000, Models 610, 620, 630, 640, 650, 660s  !           VAXBI Bus Based Systemsl  0           o  VAX 8200, VAX 8250, VAXserver 8200,              VAXserver 8250,  0           o  VAX 8300, VAX 8350, VAXserver 8300,              VAXserver 8350n             SBI Bus Based Systemsn  #           o  VAX 11/780, VAX 11/785S  0           o  VAX 8600, VAX 8650, VAXserver 8600,              VAXserver 8650p             CMI Bus Based Systems              o  VAX 11/750   .           Special System Specific Internal Bus             o  VAX 11/730   ,           o  MicroVAX 2000, VAXstation 2000,!              VAXstation 2000/GPX, #              VAXstation 2000/MFB[3]s  7           o  VAXft 3000, Models 110, 310, 410, 610, 612l  8           o  MicroVAX 3100, Models 10, 10E, 20, 20E, 30,              40, 80, 85, 90, 95   4           o  VAXserver 3100, Models 10, 10E, 20, 20E  7           o  VAXstation 3100, Models 30, 38, 40, 48, 76S  3           o  VAXstation 3100/GPX, Models 38, 48, 76r  6           o  VAXstation 3100/SPX[4], Models 38, 48, 76             ____________________  )         [3] Monochrome Frame Buffer (MFB)o  C         [4] 2D Scanline Processor Accelerator Graphics System (SPX)t  -                                            71  r  n      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    +           o  VAXstation 4000, Models 60, 90m              o  VAXstation 4000-VLC  8           o  VAX 9000, Models 110, 110VP[5], 210, 210VP,              310, 310VP   5           o  VAX 9000, Models 320, 320VP, 330, 330VP,               340, 340VP   5           o  VAX 9000, Models 410, 410VP, 420, 420VP,a              430, 430VP5  (           o  VAX 9000, Models 440, 440VP             System Restrictionse  J           The following list describes version specific restrictions. The I           DECwindows Motif environment is not supported on these systems.e  )           MicroVAX I/VAXstation I Systemst  M           The final version of OpenVMS VAX that supports these systems is VMS            V5.1-1.              VAX-11/725  7           VMS V5.1 was the final version to support theh           VAX-11/725.i             VAX-11/730 Systeme  O           The VAX-11/730 system supports additional memory to a maximum of 5 MBlO           for systems configured with R80/RL02 or dual RL02 disks. Other VAX-11nP           /730 system configurations support a maximum of 3 MB of memory for theP           VAX-11/730 only. To run OpenVMS VAX Version 6.1, 4 MB of memory is re-           quired.o             ____________________  !         [5] Vector Processor (VP)r  -                                            72r o  h      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    P           OpenVMS VAX 6.2 is planned to be the final version to support the fol-           lowing systems:n           VAX-11/730           VAX-11/750           VAX-11/751           VAX-11/780           VAX-11/782           VAX-11/785           MicroVAX I           VAXstation I                                                              -                                            73            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42           Appendix A  M       This appendix describes Digital Equipment Corporation terminals, disks,fJ       tapes, controllers, graphics, and network options. Some restrictions5       for specific devices are listed, if applicable.   H      Digital reserves the right to change the number and type of devicesH      supported by OpenVMS Alpha, OpenVMS VAX, DECnet for OpenVMS Alpha, O      DECnet-VAX, DECnet/OSI, and OpenVMS Cluster Software. The minimum hardwarenM      requirements for future versions and updates of these software products gO      may be different from current hardware requirements. For configuration de-yH      tails about Alpha or VAX hardware, refer to the Systems and Options=      Catalog and the Network and Communications Buyers Guide.   J      Refer to the following SPDs for detailed product information: DECnet I      for OpenVMS (SPD 48.48.xx), DECnet/OSI (SPD 50.45.xx, 25.03.xx) and a-      OpenVMS Cluster Software (SPD 29.78.xx).   ,       Terminals and Terminal Line Interfaces  I       To prevent input from overflowing a buffer, terminals use the ASCIIeK       control characters DC1 and DC3 for synchronization as defined by Dig- K       ital's DEC STD 111, Revision A. VXT windowing terminals support stan-iI       dard ANSI applications and X windows using the LAT transport proto-h
       col.  I       The following table lists the terminals that are supported by Open-s       VMS Alpha:  5           VT200 series   VT300  series   VT400 seriesa  (           VT500 series   VXT 2000 series  J        The following table lists the terminals that are supported by Open-        VMS VAX:U      -                                            74r f  d      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      1           VT52           VT100-         LA-series                           seriesd  -           VT300-         VT1000-        LQP02            series         seriesl  %           VT200-series   VT500-series     N         Terminals on Professional 350, Rainbow 100, and DECmate II systems em-         ulate VT100 terminals.  L         Only limited support is available for the VT52. The VT131, when run-P         ning an application, operates in block mode. When interacting with Open-N         VMS VAX and associated utilities, the VT131 operates only in VT100 (or0         interactive) mode and not in block mode.  O         Note: The VT1000 is a monochrome windowing terminal that supports stan-SL         dard ANSI applications and "X" windows. The transport protocols sup-M         ported are LAT for VMS. The product supports 15-inch and 19-inch mon-o         itors.  
         Disksa  N         The first column lists the disk drive. The second column is a descrip-M         tion of the device. The third column lists the bus the device is sup-rP         ported on. The fourth column lists the minimum required version of Open-M         VMS Alpha that supports these devices.The fifth column lists the min-2O         imum required version of OpenVMS VAX that supports these devices. ("NS"3#         stands for "Not Supported")M                    -                                            75a           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________O2           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version__________   =           EF51R    107 MB solid      DSSI    NS         5.5-2s                    state  =           EF52R    205 MB solid      DSSI    NS         5.5-2                     state  =           EF53     267 MB solid      DSSI    NS         5.5-2(                    state  /           ESE-     120 MB solid      SDI     NSM           20       state  =           ESE-     120 MB solid      SDI     1.0        5.5-2s           52       state  =           ESE-     600 MB solid      SDI     1.5        5.5-2            56       state  =           ESE-     960 MB solid      SDI     1.5        5.5-2            58       state  =           EZ51R    100 MB solid      SCSI    1.5        5.5-2s                    state  =           EZ54R    467 MB solid      SCSI    1.5        5.5-2V                    state  =           EZ58R    855 MB solid      SCSI    1.5        5.5-2w                    state  ;           RA60     205 MB remov-     SDI     NS         6.1e                    ablef  ;           RA70     280 MB fixed      SDI     NS         6.1t  =           RA71     700 MB fixed      SDI     NS         5.4-2s                    disk   =           RA72     1 GB fixed        SDI     1.0        5.4-2                     disks  =           RA73     2 GB fixed        SDI     1.0        5.5-2r                    diskM  -                                            76h i         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________ 2           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version__________c  ;           RA80[1]  128 MB fixed      SDI     NS         6.1c                    diskL  ;           RA81     456 MB fixed      SDI     NS         6.1e                    diskr  ;           RA82     622 MB fixed      SDI     NS         6.1                     diskt  ;           RA90     1.2 GB fixed      SDI     1.0        6.1                     disku  ;           RA92     1.5 GB fixed      SDI     1.0        6.1s                    diskp  ;           RC25[3]  2 disks each      Q-bus   NS         6.1a                    26 MB (1                     fixed and                    1 removable)a                    disk drive                     with shared                    spindle  /           RD32[3]  VAX 42 MB         Q-bus   NSn                    fixed diskv  ;           RD51[3]  10 MB fixed       Q-bus   NS         6.1                     disk   ;           RD52[3]  31 MB fixed       Q-bus   NS         6.1                     disko  /           RD53[3]  71 MB fixed       Q-bus   NS                     disks  /           RD54     159 MB fixed      Q-bus   NSe                    disk   ;           RF30     150 MB fixed      DSSI    NS         6.1D                    diska  0           RF31     381 MB fixed      DSSI    1.5                    disk   -                                            77t f  r      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________ 2           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version__________n  =           RF31F    200 MB fixed      DSSI    NS         5.4-2i                    diskr  =           RF31T    381 MB fixed      DSSI    1.5        5.5-2e                    diskn  ;           RF35     800 MB fixed      DSSI    1.0        5.5n                    diskh  ;           RF36     1.6 GB fixed      DSSI    6.1        6.0                     disk   ;           RF71     400 MB fixed      DSSI    1.5        6.1s                    disk   =           RF72     1 GB fixed        DSSI    1.5        5.5-2                     disk   ;           RF74     3.5 GB fixed      DSSI    6.1        6.0n                    diska  /           RK06[3]  14 MB remov-      UNIBUS  NSo                    able disk  /           RK07[3]  28 MB remov-      UNIBUS  NSt                    able disk  /           RL02[3]  10 MB remov-      UNIBUS  NS_                    able disk  /           RM03+    67 MB remov-      M-      NS_(                    able disk         bus  /           RM05     256 MB remov-     M-      NS (                    able disk         bus  /           RM80[1]  124 MB fixed      M-      NSh(                    disk              bus  /           R80[4]   124 MB fixed              NS4!                    disk drive fora!                    VAX-11/725 andl                    VAX-11/730   -                                            780           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________02           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version___________  /           RRD40[3] 600 MB read-      Q-bus   NS (                    only optical      and)                    disk drive        SCSI   =           RRD42    600 MB read-      SCSI    1.0        5.4-2I                    only optical                     disk drive   =           RRD43    680 MB read-      SCSI    6.1        5.5-2                     only opticalV                    disk drive0  0           RRD44    680 MB read-      SCSI    6.1                    only optical0                    disk driveC  /           RRD50[3] 600 MB read-      Q-bus   NSe                    only opticalD                    disk drive   /           RP05[4]  88 MB re-         M-      NSD(                    movable disk      bus                    drive  /           RP06     176 MB re-        M-      NSD(                    movable disk      bus                    drive  /           RP07     516 MB fixed      M-      NS8(                    disk drive        bus  0           RWZ01    594 MB optical    SCSI    1.0!                    removable disk                     drive  /           RX02[3]  512 KB            UNIBUS  NS.                    diskette   /           RX23     1.47 MB           SCSI    NS0                    diskettea  -                                            790 /  3      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________62           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version__________/  4           RX26     2.8 MB            I82077  1.5-1H1!                    diskette drive   ;           RX26     2.8 MB            SCSI    1.0        5.5r!                    diskette drivee  /           RX33[3]  1.2 MB            Q-bus   NS                     diskettee                    drive. Re- !                    quires minimum)                    RQDX3 mi-                    crocode ofn                    V3.0   /           RX50[3]  400 KB            Q-bus   NSA                    diskettey  /           RV20[3]  2 GB Write        Q-bus,  NSr,                    Once Read Many    UNIBUS,*                    optical disk      VAXBI                    driveM           ___________________________________________________________________o2           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version__________A  /           RV64[3]  2 GB Write        Q-bus,  NSe,                    Once Read Many    UNIBUS,*                    optical disk      VAXBI                    sub-system   /           RZ22[3]  52 MB fixed       SCSI    NS                     disks  /           RZ23[4]  104 MB fixed      SCSI    NS                     disk4  =           RZ23L[1] 121 MB fixed      SCSI    1.5        5.4-1_                    diski  -                                            80-    e      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________ 2           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version__________   ;           RZ24     209 MB fixed      SCSI    1.5        6.18                    disk   =           RZ24L    245 MB fixed      SCSI    1.0        5.4-3                     disk8  =           RZ25     425 MB fixed      SCSI    1.0        5.4-3V                    disk8  =           RZ25L    500 MB fixed      SCSI    1.5        5.5-24                    diska  ;           RZ25M    540 MB fixed      SCSI    6.1        6.12                    diskV  =           RZ26     1.05 GB fixed     SCSI    1.0        5.5-2X                    disk   ;           RZ26B    1.05 GB fixed     SCSI    1.5        6.0s                    disk   =           RZ26L    1.0 GB fixed      SCSI    1.5        5.5-26                    diskV  =           RZ28     2.1 GB fixed      SCSI    1.5        5.5-2                     disk8  ;           RZ28B    2.1 GB fixed      SCSI    1.5        6.0                     disk0  :           RZ29B    4.4 GB fixed      SCSI    6.1        NS                    disk   =           RZ35     852 MB fixed      SCSI    NS         5.4-3v                    diskV  ;           RZ55     332 MB fixed      SCSI    1.0        6.16                    disk   ;           RZ56     665 MB fixed      SCSI    1.0        6.1p                    diskr  =           RZ57[2]  1 GB fixed        SCSI    1.5        5.4-30                    disk4  -                                            81l           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________ 2           Disk                               AlphaM           Drive____Description_______Bus_____Version____VAX_Version__________   ;           RZ58     1.35 GB fixed     SCSI    1.0        5.5                     disk   ;           RZ73     2 GB fixed        SCSI    1.0        6.0/M           _________disk______________________________________________________0  M           Disk Options Supported by Digital's Services Enterprise Integration "           Center (SEIC) - VAX only  /           RF30-RA    150 MB removable    (DSSI)                       disk9  /           RF31-RA    381 MB removable    (DSSI)2                      diskt  /           RF71-RA    400 MB removable    (DSSI)                       diske  /           RF71-RA    1 GB removable      (DSSI)4                      disk   8           RWZ01      594 MB optical      (SCSI) (V5.4-3)#                      removable diskn  
         Tapese  O         The first column lists the device name. The second column is a descrip- M         tion of the device. The third column lists the bus the device is sup-5P         ported on. The fourth column lists the minimum required version of Open-L         VMS Alpha and the fifth column lists the minimum required version ofK         OpenVMS VAX that supports these devices. ("NS" stands for "Not Sup-          ported")             ____________________P       [1] Specific tailoring is required in order to use this device as an Open-M           VMS Alpha or VAX system disk with the DECwindows Motif environment. -       [2] Minimum revision firmware is V6000.h>       [3] Device cannot be used as an OpenVMS VAX system disk.M       [4] Device cannot be used as an OpenVMS VAX system disk with DECwindowsi           Motif environment.  -                                            821           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________s2                                              AlphaM           Tape____Description_______Bus______Version____VAX_Version__________1  0           TA78    1600/6250 BPI,    STI      1.0                   STI TU78  /           TA79    STI TU79          STI      NS   0           TA81    145 MB tape       STI      1.0                   drive_  0           TA90    1.2 GB tape       STI      1.0                   cartridge                    subsystem.                    (5-inch 200 MB                   cartridge)  /           TA90E   1.2 GB tape       STI      NSa                   cartridget                   subsystem.                   Compacts                   data records                   automatically   =           TA91    High perfor-      STI      NS         5.4-2                    mance tape                   drive   /           TE16    9-track mag-      M-BUS    NS                    netic tape                   drive   =           TF70    290 MB TK70       DSSI     NS         5.4-25                    tape cartridge                   drivee  =           TF85    2.6 GB stream-    DSSI     6.1        5.5-2c                   ing tape                   cartridgeo                   drivev  -                                            83r r         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________S2                                              AlphaM           Tape____Description_______Bus______Version____VAX_Version__________b  =           TF857   18.2 GB tape      DSSI     6.1        5.5-2                    cartridgeo                   loader  ;           TF86    6.0 GB DLT        DSSI     6.1        6.1i                    tape cartridge  ;           TF867   42 GB DLT tape    DSSI     6.1        6.1e                   loader  /           TK50    95 MB, 5 1/4-     Q-bus    NSa'                   inch streaming    and8(                   tape cartridge    SCSI                   drivep  /           TK70    296 MB, 5 1/4-    Q-bus    NSs                    inch streaming                    tape cartridge                   drive   0           TKZ09   5.0 GB, 8mm       SCSI     1.5                   tape drive  0           TKZ60   200 MB, 3480      SCSI     1.0                   tape drive                   (no compres-                   sion)s  0           TLZ04   1.2 GB, 4mm,      SCSI     1.0                    DAT tape drive  ;           TLZ06   4 GB, 4mm, DAT    SCSI     1.0        6.1T                   tape drive  ;           TLZ07   8 GB, 4mm, DAT    SCSI     6.1        6.1                    tape drive  /           TLZ08   5.25-inch, 2      SCSI     NSr                   GB, 8mm tape                   drive   -                                            84r           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________ 2                                              AlphaM           Tape____Description_______Bus______Version____VAX_Version__________s  0           TLZ6L   4 GB, 3.5-        SCSI     6.1                   inch, 4mm DATo                   tape loadereM           ___________________________________________________________________s2                                              AlphaM           Tape____Description_______Bus______Version____VAX_Version__________   ;           TLZ7L   8 GB, 3.5-        SCSI     6.1        6.1n                   inch, 4mm DAT-                   tape loaderS  /           TS05    9-track mag-      Q-bus    NS                    netic tape                   driveu  /           TS11    9-track mag-      UNIBUS   NSc                   netic tape                   drives  0           TSZ05   1600 bits/in      SCSI     1.5                   tape drive  0           TSZ07   1600/6250 BPI     SCSI     1.0                   tape drive  /           TU77    9-track mag-      M-BUS    NSe                   netic tape                   drive3  /           TU78    9-track mag-      M-BUS    NS                    netic tape                   drive   /           TU80    9-track mag-      UNIBUS   NSr                   netic tape                   drive_  /           TU81    9-track mag-      UNIBUS   NS_                   netic tape                   drive   -                                            85s _  r      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42  M           ___________________________________________________________________S2                                              AlphaM           Tape____Description_______Bus______Version____VAX_Version__________   /           TU81-   Streaming 9-      Q-bus,   NSI+           Plus    track magnetic    UNIBUS, )                   tape drive        VAXBI   0           TZ30    95 MB, half-      SCSI     1.0                   height DLT                   tape drive  0           TZ85    2.6 GB DLT        SCSI     1.0                   tape drive  0           TZ857   18 GB, DLT        SCSI     1.0                   tape loader   0           TZ86    6.0 GB, DLT       SCSI     1.5                   tape drive  0           TZ867   42 GB, DLT        SCSI     1.5                   tape loader   ;           TZ87    20 GB, DLT        SCSI     6.1        6.1                    tape drive  ;           TZ875   100 GB, DLT       SCSI     6.1        6.1A                   tape loader   ;           TZ877   140 GB, DLT       SCSI     6.1        6.1                    tape loader   0           TZK08   2.2 GB 8mm,       SCSI     6.1                   tape drive  0           TZK10   320/525 MB,       SCSI     1.0                    QIC tape drive  0           TZK11   2.0 GB, QIC       SCSI     6.1M           ________tape_drive_________________________________________________r             Controllers.  -                                            86_ _  _      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      G           HSC40         Hierarchical storage controller for MSCP served_K                         disks and TMSCP served tapes. (HSC software must be J                         at minimum Version 8.1.) Refer to SPD 42.81.xx for1                         supported configurations.   G           HSC50         Hierarchical storage controller for MSCP served K                         disks and TMSCP served tapes. (HSC software must bedJ                         at minimum Version 4.1.) Refer to SPD 32.96.xx for1                         supported configurations.c  G           HSC60         Hierarchical storage controller for MSCP served K                         disks and TMSCP served tapes. (HSC software must bevJ                         at minimum Version 8.1.) Refer to SPD 42.81.xx for1                         supported configurations.   G           HSC65         Hierarchical storage controller for MSCP served K                         disks and TMSCP served tapes. (HSC software must besJ                         at minimum Version 8.1.) Refer to SPD 42.81.xx for1                         supported configurations.   G           HSC70         Hierarchical storage controller for MSCP served K                         disks and TMSCP served tapes. (HSC software must be J                         at minimum Version 8.1.) Refer to SPD 42.81.xx for1                         supported configurations.   G           HSC90         Hierarchical storage controller for MSCP servedaK                         disks and TMSCP served tapes. (HSC software must be_J                         at minimum Version 8.1.) Refer to SPD 42.81.xx for1                         supported configurations.V  G           HSC95         Hierarchical storage controller for MSCP servedSK                         disks and TMSCP served tapes. (HSC software must be J                         at minimum Version 8.1.) Refer to SPD 42.81.xx for1                         supported configurations.   C           HSD05         DSSI to SCSI-2 FSE StorageWorks bus adapter B                         (Firmware must be at minimum Version X36.)  C           HSD10         DSSI to SCSI-2 FSE StorageWorks bus adapter   -                                            87  .         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      H           HSD30         DSSI based StorageWorks controller that supportsJ                         up to 3 SCSI-2 FSE ports. (HSD firmware must be at.                         minimum Version V15D.)  H           HSJ30         DSSI based StorageWorks controller that supportsJ                         up to 3 SCSI-2 FSE ports. (HSJ firmware must be at.                         minimum Version V15J.)  H           HSJ40         DSSI based StorageWorks controller that supportsJ                         up to 6 SCSI-2 FSE ports. (HSJ firmware must be at.                         minimum Version V15J.)  K           HSZ40-BX      Fast Wide Differential SCSI based StorageWorks con-lL                         troller that supports up to 6 SCSI-2 FSE ports. (HSZC                         firmware must be at minimum Version V2.5Z.)p  J           KDM70         Mass-storage controller for XMI systems with eight"                         SDI ports.  I           KFESA         Mass-storage controller for EISA systems with onen/                         DSSI port. (Alpha only)   I           KFESB         Mass-storage controller for EISA systems with onep/                         DSSI port. (Alpha only)   H           KFMSB         Mass-storage controller for XMI systems with two0                         DSSI ports. (Alpha only)  K           KZESC-AA      Backplane RAID controller for EISA systems with one 5                         SCSI-2 FSE port. (Alpha only)d  G           KZESC-BA      Backplane RAID controller for EISA systems with <                         three SCSI-2 FSE ports. (Alpha only)  H           KZMSA         Mass-storage controller for XMI systems with twoI                         SCSI ports. (Limited SCSI-2 support - Alpha only)   L           KZPSA         Mass-storage adapter for PCI systems with one SCSI-2.                         FWD port. (Alpha only)  J           KZPSC-AA      Backplane RAID controller for PCI systems with one5                         SCSI-2 FSE port. (Alpha only)   L           KZPSC-BA      Backplane RAID controller for PCI systems with three6                         SCSI-2 FSE ports. (Alpha only)  -                                            88I    .      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      L           KZPAA         Mass-storage adapter for PCI systems with one SCSI-2.                         FSE port. (Alpha only)  J           KZTSA         Mass-storage adapter for TURBOchannel systems with9                         one SCSI-2 FWD port. (Alpha only)   I           PB2HA-SA      Mass-storage controller for EISA systems with one_H                         SCSI port. (Limited SCSI-2 support - Alpha only)  J           PMAZB         Mass-storage adapter for TURBOchannel systems with:                         two SCSI-2 FSE ports. (Alpha only)  J           PMAZC         Mass-storage adapter for TURBOchannel systems with?                         two fast SCSI-2 FSE ports. (Alpha only)               Controllers - VAX only  K           HSZ10         SCSI based StorageWorks controller that supports up *                         to 2 SCSI-2 ports.  L           IDC           Integrated Disk Controller for VAX-11/725 and VAX-11%                         /730 systems.   J           IDTC          Integral Disk and Tape Controller for VAX 8600 and)                         VAX 8650 systems._  L           LPA11-K       Microprocessor controller for laboratory acquisitionI                         I/O devices, accommodating up to two AD11-Ks, onesJ                         AA11-K, one KW11-K, two AM11-Ks, and five DR11-Ks.L                         One LPA11-K controller is supported per UNIBUS and a@                         maximum of two are supported per system.  G           KDA50         Q-bus MSCP disk controller. The KDA50 disk con- L                         troller supports up to four of the following drives:9                         RA60, RA70, RA80, RA81, and RA82.s  G           KDB50         VAXBI MSCP disk controller. The KDB50 disk con- L                         troller supports up to four of the following drives:3                         RA60, RA80, RA81, and RA82._  H           KFMSA         Mass-storage controller for XMI systems with two#                         DSSI ports._  -                                            89  4         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      I           KFQSA         Q-bus to DSSI bus adapter. This adapter allows up K                         to seven DSSI storage devices to attach to the DSSI G                         bus. (Six DSSI storage devices are allowed in a42                         Multi-Host Configuration.)  H           KLESI         Q-bus, UNIBUS, and VAXBI tape controller for the1                         TU81-Plus, RV20, or RC25.-  I           KRQ50         Q-bus controller for the RRD40/RRD50 compact disc1                         reader.   L           KZQSA         Q-bus to SCSI bus adapter. This adapter allows up toI                         7 SCSI storage devices to attach to the SCSI bus.   I           KFDDA         VAX 4000 model 100 DSSI bus adapter. This adapterSL                         allows up to 7 DSSI storage devices to attach to theL                         DSSI bus. (Six DSSI storage devices are allowed in a2                         Multi-Host Configuration.)  I           KFDDB         VAX 4000 model 500/600/700 DSSI bus adapter. This J                         adapter allows up to 7 DSSI storage devices to at-K                         tach to the DSSI bus. (Six DSSI storage devices are ?                         allowed in a Multi-Host Configuration.)   J           LP11          UNIBUS parallel high-speed line printer controller.                         for the LPxx printers.  J           LPV11         Q-bus parallel high-speed line printer controller.  D           RK711         UNIBUS disk controller for RK07 disk drives.  G           RL211         UNIBUS disk controller for the RL02 disk drive.   I           RQDXx         Q-bus disk controller for MicroVAX and VAXstation G                         systems. There is an RQDX1, RQDX2, and an RQDX3 I                         controller. The RQDXx disk controller supports as_H                         many as four disk units, with each RX50 disketteK                         drive counting as two units. Due to controller lim- G                         itations, the system supports a maximum of four3G                         devices; the number of RD/RX devices the systemRI                         supports depends on the enclosure. The RQDX3 diskFH                         controller is required for the RD54 and the RX33                         drives.   -                                            90d n         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      K           RX211         UNIBUS diskette controller for two RX02 drives. OnecJ                         RX211 diskette controller is supported per system.  G           RUX50         UNIBUS diskette controller for RX50 drives. OnerJ                         RUX50 diskette controller is supported per system.  J           TM03          MASSBUS tape controller for the TE16 and TU77 mag-*                         netic tape drives.  F           TM32          BI-bus 9-track tape controller only with large'                         record support.   J           TM78          MASSBUS tape controller for the TU78 magnetic tape                         drive.  I           TQK50         Q-bus tape controller for the TK50 cartridge tapei                         drive.  I           TQK70         Q-bus tape controller for the TK70 cartridge tapen                         drive.  I           TS11          UNIBUS tape controller for the TS11 magnetic tape_                         drive.  J           TBK50         BI-bus tape controller for the TK50 cartridge tape                         drive.  J           TBK50         BI-bus tape controller for the TK50 cartridge tape                         drive.  J           TBK70         BI-bus tape controller for the TK70 cartridge tape                         drive.  J           TUK50         UNIBUS tape controller for the TK50 cartridge tapeI                         drive. One TUK50 tape controller is supported per                          system.g  I           UDA50         UNIBUS MSCP disk controller. The UDA50 controllertK                         must have a minimum microcode version of REV 3. The J                         UDA50 controller supports up to 4 of the following@                         disk drives: RA60, RA80, RA81, and RA82.  6           Asynchronous Terminal Controllers - VAX only  -                                            91i a         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      K           CXA16      16-line serial terminal multiplexer (DEC-423), maximum50                      baud rate supported: 38400./                      (No modem control) (Q-bus)t  I           CXB16      16-line serial terminal multiplexer (RS422), maximum 0                      baud rate supported: 38400./                      (No modem control) (Q-bus)   H           CXY08      8-line serial terminal multiplexer (RS232), maximum0                      baud rate supported: 19200.1                      (Full modem control) (Q-bus)V  H           DHB32      16-line asynchronous terminal controller for VAXBI,@                      maximum baud rate supported: 19200. (VAXBI)  H           DHF11      32-line asynchronous terminal controller (DEC 423),K                      maximum baud rate supported: 19200. (No modem control)I                      (Q-bus)  K           DHT32      8-line asynchronous terminal controller (DEC 423). (No 3                      modem control) (MicroVAX 2000)e  J           DHQ11      8-line asynchronous terminal controller (EIA RS-232-CL                      or RS-423-A), maximum baud rate supported: 19200. (Full+                      modem control) (Q-bus)   I           DHU11      16-line asynchronous terminal controller (RS-232-C), F                      maximum baud rates supported: OpenVMS VAX, 19200;D                      DECnet-VAX, 9600. (Full modem control) (UNIBUS)  I           DHV11      8-line asynchronous terminal controller (EIA RS-232- J                      C or RS-423-A), maximum baud rates supported: OpenVMSG                      VAX, 19200; DECnet-VAX, 9600. (Full modem control)                       (Q-bus)  J           DMB32      8-line asynchronous terminal controller, maximum baudK                      rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. 1                      (Full modem control) (VAXBI)n  J           DMF32      8-line asynchronous terminal controller, maximum baudK                      rates supported: OpenVMS VAX, 19200; DECnet-VAX, 9600. C                      (Full modem control on first 2 lines) (UNIBUS)_  -                                            92  L         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      J           DMZ32      24-line asynchronous terminal controller (EIA RS-232-J                      C or RS-423-A), maximum baud rates supported: OpenVMSK                      VAX, 19200; DECnet-VAX, 9600. (Modem support dependent /                      on configuration) (UNIBUS)   I           DZ11       8-line asynchronous terminal controller (EIA RS-232- G                      C or RS-423-A), maximum baud rate supported: 9600.e5                      (Partial modem control) (UNIBUS)   I           DZ32       8-line asynchronous terminal controller (EIA RS-232-sG                      C or RS-423-A), maximum baud rate supported: 9600.a5                      (Partial modem control) (UNIBUS)   I           DZQ11      4-line asynchronous terminal controller (EIA RS-232-UI                      C or RS-423-A), maximum baud rate supported: OpenVMS J                      VAX, 19200; DECnet-VAX, 9600. (Partial modem control)                      (Q-bus)  I           DZV11      4-line asynchronous terminal controller (EIA RS-232- I                      C or RS-423-A), maximum baud rate supported: OpenVMS J                      VAX, 19200; DECnet-VAX, 9600. (Partial modem control)                      (Q-bus)  ,           Synchronous Controllers - VAX only  P           The VAX Wide Area Network Device Drivers software product contains theP           synchronous device drivers and is required when using synchronous com-I           munication options. Refer to SPD 29.64.xx for more information.o  B           DMB32      Point-to-point synchronous interface. (VAXBI)  G           DMC11      High-speed local point-to-point synchronous inter- J                      face; retired device, no longer offered as an option.                      (UNIBUS)   H           DMF32      Point-to-point or multipoint synchronous interface.                      (UNIBUS)   H           DMP11      Point-to-point or multipoint synchronous interface;I                      (UNIBUS) retired device, no longer offered as an op-e                      tion.  -                                            93l e         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      J           DMR11      Remote point-to-point synchronous interface; (UNIBUS)$                      replaces DMC11.  H           DMV11      Point-to-point or multipoint synchronous interface.                      (Q-bus)  L           DPV11      Synchronous, 1 line, half or full-duplex point-to-pointJ                      communication interface supporting DDCMP, HDLC, SDLC,)                      or BISYNC protocols.   F           DSB32      Two-line, multiple protocol, synchronous adapter.                      (VAXBI)  I           DSH32      One-line synchronous (full modem control) and 8-lineMH                      asynchronous (no modem control) communications con-K                      troller for the MicroVAX 2000. DEC423 devices are sup- L                      ported. Maximum baud rates supported: OpenVMS VAX, 19.2H                      KBPS (kilobits/second); 9.6 KBPS for MicroVAX 2000,                      etc.o  H           DST32      Synchronous single-line support for DDCMP up to 9.6L                      KBPS, full duplex for MicroVAX 2000 systems. Concurrent9                      use with the DHT32 is not supported.4  L           DSV11      Synchronous, 2-line, half or full-duplex point-to-pointK                      communication interface supporting DDCMP (1 or 2 lines $                      up to 64 KBPS).  H           DSF32      DEC WANcontroller 620 - Two-line synchronous commu-G                      nications controller designed specifically for theeK                      VAXft 3000 processors, supporting DDCMP. DDCMP is sup- K                      ported at speeds up to 64 KBPS per line for a two-lines                      operation.              Graphics Options  <           PMAG          A 24-plane graphics adapter upgrade.  :           PMAGB         A multiscreen graphics adapter forK                         TURBOchannel systems to connect multiple 8/24-planed4                         color or grayscale monitors.  -                                            94f           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      :           PMAGC         A multiscreen graphics adapter forJ                         TURBOchannel systems to connect multiple ZLX 8/24-:                         plane color or grayscale monitors.  :           PMAGD         A multiscreen graphics adapter forL                         TURBOchannel systems to connect multiple ZLX 8-plane4                         color or grayscale monitors.  I           PBXGA-AA      A multiscreen graphics adapter for PCI systems torH                         connect ZLX 8-plane color or grayscale monitors.  H           PBXGA-BA      Multiscreen graphics adapters for PCI systems toI           /CA           connect ZLX 24-plane color or grayscale monitors.t  D           PB2GA-AA      Compaq QVision VGA adapter for EISA systems.  C           PB2GA-CA      Compaq QVision VGA adapter for PCI systems.V  I           PB2GA-FA      ATI Mack-64 CX (2mbDRAM) VGA adapter for PCI sys-d                         tems.u  5           PCXBV-DE      A 15" color quadmode monitor. 
           /DGu  ,           PCXAV-FC      A 19" color monitor.
           /FD              LAN Optionsb  H           DEFAA         A high-performance network adapter that connectsL                         FUTUREBUS+ systems to ANSI FDDI local area networks.  H           DEFEA         A high-performance network adapter that connectsF                         EISA systems to ANSI FDDI local area networks.  L           DEFPA         A high-performance network adapter that connects PCIA                         systems to ANSI FDDI local area networks.   H           DEFTA         A high-performance network adapter that connectsI                         TURBOchannel systems to ANSI FDDI local area net-                          works.  H           DEFZA         A high-performance network adapter that connectsI                         TURBOchannel systems to ANSI FDDI local area net-n2                         works. (DMA receive only.)  -                                            95     A      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      L           DEMFA         A high-performance network adapter that connects XMIA                         systems to ANSI FDDI local area networks.D  L           DETRA         A network adapter that connects the TURBOchannel bus;                         to a Token Ring local area network.r  L           DEMNA         A high-performance network adapter that connects XMII                         systems to both the Ethernet and IEEE 802.3 localm&                         area networks.  7           DE422         A network adapter that connects H                         EISA systems to both the Ethernet and IEEE 802.3,                         local area networks.  H           DE425         A high-performance network adapter that connectsH                         EISA systems to both the Ethernet and IEEE 802.3,                         local area networks.  H           DE434         A high-performance network adapter that connectsG                         PCI systems to both the Ethernet and IEEE 802.3M,                         local area networks.  7           DE435         A network adapter that connectsaG                         PCI systems to both the Ethernet and IEEE 802.3 ,                         local area networks.  H           DE436         A high-performance network adapter that connectsL                         QUAD PCI systems to both the Ethernet and IEEE 802.3,                         local area networks.  I           DW300         A network adapter that connects the EISA bus to a 6                         Token Ring local area network.  7           PB2CA-AA      A network adapter that connects)H                         EISA systems to both the Ethernet and IEEE 802.3,                         local area networks.  7           PMAD          A network adapter that connectsyJ                         TURBOchannel systems to both the Ethernet and IEEE2                         802.3 local area networks.              LAN Options - VAX only  3           DEUNA      Ethernet to UNIBUS controller.   -                                            96  n  r      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      H           DELUA      Ethernet to UNIBUS controller. The minimum revision*                      level required is F1.  @           DEBNA      Ethernet to VAXBI communication controller.  @           DEBNI      Ethernet to VAXBI communication controller.  I           DEMNA      The DEMNA is a high performance network adapter that G                      connects XMI systems to both the Ethernet and IEEEu/                      802.3 local area networks.   3           DESVA      Ethernet controller interface.f  G           DEQNA      Ethernet controller to Q-bus. The minimum revisionsH                      level required is K3. All systems utilizing a DEQNAL                      must operate with software data checking enabled. SinceJ                      AUTOGEN will automatically set the correct parameter,G                      no system management intervention is required. Not H                      supported by VAXcluster software. Not supported forK                      any interfaces except for access using QIO or ALTSTART'                       interfaces.  J           DELQA      Ethernet controller to Q-bus. This is the replacementJ                      for DEQNA. The minimum revision level required is C3.  K           DESQA      Ethernet controller to Q-bus for S-BOX configurations.   -           DEFQA      FDDI to Q-bus controller   4           DEFZA      FDDI to TURBOchannel controller  4           DEFTA      FDDI to TURBOchannel controller  I           KFE52      DSSI/Ethernet Adapter for the VAXft 3000. Minimum of K                      two adapters per system providing redundant connectionp8                      to the Ethernet and the DSSI buses.             CI Options  J           CIXCD-AC      Native CI adapter for DEC 7000 and 10000 Alpha XMIJ                         systems. (Minimum microcode version REV 1.0 is re-                          quired.)             CI Options - VAX onlyS  -                                            97            L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42    N           VAXcluster Software may support multiple CI adapters per system. Re-O           fer to the VAXcluster Software Product Description (SPD 29.78.xx) fore'           the supported configurations.e  J           CI750      CI Adapter for VAX-11/750 systems. (Minimum microcode2                      version REV 8.7 is required.)  I           CI780      CI Adapter for VAX-11/780, VAX-11/785, VAX 8600, and-L                      VAX 8650 systems. (Minimum microcode version REV 8.7 is                      required.)   J           CIBCI      CI Adapter for VAXBI systems. (Minimum microcode ver-/                      sion REV 8.7 is required.)X  L           CIBCA-     Native CI Adapter for VAXBI systems. (Minimum microcode2           AA         version REV 7.5 is required.)  L           CIBCA-     Native CI Adapter for VAXBI systems. (Minimum microcode2           BA         version REV 5.2 is required.)  I           CIXCD-     Native CI Adapter for VAX 9xxx XMI systems. (Minimum <           AA         microcode version REV 1.0 is required.)  I           CIXCD-     Native CI Adapter for VAX 6xxx XMI systems. (Minimum <           AB         microcode version REV 1.0 is required.)             Miscellaneoust  L           InfoServer    An integrated hardware and software system that sitsH                         directly on the Ethernet to provide CD-ROM, hardI                         disk, magneto-optical, and tape access to OpenVMS G                         clients in a local area network. It supports upcG                         to 14 SCSI devices and can be used for softwareeG                         distribution and initial system load (ISL). For J                         more information, refer to the InfoServer Software;                         Product Description (SPD 33.20.xx.)h  5           PC4XD-AA      Parallel/serial port adapter.d  .           PMTCE         TURBOchannel Extender.  "           Miscellaneous - VAX only  -                                            98M           L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      G           CR11       Card reader. One CR11 card reader is supported peri%                      system. (UNIBUS)   ;           DRV11-     General purpose DMA interface. (Q-bus)e           WA  J           DR11-W     General purpose high-speed DMA interface - one DR11-W4                      interface supported per UNIBUS.  G           DR750      High performance general purpose interface for the J                      VAX-11/750. One DR750 interface is supported per sys-I                      tem. This device may not be used in conjunction with                       the CI750.   G           DR780      High performance general purpose interface for the K                      VAX-11/780 and VAX-11/785. One DR780 interface is sup- G                      ported per system. On the VAX 8600 and VAX 8650 as L                      many as four per system are permitted provided that the&                      M8297-YA is used.  +           DWBUA      XMI to UNIBUS adapter.e  L           DWMBA      XMI to BI adapter; also the adapter used to connect the1                      XMI to VAX expander cabinet.e  (           DWMVA      XMI to VME adapter.  H           DW750      UNIBUS Adapter for second UNIBUS for the VAX-11/750                      system.  J           DW780      UNIBUS Adapter for VAX-11/780, VAX 8600 and VAX 8650.  J           FP730      Floating Point Accelerator for the VAX-11/730 system.  J           FP750      Floating Point Accelerator for the VAX-11/750 system.  J           FP780      Floating Point Accelerator for the VAX-11/780 system.  J           FP785      Floating Point Accelerator for the VAX-11/785 system.  H           FP86-AA    Floating Point Accelerator for the VAX 8600 and VAX"                      8650 systems.  C           FV64A      Vector Processing option for the VAX 6000-400.   F           H7112      Memory battery backup for VAX-11/750, VAX-11/780,H                      VAX-11/785, VAX 8600, and VAX 8650 systems. This is6                      required for power-fail/recovery.  -                                            99  C  3      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      H           KE780      G and H floating point microcode for the VAX-11/780                      system.  K           KU780      User-writable control store for the VAX-11/780 system.n  ?           RH750      MASSBUS adapter for the VAX-11/750 system.   G           RH780      MASSBUS controller for the VAX-11/780, VAX-11/785, 4                      VAX 8600, and VAX 8650 systems.  F           SBI        System Backplane Interconnect for the VAX-11/780,J                      VAX-11/785, and I/O BUS for the VAX 8600 and VAX 8650                      systems.r  2           VS40X      4-plane graphics coprocessor.  9           WS01X      VAXstation 3100 SPX Graphics option.o             Abbreviationsa  (           DLT        Digital Linear Tape  9           DSSI       DIGITAL Storage Systems Interconnect   <           EISA       Extended Industry Standard Interconnect  5           FDDI       Fiber Distributed Data Interfacer  =           IEEE       Institute for Electrical and Electronics                       Engineers  ?           I80277     Intel 82077 PC Compatible Floppy Interfaceo  2           MSCP       Mass Storage Control Protocol  6           PCI        Peripheral Component Interconnect  +           QIC        Quarter Inch CartridgeN  5           SCSI       Small Computer Systems Interface   -           SDI        Standard Drive Interfacef  ,           STI        Standard Tape Interface  7           TMSCP      Tape Mass Storage Control Protocole  1           XMI        Extended Memory Interconnectm             M-BUS      MASSBUS  -           SCSI-2     SCSI-2 Fast Single Ended,
           FSEu  -                                           100r o  (      L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      2           SCSI-2     SCSI-2 Fast Wide Differential
           FWD0  9           RAID       Redundant Array of Inexpensive Disks   P           The above information is valid at time of release. Please contact yourC           local Digital office for the most up-to-date information.   /            1995 Digital Equipment Corporation.               All rights reserved.  J           [R]  Adobe, Display PostScript, and PostScript are trademarks of"                Adobe Systems, Inc.  K           [R]  COMPAQ is a registered trademark of Compaq Computer Corpora-)                tion.  J           [R]  IBM is a registered trademark of International Business Ma-"                chines Corporation.  G           [R]  IEEE is a registered trademark and POSIX is a registered K                certification mark of the Institiute of Electrical and Elec-)!                tronics Engineers.r  L           [R]  Microsoft is a registered trademark of Microsoft Corporation.F                registered trademarks of Open Software Foundation, Inc.  J           [R]  Motif and OSF/Motif are registered trademarks of Open Soft-$                ware Foundation, Inc.  F           [R]  Sun is a registered trademark of Sun Microsystems, Inc.  ?           [TM] X/Open is a trademark of X/Open Company Limited.   L           [TM] X Window System is a trademark of the Massachusetts Institute                of Technology.   K           [TM] OSF and OSF/1 are registered trademarks of the Open Software                 Foundation, Inc.   -                                           101e c         L           OpenVMS Operating System for VAX and Alpha, Version 6.2's 25.01.42      H           [TM] The DIGITAL logo, AlphaGeneration, AlphaServer, AlphaSta-H                tion, Bookreader, CDA, CI, DEC, DEC Ada, DECamds, DEC BA-F                SIC, DEC Fortran, DECdtm, DECmigrate, DECnet, DECprint,C                DECram, DECthreads, DECscheduler, DECtp, DECwindows,MF                Digital, DNA, EDT, HSC, InfoServer, KDM, LAT, MicroVAX,F                MSCP, OpenVMS, PATHWORKS, Polycenter, Q-bus, RA, RRD42,G                RX, RZ, SDI, STI, StorageWorks, TA, TMSCP, TURBOchannel,sG                UETP, UNIBUS, VAX, VAX Ada, VAX BASIC, VAX BLISS-32, VAX G                C, VAX COBOL, VAX DIBOL, VAX Fortran, VAXft, VAX Pascal, J                VAX SCAN, VAXserver, VAXstation, VAX Volume Shadowing, VMS,L                VMScluster, VT300, VXT2000, and XUI are trademarks of Digital%                Equipment Corporation.                                                         -                                           102b                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      