Software Product Description ___________________________________________________________________ PRODUCT NAME: OpenVMS AXP Operating System, Version 1.5 SPD 41.87.01 DESCRIPTION[*] OpenVMS AXP is a general-purpose multiuser operating system that sup- ports Digital Equipment Corporation's Alpha AXP series computers in both production and development environments. OpenVMS AXP software sup- ports industry standards, facilitating application portability and in- teroperability. OpenVMS AXP provides symmetric multiprocessing (SMP) support for multiprocessing Alpha AXP systems. OpenVMS AXP can be tuned to perform well in a wide variety of appli- cations, including compute-intensive, I/O-intensive, real-time, and combinations of those and other environments. Actual performance de- pends on the type of computer, available physical memory, and the num- ber and type of disk and tape drives on the system. OpenVMS AXP software has integrated networking and distributed com- puting capabilities. OpenVMS AXP contains extensive features that pro- mote ease-of-use, improve productivity, and facilitate system manage- ment. ____________________ "Licensee agrees to only execute Display PostScript on those Digi- tal workstations identified as licensed systems in this Software Prod- uct Description, and that in any event licensee agrees not to make use of the software directly or indirectly, to print bitmap images with print resolutions greater than 150 DPI, or to generate fonts or typefaces for use other than with the Digital licensed system." (Terms and Conditions for Display PostScript can be found in Appendix B of this Software Product Description, on Third-Party Licensing.) DIGITAL May 1993 OpenVMS AXP Version 1.5 is the second release of the OpenVMS operat- ing system for Digital's 64-bit Alpha AXP architecture. This release contains most of the features of the OpenVMS VAX operating system. Open- VMS AXP compilers and applications take advantage of 64 bits by us- ing 64-bit data-types. Consult the Software Product Descriptions of OpenVMS AXP compilers for further details. Note that application vir- tual address space is a 32-bit implementation for compatibility and migration purposes. User Environment Users can access OpenVMS AXP software by using the English-like Dig- ital Command Language (DCL), the command language for OpenVMS AXP that is supplied with the system. DCL commands take the form of a command name followed by parameters and qualifiers. DCL commands provide in- formation about the system, initiate system utilities, and initiate user programs. OpenVMS AXP prompts users to enter required DCL param- eters, making it easy for novice users to use. Users can enter DCL commands at a terminal or include them in command procedures; command procedures can be run interactively or submitted to a batch queue for deferred execution. Information on DCL and OpenVMS AXP utilities is available through the online OpenVMS AXP Help system. Online Help includes summary infor- mation on all aspects of system operation. A number of tools and utilities are integrated into the OpenVMS AXP operating system. These tools and utilities include the following. Text Processing The Extensible Versatile Editor (EVE), one of several text editors sup- plied by Digital, allows users to insert, change, and delete text quickly. Written in the DEC Text Processing Utility (DECTPU) language, EVE is a full-screen editor that allows users to manipulate text on a ter- minal screen. EVE also provides an EDT-style keypad, allowing users of the EDT text editor to easily transition to EVE. 2 Mail Utility The Mail utility allows users to send messages to any other user on the system. Multinode operation is available if DECnet for OpenVMS AXP is installed and licensed on each participating node on the config- ured network. Command-Level Programming Command-level programming allows users to create special files called command procedures that contain a series of DCL commands. When users start a command procedure, the system consecutively processes the com- mands in the command procedure. Users can also use DCL commands to as- sign symbolic names, evaluate numerical and logical expressions, ac- cept parameters, perform conditional (IF-THEN-ELSE) and branching (GOTO) logic, and handle error conditions. User Environment Tailoring Users can customize the computing environment with user login command procedures, shorthand commands, binding of commands to function keys, and command recall and editing. Terminal Fallback Facility (TFF) This facility allows Digital 7-bit terminals to input and output the Digital Multinational Character Set (MCS). Specific tables allow con- version to MCS for a number of different 7-bit National Replacement Character sets, such as French, German, Spanish, and Swedish. The TFF also allows character composition on terminals that do not have the compose key. Program Development Environment OpenVMS AXP includes a comprehensive set of tools for developing pro- grams, including run-time libraries (RTLs), a linker, a librarian, and a symbolic debugger. Tools available to the OpenVMS AXP programmer in- clude the following. Language and Run-Time Library Support 3 OpenVMS AXP includes several run-time libraries which provide string manipulation, parallel processing support, I/O routines, I/O conver- sion, terminal independent screen handling, date and time formatting routines, highly accurate mathematical functions, signaling and con- dition handling, and other general purpose functions. These routines can be called from programs written in such languages as MACRO-64, Ada, C, Fortran, and Pascal. Also included in OpenVMS AXP are language support libraries. While each language is different, all provide support for sequential file I/O and most support direct and indexed file I/O as well. Language RTLs also provide support for I/O formatting, error handling, and, in DEC For- tran, the ability to read unformatted files containing data from other vendors. Translated OpenVMS VAX RTLs are provided to preserve customer invest- ment by ensuring that existing OpenVMS VAX software can run on an Open- VMS AXP system and by ensuring compatible results. A translated Open- VMS VAX RTL is an RTL image which has undergone binary translation be- cause no compiler exists for the programming language to produce an OpenVMS AXP RTL image at this point in time. Translated RTLs inter- operate with their native counterparts where possible. Major OpenVMS AXP languages (including those listed above) adhere to the common calling standard, meaning that routines written in any of these languages can directly call routines written in any other lan- guage. Development of applications using multiple languages is sim- ple and straightforward. At a lower level, programs can call system services directly for se- curity, event flag, asynchronous system trap, logical name, record and file I/O, process control, timer, time conversion, condition handling, lock management, and memory management services. Again, system ser- vices use the Alpha AXP calling standard and condition handling con- ventions. Macro-32 Compiler The Macro-32 compiler for OpenVMS AXP is supplied with OpenVMS AXP soft- ware for migration purposes. 4 DECthreads OpenVMS AXP includes a user-mode multi-threading capability referred to as DECthreads. DECthreads provides an implementation of draft 4 of the proposed POSIX 1003.4a standard. DECthreads is a library of run- time routines callable from a C program that allows the user to cre- ate multiple threads of execution within a single address space. Multi- threading capability allows computation activity to be overlapped with I/O activity. Synchronization elements, such as mutexes and condition variables, are provided to help ensure that shared resources are ac- cessed correctly. DECthreads also provides multiple scheduling poli- cies for scheduling and prioritizing threads. Librarian Utility The Librarian utility permits storage of object modules, image files, macros, help text, or any general record-oriented information in cen- tral, easily accessible files. Object module and image file libraries are searched by the linker when the linker finds a reference it can- not resolve in one of its input files. Macro-32 libraries are searched by the Macro-32 compiler when the compiler finds a macro that is not defined in the input file. Debugger The OpenVMS AXP debugger allows users to trace program execution as well as display and modify register contents using the same symbols that are present in the source code. RMS File Utilities RMS file utilities allow users to analyze the internal structure of an RMS file and to determine the most appropriate set of parameters for an RMS file. They can also be used to create, load, and reclaim space in an RMS file. Refer to the Operating System Environment sec- tion of this Software Product Description for more information on RMS. File Differences Utility The File Differences utility compares the contents of two files and lists those records that do not match. 5 Translated Image Environment OpenVMS AXP provides an array of services to allow the operation of programs that have undergone binary translation from OpenVMS VAX im- ages. These programs can perform virtually all user-mode functions on OpenVMS AXP, and can operate in combination with other programs (im- ages) that have been translated from OpenVMS VAX or have been built using native compilers on OpenVMS AXP. Without requiring special source code, the Translated Image Environment automatically resolves differ- ences between the VAX and Alpha AXP architectures, including float- ing point registers, condition codes, exception handling, ASTs, and others. The Translated Image Environment included with OpenVMS AXP is suffi- cient to run such images which have been translated elsewhere. The DECmigrate for OpenVMS AXP layered product can be used to translate OpenVMS VAX images. For additional information on the precise characteristics of programs suitable for binary translation refer to the DECmigrate for OpenVMS AXP Systems Software Product Description (SPD 39.44.xx). System Management Environment OpenVMS AXP provides a variety of tools to aid the system manager in configuring and maintaining an optimal system. Tools available for the system manager include the following. Batch and Print Queuing System OpenVMS AXP provides an extensive batch/print capability that allows the creation of queues and the setup of spooled devices in order to process non-interactive workloads in parallel with timesharing or real- time jobs. The OpenVMS AXP batch and print operations support two types of queues: generic queues and execution queues. A generic queue is an interme- diate queue that holds a job until an appropriate execution queue be- comes available to initiate the job. An execution queue is a queue through which the job (either print or batch) is actually processed or exe- cuted. 6 The system queues batch jobs for execution. The system manager can reg- ulate the number of queues and the number of streams per queue (that is, the number of batch jobs in the queue that can execute concurrently). Both generic and execution batch queues can have different attributes, such as the maximum CPU time permitted, working set size, and prior- ity. Facilities are provided for starting and stopping queues, and for starting and stopping jobs in a queue. Print queues, both generic and execution, together with queue manage- ment facilities, provide versatile print capabilities, including sup- port of ANSI and PostScript(R) file printing. Accounting Utility For accounting purposes, OpenVMS AXP keeps records of the use of sys- tem resources. These statistics include processor and memory utiliza- tion, I/O counts, print symbiont line counts, image activation counts, and process termination records. The OpenVMS AXP Accounting utility allows various reports to be generated using this data. Autoconfigure/AUTOGEN Utilities OpenVMS AXP provides utilities to automatically configure the avail- able devices into the system tables and to set system operational pa- rameters based on the detected peripheral and memory configuration. There is no need for a traditional "system generation" process when the hardware configuration is expanded or otherwise modified. The OpenVMS AXP AUTOGEN command procedure automatically sets a num- ber of system parameters by detecting devices installed in a config- uration. A feedback option can be used to generate a report of rec- ommended parameter settings for system tuning. Backup Utility The Backup utility provides full volume and incremental file backup for file-structured and mounted volumes. Individual files, selected directory structures, or all files can be backed up and restored. Files can be selected by various dates (creation, modification, and so forth). 7 Files can be backed up to magnetic tape or magnetic disk. With stan- dalone backup, system managers can back up and restore system disks. Standalone backup is used during the installation of the OpenVMS AXP operating system. The Backup utility can be used to restore a saveset or list the contents of a saveset. Analyze Disk Structure Utility The Analyze Disk Structure utility compares the structure information on a disk with the contents of the disk, prints the structure infor- mation, and permits changes to that information. It also can be used to repair errors that are detected in the file structure of disks. Monitor Utility The Monitor utility permits the system manager to monitor different classes of system-wide performance data, including process activity, I/O activity, and memory management activity, at specified intervals. The data may be displayed as it is gathered or saved in a file for later use. License Management Facility (LMF) The License Management Facility (LMF) allows the system manager to en- able software licenses and to determine which software products are licensed on an OpenVMS AXP system. SYSMAN Utility The SYSMAN utility allows the system manager to define a system man- agement environment so that operations performed from the local Open- VMS AXP system can be executed on all other OpenVMS AXP systems in the defined environment. The environment may include OpenVMS AXP systems networked via DECnet for OpenVMS AXP. Operations OpenVMS AXP enables varying levels of privilege to be assigned to dif- ferent operators. In addition, system-generated messages can be routed to different terminals based on their interest to the console oper- ators, tape librarians, security administrators, and system managers. 8 Operators can use the OpenVMS AXP Help Message utility to get an on- line description of OpenVMS AXP error messages. Security and Control OpenVMS AXP provides privilege, protection, and quota mechanisms to control user access to system-controlled structures in physical mem- ory, to system-structured files, and to certain devices. User account information is maintained by the system manager in the user authorization file (UAF). When creating user accounts with the Authorize utility, the system manager assigns the privileges and quo- tas associated with each user account. The system manager also assigns a unique user name, password, and user identification code (UIC) to each account. Optionally, additional identifiers can be assigned to each account, permitting users to belong to multiple overlapping groups or projects. Account use may be limited by time of day, day of week, and type of access, such as local, remote, or batch. To log in and gain access to the system, the user must supply a user name and password. The password is encoded and does not appear on ter- minal displays. Users can change their password voluntarily, or the system manager can selectively enforce how frequently passwords change, password length, and generation of random alphabetic passwords. Additionally, OpenVMS AXP provides several password filters that screen all user password changes against a dictionary of 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 can in- stall its own filter to screen passwords against a site-specific pass- word policy. The system password hash algorithm can also be replaced with a pri- vate algorithm for those sites that have contractual agreements to use specific password encryption algorithms. This feature can be enabled on a per-user, per-password basis. 9 Login security includes break-in detection, which allows terminals to be disabled when password guessing is detected. When a user logs in, the system displays a message stating when the last login for the ac- count occurred and whether any failed attempts to log in have taken place since the last successful login. A UIC consists of two fields: the unique user field and a group field. Every file, device, queue, or other system object is labeled with the UIC of its owner (normally the user who created the object). Files, devices, queues, and other system objects are assigned a pro- tection mask that allows read, execute, write, and delete access to be selectively granted to the object's owner and group, to privileged system users, and to all other users. In addition, files, devices, queues, and some other system objects can be protected with access control lists to allow selectively granted or denied access to a list of individ- ual users, groups, or identifiers. Scavenge protection can be enabled selectively in the form of file high- water marking, erase on allocate, and erase on delete, to ensure that file contents cannot be read after a file has been deleted. Security alarms are provided to allow selective auditing of security- related events, including: o Login and logout o Login failures and break-in attempts o Authorization changes o File access, selectable by use of privilege, type of access, and by individual file Note: No system can provide complete security and Digital cannot guar- antee system security. However, Digital continually strives to enhance the security capabilities of its products. Customers are strongly ad- vised to follow industry-recognized security practices. 10 Operating System Environment Processes and Scheduling The basic unit of execution in OpenVMS AXP is the process. A process consists of individual address space and registers known as "context," and code called an "executable image." The context identifies the pro- cess and describes its current state. Executable images consist of sys- tem programs and user programs that have been compiled and linked. The maximum number of concurrent processes is 8 192 per OpenVMS AXP system. Processes receive processor time to execute their images based on the priority of the process. Thirty-two priorities are recognized: pri- orities 0 to 15 are for time-sharing processes and applications that are not time critical (four is the typical default for time-sharing processes), and priorities 16 to 31 are for real-time processes. Each time an event such as an I/O interrupt occurs, the system first services the event and then passes control to the highest priority pro- cess ready to execute. The system automatically adjusts the priori- ties of processes whose base priority is in the range of 0 to 15 to favor I/O-bound and interactive processes, but the system will not ad- just the priority of a process in the range of 16 to 31. Real-time processes can be assigned higher priorities to ensure that they receive processor time whenever they are ready to execute. Real- time processes are scheduled pre-emptively; that is, if a real-time process is ready to execute, it is given the processor immediately, unless a real-time process with a higher priority is ready to execute. OpenVMS AXP uses paging and swapping mechanisms to provide sufficient virtual memory for multiple concurrently executing processes. Also, paging and swapping is provided for processes whose memory require- ments exceed available physical memory. The maximum working set size is 400 MB of memory. 11 Programmers can exercise control over memory management from within an image. An image executing in a real-time process, for example, can inhibit paging or swapping of critical code and data. Peripheral devices can be managed by the system or allocated by in- dividual processes. At least one disk must be a system disk. Other disks can be designated as data disks for the general use of all users log- ging into the system or for a specific group of users. The system con- trols interactive terminals and one or more printers. Input/Output The QIO system service provides a direct interface to the operating system's I/O routines. These services are available from within most OpenVMS AXP programming languages and can be used to perform low-level I/O operations efficiently with a minimal amount of system overhead for time-critical applications. Device drivers execute I/O instructions to transfer data to and from a device and to communicate directly with an I/O device. Each type of I/O device requires its own driver. Digital supplies drivers for all devices supported by the OpenVMS AXP operating system and provides QIO system service routines to access the special device-dependent fea- tures available in many of these devices. OpenVMS AXP supports a variety of disk and tape peripheral devices, as well as terminals, networks, and mailboxes (virtual devices for in- terprocess communication). Record Management Services (RMS) Record Management Services (RMS) is a set of I/O services that helps application programs to process and manage files and records. Although it is primarily intended to provide a comprehensive software inter- face to mass storage devices, RMS also supports device-independent ac- cess to unit-record devices. RMS supports sequential, relative, and indexed file organizations in fixed-length and variable-length record formats. RMS also supports byte stream formats for sequential file organization. 12 RMS record access modes provide access to records in four ways: se- quentially, directly by key value, directly by relative record num- ber, and directly by record file address. RMS also supports block I/O operations for various performance-critical applications that may re- quire user-defined file organizations and record formats. RMS promotes safe and efficient file sharing by providing multiple file access modes, automatic record locking where applicable, and optional buffer sharing by multiple processes. RMS utilities aid file creation and record maintenance. These util- ities convert files from one organization and format to another, re- structure indexed files for storage and access efficiency, and reclaim data structures within indexed files. The utilities also generate ap- propriate reports. For systems that have DECnet for OpenVMS AXP installed, RMS provides a subset of file and record management services to remote network nodes. Network remote file operations are generally transparent to user pro- grams. DCL commands such as EDIT, CREATE, COPY, TYPE, and PRINT allow manip- ulation of RMS files and records within RMS files at the DCL command level. Reliability The system handles hardware errors as transparently as possible while maintaining data integrity and providing sufficient information to di- agnose the cause of an error. The system limits the effects of an er- ror by first determining if the error is fatal. If the error is fa- tal then the process that encountered the error is aborted. If the er- ror occurs in system context then the current OpenVMS AXP session is shut down. If the error is not fatal then recovery actions pertinent to the error are executed and the current operation is continued. 13 In all cases, information relevant to an error is collected and put in an error log file for later analysis. Hardware errors include the following categories: o Processor errors These include processor soft errors, processor hard errors, pro- cessor machine checks, adapter errors. o Memory errors These are hardware errors that are handled in a slightly differ- ent manner. The system examines memory at startup time and does not use any pages found to be bad. During system operation, the hard- ware transparently corrects all single-bit memory errors for those systems with Error Correction Code (ECC) memory. Other failures include: o Operating system errors (system-detected inconsistencies or archi- tectural errors in system context) o User errors o I/O errors The system logs all processor errors, all operating system errors de- tected through internal consistency checks, all double-bit memory er- rors (and a summary of corrected single-bit memory errors), and most I/O errors. If the system is shut down because of an unrecoverable hardware or soft- ware error, a dump of physical memory is written. The dump includes the contents of the processor registers. The OpenVMS AXP System Dump Analyzer utility is provided for analyzing memory dumps. Interprocess Communication OpenVMS AXP provides a number of facilities for applications that con- sist of multiple cooperating processes. o Mailboxes are virtual devices that allow processes to communicate with queued messages. 14 o Shared memory sections on a single processor permit multiple pro- cesses to access shared address space concurrently. o Common event flags provide simple synchronization. o The lock manager provides a more comprehensive enqueue/dequeue fa- cility with multilevel locks, values, and ASTs (asynchronous sys- tem traps). Networking Facilities DECnet for OpenVMS AXP offers task-to-task communications, file man- agement, downline system and task loading, network command terminals, and network resource sharing capabilities using the Digital Network Architecture (DNA) protocols. OpenVMS AXP provides device drivers for all Digital LAN adapters listed in the Network Options section of Appendix A of this SPD. Application programmers can use the QIO system service to communicate with other systems connected via the Ethernet using either Ethernet or IEEE 802.3 packet format. Simultaneous use of Digital Ethernet and IEEE 802.3 pro- tocols are supported on any Digital Ethernet adapter. Not all devices are supported, and certain restrictions apply rela- tive to line speed and line utilization. Refer to the Hardware Charts section and Appendix A of this SPD, as well as the DECnet for Open- VMS AXP Software Product Description (SPD 42.25.xx), for more infor- mation. DECdtm Services The DECdtm services embedded in the OpenVMS AXP operating system sup- port fully distributed databases using a "two phase commit" protocol. The DECdtm services provide the technology and features for distributed processing, ensuring both transaction and database integrity across multiple resource managers. Updates to distributed databases occur as a single "all or nothing" unit of work, regardless of where the data physically resides. This ensures consistency of distributed data. 15 DECdtm services allow applications to define "global transactions" that may include calls to any of a number of Digital data management prod- ucts. Regardless of the mix of data management products used, the global transaction will either commit or abort. OpenVMS is unique in provid- ing transaction processing functionality as base operating system ser- vices. DECdtm features include: o Embedded OpenVMS AXP system services support the DECtp architec- ture, providing features and the technology for distributed trans- action processing. o DECdtm allows multiple disjoint resources to be updated atomically. These resources can be either physically-disjointed (for example, on different CPUs) or logically-disjointed (for example, in dif- ferent databases on the same CPU). o DECdtm encourages robust application development. Applications can be written to ensure that data is never in an inconsistent state, even in the event of system failures. o As an OpenVMS AXP service, DECdtm can be called using any Digital TP monitor or database product. This is useful for applications us- ing several database products. Symmetric Multiprocessing OpenVMS AXP provides symmetric multiprocessing (SMP) support for mul- tiprocessing Alpha AXP systems. SMP is a form of tightly coupled mul- tiprocessing in which all processors execute code streams simultane- ously. The processors can perform operations in all OpenVMS AXP ac- cess modes (user, supervisor, executive, and kernel). OpenVMS AXP SMP configurations consist of multiple central process- ing units executing code from a single shared memory address space. Users and processes share a single copy of OpenVMS AXP. SMP also pro- vides simultaneous shared access to common data in global sections to all processors. OpenVMS AXP SMP dynamically balances the execution of all processes across all available processors based on process pri- ority. 16 SMP support is an integral part of OpenVMS AXP and is provided trans- parently to the user. Because an SMP system is a single system entity, it is configured into a network and VMScluster systems as a single node. Disk and Tape Volumes Disk volumes can be organized into volume sets. Volume sets can con- tain a mix of disk device types and can be extended by adding volumes. Within a volume set, files of any organization type can span multi- ple volumes. Files can be allocated to the set as a whole (the default) or to specific volumes within the set. Optionally, portions of indexed files can be allocated to specific areas of a single disk volume or to specific volumes in a volume set. Disk quotas can be placed to control the amount of space individual users can allocate. Quota assignment is made by User Identification Code and can be controlled for each individual volume. Disk structure information can be cached in memory to reduce the I/O overhead required for file management services. Although not required to do so, users can preallocate space and control automatic alloca- tion. For example, a file can be extended by a given number of blocks, contiguously or noncontiguously, for optimal file system performance in specific cases. The system applies software validity checks and checksums to criti- cal disk structure information. If a disk is improperly dismounted be- cause of user error or system failure, the system automatically re- builds the disk's structure information the next time the disk is mounted. The system detects bad blocks dynamically and prevents their reuse once the files to which the blocks were allocated have been deleted. On Dig- ital Storage Architecture (DSA) disks, the disk controller dynamically detects and replaces bad blocks automatically. The system provides eight levels of named directories and subdirec- tories whose contents are alphabetically ordered. Device and file spec- ifications follow Digital conventions. Logical names can be used to abbreviate the specifications and to make application programs device 17 and file-name independent. A logical name can be assigned to an en- tire specification, to a portion of a specification, or to another log- ical name. OpenVMS AXP supports multivolume magnetic tape files with transpar- ent volume switching. Access positioning is done either by file name or by relative file position. Associated Products VMScluster Software VMScluster Software is an OpenVMS AXP System Integrated Product that is separately licensed. It provides a highly integrated OpenVMS com- puting environment distributed over multiple Alpha AXP and VAX sys- tems. VMScluster systems communicate using any combination of the follow- ing interconnects; CI, DSSI, and Ethernet. VMScluster systems that in- clude a CI may optionally be configured with HSC-series intelligent storage controllers. Applications running on one or more nodes in a VMScluster system ac- cess shared resources in a coordinated manner. VMScluster Software com- ponents synchronize access to shared resources, preventing multiple processes on any node in the VMScluster from interfering with each other when updating data. This coordination ensures data integrity during multiple concurrent update transactions. Application programs can spec- ify the level of VMScluster-wide file sharing that is required; ac- cess is then coordinated by the OpenVMS Extended QIO Processor (XQP) and Record Management Services (RMS). The OpenVMS queue manager controls VMScluster-wide batch and print queues, which can be accessed by any VMScluster node. Batch jobs submitted to VMScluster-wide queues are routed to any available CPU so that the batch load is shared. 18 Two or more Alpha AXP and VAX computers connected to the same Computer Interconnect (CI) or Digital Storage Systems Interconnect (DSSI) must run VMScluster software and be part of the same VMScluster system. Refer to the VMScluster Software Software Product Description (SPD 42.18.xx) for more information. Networking Facilities DECnet for OpenVMS AXP software is a System Integrated Product (SIP) that is separately licensed from OpenVMS AXP. Refer to the DECnet for OpenVMS AXP Software Product Description (SPD 42.25.xx) for further information on supported communications devices and software features. Terminal Server Products Digital's terminal server products can be used for terminal server ac- cess to OpenVMS AXP. OpenVMS AXP can also establish a connection to other devices (such as printers) attached to such terminal servers. DECwindows Motif(R) for OpenVMS AXP Digital offers a separately orderable layered product called DECwin- dows Motif for OpenVMS AXP which provides support for both OSF/Motif(R), a standards-based graphical user interface, and the X user interface (XUI) in a single run-time and development environment. By default, DECwindows Motif displays the OSF/Motif user interface. Because both Motif and XUI are based on MIT's X Window System applications writ- ten to either toolkit will run regardless of which environment the user selects. Refer to the DECwindows Motif for OpenVMS AXP Software Prod- uct Description (SPD 42.19.xx) for more information. The OpenVMS AXP software installation procedure contains an optional step to allow installation of the DECwindows Motif for OpenVMS AXP de- vice and font support, which is required to run the DECwindows Motif for OpenVMS AXP layered product. Please refer to the OpenVMS Alpha Up- grade and Installation Manual for details concerning the optional in- stallation of the prerequisite DECwindows Motif for OpenVMS AXP de- vice support. 19 Enhanced X Window Display PostScript(R) The X Window System Display PostScript System provided with DECwin- dows Motif extends the native X graphical programming environment for DECwindows users displaying text or images on workstations that sup- port the XDPS extension. The DECwindows Motif for OpenVMS AXP layered product must be installed and licensed in order to use Display PostScript. X Display PostScript has two components: o Display PostScript server extension, which is provided with the dis- play server in the OpenVMS AXP and OpenVMS VAX operating systems. A workstation is required to use this server. o Adobe(R) client libraries, which are used by applications to perform PostScript operations, such as rotating and scaling fonts, gener- ating curves, and displaying PostScript documents. The Adobe client libraries are available in the DECwindows Motif for OpenVMS lay- ered product, as well as on third-party platforms, including IBM(R), Sun(R), and Silicon Graphics. X Display PostScript adds the following capabilities to the basic X11 Window System environment: o All DECwindows fonts can be displayed at any size and rotation an- gle. o Display PostScript graphics are specified in a user-defined coor- dinate system independent of monitor density. o Color or gray-scale rendition is automatically modified to take ad- vantage of the monitor type through either direct display, color dithering, or half-toning. o Display PostScript display routines can be downloaded to the server and executed on command. o Sophisticated graphics primitives, such as precisely controlled Bezier curves, can be displayed. o Any display can be scaled and rotated arbitrarily. 20 The Display PostScript system also allows users to view PostScript files with such applications as DECwindows Mail and the CDA Viewer without generating hardcopy. (Terms and Conditions for Display PostScript can be found in Appendix B of this Software Product Description, on Third- Party Licensing). DECram for OpenVMS AXP Digital offers a separately orderable layered product called DECram for OpenVMS AXP. DECram for OpenVMS AXP is a disk device driver that allows an OpenVMS AXP system manager to create pseudo disks (RAMdisks) that reside in main memory for the purpose of improving I/O perfor- mance. Frequently accessed data can be accessed much faster from a DE- Cram device than from a physical disk device. These RAMdisks can be accessed through the file system just as physical disks are accessed, requiring no change to application and/or system software. Since main memory is allocated for the DECram device, an amount of ex- tra memory is generally required. The amount of memory dedicated is selectable. The OpenVMS AXP system manager designates the amount of memory dedicated to the DECram device(s) and the files that will be stored on it. The maximum size of a DECram device is 524 280 blocks. Refer to the DECram for OpenVMS AXP Software Product Description (SPD 34.26.xx) for more information. Standards OpenVMS AXP is based on the public, national, and international stan- dards listed below. Support for POSIX Standards and XPG3 BASE Branding POSIX (Portable Operating System Interface for Computing Environments) is a set of standards and draft standards that are being generated by the Institution of Electronic and Electronic Engineers (IEEE). Con- formance to POSIX 1003.1-1988 and -1990 is demonstrated by passing the POSIX Conformance Test Suite (PCTS) which tests for conformance to NIST's Federal Information Standard 151-1 (FIPS 151-1) and results in a Cer- tificate of Validation issued by NIST. 21 XPG3 BASE branding is awarded by X/Open[TM] Company Limited to sys- tems which are compliant to the base specifications as defined in the X/Open Portability Guide Issue 3 (XPG3). The Branding certificate is obtained after successfully passing the X/Open Verification Test Suite for XPG3 (VSX4 in XPG3 mode) and declaring conformance to the spec- ifications in the XPG3. The OpenVMS AXP environment with POSIX for OpenVMS AXP is expected to obtain the NIST Certificate of Validation for FIPS 151-1 and XPG3 Base branding from X/Open. Refer to the POSIX for OpenVMS AXP Software Prod- uct Description (SPD 47.49.xx) for more information. Support for OSF/Motif and X Window System Standards DECwindows Motif provides support for both OSF/Motif, a standards-based graphical user interface, and the X Consortium's X Window System. Standards Listing These standards are American National Standards Institute (ANSI), U.S. Federal Information Processing (FIPS), and International Standards Or- ganization (ISO) standards. The following information may be useful in determining responsiveness to stated conformance requirements as enabled in particular commercial or government procurement solicita- tion documents: o ANSI X3.4-1986: American Standard Code for Information Interchange o ANSI X3.22-1973: Recorded Magnetic Tape (800 BPI, NRZI) o ANSI X3.27-1987: File Structure and Labeling of Magnetic Tapes for Information Interchange o ANSI X3.39-1986: Recorded Magnetic Tape (1600 BPI, PE) o ANSI X3.40-1983: Unrecorded Magnetic Tape o ANSI X3.41-1974: Code Extension Techniques for Use with 7-bit ASCII o ANSI X3.42-1975: Representation of Numeric Values in Character Strings o ANSI X3.54-1986: Recorded Magnetic Tape (6250 BPI, GCR) o ANSI X3.131-1986 (SCSI I): Small Computer System Interface 22 o ANSI/IEEE 802.2-1985: Logical Link Control o ANSI/IEEE 802.3-1985: Carrier Sense Multiple Access with Collision Detection o FIPS 1-2: Code for Information Interchange, its Representations, Subsets, and Extensions Note: FIPS 1-2 includes ANSI X3.4-1977(86)/FIPS 15; ANSI X3.32-1973 /FIPS 36; ANSI X3.41-1974/FIPS 35; and FIPS 7. o FIPS 3-1/ANSI X3.22-1973: Recorded Magnetic Tape Information In- terchange (800 CPI, NRZI) o FIPS 16-1/ANSI X3.15-1976: Bit Sequencing of the Code for Infor- mation Interchange in Serial-by-bit Data Transmission Note: FED STD 1010 adopts FIPS 16-1. o FIPS 25/ANSI X3.39-1986: Recorded Magnetic Tape for Information In- terchange (1600 CPI, Phase Encoded) o FIPS 37/ANSI X3.36-1975: High Speed Data Signaling Rates Between Data Terminal Equipment and Data Communication Equipment Note: FED STD 1001 adopts FIPS 37. o FIPS 50/ANSI X3.54-1986: Recorded Magnetic Tape for Information In- terchange, 6250 CPI (246 CPMM), Group Coded Recording o FIPS 79/ANSI X3.27-1987: Magnetic Tape Labels and File Structure for Information Interchange o FIPS 86/ANSI X3.64-1979: Additional Controls for Use with Ameri- can National Standard Code for Information Interchange Note: Other FIPS not applicable. Note: Information regarding interchangeability of ANSI and FED stan- dards with FIPS is contained in "ADP Telecommunications Standards Index," July 1988, published and maintained by the General Services Administration. o ISO 646: ISO 7-bit Coded Character Set for Information Exchange 23 o ISO 1001: File Structure and Labeling of Magnetic Tapes for Infor- mation Interchange o ISO 1863: Information Processing - 9-track, 12, 7 mm (0.5 in) wide magnetic tape for information interchange recorded at 32 rpmm (800 rpi) o ISO 1864: Information Processing - Unrecorded 12, 7 mm (0.5 in) wide magnetic tape for information interchange - 35 ftpmm (800 ftpi) NRZI, 126 ftpmm (3,200 ftpi) phase encoded, and 356 ftmm (9,042 ftpi) NRZI o ISO 2022: Code Extension Techniques for Use with ISO 646 o ISO 3307: Representations of Time of the Day o ISO 3788: Information Processing - 9-track, 12, 7 mm (0.5 in) wide magnetic tape for information interchange recorded at 63 rpmm (1 600 rpt) phase encoded o ISO 4873: 8-bit Code for Information Interchange - Structure and Rules for Implementation o ISO 5652: Recorded Magtape (6250) o ISO 6429: Control Functions for Coded Character Sets o ISO 9660: Information processing - Volume and file structure of CD- ROM for information interchange. o ISO 9945-1: POSIX IEEE 1003.1-1990. INSTALLATION OpenVMS AXP is distributed as a binary kit on CD-ROM. Procedures for setting up the system disk from media and for preparing the system for day-to-day operations are provided. The procedures are described in the OpenVMS Alpha Upgrade and Installation Manual and cover letter. Test Package and Diagnostics OpenVMS AXP includes a user environment test package (UETP) which ver- ifies that the OpenVMS AXP operating system is properly installed and ready for use on the customer's systems. 24 Diagnostics can be run on individual devices during normal system op- eration. Certain critical components can operate in degraded mode. OpenVMS AXP DISK SPACE REQUIREMENTS OpenVMS AXP Operating System The disk space requirement for OpenVMS AXP files after installation is approximately 180 MB. This figure does not include space for the page, swap, and dump files. Running the AUTOGEN procedure on a 32-MB- memory system creates the page file, swap file, and dump file. An ad- ditional 67 MB of disk space is needed as AUTOGEN creates files of the following size: ___________________________________________________________________ Page_File___Swap_File____Dump_File_________________________________ 37 MB 6 MB 24 MB (required)__(suggested)__(optional)________________________________ Most systems will require larger page and swap files depending upon the system workload. This figure also includes Help library files in data-compressed for- mat. Most system managers choose to expand these files for faster ac- cess. The expansion requires approximately an additional 8 MB. To support full OpenVMS AXP, a system disk of at least 225 MB is re- quired. This includes: ___________________________________________________________________ Page_File___Swap_File____Dump_File_________________________________ 37_MB_______6_MB_________No_Dump_File______________________________ 25 A system disk of at least 400 MB is recommended to handle temporary disk space usage during an operating system upgrade to its next re- lease. This includes: ___________________________________________________________________ Page_File___Swap_File____Dump_File_________________________________ 37_MB_______6_MB_________24_MB_____________________________________ Refer to the OpenVMS Alpha Upgrade and Installation Manual for infor- mation on system disk requirements. OpenVMS AXP Operating System and DECwindows Motif for OpenVMS AXP To support full OpenVMS AXP and full DECwindows Motif for OpenVMS AXP, a system disk of at least 280 MB is required. This includes: ___________________________________________________________________ Page_File___Swap_File____Dump_File_________________________________ 37_MB_______6_MB_________No_Dump_File______________________________ A system disk of at least 485 MB is recommended to handle temporary disk space usage during an operating system upgrade to its next re- lease. This includes: ___________________________________________________________________ Page_File___Swap_File____Dump_File_________________________________ 37_MB_______6_MB_________24_MB_____________________________________ Refer to the OpenVMS Alpha Upgrade and Installation Manual for infor- mation on system disk requirements. 26 Additional disk space will be required for layered product installa- tion on the system disk. Due to space constraints, there is no guar- antee that layered products can be installed if user files reside on the system disk. Refer to layered product installation guides for lay- ered product disk space requirements. Memory Requirements The minimum amount of memory required for a system user to install, boot, and log in to an OpenVMS AXP system is 32 MB. To ensure satis- factory performance of some applications, additional memory may be re- quired. Please refer to specific layered product Software Product De- scriptions for their memory requirements. Please refer to the OpenVMS AXP documentation for more information on performance. GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. DISTRIBUTION MEDIA CD-ROM DOCUMENTATION Digital offers OpenVMS AXP documentation in a variety of formats: o Printed books (hardcopy) o Online viewable books (using the DECwindows Motif for OpenVMS AXP Bookreader) o Printable files 27 OpenVMS AXP customers automatically receive the entire OpenVMS AXP doc- umentation offering in online viewable format on their OpenVMS AXP CD-ROM. Viewing online documentation requires that DECwindows Motif for Open- VMS AXP be installed on the system and that a valid DECwindows Motif for OpenVMS AXP license is registered and loaded. See the DECwindows Motif for OpenVMS AXP Software Product Description (SPD 42.19.xx) for ordering and licensing information. In addition, OpenVMS AXP documentation is organized to offer a choice of three sets of hardcopy documentation: the Base Documentation Set, the Standard Documentation Set, and the Standard + Optional Documen- tation Set. o Base Documentation Set-a desktop set for users of small standalone systems or users connected to large OpenVMS AXP systems. The Base Documentation Set contains information on the activities that you are most likely to perform as a user or a system manager of a small standalone system. It also includes system security information. It contains no programming information. o Standard Documentation Set-a full documentation set for users who need extensive explanatory information on all major OpenVMS AXP re- sources, complete reference information on system routines and util- ities, detailed examples, master indexes, a glossary, and infor- mation on the Help Message facility. The Standard Documentation Set meets the needs of system managers and of system and application programmers. It includes the Base Documentation Set as well as four other kits: - Master Reference - Advanced System Management - Networking - Programming o Standard + Optional Documentation Set-for customers who need all available OpenVMS documentation. This set includes the Standard Doc- umentation Set and all optional documentation. 28 Most manuals contain information that is common to both OpenVMS VAX and OpenVMS AXP systems. Any functional differences between the two are clearly described in the text and marked with margin icons. In ad- dition, a small number of books have been produced specifically for the OpenVMS AXP operating system or the OpenVMS VAX operating system. OpenVMS AXP hardcopy documentation customers receive OpenVMS common manuals and OpenVMS AXP-specific manuals. An additional hardcopy documentation offering delivers all OpenVMS com- mon manuals, OpenVMS VAX-specific manuals, and OpenVMS AXP-specific manuals. Users running OpenVMS on both VAX and Alpha AXP systems, can use one order number for all OpenVMS operating system documentation needs. A complete listing of all the documentation kits and their con- tents is in the Overview of OpenVMS Documentation. Note: Each book in these sets is also separately orderable. SOURCE LISTINGS OpenVMS AXP Operating System Source Listings are available on compact disc. These discs contain all source listings files that make up the OpenVMS AXP operating system. Digital provides source listings for all key modules of the OpenVMS AXP operating system that are appropriate for end users or application developers. Certain source listings, how- ever, are excluded from the compact disc. The orderable compact disc kit includes the license required to view these files on a standalone system or a VMScluster system. If users want to make these files available to another system (possibly at a remote site), they will need to purchase another kit. A source license agreement must be signed for all kits. Contact your local Digital representative for more information. 29 ORDERING INFORMATION Licenses QL-MT1A*-6* OpenVMS AXP Operating System Base License QL-MT1A9-6* OpenVMS AXP Operating System Symmetric Multiprocess- ing (SMP) Base Extension License QL-MT2A*-** OpenVMS AXP Interactive User License Media and Online Documentation QA-MT1AA-H8 OpenVMS AXP software and online documentation com- pact disc QA-MT3AA-H8 OpenVMS VAX/AXP software and online documentation compact discs Digital Layered Product Media QA-03XAA-H8 Digital CD-ROM Software Library for OpenVMS AXP Hardcopy Documentation Sets QA-MT1AB-GZ OpenVMS AXP Base Documentation Set QA-MT1AA-GZ OpenVMS AXP Standard Documentation Set QA-MT1AH-GZ OpenVMS AXP Standard + Optional Documentation Set QA-MT3AB-GZ OpenVMS VAX/AXP Base Documentation Set QA-MT3AA-GZ OpenVMS VAX/AXP Standard Documentation Set QA-MT3AH-GZ OpenVMS VAX/AXP Standard + Optional Documentation Set Source Listings Kits QB-MT1AB-E8 OpenVMS AXP Listings CD-ROM Kit & License 30 Software Product Services QT-MT1A*-** Base System Software Support Service QT-MT2A*-** Interactive User Software Support Service A variety of integrated and à la carte hardware and software product services are available. For additional information, please contact your local Digital office. Media and Documentation Update Service QT-MT1AA-E8 OpenVMS AXP software and online documentation com- pact disc QT-MT3AA-E8 OpenVMS VAX/AXP software and online documentation compact discs Digital Layered Product Media Service QT-03XAA-C8 Digital CD-ROM Software Library for OpenVMS AXP Hardcopy Documentation Only Update Service QT-MT1AB-KZ OpenVMS AXP Base Documentation Set QT-MT1AA-KZ OpenVMS AXP Standard Documentation Set QT-MT1AH-KZ OpenVMS AXP Standard + Optional Documentation Set QT-MT3AB-KZ OpenVMS VAX/AXP Base Documentation Set QT-MT3AA-KZ OpenVMS VAX/AXP Standard Documentation Set QT-MT3AH-KZ OpenVMS VAX/AXP Standard + Optional Documentation Set Source Listings Service 31 QT-MT1AB-Q8 OpenVMS AXP Source Listings Service * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate Digital price book. SOFTWARE LICENSING The OpenVMS AXP operating system software is furnished under the li- censing provisions of Digital Equipment Corporation's Standard Terms and Conditions. The OpenVMS AXP operating system license also includes the license for DECprint Supervisor for OpenVMS, Base. The DECprint Supervisor for OpenVMS has separate documentation, media kit, and service products. Refer to DECprint Supervisor for OpenVMS Software Product Description (SPD 44.15.xx) for more information. The System Integrated Product DECnet for OpenVMS AXP is a separately licensed product. Refer to the DECnet for OpenVMS AXP Software Prod- uct Description (SPD 42.25.xx) for more information. The System Integrated Product VMScluster Software is a separately li- censed product. Refer to the VMScluster Software Product Description (SPD 42.18.xx) for more information. DECwindows Motif for OpenVMS AXP is a separately licensed layered prod- uct. Refer to the DECwindows Motif for OpenVMS AXP Software Product Description (SPD 42.19.xx) for more information. DECram for OpenVMS AXP is a separately licensed layered product. Re- fer to the DECram for OpenVMS AXP Software Product Description (SPD 34.26.xx) for more information. DECmigrate for OpenVMS AXP Systems is a separately licensed layered product. Refer to the DECmigrate for OpenVMS AXP Systems Software Prod- uct Description (SPD 39.44.xx) for more information. OpenVMS AXP License Information 32 There are three types of OpenVMS licenses available on Alpha AXP pro- cessors. 1. Operating System Base License (QL-MT1A*-6*) This license grants the right to non-interactive use of the remote batch, print, application, and computing services of the OpenVMS AXP oper- ating system on a single processor. This license authorizes one di- rect login for system management purposes only. The Operating System Base License is a prerequisite for Interactive User Licenses and SMP Extension Licenses. The Operating System Base License provides the right to use only the OpenVMS AXP features of the current version license. 2. Symmetric Multiprocessing (SMP) Base Extension License (QL-MT1A9- 6*) SMP Extensions extend the Operating System Base License to enable Sym- metric Multiprocessing capability on those OpenVMS AXP systems sup- porting SMP. SMP Extensions are permanently tied to the Operating Sys- tem Base License and may not be separated from the Operating System Base Licenses if an SMP board is removed from the system. SMP Extensions grant the right to use the same version of the oper- ating system software as permitted for the corresponding Operating Sys- tem Base License at the time when the SMP Extension is installed. 3. Interactive User License (QL-MT2A*-**) This license grants the right to interactive use of the OpenVMS AXP operating system, provided the appropriate Operating System Base Li- cense has been previously installed on the Alpha AXP system. These In- teractive User licenses, which are concurrent use licenses, are avail- able in any quantity desired or as an unlimited user license. A user is defined as an individual who is logged on to a processor and/or is interactively using the operating system software by means other than login. 33 When an Alpha AXP SMP System upgrade is performed, the SMP Extension to the OpenVMS AXP Operating System License permits the use of all ex- isting Interactive User Licenses (including Unlimited Users) on the upgraded system. This License grants the right to use the same version of the operat- ing system software as permitted for the corresponding operating sys- tem when the Interactive User License is installed. License Management Facility Support The OpenVMS AXP operating system supports Digital's License Manage- ment Facility (LMF). If an OpenVMS AXP license is not registered and activated using the License Management Facility, then only a single login is permitted for system management purposes through the system console (OPA0:). OpenVMS AXP Interactive User Licenses define the number of concurrent users that are activity licenses as defined by the LMF. OpenVMS AXP defines activities, sometimes referred to as an OpenVMS AXP "user," as follows: o Each remote terminal connection is considered an activity. This is true even if users set host to their local node (SET HOST 0). o Each connection from a terminal server is considered an activity. o A multiple-window session on a workstation is considered one ac- tivity, regardless of the number of windows. o A batch job is not considered an activity. o A remote network connection that is a connection other than a re- mote terminal connection, is not considered an activity. For more information about Digital's licensing terms and policies, con- tact your 34 SOFTWARE PRODUCT SERVICES A variety of service options are available from Digital. For more in- formation, contact your local Digital office. SOFTWARE WARRANTY Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the Software Warranty Addendum of this SPD and the applicable Digital Standard Terms and Con- ditions. SUPPORTED HARDWARE The following tables list supported hardware for OpenVMS AXP, DECwin- dows Motif for OpenVMS AXP, DECnet for OpenVMS AXP, and VMSclusters. Combinations of hardware options are subject to limitations such as bandwidth, physical configuration constraints, and electrical load and power supply. The content of this hardware configuration section is intended to spec- ify the device limitations and provide a general guide. It does not describe all possible hardware configurations or circumstances. Any particular configuration should be discussed with Digital. Contact Dig- ital for the most up-to-date information on possible hardware config- urations. Digital reserves the right to change the number and type of devices supported by OpenVMS AXP, DECwindows Motif for OpenVMS AXP, DECnet for OpenVMS AXP, and VMSclusters. The minimum hardware requirements for future versions and updates of OpenVMS AXP, DECwindows Motif for Open- VMS AXP, DECnet for OpenVMS AXP, and VMSclusters may be different from current hardware requirements. For configuration details about Alpha AXP systems, refer to the Digital Systems and Options Catalog and the Networks and Communications Buyers Guide. A listing of Digital terminals, disks, tapes, controllers, communi- cations options, and VMScluster options is in Appendix A. Some restric- tions for specific devices are listed if applicable. 35 Refer to the individual SPDs for DECnet for OpenVMS AXP (SPD 42.25.xx) and VMScluster Software (SPD 42.18.xx) for detailed product informa- tion. How to Read the Tables The first column lists the Alpha AXP system, the media (CD-ROM) from which the OpenVMS AXP operating system can be loaded onto the system disk, and the type and maximum number of busses supported on the sys- tem. The second column lists the disk controllers and drives that can be used on the system. A disk controller can be used with any disk drive listed next to it. The third column lists the tape controllers and drives that can be used on the system. The tape controller can be used with any tape drive listed next to it. The fourth column lists the communications options available for the systems. The listed Ethernet devices can also be used for network con- nections. The fifth column lists other hardware that can be used and the max- imum amount of memory allowed on the systems in each category. 36 ___________________________________________________________________ Miscellaneous System Disks Tapes ________________ _______________ Options (LAN __________CTRL_____DRIVE_____CTRL___DRIVE____________/CI)__________ DEC 3000 Integral RRD42 IntegralTLZ04 Integral 128 Models RWZ01 TLZ06 MB 300, SCSI RZ23L SCSI TZ30 Ethernet Max 300L RZ24 TZK10 Mem RZ25 RZ26 PMAGB- (BUS) RZ26B BE SCSI RZ55 PMTCE(1) TURBOchannel RZ56 RX26 RZ58 Note: Factory-loaded software on all configurations that include internal disks. Supports_Display_PostScript._______________________________________ 37 ___________________________________________________________________ Miscellaneous System Disks Tapes ________________ _______________ Options (LAN __________CTRL_____DRIVE_____CTRL___DRIVE____________/CI)__________ DEC 3000 Integral RRD42 IntegralTKZ09 IntegralDEFZA Model Models RWZ01 TKZ60 (1) 400, 400, SCSI RZ23L SCSI TLZ04 EthernetPMAD 400S 400S, RZ24 TLZ06 (1) 128 500, RZ25 TSZ05 MB 500S, RZ26 TSZ07 Max 500X RZ26B TZK10 Mem RZ55 TZ30 (BUS) RZ56 TZ85 Model SCSI RX26 TZ857 500, TURBOchannel RZ24L TZ86 500S, RZ58 TZ867 500X 256 MB Max Mem PMAGB- BE PMTCE (1) Note: Factory-loaded software on all configurations that include internal disks. Supports_Display_PostScript._______________________________________ 38 ___________________________________________________________________ Miscellaneous System Disks Tapes ________________ _______________ Options (LAN __________CTRL_____DRIVE_____CTRL___DRIVE____________/CI)__________ DEC 4000 Integral RRD42 IntegralTKZ09 Integral 512 Model RZ26 TLZ06 MB 600 Se- SCSI RZ73 SCSI TSZ07 Ethernet Max ries RZ74 TZ30 Mem TZ85 (BUS) RF30 TZ857 SCSI (5) Integral RF31 TZ86 DSSI (4) RF31T TZ867 DSSI RF35 RF71 TF85 RF72 IntegralTF857 RF73 DSSI Note: Factory loaded software on all configurations that include internal disks. ___________________________________________________________________ 39 ___________________________________________________________________ Miscellaneous System Disks Tapes ________________ _______________ Options (LAN __________CTRL_____DRIVE_____CTRL___DRIVE____________/CI)__________ DEC 7000 KDM70 ESE52 KDM70 TA78 CIXCD 3.5 Model HSC** ESE56 HSC** TA81 (2) GB 600 Se- CIXCD ESE58 CIXCD TA90 DEMFA Max ries (2) RA72 (2) DEMNA Mem RA73 (BUSSES) RA90 KZMSA TKZ09 SCSI RA92 TKZ60 XMI (4) TLZ06 KZMSA RRD42 TSZ07 RWZ01 TZ85 RZ26 TZ857 RZ73 TZ86 RZ74 TZ867 Note: Maximum number of KDM70: 3 per XMI; 12 per system. Maximum number of KZMSA: 4 per XMI; 6 per system. Maximum number of DEMFA: 4 per XMI; 4 per system. Maximum_number_of_DEMNA:_4_per_XMI;_6_per_system.__________________ 40 ___________________________________________________________________ Miscellaneous System Disks Tapes ________________ _______________ Options (LAN __________CTRL_____DRIVE_____CTRL___DRIVE____________/CI)__________ DEC KDM70 ESE52 KDM70 TA78 CIXCD 3.5 10000 HSC** ESE56 HSC** TA81 (2) GB Model CIXCD ESE58 CIXCD TA90 DEMFA Max 600 Se- (2) RA72 (2) DEMNA Mem ries RA73 RA90 KZMSA TKZ09 (BUSSES) RA92 TKZ60 SCSI TLZ06 XMI (4) KZMSA RRD42 TSZ07 RWZ01 TZ85 RZ26 TZ857 RZ73 TZ86 RZ74 TZ867 Note: Maximum number of KDM70: 3 per XMI; 12 per system. Maximum number of KZMSA: 4 per XMI; 6 per system. Maximum number of DEMFA: 2 per XMI; 2 per system. Maximum_number_of_DEMNA:_4_per_XMI;_6_per_system.__________________ 41 Appendix A This appendix describes Digital terminals, disks, tapes, controllers, graphics, and network options. Some restrictions for specific devices are listed if applicable. Terminals and Terminal Line Interfaces The following table lists the terminals that are supported by Open- VMS AXP. To prevent input from overflowing a buffer, terminals use the ASCII control characters DC1 and DC3 for synchronization as defined by Digital's DEC STD 111, Revision A. VXT windowing terminals support standard ANSI applications and "X" windows using the LAT transport pro- tocol. VT200- VT300-series series VT400- VXT 2000-series series Disks The first column lists the device name. The second column is a descrip- tion of the device. The third column lists the bus the device is sup- ported on. The fourth column lists the device's protocol. The fifth column lists the minimum required version of OpenVMS AXP that supports these devices. RA72 1 GB fixed disk SDI MSCP 1.0 drive RA73 2 GB fixed disk SDI MSCP 1.0 drive RA90 1.2 GB fixed disk SDI MSCP 1.0 drive RA92 1.5 GB fixed disk SDI MSCP 1.0 drive 42 ESE-52 120 MB solid state SDI MSCP 1.0 disk ESE-56 600 MB solid state SDI MSCP 1.5 disk ESE-58 960 MB solid state SDI MSCP 1.5 disk RF30 150 MB fixed disk DSSI MSCP 1.5 drive RF31 381 MB fixed disk DSSI MSCP 1.5 drive RF31T 381 MB fixed disk DSSI MSCP 1.5 drive RF35 800 MB fixed disk DSSI MSCP 1.0 drive RF71 400 MB fixed disk DSSI MSCP 1.5 drive RF72 1 GB fixed disk DSSI MSCP 1.5 drive RF73 2 GB fixed disk DSSI MSCP 1.0 drive RRD42 600 MB read-only SCSI SCSI 1.0 optical disk drive RWZ01 594 MB optical SCSI SCSI 1.0 removable disk drive RX26 2.8 MB diskette SCSI SCSI 1.0 drive RZ24L 245 MB fixed disk SCSI SCSI 1.0 drive RZ25 425 MB fixed disk SCSI SCSI 1.0 drive RZ26 1.05 GB fixed disk SCSI SCSI 1.0 drive 43 RZ26B 1.05 GB fixed disk SCSI SCSI 1.5 drive RZ55 332 MB fixed disk SCSI SCSI 1.0 drive RZ56 665 MB fixed disk SCSI SCSI 1.0 drive RZ58 1.35 GB fixed disk SCSI SCSI 1.0 drive RZ73 2 GB fixed disk SCSI SCSI 1.0 drive RZ74 3.57 GB fixed disk SCSI SCSI 1.5 drive Tapes The first column lists the device name. The second column is a descrip- tion of the device. The third column lists the device's protocol. The fourth column lists the bus the device is supported on. The fifth col- umn lists the minimum required version of OpenVMS AXP that supports these devices. TA78 1600/6250 BPI, STI TMSCP 1.0 STI TU78 TA81 145 MB tape drive STI TMSCP 1.0 TA90 1.2 GB tape car- STI TMSCP 1.0 tridge subsystem. (5-inch 200 MB car- tridge) TKZ09 5.0 GB, 8mm tape SCSI SCSI 1.5 drive TKZ60 200 MB, 3480 tape SCSI SCSI 1.0 drive (no compression) 44 TLZ04 1.2 GB, 4mm, DAT SCSI SCSI 1.0 tape drive TLZ06 4 GB, 4mm, DAT tape SCSI SCSI 1.0 drive TSZ05 1600 BPI tape drive SCSI SCSI 1.5 TSZ07 1600/6250 BPI tape SCSI SCSI 1.0 drive TZ30 95 MB, 5-1/4-inch, SCSI SCSI 1.0 half-height, tape drive TZ85 2.6 GB tape drive SCSI SCSI 1.0 TZ857 18 GB tape loader SCSI SCSI 1.0 TZ86 6.0 GB tape drive SCSI SCSI 1.5 TZ867 42 GB tape loader SCSI SCSI 1.5 TZK10 320/525 MB, QIC SCSI SCSI 1.0 (Quarter Inch Car- tridge), tape drive Controllers HSC40 Hierarchical Storage Controller for MSCP served disks and TMSCP served tapes. (HSC software must be at mini- mum Version 8.1) HSC50 Hierarchical Storage Controller for MSCP served disks and TMSCP served tapes. (HSC software must be at mini- mum Version 4.1) HSC60 Hierarchical Storage Controller for MSCP served disks and TMSCP served tapes. (HSC software must be at mini- mum Version 8.1) HSC65 Hierarchical Storage Controller for MSCP served disks and TMSCP served tapes. (HSC software must be at mini- mum Version 8.1) 45 HSC70 Hierarchical Storage Controller for MSCP served disks and TMSCP served tapes. (HSC software must be at mini- mum Version 8.1) HSC90 Hierarchical Storage Controller for MSCP served disks and TMSCP served tapes. (HSC software must be at mini- mum Version 8.1) HSC95 Hierarchical Storage Controller for MSCP served disks and TMSCP served tapes. (HSC software must be at mini- mum Version 8.1) KDM70 An intelligent MSCP/TMSCP mass-storage controller for XMI systems with eight ports that support RA Series Disks and Storage Arrays, TA Series Tape, and Solid State Disks. KZMSA An intelligent mass-storage controller for XMI systems with two SCSI ports that support RZ Series Disks and Storage Arrays and TZ Series Tape. Graphics Options PMAGB A multi-screen graphics adapter for TURBOchannel systems to connect multiple 8-plane color or grayscale monitors. LAN Options DEFZA A high-performance network adapter that connects TUR- BOchannel systems to ANSI FDDI local area networks. (DMA receive only) DEMFA A high-performance network adapter that connects XMI systems to ANSI FDDI local area networks. DEMNA A high-performance network adapter that connects XMI systems to both the Ethernet and IEEE 802.3 local area networks. 46 PMAD A network adapter that connects TURBOchannel systems to both the Ethernet and IEEE 802.3 local area networks. CI Options CIXCD-AC Native CI adapter for DEC 7000 and 10000 AXP XMI sys- tems. (minimum microcode version REV 1.0 is required) Miscellaneous InfoServer An integrated hardware/software system which sits directly on the Ethernet to provide CD-ROM, hard disk, magneto optical, and tape access to OpenVMS clients in a local area network. It supports up to 14 SCSI devices and can be used for software distribution and initial system load (ISL). For more information refer to the InfoServer Software Product Description (SPD 33.20.xx.) Acronyms DSSI Digital Storage Systems Interconnect FDDI Fiber Distributed Data Interconnect IEEE Institute for Electrical and Electronic Engineers MSCP Mass Storage Control Protocol SCSI Small Computer System Interconnect SDI Standard Drive Interface STI Standard Tape Interface TMSCP Tape Mass Storage Control Protocol XMI Extended Memory Interconnect 47 Appendix B Third-Party Licensing Adobe Systems Incorporated, License Terms and Agreement In addition to the licensing provisions of Digital Equipment Corpo- ration's Standard Terms and Conditions, the following additional Li- cense Terms and Conditions are imposed by Adobe with respect to Dis- play PostScript: 1. Digital grants to customer a nonexclusive sublicense, subject to Paragraph 5 below and the other provisions hereof (a) to use the PostScript Software and associated software documentation furnished with this pack- age ("Software") solely for customer's own internal business purposes on a single Digital computer system; (b) to use the digitally-encoded machine-readable outline and bitmap programs ("Font Programs") pro- vided by Digital in a special encrypted format ("Coded Font Programs") and identified in Paragraph 6 below to reproduce and display designs, styles, weights, and versions of letters, numerals, characters and sym- bols ("Typefaces" and "Screen Typefaces") solely for customer's own customary business or personal purposes on the screen of the Digital computer system; and (c) to use the trademarks used by Digital to iden- tify the Coded Font Programs and Typefaces reproduced therefrom ("Trade- marks"). Customer may assign its rights under this Agreement to a li- censee of all of customer's right, title and interest to such Soft- ware and Coded Font Programs provided the licensee agrees to be bound by all of the terms and conditions of this Agreement. 2. Customer acknowledges that the Software, Coded Font Programs, Type- faces and Trademarks are proprietary to Digital and its suppliers. Cus- tomer agrees to hold the Software and Coded Font Programs in confi- dence, disclosing the Software and Coded Font Programs only to autho- rized employees having a need to use the Software and Coded Font Pro- grams as permitted by this Agreement and to take all reasonable pre- cautions to prevent disclosure to other parties. 48 3. Customer will not adapt or use any trademark or trade name which is likely to be similar to or confusing with that of Digital or any of its suppliers or take any other action which impairs or reduces the trademark rights of Digital or its suppliers. Any use of the Trade- marks must identify the applicable "Trademark Owner" set forth in Para- graph 6 hereto as the owner of such Trademarks. At the reasonable re- quest of Digital, customer must supply samples of any Typeface iden- tified by a Trademark. 4. The Software licensed hereunder is restricted to use to generate screen displays on a single Digital computer system having a screen resolution of less than or equal to 150 dots/per/inch. Customer agrees not to make use of the software, directly or indirectly, to print bitmap images with print resolutions of greater than 150 dots/per/inch, or to generate Fonts or Typefaces for use other than with the Digital com- puter systems. Any failure of customer to comply with this provision is a material breach of Digital's licensing provisions. 5. Customer agrees that Adobe Systems Incorporated is a third party beneficiary of the license agreement covering Software. 6. Coded Font Programs: ___________________________________________________________________ Identifying Trademark___Typeface_____Trademark_Owner___________________________ Times Roman Linotype-Hell AG and/or its subsidiaries Times Bold Linotype-Hell AG and/or its subsidiaries Times Italic Linotype-Hell AG and/or its subsidiaries Times Bold Linotype-Hell AG and/or its subsidiaries Italic Helvetica Linotype-Hell AG and/or its subsidiaries Helvetica Bold Linotype-Hell AG and/or its subsidiaries 49 Identifying________________________________________________________ Trademark___Typeface_____Trademark_Owner___________________________ Helvetica Oblique Linotype-Hell AG and/or its subsidiaries Helvetica Bold Linotype-Hell AG and/or its subsidiaries Oblique Symbol Public Domain Courier Public Domain Courier Bold Public Domain Courier Oblique Public Domain Courier Bold Public Domain Oblique ITC Sou- Light International Typeface Corporation venir ITC Sou- Light International Typeface Corporation venir Italic ITC Sou- Demi International Typeface Corporation venir ITC Sou- Demi International Typeface Corporation venir Italic ITC Avant Book International Typeface Corporation Garde Gothic ITC Avant Book International Typeface Corporation Garde Oblique Gothic ITC Avant Demi International Typeface Corporation Garde Gothic ITC Avant Demi International Typeface Corporation Garde Oblique Gothic 50 Identifying________________________________________________________ Trademark___Typeface_____Trademark_Owner___________________________ ITC Book International Typeface Corporation Lubalin Graph ITC Book International Typeface Corporation Lubalin Oblique Graph ITC Demi International Typeface Corporation Lubalin Graph ITC Demi International Typeface Corporation Lubalin Oblique Graph New Cen- Roman Public Domain tury Schoolbook New Cen- Italic Public Domain tury Schoolbook New Cen- Bold Public Domain tury Schoolbook New Cen- Bold Public Domain tury Italic Schoolbook_________________________________________________________ (R) Adobe, Display PostScript, and PostScript are trademarks of Adobe Systems, Inc. (R) IBM is a registered trademark of International Business Ma- chines Corporation. 51 (R) Motif and OSF/Motif are registered trademarks of Open Software Foundation, Inc. (R) Sun is a registered trademark of Sun Microsystems, Inc. [TM]X/Open is a trademark of X/Open Company Limited. [TM]The DIGITAL logo, Alpha AXP, AXP, Bookreader, CDA, CI, DEC, DEC Fortran, DECdtm, DECmigrate, DECnet, DECprint, DECthreads, DECtp, DECwindows, Digital, DNA, EDT, HSC, KDM, MSCP, OpenVMS, RA, RRD42, RX, RZ, SDI, STI, TA, TMSCP, TURBOchannel, UETP, VAX, VMScluster, VT300, VXT2000, and XUI are trademarks of Digital Equipment Corporation. 52