Software Product Description _____________________________________________________________________ PRODUCT NAME: OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Note: Digital bases a VMS is a general-purpose great deal of software multiuser operating system development on national and that supports VAX, Micro/VAX, international standards. To VAXstation, and VAXserver emphasize this commitment to series computers in both software standards, Digital development and production has revised the name of environments. VMS can be the VMS Operating System. tuned to perform well in a OpenVMS VAX is the new wide variety of applications, title for the VMS software including compute-intensive, that runs on Digital's VAX Input/Output (I/O)-intensive, processors. All references real-time, and combinations of to VMS in this SPD pertain those and other environments. to the new title OpenVMS (Actual performance depends VAX. on the type of VAX computer, available physical memory, and DESCRIPTION[*] the number and type of disk and tape drives on the system.) __________ [*] "Licensee agrees VMS has well-integrated to only execute Display networking, distributed PostScript® on those Digital computing, multiprocessing, computer systems identified and windowing capabilities. VMS as licensed systems in contains extensive features this Software Product that promote ease-of-use, Description, and that in any improve the productivity of event licensee agrees not programmers, and facilitate to make use of the software system management. directly or indirectly, to POSIX Support print bitmap images with print resolutions greater VMS also supports a than 150 DPI, or to generate large number of industry fonts or typefaces for use standards, facilitating other than with the Digital application portability licensed system." (Terms and interoperability. This and Conditions for Display standards support now extends PostScript can be found in to POSIX (Portable Operating Appendix C of this Software System Interface). POSIX Product Description (SPD).) defines a set of interface standards for various parts of an operating system. The POSIX standards and draft standards have been generated by the Institute of Electrical DIGITAL August 1992 AE-PT7JA-TE OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 and Electronic Engineers The VMS environment with VMS (IEEE) and are supported by POSIX and VAX C installed has organizations such as the been awarded the X/Open XPG3 International Organization BASE brand. Platforms and for Standardization (ISO). components that successfully The VMS Version 5.5-2 complete the branding process environment with VMS POSIX and pass X/Open Verification installed includes support Test Suite for XPG3 (VSX3) are for the standards and draft awarded the X/Open XPG3 brand. standards for the system Components must pass a series application programming of more than 5500 tests in interface (POSIX 1003.1), VSX3 to earn the X/Open BASE shell and utilities (P1003.2), Brand. These tests ensure users and real-time programming that the VMS environment with (P1003.4). VMS POSIX and VAX C installed supports the essential set of VMS POSIX V1.0 was granted interfaces necessary in an open National Institute of system. Standards and Technology (NIST) The inclusion of XPG3 BASE certification in January 1992. support in the VMS environment This means that VMS POSIX has gives application developers passed the POSIX Conformance a broader set of standards- Test Suite (PCTS) that tests based portability features for conformance to NIST's to incorporate into their Federal Information Processing applications. Most applications Standard (FIPS 151-1), which that strictly conform to the is based on POSIX 1003.1- POSIX and XPG3 specifications 1988. VMS POSIX conforms to can be developed on a VMS the POSIX 1003.1-1988 standard system with VMS POSIX and as required by FIPS 151-1. the VAX C compiler, and then XPG3 BASE Branding ported without modification The VMS V5.5-2 environment to any other platform that with VMS POSIX Version 1.1 and also supports the same POSIX VAX C Version 3.2 installed standards, draft standards, and extends the support for XPG3 specifications. POSIX standards and draft standards to include the X/Open User Environment BASE specifications defined Users can access VMS by using in the X/Open Portability the English-like Digital Guide, Issue 3 (XPG3). The Command Language (DCL), the XPG3 BASE specifications command language for VMS that extend the system application is supplied with the system. programming interface and DCL commands take the form shell and utilities offered of a command name followed by in the IEEE POSIX standards parameters and qualifiers. DCL and draft standards. XPG3 commands provide information also includes standards-based about the system, initiate internationalization support. system utilities, and initiate user programs. VMS prompts users to enter required DCL 2 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 parameters, making it easy for also use special DCL commands novice users to use. to assign symbolic names, Users can enter DCL commands at evaluate numerical and logical a terminal or include them expressions, accept parameters, in command procedures and communicate interactively with can run command procedures the user invoking the command interactively or submit them procedure, perform conditional to a batch queue for deferred (IF-THEN-ELSE) and branching execution. (GOTO) logic, and handle error conditions. Information on DCL and VMS User Environment Tailoring Utilities is available through - Users can customize the online Help. Online Help computing environment with includes summary operational user login command procedures, information on all aspects of shorthand commands, binding of system operation. commands to function keys, and A number of tools and utilities command recall and editing. are integrated into the VMS Program Development Environment Operating System. This section briefly describes some of these VMS provides a comprehensive tools and utilities. set of tools for developing Text processing - The programs including editors Extensible VAX Editor (EVE), (for editing source programs), one of several text editors a linker, a librarian, and supplied by Digital, allows a symbolic debugger. The users to insert, change, and assembly-level VAX MACRO delete text quickly. Written in language is supplied with VMS. the VAX Text Processing Utility The VMS Run-Time Library Language (VAXTPU), EVE is a provides string manipulation, full-screen editor that allows I/O routines, I/O conversion, users to scroll through text on terminal independent screen a terminal screen. EVE provides handling, date and time an EDT-style keypad, allowing formatting routines, common users of EDT to transition to mathematical functions, EVE easily. signaling and condition Mail facility - The Mail handling, and other general facility allows users to send purpose functions. These messages to any other user on routines can be called from the system. Multinode operation programs written in VAX MACRO is available if DECnet-VAX is or from VAX Ada, VAX BASIC, installed and licensed on each VAX BLISS-32 Implementation participating node. Language, VAX C, VAX COBOL, VAX DIBOL, VAX FORTRAN, Command-level programming - VAX Pascal, VAX PL/I, and Command-level programming VAX SCAN. allows users to create special Major VMS languages (including files called command procedures those listed above) adhere that contain a series of DCL to the VAX common calling commands. When users execute a standard, meaning that routines command procedure, the system written in any of these processes the commands in the languages can directly call command procedure. Users can 3 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 routines written in any other Debugger - The debugger language. Development of allows users to trace program applications using multiple execution as well as display languages is simple and and modify register contents straightforward. using the same symbols that are All routines in the Run-Time in the source code. Library follow the VMS calling RMS file utilities - RMS standard and condition handling file utilities allow users to conventions and most are analyze the internal structure contained within a shareable of an RMS file and to determine image. the most appropriate set of At a lower level, programs parameters for an RMS file. can call system services They can also be used to directly for security, event create, efficiently load, and flag, asynchronous system trap, reclaim space in an RMS file. logical name, record and file Refer to the Operating System I/O, process control, timer, Environment section of this time conversion, condition Software Product Description handling, lock management, and (SPD) for more information on memory management services. RMS. Again, system services use File Differences utility - This the VMS calling standard and utility compares the contents condition handling conventions. of two files and lists those VMS supports execution of non- records that do not match. privileged images created Terminal Fallback Facility on earlier versions of VMS. (TFF) - This facility allows Recompiling and relinking are Digital 7-bit terminals, such typically not required. as the VT100, to input and Some tools available to the VMS output the DEC Multinational programmer are: Character Set (MCS). Specific tables allow conversion for Librarian utility - The a number of different 7-bit Librarian utility permits National Replacement Character efficient storage of object sets, such as French, German, modules, macros, Help text, Spanish, and Swedish, to MCS. or any general record-oriented TFF also allows character information in central, easily composition on terminals that accessible files. Object module do not have the compose key. libraries are searched by the National Character Set (NCS) linker when the linker finds a utility - This utility allows reference it cannot resolve in users to define non-ASCII one of its input files. Macro string collating sequences libraries are searched by the and to define conversion assembler when the assembler functions. Conversion functions finds a macro that is not use conversion algorithms to defined in the input file. change an input string, for example, to change lower case characters to upper case. NCS also allows RMS indexed files to be collated using user- specified collating sequences. 4 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 System Management Environment data may be displayed as it is VMS provides a variety of tools gathered or saved in a file for to aid the system manager in later use. configuring and maintaining an License Management Facility optimal system. Some tools (LMF) - This facility allows available for the system the system manager to easily manager are: determine which software Backup utility - This utility products are licensed on a provides full volume and standalone VAX and on each of incremental file backup for the VAX systems in a VAXcluster file-structured, mounted System. It allows the system volumes and volume sets. manager to select which subset Individual files, selected of systems or users in a directory structures, or all VAXcluster may use the software files on a volume set can products. LMF also provides be backed up and restored. an audit trail that allows the Files can be selected by system manager to track license various dates (creation, changes that occur within a modification, etc.). Files VAXcluster system. Refer to the can be backed up to magnetic VAXcluster Support section for tape, magnetic disk, or WORM more information on VAXcluster (Write Once Read Many) optical Systems. disk. With standalone backup, VMS System Management (SYSMAN) system managers can back up utility - This utility allows and restore system disks. the system manager to define a Standalone backup can also be system management environment used during the installation of so that operations performed the VMS Operating System. The from the local VAX system Backup utility can be used to can be executed on all other restore a saveset or list the VAX systems in the defined contents of a saveset. environment. The environment Analyze disk structure utility may include VAX systems in a - This utility compares the DECnet-VAX network or in a structure information on a disk VAXcluster System. volume with the contents of the Operations - VMS enables disk, prints the structure varying levels of privilege information, and permits to be assigned to different changes to that information. operators. In addition, system It also can be used to repair generated messages can be errors that are detected in the routed to different terminals file structure of disks. based on their interest Monitor utility - This utility to the console operators, permits the system manager to tape librarians, security monitor different classes of administrators, and system system-wide performance data managers. Operators can use including process activity, the VMS Help facility to get an I/O activity, memory management online description of VMS Error activity, vector processing Messages. activity, and two-phase commit transaction activity at specified intervals. The 5 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Security and Control - VMS can install their own filter provides privilege, protection, to screen passwords against a and quota mechanisms to site-specific password policy. control user access to system- The system password hash controlled structures in algorithm can also be replaced physical memory, to system- with a private algorithm structured files and volumes, for those sites that have and to certain devices. contractual agreements to use User account information specific password encryption is maintained by the algorithms. This feature can system manager in the User be enabled on a per-user, per- Authorization File (UAF). When password basis. creating user accounts with the Login security includes Authorize utility, the system breakin detection, which allows manager assigns the privileges terminals to be disabled when and quotas associated with password guessing is detected. each user account. The system When a user logs in, the system manager also assigns a unique displays a message stating when user name, password, and user the last login for the account identification code (UIC) to occurred and if there have been each account. Optionally, failed attempts to log in since additional identifiers can the last successful login. be assigned to each account, permitting users to belong to A UIC consists of two fields, multiple overlapping groups or the unique user field and projects. Account use may be a group field. Every file, limited by time of day, day of device, queue, or other system week, and type of access, such object is labeled with the UIC as local, remote, or batch. of its owner (normally the user To log in and gain access to who created the object). the system, the user must Files, devices, queues, and supply the user name and other system objects are password. The password is assigned a protection mask encoded and does not appear that allows read, execute, on terminal displays. Users write, and delete access to can change their password be selectively granted to voluntarily, or the system the object's owner, group, to manager can selectively enforce privileged system users, or to how frequently passwords all other users. In addition, change, password length, and files, devices, queues, and generation of random alphabetic some other system objects passwords. can be protected with access Additionally, VMS provides control lists to allow access several password filters to be selectively granted or that screen all user password denied to a list of individual changes against a dictionary of users, groups, or identifiers. common passwords. This prevents users from reusing passwords that they have used within the last year. In addition to these built-in filters, a site 6 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Scavenge protection can be VMS includes a facility to enabled selectively in the form automate operating system of file high-water marking, software updates, as well as erase on allocate, and erase to handle the installation on delete, to ensure that file of optional Digital-supplied contents cannot be read after a software products. file has been deleted. Tailoring Facility Security alarms are provided Tailoring lets the system to allow selective auditing manager remove groups of VMS of security related events, files from the system disk or including: add groups of VMS files that o Login and logout were formerly removed. The o Login failures and VMSTAILOR program supplies breakin attempts step-by-step instructions. o Authorization changes The DECW$TAILOR program is used to add or remove groups o File access, selectable of DECwindows files from the by use of privilege, system disk. type of access, and by Due to space constraints, there individual file is no guarantee that layered Note: No system can provide products can be installed if complete security and user files reside on the system Digital cannot guarantee disk. system security. However, Application programs will Digital continually strives execute as long as the layered to enhance the security products or optional software capabilities of its products do not depend on products. Customers are optional software run-time strongly advised to follow components that are not industry-recognized security supported in the tailored practices. environment. Refer to the product's System Support INSTALLATION Addendum (SSA) for the optional VMS is distributed as binary products supported in the kits on tape and compact disc. tailored environment. Procedures for setting up Batch/Print Facility the system disk from a kit VMS provides an extensive batch and for preparing the system /print facility that allows for day-to-day operations are the creation of queues and easy and straightforward. The the setup of spooled devices procedures are described in the in order to process non- VMS Upgrade and Installation interactive workloads in Manual and in the VMS Update parallel with timesharing or Procedures. Computer-specific real-time jobs. information is contained in the upgrade and installation supplements for each family of VAX computers. VMSINSTAL 7 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 In the VMS Operating System, Accounting batch and print operations For accounting purposes, VMS support two types of queues: keeps records of the use generic queues and execution of system resources. These queues. A generic queue is an statistics include processor intermediate queue that holds and memory utilization, I/O a job until an appropriate counts, print symbiont line execution queue becomes counts, image activation available to initiate the job. counts, and process termination An execution queue is a queue records. VMS Accounting allows through which the job (either various reports to be generated print or batch) is actually using this data. processed or executed. The system queues batch jobs Autoconfigure/Autogen for execution. The system VMS provides utilities to manager can regulate the number automatically configure the of queues and the number of available devices into the streams per queue (that is, system tables and to set system the number of batch jobs in operational parameters based the queue that can execute on the detected peripheral and concurrently). memory configuration. There Both generic and execution is no need for a traditional batch queues can have different "system generation" process attributes, such as the maximum when the hardware configuration CPU time permitted, working set is expanded or otherwise size, and priority. Facilities modified. are provided for starting and stopping queues, and Operating System Environment for starting and stopping Process and Scheduling jobs in a queue. Because multiple execution queues The basic unit of execution in can be associated with a VMS is the process. A process generic queue, VMS enables consists of individual address load balancing across available space and registers known as CPUs in a VAXcluster system, "context," and code called increasing overall system an "executable image." The throughput. context identifies the process Print queues, both generic and and describes its current execution, together with queue state. Executable images management facilities, provide consist of system programs and versatile print capabilities, user programs that have been including support of ANSI and compiled and linked. PostScript® file printing. The maximum number of Sites requiring sophisticated concurrent processes is 8,192 batch job dependency per VAX system. checking and job restart capabilities should refer to the DECscheduler for VMS Software Product Description (SPD 32.19.xx). 8 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Processes receive processor Programmers can exercise time to execute their images control over memory management based on the priority of the from within an image. An process. Thirty-two priorities image executing in a real- are recognized: priorities 0 time process, for example, can to 15 are for time-sharing inhibit paging or swapping of processes and applications that critical code and data. are not time critical (four Peripheral devices can be is the typical default for managed by the system or time-sharing processes), and allocated by individual priorities 16 to 31 are for processes. At least one disk real-time processes. must be a system disk. Other Each time an event such as disks can be designated as an I/O interrupt occurs, data disks for the general use the system first services of all users logging into the the event and then passes system or for a specific group control to the highest priority of users. The system controls process ready to execute. The interactive terminals and one system automatically adjusts or more printers. priorities of processes whose Vector Processing base priority is in the range of 0 to 15 to favor I/O-bound A single data item, having one and interactive processes, but value, is known as a scalar the system will not adjust the value. A group of related priority of a process in the scalar values, or elements, range of 16 to 31. all of the same data type, is Real-time processes can be known as a vector. assigned higher priorities An extension to the VAX to ensure that they receive architecture defines an processor time whenever they optional design for integrated are ready to execute. Real- vector processing that has been time processes are scheduled adopted by several VAX systems. pre-emptively; that is, if a The VAX vector architecture real-time process is ready includes 16 64-bit vector to execute, it is given the registers (V0 through V15), processor immediately, unless a each containing 64 elements; real-time process with a higher vector control registers; priority is ready to execute. vector function units; and a VMS uses paging and swapping set of vector instructions. mechanisms to provide VAX vector instructions sufficient virtual memory transfer data between the for multiple concurrently vector registers and memory, executing processes. Also, perform integer and floating- paging and swapping is provided point arithmetic, and execute for processes whose memory processor control functions. requirements exceed available A more detailed description of physical memory. The maximum the VAX vector architecture, working set size is 200,000 vector registers, and vector pages of memory. instructions appears in the VAX MACRO and Instruction Set Reference Manual. 9 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 The VMS Operating System non-privileged VAX vector provides fully-shared, multi- instructions and the VMS vector programming support for VAX system services, as described vector processing systems. in the VMS documentation. Use By default, VMS loads vector of VVIEF is restricted to user support code when initializing mode code. vector-present systems, DECdtm Services but does not load it when initializing vector-absent The DECdtm services embedded systems. A system manager can in the VMS Operating System control this behavior by using support fully distributed the SYSGEN parameter VECTOR_ databases using a "two phase PROC, as described in the VMS commit" protocol. The DECdtm documentation. services provide the technology The presence of vector support and features for distributed code in a system has little processing, ensuring both affect on processes running transaction and database in a scalar-only system, or integrity across multiple scalar processes running in resource managers. Updates to a vector-present system. If distributed databases occur as many processes must compete a single "all or nothing" unit simultaneously for vector of work, regardless of where processor resources in a the data physically resides. system, the system manager This ensures consistency of can maintain good performance distributed data. by adjusting system resources DECdtm services allow and process quotas as indicated applications to define "global in the VMS documentation. transactions" that may include The VMS Operating System makes calls to any of a number the services of the vector of Digital data management processor available to system products. Regardless of the users by means of a software mix of data management products abstract known as a capability. used, the global transaction A system manager can restrict will either commit or abort. the use of the vector processor VMS is unique in providing to users holding a particular transaction processing identifier by associating an functionality as base operating access control list (ACL) entry system services. with the CAPABILITY object DECdtm Features VECTOR. o Embedded VMS system The VAX Vector Instruction services support the Emulation Facility (VVIEF) DECtp architecture, is a standard feature of the providing features VMS Operating System that and the technology for allows vectorized applications distributed transaction to be written and debugged processing. in a VAX system in which vector processors are not available. VVIEF emulates the VAX vector processing environment, including the 10 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 o DECdtm allows multiple o The lock manager provides disjoint resources to a more comprehensive be updated atomically. enqueue/dequeue facility These resources can with multi-level locks, be either physically- values, and ASTs disjointed (for example, (Asynchronous System on different CPUs) or Traps). logically-disjointed (for Symmetric Multiprocessing example, in different databases on the same VMS provides symmetric CPU). multiprocessing (SMP) support o DECdtm encourages robust for multiprocessing VAX application development. systems. SMP is a form of Applications can be tightly coupled multiprocessing written to ensure that in which all processors perform data is never in an operations simultaneously. inconsistent state, even The processors can perform in the event of system operations in all VAX access failures. modes (user, supervisor, o As a VMS service, DECdtm executive, and kernel). can be called using VMS SMP configurations consist any Digital TP monitor of multiple central processing (ACMS or DECintact) units executing code from a or database product single shared memory address (DBMS, RDB, RMS). This is space. Users and processes useful for applications share a single copy of VMS. using several database SMP also provides simultaneous products. shared access to common data Interprocess Communication in global sections to all processors. VMS SMP dynamically VMS provides a number of balances the execution of all facilities for applications processes across all available that consist of multiple processors based on process cooperating processes: priority. o Mailboxes are virtual SMP support is an integral devices that allow part of VMS and is provided processes to communicate transparently to the user. with queued messages. Because an SMP system is a o Shared memory sections single system entity, it is on a single processor configured into a network and or a symmetrical VAXcluster systems as a single multiprocessing (SMP) node. system permit multiple VAXcluster Support processes to access VAXcluster Software is a VMS shared address space System Integrated Product concurrently. (SIP) that is separately o Common event flags licensed. It provides a highly provide simple integrated VMS computing synchronization. environment distributed over multiple VAX, VAX Workstation, and Micro/VAX CPUs. This 11 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 environment is called a Refer to the VAXcluster VAXcluster system and may Software Software Product contain up to 96 VAX CPUs. Description (SPD 29.78.xx) VAXcluster CPUs communicate for more information. using any combination of Networking Facilities four interconnects; CI, DSSI, VMS provides device drivers Ethernet, and FDDI. VAXcluster for all Digital Ethernet systems that include a CI may adapters listed in the Ethernet optionally be configured with Options section of this SPD. HSC-series intelligent storage Application programmers can controllers. use the QIO system service Applications running on one to communicate with other or more CPUs in a VAXcluster systems connected via the system access shared resources Ethernet using either Ethernet in a coordinated manner. or IEEE 802.3 packet format. VAXcluster Software components Simultaneous use of Digital synchronize access to shared Ethernet and IEEE 802.3 resources, preventing multiple protocols are supported on processes on any CPU in the any Digital Ethernet adapter. VAXcluster from interfering VMS also provides device with each other when updating drivers for Digital data. This coordination asynchronous adapters that ensures data integrity during are supported by DECnet-VAX. multiple concurrent update Customers must order the transactions. Application VAX Wide Area Network Device programs can specify the level Drivers kit (refer to SPD of VAXcluster-wide file sharing 29.64.xx) to obtain synchronous that is required; access is device drivers for Digital then coordinated by the VMS synchronous adapters. Not all Extended QIO Processor (XQP) devices are supported, and and Record Management Services certain restrictions apply (RMS). relative to line speed and The VMS queue manager controls line utilization. Refer to the VAXcluster-wide batch and print Hardware Charts and Appendix queues, which can be accessed B of this SPD, as well as the by any VAXcluster CPU. Batch DECnet-VAX SPD (25.03.xx), for jobs submitted to VAXcluster- more information. wide queues are routed to any DECnet-VAX offers task-to- available CPU so that the batch task communications, file load is shared. management, downline system Two or more VAX computers and task loading, network connected to the same Computer command terminals, and Interconnect (CI) or Digital network resource sharing Storage Systems Interconnect capabilities using the (DSSI) must run VAXcluster Digital Network Architecture software and be part of the (DNA) protocols. same VAXcluster system. 12 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 DECnet-VAX Software is a Digital's terminal server System Integrated Product products can be used for (SIP) that is separately terminal server access to licensed from the VMS VMS. When used in a VAXcluster Operating System. Refer system environment, terminal to the DECnet-VAX SPD servers automatically (SPD 25.03.xx) for further distribute users at login information on supported time across the available VAX communications devices and systems. software features. VMS can also establish a Internet networking is connection to other devices available through the (such as printers) attached to VMS/ULTRIX Connection layered such terminal servers. product. This product provides Reliability TCP/IP networking (useful with DECwindows), Network File The system handles hardware System (NFS), File Transfer errors as transparently as Protocol (FTP), Remote Terminal possible while maintaining Services (TELNET), and other data integrity and providing features. Refer to the VMS sufficient information to /ULTRIX Connection SPD (SPD diagnose the cause of the 25.A4.xx). error. The system limits the Multi-Threading Capability effects of an error by first determining if the error VMS includes a user-mode multi- is fatal. If the error is threading capability referred fatal then the process that to as DECthreads. DECthreads encountered the error is provides an implementation aborted. If the error occurs of draft 4 of the proposed in system context then the POSIX 1003.4a standard and current VMS session is shut is Digital's implementation down. If the error is not fatal of the Distributed Computing then recovery actions pertinent Environment (DCE) Threads as to the error are executed and defined by the Open Software current operation is continued. Foundation. DECthreads is a In all cases, information library of run-time routines relevant to the error is that allows the user to create collected and put in the error multiple threads of execution log file for later analysis. within a single address space. Hardware errors include the Multi-threading capability following categories: allows computation activity to be overlapped with I/O o Processor errors (these activity. Synchronization include processor soft elements, such as mutexes errors, processor hard and condition variables, are errors, processor machine provided to help ensure that checks, adapter errors). shared resources are accessed correctly. DECthreads also provides multiple scheduling policies for scheduling and prioritizing threads. Terminal Server Products 13 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 o Memory errors are the processor registers. hardware errors that The VMS System Dump are handled in a slightly Analyzer utility is different manner. The provided for analyzing system examines memory memory dumps. at startup time and Power Failures does not use any pages found to be bad. During If power fails, the system system operation, the shuts down automatically. When hardware transparently power is restored, the system corrects all single- restarts automatically and bit memory errors for resumes processing at the point those systems with ECC of interruption if the system memory. An unrecoverable has a time-of-day clock and error causes the memory a memory battery backup unit, page on which the error if the contents of memory are occurred to be added still valid, and if the system to the bad page list. is set to permit automatic If the page has not rebooting. been modified, system The system restarts devices operation continues with and communications lines. All a new copy of the page. I/O operations in progress, Other failures include: including magnetic tape I/O o Operating system errors operations, are restarted. (system-detected On request, programs can be inconsistencies or notified of power restoration. architectural errors An optional battery-operated in system context) hardware clock resets the date and time of day when o User errors the system restarts. If the o I/O errors system does not have a battery The system logs all backup unit, or if the memory processor errors, all contents are not valid on operating system errors power restoration, the system detected through internal will reboot automatically if consistency checks, the system is set to permit all double-bit memory automatic rebooting. errors (and a summary If, for any reason, the system of corrected single- disk does not come back on line bit errors), and all after a power failure within I/O errors. (Double- a specific time after the CPU bit errors are detected regains power, the system shuts only on those VAX and down. Micro/VAX systems with ECC memory.) Test Package and Diagnostics If the system is shut VMS includes a User Environment down because of an Test Package (UETP) that unrecoverable hardware verifies that the VMS Operating or software error, a System is properly installed dump of physical memory and ready for use on the is written. The dump customer's systems. includes the contents of 14 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Diagnostics can be run on These I/O devices include individual devices during line printers, card readers, normal system operation. and general purpose data Certain critical components can acquisition devices such as operate in degraded mode. For the DRB32. example, the memory cache can VMS Record Management Services be disabled. The system places (VMS RMS) a component in degraded mode when errors pass a threshold VMS RMS is a set of I/O level. services that help application Input/Output programs to process and manage files and records. Although The QIO system service it is primarily intended provides a direct interface to provide a comprehensive to the operating system's I/O software interface to mass routines. These services are storage devices, VMS RMS also available from within most VAX supports device-independent programming languages and can access to unit-record devices. be used to perform low-level VMS RMS supports sequential, I/O operations efficiently relative, and indexed file with a minimal amount of system organizations in fixed-length overhead for time-critical and variable-length record applications. formats. VMS RMS also supports Device drivers execute I/O byte stream formats for instructions to transfer data sequential file organization. to and from the device and to VMS RMS record access modes communicate directly with an provide access to records I/O device. Each type of I/O in four ways: sequentially, device requires its own driver. directly by key value, directly Digital supplies drivers for by relative record number, all devices supported by and directly by record file the VMS Operating System and address. VMS RMS also supports provides QIO system service block I/O operations for routines to access the special various performance-critical device dependent features applications that may require available in many of these user-defined file organizations devices. Users with special and record formats. needs or non-VMS supported VMS RMS promotes safe and devices can write their own efficient file sharing by device drivers. The VMS Device providing multiple file access Support Manual and the VMS modes, automatic record locking Device Support Reference where applicable, and optional Manual in the VMS Extended buffer sharing by multiple Documentation set describe how processes. to write device drivers. The VMS Operating System VMS RMS utilities aid supports a variety of disk file creation and record and tape peripheral devices, maintenance. These utilities as well as terminals, networks, convert files from one mailboxes (virtual devices for organization and format to interprocess communication), another, restructure indexed and more general I/O devices. files for storage and access 15 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 efficiency, and reclaim data o After Image Journaling. structures within indexed Provides the ability files. The utilities also to "redo" modifications generate appropriate reports. that have been made to For systems that have DECnet a file. This type of installed, VMS RMS provides journaling allows you to a subset of file and record recover files that are management services to remote inadvertently deleted, network nodes. Network remote lost or corrupted. RMS file operations are generally Journaling recovers the transparent to user programs. file by applying the journaled modifications DCL commands such as EDIT, to a backup copy, thereby CREATE, COPY, TYPE, and PRINT restoring its final allow manipulation of RMS files state. No application and records within RMS files at modifications are the DCL command level. necessary in order to use RMS Journaling for OpenVMS After Image journaling. RMS Journaling for OpenVMS is a o Recovery Unit Journaling. VMS System Integrated Product Provides the ability (SIP) that enables a system to maintain transaction manager, user, or application integrity. A transaction to maintain the data integrity may be defined as a of RMS files in the face of a series of many file number of failure scenarios. updates, on one or more It protects RMS file data from files. In the event of becoming lost, corrupted, or any failure during the inconsistent. RMS Journaling transaction, Recovery for OpenVMS is separately Unit journaling will licensed. roll-back the partially completed transaction RMS Journaling provides the to its starting point. ability to maintain three types This allows complex of journaling that maintain transactions to be modification information for completed as an atomic journaled RMS files. event - partially o Before Image Journaling. completed transactions Provides the ability to can be avoided. Recovery "undo" modifications Unit journaling requires that have been made application modification. to a file. This type Refer to SPD 27.58.xx for more of journaling provides information. the ability to return Disk and Tape Volumes a file to a previous known state. This is Disk volumes can be organized useful in the event that into volume sets. Volume a file is updated with sets can contain a mix of erroneous or bad data. No disk device types and can be application modifications extended by adding volumes. are necessary in order Within a volume set, files to use Before Image of any organization type can journaling. span multiple volumes. Files 16 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 can be allocated to the set The system provides eight as a whole (the default) or levels of named directories to specific volumes within the and subdirectories whose set. Optionally, portions of contents are alphabetically indexed files can be allocated ordered. Device and file to specific areas of a single specifications follow Digital disk volume or to specific conventions. Logical names volumes in a volume set. can be used to abbreviate the Disk quotas can be placed to specifications and to make control the amount of space application programs device individual users can allocate. and file-name independent. A Quota assignment is made by logical name can be assigned to User Identification Code and an entire specification, to a can be controlled for each portion of a specification, or volume set in the system (or to another logical name. for each individual volume if VMS supports multivolume the volume is not part of a magnetic tape files with set). transparent volume switching. Disk structure information can Access positioning is done be cached in memory to reduce either by filename or by the I/O overhead required for relative file position. file management services. Volume Shadowing for OpenVMS Although not required to do Digital provides the Volume so, users can preallocate Shadowing for OpenVMS product space and control automatic for performing disk shadowing allocation. For example, a operations, using a RAID 1 file can be extended by a given implementation. number of blocks, contiguously or noncontiguously, for optimal Volume Shadowing for OpenVMS is file system performance in a VMS System Integrated Product specific cases. (SIP) that is separately The system applies software licensed. Volume Shadowing validity checks and checksums for OpenVMS provides high to critical disk structure data availability for disk information. If a volume storage devices by ensuring is improperly dismounted against data loss resulting because of user error or from media deterioration or system failure, the system through controller or device automatically rebuilds the failure. This prevents storage volume's structure information subsystem component failures the next time the volume is from interrupting system or mounted. The system detects bad application operation. blocks dynamically and prevents The system disk and Files-11 their reuse once the files to On-Disk Structure 2 (ODS2) data which the blocks were allocated disks can be volume shadowed. are deleted. On Digital Storage Architecture (DSA) disks, the disk controller dynamically detects and replaces bad blocks automatically. 17 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 The Volume Shadowing for regardless of which environment OpenVMS product supports the user selects. Refer to the shadowing of all MSCP-compliant VMS DECwindows Motif SPD (SPD DSA disks and all Digital 36.09.xx) for more information. SCSI disks. All disks in a VMS DECwindows Environment single shadow set must have the same physical geometry Integral to VMS is support and can be located on a for the VMS DECwindows desktop single system or anywhere in environment. VMS DECwindows is a VAXcluster system. Disks based on MIT's specification can be configured on any MSCP for the X Window System, or Digital SCSI compliant Version 11, Release 3, and is controller; this includes delivered as a component of the HSC-series controllers, local VMS Operating System. X Window controllers, DSSI Integrated System standards supported as Storage Elements, and VMS MSCP part of DECwindows include the Served DSA devices. Nonlocal X11 network protocol, a base disks can be accessed using any set of workstation fonts, the of the supported VAXcluster C language binding for the interconnects (CI, DSSI, Xlib programming library, and Ethernet, FDDI, and mixed). the C language binding for Volume Shadowing for OpenVMS the Xtoolkit library. Also provides fault tolerance featured within DECwindows for resulting from disk media workstation users is support errors or controller errors for Adobe's Display PostScript across the full range integrated into X11. of VAX processors and Support of the X11 network configurations. Shadow set protocol in the client library, member units can be located and display server components on different controllers and provides VMS with the ability VMS MSCP servers, providing to interoperate with other configuration flexibility X11-compliant systems in a and a high degree of data distributed fashion. availability. DECwindows supports the client- Refer to SPD 27.29.xx for more server distribution inherent information. in the X Window System, with VMS DECwindows Motif[TM] three VMS-provided transport interfaces - local shared Digital offers a separately memory, DECnet, and TCP/IP orderable layered product (using Digital's VMS/ULTRIX called VMS DECwindows Connection (UCX) layered Motif[TM]. VMS DECwindows Motif product). Users can also provides support for both OSF provide their own transport /Motif[TM], an open standard subsystems and transport that is the new default user interfaces. interface, and the X User Interface in a single run-time and development environment. Because both Motif and XUI are based on MIT's X Window System, applications written to either toolkit continue to run 18 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 To determine whether a 4. The DECterm terminal separately orderable DECwindows emulator provides or X application runs on or workstation users with can communicate with a VMS a traditional character DECwindows system, consult the cell interface for application's Software Product existing VMS features Description. and applications. It The DECwindows desktop is a ReGIS and sixel environment provides a compatible VT320 terminal graphical user interface emulator. Programs to VMS. This user interface written for VT52, VT100, defines a powerful model VT220, or VT320-class for interacting with the VMS terminals and using Operating System using a point VMS terminal driver and click metaphor. It includes features operate without a set of integrated desktop modification in this applications that demonstrate workstation window. the power of this new metaphor DECterm also provides and that provide VMS users with workstation-oriented a base set of desktop tools. features such as mouse- based cursor positioning, The user environment consists variable screen sizes, of four basic components: and cutting and pasting 1. The Session Manager of text between terminal provides the top-level emulators and other user interface to a DECwindows applications. DECwindows workstation. It performs application activation, session- wide customization, screen printing, security management, and session control. The session manager also allows users to specify the language in which DECwindows should run, provided that a VMS DECwindows language variant kit has been ordered and installed. 2. The Window Manager provides user control for managing windows. 3. FileView is a graphical interface to VMS file management that allows users to navigate through the VMS file system and perform operations on files. 19 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Applications o TPU/EVE - A DECwindows A set of integrated desktop user interface to the VMS applications is provided TPU/EVE editor as a base component of the DECwindows workstation users DECwindows environment. These can display PostScript files applications establish and featuring WYSIWYG (what you see demonstrate the consistent is what you get) compatibility DECwindows user model. They between the display and any of also provide significant end Digital's PostScript printers. user capabilities. Display PostScript ability is o Bookreader - A tool for available within the Compound viewing the contents Document viewer and DECwindows of books that are Mail. distributed and stored Programming Support on-line The VMS DECwindows environment o Calculator - A basic includes an extensive set of scientific calculator programming libraries and tools o Calendar - A personal for use by developers of new time management system applications. These components o Cardfiler - A support the development of hierarchical information portable applications by storage application focusing on three broad areas: similar to an online o X Window System (X) address and/or phone book support o Clock - An analog and/or o X User Interface (XUI) digital date and time support display with notification o Compound Document by alarm Architecture (CDA) o Compound Document viewer support - Tools for reading Components from each of documents containing these areas can be used in compound text, graphics, any combination to address and image data on the needs of applications. terminals and DECwindows They can also use the tools workstations from a variety of different o DEBUG - A DECwindows programming languages. All user interface to the VMS programming libraries have DEBUGGER been provided with procedural o Mail - A DECwindows user language bindings in both interface to the VMS mail the style of the VAX calling facility standard and the style of the o Notepad - A simple text MIT C language programming editor conventions. o Paint - A simple bitmap graphics editor o Puzzle game - A game that challenges users to sort mixed up puzzle tiles 20 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Support is provided for the The XUI Style Guide, available following languages: in the VMS DECwindows VAX Ada VAX FORTRANogramming Kit, describes the principles, philosophy, VAX BASIC VAX MACROand components used to build consistent and well-integrated VAX BLISS-32 VAX PascalECwindows applications. Implementation Its concepts are implemented Language by the XUI Toolkit. The XUI Toolkit is a superset of the VAX C (VAX calling VAX X Window System Xtoolkit and standard PL/I contains four components: or MIT o Xtoolkit components convention) (known as intrinsics) for X Window System (X) Programming managing, modifying, and Support creating user interface The X Window System compatible objects (known as widgets X programming library (Xlib) and gadgets) provided by the VMS DECwindows o DECwindows widgets and environment provides basic gadgets for implementing resource management (windows, common user interface color maps, input devices) objects such as scroll and bitmap graphics services. bars, menus, and push It defines a mapping of the X buttons network protocol to a procedure o Utility routines that library. provide applications with The Xtoolkit programming functions for performing library is also supported by common tasks such as cut the VMS DECwindows environment. and paste It is described further under o Resource manager routines XUI Programming Support. for loading user X User Interface (XUI) interface definition Programming Support files and creating widgets and gadgets based XUI determines the application on the contents of the model for Digital and third- definition files party software tailored for The XUI Toolkit is used in the DECwindows environment. conjunction with the DECwindows It establishes the conventions User Interface Language (UIL) and styles that are encouraged compiler. The user interface for applications that share definition files produced by a DECwindows workstation. this compiler contain the data Applications use XUI components to separate form and function to build user interfaces that in DECwindows applications and make them look and feel like allow DECwindows toolkit widget integrated members of the and gadget details, such as Digital computing environment. menu item labels, to be stored separately from the toolkit and application run-time code. This capability allows application 21 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 developers to prototype and Programming access to XDPS modify user interface designs, is through the Adobe Client separate form and function Library. In addition, a in applications, and support converter called pswrap allows international products. users to convert PostScript Enhanced X Windows Display code into C programs that can PostScript (XDPS) be called from other languages. The Display PostScript system Compound Document Architecture provided with VMS DECwindows (CDA) Programming Support extends the native X graphical The CDA Toolkit provides access programming environment for routines that applications Digital DECwindows workstation can use to create, read, and users. write files containing compound X Display PostScript adds the text, graphics, and imaging following capabilities to the data. These files provide a basic X11 environment: vehicle for recording this information on disk, a medium o All DECwindows fonts can for interchange of this data be displayed at any size between applications, and an and rotation angle intermediate form from which o XDPS graphics specified high-resolution printable in a user-defined graphics data can be generated. coordinate systems are In addition to providing independent of monitor support for developing new density applications to access compound o Color or gray- documents, VMS also provides scale rendition are fallback support, allowing many automatically modified existing utilities to read and to take advantage of operate on these new kinds of the monitor type through files. either direct display, Transport Mechanisms color dithering, or half- toning VMS DECwindows supports three o DPS Display routines different user-selectable can be downloaded to the mechanisms for transport of server and executed on X network protocol packets command between applications and display servers. o Sophisticated graphics A VMS DECwindows-specific primitives such as shared memory-based transport precisely-controlled is used when the DECwindows Bezier curves can be application and display displayed server are located on the same o Any display can be scaled workstation. This optimization and rotated arbitrarily provides significantly greater performance. It is the default transport under these circumstances. 22 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 DECnet is used when the provided so that customers can DECwindows application and make their own private fonts display server are distributed available on their DECwindows across two different machines workstations and terminals. in the network. It is the Multi-headed Workstation default transport under these Support circumstances. TCP/IP is used when the A multi-headed workstation DECwindows application and consists of one system box, display server are distributed one keyboard and one mouse, across two different machines but more than one monitor and in the network and the Digital- graphics controller. It is a supplied VMS/ULTRIX Connection single-user workstation. Multi- (UCX) layered product is being headed workstations provide used to make the connection. more screen area for complex See the SOFTWARE LICENSING applications. section of this SPD for The screens on the multiple licensing details. monitors are controlled by a Workstation Device Support single server. The mouse cursor can be moved freely between The VMS DECwindows environment screens, and the keyboard can provides several software be used to generate input to components to support windows on any screen. The displaying graphics and server implementation handles windowing output on and each monitor as a separate receiving keyboard and X11 screen. This means that pointer driver input from VAX a single window cannot cross workstations. screen boundaries; for example, Device drivers are provided to users cannot drag a window support output to monochrome from one monitor to another. and color displays and to However, users can cut and receive input from keyboard, paste between windows on mouse, and tablet devices. different screens, and windows can be opened on either screen, A display server compatible or both, by user applications. with the X Window System The Dual Monitor Option is receives output requests from a cable and adapter module applications and translates that allows two monitors to be those requests into driver connected at the same time to a commands. They also relay single VAXstation 3100 system driver-generated input events box (models 30, 38, 40, and back to the applications. 48). The Quad Monitor Option Over 400 video fonts are is a cable and adapter module provided in a variety of that allows four monitors to styles and point sizes for be connected at the same time use on 75 and 100 dot per to a single VAXstation 4000 inch (dpi) monitors. These model 60. The system must video fonts have been designed include one of the 8-plane to correspond directly to graphics options, either the the fonts used by Digital's GPX graphics or SPX graphics PostScript printers. In accelerator. addition, a font compiler is 23 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 The system must include at o ANSI X3.26-1980: least one monochrome monitor, Hollerith Punched Card VR150 or VR262, driven by the Code single-plane frame buffer that o ANSI X3.27-1987: File is standard on all VAXstations Structure and Labeling 3100s. VAXstation 4000 model of Magnetic Tapes for 60s do not require a monochrome Information Interchange monitor. o ANSI X3.39-1986: Recorded The second monitor, connected Magnetic Tape (1600 BPI, to the 8-plane graphics option, PE) can be color, or it can be o ANSI X3.40-1983: monochrome for gray scale Unrecorded Magnetic Tape operations. Supported color monitors for the VAXstation o ANSI X3.41-1974: Code 3100s are the VR160, VR290, Extension Techniques for VR297, VR299, and VRT19. Use with 7-bit ASCII Supported color monitors for o ANSI X3.42-1975: the VAXstation 4000 model 60 Representation of Numeric are VRT16, VRT19, and VR320. Values in Character Strings Standards o ANSI X3.54-1986: Recorded The VMS Operating System Magnetic Tape (6250 BPI, is based on the public, GCR) national, and international o ANSI X3.131-1986 (SCSI standards listed below. These I): Small Computer System standards are developed by the Interface American National Standards o ANSI X3T9.2/89-042 (SCSI Institute (ANSI), U.S. Federal II): Small Computer Government (responsible System Interface as for FIPS), Institute of described in REV 10C Electrical and Electronic o ANSI/IEEE 802.2-1985: Engineers (IEEE), and the Logical Link Control International Organization for Standardization (ISO). o ANSI/IEEE 802.3-1985: The following information Carrier Sense Multiple may be useful in determining Access with Collision responsiveness to stated Detection conformance requirements o FIPS 1-2: Code for as enabled in particular Information Interchange, commercial and/or government its Representations, procurement solicitation Subsets, and Extensions documents. Note: 1-2 includes ANSI o ANSI X3.4-1986: American X3.4-1977(86)/FIPS 15; Standard Code for ANSI X3.32-1973/FIPS 36; Information Interchange ANSI X3.41-1974/FIPS 35; o ANSI X3.22-1973: Recorded and FIPS 7 Magnetic Tape (800 BPI, o FIPS 2-1/ANSI 3.6-1965: NRZI) Perforated Tape Code for Information Interchange 24 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 o FIPS 3-1/ANSI X3.22-1973: o FIPS 79/ANSI X3.27-1987: Recorded Magnetic Tape Magnetic Tape Labels Information Interchange and File Structure for (800 CPI, NRZI) Information Interchange o FIPS 13/ANSI X3.21-1967: o FIPS 86/ANSI X3.64-1979: Rectangular Holes in Additional Controls Twelve-row Punched Cards for Use with American o FIPS 14/ANSI X3.26-1980: National Standard Hollerith Punched Card Code for Information Code Interchange o FIPS 16-1/ANSI X3.15- o FIPS 151-1: Portable 1976: Bit Sequencing of Operating System the Code for Information Interface (POSIX 1003.1) Interchange in Serial-by- o Other FIPS not applicable bit Data Transmission o POSIX 1003.1, 1988: Note: FED STD 1010 adopts System application FIPS 16-1 programming interface o FIPS 22-1/ANSI X3.1- o POSIX 1003.2, draft 10: 1976: Synchronous Shell and utilities Signaling Rates Between o POSIX 1003.4, draft 9: Data Terminal and Data Real-time programming Communication Equipment Note: FED STD 1013 adopts Note: Information FIPS 22-1 regarding o FIPS 25/ANSI X3.39- interchangeability of 1986: Recorded Magnetic ANSI and FED standards Tape for Information with FIPS is contained in Interchange (1600 CPI, "ADP Telecommunications Phase Encoded) Standards Index," July 1988, published and o FIPS 26/ANSI X3.18-1967: maintained by the General One Inch Perforated Paper Services Administration. Tape for Information o ISO 646: ISO 7-bit Interchange Coded Character Set for o FIPS 37/ANSI X3.36-1975: Information Exchange Synchronous High Speed o ISO 1001: File Structure Data Signaling Rates and Labeling of Magnetic Between Data Terminal Tapes For Information Equipment and Data Interchange Communication Equipment o ISO 1863: Information Note: FED STD 1001 adopts Processing - 9-track, FIPS 37 12, 7 mm (0.5 in) o FIPS 50/ANSI X3.54- wide magnetic tape for 1986: Recorded Magnetic information interchange Tape for Information recorded at 32 rpmm (800 Interchange, 6250 CPI rpi) (246 CPMM), Group Coded Recording 25 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 o ISO 1864: Information approximately 8,500 additional Processing - Unrecorded blocks. 12, 7 mm (0.5 in) At least 67,000 free blocks wide magnetic tape for are required in order to information interchange - update VMS V5.5 to VMS V5.5- 35 ftpmm (800 ftpi) NRZI, 2. Alternative installation 126 ftpmm (3 200 ftpi) options are available for phase encoded and 356 small operating system disk ftmm (9 042 ftpi), NRZI configurations. Please refer to o ISO 2022: Code Extension the VMS Versions 5.5-2 Update Techniques for Use with Procedures for information ISO 646 concerning these installation o ISO 3307: Representations options. of Time of the Day To support full VMS, a system o ISO 3788: Information disk of greater than 100 MB is Processing - 9-track, recommended. When a smaller 12, 7 mm (0.5 in) disk is used, additional wide magnetic tape for tailoring is required prior to information interchange installing some VMS options. recorded at 63 rpmm (1 This does not include the 600 rpt), phase encoded dump file space. Refer to o ISO 4873: 8-bit Code for VMS Upgrade and Installation Information Interchange - Procedures for information on Structure and Rules for tailoring. Implementation VMS DECwindows Disk Block o ISO 5652: Recorded Requirements Magtape (6250) The disk block size for the o ISO 6429: Control complete VMS DECwindows XUI Functions for Coded environment after installation Character Sets is approximately 68,000 blocks. This is in addition to the VMS Disk Block Requirements 107,600 blocks required for the other components of the VMS Disk Space Requirements (Block Operating System environment. Cluster Size = 2): A subset of the DECwindows The disk block size for the environment can be installed. VMS Operating System, Version For example, programming 5.5-2 after installation is support need not be installed approximately 107,600 blocks. in a user environment. This figure includes 5,600 The following list describes blocks for page and swap files. how many blocks are needed for Most systems will require each section: larger page and swap files. o User environment and This figure also includes applications - 14,000 Help library files that are blocks. This section in data-compressed format. provides support for Most system managers choose to running VMS DECwindows expand these files (for faster applications on VAX access). The expansion requires compute servers. 26 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 o Workstation device than minimum configuration support - 19,000 blocks. requirements to continue to This number includes run VMS. Please refer to the 2,800 blocks for the VMS Installation and Upgrade 75 dpi fonts and 3,900 Manual for details concerning blocks for the 100 dpi the partial installation of the fonts. On 75 dpi systems, VMS DECwindows software. the 100 dpi fonts do not Memory Requirements have to be installed. On 100 dpi systems, both The following tables describe sets of fonts must be the minimum amount of memory installed. required for a system user o Programming support to install, boot, and login - 32,000 blocks to a VMS system. To ensure (approximately 3,500 satisfactory performance of per language). This applications, additional memory number includes support will be required. for all the programming The minimum amount of memory languages. If only a supported for a stand-alone subset of languages is VMS system is 2 MB. This first installed, the amount of table contains the minimum disk space will be less. amount of additional memory o Example files - required for the following approximately 3,000 components to be installed on a blocks. VMS system. Note that the individual sizes _____________________________ add up to more than the total Necessary because some components are Component_______Memory_______ shared by multiple portions of DECnet .5 MB the environment. VAXcluster 1.5 MB To support full VMS and full VMS DECwindows, a system disk DECwindows 1.5 MB of greater than 115 MB is with remote recommended. When a smaller execution of disk is used, additional applications tailoring is required prior to installing some VMS and DECwindows 2.0 MB VMS DECwindows options. with local Refer to the VMS Upgrade and execution of Installation Procedures for applications information on tailoring. _____________________________ The VMS DECwindows software Two example configurations installation is an optional based on the previous table step in the VMS installation are: or upgrade procedure. It has been designed this way to allow users who do not need the VMS DECwindows software to conserve disk space and to allow systems with less 27 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 _____________________________ Minimum DISTRIBUTION MEDIA Supported Compact Disc System__________Memory_______ DECwindows 4.0 MB 9-track 1600 BPI Magnetic tape, with TK50 Streaming Tape applications The VMS Operating System is executing also available as part of remotely, and the VMS Consolidated Software DECnet Distribution on CDROM. DECwindows 6.0 MB The VMS Documentation is also with available as part of the VMS applications Online Documentation Library on executing CDROM. locally, VAXcluster DOCUMENTATION and_DECnet___________________ Extensive documentation Note: These are the minimum is available for VMS. The memory requirements. More documentation is organized memory will be required for into functional subkits, based satisfactory performance on usage. For example, all of the operating system and system management manuals are DECwindows applications. The in one subkit. An easy-to- performance and memory usage use desk-top set of manuals of VMS DECwindows systems is also available for users is particularly sensitive who do not require extensive to system configuration documentation. and window and application Documentation for VMS usage. Remote execution of DECwindows is available in an application requires two different sets. The VMS an additional system DECwindows User Kit is for the that runs the application end user and the VMS DECwindows while the display of the Programming Kit is for the application occurs on the DECwindows software developer. local workstation. In addition, the VMS Online Please refer to specific Documentation Library compact layered product Software disc contains the following Product Descriptions for their VMS documentation, which can memory requirements. be read using the DECwindows Please refer to the VMS Bookreader application: documentation for more o VMS Base Documentation information on performance. Set o VMS Extended GROWTH CONSIDERATIONS Documentation Set The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. 28 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 o VMS DECwindows User Kit Base Documentation Set: and Programmer Kit[1] QA-09SAA-GZ o Selected VMS Layered Extended Documentation Set: Product Documentation QA-001AA-GZ DECwindows User Kit Documentation:[1] ORDERING INFORMATION QA-09SAB-GZ This section contains order DECwindows Programmers Kit numbers for VMS media, Documentation: licenses, documentation, and QA-001AM-GZ services. VMS Online Documentation Library on Compact Disc: ORDERING INFORMATION This QA-VYR8A-G8 section contains order numbers [1]Included in both VMS Base for OpenVMS media, licenses, Documentation and Extended documentation, and services. Documentation Sets. Software Licenses QL-001A*-** VAX VMS Software Product Services Operating System License Software Support Service:[2] for OpenVMS QT-001A*-** VAX VMS QL-005A*-** OpenVMS O/S Base Operating System Software License Support Service for OpenVMS QL-XULA*-** OpenVMS QT-005A*-** OpenVMS O/S Base Interactive User License Software Support Service Media and Documentation QT-XULA*-** OpenVMS Interactive User Software With Base Documentation Set: Support Service QA-09SA*-H* [2]A variety of integrated With Extended Documentation and a la carte Hardware Set: QA-001A*-H* and Software Products are Additional Media available. For additional VMS Consolidated Software information, please contact Distribution on your local office. CDROM: QA-VWJ8A-A8 Media and Documentation Update Additional Documentation Service Sets With Base Documentation Set: __________ QT-09SA*-E* [1] With the exception With Extended Documentation of the Adobe PostScript Set: QT-001A*-E* Documentation, which is not available online Additional Media Update Service VMS Consolidated Software Distribution on CDROM: QT-VWJ8A-C8 Documentation Only Update Service 29 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Base Documentation Set: Customers who wish to run QT-09SAA-KZ DECwindows over TCP/IP need Extended Documentation Set: only purchase the VMS/ULTRIX QT-001AA-KZ Connection product media and VMS Online Documentation documentation kit. A separate Library on Compact Disc: license is not required. QT-VYR8A-C8 Customers who want to utilize The Software Media and Extended the full VMS/ULTRIX Connection Documentation Set (QA-001A*- functionality (FTP, NFS, H*) is recommended for users TELNET) do need to purchase a managing high-end VAX systems, separate license. Refer to the e.g., VAX 6000 610, VAXcluster VMS/ULTRIX Connection System systems, or DECnet-VAX Support Addendum (SSA 25.A4.xx- networks. The Software Media x) for required versions. and Base Documentation Set Please see the Third Party (QA-09SA*-H*) is recommended Licensing section in Appendix C for managers of small stand- for information regarding the alone systems and for general Adobe licensing. end-users. The System Integrated Products * Denotes variant (SIPs), VAXcluster Software fields. For additional (SPD 29.78.xx), DECnet-VAX (SPD information on available 25.03.xx), VAX Volume Shadowing licenses, services, (SPD 27.29.xx), and VAX RMS and media, refer to the Journaling (SPD 27.58.xx) appropriate price book. are separately licensed products. Please refer to the SOFTWARE LICENSING appropriate product's SPD for more information. The VMS software is furnished Software License Information under the licensing provisions of Digital's Standard Terms and The VMS Operating System uses Conditions. one of two different categories Digital offers a separately of licenses depending on orderable layered product the hardware and software called VMS DECwindows Motif. configurations used and Refer to the VMS DECwindows currently supported. This Motif SPD (SPD 36.09.xx) for information is also provided more information. in the applicable country's Price List. Integral to VMS is support These are the two categories of for the VMS DECwindows desktop Operating System licenses for environment, which is delivered OpenVMS: as a component of the VMS Operating System, requiring 1. VAX VMS Licensing no separate license. 2. OpenVMS Licensing Digital provides the proper license type with the purchase of the system. Not all VMS license types are available for all system models. VAX VMS License Information 30 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 The VAX VMS licenses include This type of license provides the rights for the VAX use for a single user on a VAX Rdb/VMS Run-Time Option. Workstation. This allows the running of an 4. File and Application application developed using Server License (QL-001A*- VAX Rdb/VMS. However, VAX **) Rdb/VMS has separate media and documentation. In addition, This type of license provides should a user want to perform for the non-interactive use of Rdb development, a separate OpenVMS. license must be purchased. OpenVMS-based VAXservers Refer to SPD 25.59.xx for are sold with a File and further information. Application Server License. There are four types of VAX VMS The intent of an OpenVMS-based licenses: VAXserver is to provide file, 1. Traditional License (QL- print, application, and compute 001A*-**) "services" to "clients" who have remotely submitted their This type of license provides requests (for example via unlimited use to the users network/remote submit/batch on a defined system. VAX VMS jobs, etc.). traditional licenses are sized The software licensing to capacity according to system stipulates that no direct type. operating system log-ons by 2. Multi-user License (QL- users are permitted on the 001A*-**) OpenVMS-based VAXserver. One direct log-on is allowed for This type of license provides system management purposes use according to a specified only. number of concurrent users. While remote submission of This is an activity-based OpenVMS-based applications license. The Multi-user License for execution on a OpenVMS- provides the customer with based VAXserver is allowed, the right to use the operating interactive use (direct system up to the limit of users log-on and execution) specified in the license. An of OpenVMS-based layered operating system "User" is products is prohibited. a person who is logged onto All VAX VMS licenses the system and/or is using provide the right to the system interactively. use only the OpenVMS Interactive use of the features, functionality, and operating system includes the facilities provided by the display of information upon current version license. Any any video or hardcopy display features, functionality, and product whether in a DECwindows facilities not specifically /X Windows environment or licensed in the purchased otherwise. This license is only version of OpenVMS may available on limited system not be used if a prior models, primarily Micro/VAX and version kit containing VAX 4000 systems. such unlicensed features 3. VAX VMS Workstation is installed. License (QL-001A*-**) 31 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Not all VAX VMS license 2. OpenVMS Interactive User types are available for all License (QL-XULA*-**) versions of VMS, OpenVMS or The OpenVMS Interactive User all VAX models. License provides the right to OpenVMS License Information interactively use the operating There are two types of system by the specified, or OpenVMS licenses: unlimited, number of concurrent users, on a designated, 1. OpenVMS O/S Base License single processor. A user is (QL-005A*-**) an individual who is logged OpenVMS O/S Base License grants on to a processor and/or the right to unrestricted, non- is interactively using the interactive use of the OpenVMS operating system software by Operating System for the means other than login. An execution of remotely submitted OpenVMS O/S Base License is requests for batch, print, a prerequisite to the OpenVMS application, and computing Interactive User License. services, on a designated, This license grants the right single processor. to use the same version No direct OpenVMS operating of the operating system system log-ons by users are that is permitted under the permitted on the system. One corresponding O/S Base License direct log-on is allowed for at the time of the initial system management purposes installation of the Interactive only. User License. The OpenVMS Base License In-cabinet upgrades are does not include the license supported with OpenVMS right for the VAX Rdb/VMS licensing. When upgrading Run-Time Option. The Rdb/VMS a processor, the customer Run-Time License is available is required to upgrade the separately. operating system licenses. For OpenVMS, this is accomplished Interactive use of systems with a BASE upgrade license licensed with an OpenVMS O that upgrades the O/S BASE /S Base License requires license and permits the use of the addition of an OpenVMS all "specified quantity" (e.g., Interactive User License (for 4 user) interactive licenses one or more users). on the processor. For unlimited The OpenVMS O/S Base License user licenses, an additional provides the right to use upgrade license for Unlimited only the OpenVMS features, Interactive User is required. functionality, and facilities The OpenVMS O/S Base and provided by the current Interactive Use licenses are version. Any features, not supported by VMS or OpenVMS functionality, and facilities operating system releases prior not specifically licensed to OpenVMS Version 5.5. in the purchased version of OpenVMS may not be used if a prior version kit containing such unlicensed features is installed. 32 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Digital provides the proper o A remote network license type with the purchase connection that is of the system. Not all OpenVMS a connection other license types are available for than a remote terminal all system models. connection, is not License Management Facility considered an activity. Support For more information about The VMS Operating System Digital's licensing terms and supports the License Management policies, contact your local Facility. Digital office. If no VMS license is registered SOFTWARE PRODUCT SERVICES and activated using the License Management Facility, then a A variety of service options single login is permitted for are available from Digital. For system management purposes more information, contact your through the system console local Digital office. (OPA0:). Several of the VAX VMS and SOFTWARE WARRANTY OpenVMS license types are based Warranty for this software on the number of concurrent product is provided by Digital users, called an activity with the purchase of a license license. Every product has the for the product as defined in option to define an activity the Software Warranty Addendum as related to the License of this SPD and the applicable Management Facility. OpenVMS Digital Standard Terms and defines activities, sometimes Conditions. referred to as an OpenVMS "user," as follows: o Each remote terminal SUPPORTED HARDWARE FOR VMS, VMS connection is considered DECwindows, VAXcluster, and an activity. This is true DECnet-VAX even if you set host to This section of the SPD your local node (SET HOST contains four parts: Hardware 0). Charts, Appendix A, Appendix B, o Each connection from and Appendix C. a terminal server is The charts list the hardware considered an activity. that VMS, VMS DECwindows, o A multiple-window session DECnet-VAX, and VAXcluster on a workstation is Software supports. Combinations considered one activity, of hardware options are regardless of the number subject to limitations of windows. such as bandwidth, physical o A batch job is not configuration constraints, considered an activity. and electrical load and power supply. Appendix A describes system- specific restrictions for the configurations listed. 33 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Appendix B describes Digital The second column lists the terminals, disks, tapes, disk controllers and drives controllers, communications that can be used on the system. options, and VAXcluster A disk controller can be used options. Some restrictions with any disk drive listed for specific devices are listed next to it: for example, on if applicable. a Micro/VAX II or VAXstation The content of this hardware II system the RQDX3 disk configuration appendix is controller can be used with intended to specify the an RD52, RD53, RD54, RX50, or device limitations and provide RX33 disk drive. a general guide. It does The third column lists the tape not describe all possible controllers and drives that can hardware configurations or be used on the system. The tape circumstances. Any particular controller can be used with any configuration should be tape drive listed next to it: discussed with Digital. Contact for example, on a Micro/VAX II Digital for the most up-to- or VAXstation II system, the date information on possible TQK50 controller can be used hardware configurations. with the TK50 tape drive. Digital reserves the right The fourth and fifth columns to change the number and type list the communications and of devices supported by VMS, VAXcluster options available VMS DECwindows, DECnet-VAX, for the systems. The listed and VAXcluster Software. The Ethernet devices can also be minimum hardware requirements used for network connections. for future versions and updates The sixth column lists other of VMS, VMS DECwindows, hardware that can be used and DECnet-VAX, and VAXcluster the maximum amount of memory Software may be different from allowed on the systems in each current hardware requirements. category. For configuration details about VAX hardware, refer to the VAX System and Options Catalog and the Networks and Communications Buyers Guide. Refer to the individual SPDs for DECnet-VAX (SPD 25.03.xx) and VAXcluster Software (SPD 29.78.xx) for detailed product information. How to Read the Charts The first column lists the VAX system, the media (tape, disk, or compact disc) from which the VMS Operating System can be loaded onto the system disk, and the maximum number of busses supported on the system. 34 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ Micro/VAX KDA50 RA- TQK50 TK50 Asynch-CXA16*+ DEQNA DRV11- II, RQDX2 series* TK70 DELQA WA* VAXstation TQK70 TS05 CXB16*+ DESQ# LPV11 II RD51 TU81- VCB01- RD52 TSV05 Plus* CXY08* KP (Load RQDX3 RD53 RV20* DZV11 (VsII) Media) RX50 KLESI DHV11* VCB02- TK50 RD52 DHQ11 B Magtape RD53 DZQ11 (VsII RX33## RD54 Synch- /GPX) CDROM KRQ50 RX50 DMV11 VCB02- RX33 DSV11 D (BUSSES) KLESI RRD50 (VsII KFQSA RRD40 /GPX) 1 Q-bus RC25 RQDXE 2 (DSSI) DSSI** RF30 16 RF71 MB Max Mem * Can be used on a Micro/VAX II system only. ** Only available via the KFQSA. + DECnet-VAX does not support these options. # Only available with BA200-series enclosures. ## VMS distribution on this media has been retired. Supports_Display_PostScript._______________________________________ Micro/VAX IntegralRD32 TZK50 TK50 Asynch-DST32*+ Integral VS40X 2000 RD53 (Vs2000) VAXstation RD54 DSH32 2000 RX33 Synch- DST32*+ 14 (Load MB Max Media) DSH32* Mem TK50 RX33# (BUSSES) N/A * Can be used on a Micro/VAX 2000 system only. # VMS distribution on this media has been retired. + Concurrent use of the DST32 and the DHT32 is not supported. Supports Display PostScript. ___________________________________________________________________________ 35 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ Micro/VAX IntegralRX23 TKZ50 TK50Z DSH32 Integral 32 MB 3100 RZ23 TZ30 Max VAXserver RZ24 TLZ04 (1 Mem 3100 RZ25 TZK10 sync. Models RZ55 & 8 10/10e RZ56 async. 20/20e RZ57 lines) RRD40 (Load RRD42 Media*) RX26 TK50 RZ23L CDROM (BUSSES) Integral SCSI * Factory-loaded software on all configurations that include RZ23L, RZ24, and RZ25 internal disks. ___________________________________________________________________________ 36 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ *Micro/VAXIntegralRX33+ TK50Z+ DHW41- Integral Models 3100 RZ24 TZ30 AA 30/40 Models RZ25 TLZ04+ DHW41- 32 MB 30/40 RZ55+ TZK10 BA Max /80/90 RZ56+ TZ85+ DHW42- Mem RZ57+ AA (Load RZ58+ DHW42- Model Media*) RRD42 BA 80 TK50 RZ26 DHW42- 72 MB CDROM RX26 UP Max TZ85 RZ23L DHW42- Mem RZ24L CA (BUSSES) DSW41- Model AA 90 Integral DSW42- 128 AA MB Max SCSI Mem *Factory-loaded software on all configurations that include RZ24L, RZ25 and RZ26 internal disks +External_device_only______________________________________________ VAXstationIntegralRZ22 IntegraTK50Z Integral WS01X 3100 RZ23 TZ30 VCB02 Series RZ24 Graph- RZ55 ics (Load RZ56 VS40X- Media) RRD40 PA TK50 RX23 Graph- CDROM ics Coprocessor (BUS) SCSI 32 MB Max Mem Supports Display PostScript. ___________________________________________________________________________ 37 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAXstationRQDX3 RD53 TQK50 TK50 Asynch-DHV11 DELQA Graphics 3200 RD54 TS05 DZQ11 Sub- KRQ50 RRD40 TSV05 system (Load RRD50 DSV11 for Media) Synch- the TK50 Vs3200 CDROM 32MB (BUS) Max 1 Q-bus Mem Supports Display PostScript. ___________________________________________________________________________ 38 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ Micro/VAX IntegralRF30 TQK70 TK70 Asynch-CXA16+ 52 MB 3300 RF31 TK50 CXB16+ Max /3400 RF31F TQK50 TF85 CXY08 Mem VAXserver RF71 TF857 3300 KFQSA RF72 KFQSA TS05 DSV11 /3400 RRD40 TU81- Synch- KRQ50 RRD50 Plus (Load RRD42 TSV05 Media) KZQSA TLZ04 TK50 RA- KLESI CDROM KDA50 series Magtape (BUSSES) 1 DSSI* 1 Q-bus * Second DSSI available only via the KFQSA. + DECnet-VAX does not support these options. Note: Refer to the Systems and Options Catalog for listing of supported Q-bus_options._____________________________________________________ 39 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Micro/VAX RQDX3 RD53* TQK70 TK70 Asynch-CXA16+ DELQA Graphics 3500 RD54* TK50 CXB16+ DESQA Sub- VAXserver KDA50 RA- TQK50 TS05 CXY08 system 3500 KRQ50 series TF85 for VAXstation RRD40 TSV05 TF857 DSV11 the 3500 KZQSA RRD50 TU81- Synch- Vs3500 RRD42 Plus (Load KFQSA TLZ04 64MB Media) RF30 KFQSA Max TK50 RF31 Mem Magtape FR31F KLESI CDROM RF71 RF72 RV20 (BUSSES) 1 Q-bus 1 DSSI ** * Available on Micro/VAX 3500 system only. + DECnet-VAX does not support these options. ** Only available via the KFQSA. Supports Display PostScript. Note: Refer to the Systems and Options Catalog for listing of supported Q-bus options. ___________________________________________________________________________ VAXstationI/O RZ55 TQK70 TK70 Asynch-CXA16+ Integral Graphic 3520 Adapter RZ56 CXB16+ Subsys- VAXstation RRD40 CXY08 3540 tem DSV11 for (Load Synch- the Media) Vs3520 TK50 /3540 CDROM VCB03 op- (BUSSES) tional graph- 1 SCSI ics 1 Q-bus 64MB Max Mem Supports Display PostScript. + DECnet-VAX does not support these options. Note: Refer to the Systems and Options Catalog for listing of supported Q-bus options. ___________________________________________________________________________ 40 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ Micro/VAX KDA50 RA- TQK70 TK70 Asynch-CXA16+ DELQA 64 MB 3600 KRQ50 series TK50 CXB16+ DESQA Max VAXserver RRD40 TQK50 TS05 CXY08 Mem 3600 KZQSA RRD50 TU81- VAXserver RRD42 TSV05 Plus DSV11 3602 KFQSA TLZ04 RV20 Synch- RF30 KLESI TF85 (Load RF31 TF857 Media) RF31F KFQSA TK50 RF71 Magtape RF72 CDROM (BUSSES) 1 Q-bus 1 DSSI** + DECnet-VAX does not support these options. ** Only available via the KFQSA. Note: Refer to the Systems and Options Catalog for listing of supported Q-bus_options._____________________________________________________ Micro/VAX KFQSA RF30 TQK70 TK70 Asynch-CXA16+ DESQA 64 MB 3800 RF31 TK50 CXB16+ DELQA Max VAXserver RF31F TQK50 TS05 CXY08 Mem 3800 RF71 TU81- RF72 TSV05 Plus DSV11 (Load KRQ50 RRD40 TF85 Synch- Media) RRD50 KLESI TF857 TK50 KZQSA RRD42 CDROM TLZ04 KFQSA KDA50 RA- (BUSSES) series 1 Q-bus 1 DSSI* * Only available via the KFQSA. + DECnet-VAX does not support these options. Note: Refer to the Systems and Options Catalog for listing of supported Q-bus options. ___________________________________________________________________________ 41 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Micro/VAX KDA50 RA- TQK70 TK70 Asynch-CXA16+ DESQA 64 MB 3900 KRQ50 series TK50 CXB16+ DELQA Max VAXserver RRD40 TQK50 TU81- CXY08 Mem 3900 KZQSA RRD50 Plus RRD42 KLESI TS05 DSV11 (Load KFQSA TLZ04 TF85 Synch- Media) RF30 TSV05 TF857 TK50 RF31 CDROM RF31F KFQSA Magtape RF71 RF72 (BUS) 1 Q-bus 1 DSSI* * Only available via the KFQSA. + DECnet-VAX does not support these options. Note: Refer to the Systems and Options Catalog for listing of supported Q-bus options. ___________________________________________________________________________ 42 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAXstationIntegralRZ22 IntegraTK50Z Synch- DSW21 Integral PV21X, 4000* RZ23 TZ30 DWCTX- PV61G Models RZ23L TZK10 BX (Ethernet(Model 60/VLC RZ24 TLZ04 60) RZ24L TLZ06 Graph- (Load RZ25 ics Media) RZ55 PV31G TK50 RZ56 (VLC) CDROM RRD40 Graph- RX23 ics (BUS) RZ57 PMAZ SCSI RZ58 VSXXX- RX26 AA, RX33 VSXXX- RRD42 GA mouse VSX10, VSX20, VSX30 dial box LK201 LK401 VSXXX- AB (tablet) VSXXX- JA (head- set) VLC 24 MB Max Mem Model 60 104 MB Max Mem *Factory-loaded software on all configurations that include internal disks (RZ24, and RZ25) Supports Display PostScript. ___________________________________________________________________________ 43 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 *VAXstatioIntegralRZ23 IntegraTK50Z Synch- DSW21- Integral 4000 RZ24 TZ30 AA,AB,AC, PV71G- Model RZ24L TZK10 (EthernetAA 90 RZ57 TLZ04 - PV71G- RZ58 TLZ06 AD,AE,AF BA (Load RWZ01 PV71G- Media) RRD42 CA TK50 LCSPX CDROM SPXg /gt (BUS) DWCTX- SCSI BX VSXXX- AA, VSXXX- GA mouse VSX10, VSX20, VSX30 dial box LK201 LK401 VSXXX- AB (tablet) VSXXX- JA (head- set) Model 90 128 MB Max Mem *Factory-loaded software on all configurations that include internal disks (RZ24L, and RZ25) Supports Display Postscript. 44 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX-11 UDA50 RA- TS11 TS11 Asynch-DMF32 DEUNA+ CR11 /730 RK711 series TUK50 TU80 DZ11 DELUA+ DR11-W RL211 RK07 TU81 DZ32 DMF32- (Load RX211 RL02 KLESI TU81- DMZ32 LP Media) RUX50 RX02 Plus DHU11 LP11 RL02* (IntegraRX50 LPA11 Magtape DMF32 FP730 IDC RL02 Synch- DMR11 (BUS) R80 5 1 MB Max UNIBUS Mem * VMS distribution on this media has been retired. + VAX-11/730 systems are not supported in VAXcluster systems. ___________________________________________________________________________ ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX-11 UDA50 RA- TS11 TS11 Asynch-DMF32 DEUNA DMF32- /750 RK711 series KLESI TU80 DZ11 DELUA LP RL211 RK07 TU81 DZ32 (CI) DR11-W (Load RX211 RL02 TU81- DMZ32 CI750 DR750 Media) KLESI RX02 Plus DHU11 DW750 RL02* RUX50 RC25 RV20 FP750 RK07* RX50 TUK50 TK50 DMF32 H7112 RA60* RM03 TA- Synch- DMR11 KU750 Magtape RM05 series LPA11 RM80 (CI) RH750 (BUSSES) RP06 HSC LP11 (CI) RP07 TM03 TE16 2 HSC TM78 TU77 14 UNIBUS ESE-20 TU78 MB Max 3 MASS- RA- Mem BUS series * VMS is not distributed on this media type. ___________________________________________________________________________ 45 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX-11 UDA50 RA- TS11 TS11 Asynch-DMF32 DEUNA DM32- /780 RK711 series KLESI TU80 DZ11 DELUA FP VAX-11 RL211 RK06 TU81 DMZ32 (CI) DR11-W /785 RX211 RK07 TU81- DHU11 CI780 DR780 KLESI RL02 Plus DW780 (Load RUX50 RX02 RV20 DMF32 H7112 Media) RC25 TUK50 TK50 Synch- DMR11 FP780** RK07* RX50 TA- RA60* RM03 series FP785*** Magtape RM05 (CI) RM80 HCS KE780** (BUSSES) RP05 TM03 TE16 RP06 TM78 TU45 KU780** 4 (CI) RP07 TU77 UNIBUS HCS TU78 RH780 4 MASS- ESE-20 LP11 BUS RA- series 64 MB Max Mem * VMS is not distributed on this media. ** These options are used on the VAX-11/780 only. ***_Used_on_the_VAX-11/785.________________________________________ VAXft KFE52 RF31 KFE52 TF70 Synch- DSF32 Integral 128 Models RF72 MB Max 110/310 Mem (Load Media) TK50 CDROM via InfoS- erver (Busses) 2 DSSI ___________________________________________________________________________ 46 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAXft KFE52 RF31 KFE52 TF70 Synch- DSF32 Integral 256 Models RF72 TF85 MB Max 410/610 RF73 (Model TF857 Mem / 610 612 /612 only) (Load Media) KFQSA TK50 CDROM via InfoS- erver (Busses) 2 DSSI ___________________________________________________________________________ 47 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX IntegralRF30 IntegraRSV20 Asynch-DHW42- Integral 128 4000 & RF31 TF85 AA MB Max Model KFQSA RF31F KZQSA TF857 DHW42- DELQA Mem 100 RF31T TZK10 BA DESQA RF35 KFQSA TZ30 DHW42- (Load RF71 TLZ04 Synch- UP Media) RF72 TSV05 TLZ06 DHW42- TK50 RF73 TS05 CA CDROM KDA50 RA- KLESI TSZ07 DSW42- KRQ50 series TU81- AA (BUS) KZQSA RRD40 Plus 1 Q-bus RRD42 2 DSSI RWZ01 RX26 Note: Factory loaded software on all configurations that contain a disk. ___________________________________________________________________________ VAX IntegralRF30 TQK50 RSV20 Asynch-CXA16+ Integral 64 MB 4000 & RF31 TF85 CXB16+ Max Model KFQSA RF31F TQK70 TF857 CXY08 DELQA Mem 200 RF35 TLZ04 DESQA RF71 TSV05 TS05 DPV11 (Load RF72 TSZ07 Synch- DSV11 Media) RF73 KLESI TK50 TK50 RA- TK70 CDROM KDA50 series KZQSA TU81- KRQ50 RRD40 Plus (BUS) KZQSA RRD42 Integral 1 Q-bus & 4 DSSI KFQSA Note: Factory loaded software on all configurations that contain a disk. ___________________________________________________________________________ 48 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAX IntegralRF30 TQK70 TK70 Asynch-CXA16+ Integral 256 4000 & RF31 TS05 MB Max Model KFQSA RF71 TQK50 TU81- CXB16+ DESQA Mem 300 RF31F Plus Synch- CXY08 DELQA RF72 TSV05 TK50 DSV11 (Load RF73 RSV20 DPV11 Media) RF25 KLESI TLZ04 TK50 RA- TSZ07 CDROM KDA50 series KZQSA TF85 KRQ50 TF857 (BUS) KZQSA RRD40 Integral 1 Q-bus RRD42 & 4 DSSI KFQSA Note: Factory loaded software on all configurations that contain a disk. ___________________________________________________________________________ 49 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX IntegralRF30 TQK50 RSV20 Asynch-CXA16+ Integral 512 4000 & RF31 TF85 MB Max Model KFQSA RF31F TQK70 TF857 CXB16+ DELQA Mem 400 RF31T TLZ04 Synch- CXY08 DESQA RF35 TSV05 TS05 DPV11 (Load RF71 TSZ07 DSV11 Media) RF72 KLESI TK50 TK50 RF73 TK70 CDROM KDA50 RA- KZQSA TU81- KRQ50 series Plus (BUS) KZQSA RRD40 IntegraTLZ06 1 Q-bus RRD42 & 4 DSSI RWZ01 KFQSA Note: Factory loaded software on all configurations that contain a disk. ___________________________________________________________________________ VAX IntegralRF30 TQK50 RSV20 Asynch-CXA16+ Integral 512 4000 & RF31 TF85 MB Max Model KFQSA RF31F TQK70 TF857 CXB16+ DELQA Mem 500 RF31T TLZ04 Synch- CXY08 DESQA RF35 TSV05 TS05 DPV11 (Load RF71 TSZ07 DSV11 Media) RF72 KLESI TK50 TK50 RF73 TK70 CDROM KDA50 RA- KZQSA TU81- KRQ50 series Plus (BUS) KZQSA RRD40 IntegraTLZ06 1 Q-bus RRD42 & 4 DSSI RWZ01 KFQSA Note: Factory loaded software on all configurations that contain a disk. ___________________________________________________________________________ 50 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAX IntegralRF30 TQK50 RSV20 Asynch-CXA16+ Integral 512 4000 & RF31 TF85 MB Max Model KFQSA RF31F TQK70 TF857 CXB16+ DELQA Mem 600 RF31T TLZ04 Synch- CXY08 DESQA RF35 TSV05 TS05 DPV11 (Load RF71 TSZ07 DSV11 Media) RF72 KLESI TK50 TK50 RF73 TK70 CDROM KDA50 RA- KZQSA TU81- KRQ50 series Plus (BUS) KZQSA RRD40 IntegraTLZ06 1 Q-bus RRD42 & 4 DSSI RWZ01 KFQSA Note: Factory loaded software on all configurations that contain a disk. ___________________________________________________________________________ 51 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX 6000- KDB50 RA- KLESI TU81- Asynch-DMB32 DEBNA LP11* 200 KDM70 series Plus DHB32 DEBNI DMB32- Series+ TM32 TBK50 RV20 DEMNA LP VAXserver (CI) TK50 DMB32 DEMFA DR11-W* 6000- HSC TBK70 TK70 Synch- DSB32 (CI) 210 ESE-20 CIBCA- DWMUA* VAXserver RA- TA- AA DRB32 6000- series (CI) series CIBCA- 220 HSC BA KDM70 CIXCD- 512 (Load AB MB Max Media) Mem TK50 Magtape CDROM via InfoS- erver (BUSSES) 6 VAXBI 1 UNIBUS 2 VME (DWMVA) KFMSA + Formerly named the VAX 6210, 6220, 6230, 6240. * Supported on the VAX 6000-210 and VAX 6000- 220_systems_only.__________________________________________________ 52 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAX 6000- KDB50 RA- KLESI TU81- Asynch-DMB32 DEBNA LP11* 300 KDM70 series Plus DHB32 DEBNI DMB32- Series+ TM32 TBK50 TK50 DEMNA M VAXserver (CI) TK70 DMB32 DEMFA DR11-W* 6000- HSC TBK70 Synch- DSB32 (CI) 310/320 ESE-20 TA- CIBCA- DRB32 RA- (CI) series AA DWMUA* (Load series HSC CIBCA- Media) KDM70 BA 512 TK50 CIXCD- MB Max Magtape AB Mem CDROM via InfoS- erver (BUSSES) 6 VAXBI 1 UNIBUS* 2 VME (DWMVA) KFMSA + Formerly named the VAX 6310, 6320, 6330, 6340, 6360. * Supported on the VAX 6000-310 and VAX 6000- 320 systems only. ___________________________________________________________________________ 53 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX 6000- KDB50 RA- KLESI TU80- Asynch-DMB32 DEBNA LPA11 400 KDM70 series Plus DHB32 DEBNI DR11-W Series TM32 TBK70 TK70 DEMNA FV64A VAXserver TK50 DMB32 DEMFA DMB32 6000- TBK50 Synch- DSB32 (CI) DRB32 410/420 TA- CIBCA- (CI) series BA 512 (Load HSC CIXCD- MB Max Media) AB Mem TK50 Magtape CDROM via InfoS- erver (BUSSES) 6 VAXBI 1 UNIBUS 2 VME (DWMVA) KFMSA______________________________________________________________ 54 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAX 6000- KDB50 RA- KLESI TU80- Asynch-DMB32 DEBNA FV64A 500 KDM70 series Plus DHB32 DEBNI DMB32 Series TM32 TBK70 TK70 DEMNA DRB32 VAXserver TK50 DMB32 DEMFA 6000- TBK50 Synch- DSB32 (CI) 512 510/520 TA- CIBCA- MB Max (CI) series BA Mem (Load HSC CIXCD- Media) AB TK50 Magtape CDROM via InfoS- erver (BUSSES) 6 VAXBI 2 VME (DWMVA) KFMSA ___________________________________________________________________________ VAX 6000- KDB50 RA- KLESI TU80- Asynch-DMB32 DEBNA DMB32 600 KDM70 series Plus DHB32 DEBNI DRB32 Series TM32 TBK70 TK70 DEMNA TK50 DMB32 DEMFA 512 (Load TBK50 Synch- DSB32 (CI) MB Max Media) TA- CIBCA- TK50 (CI) series BA Magtape HSC CIXCD- CDROM AB via InfoS- erver (BUSSES) 6 VAXBI 2 VME (DWMVA) KFMSA ___________________________________________________________________________ 55 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX 8200 KDB50 RA- KLESI TU81- Asynch-DHB32 DEBNA DMB32- (CI) series Plus DMB32 DEBNI LP VAX 8250 HSC TM32 RV20 DHU11 DELUA DR11-W ESE-20 TS11 RV64 DMF32 (CI) DWBUA RA- TUK50 TU80 DMZ32 CIBCA- DRB32 (Load series TU81 AA LP11 Media) TBK50 TU81- DMB32 CIBCA- Magtape Plus Synch- DSB32 BA 128 RA60* CIBCI MB Max TK50 (CI) TK50 Mem HSC TA- (BUSSES) series 1 VAXBI 1 UNIBUS * VMS Operating System is not distributed on RA60_media.________________________________________________________ VAX 8300 KDB50 RA- KLESI TU81- Asynch-DHB32 DEBNA DMB32- (CI) series Plus DMB32 DEBNI LP VAX 8350 HSC TM32 RV20 DHU11 DELUA DR11-W ESE-20 TS11 RV64 DMF32 (CI) DWBUA RA- TUK50 TU80 DMZ32 CIBCA- DRB32 (Load series TU81- AA LP11 Media) TBK50 Plus DMB32 CIBCA- Magtape Synch- DSB32 BA 128 RA60* (CI) TK50 CIBCI MB Max TK50 HSC TA- Mem series (BUSSES) 1 VAXBI 1 UNIBUS * VMS Operating System is not distributed on RA60 media. ___________________________________________________________________________ 56 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAX KDB50 RA- KLESI TU81- Asynch-DHB32 DEBNA DMB32- 85xx (CI) series Plus DMB32 DEBNI LP HSC RV20 DHU11 DELUA DR11-W (Load ESE-20 RV64 DMF32 (CI) DWBUA Media) RA- (CI) DMZ32 CIBCA- DRB32 Magtape series HSC TA- AA LP11 series DMB32 CIBCA- (BUSSES) Synch- DSB32 BA 256 CIBCI MB Max 2 VAXBI Mem 1 UNIBUS ___________________________________________________________________________ 57 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX 8600 UDA50 RA- TS11 TS11 Asynch-DMF32 DEUNA DMF32- RL211 series KLESI TU80 DZ11 DELUA LP VAX RX211 RL02 TU81 DZ32 (CI) DR11-W 8650 RUX50 RX02 TUK50 TU81- DMZ32 CI780 DR780 KLESI RX50 Plus DHU11 DW780 (Load RC25 FP86- Media) RM03 (CI) RV20 DMF32 AA Magtape RM05 HSC TK50 Synch- DMR11 RH780 RM80 TA- (BUSSES) RP05 series 260 RP06 TM03 TE16 MB Max 7 (IntegraRP07 RM78 TU77 Mem UNIBUS IDTC TU78 6 MASS- (CI) RA60 IDTC TU81 BUS HSC RA80 2 SBI RA81 RA82 ESE-20 RA- __________________series___________________________________________ VAX KD850 RA- KLESI TU81- Asynch-DHB32 DEBNA DMB32- 8700 (CI) series Plus DMB32 DEBNI LP VAX HSC RV20 DMF32 DELUA DR11-W 8800 ESE-20 RV64 DMZ32 (CI) DRB32 RA- (CI) CIBCA- DWBUA (Load series HSC TA- DMB32 AA LP11 Media) series Synch- DSB32 CIBCA- Magtape BA 512 CIBCI MB Max (BUSSES) Mem 4 VAXBI 2 UNIBUS ___________________________________________________________________________ 58 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 VAX KD850 RA- KLESI TU81- Asynch-DMB32 DEBNA DMB32- 8810* (CI) series Plus DHB32 DEBNI LP VAX HSC RV20 (CI) DR11-W 8820 ESE-20 RV64 DMB32 CIBCA- DWBUA VAX RA- Synch- DSB32 AA DRB32 8830 series CIBCA- LP11 VAX BA 8840 CIBCI** 512 MB Max (Load Mem Media) Magtape (BUSSES) 6 VAXBI 1 UNIBUS * The VAX 8810 can support a maximum of 4 VAXBIs. ** Supported only on the VAX 8810. ___________________________________________________________________________ 59 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 ___________________________________________________________________ Options Miscellaneous System Disks Tapes Communication (LAN _______________ ______________ (WAN) /CI) __________CTRL____DRIVE____CTRL___DRIVE____________________________ VAX 9000- KDM70 RA- KLESI RV20 Asynch-DMB32 DEMNA DRB32- 110/210 (6 series RV64 (2 (4 M/-E VAX 9000- max) ESE-20 (2 TA- max) max) /-W/-C 310/410 (CI) max) series FDDI- DHB32 (CI) (2 HSC ESE-20 RF- (2 CIXCD max) (Load RA- KDM70 series max) (4 DWMBB- Media) series TF- DEMFA max) HA/-CA Magtape KFMSA series (4 DEBNI /-JA CDROM max) (3 (VAXBI via (2 Synch- max) EXP) InfoS- max) DMB32 KDB50 erver DSB32 (2 max) (BUSSES) DSB32- M 1 XMI (2 4 VAXBI max) 512 MB Max Mem ___________________________________________________________________________ NOTE: The VMS software that runs on the Micro/VAX console subsystem is licensed for use only with standard console activities. No other use is intended_or_implied._______________________________________________ 60 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Appendix A The VAX-11/730 system supports This appendix describes some one UNIBUS magnetic tape restrictions to the system subsystem. configurations listed in the Refer to the Hardware System charts. See the VAX System and and Options Catalog for the Options Catalog and the Network different hardware options and Communications Buyers Guide supported on these systems. for details of VAX hardware The VMS DECwindows environment configurations. is not supported on these Micro/VAX I/VAXstation I systems. Systems The final version of VMS that supports these systems is VMS V5.1-1. Micro/VAX II System The CX-series boards and DESQA controller can be used in a BA213 cabinet only. Micro/VAX 2000 and VAXstation 2000 Systems DECnet-VAX supports only one asynchronous data/modem RS- 232C serial line up to 9600 baud on the integral 4 line asynchronous controller. VAXserver 3602 System The VAXserver 3602 is two VAXserver 3600 systems. VAX-11/725 VMS V5.1 was the final version to support the VAX-11/725. VAX-11/730 System The VAX-11/730 system supports additional memory to a maximum of 5 MB for systems configured with R80/RL02 or dual RL02 disks. Other VAX-11/730 system configurations support a maximum of 3 MB of memory for the VAX-11/730 only. A maximum of two RL02 disk drives can be added to the dual RL02 and the R80/RL02 configuration for VAX-11/730 only. 61 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Appendix B Note: The VT1000 is a This appendix describes monochrome windowing Digital Equipment Corporation terminal that supports terminals, disks, tapes, standard ANSI applications controllers, communications and "X" windows. The options, and VAXcluster transport protocols options. supported are LAT for VMS. The product supports 15 inch Terminals and Terminal Line and 19 inch monitors. Interfaces Disks To prevent input from To support full VMS, a overflowing a buffer, system disk of greater than terminals use the ASCII control 100 MB is recommended. To characters DC1 and DC3 for support full VMS and full synchronization as defined by VMS DECwindows, a system disk Digital's DEC STD 111, Revision of greater than 115 MB is A. recommended. When a smaller The following table lists the disk is used, additional terminals that are supported by tailoring is required prior VMS: to installing some VMS and VT52 VT100- LA- VMS DECwindows options. This series seriesdoes not include the dump file space. Refer to the Upgrade VT300- VT1000- LQP02 and Installation Procedures series series Manual for information on tailoring. For the disks that VT200- have been introduced since series the last edition of the VMS Operating System SPD, the Terminals on Professional minimum required version of 350, Rainbow 100, and DECmate VMS for these disks is listed. II systems emulate VT100 ESE-20 120 MB solid (MSCP) terminals. state disk Only limited support is drive. available for the VT52. The VT131, when running an ESE-52 120 MB solid (MSCP) application, operates in block state disk (V5.5- mode. When interacting with VMS drive. 2) and its associated utilities, the VT131 only operates in ESE-56 600 MB solid (MSCP) VT100 (or interactive) mode and state disk (V5.5- not in block mode. drive. 2) ESE-58 960 MB solid (MSCP) state disk (V5.5- drive. 2) 62 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 RA60 205 MB (MSCP) RD53* 71 MB fixed (Q-bus, removable disk disk drive. or drive. In- te- RA70 280 MB fixed (MSCP) gral disk drive. Con- troller RA71 700 MB fixed (MSCP) on disk drive. (V5.4- Mi- 2) cro/VAX 2000) RA72 1 GB fixed disk (MSCP) drive. (V5.4- RD54 159 MB fixed (Q-bus, 2) disk drive. or In- RA80 128 MB fixed (MSCP) te- disk drive. gral Con- RA81 456 MB fixed (MSCP) troller disk drive. on Mi- RA82 622 MB fixed (MSCP) cro/VAX disk drive. 2000) RA90 1.2 GB fixed (MSCP) RF30 150 MB fixed (DSSI) disk drive. disk drive. RA92 1.5 GB fixed (MSCP) RF31F 200 MB fixed (DSSI) disk drive. disk drive. (V5.4- 2) RC25* 2 disks each 26 (Q-bus, MB (1 fixed and UNIBUS) RF31- 381 MB (DSSI) 1 removable) JA shockmounted disk drive with removable disk shared spindle. drive. RD32* VAX 42 MB fixed RF31- 381 MB fixed (DSSI) disk drive for KA disk drive. Micro/VAX 2000 and VAXstation RF35 800 MB fixed (DSSI) 2000. disk drive. (V5.5) RD51* 10 MB fixed (Q-bus) RF71 400 MB fixed (DSSI) disk drive. disk drive. RD52* 31 MB fixed (Q-bus) RF73 2 GB fixed disk (DSSI) disk drive. drive. (V5.5) RK06* 14 MB removable (UNIBUS) disk drive. 63 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 RK07* 28 MB removable (UNIBUS)RP07 516 MB fixed (MASSBUS) disk drive. disk drive. (2.2 MB/sec RL02* 10 MB removable (UNIBUS) transfer rate disk drive. is supported if the RH780 RM03+ 67 MB removable (MASSBUS) is at REV B1 disk drive. or greater for the VAX-11/780, RM05 256 MB (MASSBUS) VAX-11/785, removable disk VAX 8600 and drive. VAX 8650.) RM80 124 MB fixed (MASSBUSRX02* 512 KB diskette (UNIBUS) disk drive. drive. The RX02 drive also R80** 124 MB fixed writes using disk drive for single-density VAX-11/725 and RX01 diskettes. VAX-11/730. RX23 1.47 MB (SCSI) RRD40* 600 MB read- (Q-bus diskette drive. only optical and disk drive. SCSI) RX26 2.8 MB diskette (SCSI) drive. (V5.5) RRD42 600 MB read- (SCSI) only optical (V5.4- RX33* 1.2 MB diskette (Q-bus, disk drive. 2) drive. Requires or minimum RQDX3 In- RRD50* 600 MB read- (Q-bus) microcode of te- only optical V3.0. gral disk drive. Con- troller RP05** 88 MB removable (MASSBUS) on disk drive. Mi- cro/VAX RP06 176 MB (MASSBUS) 2000) removable disk drive. RX50* 400 KB diskette (Q-bus, drive. or In- te- gral Con- troller on Mi- cro/VAX 2000) 64 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 RV20* 2 GB Write (Q-bus, RZ58 1.35 GB fixed (SCSI) Once Read Many UNIBUS, disk drive. (V5.5) optical disk VAXBI) drive. RV64* 2 GB Write (Q-bus, Once Read Many UNIBUS, optical disk VAXBI) sub-system. RZ22* 52 MB fixed (SCSI) disk drive. RZ23** 104 MB fixed (SCSI) disk drive. RZ23L 121 MB fixed (SCSI) disk drive. (V5.4- 1) RZ24 209 MB fixed (SCSI) disk drive. RZ24L 240 MB fixed (SCSI) disk drive. (V5.4- 3) RZ25 425 MB fixed (SCSI) disk drive. (V5.4- 3) RZ26 1.0 GB fixed (SCSI) disk drive. (V5.5- 2) RZ35 852 MB fixed (SCSI) disk drive. (V5.4- 3) RZ55 332 MB fixed (SCSI) disk drive. RZ56 665 MB fixed (SCSI) disk drive. RZ57 1 GB fixed disk (SCSI) drive. (V5.4- 3) 65 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 * Device cannot be used as TA91 High (MSCP) a VMS system disk. performance (V5.4- tape drive. 2) ** Device cannot be used as a VMS system disk TE16 9-track (MASSBUS) with VMS DECwindows magnetic tape environment. drive. Disk Options Supported by TF70 290 MB TK70 (DSSI) Digital's Services Enterprise tape cartridge (V5.4- Integration Center (SEIC) drive. 2) RF30- 150 MB (DSSI) TF85 2.6 GB (DSSI) RA removable disk streaming (V5.4- drive. tape cartridge 2) RF31- 381 MB (DSSI) drive. RA removable disk TF857 18.2 GB tape (DSSI) drive. cartridge (V5.4- RF71- 400 MB (DSSI) loader. 2) RA removable disk TK50 95 MB, 5 1/4 (Q-bus drive. inch streaming and RF71- 1 GB removable (DSSI) tape cartridge SCSI) RA disk drive. drive. RWZ01 594 MB optical (SCSI) TK70 296 MB, 5 1/4 (Q-bus) removable disk (V5.4- inch streaming drive. 3) tape cartridge drive. Tapes TLZ04 4 GB, 3.5 (SCSI) TA78 STI TU78. (MSCP) inch, 4 mm tape drive. TA79 STI TU79. (MSCP) TLZ06 4 GB, 3.5 inch, (SCSI) TA81 STI TU81. (MSCP) 4 mm DAT tape (V5.5- drive. 1) TA90 1.2 GB, tape (MSCP) cartridge TS11 9-track (UNIBUS) subsystem. magnetic tape (5 inch 200 MB drive. cartridge) TU77 9-track (MASSBUS) TA90E 1.2 GB tape (MSCP) magnetic tape cartridge drive. subsystem. Compacts TU78 9-track (MASSBUS) data records magnetic tape automatically. drive. 66 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Controllers TU80 9-track (UNIBUS)DMB32- VAXBI DMA parallel magnetic tape LP high speed line drive. printer controller. TU81 9-track (UNIBUS)DRB32 High speed general magnetic tape purpose parallel drive. interface for VAXBI TU81- Streaming 9- (Q-bus, (systems). Plus track magnetic UNIBUS, DMF32- Synchronous tape drive. VAXBI) LP /Asynchronous TZ30 95 MB, 5 1/4 (SCSI) communication inch, half- option with printer height, tape port for use drive. on UNIBUS based systems. TZ85 2.6 GB, 5 1 (SCSI) HSC40 Hierarchical /4 inch tape (V5.4- Storage Controller drive. 3) for MSCP disks and TZ86 6 GB, 5 1/4 (SCSI) TMSCP tapes. (HSC inch, tape (V5.5- Software must be a drive. 2) minimum Version of 6.5) TZK10 320/525 MB QIC (SCSI) HSC50 Hierarchical (quarter inch (V5.4- Storage Controller cartridge) tape 2) for MSCP disks and drive. TMSCP tapes. (HSC Tape Options Supported by Software must be a Digital's Services Enterprise minimum Version of Integration Center (SEIC) 4.1) TLZ08 5.25 inch, 2 (SCSI) HSC60 Hierarchical GB, 8 mm tape Storage Controller drive. for MSCP disks and TMSCP tapes. (HSC TS05 9-track (Q-bus) Software must be a magnetic tape minimum Version of drive. 6.5) TSZ05 1600 BPI, 9 (SCSI) HSC65 Hierarchical track tape Storage Controller drive. for MSCP disks and TMSCP tapes. (HSC TSZ07 1600/6250 BPI, (SCSI) Software must be a tape drive. (V5.4- minimum Version of 1) 7.0) 67 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 HSC70 Hierarchical KDA50 Q-bus MSCP disk Storage Controller controller. for MSCP disks and The KDA50 disk TMSCP tapes. (HSC controller supports Software must be a up to four of the minimum Version of following drives: 6.5) RA60, RA70, RA80, RA81, and RA82. HSC90 Hierarchical Storage Controller KDB50 VAXBI MSCP disk for MSCP disks and controller. TMSCP tapes. (HSC The KDB50 disk Software must be a controller supports minimum Version of up to four of the 6.5) following drives: RA60, RA80, RA81, HSC95 Hierarchical and RA82. Storage Controller for MSCP disks and KDM70 The KDM70 is an TMSCP tapes. (HSC intelligent MSCP Software must be a /TMSCP mass-storage minimum Version of controller that 7.0) supports RA Series Disks and Storage IDC Integrated Disk Arrays, TA Series Controller for Tape, and ESE20. VAX-11/725 and VAX-11/730 systems. KFQSA Q-bus DSSI bus storage adapter. IDTC Integral Disk and This adapter allows Tape Controller for up to seven DSSI VAX 8600 and VAX storage devices 8650 systems. to attach to the DSSI bus. (Six LPA11-K Microprocessor DSSI storage controller devices are allowed for laboratory in a Dual-Host acquisition Configuration.) I/O devices, accommodating up KLESI Q-bus, UNIBUS, to two AD11-Ks, one and VAXBI tape AA11-K, one KW11-K, controller for the two AM11-Ks, and TU81-Plus, RV20, or five DR11-Ks. One RC25. LPA11-K controller is supported per KRQ50 Q-bus controller UNIBUS and a for the RRD40 maximum of two /RRD50 compact are supported per disk reader. system. 68 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 KZQSA Q-bus to SCSI RQDXx Q-bus disk bus adapter. This controller for adapter allows up Micro/VAX and VAX- to 7 SCSI storage station systems. devices to attach There is an RQDX1, to the SCSI bus. RQDX2, and an RQDX3 controller. LP11 UNIBUS parallel The RQDXx disk high-speed line controller supports printer controller as many as four for the LPxx disk units, with printers. each RX50 diskette drive counting as LPV11 Q-bus parallel two units. Due high-speed line to controller printer controller. limitations, the system supports RK711 UNIBUS disk a maximum of controller for 4 devices; the RK07 disk drives. number of RD/RX devices the system RL211 UNIBUS disk supports depends controller for the on the enclosure. RL02 disk drive. The RQDX3 disk controller is required for the RD54 and the RX33 drives. RX211 UNIBUS diskette controller for two RX02 drives. One RX211 diskette controller is supported per system. RUX50 UNIBUS diskette controller for RX50 drives. One RUX50 diskette controller is supported per system. TM03 MASSBUS tape controller for the TE16 and TU77 magnetic tape drives. 69 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 TM32 BI-bus 9 track tape UDA50 UNIBUS MSCP disk controller only controller. The with large record UDA50 controller support. must have a minimum microcode version TM78 MASSBUS tape of REV 3. The UDA50 controller for controller supports the TU78 magnetic up to 4 of the tape drive. following disk drives: RA60, RA80, TQK50 Q-bus tape RA81, and RA82. controller for Controller Options Supported by the TK50 cartridge Digital's Services Enterprise tape drive. Integration Center (SEIC) TQK70 Q-bus tape TSV05 Q-bus tape controller for controller for the TK70 cartridge the TS05 magnetic tape drive. tape drive. TS11 UNIBUS tape TSU05 Unibus tape controller for controller for the TS11 magnetic the TS05 magnetic tape drive. tape drive. TBK50 BI-bus tape MASSBUS Adapter/Tape Subsystems controller for These include a MASSBUS the TK50 cartridge adapter, a tape formatter, tape drive. and a transport (a TU77 for TBK70 BI-bus tape the TxU77 subsystems, a TE16 controller for transport for TxE16 subsystem, the TK70 cartridge or a TU78 for the TEU78 tape drive. subsystem). A maximum of three additional TUK50 UNIBUS tape TU77 magnetic tape transports controller for the can be added to a TxU77 TK50 cartridge tape subsystem and a maximum of drive. One TUK50 seven additional TE16 magnetic tape controller tape transports can be added is supported per to a TxE16 subsystem. Different system. magnetic tape transports cannot be mixed on the same tape subsystem. With disks and magnetic tape transports mixed on the same MASSBUS, the following rules apply: o Disks can be added to a magnetic tape subsystem to a maximum of seven 70 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 additional disks per tape subsystem. DHT32 8 line asynchronous o Tapes cannot be added to terminal controller a disk subsystem. (DEC 423). (No modem control) Asynchronous Terminal (Micro/VAX 2000) Controllers DHQ11 8 line asynchronous CXA16 16 line serial terminal controller terminal (EIA RS-232-C multiplexer (DEC- or RS-423-A), 423), maximum baud maximum baud rate supported: rate supported: 38400. (No modem 19200. (Full modem control) (Q-bus) control) (Q-bus) CXB16 16 line serial DHU11 16 line terminal asynchronous multiplexer terminal controller (RS422), maximum (RS-232-C), baud rate maximum baud rates supported: 38400. supported: VMS (No modem control) 19200, DECnet-VAX (Q-bus) 9600. (Full modem control) (UNIBUS) CXY08 8 line serial terminal DHV11 8 line asynchronous multiplexer terminal controller (RS232), maximum (EIA RS-232- baud rate C or RS-423-A), supported: 19200. maximum baud rates (Full modem supported: VMS control) (Q-bus) 19200, DECnet-VAX 9600. (Full modem DHB32 16 line control) (Q-bus) asynchronous terminal controller DMB32 8 line asynchronous for VAXBI, terminal maximum baud rate controller, supported: 19200. maximum baud rates (VAXBI) supported: VMS 19200, DECnet-VAX DHF11 32 line 9600. (Full modem asynchronous control) (VAXBI) terminal controller (DEC 423), maximum baud rate supported: 19200. (No modem control) (Q-bus) 71 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 DMF32 8 line asynchronous DZ32 8 line asynchronous terminal terminal controller controller, (EIA RS-232- maximum baud rates C or RS-423-A), supported: VMS maximum baud rate supports 19200, supported: 9600. DECnet-VAX supports (Partial modem 9600. (Full modem control) (UNIBUS) control on first 2 lines) (UNIBUS) DZQ11 4 line asynchronous terminal controller DMZ32 24 line (EIA RS-232- asynchronous C or RS-423-A), terminal controller maximum baud rate (EIA RS-232- supported: VMS C or RS-423-A), supports 19200, maximum baud rates DECnet-VAX supports supported: VMS 9600. (Partial 19200, DECnet-VAX modem control) 9600. (Modem (Q-bus) support dependent on configuration) DZV11 4 line asynchronous (UNIBUS) terminal controller (EIA RS-232- DSH32 1 line synchronous C or RS-423-A), (full modem maximum baud rate control) and 8 supported: VMS line asynchronous supports 19200, (no modem control) DECnet-VAX supports communications 9600. (Partial controller for the modem control) Micro/VAX 2000. (Q-bus) DEC423 devices Integral asynchronous serial are supported. lines for the Micro/VAX 2000 Maximum baud rates and the VAXstation 2000. supported: VMS 19.2 KBPS (kilobits On the Micro/VAX 2000, one /second). line is the modem/data line and three are data-only lines. DZ11 8 line asynchronous On the VAXstation 2000, the terminal controller lines support keyboard, mouse, (EIA RS-232- modem connection, and printer C or RS-423-A), or plotter. DECnet-VAX supports maximum baud rate all four asynchronous data supported: 9600. /modem RS-232C serial lines up (Partial modem to 9.6 KBPS on the integral 4 control) (UNIBUS) line asynchronous controller for Micro/VAX 2000. Synchronous Controllers 72 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 The VAX Wide Area Network Device Drivers software product DSB32 Two line, multiple contains the synchronous device protocol, drivers and is required when synchronous using synchronous communication adapter. (VAXBI) options. Refer to SPD 29.64.xx for more information. DSH32 1 line synchronous DMB32 Point-to-point (full modem synchronous control) and 8 interface. (VAXBI) line asynchronous (no modem control) DMC11 High-speed local communications point-to-point controller for the synchronous Micro/VAX 2000. interface; retired DEC423 devices device, no longer are supported. offered as an Maximum baud rates option. (UNIBUS) supported: VMS 19.2 KBPS (kilobits DMF32 Point-to-point /second). 9.6 KBPS or multipoint for Micro/VAX 2000, synchronous etc. interface. (UNIBUS) DST32 Synchronous single DMP11 Point-to-point line support for or multipoint DDCMP up to 9.6 synchronous KBPS, full duplex interface; (UNIBUS) for Micro/VAX 2000 retired device, no systems. Concurrent longer offered as use with the DHT32 an option. is not supported. DMR11 Remote point-to- DSV11 Synchronous, 2 point synchronous line, half or full- interface; (UNIBUS) duplex point-to- replaces DMC11. point communication interface DMV11 Point-to-point supporting DDCMP or multipoint (1 or 2 lines up to synchronous 64 KBPS). interface. (Q-bus) DPV11 Synchronous, 1 line, half or full- duplex point-to- point communication interface supporting DDCMP, HDLC, SDLC, or BISYNC protocols. 73 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 DSF32 DEC WANcontroller DEMNA The DEMNA is a 620 - Two line high performance synchronous network adapter communications that connects XMI controller designed systems to both the specifically Ethernet and IEEE for the VAXft 802.3 local area 3000 processors, networks. supporting DDCMP. DDCMP is supported DESVA Ethernet controller at speeds up to 64 interface. KBPS per line for a two-line operation. DEQNA Ethernet controller LAN Options to Q-bus. The minimum revision DEUNA Ethernet to UNIBUS level required is controller. K3. All systems utilizing a DEQNA DELUA Ethernet to UNIBUS must operate with controller. The software data minimum revision checking enabled. level required is Since AUTOGEN will F1. automatically set the correct DEBNA Ethernet to VAXBI parameter, no communication system management controller. intervention is required. DEBNI Ethernet to VAXBI Not supported communication by VAXcluster controller. software. Not supported for any DEMFA The DEMFA is a interfaces except high performance for access using network adapter QIO or ALTSTART that connects interfaces. XMI systems to both Ethernet and DELQA Ethernet controller IEEE FDDI (Fiber to Q-bus. This is Distributed Data the replacement for Interconnect) local DEQNA. The minimum area networks. revision level required is C3. DESQA Ethernet controller to Q-bus for S-BOX configurations. 74 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 KFE52 DSSI/Ethernet CIXCD- Native CI Adapter Adapter for AA for VAX 9xxx the VAXft 3000. XMI systems. Minimum of two (Minimum microcode adapters per system version REV 1.0 is providing redundant required.) connection to the Ethernet and the CIXCD- Native CI Adapter DSSI buses. AB for VAX 6xxx CI Options XMI systems. (Minimum microcode VAXcluster Software may version REV 1.0 is support multiple CI adapters required.) per system. Refer to the Miscellaneous VAXcluster Software Product Description (SPD 29.78.xx) for CR11 Card reader. One the supported configurations. CR11 card reader CI750 CI Adapter for is supported per VAX-11/750 systems. system. (UNIBUS) (Minimum microcode DRV11- General purpose DMA version REV 8.7 is WA interface. (Q-bus) required.) CI780 CI Adapter for DR11-W General purpose VAX-11/780, VAX-11 high-speed DMA /785, VAX 8600, and interface - one VAX 8650 systems. DR11-W interface (Minimum microcode supported per version REV 8.7 is UNIBUS. required.) DR750 High performance CIBCI CI Adapter for general purpose VAXBI systems. interface for the (Minimum microcode VAX-11/750. One version REV 8.7 is DR750 interface required.) is supported per system. This device CIBCA- Native CI Adapter may not be used in AA for VAXBI systems. conjunction with (Minimum microcode the CI750. version REV 7.5 is required.) CIBCA- Native CI Adapter BA for VAXBI systems. (Minimum microcode version REV 5.2 is required.) 75 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 DR780 High performance FP780 Floating Point general purpose Accelerator for the interface for the VAX-11/780 system. VAX-11/780 and VAX-11/785. One FP785 Floating Point DR780 interface Accelerator for the is supported per VAX-11/785 system. system. On the VAX 8600 and VAX FP86-AA Floating Point 8650 as many as Accelerator for the four per system are VAX 8600 and VAX permitted provided 8650 systems. that the M8297-YA is used. FV64A Vector Processing option for the DSSI Digital VAX 6000-400. Storage Systems Interconnect. H7112 Memory battery back-up for VAX-11 DWBUA XMI to UNIBUS /750, VAX-11 adapter. /780, VAX-11/785, VAX 8600, and VAX DWMBA XMI to BI adapter; 8650 systems. also the adapter This is required used to connect the for power-fail XMI to VAX expander /recovery. cabinet. KE780 G and H floating DWMVA XMI to VME adapter. point microcode for the VAX-11/780 DW750 UNIBUS Adapter system. for second UNIBUS for the VAX-11/750 KU780 User-writeable system. control store for the VAX-11/780 DW780 UNIBUS Adapter system. for VAX-11/780, VAX 8600 and VAX MA780 Multiport shared 8650. memory. A multiple version VMS 4.7 FP730 Floating Point and VMS 5.x-n Accelerator for the VAXcluster system VAX-11/730 system. is not supported if the system is FP750 Floating Point configured with Accelerator for the MA780 memory. VAX-11/750 system. RH750 MASSBUS adapter for the VAX-11/750 system. 76 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 RH780 MASSBUS controller [TM]The DIGITAL Logo, ACMS, for the VAX-11 BI, CI, CX, DBMS, DDCMP, /780, VAX-11/785, DECdtm, DECintact, VAX 8600, and VAX DECmate, DECnet, 8650 systems. DECscheduler, DECtp, DECterm, DECwindows, SBI System Backplane DELUA, DEUNA, DEQNA, Interconnect for DRB32, HSC, HSC40, the VAX-11/780, HSC50, HSC70, KDA, VAX-11/785, and KDM, KLESI, KRQ50, I/O BUS for the LAT, LQP02, MASSBUS, VAX 8600 and VAX Micro/VAX, RA, RC, 8650 systems. Rdb/VMS, RF, RK, RL, RM, RQDX2, RQDX3, SCSI Small Computer RRD50, RUX50, RX, TA, System TE, TEU78, TK, TM, TS, Interconnect. TQK50, TS05, TU, UDA, ULTRIX, UNIBUS, VAX, VS40X 4-plane graphics VAX Ada, VAX BASIC, coprocessor. VAX BLISS-32, VAX C, VAX COBOL, VAX FORTRAN, WS01X VAXstation 3100 SPX VAX Pascal, VAX SCAN, Graphics option. VAXBI, VAXcluster, VAXft, VAXstation, InfoServeInfoServer 100 VAXserver, VMS, VR150, 100 is a stand- VR160, VT, and VT1000 alone Ethernet- are trademarks of based virtual Digital Equipment disk server. The Corporation. server has locally attached SCSI removable CDROMs and SCSI disk storage. VMS V5.5 supports virtual disk reads. For other features, please refer to the InfoServer 100/150 Software Product Descriptions. ® PostScript is a registered trademark of Adobe Systems, Inc. [TM]Motif and OSF/Motif are trademarks of Open Software Foundation, Inc. 77 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 Appendix C 2. Licensee acknowledges Third Party Licensing Section that the Software, Coded Font Programs, Typefaces Adobe Systems Incorporated, and Trademarks are License Terms and Agreement proprietary to Licensor 1. Licensor grants to and its suppliers. Licensee a nonexclusive Licensee agrees to sublicense, subject to hold the Software and other provisions hereof Coded Font Programs in (a) to use the PostScript confidence, disclosing Software ("Software") the Software and Coded solely for Licensee's Font Programs only to own internal business authorized employees purposes on a Single having a need to use the Licensed System; (b) to Software and Coded Font use the digitally-encoded Programs as permitted machine-readable outline by this Agreement and and bitmap programs to take all reasonable ("Font Programs") precautions to prevent provided by Licensor in a disclosure to other special encrypted format parties. ("Coded Font Programs") 3. Licensee will not make and identified herewith or have made, or permit to reproduce and display to be made, any copies designs, styles, weights, of the Software or and versions of letters, Coded Font Programs or numerals, characters portions thereof, except and symbols ("Typefaces" as necessary for its use and "Screen Typefaces") with a single Licensed solely for Licensee's System hereunder. own customary business Licensee agrees that any or personal purposes such copies shall contain on the screen of the the same proprietary Licensed System; and (c) notices which appear on to use the trademarks or in the Software or the used by Licensor to Coded Font Programs. identify the Coded Font 4. Except as stated above, Programs and Typefaces this Agreement does not reproduced therefrom grant Licensee any rights ("Trademarks"). Licensee to patents, copyrights, may assign its rights trade secrets, trade under this Agreement names, trademarks to a licensee of all of (whether registered or Licensee's right, title unregistered), or any and interest to such other rights, franchises, Software and Coded Font or licenses in respect Programs provided the of the Software, Coded licensee agrees to be Font Programs, Typefaces, bound by all of the terms or Trademarks. Licensee and conditions of this will not adapt or use any Agreement. trademark or trade name which is likely to be 78 OpenVMS VAX Operating System, Version 5.5-2 SPD 25.01.36 similar to or confusing 7. The software licensed with that of Licensor hereunder is restricted or any of its suppliers to use to generate screen or take any other action displays on a single which impairs or reduces Licensed System having the trademark rights a screen resolution of of Licensor or its less than 150 dots/per suppliers. Any use of /inch. Licensee agrees the Trademarks must not to make use of the identify the applicable software, directly or ``Trademark Owner'' set indirectly, to print forth in Schedule A bitmap images with print hereto as the owner of resolutions of 150 dots such Trademarks. At the /per/inch or greater, reasonable request of or to generate Fonts or Licensor, Licensee must Typefaces for use other supply samples of any than with the Licensed Typeface identified by a System. Any failure Trademark. of Licensee to comply 5. Licensee agrees that with this provision is a it will not attempt material breach of this to alter, disassemble, End User Agreement. decrypt or reverse compile the Software or Coded Font Programs. 6. Licensee acknowledges that the laws and regulations of the United States restrict the export and re-export of commodities and technical data of United States origin, including the Software or Coded Font Programs. Licensee agrees that it will not export or re-export the Software or Coded Font Programs in any form without the appropriate United States and foreign government licenses. Licensee agrees that its obligations pursuant to this section shall survive and continue after any termination or expiration of rights under this Agreement. 79