       %                                COMPAQ    Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  ACMSxp Version 3.2A for OpenVMS Alpha   SPD 60.53.07    DESCRIPTION   F Compaq ACMSxp for OpenVMS Alpha is middleware that makes client/serverC business applications run more reliably, efficiently, and securely. D ACMSxp works with other Compaq Computer Corporation commercial soft-C ware products to provide users with a complete and customizable de- C velopment and runtime environment for transaction processing appli- G cations such as order tracking, accounting and billing, shop floor con- & trol, and insurance claims processing.  E Many of the concepts and features incorporated in ACMSxp have evolved F from the Compaq ACMS TP monitor, which has been available on the Open-D VMS VAX platform since 1984. However, ACMSxp is a different and sep-F arately orderable product that runs on multiple platforms and does notF share any common source or binary ACMS files. ACMSxp has been designedC to take advantage of open transaction processing technology, incor- G porating the latest industry standards for data communications and dis- F tributed computing. ACMSxp also conforms to widely accepted Spirit and5 X/Open industry standards for transaction processing.   E ACMSxp documentation helps guide users through the entire application E development life cycle, including the installation, planning, design, D development, testing, implementation, management, and maintenance ofG complex TP applications. ACMSxp provides a high-level structured trans- C action definition language (STDL) that defines TP application func- " tions and runtime characteristics.  C                                                           June 1999   C                                                         AE-QRFYH-TE          G ACMSxp makes efficient use of the operating system and associated hard- H ware resources, making itself particularly suitable for running mission-C critical applications that require high throughput and performance.   D ACMSxp is closely integrated with the following Compaq layered soft- ware products:  . o  Compaq DCE client/server data communication  D o  Compaq TP Desktop Connector for ACMSxp for multivendor client ac-    cess to ACMSxp   ? o  Compaq TP Web Connector for web-enabling ACMSxp applications   ) o  Compaq C language compiler for OpenVMS   F Because ACMSxp is designed to allow for modular implementation as wellD as development, users can separate and distribute front-end process-F ing (data input/output operations such as forms processing) from back-E end processing (data calculations and database storage). In addition, D ACMSxp allows developers to implement applications using nonstandardG terminal or I/O devices (such as barcode readers and ATMs). ACMSxp sup- D ports the deployment of TP applications in a production environment.   Features  & o  Application development environment   o  Runtime system   ( o  System and application administration    o  Front-end/back-end processing   o  Database management   o  Japanese text data support    o  Documentation set  "                                  2         # Application Development Environment   D The ACMSxp development environment is based on a modular approach toG application development. When creating an application with ACMSxp, pro- F grammers can clearly delineate the behaviors of the various functionalF portions of the application, including user interface capture and dis-G play, data calculation, access to data storage, and higher-level trans-  action block responsibilities.  C To support programmers in adhering to this modular approach, ACMSxp G provides a high-level programming language called the Structured Trans- E action Definition Language (STDL). STDL is a compiler-based, English- G like definition language that replaces lower-level system service calls C for most TP application functions. Because the STDL syntax is simi- C lar to English, programmers can more easily define the sequence and = style in which the various functions of an application occur.   D Using STDL, programmers can specify as much or as little applicationD control as they choose, depending on their preferences for configur-E ing the application environments. Some environments require that most I of the control occur at the client, with the server dedicated to database E access. In this case, relatively little STDL programming is required. C Other applications require more stringent control at the server, to F provide more sophisticated security, reliability, or availability fea-C tures. A more robust high-level definition of the application using  STDL is warranted in this case.   , The basic functional components of STDL are:  B o  Exchange step definition and invocation for display interaction  D o  Processing step definition and invocation for database access and!    general computation activities   K o  Data resource definition of entities such as servers, tasks, workspaces,     and logs   C o  Transaction demarcation and resource manager recovery specifica-     tion   "                                  3         D o  Execution flow control specification such as IF ... THEN ... ELSE    and loop statements.    Runtime System  F ACMSxp, when integrated with other layered products, provides all fea-D tures required for the execution of TP applications in a distributedC environment. The ACMSxp runtime system is based on DCE. ACMSxp uses D DCE for remote procedure call (RPC) communication, naming resolution, (CDS), threading (DECthreads), and security.  F The runtime system is composed of the following components, which man-> age applications and the control of the runtime system itself:   o  Request execution  C A request performs work for an ACMSxp end user. A request is always F executed on behalf of a particular ACMSxp end user and is created whenE the end user invokes an application procedure. When a client performs C a remote procedure call, the call is redirected to a backup or sec- H ondary server if the intended server is not reachable (due to node fail-4 ure, for example). This behavior is called failover.   o  Exception handling   C An exception is the occurrence of an error or other unexpected con- E dition during the execution of a request. Exceptions may be raised by C the application or the ACMSxp runtime system. When an exception oc- C curs, it is either propagated back to the client that initiated the D request, or it is handled at the task level without the client know- ing an exception occurred.  
 o  Servers  D An ACMSxp system has two types of servers; system servers defined byD ACMSxp, and user-defined application servers. System servers provideD ACMSxp runtime features and are managed by the ACMSxp system. An ap-E plication server provides a set of application procedures and is man- F aged through ACMSxp system administration. The set of application pro-C cedures provided by a particular server is defined by an STDL group  specification.  "                                  4          o  Security   D To invoke a server, ACMSxp software uses an authorization mechanism.G If authorization fails, invocation is rejected. Any authorization fail- " ure is logged as a security event.   o  RPC communication  D The ACMSxp runtime environment provides full support for the DCE RPCE protocol supplied with the DCE RPC product. The DCE RPC protocol sup- C ports full interoperation between ACMSxp clients and servers resid-  ing in separate address spaces.    o  Transactional coordination   D The ACMSxp runtime environment provides full transactional coordina-F tion of resources across all Compaq platforms including Windows NT[R], OpenVMS, and Tru64 UNIX[R].    o  Process management   D Runtime server process termination is detected by the ACMSxp runtimeD system and may cause the creation of a new server process to replace the terminated one.   % System and Application Administration   C ACMSxp provides facilities for managing the runtime system environ- 8 ment and includes the following administrative features:   o  System configuration   C Scripts are provided for creating, deleting, starting, and stopping C the TP system. Most management operations can be performed remotely  using the ACMSxp GUI.    o  Centralized administration   F System and application servers can be managed from a central location.C This can be done from either the command line interface or from the F GUI (Graphical User Interface) running on the Windows NT platform. TheE operations that can be performed from one location include: creating, C deleting, starting, and stopping servers; showing and modifying at- E tributes of TP systems, servers, and other objects within TP systems.   "                                  5          o  Multiple TP systems  F A single node can host multiple TP systems. Each TP system and the ap-D plication components within it are completely isolated from other TPD systems on the node. For example, test and production versions of an< application can run in separate TP systems on the same node.   o  Access control   D Access control lists (ACLs) control who can invoke procedures or in-C sert elements into queues at runtime. ACLs can also control who can " perform administration operations.   o  Event logging  G Exceptions and trace information in the runtime environment can be con- D figured to capture events and record them in an event log. A tool is5 provided for examining the contents of the event log.    o  Performance monitoring   F ACMSxp performance monitoring software allows you to collect data con-I cerning processing activity within a particular TP system on an as needed  basis.  ) o  Selectable Resource Manager (RM) model   E Allows the configuration of ACMSxp with or without transactional sup- C port. Allows selection of several transaction management configura- G tions depending on the number and type of resource managers being used.    Front-End/Back-End Processing   D With the aid of customer-written presentation servers, ACMSxp appli-D cations can be developed with a centralized or client/server config-F uration. Customer-written presentation servers enable customers to in-E terface with client devices or nonstandard devices. ACMSxp routes ex- E change I/O to the device that originated the request and supplies the D device with the context necessary for the customer-written presenta-! tion server to access the device.   "                                  6         C Customer-written presentation servers are serially reusable, single D user, synchronous servers. However, the presentation server code de-D veloper must be aware that the presentation procedures run in a mul- tithreaded environment.    Database Management   C This release of ACMSxp for OpenVMS Alpha supports the Oracle[R] Rdb  database management system.    Japanese Text Data Support  I ACMSxp for OpenVMS Alpha allows the exchange of Japanese text data across A different platforms through the use of code conversion functions.    Documentation Set   C ACMSxp for OpenVMS Alpha includes a complete and comprehensive doc- C umentation set. ACMSxp concepts and components are explained to new E users in a Software System Overview. An STDL Encyclopedia is provided D as a full reference to the STDL language. Additionally, a comprehen-H sive three-part guide demonstrates how ACMSxp applications are designed,D developed, and managed, using the example of a reservations process- ing application.  C The ACMSxp for OpenVMS Alpha documentation set consists of the fol-  lowing manuals and online help:    o  ACMSxp Release Notes   G Specific information related to the current version of ACMSxp for Open- C VMS Alpha and material added too late for publication in other ACM-  Sxp documents.   o  Getting Started  C A manual containing a step-by-step tutorial for developing a simple  ACMSxp application.   . o  ACMSxp for OpenVMS Alpha Installation Guide  C Description of installation requirements, step-by-step installation > instructions, and post-installation tasks, with full examples.  "                                  7          o  Software System Overview   D An overview of the ACMSxp software system, including an introduction: to the STDL language and a discussion of related products.   o  STDL Encyclopedia  E The reference material for the STDL application programming interface 6 to the ACMSxp portable transaction processing monitor.  . o  ACMSxp Developing and Managing Applications  C A three-part manual describing how to design, develop, and manage a D transaction processing application that can be implemented using the ACMSxp portable TP monitor.    o  ACMSxp Help  E A comprehensive help file that describes the STDL language and how to ' develop and manage ACMSxp applications.    o  ACMSxp Management GUI Help   E A system administration GUI help file that provides information about A managing ACMSxp entities through the GUI entity hierarchy window.    CONFORMANCE TO STANDARDS  E ACMSxp conforms to formal industry standards set forth by the follow-  ing standards bodies:   - o  International Standards Organization (ISO)   / o  American National Standards Institute (ANSI)   9 ACMSxp conforms to the following industry specifications:   > o  Open Software Foundation (OSF) DCE (part of The Open Group)  - o  Multivendor Integration Architecture (MIA)   
 o  NMF/Spirit   " o  X/Open (part of The Open Group)      -  DTP Model   "                                  8         
    -  STDL   HARDWARE REQUIREMENTS   E ACMSxp Version 3.2A for OpenVMS Alpha is supported on all Alpha hard- D ware configurations running OpenVMS Version 6.2, 7.1, or 7.2. Refer-F ence can be made to the configuration charts listed in the OpenVMS Op-C erating System Software Product Description (SPD 25.01.xx) Hardware  Support Tables.   1 Disk Space Requirements (Block Cluster Size = 1):   * Disk space required on       30,000 blocks user disk for installa-  tion: * Disk space required on       24,000 blocks user disk for permanent  use:  H The sizes are approximate; actual sizes may vary depending on the user's1 environment, configuration, and software options.    Memory Requirements:  G The minimum memory supported is 128 Megabytes. However, the use of this F software in conjunction with increased memory capability improves per-	 formance.    SOFTWARE REQUIREMENTS   F ACMSxp for OpenVMS Alpha runs on all Alpha machines that use the Open-F VMS operating system. Allowable configurations include: one Alpha pro-D cessor for centralized configurations; multiple Alpha processors for client/server configurations.   C Software required on all OpenVMS Alpha nodes in ACMSxp environment:   ) o  OpenVMS Alpha Version 6.2, 7.1, or 7.2   9 o  Compaq TCP/IP Services for OpenVMS Version 4.1 (ECO 4)   "                                  9         D o  Compaq DCE Version 1.4 (ECO 1) Runtime Services for OpenVMS Alpha   o  RMS Journaling License   ! o  DECnet/OSI Version 6.3 (ECO 6)   C Additional software required on at least one additional node in the  network:  C o  Compaq DCE Version 1.4 (ECO 1) Cell Directory Server for OpenVMS     Alpha  C o  Compaq DCE Version 1.4 (ECO 1) Security Server for OpenVMS Alpha   D Additional software required on all OpenVMS Alpha nodes used for de-
 velopment:   o  Compaq C Version 5.3-006   G o  Compaq DCE Version 1.4 (ECO 1) Application Developer's Kit for Open-     VMS Alpha   SOFTWARE LICENSING INFORMATION  E ACMSxp for OpenVMS Alpha is available in either a Development or Run- E time license offering. The Development license permits the use of the C software to develop, test, and deploy ACMSxp applications. The Run- D time license permits the use of the software to test and deploy ACM- Sxp applications.   G Both Development and Runtime license offering are available in two dif- E ferent license types. These license types are Capacity and Conncurent  Use:  C o  The Capacity license offering permits the use of the software on     a single system.   C o  The Concurrent Use license offering permits the use of the soft-     ware by a single user.   "                                 10         E This software is furnished only under a license. For more information D about Compaq's licensing terms and policies, contact your local Com- paq office._  # LICENSE MANAGEMENT FACILITY SUPPORT   C This layered product supports the OpenVMS License Management Facil-  ity.  C License units for this product are allocated on a Capacity and Con-i current Use basis.  F Each Concurrent Use license allows any one individual at a time to use the layered product.  E For more information on the License Management Facility, refer to thesJ OpenVMS Alpha Operating System Software Product Description (SPD 41.61.xx)D or the License Management Facility manual of the OpenVMS Alpha Oper- ating System documentation set.   F For more information about Compaq's licensing terms and policies, con- tact your local Compaq office.   OPTIONAL SOFTWAREw   o  TP Web Connector Version 1.2-  G    Enables seamless web access to business applications running on ACM-tH    Sxp, ACMS, and Compaq Portable TP systems. For more information visit    the web site located at:C/    http://www.software.digital.com/tpwebconnectt   o  Compaq COBOL Version 2.4i  C o  Any database supported by OpenVMS Alpha Version 6.2, 7.1, or 7.2           "                                 11 S    s  C o  Compaq DECforms is an optional software product for the develop- E    ment and deployment of forms-based user interfaces for interactiveuG    applications running on OpenVMS systems. DECforms is a complete useraF    interface management system (UIMS), providing applications with theE    look and feel of a forms interface and a robust set of dialog man--F    agement and validation functions to control the user interface dur-D    ing application execution. DECforms supports Motif-based worksta-H    tions, X terminals, VT-based character-cell terminals, and PostScript    printers.  . o  TP Desktop Connector Version 3.1 for ACMSxp  K    Enables desktop system users to access ACMSxp, ACMS, and Compaq Portable G    TP applications from the native desktop system environment. For more--    information visit the web site located at:g#    http://ww1.digital.com/tpdesktopl   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.   DISTRIBUTION MEDIA  C This product is distributed on an individual product CDROM, or partp; of the OpenVMS Consolidated Software Distribution on CDROM.e   YEAR 2000 READYi    This product is Year 2000 Ready.  E Year 2000 Ready is defined: "Year 2000 Ready" products are defined by C Compaq as products capable of accurately processing, providing, and D /or receiving date data from, into and between the twentieth and theC twenty-first centuries, and the years 1999 and 2000, including leapg        "                                 12 b    e  D year calculations, when used in accordance with the associated prod-D uct documentation and provided that all hardware, firmware and soft-C ware used in combination with such products properly exchange accu-i! rate date data with the products.   C For additional information visit the DIGITAL Brand area on Compaq's D Year 2000 Ready web site located at http://www1.digital.com/year2000 /warranty.asp.   SOFTWARE WARRANTYn  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.s   ORDERING INFORMATION  C Listed below is the ordering information for the ACMSxp Developmentc and Runtime offerings.  C ___________________________________________________________________hC Development________________________________________________________m  ( Licenses                     QL-4WRA*-**  ( Media/Documentation          QA-4WRAA-H8  ( Documentation Only           QA-4WRAA-GZ  C Product_Services_____________QT-4WRA*-**___________________________d  C ___________________________________________________________________ C Runtime____________________________________________________________   ( Licenses                     QL-4WSA*-**( Media/Documentation          QA-4WSAA-H8( Documentation Only           QA-4WSAA-GZC Runtime_Services_____________QT-4WSA*-**___________________________i    "                                 13 e    e  F *  Denotes variant fields. For additional information on available li-D    censes, services, and media, refer to the appropriate price book.  F The above information is valid at time of release. Please contact your8 local Compaq office for the most up to date information.   SOFTWARE PRODUCT SERVICESe  D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.   TRADEMARK INFORMATIONs  I Compaq and the Compaq logo are registered with the U.S. Patent and Trade-SE mark Office. ACMS, ACMSxp, OpenVMS, DECforms, DECthreads, and VAX arer* trademarks of Compaq Computer Corporation.  H All other trademarks and registered trademarks are the property of their respective holders.t  = [R]  Motif and OSF are registered trademarks of Open Software       Foundation, Inc.r  > [R]  Oracle and Oracle Rdb are registered trademarks of Oracle      Corporation.   B [R]  UNIX is a registered trademark in the United States and other?      countries licensed exclusively through X/Open Company Lim-m
      ited.  B [R]  Windows and Windows NT are registered trademarks of Microsoft      Corporation.e  %  1999 Digital Equipment Corporation.d All rights reserved.          "                                 14