       $                               COMPAQ   Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq TP Desktop Connector V3.1A       SPD 34.81.18    DESCRIPTION   F The Compaq TP Desktop Connector is a set of software products that en-F able desktop system users (clients) to access Compaq ACMS, Compaq ACM-D Sxp, or Compaq Portable TP transaction processing systems from their native desktop environment.   C There are three TP Desktop Connector options. They are packaged ac- : cording to the transaction processing system they support.  " o  TP Desktop Connector for ACMSxp    o  TP Desktop Connector for ACMS  ' o  TP Desktop Connector for Portable TP   F The following charts list the clients and network transports supported- for each of the TP Desktop Connector options:    TP Desktop Connector for ACMSxp C ___________________________________________________________________ C Clients_________________Networks___________________________________    Windows 95[TM]          TCP/IP
 Windows 98  C Windows_NT[R]___________TCP/IP_____________________________________   C                                                         August 1999   C                                                         AE-PG9JU-TE         TP Desktop Connector for ACMS C ___________________________________________________________________ C Clients_________________Networks___________________________________    Microsoft[R] Win-       DECnet dows[R]                 TCP/IP DOS                     IPX/SPX                          X.25   Windows 95              DECnet Windows 98              TCP/IP   Windows NT              DECnet                         TCP/IP   Macintosh[R]            TCP/IP                         Dial-in    Compaq Tru64 UNIX       DECnet                         TCP/IP   Compaq OpenVMS          DECnetC ________________________TCP/IP_____________________________________   $ TP Desktop Connector for Portable TPC ___________________________________________________________________ C Clients_________________Networks___________________________________    Windows 95              TCP/IP
 Windows 98  C Windows_NT______________TCP/IP_____________________________________   F The TP Desktop Connector options include one or more UNSUPPORTED soft-D ware components, which are clearly identified in this Software Prod-D uct Description. These software components are included because theyC may be useful for the user; however, they are not supported by Com- D paq Customer Service Centers. Inclusion of these software components    "                                  2       D does not constitute a commitment from Compaq that they will continue to be provided in this product.   C Certain third-party products can be used in conjunction with the TP D Desktop Connector options and are mentioned in this SPD. Third-partyC products such as those listed are not provided by this product, nor , are they directly supported by this product.  E In general, Compaq does not directly support any third-party products C for use with the TP Desktop Connector options. However, appropriate D versions of certain third-party products have been tested and certi-G fied to be appropriate for use with this product. The Optional Software ; section of this document contains a list of these products.   ' Features: TP Desktop Connector for ACMS   / Features are described for the following areas:    o  Development environment   o  Runtime system    o  Network support   o  Management and control    o  Documentation   Development Environment   C The TP Desktop Connector for ACMS option provides a set of applica- C tion programming interfaces, along with support libraries, that al- C low software programs to interact with ACMS applications as authen- C ticated clients. These interfaces allow programmers to write client E programs without requiring extensive knowledge of programming ACMS or  network communications.   F The TP Desktop Connector for ACMS option provides application program-C ming interfaces for the Microsoft Windows, DOS, Windows 95, Windows F 98, Windows NT, Macintosh, OpenVMS, and Tru64 UNIX environments. TheseF client services allow the desktop programmer to develop programs that:  "                                  3       C o  Sign in to the TP Desktop Connector gateway for client authenti- 	    cation   D o  Select ACMS tasks for execution under the control of the ACMS Ex-    ecution Controller   E o  Respond to callbacks from the ACMS system as part of ACMS task ex- "    change steps (forms processing)  / o  Sign out of the TP Desktop Connector gateway   : There are five different programming interfaces available:  
 o  Automation   
 o  C-language    o  Java[TM]    o  Client Services    o  Client Services for Macintosh   Automation Interface  C The Automation interface supports any desktop tool or Microsoft Of- F fice product that supports Automation. ACMS tasks are presented as Au- tomation objects.                         "                                  4        C-language Interface  E The C-language interface supports any desktop tools that support a C- D callable interface. ACMS TP tasks are presented as callable C proce- dures.   Java Interface  E The Java interface supports any desktop tools that support Java. ACMS ' TP tasks are presented as Java objects.    Client Services Interface   F The portable client interface provides support for three models of ap- plication development:  D o  Blocking interface where execution of the program is blocked dur-C    ing execution of the TP Desktop Connector gateways, for example,     Microsoft COBOL on DOS.  C o  Nonblocking event-driven interface to accommodate such nonblock- 5    ing environments as Motif[R] or Microsoft Windows.   F o  Forced nonblocking that facilitates exchange I/O between ACMS tasks4    and desktop tools that do not support call backs.  C The services provided by the portable client for Microsoft Windows, D Windows 95, Windows 98, Windows NT, DOS, Tru64 UNIX, and OpenVMS ad- dress the areas of:   9 o  Sign in/out services-establish and terminate sessions.   A o  Call processing services-send and receive application requests   G o  Presentation procedure routines-called automatically by the portable G    client to facilitate forms processing for the desktop user (not sup- /    ported in a forced nonblocking environment).   ' Client Services for Macintosh Interface   D This API supports the Data Access Manager (DAM) facility of the Mac-D intosh operating system. A special DAM device driver (DDEV) provides services for client execution.  "                                  5       F These services are synchronous; program control returns only when ser-C vice execution is complete. Nonblocking task execution is supported C because the DBExec service completes as soon as the task is submit- G ted for execution to ACMS. The DBState service is used to poll for task  completion.    Runtime System  C Client runtime libraries are provided for the client operating sys- C tems to support the execution of client programs that use the prod- D uct's services. The client for Macintosh includes external functions0 for HyperCard and 4th DIMENSION[R] applications.                                                        "                                  6       C The TP Desktop Connector gateway is an asynchronous, multithreaded, E runtime component residing on any OpenVMS node, regardless of the lo- E cation of ACMS applications being called by desktop clients. There is G generally one gateway on a node. The gateway is an ACMS agent that per-  forms the following functions:  3 o  Authenticates desktop clients (ACMS submitters).   E o  Calls tasks for users; this can include local and remote ACMS task 
    selection.   C o  Communicates with the desktop client program as part of task ex- E    change step (desktop presentation procedure) execution. This func- D    tion is supported by only the client services and client services    for Macintosh interfaces.  C o  Provides information to the system manager concerning TP Desktop <    Connector submitters (For Client Servers interface only).   Network Support   C The following network connectivity software is supported (see Soft- C ware Requirements) for desktop nodes connected to a Local Area Net- ( work (LAN) or a Wide Area Network (WAN):   o  AppleTalk[R]   	 o  DECnet   
 o  IPX/SPX  	 o  TCP/IP    o  X.25   F Note: For OpenVMS clients, a communication module is provided for test8 purposes for Novell[R] NetWare[R] but it is UNSUPPORTED.      "                                  7        Management and Control  C The TP Desktop Connector supports the following management and con-  trol features:  D o  The client interface reports errors from ACMS back to the desktop+    client program for local error handling.   G o  The client interface optionally logs error messages to a local desk-     top device file.   C o  Messages can be protected against sabotage or network corruption E    by adding Cyclic Redundancy Checking (CRC) for the client services 5    and client services for Macintosh interfaces only.   G o  The gateway reports ACMS and desktop client errors to the ACMS soft-     ware event logger.                                               "                                  8       D o  OpenVMS system managers can control desktop client access to ACMSG    and remove desktop clients from the ACMS system, using standard ACMS 
    utilities.   D o  Provides a graphical user interface to manage parameters required%    for communication with ACMS tasks.   
 Documentation   C The TP Desktop Connector for ACMS documentation set consists of the 
 following:  . o  Compaq TP Desktop Connector Getting Started  : o  Compaq TP Desktop Connector for ACMS Installation Guide  $ o  TPware Management GUI online help   o  STDL online help   # o  Client Build Utility online help   C o  Compaq TP Desktop Connector for ACMS Client Application Program- 
    ming Guide   @ o  Compaq TP Desktop Connector for ACMS Gateway Management Guide  F o  Compaq TP Desktop Connector for ACMS Client Services Reference Man-    ual  9 o  Compaq TP Desktop Connector Version 3.1A Release Notes   5 o  4th DIMENSION Externals User's Guide (online only)   + Compaq TP Desktop Connector Getting Started   H The TP Desktop Connector Getting Started document describes how to buildC and manage client applications that use the Automation, C-language,  and Java interfaces.  7 Compaq TP Desktop Connector for ACMS Installation Guide   "                                  9       D The TP Desktop Connector for ACMS Installation Guide provides infor-E mation about installing the TP Desktop Connector for ACMS product and  sample client applications.   ! TPware Management GUI online help   C The TPware Management GUI online help describes the management tabs > that the Management GUI provides for managing TPware products.   STDL online help  E The STDL online help provides reference topics on X/Open STDL syntax.     Client Build Utility online help  E The Client Build GUI online help describes a graphical user interface 8 that makes it easier to create Automation and C clients.                                              "                                 10       C Compaq TP Desktop Connector for ACMS Client Application Programming  Guide   F The TP Desktop Connector for ACMS Client Application Programming GuideG describes how to develop and test client programs. It includes detailed F information on components and functions, design and development guide-! lines, and interface information.   = Compaq TP Desktop Connector for ACMS Gateway Management Guide   C The TP Desktop Connector for ACMS Gateway Management Guide contains D the information needed to manage the gateway on the system where theC ACMS monitor resides and information on the network transports that  can be used.  C Compaq TP Desktop Connector for ACMS Client Services Reference Man-  ual   E The TP Desktop Connector for ACMS Client Services Reference Manual is D a companion document to the Application Programming and Gateway Man-F agement Guides. The document contains a description of the client ser-" vices and presentation procedures.  6 Compaq TP Desktop Connector Version 3.1A Release Notes  F Release Notes (available online as part of the media kit) contains in-G formation specific to this release and information added after the pro- - duction date for the other product documents.   $ 4th DIMENSION Externals User's Guide  E 4th DIMENSION Externals User's Guide (available online as part of the C media kit, on the Macintosh) contains information on how to use the  Externals with 4th DIMENSION.             "                                 11       @ Features: TP Desktop Connector for ACMSxp & TP Desktop Connector for Portable TP   / Features are described for the following areas:    o  Development environment   o  Runtime system    o  Network support   o  Management and control    o  Documentation   Development Environment   I The TP Desktop Connector for ACMSxp and TP Desktop Connector for Portable E TP options provide a set of application programming interfaces, along E with support libraries, that allow software programs to interact with C ACMSxp or Portable TP applications as clients. These interfaces al- D low programmers to write client programs without requiring extensiveC knowledge of programming ACMSxp, Portable TP, or network communica-  tions.                                "                                 12       D Application programming interfaces are provided for Windows 95, Win-D dows 98, and Windows NT environments. The programming interfaces al-D low the desktop programmer to develop programs that select ACMSxp orC Portable TP tasks for execution. The application programming inter- 
 faces are:  
 o  Automation   
 o  C-language    o  Java    Automation Interface  C The Automation interface supports any desktop tool or Microsoft Of- F fice product that supports Automation. ACMSxp or Portable TP tasks are  presented as Automation objects.   C-language Interface  E The C-language interface supports any desktop tools that support a C- I callable interface. ACMSxp or Portable TP tasks are presented as callable 
 C procedures.    Java Interface  E The Java interface supports any desktop tools that support Java. ACM- 7 Sxp or Portable TP tasks are presented as Java objects.    Runtime System  G Runtime libraries are provided for the client operating systems to sup- & port the execution of client programs.   Network Support   - TCP/IP is supported for network connectivity.       "                                 13        Management and Control  C The TP Desktop Connector supports the following management and con-  trol features:  C o  ACMSxp and Portable TP servers report back to the desktop client $    program for local error handling.  D o  The desktop client program can optionally log error messages to a    local desktop device file.   C o  The server for ACMSxp and Portable TP outputs error reports to a 1    server-specific log file on the server system.   F o  ACMSxp and DCE management and security services can be used to con-    trol clients.  D o  Provides a graphical user interface to manage parameters required6    for communication with ACMSxp or Portable TP tasks.  . Documentation: TP Desktop Connector for ACMSxp  E The documentation set for TP Desktop Connector for ACMSxp consists of  the following:  . o  Compaq TP Desktop Connector Getting Started  < o  Compaq TP Desktop Connector for ACMSxp Installation Guide  $ o  TPware Management GUI online help   o  STDL online help   # o  Client Build Utility online help   9 o  Compaq TP Desktop Connector Version 3.1A Release Notes   + Compaq TP Desktop Connector Getting Started   H The TP Desktop Connector Getting Started document describes how to buildC and manage client applications that use the Automation, C-language,  and Java interfaces.  9 Compaq TP Desktop Connector for ACMSxp Installation Guide   "                                 14       C The TP Desktop Connector for ACMSxp Installation Guide provides in- D formation about installing the TP Desktop Connector for ACMSxp prod-B uct on desktop systems and configuring sample client applications.  ! TPware Management GUI online help   C The TPware Management GUI online help describes the management tabs > that the Management GUI provides for managing TPware products.   STDL online help  E The STDL online help provides reference topics on X/Open STDL syntax.     Client Build Utility online help  E The Client Build GUI online help describes a graphical user interface 8 that makes it easier to create Automation and C clients.  6 Compaq TP Desktop Connector Version 3.1A Release Notes  F The Release Notes (available online as part of the media kit) containsD information specific to this release and information added after the0 production date for the other product documents.  3 Documentation: TP Desktop Connector for Portable TP   C The documentation set for TP Desktop Connector for Portable TP con-  sists of the following:   . o  Compaq TP Desktop Connector Getting Started  A o  Compaq TP Desktop Connector for Portable TP Installation Guide   $ o  TPware Management GUI online help   o  STDL online help   # o  Client Build Utility online help   9 o  Compaq TP Desktop Connector Version 3.1A Release Notes   + Compaq TP Desktop Connector Getting Started   "                                 15       H The TP Desktop Connector Getting Started document describes how to buildC and manage client applications that use the Automation, C-language,  and Java interfaces.  > Compaq TP Desktop Connector for Portable TP Installation Guide  D The TP Desktop Connector for Portable TP Installation Guide providesE information about installing the TP Desktop Connector for Portable TP F product on desktop systems and configuring sample client applications.  ! TPware Management GUI online help   C The TPware Management GUI online help describes the management tabs > that the Management GUI provides for managing TPware products.   STDL online help  E The STDL online help provides reference topics on X/Open STDL syntax.     Client Build Utility online help  E The Client Build GUI online help describes a graphical user interface 8 that makes it easier to create Automation and C clients.  6 Compaq TP Desktop Connector Version 3.1A Release Notes  F The Release Notes (available online as part of the media kit) containsD information specific to this release and information added after the0 production date for the other product documents.  4 HARDWARE REQUIREMENTS: TP Desktop Connector for ACMS   Servers, and Client for OpenVMS   F o  Any Alpha hardware configuration that supports OpenVMS Version 6.2,    7.1, or 7.2  D o  Any VAX hardware configuration that supports OpenVMS Version 5.5-    2, 6.2, 7.1, or 7.2  "                                 16       $ Client for Microsoft Windows and DOS  D o  An Intel[R] 80386-, 80486-, or Pentium[R]-based personal computer  D o  A minimum of 640KB system memory. At least 1 megabyte is stronglyD    recommended. For Microsoft Windows client applications at least 4    megabytes is required.   # Client for Windows 95 or Windows 98   C o  Intel 80386-, 80486-, or Pentium-based system capable of running     Windows 95 or Windows 98.   Client for Windows NT   C o  Intel 80386-, 80486-, or Pentium-based system capable of running     Windows NT or,   4 o  Alpha-based system capable of running Windows NT.   Client for Macintosh  E o  Any Macintosh computer capable of running the supported version of "    the Macintosh Operating System.  < o  Power Macintosh computers using Macintosh emulation mode.  ; HARDWARE REQUIREMENTS: TP Desktop Connector for ACMSxp & TP ! Desktop Connector for Portable TP   # Client for Windows 95 or Windows 98   C o  Intel 80386-, 80486-, or Pentium-based system capable of running     Windows 95 or Windows 98.            "                                 17        Client for Windows NT   C o  Intel 80386-, 80486-, or Pentium-based system capable of running     Windows NT or,   4 o  Alpha-based system capable of running Windows NT.  4 SOFTWARE REQUIREMENTS: TP Desktop Connector for ACMS   OpenVMS Server  F o  If using client services interface, ACMS for OpenVMS Versions 3.3B-    4.2-2 (SPD 25.50.xx)   D o  If using Automation, C-language, or Java interfaces, ACMS Version#    4.2-2 for OpenVMS (SPD 25.50.xx)    o  If using DECnet:   4    -  DECnet-VAX Versions 5.5-6.1 (SPD 48.48.xx) or,  =    -  DECnet for OpenVMS Alpha Version 6.1 (SPD 42.25.xx) or,   A    -  DECnet for OpenVMS VAX and Alpha Version 6.2 (SPD 48.48.xx)   C o  If using PATHWORKS or AppleTalk, reference the PATHWORKS Version E    6.0A for DOS and Windows SPD for that client for specific software     requirements    o  If using TCP/IP:   G    -  Compaq TCP/IP Services for OpenVMS Version 4.0-4.2 (SPD 46.46.xx) 	       or,   '    -  TGV MultiNet[R] Version 3.3 Rev A   F o  If using NetWare, an IPX stack must be installed on the server sys-G    tem; this is available as software services within the Leverage Host <    Services Version 4.0 product from Emulex[TM] Corporation.  J o  If using X.25, PATHWORKS Version 6.0 for DOS and Windows (SPD 55.07.xx)  "                                 18       $ Client for Microsoft Windows and DOS   o  Microsoft DOS Version 6.22   D o  Microsoft Windows Version 3.1 or Microsoft Windows for Workgroups    Version 3.11   C o  If using DECnet, PATHWORKS for DOS and Windows Version 6.0A (SPD     55.07.xx)   o  If using TCP/IP:   C    -  Microsoft Windows requires PATHWORKS for DOS and Windows Ver-        sion 6.0A (SPD 55.01.xx)  D    -  Microsoft Windows for Workgroups include the necessary Windows
       Sockets   C o  If using NetWare, Novell's NetWare DOS Client Versions 3.x, 4.0, 0    or PATHWORKS Version 6.0A for DOS and Windows  K o  If using X.25, PATHWORKS Version 6.0A for DOS and Windows (SPD 55.07.xx)   # Client for Windows 95 or Windows 98   . o  Windows 95 Version 4.00.950 B or Windows 98  E o  If using Automation, C-language, or Java interfaces, Visual C++[R] .    Version 5.0 (required for development only)  5 o  If using the Java interface, one of the following:   F    -  Sun Microsystems Java Development Kit (JDK) Version 2.0 or later  =    -  Microsoft SDK for Java Version 3.1, build 3167 or later   < o  If using DECnet, PATHWORKS 32 Version 7.0A (SPD 56.33.xx)  C o  If using TCP/IP, Windows sockets are provided with Windows 95 or 
    Windows 98   "                                 19        Client for Windows NT   = o  Windows NT operating system Version 4.0 for Alpha or Intel   7 o  If using Automation, C-language, or Java interfaces:   0    -  Windows NT Version 4.0 with Service Pack 4      -  Visual C++ Version 5.0  5 o  If using the Java interface, one of the following:   F    -  Sun Microsystems Java Development Kit (JDK) Version 2.0 or later  =    -  Microsoft SDK for Java Version 3.1, build 3167 or later   < o  If using DECnet, PATHWORKS 32 Version 7.0A (SPD 56.33.xx)  F o  If using TCP/IP, Windows NT Windows Sockets for TCP/IP are provided    with Windows NT   Client for Macintosh  . o  Macintosh Operating System Versions 7.0-7.5  E o  If using TCP/IP, MacTCP[R] Tool (available from Apple[R] Computer,     Inc.)  G o  If using dial-in (serial communication), a serial communication tool A    is needed (for example: Serial Tool from Apple Computer, Inc.)    Client for OpenVMS  E o  OpenVMS VAX Operating System Versions 5.5-2, 6.2, 7.1, or 7.2 (SPD D    25.01.xx) or OpenVMS Alpha Operating System Versions 6.2, 7.1, or    7.2 (SPD 41.87.xx)    o  If using DECnet:   4    -  DECnet-VAX Versions 5.5-6.1 (SPD 48.48.xx) or,  9    -  DECnet for OpenVMS Alpha Version 6.1 (42.25.xx) or,   "                                 20       A    -  DECnet for OpenVMS VAX and Alpha Version 6.2 (SPD 48.48.xx)    o  If using TCP/IP:   K    -  Compaq TCP/IP Services for OpenVMS VAX Version 4.0-4.2 (SPD 25.A4.xx) 	       or,   C    -  Compaq TCP/IP Services for OpenVMS Alpha Version 4.0-4.2 (SPD        46.46.xx) or,   $    -  TGV MultiNet Version 3.3 Rev A   Client for Tru64 UNIX   : o  Tru64 UNIX Operating System Version 4.0B (SPD 41.61.xx)  E o  If using TCP/IP, all components are provided by the Tru64 UNIX op-     erating system   ; SOFTWARE REQUIREMENTS: TP Desktop Connector for ACMSxp & TP ! Desktop Connector for Portable TP   
 ACMSxp Server   . At least one of the following ACMSxp products:  7 o  ACMSxp Version 3.1 or 3.2 for OpenVMS (SPD 60.53.xx)   : o  ACMSxp Version 3.1 or 3.2 for Windows NT (SPD 60.52.xx)  : o  ACMSxp Version 3.1 or 3.2 for Tru64 UNIX (SPD 50.66.xx)  1 o  ACMSxp Version 3.1 for HP-UX[R] (SPD 70.15.xx)   2 o  ACMSxp Version 3.1 for Solaris[R] (SPD 70.35.xx   Portable TP Server  5 Portable TP Version 2.0 for Windows NT (SPD 70.26.xx)   "                                 21       # Client for Windows 95 or Windows 98   . o  Windows 95 Version 4.00.950 B or Windows 98  9 o  Visual C++ Version 5.0 (required for development only)   5 o  If using the Java interface, one of the following:   F    -  Sun Microsystems Java Development Kit (JDK) Version 2.0 or later  =    -  Microsoft SDK for Java Version 3.1, build 3167 or later   4 o  DCOM for Windows 95 or Windows 98, available from    www.microsoft.com/com   Client for Windows NT   - o  Windows NT Version 4.0 with Service Pack 4   9 o  Visual C++ Version 5.0 (required for development only)   5 o  If using the Java interface, one of the following:   F    -  Sun Microsystems Java Development Kit (JDK) Version 2.0 or later  =    -  Microsoft SDK for Java Version 3.1, build 3167 or later   E o  If using DCE, Compaq DCE Runtime Services Version V2.0 for Windows      NT Alpha/Intel (SPD 53.43.xx)  C o  If using Microsoft RPC, all components are provided with the op-     erating system   D o  Required for development only, Compaq DCE Application Developer's<    Kit Version 2.0 for Windows NT Alpha/Intel (SPD 53.43.xx)   SOFTWARE LICENSING INFORMATION  F All TP Desktop Connector options offer Concurrent Use and Personal Use
 licensing.  C o  Concurrent Use Licensing - The number of Concurrent Use licenses D    determines the number of concurrent logins to any TP application.  "                                 22       D    This style of licensing works best and is the most cost effectiveD    for deployments where users primarily login to only one TP appli-    cation at a time.  C o  Personal Use Licensing - The number of Personal Use licenses de- F    termines the numbers of identified individuals that can access mul-F    tiple TP applications. The main difference between Personal Use andF    Concurrent Use licensing is that Personal Use license permits iden-F    tified individuals to login to multiple TP applications at the sameD    time. This style of licensing works best and is the most cost ef-E    fective for deployments where users require simultaneous to access     multiple TP applications.  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 (LMF)   E The TP Desktop Connector for ACMS option supports the OpenVMS License D Management Facility. License units for this product are allocated on' a Concurrent Use or Personal Use basis.   C A Concurrent Use license allows one login to a TP Desktop Connector  gateway.  D A Personal Use license allows one identified individual to have mul-6 tiple logins to the same TP Desktop Connector gateway.  E For more information on the License Management Facility, refer to the D OpenVMS Operating System Software Product Description (SPD 25.01.xx)G or the License Management Facility manual of the OpenVMS Operating Sys-  tem documentation set.  E For more information about the Compaq's licensing terms and policies, ! contact your local Compaq office.         "                                 23       2 CLUSTER ENVIRONMENT: TP Desktop Connector for ACMS  C This layered product is fully supported when installed on any valid E and licensed VMScluster configuration without restrictions. The HARD- F WARE REQUIREMENTS sections of this product's Software Product Descrip-; tion details any special hardware required by this product.   E VMScluster configurations are fully described in the VMScluster Soft- E ware Product Description (SPD 29.78.xx) and include CI, Ethernet, and " Mixed Interconnect configurations.                                                            "                                 24       0 OPTIONAL SOFTWARE: TP Desktop Connector for ACMS  $ Client for Microsoft Windows and DOS  E o  A program module assembler to create the DOS programming libraries C    and other libraries that create a client program. Assemblers are     available from Microsoft.  ? o  C compiler compatible with Microsoft Visual C++ Version 1.52   C o  Microsoft COBOL Version 5.0 (Microsoft Corporation). MS[R]-COBOL D    is required to modify and relink the command line sample applica-    tion for DOS.  F o  Microsoft Windows Software Development Kit Version 3.1 or 3.11 (Mi-    crosoft Corporation)   6 o  Visual Basic[R] Version 4.0 (Microsoft Corporation)  6 o  PowerBuilder[R] Version 5.0 (Powersoft Corporation)  $ o  SQLWindows[R] (Gupta Corporation)  , o  Smalltalk[R] (ParcPlace[R] Systems, Inc.)   o  JAM[R] (JYACC)   ( o  OpenUI[TM] (Open Software Associates)  # Client for Windows 95 or Windows 98   C o  If using the Automation interface, any desktop tool or Microsoft *    Office product that supports Automation  C o  If using the Java interface, any Java Integrated Development En- D    vironment (IDE) compatible with Sun Microsystems JDK Version 2.0,4    or Microsoft SDK for Java Version 3.1, build 3167  D o  If using the C-language interface, any desktop tool that supports    a C-callable interface.  "                                 25       * o  If using the client services interface:  &    -  Visual Basic Versions 4.0 or 5.0  <    -  Visual C++ Versions 4.0 or 5.0 (Microsoft Corporation)      -  PowerBuilder Version 5.0  =    -  Delphi[TM] Version 2.0 (Borland[R] International, Inc.)   9    -  Developer/2000[TM] Release 2.0 (Oracle Corporation)    Client for Windows NT   C o  If using the Automation interface, any desktop tool or Microsoft *    Office product that supports Automation  C o  If using the Java interface, any Java Integrated Development En- D    vironment (IDE) compatible with Sun Microsystems JDK Version 2.0,4    or Microsoft SDK for Java Version 3.1, build 3167  D o  If using the C-language interface, any desktop tool that supports    a C-callable interface.  * o  If using the client services interface:  &    -  Visual Basic Versions 4.0 or 5.0  $    -  Visual C++ Versions 4.0 or 5.0      -  Smalltalk       -  PowerBuilder Version 5.0      -  Delphi Version 2.0       -  Developer/2000 Release 2.0      "                                 26        Client for Macintosh  & o  HyperCard[R] (Apple Computer, Inc.)  , o  Macintosh Programmer's Workshop (MPW[TM])B    Development Environment Versions 3.2-3.3 (Apple Computer, Inc.)  G o  Macintosh Programmer's Workshop C Version 3.1 (Apple Computer, Inc.)   / o  4th DIMENSION Versions 2.3-3.1 (ACI US Inc.)    o  Smalltalk  ) o  Open Interface[TM] (Neuron Data, Inc.)   4 o  Think C Version 4.0-4.1 (Symantec[R] Corporation)   Client for OpenVMS   VAX   & o  DECforms Version 2.2 (SPD 29.90.xx)  6 o  Compaq C for OpenVMS VAX Version 5.7 (SPD 25.38.xx)  B o  Compaq DECset Release 11 for OpenVMS VAX Systems (SPD 27.07.xx)  : o  DECwindows Motif Version 1.1 for OpenVMS (SPD 42.19.xx)   Alpha   & o  DECforms Version 2.2 (SPD 29.90.xx)  @ o  Compaq C Version 1.2 for OpenVMS Alpha Systems (SPD 42.26.xx)  D o  Compaq DECset Release 11 for OpenVMS Alpha Systems (SPD 42.29.xx)  @ o  DECwindows Motif Version 1.1 for OpenVMS Alpha (SPD 42.19.xx)    "                                 27        Client for Tru64 UNIX   7 o  Compaq C++ Version 5.4 for Tru64 UNIX (SPD 41.91.xx)   ? OPTIONAL SOFTWARE: TP Desktop Connector for ACMSxp & TP Desktop  Connector for Portable TP   C o  If using the Automation interface, any desktop tool or Microsoft *    Office product that supports Automation  C o  If using the Java interface, any Java Integrated Development En- D    vironment (IDE) compatible with Sun Microsystems JDK Version 2.0,4    or Microsoft SDK for Java Version 3.1, build 3167  D o  If using the C-language interface, any desktop tool that supports    a C-callable interface.   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  , All product options are available on CD-ROM.  E The TP Desktop Connector for ACMS option is also available as part of / the OpenVMS Software Product Library on CD-ROM.   E The documentation for TP Desktop Connector for ACMS is also available > as part of the OpenVMS Online Documentation Library on CD-ROM.                "                                 28        YEAR 2000 READY     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 leap 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- ! rate date data with the products.   C For additional information visit the DIGITAL Brand area on Compaq's C Year 2000 Ready web site located at http://ww1.digital.com/year2000  /warranty.asp.  C To ensure that this product is Year 2000 Ready, the following test- " ing process/methods were utilized:  D    This product does not require specific Year 2000 testing since no"    date manipulation is performed.  C To ensure that this product interoperates properly with other hard- G ware and software, the following testing process/methods were utilized:   C    This product does not require Year 2000 interoperability testing 2    since date data is passed without manipulation.   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.             "                                 29        ORDERING INFORMATION   TP Desktop Connector for ACMS C ___________________________________________________________________ C _____________________________Part_Number___________________________   ( Concurrent Use License       QL-GZGAL-3*  ( Personal Use License         QL-GZGAL-2B  ( Media & Documentation        QA-GZGAA-H8 (CD-ROM)  ( Documentation Only           QA-GZGAA-GZ  C Services_____________________QT-GZG**-**___________________________    TP Desktop Connector for ACMSxp C ___________________________________________________________________ C _____________________________Part_Number___________________________   ( Concurrent Use License       QL-644AL-3*  ( Personal Use License         QL-644AL-2B  ( Media & Documentation        QA-644AA-H8 (CD-ROM)  ( Documentation Only           QA-644AA-GZ  C Services_____________________QT-644**-**___________________________                   "                                 30       $ TP Desktop Connector for Portable TPC ___________________________________________________________________ C _____________________________Part_Number___________________________   ( Concurrent Use License       QL-645AL-3*  ( Personal Use License         QL-645AL-2B  ( Media & Documentation        QA-645AA-H8 (CD-ROM)  ( Documentation Only           QA-645AA-GZ  C Services_____________________QT-645**-**___________________________   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 yourC local Compaq office or Business Partner for the most up-to-date in- 
 formation.   SOFTWARE PRODUCT SERVICES   D A variety of service options are available from Compaq. For more in-+ formation contact your local Compaq office.    TRADEMARK INFORMATION   I Compaq and the Compaq logo are registered with the U.S. Patent and Trade- E mark Office. ACMS, ACMSxp, DECforms, DECnet, DECset, DECwindows, DIG- C ITAL, OpenVMS, PATHWORKS, and VAX are trademarks of Compaq Computer  Corporation.  H All other trademarks and registered trademarks are the property of their respective holders.   ; [R]  4th DIMENSION is a registered trademark of ACI US Inc.     "                                 31         B [R]  Apple, AppleTalk, HyperCard, Macintosh, and MacTCP are regis--      tered trademarks of Apple Computer, Inc.   @ [R]  Borland is a registered trademark of Borland International,	      Inc.   ; [R]  Emulex is a registered trademark of Emulex Corporation   A [R]  Hayes is a registered trademark of Hayes Microcomputer Prod-       ucts, Inc.   @ [R]  HP-UX is a registered trademark of Hewlett-Packard Corpora-
      tion.  , [R]  JAM is a registered trademark of JYACC.  > [R]  Microsoft, MS, SQLWindows, Visual Basic, Visual C++, Win-@      dows, and Windows NT are registered trademarks of Microsoft      Corporation.   B [R]  MultiNet is a registered trademark of Process Software Corpo-      ration   A [R]  Motif is a registered trademark of Open Software Foundation, 	      Inc.   6 [R]  NetWare is a registered trademark of Novell, Inc.  A [R]  PowerBuilder is a registered trademark of Powersoft Corpora- 
      tion.  ? [R]  Smalltalk and ParcPlace are registered trademarks of Parc-       Place Systems, Inc.  @ [R]  Solaris is a registered trademark of Sun Microsystems, Inc.  B [R]  UNIX is a registered trademark in the United States and other?      countries licensed exclusively through X/Open Company Lim- 
      ited.  B [R]  Intel and Pentium are registered trademarks of Intel Corpora-
      tion.  9 [TM] Delphi is a trademark of Borland International, Inc.   8 [TM] Developer/2000 is a trademark of Oracle Corporation  2 [TM] Java is a trademark of Sun Microsystems, Inc.  / [TM] MPW is a trademark of Apple Computer, Inc.   "                                 32         7 [TM] Open Interface is a trademark of Neuron Data, Inc.   7 [TM] OpenUI is a trademark of Open Software Associates.   %  1999 Digital Equipment Corporation.  All rights reserved.                                                                  "                                 33