Software Product Description ___________________________________________________________________ PRODUCT NAME: OpenVMS AXP Operating System, Version 1.0 SPD 41.87.00 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 can be tuned to perform well in a wide variety of applications, including compute- intensive, I/O-intensive, real-time, and combinations of those and other environments. Actual performance depends on the type of computer, avail- able physical memory, and the number 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. OpenVMS AXP software supports a large number of industry standards, facilitating application portability and interoperability. OpenVMS AXP Version 1.0 is the first release of the OpenVMS operat- ing system for Digital's 64-bit Alpha AXP architecture. This release contains many features of the OpenVMS VAX operating system. Please note that application virtual address space is a 32-bit implementation for compatibility and migration purposes. A complete 64-bit OpenVMS AXP implementation is under investigation. OpenVMS AXP compilers take ad- vantage of 64 bits by using 64-bit data-types. Consult the Software Product Descriptions of OpenVMS AXP compilers for further details. DIGITAL October 1992 AE-PREGA-TE 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 language (DECTPU), 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. 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 and DECnet for OpenVMS VAX are installed and licensed on each partic- ipating Alpha AXP and VAX node on the configured network. Command-Level Programming 2 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. 3 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. TFF also allows character composition on terminals that do not have the com- pose 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 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. 4 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. 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 5 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. 6 File Differences Utility The File Differences utility compares the contents of two files and lists those records that do not match. 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 DECmi- grate for OpenVMS AXP layered product can be used to translate Open- VMS VAX images. For additional information on the precise character- istics of programs suitable for binary translation refer to the DECmi- grate 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. 7 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. 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. Backup Utility 8 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). 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, memory management activity, at specified intervals. The data may be displayed as it is gathered or saved in a file for later use. 9 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. 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. 10 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. 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. 11 Security alarms are provided to allow selective auditing of security- related events, including: - Login and logout - Login failures and break-in attempts - Authorization changes - 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. 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. 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. 12 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. 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. 13 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 devicedependent features 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) RMS is a set of I/O services that helps application programs to pro- cess and manage files and records. Although it is primarily intended to provide a comprehensive software interface to mass storage devices, RMS also supports device-independent access 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. 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. 14 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. Disk and Tape Volumes 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 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. 15 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. 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. 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. An unrecoverable error causes the memory page on which the error occurred to be added to the bad page list. Other failures include: o Operating system errors (system-detected inconsistencies or archi- tectural errors in system context) o User errors 16 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: - Mailboxes are virtual devices that allow processes to communicate with queued messages. - Shared memory sections on a single processor permit multiple pro- cesses to access shared address space concurrently. - Common event flags provide simple synchronization. - The lock manager provides a more comprehensive enqueue/dequeue fa- cility with multilevel locks, values, and ASTs (asynchronous sys- tem traps). Networking Facilities OpenVMS AXP provides device drivers for all Digital Ethernet adapters listed in the Network Options section of Appendix A of this SPD. Ap- plication 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 protocols are supported on any Digital Ethernet adapter. 17 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. 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. 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[TM], 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 18 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. 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. The number of DECram units used will most often be quite small (usu- ally one, but sometimes two or more). 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. These standards are American National Standards Institute (ANSI), U.S. Federal Information Processing (FIPS), and In- ternational Standards Organization (ISO) standards. The following in- formation may be useful in determining responsiveness to stated con- formance requirements as enabled in particular commercial or govern- ment procurement solicitation documents: o ANSI X3.4-1986: American Standard Code for Information Interchange o ANSI X3.22-1973: Recorded Magnetic Tape (800 BPI, NRZI) 19 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 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 20 o FIPS 86/ANSI X3.64-1979: Additional Controls for Use with Ameri- can National Standard Code for Information Interchange o 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 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 21 INSTALLATION OpenVMS AXP is distributed as a binary kit on CDROM. 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. 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 The disk space requirement for OpenVMS AXP Version 1.0 files after in- stallation is approximately 165 KB. 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 additional 67 MB of disk space is needed as AUTOGEN creates files of the following size: - 37 MB for page file (required) - 6 MB for swap file (suggested) - 24 MB for dump file (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 210 MB is re- quired. This includes: - 37 MB for page file 22 - 6 MB for swap file - and no dump file 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: - 37 MB for page file - 6 MB for swap file - 24 MB for dump file Refer to the OpenVMS Alpha Upgrade and Installation Manual for infor- mation on system disk requirements. To support full OpenVMS AXP and full DECwindows Motif for OpenVMS AXP, a system disk of at least 280 MB is required. This includes: - 37 MB for page file - 6 MB for swap file - and no dump file A system disk of at least 470 MB is recommended to handle temporary disk space usage during an operating system upgrade to its next re- lease. This includes: - 37 MB for page file - 6 MB for swap file - 24 MB for dump file Refer to the OpenVMS Alpha Upgrade and Installation Manual for infor- mation on system disk requirements. 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. 23 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 CDROM DOCUMENTATION Digital offers OpenVMS AXP documentation in a variety of formats: - printed books (hardcopy) - online viewable books (using the DECwindows Motif for OpenVMS AXP Bookreader) - printable files OpenVMS AXP customers automatically receive the entire OpenVMS AXP doc- umentation offering in online viewable format on their OpenVMS AXP CDROM. Viewing online documentation requires that DECwindows Motif for Open- VMS AXP is 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. 24 In addition, OpenVMS AXP documentation is organized to offer a choice of two sets of hardcopy documentation: the Extended Documentation Set or the Base Documentation Set. o Extended 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 utility. The Extended 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 Base Documentation Set-a desktop documentation 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 users are most likely to perform as a user or a system man- ager of a small standalone system. It also includes system secu- rity information. It contains no programming information. Note: Each book in both sets is also separately orderable. Most manuals in the OpenVMS AXP Extended and Base Documentation sets contain information that is common to both OpenVMS AXP and OpenVMS VAX operating systems. Any functional differences between the two are clearly described in the text and marked with margin icons. In addition, a small number of books have been produced specifically for the OpenVMS AXP operating system or the OpenVMS VAX operating system. 25 ORDERING INFORMATION Licenses OpenVMS AXP Operating System Base License: QL-MT1A*-6* OpenVMS AXP Interactive User License: QL-MT2A*-** Media and Online Documentation OpenVMS AXP software and online documentation compact disc: QA-MT1AA-H8 Additional Media Digital CDROM Software Library for OpenVMS AXP: QA-03XAA-H8 Hardcopy Documentation Sets OpenVMS AXP Extended Documentation Set: QA-MT1AA-GZ OpenVMS AXP Base Documentation Set: QA-MT1AB-GZ Software Product Services Software Support Service: QT-MT1A*-** QT-MT2A*-** 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 OpenVMS AXP software and online documentation compact disc: QT-MT1AA-E8 Hardcopy Documentation Only Update Service 26 OpenVMS AXP Extended Documentation Set: QT-MT1AA-KZ OpenVMS AXP Base Documentation Set: QT-MT1AB-KZ * 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 System Integrated Product (SIP), DECnet for OpenVMS AXP is a sep- arately licensed product. Refer to the DECnet for OpenVMS AXP Soft- ware Product Description (SPD 42.25.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 There are two types of OpenVMS licenses available on Alpha AXP pro- cessors. 1. Operating System Base License 27 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. The Operating System Base License provides the right to use only the OpenVMS AXP features of the current version license. 2. Interactive User License 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. This license grants the right to use the same version of the operat- ing system which is permitted under the corresponding Operating Sys- tem Base License at the time of the initial installation of the In- teractive User License. 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: 28 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 local Digital office. 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, and DECnet for OpenVMS AXP. Combinations of hardware options are subject to limitations such as bandwidth, phys- ical 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 29 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. The minimum hardware requirements for fu- ture versions and updates of OpenVMS AXP may be different from cur- rent hardware requirements. For configuration details about Alpha AXP systems, refer to the Digital Systems and Options Catalog and the Net- works and Communications Buyers Guide. A listing of Digital terminals, disks, tapes, controllers, and net- work options is in Appendix A. How to Read the Tables The first column lists the Alpha AXP system, the media (CDROM) 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. 30 ___________________________________________________________________ Table_1:___________________________________________________________ Miscellaneous System Disks Tapes Communication ________________ _______________ (LAN) __________CTRL_____DRIVE_____CTRL___DRIVE__________________________ DEC 3000 Integral RRD42 IntegralTLZ04 DEFZA Model Models RWZ01 TLZ06 (1) 400, 400, SCSI RZ23L SCSI TZK10 PMAD 400S 400S, RZ24 TZ30 (1) 128 500, RZ25 MB 500S RZ26 Integral Max RZ55 Mem (Load RZ56 Ethernet Media) RX26 Model CDROM RZ24L 500, RZ58 500S (BUS) SCSI 256 TURBOchannel MB Max Mem PMAGB- BE PMTCE (1) Note: Factory-loaded software on all configurations that include internal_disks.____________________________________________________ 31 ___________________________________________________________________ Table_2:___________________________________________________________ Miscellaneous System Disks Tapes Communication ________________ _______________ (LAN) __________CTRL_____DRIVE_____CTRL___DRIVE__________________________ DEC 4000 Integral RRD42 IntegralTLZ06 Integral 512 Model RZ26 TSZ07 Ether- MB 610 SCSI RZ73 SCSI TZ85 net Max TZ857 Mem (Load RF35 TZ30 Media) Integral RF73 CDROM TF85 DSSI Integral (BUS) SCSI (5) DSSI DSSI (4) Note: Factory loaded software on all configurations that include internal disks. ___________________________________________________________________ 32 ___________________________________________________________________ Table_3:___________________________________________________________ Miscellaneous System Disks Tapes Communication ________________ _______________ (LAN) __________CTRL_____DRIVE_____CTRL___DRIVE__________________________ DEC 7000 KDM70 ESE52 KDM70 TA78 DEMFA 2 Model RA72 TA81 (1) GB 610 RA73 TA90 DEMNA Max RA90 (4) Mem (Load RA92 KZMSA TKZ60 Media) TSZ07 CDROM KZMSA RRD42 TLZ06 RZ26 (BUSSES) RZ73 SCSI RWZ01 XMI (4) Note: Maximum number of KDM70: 3 per XMI; 12 per system. Maximum number of KZMSA: 4 per XMI; 4 per system. One SCSI tape per SCSI bus with no other device allowed on that bus._______________________________________________________________ 33 ___________________________________________________________________ Table_4:___________________________________________________________ Miscellaneous System Disks Tapes Communication ________________ _______________ (LAN) __________CTRL_____DRIVE_____CTRL___DRIVE__________________________ DEC KDM70 ESE52 KDM70 TA78 DEMFA 2 10000 RA72 TA81 (1) GB Model RA73 TA90 DEMNA Max 610 RA90 (4) Mem RA92 KZMSA TLZ06 (Load TKZ60 Media) KZMSA RRD42 TSZ07 CDROM RZ26 RZ73 (BUSSES) RWZ01 SCSI XMI (4) Note: Maximum number of KDM70: 3 per XMI; 12 per system. Maximum number of KZMSA: 4 per XMI; 4 per system. One SCSI tape per SCSI bus with no other device allowed on that bus. ___________________________________________________________________ 34 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 To prevent input from overflowing a buffer, terminals use the ASCII control characters DC1 and DC3 for synchronization as defined by Dig- ital's DEC STD 111, Revision A. The following table lists the termi- nals that are supported by OpenVMS AXP: VT200- VT300- VT400-series 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. RA72 1 GB fixed disk SDI MSCP drive RA73 2 GB fixed disk SDI MSCP drive RA90 1.2 GB fixed disk SDI MSCP drive RA92 1.5 GB fixed disk SDI MSCP drive ESE52 120 MB solid state SDI MSCP disk RF35 800 MB fixed disk DSSI MSCP drive 35 RF73 2 GB fixed disk DSSI MSCP drive RRD42 600 MB read-only SCSI SCSI optical disk drive RWZ01 594 MB optical SCSI SCSI removable disk drive RX26 2.8 MB diskette SCSI SCSI drive RZ24L 245 MB fixed disk SCSI SCSI drive RZ25 425 MB fixed disk SCSI SCSI drive RZ26 1.05 GB fixed disk SCSI SCSI drive RZ55 332 MB fixed disk SCSI SCSI drive RZ56 665 MB fixed disk SCSI SCSI drive RZ58 1.35 GB fixed disk SCSI SCSI drive RZ73 2 GB fixed disk SCSI SCSI 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. TA78 1600/6250 BPI, STI TMSCP STI TU78. TA81 145 MB tape drive. STI TMSCP 36 TA90 1.2 GB tape car- STI TMSCP tridge subsystem. (5-inch 200 MB cartridge) TKZ60 200 MB, 3480 tape SCSI SCSI drive TLZ04 1.2 GB, 4mm, DAT SCSI SCSI tape drive TLZ06 4 GB, 4mm, DAT SCSI SCSI tape drive TSZ07 1600/6250 BPI SCSI SCSI tape drive (no compaction) TZ30 95 MB, 5-1/4-inch, SCSI SCSI half-height, tape drive TZ85 2.6 GB tape drive SCSI SCSI TZ857 18 GB tape loader SCSI SCSI TZK10 320/525 MB, QIC SCSI SCSI (Quarter Inch Cartridge), tape drive Controllers KDM70 The KDM70 is an intelligent MSCP/TMSCP mass-storage con- troller for XMI systems with eight ports that support RA Series Disks and Storage Arrays, TA Series Tape, and Solid State Disks. KZMSA The KZMSA in an intelligent mass-storage controller for XMI systems with two SCSI ports that support RZ Series Disks and Storage Arrays and TZ Series Tape. 37 Graphics Options PMAGB The PMAGB is a multi-screen graphics adapter for TUR- BOchannel systems to connect multiple 8-plane color or grayscale monitors. Network Options DEFZA The DEFZA is a high-performance network adapter that connects TURBOchannel systems to ANSI FDDI local area networks. DEMFA The DEMFA is a high-performance network adapter that connects XMI systems to ANSI FDDI local area networks. DEMNA The DEMNA is a high-performance network adapter that connects XMI systems to both the Ethernet and IEEE 802.3 local area networks. PMAD The PMAD is a network adapter that connects TURBOchannel systems to both the Ethernet and IEEE 802.3 local area networks. 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 38 XMI Extended Memory Interconnect (R) PostScript is a registered trademark of Adobe Systems, Inc. (R) Motif and OSF/Motif are registered trademarks of Open Software Foundation, Inc. [TM]X Window System is a common law trademark of MIT. [TM]The DIGITAL logo, Alpha AXP, AXP, Bookreader, DEC, DEC Fortran, DECmigrate, DECnet, DECthreads, DECwindows, Digital, DNA, EDT, KDM, MSCP, OpenVMS, RA, RRD42, RX, RZ, SDI, STI, TA, TK, TMSCP, TS, TURBOchannel, UETP, VAX, VMS, VT300, and XUI are trademarks of Digital Equipment Corporation. 39