                Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq ACMS for OpenVMS Alpha, Version 4.4B      SPD 3 25.50.22                Compaq ACMS for OpenVMS VAX  , Version 4.4A)    DESCRIPTION   C Compaq Application Control and Management System for OpenVMS (ACMS) F is a transaction processing (TP) monitor designed for the Compaq Open-C VMS operating systems. ACMS works with other Compaq Computer Corpo- E ration commercial application software products to provide users with D a complete and customizable development and run-time environment forD transaction processing applications such as order tracking, account-G ing and billing, banking, shop floor control, and insurance claims pro-  cessing.  D ACMS software helps users through the entire application developmentF life cycle, including the installation, planning, design, development,F testing, implementation, management, and maintenance of complex TP ap-G plications. ACMS provides a special-purpose application definition lan- C guage for the structured definition of TP application functions and  run-time characteristics.   C ACMS makes efficient use of the OpenVMS operating systems and asso- F ciated hardware resources, making ACMS particularly suited to mission-C critical applications that require high throughput and performance.   G ACMS integrates with the following Compaq and third-party layered prod-  ucts:   F o  Compaq TP Desktop Connector, formerly called ACMS Desktop, for mul-.    tivendor client access to ACMS applications  C o  Compaq TP Web Connector for Web browser-based access to ACMS ap- 
    plications   C                                                         August 2002            B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C o  Compaq DECforms or Compaq TDMS for forms management (Note: Usage +    of TDMS requires an OpenVMS VAX system.)   E o  All OpenVMS languages that conform to the OpenVMS Calling Standard   E o  Oracle CDD for the creation, analysis, and administration of meta-     data   D o  Oracle Rdb, Oracle CODASYL DBMS, and OpenVMS RMS for data manage-    ment   5 o  Oracle Trace for performance event data collection   D Because ACMS is designed to allow for modular implementation as wellC as development, the client/server model can be used to separate and E distribute front-end processing (data input/output operations such as J forms processing) from back-end processing (data calculations and databaseD storage). In addition, ACMS allows users the use of nonstandard ter-C minal or I/O devices, such as bar-code readers and automatic teller  machines (ATMs).   Features  % ACMS provides the following features:   & o  Application development environment   o  Run-time system  % o  Application management and control    o  Remote system management    o  Client/server processing    o  Presentation services   o  Database management  0 o  Resource utilization collection and reporting   o  Task queuing    o  Data dictionary   o  Security   "                                  2           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   / o  OpenVMS Cluster environment and availability   # Application Development Environment   F ACMS uses a high-level, English-like definition language that replacesF system service calls for most TP application functions. Using the ACMS7 Application Definition Utility (ADU), a programmer can:   9 o  Structure all application work into three basic steps:   0    -  Exchange steps for terminal I/O processing  B    -  Processing steps for database access and general computation  F    -  Block steps for performing work common to several processing and       exchange steps  D o  Control task execution and flow using conditional statements suchF    as IF THEN ... ELSE, WHILE DO, SELECT FIRST, and CONTROL FIELD syn-/    tax in conjunction with Boolean expressions.   C o  Define and implement subroutine transactions using the CALL TASK 
    syntax.  ) o  Create menus and hierarchies of menus.   N o  Define resources used to execute transactions, such as servers, workspaces,    and audit trails.  ) o  Start and end database recovery units.   C ACMS also includes the ACMS Task Debugger to debug ACMS definitions  and servers.   Run-Time System   D ACMS includes a complete run-time system for application deployment.A The ACMS Run-Time System consists of eight specialized processes.   F The following ACMS processes manage the work within ACMS transactions:  E o  Command Process (CP) - Manages logins and interaction between ter- D    minals and ACMS. CPs are multithreaded (one CP process can handleC    menus and forms I/O for many ACMS terminals simultaneously). The   "                                  3           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   E    CP passes input data to the Application Execution Controller (EXC)     for processing by a server.  C o  Application Execution Controller (EXC) - Controls task execution D    for all the tasks in an application. Each application has its ownH    EXC process, which starts up and controls the server processes needed'    to handle processing work for tasks.   D o  Server Process (SP) - Carries out the high-level programming lan-F    guage routines or DCL routines that handle a task's processing workC    and database or file I/O. Programmers link their routines to the G    ACMS-supplied main program to create customized servers for database ,    access, computation, and other functions.  H o  Queued Task Initiator (QTI) - Removes task elements from a task queueC    and initiates their execution in a specified application. Queued F    tasks are tasks placed in a queue for later execution. Queued tasksE    cannot collect terminal input data; otherwise they are the same as     any other ACMS task.   D The ACMS processes that monitor and control the run-time system are:  D o  ACMS Central Controller (ACC) - Acts as the central control pointD    for ACMS run-time systems. The ACC starts and controls the Termi-G    nal Subsystem Controller, the QTI, the EXC, and the audit trail log. D    The ACC process must be started and running on each computer sys-(    tem where ACMS applications are used.  E o  Audit Trail Logger (ATL) - Writes information about a running ACMS E    system to the audit trail log file. The ATL keeps a record of when D    the ACMS system starts and stops, when users log in, and when ap-'    plications and tasks start and stop.   F o  Terminal Subsystem Controller (TSC) - Creates and controls the num-F    ber of active Command Processes (CPs) and assigns terminals to CPs.D    The TSC starts and stops CPs as needed, and controls which termi-    nals can access ACMS.        "                                  4           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C o  Software Event Logger (SWL) - Records all ACMS internal software D    errors and event messages that occur during the execution of ACMS    application programs.  G Communication among these run-time processes can occur on a single com- D puter system, or between more than one computer in a OpenVMS ClusterD system or DECnet network. For example, a Command Process (CP) on oneD computer system can initiate a task within an application on another computer system.  " Application Management and Control  F Once an application is developed, the user moves that application intoC a production (real-use) environment. ACMS provides support for ACMS . applications used in a production environment.  D ACMS includes seven utilities for defining, monitoring and modifying' application management characteristics:   : o  ACMSGEN - Modifies and displays ACMS system parameters.  D o  Application Authorization Utility (AAU) - Authorizes applications    to be installed.   E o  User Definition Utility (UDU) - Authorizes users to log in to ACMS F    and assigns login displays, including default menus, to ACMS users.  C o  Device Definition Utility (DDU) - Authorizes ACMS terminals and, D    optionally, defines captive terminals to log in directly to ACMS.  D o  Queue Manager (QUEMGR) - Creates and manages ACMS task queues and    queued task elements.  F o  Software Event Log Utility Program (SWLUP) - Creates reports of se-7    lected events recorded by the Software Event Logger.   D o  Audit Trail Report Utility (ATR) - Returns records of application    and user activity.       "                                  5           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   D In addition to the utilities, ACMS also provides users with the fol-6 lowing support for application management and control:  E o  ACMS operator commands - Performs standard operator functions such E    as starting and stopping the ACMS system, the TSC process, the QTI "    process, and ACMS applications.  D o  Command procedures - Evaluates and modifies the values of OpenVMSB    and ACMS system parameters and of ACMS run-time process quotas.   Remote System Management  C The ACMS Remote Manager provides the capability to monitor and man- E age the ACMS application environment. ACMS system managers can access F the Remote Manager using one of the supported interfaces over a TCP/IP network.  D The Remote Manager must be running on the same node as the ACMS run-D time system it is monitoring or accessing. Communication between the; Remote Manager and the ACMS run-time system is transparent.   4 Three interfaces allow access to the Remote Manager:  C o  RPC Interface-Provides local or remote access to ACMS management E    information using the Open Network Computing Remote Procedure Call F    (ONC RPC) protocol. This interface can be used by user-written pro-7    grams to implement customized ACMS management tools.   F o  Command Line Utility-Provides command line access to management in-C    formation as well as control of the Remote Manager process. This "    utility uses the RPC Interface.  D o  Simple Network Management Protocol (SNMP) Interface-Provides net-F    work access to ACMS management information using the industry stan-E    dard SNMP protocol. This protocol is supported by most system man-     agement consoles and tools.  E ACMS system managers control the data being collected, including ACMS D process monitoring, and the management interfaces themselves through either SNMP or RPC commands.  "                                  6           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   D The Remote Manager enables ACMS system managers to do the following:  & o  Remotely manage the Remote Manager.  C o  Remotely manage data collection including configuring SNMP traps .    and viewing management information on line.  ) o  Remotely modify ACMS run-time systems.   D o  Write programs that remotely access management information online    using ONC RPC and SNMP.   Client/Server Processing  G ACMS uses the client/server model to distribute and separate functions. C This model can be implemented on a single node or on multiple nodes  in a DECnet network.  C The terminal and menu functions are handled on the client, or front C end, of the transaction processing system, while task flow control, F data processing, and computations are performed on the server, or back end, of the system.   C Because the ACMS client/server model always provides separate front E and back ends, users can at any time offload the front-end to another ; computer system without reprogramming the application code.   D The ACMS Systems Interface (SI) lets users write front end programs,F or agents, to support specialized devices such as bar-code readers and automatic teller machines.  C ACMS includes support for failover in a distributed environment. If D one OpenVMS node is not available to process a transaction, ACMS canE automatically route the transaction to another application running on  an available node.   Presentation Services   C ACMS supports both terminal-driven and PC/workstation-driven TP ap- D plications with presentation services. Users have the option of run-C ning ACMS tasks from menus on VT terminals, or from a GUI interface # on a PC/workstation desktop system.   "                                  7           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   I ACMS supports DECforms as its primary presentation service for character- D cell terminals in ACMS applications. In addition, ACMS provides sup-C port for Compaq TDMS on OpenVMS VAX systems. ACMS applications that C use TDMS must be distributed in order to use ACMS on OpenVMS Alpha. D See the Compaq ACMS for OpenVMS Writing Applications manual for more% information about these restrictions.   I The TP Desktop Connector product provides an API that allows user-written D program running on various PC or workstation desktop systems to ini-G tiate and respond to ACMS tasks. A wide range of Compaq and third-party D desktop tools can be used for the development of client presentation services and applications.  J ACMS also provides support for other presentation service products throughD the ACMS Request Interface and Systems Interface. The Request Inter-E face lets users use presentation services other than DECforms or TDMS E for I/O functions limited to one user per process. The Systems Inter- F face lets users use presentation services for single-user or multiple- user I/O functions.    Database Management   F ACMS includes support in its definition language for starting and end-C ing database transactions/recovery units through a database manage- D ment system. Database products supported include Oracle Rdb (includ-' ing SQL), RMS, and Oracle CODASYL DBMS.   E Using the DECdtm component of the OpenVMS operating system, ACMS lets C users coordinate operations on multiple recoverable resources (such E as databases and files) within a single atomic transaction. Users can E perform operations on multiple databases through a single transaction D and ensure atomicity (that is, if the transaction fails, any changesF made to databases, files, or ACMS queues are rolled back to their pre-G vious state before the transaction started). Please note that RMS Jour- D naling for OpenVMS is required to support recoverable ACMS queue op-G erations coordinated using DECdtm. RMS Journaling for OpenVMS is a sep- D arate layered product, distinct from RMS, and is supplied with Open- VMS.      "                                  8           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C ACMS applications can also access other data management products or B file management systems that support the OpenVMS Calling Standard.  - Resource Utilization Collection and Reporting   C ACMS supports Oracle Trace to allow the collection and reporting of G event-based data gathered from any combination of OpenVMS layered prod- C ucts and ACMS applications. For each predefined event in ACMS, Ora- E cle Trace can collect information about resource utilization, such as G CPU time, or ACMS data items, such as task name. Using the Oracle Trace C cross-facility feature, you can relate ACMS events with events from  multiple layered products.   Task Queuing  D Some ACMS applications require that the data be collected and storedE in a temporary storage area (queue) for the application to process at D another time. The ACMS queuing facility lets users create and manageD ACMS task queues. ACMS queue services are used to place/remove tasks on/off ACMS task queues.   Data Dictionary   D ACMS supports the Oracle CDD/Repository data dictionary. ACMS storesE application definitions in Oracle CDD/Repository directories and uses < Oracle CDD/Repository record definitions for its workspaces.   Security  C ACMS ensures that the user's data remains secure by giving the sys- E tem manager control over which users have access to ACMS. Using Open- ; VMS and ACMS authorization facilities, system managers can:    o  Authorize users to use ACMS.   ( o  Control terminals connecting to ACMS.  ) o  Limit the applications a user can run.       "                                  9           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   D o  Prevent unauthorized access to the operating system while running    ACMS tasks.  F ACMS includes transaction security in the form of access control listsC (ACLs) in the definition language. Whenever a user selects a trans- E action, that user's OpenVMS identifier is checked against the ACL de- D fined for that transaction to determine whether that user is allowed to execute that transaction.  ( OpenVMS Cluster Environment/Availability  I In a OpenVMS Cluster environment, ACMS applications support highly avail- D able configurations that help avoid single points of system failure.  D ACMS includes support for failover in a OpenVMS Cluster environment.E If one OpenVMS Cluster processor is not available to process a trans- C action, ACMS can automatically route the transaction to another ap- F plication running on an available processor that shares the same data.  C ACMS can improve the performance of a database management system in F a OpenVMS Cluster environment by allowing the use of the client/server4 model to run database servers on a single processor.  
 Documentation   = ACMS includes a complete and comprehensive documentation set:   F o  An introductory manual explains ACMS concepts and components to new	    users.   F o  Advanced manuals describe, in a task-oriented style, how to design,'    build, and manage ACMS applications.   . o  Complete reference information is provided.  E The ACMS Development System documentation set consists of the follow-  ing manuals:   o  Getting Started  G    -  Provides an introduction to the basic elements of the ACMS trans-        action processing system.   "                                 10           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C    -  Provides a step-by-step tutorial for developing a simple ACMS        application.  <    -  Provides an overview of the AVERTZ sample application.  (    -  Provides a glossary of ACMS terms.  ! o  Concepts and Design Guidelines   2    -  Describes how to design an ACMS application.   o  Writing Applications   D    -  Describes how to write task, task group, application, and menuA       definitions using the Application Definition Utility (ADU).   C    -  Describes the input/output options and restrictions in a dis-        tributed environment.   C    -  Describes how to write and migrate ACMS applications to Open-        VMS Alpha systems.   o  Writing Server Procedures  C    -  Describes how to write programs for use with tasks and how to F       debug tasks and programs, including how to write procedures that       access databases.   E    -  Describes how ACMS works with the APPC/LU6.2 programming inter- 5       face to communicate with IBM CICS applications.     o  Systems Interface Programming  D    -  Describes how to use Systems Interface (SI) Services to submit       tasks to an ACMS system.   o  Managing Applications  C    -  Describes how to authorize, install, run, and manage ACMS ap- 5       plications, and how to control the ACMS system.   " o  Remote Systems Management Guide  D    -  Describes the features of the Remote Manager for managing ACMSD       systems, how to use the features, and how to manage the Remote       Manager.  "                                 11           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX    o  ADU Reference Manual   E    -  Provides reference information about the ADU commands, phrases,        and clauses.  & o  ACMS Version 4.4 Installation Guide  D    -  Describes installation requirements, step-by-step installation9       instructions, and required post-installation tasks.    o  Quick Reference Guide  F    -  Provides a complete list of ACMS syntax with brief descriptions.   o  Release Notes  G    -  Provides late-breaking and other notable online information about )       the latest release of the software.    o  Online Help  8    -  Provides online help about ACMS and its utilities.   HARDWARE REQUIREMENTS    Hardware Configurations   D ACMS Version 4.4A is supported on all hardware configurations refer-D enced in the OpenVMS Operating System for VAX, Version 7.3, SoftwareE Product Description (SPD 25.01.xx). ACMS Version 4.4B is supported on D all hardware configurations referenced in the OpenVMS Operating Sys-I tem for Alpha, Version 7.3-1, Software Product Description (SPD 25.01.xx)   0 Disk Space Requirements (Block Cluster Size = 1)  C The approximate amount of space required on the system disk to sup- G port the ACMS for OpenVMS software is as follows. Actual sizes may vary D depending on the system environment, configuration, and software op- tions.    "                                 12           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C ___________________________________________________________________ C ACMS_Kit___________VAX__________Alpha______________________________   - Development        43,000       70,000 blocks  Installation       blocks +                    21.5         35.0 Mbytes                     Mbytes   - Development        30,000       42,000 blocks  Permanent          blocks +                    15.0         21.0 Mbytes                     Mbytes   - Run-Time In-       28,000       38,000 blocks  stallation         blocks +                    14.0         19.0 Mbytes                     Mbytes   - Run-Time Perma-    25,000       33,000 blocks  nent               blocks +                    12.5         16.5 Mbytes                     Mbytes   - Remote Instal-     21,000       27,000 blocks  lation             blocks +                    10.5         13.5 Mbytes                     Mbytes   - Remote Perma-      18,000       24,000 blocks  nent               blocks +                    9.0          12.0 Mbytes C ___________________Mbytes__________________________________________    SOFTWARE REQUIREMENTS               "                                 13           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   E Compaq ACMS for OpenVMS Alpha, Version 4.4B software runs on the fol- 0 lowing versions of the OpenVMS operating system:  D o  OpenVMS Alpha Operating Systems Versions 6.2, 7.2-2, 7.3 and 7.3-    1.   C Compaq ACMS for OpenVMS VAX, Version 4.4A software runs on the fol- 0 lowing versions of the OpenVMS operating system:  < o  OpenVMS VAX Operating Systems Versions 6.2, 7.2, and 7.3.  D However, only specific versions of networking software are supportedD for each version of the operating system. See the following sections for the supported versions.   C ___________________________________________________________________ *                 Compaq TCP/IP Services forC O/S_Version_____OpenVMS_Version____________________________________    Alpha V6.2      V4.2   VAX V6.2        V4.2   Alpha V7.2-2    V5.1   VAX V7.2        V5.1   Alpha V7.3      V5.1   VAX V7.3        V5.1  C Alpha_V7.3-1____V5.3_______________________________________________   C The following versions of Oracle CDD/Repository is required that is = supported on your version of the operating system as follows:   + o  OpenVMS Alpha requires V5.3, V6.1A, V7.1   # o  OpenVMS VAX requires V5.3 - V7.1   J Note: When using ACMS with Compaq DECnet-Plus for OpenVMS (formerly calledC DECnet/OSI), the Transport Layer must be configured to use the Net- D work Services Protocol (NSP). ACMS restricts node names to a maximum of six characters.   OPTIONAL SOFTWARE   "                                 14           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22  Compaq ACMS for OpenVMS VAX  F Certain versions of these products depend on a specific version of theH operating system. Please refer to the Software Product Description (SPD)D or contact the vendor for the product in question to determine which* version is required for correct operation.  C ___________________________________________________________________                       OpenVMSC Software_____________VAX_________OpenVMS_Alpha_____________________   1 Compaq DECforms      V3.0,       V3.0, V3.1. V3.2                       V3.1,                      V3.2 ' Compaq DECset        V11.2-      V12.4A  (except PCA)         12.4A% LSE (part of         V4.2-       V4.7  DECset)              V4.7 " Compaq TDMS          V1.9A,V1.9B -2 Compaq TP Desktop    V2.2,       V2.2, V2.3, V3.1A Connector (for-      V2.3, merly called ACMS    V3.1A Desktop). Compaq TP Web        V1.0 or     V1.0 or later Connector            later2 Oracle CDD/RepositoryV5.3-       V5.3, V6.1A, V7.1                      V7.1 * Oracle CODASYL       V5.1-       V5.1-V7.0 DBMS                 V7.0 * Oracle Rdb           V5.1-       V5.1-V7.0                      V7.0 + Oracle Trace         V2.2,       V2.2, V2.4                       V2.4 9 RMS Journaling       V6.2,       V6.2, V7.2, V7.3, V7.3-1  for OpenVMS          V7.2,C _____________________V7.3__________________________________________   + Requirements for Web Enabled Remote Manager           "                                 15           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   7 The pre-requisite software for using the ACMS HMMO are:   ' o  Compaq Management Agents for OpenVMS   E    Note: Only the WEBM Server is required to be started. The included     web agents are not required.   C o  OpenVMS Alpha V7.2-1 or higher (as required by Compaq Management     Agents for OpenVMS)  C o  Web Browser - A browser or platform that supports Java Plug-ins, -    JavaScript & Cascading Style Sheets (CSS).   ; The following browser versions and platforms are supported:   E o  Windows - Netscape V4.76, Netscape V6, Internet Explorer V5.5 with     Java Plugin V1.3.0   6 o  Tru64 UNIX - Netscape V4.72 with Java Plugin V1.2.2   SOFTWARE LICENSING  E This software is furnished only under a license. For more information G about licensing terms and policies from Compaq, contact your local Com- - paq office. LICENSE MANAGEMENT FACILITY (LMF)   C This layered product supports the OpenVMS License Management Facil-  ity.  D License units for the Development System are allocated on a CapacityE Basis by hardware tier. License units for the Run-Time or Remote Sys- D tems are allocated on a Capacity Basis by hardware tier or a Concur- rent Use basis.   E For more information on the License Management Facility, refer to the D OpenVMS Operating System for Alpha and VAX Software Product Descrip-D tion (SPD 25.01.xx) or the License Management Facility manual of the+ OpenVMS Operating System documentation set.    CLUSTER ENVIRONMENT   "                                 16           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C This layered product is fully supported when installed on any valid D and licensed OpenVMS Cluster configuration without restrictions. TheF Hardware Requirements section of this Software Product Description de-4 tails any special hardware required by this product.  I OpenVMS Cluster configurations are fully described in the OpenVMS Cluster D Software Software Product Description (SPD 29.78.xx) and include CI,0 Ethernets and mixed-interconnect configurations.   DISTRIBUTION MEDIA  C This product is distributed as part of the OpenVMS Software Product 
 Libraries.  C The software documentation is also available as part of the OpenVMS ) Online Documentation Libraries on CD-ROM.    ORDERING INFORMATION  " Three kits are available for ACMS:  E o  ACMS Development System-The complete set of ACMS features that fa- E    cilitate the development and deployment of ACMS applications on an     OpenVMS system.  D o  ACMS Run-Time System-A subset of the ACMS Development System thatC    allows the deployment and limited customization of ACMS applica-     tions on an OpenVMS system.  D o  ACMS Remote Access-A subset of the ACMS Run-Time System that pro-F    vides the capability to place users and the associated terminal I/OD    on a separate OpenVMS system to offload the application system or    OpenVMS Cluster.   C ___________________________________________________________________ C For_OpenVMS_VAX______________Part_Number___________________________   ( Development License,         QL-079A*-AA
 Unlimited Use     "                                 17           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C ___________________________________________________________________ C For_OpenVMS_VAX______________Part_Number___________________________   ( Development Documentation    QA-079AA-GZ  ( Development Software         QT-079A*-** Product Services  ( Run-Time License, Unlim-     QL-076A*-AA ited Use  ( Run-Time License, Concur-    QL-076AA-3B rent Use  ( Run-Time Documentation       QA-076AA-GZ  ( Run-Time Software Product    QT-076A*-** Services  ( Remote Access, Unlimited     QL-Y30A*-** Use   ( Remote Access, Concurrent    QL-Y30AA-3B Use   ( Remote Access Documenta-     QA-Y30AA-GZ tion  ( Remote Access Software       QT-Y30A*-**C Product_Services___________________________________________________   C ___________________________________________________________________ C For_OpenVMS_Alpha____________Part_Number___________________________   ( Development License,         QL-2PZA*-AA
 Unlimited Use   ( Development Documentation    QA-076AA-GZ  ( Development Software         QT-2PZA*-** Product Services  ( Run-Time License, Unlim-     QL-2Q1A*-AA ited Use  ( Run-Time License, Concur-    QL-076AA-3B rent Use  "                                 18           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   C ___________________________________________________________________ C For_OpenVMS_Alpha____________Part_Number___________________________   ( Run-Time Documentation       QA-076AA-GZ  ( Run-Time Software Product    QT-2Q1A*-** Services  ( Remote Access, Unlimited     QL-2Q0A*-** Use   ( Remote Access, Concurrent    QL-Y30AA-3B Use   ( Remote Access Documenta-     QA-Y30AA-GZ tion  ( Remote Access Software       QT-2Q0A*-**C Product_Services___________________________________________________   F *  Denotes variant fields. For additional information on available li-D    censes, services, and media, refer to the appropriate price book.   SOFTWARE PRODUCT SERVICES   D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.   GROWTH CONSIDERATIONS   D The minimum hardware/software requirements for any future version ofC this product may be different from the requirements for the current  version.   SOFTWARE WARRANTY   F This software is provided by Compaq with a 90-day conformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.   F The above information is valid at time of release. Please contact your8 local Compaq office for the most up-to-date information.  2  2002 Compaq Information Technologies Group, L.P.  "                                 19           B Compaq ACMS for OpenVMS Alpha, Version 4.4B           SPD 25.50.22 Compaq ACMS for OpenVMS VAX   F Compaq, the Compaq logo, ACMS, Alpha, DECforms, DECnet, DIGITAL, Open-E VMS, and VAX are trademarks of Compaq Information Technologies Group, ( L.P. in the U.S. and/or other countries.  C Microsoft and Windows NT are trademarks of Microsoft Corporation in   the U.S. and/or other countries.  D UNIX is a trademark of The Open Group in the U.S. and/or other coun- tries.  C All other product names mentioned herein may be trademarks of their  respective companies.   F Confidential computer software. Valid license from Compaq required forC possession, use, or copying. Consistent with FAR 12.211 and 12.212, H Commercial Computer Software, Computer Software Documentation, and Tech-C nical Data for Commercial Items are licensed to the U.S. Government + under vendor's standard commercial license.   E Compaq shall not be liable for technical or editorial errors or omis- C sions contained herein. The information is provided "as is" without F warranty of any kind and is subject to change without notice. The war-E ranties for Compaq products are set forth in the express limited war- E ranty statements accompanying such products. Nothing herein should be 1 construed as constituting an additional warranty.                                 "                                 20