Software Product Description ___________________________________________________________________ PRODUCT NAME: HP OpenVMS Version 8.3 for Alpha and Integrity Servers SPD 82.35.08 Note: The OpenVMS VAX information is included in the HP OpenVMS Operating System for Alpha Version 7.3-1 and 7.3-2, and VAX Version 7.3 Soft- ware Product Description (SPD 25.01.xx). This SPD describes the HP OpenVMS Operating System software for the AlphaServer and Integrity server computer families. Except where ex- plicitly noted, the features described in this SPD apply equally to AlphaServer and Integrity server systems. HP OpenVMS operating sys- tem licenses and part numbers for the two platforms are architecture specific. Please refer to the Ordering Information section of this SPD for further details. DESCRIPTION OpenVMS is a general-purpose, multiuser operating system that runs in both production and development environments. Starting with OpenVMS Version 8.2, HP introduced support for OpenVMS for Integrity servers. OpenVMS Version 8.3 continues support for all of the Integrity servers and options supported in HP OpenVMS Versions 8.2 and 8.2-1 for Integrity servers. OpenVMS Version 8.3 introduces support for additional Integrity server systems. For Alpha systems, OpenVMS Version 8.3 replaces Ver- sion 8.2; for Integrity servers, Version 8.3 replaces Version 8.2-1. Standard support for OpenVMS Version 8.2 on Integrity systems ends when OpenVMS V8.3 ships. OpenVMS Alpha Version 7.3-2 begins Prior Version Support (PVS) when OpenVMS V8.3 ships. OpenVMS Alpha supports Hewlett-Packard's AlphaServer series comput- ers. OpenVMS software supports industry standards, facilitating ap- plication portability and interoperability. OpenVMS provides symmet- ric multiprocessing (SMP) support for multiprocessing systems. July 2006 The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Ac- tual system performance depends on the type of computer, available phys- ical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, multiprocessing, and windowing capabilities. It contains extensive features that promote ease-of-use, improve the productivity of programmers, and facilitate system management. For information about the OpenVMS Version 8.3 new features, please re- fer to the HP OpenVMS Version 8.3 New Features and Release Notes at: http://h71000.www7.hp.com/openvms/ USER ENVIRONMENT Users can access the OpenVMS software by using the English-like DIG- ITAL Command Language (DCL), the command language for OpenVMS that is supplied with the system. DCL commands provide information about the system and initiate system utilities and user programs. DCL commands take the form of a command name followed by parameters and qualifiers. Users can enter DCL commands at a terminal or include them in command procedures. These command procedures can be run interactively or sub- mitted to a batch queue for later processing. Information about DCL and OpenVMS utilities is available on line through the OpenVMS Help system. For users who are familiar with the UNIX shell and utilities, an open source port of GNV is available. GNV implements a UNIX environment on OpenVMS and includes an Implementation of the UNIX shell BASH (Bourne Again Shell) and many UNIX-shell utilities. The following tools and utilities are integrated into the OpenVMS op- erating system. Text Processing 2 The Extensible Versatile Editor (EVE) is the default editor for Open- VMS. EVE allows users to insert, change, and delete text quickly. EVE is a full-screen editor that allows users to scroll through text on a terminal screen. EVE provides an EDT-style keypad, allowing EDT users to move easily to EVE. Mail Utility The Mail utility allows users to send messages to any other user on the system. Multinode operation is available if a DECnet or TCP/IP prod- uct is installed and licensed on each participating node on the net- work. Command-Level Programming Command-level programming allows users to create special files, called command procedures, that contain a series of DCL commands. When users execute a command procedure, the system processes the commands in the command procedure consecutively. User Environment Tailoring Users can customize the computing environment with login command pro- cedures, shorthand commands, binding of commands to function keys, and command recall and editing. PROGRAM DEVELOPMENT ENVIRONMENT OpenVMS includes a comprehensive set of tools for developing programs, including: run-time libraries (RTLs), a linker, a librarian, and a sym- bolic debugger. The following tools are available to the OpenVMS programmer. 3 Java[TM] SE Development Kit The Java Platform, Standard Edition Development Kit (JDK) provides a development and deployment environment for Java applications on Open- VMS Alpha and OpenVMS for Integrity servers, including a set of ba- sic development tools and a rich set of class libraries. Language and Run-Time Library Support OpenVMS includes several RTLs that provide: o String manipulation o Parallel processing support o I/O routines o I/O conversion o Terminal-independent screen handling o Date and time formatting routines o Highly accurate mathematical functions o Signaling and condition handling o Other general-purpose functions With OpenVMS Alpha, these routines can be called from programs writ- ten in such languages as MACRO-32, MACRO-64, Ada, BASIC, C, C++, COBOL, Fortran, Pascal, and PL/I. With OpenVMS for Integrity servers, these routines can be called from programs written in such languages as MACRO-32, BASIC, C, C++, COBOL, Fortran, and Pascal. Also included in OpenVMS are language-support libraries. While each language is different, all provide support for sequential file I/O, and most support direct and indexed file I/O. Language RTLs also pro- vide support for I/O formatting, error handling, and in Fortran, the ability to read unformatted files that contain data from other ven- dors. 4 RTLs are provided to support translated images created from user-mode images built on OpenVMS Alpha Version 6.1 through Version 7.3-2. Calling Standard Many HP languages adhere to the common calling standard. This means that routines written in any of these languages can directly call rou- tines written in any other language. Development of applications us- ing multiple languages is simple and straightforward. All user-accessible routines in the RTLs follow the appropriate plat- form calling standard and condition-handling conventions, and most are contained within shareable images. At a lower level, programs can call system services directly for se- curity, event flag, asynchronous system trap, logical name, record and file I/O, process control, timer, time conversion, condition handling, lock management, and memory management. Again, system services use the appropriate platform calling standard and condition-handling conven- tions. OpenVMS supports the execution of user-mode images created on earlier versions of OpenVMS. Typically, recompiling and relinking are not re- quired. MACRO Compiler With minor modifications, VAX MACRO-32 sources can be compiled for ex- ecution on Alpha or Integrity servers. POSIX Threads Library OpenVMS includes a user-mode, multithreading capability called POSIX Threads Library. POSIX Threads Library provides a POSIX 1003.1-1996 standard style threads interface. Additionally, POSIX Threads Library provides an interface that is the OpenVMS implementation of Distributed Computing Environment (DCE) threads as defined by The Open Group. 5 POSIX Threads Library is a library of run-time routines that allows the user to create multiple threads of execution within a single ad- dress space. With POSIX Threads Library Kernel Threads features en- abled, POSIX Threads Library provides for concurrent processing across all CPUs by allowing a multithreaded application to have a thread ex- ecuting on every CPU (on both symmetric and asymmetric multiproces- sor systems). Multithreading allows computation activity to overlap I/O activity. Synchronization elements, such as mutexes and condition variables, are provided to help ensure that shared resources are ac- cessed correctly. For scheduling and prioritizing threads, POSIX Threads Library provides multiple scheduling policies. For debugging multi- threaded applications, POSIX Threads Library is supported by the Open- VMS Debugger. POSIX Threads Library also provides Thread Independent Services (TIS), which assist in the development of thread-safe APIs. Librarian Utility The Librarian utility permits storage of object modules, image files, macros, help files, text files, or any general record-oriented infor- mation in central, easily accessible files. Object module and image file libraries are searched by the linker when the linker finds a ref- erence it cannot resolve in one of its input files. Macro libraries are searched by MACRO-32 and MACRO-64 when either finds a macro name that is not defined in the input file. 6 Hypersort Hypersort is a portable library of user-callable routines that pro- vide a high-performance sorting capability for Alpha and Integrity servers. Traceback Facility When an application is compiled and linked with traceback information, the Traceback facility translates stack frame addresses into routine names and line numbers and displays a symbolic traceback whenever a runtime error occurs in that application. Debugger The OpenVMS Debugger allows users to trace program execution, as well as display and modify register contents using the same symbols that are present in the source code. The debugger contains a heap analyzer feature that displays a graphic view of memory allocations and deallocations in real time. System Code Debugger The OpenVMS System Code Debugger is a kernel code debugger. It allows a system code developer to trace the execution of nonpageable system code at any interrupt priority level (IPL). Based on the OpenVMS De- bugger, the System Code Debugger uses the same interface and most of the same command set. System Dump Analyzer (SDA) Utility In the event of a system failure, OpenVMS writes the contents of mem- ory to a preallocated dump file. This dump file can later be analyzed using System Dump Analyzer (SDA). System dumps can either be full mem- ory dumps, where all memory is written, or selective memory dumps, where only portions of memory in use at the time of the system failure is written. The dump file can be located on any locally connected disk. On Alpha and Integrity servers, dump compression allows both full and selective dumps to be written to smaller files than required for un- compressed dumps. Full memory dumps, if not compressed, require a dump file big enough to hold all memory. Selective memory dumps write as 7 much of the memory in use at the time of the system failure that will fit into the dump file. Spinlock Tracing Utility The Spinlock Tracing Utility provides a mechanism for characterizing spinlock usage and can collect performance data for a given spinlock on a per-CPU basis. 8 Process Dumps When an application fails, a copy of its registers and memory can be written to a data file, which can be examined using the ANALYZE PRO- CESS utility. This utility uses the same interface and commands as the OpenVMS Debugger to allow registers and memory to be examined. On Al- pha or Integrity servers, another process can initiate the writing of the memory dump. RMS File Utilities Record Management Services (RMS) file utilities allow users to ana- lyze the internal structure of an RMS file and tune the I/O, memory, space and performance parameters of the file. The RMS file utilities can also be used to create, load, and reclaim space in an RMS file. Refer to the Operating System Environment section of this SPD for more information about RMS. File Differences Utility This utility compares the contents of two files and lists those records that do not match. Translated Image Environment (TIE) (Alpha) OpenVMS Alpha provides an array of services that allow the operation of programs which have undergone binary translation from OpenVMS VAX images. These programs perform virtually all user-mode functions on OpenVMS Alpha and operate in combination with other programs (images) that have been translated from OpenVMS VAX or have been built using native compilers on OpenVMS Alpha. Without requiring special source code, the TIE resolves differences between the VAX and Alpha archi- tectures, including floating-point registers, condition codes, excep- tion handling, and ASTs. The TIE included with OpenVMS Alpha can run images that have been translated elsewhere. For additional information, refer to the following web site: http://h71000.www7.hp.com/commercial/cace.html (under the Tools section) Translated Image Environment (TIE) (Integrity servers) 9 OpenVMS for Integrity servers provides an array of services that al- low the operation of programs which have undergone binary translation from OpenVMS Alpha images or VESTed OpenVMS VAX images. These programs perform virtually all user-mode functions on OpenVMS for Integrity servers and operate in combination with other programs (images) that have been translated from OpenVMS Alpha or VAX, or have been built using native compilers on OpenVMS for Integrity servers. Without requiring special source code, the TIE resolves differences between the Alpha and In- tegrity architectures, including floating-point. For additional information, refer to the following web site: http://h71000.www7.hp.com/commercial/cace.html (under the Tools section) SYSTEM MANAGEMENT ENVIRONMENT OpenVMS provides a set of tools and utilities that aid the system man- ager in configuring and maintaining an optimal system as follows: Web-Based Enterprise Management (WBEM) Services for OpenVMS WBEM is an industry standard for monitoring and controlling resources. It is available as an optional product on OpenVMS for Integrity server systems. This product is required for use of Instant Capacity (iCAP) and Pay Per Use (PPU) supported on cell-based Integrity servers. HP Availability Manager HP Availability Manager is a system management tool that enables you to monitor one or more OpenVMS nodes on an extended local area net- work (LAN) from either an OpenVMS Alpha system, or an OpenVMS for In- tegrity server system, or a PC running Windows[R]. This tool helps sys- tem managers and analysts target a specific node or process for de- tailed analysis and also can resolve certain performance or resource problems. It is the multiplatform replacement for the DECamds prod- uct, and includes the DECamds functionality in its capabilities. The Data Collector, part of the Availability Manager product, collects system and process data on an OpenVMS node and should be installed on each node that you need to monitor (Alpha and Integrity servers). 10 The Data Analyzer analyzes and displays the data collected by the Data Collector, and can analyze and display data from many OpenVMS nodes simultaneously (OpenVMS Alpha nodes, and PCs running Windows. Hardware recommendations and related documentation are available via the OpenVMS System Management web page located at: http://www.hp.com/products/openvms/availabilitymanager/ DECamds DECamds is in maintenance mode and is not available on OpenVMS Ver- sion 8.2 or higher. Availability Manager replaces DECamds. DECamds in- stalls and runs on VAX from V6.2 through V7.3 and Alpha from V6.2 through V7.3-2. DECamds is not supported on OpenVMS for Integrity servers and will not install on OpenVMS Alpha Version 8.2 or higher. Management Agents for OpenVMS HP Systems Insight Manager (HP SIM) is the foundation for HP's uni- fied infrastructure management strategy. It provides hardware level management for all HP storage products and servers, including Open- VMS Alpha and OpenVMS for Integrity servers. With Management Agents installed on an OpenVMS system, that system can be managed using HP SIM as the single management console providing fault monitoring, con- figuration management, and event alarms. The Management Agents for Open- VMS and related documentation is available on the OpenVMS System Man- agement web page located at: http://www.hp.com/products/openvms/managementagents/ HP OpenVMS Management Station HP OpenVMS Management Station (OMS) is a powerful Microsoft[R] Win- dows based management tool for system managers and others who perform system management tasks on OpenVMS systems. OMS features an intuitive user interface that is meaningful to system managers and their envi- ronment by allowing them to manage user accounts, printers, and stor- age on their systems. System managers and help desk staff no longer 11 need to remember complicated DCL syntax or command procedures to man- age their OpenVMS Alpha and Integrity server systems. OMS is based on the Microsoft Management Console (MMC). The Microsoft Management Con- sole provides a common management framework for various administra- tion programs. OpenVMS Management Station is implemented as an MMC snap- in and includes all of the MMC components you need. OpenVMS Manage- ment Station and related documentation is available via the OpenVMS System Management web page located at: http://www.hp.com/products/openvms/managementstation/ Enterprise Capacity and Performance Analyzer Enterprise Capacity and Performance (ECP) Analyzer works with the data that is collected by a Data Collector (ECP Data Collector for VAX and Performance Data Collector (TDC) Version 2.1 or later for Alpha and Integrity servers). ECP Analyzer provides both graphical (MOTIF-based) and tabular reports for the data assembled by the collector includ- ing metrics for CPU, disk I/O, memory, paging, processes, locks, and SCS. The ECP Analyzer, which runs on Alpha, will process data from: o ECP Data Collector (VAX) o TDC (Alpha and Integrity servers) The Performance Analyzer and related documentation is available on the OpenVMS System Management web page located at: http://www.hp.com/products/openvms/ecp/ Performance Data Collector Performance data for an AlphaServer or Integrity server system can be gathered using the Performance Data Collector (TDC). By default, TDC periodically collects and stores data in a file that can be retrieved by user applications. A TDC Software Developers Kit (SDK) supports in- tegration of TDC with new or existing applications and allows process- ing of "live" data as well as data read from files. TDC Version 2.2 runtime software is installed with OpenVMS Version 8.3. 12 Performance Data Collector runtime software (TDC_RT Version 2.2) is installed with OpenVMS Version 8.3. Additional Performance Data Collector software and updates, the SDK, and related documentation are available at: http://www.hp.com/products/openvms/tdc/ Graphical Configuration Manager for OpenVMS The Graphical Configuration Manager (GCM) for OpenVMS is a portable client/server application that provides a visual means of viewing and controlling the configuration of partitioned AlphaServer systems run- ning OpenVMS. The GCM client, a Java-based application, can run on any operating system that supports a TCP/IP network and the Java runtime environment- Software Development Kit (SDK), v1.2.2 or higher, for the Java Platform. (Currently, the GCM client is not supported on SDK Ver- sion 1.3 or higher.) A GCM server runs as a detached process on each partitioned OpenVMS instance on one or more AlphaServer systems. Class Scheduler for CPU Scheduling The Class Scheduler is a SYSMAN-based interface for defining and con- trolling scheduling classes for OpenVMS systems that allows you to des- ignate the percentage of CPU time that a system's user may receive by placing users into scheduling classes. Batch and Print Queuing System OpenVMS provides an extensive batch and print capability that allows the creation of queues and the setup of spooled devices to process non- interactive workloads in parallel with timesharing or real-time jobs. The OpenVMS batch and print operations support two types of queues: generic queues and execution queues. A generic queue is an interme- diate queue that holds a job until an appropriate execution queue be- comes available to initiate the job. An execution queue is a queue through which the job (either print or batch) is actually processed. Because multiple execution queues can be associated with a generic queue, Open- VMS enables load balancing across available systems in an OpenVMS Clus- ter system, increasing overall system throughput. 13 Print queues, both generic and execution, together with queue manage- ment facilities, provide versatile print capabilities, including sup- port for various print file formats. Accounting Utility For accounting purposes, OpenVMS keeps records of system resource us- age. These statistics include processor and memory utilization, I/O counts, print symbiont line counts, image activation counts, and pro- cess termination records. The OpenVMS Accounting utility allows you to generate various reports using this data. Audit Analysis Utility For security auditing purposes, OpenVMS selectively records critical, security-relevant events in the system security audit log file. These records contain the date and time the event occurred, the identity of the associated user process, and information specific to each event type. This information helps the system manager maintain system se- curity and deter possible intruders. The OpenVMS Audit Analysis util- ity allows you to generate various reports from this data. Autoconfigure and AUTOGEN Utilities The Autoconfigure and AUTOGEN utilities automatically configure the available devices in the system tables and set system parameters based on the peripheral and memory architecture. This eliminates the need for a traditional system generation process when the hardware config- uration is expanded or otherwise modified. The OpenVMS AUTOGEN command procedure sets several system parameters automatically by detecting the devices installed in a configuration. A feedback option allows you to generate a report of recommended pa- rameter settings based on previous usage patterns. Backup Utility 14 The Backup utility provides both full-volume and incremental file back- ups for file-structured, mounted volumes and volume sets. Individual files, selected directory structures, or all files on a volume set can be backed up and restored. Files can be selected by various dates (such as creation or modification) and can be backed up to magnetic tape, magnetic disk, or Write Once Read Many (WORM) optical disk. The Backup utility can also be used to restore a saveset or list the contents of a saveset. A Backup API is included for invoking backup routines from an executable procedure. The Backup Manager for OpenVMS provides a screen-oriented interface to the Backup utility that assists users in performing routine backup operations. The Backup Manager is menu driven and provides: o Access to the save, restore, and list operations without having to understand Backup command syntax o The ability to create, modify, recall, and delete Backup Manager templates that describe the Backup save operations Recordable DVD OpenVMS provides the capability on Alpha and Integrity server systems to record locally mastered disk volumes or disk image files onto a CD- R, CD-RW, DVD+R or DVD+RW optical-media recording device on specific drives and configurations. Recordable CD OpenVMS provides the capability to write once to CD-R media using an application shipping in the base operating system. The feature sup- ports only those writable CD devices (CD-RW) that ship with supported Alpha systems and supported Integrity servers. For the application de- tails, please reference the OpenVMS documentation set. For platforms supporting the CD-RW hardware option, please refer to the appropri- ate page at the following web sites: http://h18002.www1.hp.com/alphaserver/ http://www.hp.com/products1/servers/integrity/index.html 15 Analyze Disk Structure Utility The Analyze Disk Structure utility compares the structure information on a disk volume with the contents of the disk, prints the structure information, and permits changes to that information. It can also be used to repair errors detected in the file structure of disks. License Management Facility (LMF) The License Management Facility allows the system manager to enable software licenses and to determine which software products are licensed on an OpenVMS system. System Management Utility (SYSMAN) The System Management utility allows system managers to define a man- agement environment in which operations performed from the local Open- VMS system can be executed on all other OpenVMS systems in the envi- ronment. HP Services Tools HP Services provides web-based tools for crash dump analysis and hard- ware fault isolation. For more information, visit the following web site: http://h18000.www1.hp.com/support/svctools/ SECURITY OpenVMS provides a rich set of tools to control user access to system- controlled data structures and devices that store information. Open- VMS employs a reference monitor concept that mediates all access at- tempts between subjects (such as user processes) and security-relevant system objects (such as files). OpenVMS also provides a system secu- rity audit log file that records the results of all object access at- tempts. The audit log can also be used to capture information regard- ing a wide variety of other security-relevant events. 16 User account information, privileges and quotas associated with each user account is maintained in the system user authorization file (SYSUAF). Each user account is assiged a user name, password, and unique user identification code (UIC). To log in and gain access to the system, the user must supply a valid user name and password. The password is encoded and does not appear on terminal displays. Users can change their password voluntarily, or the system manager can specify how frequently passwords change, along with minimum password length, and the use of randomly generated passwords. Operations OpenVMS allows for varying levels of privilege to be assigned to dif- ferent operators. Operators can use the OpenVMS Help Message utility to receive online descriptions of error messages. In addition, system- generated messages can be routed to different terminals based on their interest to the console operators, tape librarians, security admin- istrators, and system managers. Security auditing is provided for the selective recording of security- related events. This auditing information can be directed to security operator terminals (alarms) or to the system security audit log file (audits). Each audit record contains the date and time of the event, the identity of the associated user process, and additional informa- tion specific to each event. OpenVMS provides security auditing for the following events: o Login and logout o Login failures and break-in attempts o Object creation, access, deaccess, and deletion; selectable by use of privilege, type of access, and on individual objects o Authorization database changes o Network logical link connections for DECnet for OpenVMS, DECnet- Plus, DECwindows, IPC, and SYSMAN o Use of identifiers or privileges 17 o Installed image additions, deletions, and replacements o Volume mounts and dismounts o Use of the Network Control Program (NCP) utility o Use or failed use of individual privileges o Use of individual process control system services o System parameter changes o System time changes and recalibrations Every security-relevant system object is labeled with the UIC of its owner along with a simple protection mask. The owner UIC consists of two fields: the user field and a group field. System objects also have a protection mask that allows read, write, execute, and delete access to the object's owner, group, privileged system users, and to all other users. The system manager can protect system objects with access con- trol lists (ACLs) that allow access to be granted or denied to a list of individual users, groups, or identifiers. ACLs can also be used to audit access attempts to critical system objects. OpenVMS applies full protection to the following system objects: o Common event flag clusters o Devices o Files o Group global sections o Logical name tables o Batch/print queues o Resource domains o Security classes o System global sections o ODS-2 volumes 18 o ODS-5 volumes OpenVMS provides optional security solutions to protect your infor- mation and communications: o OpenVMS Version 8.3 introduces encryption for data confidential- ity that ships as part of the operating system, thereby removing the requirement to license and install Encrypt separately. The EN- CRYPT and DECRYPT commands, now part of OpenVMS, support AES file encryption with 128, 192, or 256 bit keys. AES encryption is also supported by BACKUP/ENCRYPT, allowing for the creation of encrypted tapes and save-sets. The built-in encryption functionality is backward- compatible with file and backup tapes created by the former lay- ered product Encryption for OpenVMS. This layered product featured 56-bit Data Encryption Standard (DES), which continues to function today, allowing for the decryption of archived DES encrypted data. The AES encryption functionality supports Electronic Code Book (ECB) and Cipher Block Chaining (CBC) block modes of encryption. The Ci- pher Feedback (CFB) and Output Feedback (OFB) 8-bit character stream modes are also supported from the command line as well as by the programmatic APIs. o Secure Sockets Layer (SSL) for OpenVMS Alpha and Integrity server systems provides secure transfer of sensitive information over the Internet o Common Data Security Architecture (CDSA) is configured and initial- ized automatically during installation and upgrades and is required for Secure Delivery purposes and other security features. If you install a newer version of CDSA without upgrading the base oper- ating system, you must initalize the CDSA software, using the fol- lowing command. Enter the command from an account that has both SYSPRV and CMKRNL privileges (for example, the SYSTEM account). $ @SYS$STARTUP:CDSA$UPGRADE o Kerberos for OpenVMS o Per-Thread Security Profiles o External Authentication 19 Note: Users who are externally authenticated by their LAN Manager need only remember a single user name/password combination to gain access to their OpenVMS and LAN Manager accounts. Government Security Ratings OpenVMS is committed to consistently delivering a secure base oper- ating system, and has been evaluated and certified to be compliant with the DoD 5200.28-STD Department of Defense Trusted Computer System Eval- uation Criteria. Each release of OpenVMS sucessfully completes the same test suite used to prove C2 compliance to the National Computer Se- curity Center before it is released. Note: Because no system can provide complete security, HP cannot guar- antee complete system security. However, HP continues to enhance the security capabilities of its products. Customers are strongly advised to follow all industry-recognized security practices. OpenVMS recom- mended procedures are included in the HP OpenVMS Guide to System Se- curity. Utility Pricing on OpenVMS for Integrity servers With OpenVMS Version 8.3, Utility Pricing is introduced on OpenVMS for Integrity servers. It enables customers to pay for CPU resources when they need them, responding to planned or unplanned permanent load in- creases and temporary spikes. o Instant Capacity or iCAP is relevant for systems that are purchased through capital expenditure o Pay Per Use or PPU is valid only for systems that are leased - ex- clusively through HP Finance Instant Capacity (iCAP) Instant Capacity provides reserve capacity that the customer can put into production quickly without disrupting operations. Key features: 20 o Runs on all OpenVMS Integrity cell-based systems (rx7620, rx7640, rx8620, rx8640, and Superdome) o Provides a highly available pre-configured "ready-to-run" solution o Ability to activate reserve capacity when needed o Encompasses Cell Boards and individual CPUs o Defer/avoid purchase until used o Full corporate implementation ensures OpenVMS can share iCAP CPUs across hard partitions with HP-UX on a common Integrity system o Integrated with Global Workload Manager (gWLM) that can automat- ically re-allocate active CPUs within hard partitions in response to workload demands Operational features: o iCAP CPUs are purchased at a fraction of the price of active CPUs and are denoted as Components Without Usage Rights (CWUR) o Systems are configured in the factory before delivery with a min- imum of one active CPU and the required number of iCAP CPUs o Once iCAP CPUs are required to be activated, the balance of the price is paid and an activation Rights To Use (RTU) 'codeword' is obtained from the HP iCAP Web Portal. The iCAP CPU/memory is then made ac- tive o When a CPU or Cell board is permanently activated, support of the CPU/Cell board is automatically added to the overall support costs of the system Note: Regard iCAP activation as permanently adding a new CPU with all the attendant HP and 3rd Party software licensing and support that this requires. TiCAP (Temporary iCAP) o Enables the customer to temporarily activate a processor(s) for a set period of time, with a minimum 30 minute granularity per CPU 21 o No permanent activation fee is required - utilize an existing CPU for as long as needed o Accommodates those customers with unpredictable or planned tempo- rary processor demands Operational features: o Works with processors, does not include Cell boards or memory o Customer orders standard iCAP processors and pays the same discounted price o Customer then purchases one or more 30-CPU day right to temporar- ily activate one or more iCAP CPUs o Does not require an email connection from customer site to HP o The iCAP software issues a warning before the TiCAP license is likely to expire, based on the rate of depletion that it tracks across all relevant CPUs o Hardware Services are included for the CPUs activated by the TiCAP license o The relevant Operating Environment (OE) is automatically licensed on activated TiCAP CPUs Note: Other HP and 3rd Party software have their own licensing poli- cies and it is recommended that customers purchase sufficient soft- ware licenses to meet peak needs. Pay Per Use (PPU) PPU is a leasing program with HP Finance which customers pay only for CPU computing capacity they use. Key features: o Runs on all OpenVMS Integrity cell-based systems (rx7620, rx7640, rx8620, rx8640, and Superdome) o The customer pays a fixed minimum monthly lease and a variable monthly amount which is based on actual usage of CPUs 22 o The customer is guaranteed that for any given month the PPU charge will not exceed 105% of the standard lease cost o The customer is guaranteed that over the full term of the lease - either three or four years as initially chosen by the customer - the total PPU lease charge will not exceed 100% of the standard full term lease cost system o There are two types of PPU: o Actual percentage of utilization of each CPU, aka Percent CPU o A count of the number of active CPUs, aka Active CPU o Percent CPU and Active CPU are mutually exclusive on any single In- tegrity system o The full corporate implementation has been executed allowing Open- VMS to share PPU CPUs with HP-UX and Windows-64 (Percent CPU only) on a common partitioned Integrity system Operational features: o A PPU Metering Agent running on a target system continuously mea- sures CPU resource utilization on every installed CPU o This utilization data is sent to a Utility Meter running on an HP Proliant system that can support up to 99 individual PPU systems o This system securely communicates with the HP Utility Web Portal every 24 hours, sending collated utilization information on each PPU system o 48 hours later the customer may access the Utility Portal through a secure connection and access usage statistics for that 24 hour period for each system and/or hard partition o This information enables the accurate billing of Business Units for the actual CPU resources they have consumed 23 OPERATING SYSTEM ENVIRONMENT Processes and Scheduling Executable images consist of system programs and user programs that have been compiled and linked. These images run in the context of a process on OpenVMS systems. Sixty-four process priorities are recog- nized on OpenVMS Alpha and OpenVMS for Integrity servers. Priorities 0 to 15 are for time-sharing processes and applications (four is the typical default for timesharing processes). Priorities 16 to 63 on Al- pha and Integrity servers are for real-time processes. Real-time pro- cesses can be assigned higher priorities to ensure that they receive processor time whenever they are ready to execute. OpenVMS uses paging and swapping to provide sufficient virtual mem- ory for concurrently executing processes. Paging and swapping is also provided for processes whose memory requirements exceed available phys- ical memory. 64-Bit Virtual Addressing The OpenVMS Alpha and OpenVMS for Integrity servers operating systems provide support for 64-bit virtual memory addressing. This capabil- ity makes the 8 TB virtual address space available to the OpenVMS Al- pha and OpenVMS for Integrity servers operating systems and to appli- cation programs. Future hardware implementations for Integrity servers will provide greater capacity. OpenVMS applications can take advan- tage of 64-bit processing by using 64-bit data types supported by the compilers. Refer to the SPDs for the OpenVMS Alpha and OpenVMS for In- tegrity servers compilers for further details. Very Large Memory (VLM) Features OpenVMS Alpha and OpenVMS for Integrity servers provide the follow- ing additional memory management VLM features beyond those provided by 64-bit virtual addressing. These features can be used by database servers to keep large amounts of data in memory, resulting in dramat- ically increased runtime performance. The VLM features provided by Open- VMS Alpha and OpenVMS for Integrity servers are: 24 o Memory-resident global sections o Fast I/O for global sections o Shared page tables o Expandable global page table o Reserved memory registry DECdtm Services The DECdtm services embedded in the OpenVMS operating system support fully distributed databases using a two-phase commit protocol. The DECdtm services provide the technology and features for distributed process- ing, ensuring both transaction and database integrity across multi- ple HP resource managers. Updates to distributed databases occur as a single all-or-nothing unit of work, regardless of where the data phys- ically resides. This ensures the consistency of distributed data. DECdtm services allow applications to define global transactions that can include calls to any number of HP data management products. Re- gardless of the mix of data management products used, the global trans- action either commits or aborts. OpenVMS is unique in providing trans- action processing functionality with base operating system services. DECdtm features include: o Embedded OpenVMS system services that support the DECtp architec- ture, providing the features and technology for distributed trans- action processing. o Ability for multiple disjoint resources to be updated automatically. These resources can be either physically disjointed on different clusters at separate sites, or logically disjointed in different databases on the same node. o Ability to use the X/Open Distributed Transaction Processing XA in- terface that enables the DECdtm transaction manager to coordinate XA-compliant resource managers (the HP DECdtm XA Veneer), and XA- compliant transaction processing systems to coordinate DECdtm-compliant resource managers (the DECdtm XA Gateway). 25 o Robust application development. Applications can be written to en- sure that data is never in an inconsistent state, even in the event of system failures. o Ability to be called using any HP TP monitor or database product. This is useful for applications using several HP database products. Interprocess Communication OpenVMS provides the following facilities for applications that con- sist of multiple cooperating processes: o Mailboxes as virtual devices that allow processes to communicate with queued messages. o Shared memory sections on a single processor or an SMP system that permit multiple processes to access shared address space concur- rently. o Galaxywide sections on a Galaxy platform that permit multiple pro- cesses in multiple instances to access shared address space con- currently. o Common event flags that provide simple synchronization. o A lock manager that provides a more comprehensive enqueue/dequeue facility with multilevel locks, values, and asynchronous system traps (ASTs). o Intracluster communication services through which two processes run- ning on the same system or on different OpenVMS Cluster nodes can establish a connection and exchange data. o Logical names through which one process can pass information to other processes running on the same system or on different OpenVMS Clus- ter nodes. o Network interprocess communication is available via TCP/IP Services and DECnet-Plus (product licenses are required). Symmetric Multiprocessing (SMP) 26 OpenVMS provides symmetric multiprocessing (SMP) support for Alpha and Integrity servers multiprocessor systems. SMP is a form of tightly cou- pled multiprocessing in which all processors perform operations si- multaneously. All processors perform operations in all OpenVMS access modes, user, supervisor, executive, and kernel. OpenVMS SMP configurations consist of multiple CPUs executing code from a single shared memory address space. Users and processes share a sin- gle copy of OpenVMS for Integrity servers or OpenVMS Alpha address space. SMP also provides simultaneous shared access to common data in global sections to all processors. OpenVMS SMP selects the CPU where a pro- cess will run based on its priority and in special cases as directed by the application. OpenVMS uses a specialized scheduling algorithm when running a nonuniform memory access (NUMA) platform. SMP support is an integral part of OpenVMS and is provided to the user transparently. Because an SMP system is a single system entity, it is configured into a network and OpenVMS Cluster configurations as a sin- gle node. The maximum number of supported CPUs in an SMP configuration is 32. Networking Facilities OpenVMS provides device drivers for all HP local area network (LAN) adapters listed in the LAN Options section of Appendix A of this SPD. Application programmers can use the QIO system service to communicate with other systems connected via the LAN using either Ethernet or Institute of Electrical and Electronics Engineers (IEEE) 802.3 packet format. Simultaneous use of HP Ethernet and the IEEE 802.3 protocols are supported on any HP LAN adapter. OpenVMS Alpha supports Ethernet, FDDI, Token Ring, and ATM for local area networks (LANs). OpenVMS for Integrity servers supports Ether- net only. OpenVMS Alpha supports the standards defined by the ATM Forum's LANE Version 1.0 specifications for LAN emulation over an ATM network. By implementing an emulated LAN over an ATM network, you enable a group of ATM stations to act like a traditional LAN. LAN emulated over an 27 ATM network allows you to run your existing applications basically un- changed, while the computers on which your applications are running are connected to the ATM network. OpenVMS supports the following networking products: o HP TCP/IP Services for OpenVMS, the industry-standard set of pro- tocols for interoperating between different operating systems o HP DECnet-Plus, the Digital Network Architecture, Phase V o DECnet, the DIGITAL Network Architecture, Phase IV These networking products are described in this SPD under Associated Products. Terminal Server Products HP terminal server products provide terminal server access to Open- VMS. When used in an OpenVMS Cluster environment, terminal servers dis- tribute users across the available Alpha and Integrity server systems at login time. OpenVMS can also establish a connection to other devices (such as print- ers) attached to such terminal servers. Universal Serial Bus Support OpenVMS supports the Universal Serial Bus (USB) technology on the Al- phaServer ES47, ES80, and GS1280 systems, and the rx1600, rx2600, and rx4640 Integrity Server systems. Support for the USB interconnect en- ables OpenVMS systems to connect to multiple supported USB devices us- ing a single USB cable. OpenVMS supports the fully qualified USB de- vices listed in the appropriate AlphaServer platform configuration and options web site: http://h18002.www1.hp.com/alphaserver/ Reliability 28 OpenVMS handles hardware errors as transparently as possible while main- taining data integrity and providing sufficient information to diag- nose errors. The system limits the effects of an error by first de- termining if the error is fatal. If the error occurs in system con- text, the current OpenVMS system shuts down. If the error is not fa- tal, the system recovers actions pertinent to the error and contin- ues the current operation. In all cases, information relevant to the error is written to the er- ror log file for later analysis. Hardware errors include the follow- ing categories: o Processor errors. These include processor soft errors, processor hard errors, processor machine checks, and adapter errors. o Memory errors. These can be unrecoverable (hard) errors or recov- erable (soft) errors. The system examines memory at startup time and does not use any bad pages. During system operation, the sys- tem corrects all single-bit memory errors for those systems with error correction code (ECC) memory. o Correctible memory errors. A primary cause of these correctible mem- ory errors is alpha particle radiation. On some processors, when correctible memory errors occur, the memory controller corrects only the data returned to the CPU or I/O controller. The actual data in memory is left with the error intact. Subsequent read operations cause correction cycles to occur and, in most cases, an interrupt to report the error. On many of these processors, OpenVMS monitors the occurrence of correctible memory errors and, in almost all cases, is able to remove the error condition by rewriting the data in mem- ory. Rewriting the data causes the data to be corrected in that mem- ory location. Other failures include: o Operating system errors (system-detected inconsistencies or archi- tectural errors in system context) o User errors 29 o I/O errors The system logs all processor errors, all operating system errors de- tected through internal consistency checks, all double-bit memory er- rors (and a summary of corrected single-bit memory errors), and most I/O errors. If the system is shut down because of an unrecoverable hardware or soft- ware error, a dump of physical memory is written. The dump includes the contents of the processor registers. The OpenVMS System Dump An- alyzer (SDA) utility is provided for analyzing memory dumps. Input/Output The QIO system service and other related I/O services provide a di- rect interface to the operating system's I/O routines. These services are available from within most OpenVMS programming languages and can be used to perform low-level I/O operations efficiently with a min- imal amount of system overhead for time-critical applications. Device drivers execute I/O instructions to transfer data to and from a device and to communicate directly with an I/O device. Each type of I/O device requires its own driver. HP supplies drivers for all de- vices supported by the OpenVMS operating system and provides QIO sys- tem service routines to access the special features available in many of these devices. OpenVMS supports a variety of disk and tape peripheral devices, as well as terminals, networks, and mailboxes (virtual devices for interpro- cess communication), and more general I/O devices. I/O Performance Features Fast I/O provides a suite of additional system services that appli- cations can use to improve I/O throughput. The fast I/O services min- imize the CPU resources required to perform I/O. 30 Fast Path provides a streamlined mainline code path through the I/O subsystem to improve both uniprocessor and multiprocessor I/O perfor- mance. On multiprocessor systems, Fast Path allows all CPU process- ing for specific I/O adapters to be handled by a specific CPU. This can significantly lower the demands on the primary CPU and increase the I/O throughput on multiprocessor systems with multiple I/O ports. No user application changes are needed to take advantage of Fast Path. Fast Path can be utilized by the $QIO system service or the Fast I/O services. Extended File Cache (XFC) The Extended File Cache (XFC) is a virtual block data cache provided with OpenVMS Alpha and OpenVMS for Integrity servers. Similar to the Virtual I/O Cache, the XFC is a clusterwide, file system data cache. Both file system data caches are compatible and coexist in the Open- VMS Cluster. The XFC improves I/O performance with the following features that are not available with the virtual I/O cache: o Read-ahead caching o Automatic resizing of the cache o Larger maximum cache size o No limit on the number of closed files that can be cached o Control over the maximum size of I/O that can be cached o Control over whether cache memory is static or dynamic Virtual I/O Cache (Alpha only) OpenVMS Alpha provides a standalone or clusterwide, file-oriented disk cache. Applications benefit from the advantages of the virtual I/O cache without any special coding. The virtual I/O file-caching algorithm is chosen based on the type of clusterwide access currently in progress. Virtual I/O caching reduces current and potential I/O bottlenecks within OpenVMS systems. It reduces the number of I/Os to the disk subsystem, thereby reducing systemwide bottlenecks. 31 Record Management Services (RMS) RMS is a set of I/O services that helps application programs to pro- cess and manage files and records. Although it is intended to provide a comprehensive software interface to mass storage devices, RMS also supports device-independent access to unit-record devices. RMS supports sequential, relative, and indexed file organizations in fixed-length or variable-length record formats. RMS also supports byte stream formats for sequential file organization. RMS record access modes provide access to records in four ways: o Sequentially o Directly by key value o Directly by relative record number o Directly by record file address RMS also supports block I/O operations for various performance-critical applications that require user-defined file organizations and record formats. RMS promotes safe and efficient file sharing by providing multiple file access modes and automatic record locking (where applicable). RMS of- fers the options of enabling global buffers for buffer sharing by mul- tiple processes. RMS utilities aid file creation and record maintenance. These util- ities convert files from one organization and format to another; re- structure indexed files for storage and access efficiency; and reclaim data structures within indexed files. These utilities also generate appropriate reports. For systems that have DECnet or DECnet-Plus installed, RMS provides a subset of file and record management services to remote network nodes. Remote file operations are generally transparent to user programs. Commands such as EDIT, CREATE, COPY, TYPE, and PRINT allow users to manipulate RMS records within RMS files at the DCL command level. 32 Disk and Tape Volumes The system manager can organize disk volumes into volume sets. Vol- ume sets can contain a mix of disk device types and can be extended by adding volumes. Within a volume set, files of any organization type can span multiple volumes. Files can be allocated to the set as a whole (the default) or to specific volumes within the set. Optionally, the system manager can allocate portions of indexed files to specific ar- eas of a single disk or to specific volumes in a volume set. The system manager can place quotas on a disk to control the amount of space individual users can allocate. Quota assignment is made by UIC and can be controlled for each individual volume set in the sys- tem (or for each individual volume if the volume is not part of a set). The system manager can cache disk structure information in memory to reduce the I/O overhead required for file management services. Although not required to do so, users can preallocate space and control auto- matic allocation. For example, a file can be extended by a given num- ber of blocks, contiguously or noncontiguously, for optimal file sys- tem performance. The system applies software validity checks and checksums to criti- cal disk structure information. If a disk is improperly dismounted be- cause of user error or system failure, the system rebuilds the disk's structure information automatically the next time the disk is mounted. The system detects bad blocks and prevents their reuse once the files to which the blocks were allocated are deleted. On DIGITAL Storage Ar- chitecture (DSA) disks, the disk controller detects and replaces bad blocks automatically. The system provides 255 levels of named directories and subdirecto- ries whose contents are alphabetically ordered. Device and file spec- ifications follow HP conventions. Users can use logical names to ab- breviate the specifications and to make application programs device and file name independent. Users can assign a logical name to an en- tire specification, to a portion of a specification, or to another log- ical name. 33 OpenVMS supports multivolume magnetic tape files with transparent vol- ume switching. Access positioning is done either by file name or by relative file position. E-BUSINESS AND INTEGRATION TECHNOLOGIES The HP OpenVMS e-Business and Integration Infrastructure Package pro- vides key Internet, e-business, and integration software technologies that enhance the OpenVMS Alpha and OpenVMS for Integrity servers op- erating systems and enable the development of e-business and enter- prise integration solutions. These technologies are bundled with the OpenVMS Alpha or OpenVMS for Integrity servers operating systems. Sev- eral of the components are additionally bound by an open source soft- ware license. The following components are included on the e-Business and Integra- tion Infrastructure Package on OpenVMS Alpha: o HP Secure Web Server (SWS), including support for the popular script- ing capabilities: mod_PHP, mod_Perl and Perl, and JavaServer Pages (Tomcat) o HP Secure Web Browser (SWB) o Java SE Development Kit (JDK) o HP Extensible Markup Language (XML) Technology o Simple Object Access Protocol (SOAP) Toolkit o Universal Description, Discovery, and Integration (UDDI) Client Toolkit o Web Services Integration Toolkit (WSIT) o NetBeans and Distributed NetBeans for OpenVMS o HP OpenVMS Enterprise Directory (LDAP/X.500) o HP BridgeWorks o COM for OpenVMS o HP Reliable Transaction Router (RTR) for OpenVMS Alpha 34 The following components are included in the Foundation Operating En- vironment (FOE) for OpenVMS for Integrity servers: o HP Secure Web Server (SWS) o HP Secure Web Browser (SWB) o Java SE Development Kit (JDK) o HP Extensible Markup Language (XML) Technology o Simple Object Access Protocol (SOAP) Toolkit o Universal Description, Discovery, and Integration (UDDI) Client Toolkit o Web Services Integration Toolkit (WSIT) o NetBeans and Distributed NetBeans for OpenVMS o HP OpenVMS Enterprise Directory (LDAP/X.500) The HP Reliable Transaction Router (RTR) for OpenVMS Backend for In- tegrity servers is included in the Mission Critical Operating Envi- ronment (MCOE) for OpenVMS Integrity servers. Additional information can be found in the OpenVMS e-Business and In- tegration Infrastructure Package Software Product Description (SPD 80.58.xx) or on the OpenVMS e-Business and Integration web page at: www.hp.com/go/openvms/ebusiness/ ASSOCIATED PRODUCTS The products in this section are not licensed as part of the OpenVMS Operating System and require a separate license. HP Galaxy Software Architecture on OpenVMS Alpha HP Galaxy Software Architecture on OpenVMS Alpha is available as a sep- arately licensed System Integrated Product (SIP). 35 By running multiple instances of OpenVMS in a single computer or hard partition, an OpenVMS Galaxy computing environment gives you quantum improvements in: o Compatibility-Existing applications run without changes. o Availability-Presents opportunities to upgrade software and expand system capacity without downtime. o Scalability-Offers scaling alternatives that improve performance of SMP and cluster environments. o Adaptability-Physical resources can be dynamically reassigned to meet changing workload demands. o Cost of ownership-Fewer computer systems reduce system management requirements, floor space, and more. For more information about OpenVMS Galaxy licensing requirements, re- fer to the HP Galaxy Software Architecture on OpenVMS Alpha Software Product Description (SPD 70.44.xx). For more information about how to create, manage, and use an OpenVMS Galaxy computing environment, refer to the OpenVMS Alpha Partition- ing and Galaxy Guide. HP OpenVMS Cluster Software HP OpenVMS Cluster software is available for Alpha and Integrity server systems, both as a separately licensed layered product and within the Mission Critical Operating Environment (MCOE) package on Integrity servers. It provides a highly integrated OpenVMS computing environment that is distributed over multiple systems, separated in distance measured from feet up to 500 miles, containing up to 96 nodes. OpenVMS Cluster systems and storage communicate using a combination of the following interconnects: o Memory Channel (Alpha only) o CI (Alpha only) 36 o DIGITAL Storage Systems Interconnect (DSSI) (Alpha only) o Fiber Distributed Data Interface (FDDI) (Alpha only) o Ethernet o Small Computer Systems Interface (SCSI) (Storage Only) o Shared Memory Cluster Interconnect (SMCI) (Galaxy only, Alpha only) o Fibre Channel (Storage Only) In addition, on Alpha only, when configured with suitable FDDI bridges, OpenVMS Cluster configurations can use DS3/T3 and asynchronous trans- fer mode (ATM) networking infrastructures. Applications running on one or more nodes in an OpenVMS Cluster sys- tem share resources in a coordinated manner. While updating data, the OpenVMS Cluster software synchronizes access to shared resources, pre- venting multiple processes on any node in the cluster from uncoordi- nated access to shared data. This coordination ensures data integrity during concurrent update transactions. Mixed-architecture and mixed-version clusters that contain both Al- pha systems and Integrity server systems are supported. As of OpenVMS Version 8.3, cluster satellite boot support on Integrity server systems is supported. This feature provides support for Integrity- to-Integrity satellite booting. Cross-architecture booting (booting an Integrity satellite node from an Alpha boot server and vice-versa) is not supported. Refer to the HP OpenVMS Cluster Software Software Product Description (SPD 29.78.xx) for more information. HP Volume Shadowing for OpenVMS HP Volume Shadowing for OpenVMS Alpha and Integrity servers performs disk mirroring operations using a redundant array of independent disks (RAID-1) storage strategy. Volume Shadowing for OpenVMS is available for Alpha and Integrity server systems as both a separately licensed 37 product, as well as a component of the Enterprise Operating Environ- ment (EOE) on Integrity servers. Volume Shadowing for OpenVMS provides high data availability for disk devices by ensuring against data loss that results from media dete- rioration or controller or device failure. This prevents storage sub- system component failures from interrupting system or application tasks. Refer to the HP Volume Shadowing for OpenVMS Software Product Descrip- tion (SPD 27.29.xx) for more information. HP RMS Journaling for OpenVMS HP RMS Journaling for OpenVMS Alpha and Integrity servers is avail- able as layered products and as a part of the Enterprise Operating En- vironment (EOE) on Integrity servers. Journaling enables a system man- ager, user, or application to maintain the data integrity of RMS files in the event of a number of failure scenarios. These journaling prod- ucts protect RMS file data from becoming lost or inconsistent. RMS Journaling provides the following three types of journaling: o After-image journaling. Allows users to reapply modifications that have been made to a file. This type of journaling allows users to recover files that are inadvertently deleted, lost, or corrupted. o Before-image journaling. Allows users to reverse modifications that have been made to a file. This type of journaling allows users to return a file to a previously known state. o Recovery-unit journaling. Allows users to maintain transaction in- tegrity. A transaction can be defined as a series of file updates on one or more files. If any failure occurs during the transaction, recovery-unit journaling rolls back the partially completed trans- action to its starting point. The binary kit for RMS Journaling ships with the OpenVMS Alpha and In- tegrity server distribution kits. To run the software, customers must purchase a license and documentation. Refer to the RMS Journaling for OpenVMS Software Product Description (SPD 27.58.xx) for more infor- mation. 38 HP Advanced Server for OpenVMS Alpha HP Advanced Server for OpenVMS is supported on OpenVMS Alpha systems only. Advanced Server V7.3B for OpenVMS is the only version supported on OpenVMS Alpha Version 8.3. Advanced Server is an OpenVMS-based network operating system (NOS) com- patible with Microsoft networking technology. The software lets you establish OpenVMS systems as servers to provide Windows desktop users (including Windows and Windows XP Professional) easy and efficient ac- cess to OpenVMS file and print services. Desktop users can use Microsoft products and utilities such as Windows Explorer to access these re- sources shared over the network. Advanced Server for OpenVMS can func- tion as a file and print server for a small, isolated community of users or as the foundation of a large network distributed over a wide ge- ographical area. The Advanced Server software also provides a flex- ible system for network administration and security, for both wide area networks (WANs) and local area networks (LANs). Refer to the HP Advanced Server for OpenVMS Software Product Descrip- tion (SPD 30.50.xx) for more information. HP PATHWORKS for OpenVMS (Advanced Server) HP Pathworks for OpenVMS (Advanced Server), also known as Pathworks Advanced Server, is currently available for Alpha based systems only. Pathworks for OpenVMS Version 6.1 is the only supported version for OpenVMS Alpha Versions 7.3, 7.3-1 and 7.3-2. Pathworks for OpenVMS Ver- sion 6.1 is not supported on OpenVMS Version 8.2 or higher. For further information, refer to the HP Advanced Server for OpenVMS Software Product Description (SPD 30.50.xx). HP TCP/IP Services for OpenVMS HP TCP/IP Services for OpenVMS is a System Integrated Product (SIP). For OpenVMS Alpha, a separate license is required. For OpenVMS for In- tegrity servers, TCP/IP Services is licensed as part of the Founda- tion Operating Environment (FOE); therefore, a separate license is not required. 39 HP TCP/IP Services for OpenVMS is HP's industry-standard implementa- tion of the TCP/IP and NFS networking protocols on the OpenVMS plat- form. TCP/IP Services for OpenVMS is integrated with the OpenVMS op- erating system installation. TCP/IP Services for OpenVMS provides in- teroperability and resource sharing among systems running OpenVMS, UNIX[TM], Windows, and other operating systems that support TCP/IP. TCP/IP pro- vides a comprehensive suite of functions and applications that sup- port industry-standard protocols for heterogeneous network communi- cations and resource sharing. TCP/IP Services for OpenVMS provides a full TCP/IP protocol suite including IP/multicasting, dynamic load bal- ancing, rlogin proxy, network file access, remote terminal access, re- mote command execution, remote printing, mail, application develop- ment, Post Office Protocol (POP), SNMP Extensible agent (eSNMP), and Finger Utility. Refer to the HP TCP/IP Services for OpenVMS Software Product Descrip- tion (SPD 46.46.xx) for further information. HP DECnet-Plus and HP DECnet Software HP DECnet for OpenVMS Alpha and Integrity server software is a Sys- tem Integrated Product (SIP). DECnet for OpenVMS Alpha is licensed sep- arately from the OpenVMS operating system. DECnet for OpenVMS for In- tegrity servers is a component of the Foundation Operating Environ- ment (FOE) on Integrity servers license bundle. HP DECnet-Plus (formerly DECnet/OSI) for OpenVMS Alpha is licensed sep- arately from the OpenVMS operating system as well. DECnet-Plus for Open- VMS for Integrity servers is a component of the Foundation Operating Environment (FOE) on Integrity servers license bundle. The license for DECnet for OpenVMS Alpha and OpenVMS for Integrity servers also grants the rights to use DECnet-Plus. Note that only one version of DECnet can be active on a single system at any one time. Both DECnet and DECnet- Plus allow OpenVMS systems to participate in network task-to-task com- munications for the purposes of transfer and copy of files, printing, the running of applications, etc. 40 DECnet-Plus offers task-to-task communications, file management, down- line system and task loading, network command terminals, and network resource sharing capabilities as defined in the DIGITAL Network Ar- chitecture (DNA) Phase V protocols. DECnet-Plus provides the newest DECnet features such as extended addressing and downline-load perfor- mance enhancements. DECnet-Plus integrates DECnet and OSI protocols and now provides a linkage to TCP/IP using Request for Comments (RFC) 1006 and RFC 1859. DECnet and OSI applications can now be run over DEC- net (NSP), OSI (CLNS), and TCP/IP transports. DECnet for OpenVMS Alpha offers the networking capabilities as defined in the DIGITAL Network Architecture (DNA) Phase IV. For more infor- mation, refer to the Associated Products section of this SPD. Refer to the DECnet-Plus for OpenVMS Software Product Description (SPD 50.45.xx), or the DECnet for OpenVMS Software Product Description (SPD 48.48.xx) for further information. HP DECram for OpenVMS HP DECram for OpenVMS is a disk device driver that improves I/O per- formance by allowing an OpenVMS system manager to create pseudo disks (RAMdisks) that reside in main memory. Frequently accessed data can be accessed much faster from a DECram device than from a physical disk device. These RAMdisks can be accessed through the file system just as physical disks are accessed, requiring no change to application or system software. Because main memory is allocated for the DECram device, extra memory is generally required. The OpenVMS system manager can designate the amount of memory dedicated to the DECram devices and the files that will be stored on it. Starting with HP OpenVMS Version 8.2, the binary kit for HP DECram ships with the HP OpenVMS Alpha and Integrity servers distribution kits. To run the DECram software, customers must first purchase a separate li- cense. For HP OpenVMS Alpha customers, the software licenses is: QL-MV3A*- **. 41 For HP OpenVMS for Integrity server customers, a software license for HP DECram may be purchased either as part of the OpenVMS Enterprise Operating Environment (EOE) or as a separate per-processor core li- cense (PCL): BA407AC For more information, refer to the HP DECram for OpenVMS Software Prod- uct Description (SPD 34.26.xx). HP DECwindows Motif for OpenVMS HP DECwindows Motif for OpenVMS is a System Integrated Product (SIP). It is a separately licensed layered product offered on the Alpha plat- form. On the Integrity Server platform, the DECwindows product is part of the Foundation Operating Environment (FOE) and is licensed under this package. This product provides support for both OSF/Motif, a standards-based graphical user interface, and the X user interface (XUI) in a single, run-time and development environment. DECwindows Motif displays the OSF/Motif user interface. Because both Motif and XUI are based on X.org X Window System, applications written with either toolkit will run re- gardless of which environment the user selects. Refer to the HP DECwindows Motif for OpenVMS Software Product Descrip- tion (SPD 42.19.xx) for more information. CONFORMANCE TO STANDARDS OpenVMS is based on the following public, national, and international standards. Distributed Computing Environment (DCE) Support The DCE for the OpenVMS product family provides a set of the distributed computing features specified by The Open Group's DCE, as well as tools for application developers. With DCE, The Open Group has established a standard set of services and interfaces that facilitate the creation, use, and maintenance of client/server applications. DCE for OpenVMS serves as the basis for an open computing environment where networks of multivendor systems appear as a single system to the user. Because 42 DCE makes the underlying networks and operating systems transparent, application developers can easily build portable, interoperable client/server applications. Users can locate and share information safely and eas- ily across the entire enterprise. DCE for OpenVMS supplies system man- agers with a set of tools to consistently manage the entire distributed computing environment, while assuring the integrity of the enterprise. DCE for OpenVMS currently consists of the following products: o DCE Run-Time Services for OpenVMS o DCE Application Developers' Kit for OpenVMS o DCE Cell Directory Service (CDS) o DCE Security Server, one of which is required for each DCE The right to use the DCE Run-Time Services is included with the Open- VMS operating system base license. All other DCE products are avail- able as separate layered products. Refer to the HP Distributed Com- puting Environment (DCE) for OpenVMS Software Product Description (SPD 43.05.xx) for more detailed information. Support for OSF/Motif and X Window System Standards DECwindows Motif provides support for OSF/Motif, a standards-based graph- ical user interface. DECwindows Motif also provides support for the X Consortium's X Window System, Version 11, Release 6 (X11R6) server and the Version 11, Release 5 (X11R5) client.