                                     0                      Compaq TP Desktop ConnectorC                      for_ACMS______________________________________ '                      Installation Guide   .                      Order Number: AA-PG9DJ-TE                         August 1999      H                      This document provides information about installingH                      the Compaq TP Desktop Connector software on desktopH                      systems, and about installing the Compaq TP DesktopC                      Connector Gateway for ACMS software on systems D                      running the Compaq OpenVMS operating system andG                      Compaq ACMS software. It also describes activities E                      associated with these installations, such as the ,                      verification procedure.          C                      Revision/Update Information: This is a revised 9                                                   manual.   C                      Software Version:            Compaq TP Desktop ;                                                   Connector G                                                   Version 3.1A for ACMS   0                      Compaq Computer Corporation#                      Houston, Texas                  E            __________________________________________________________             August 1999  C            The information in this publication is subject to change             without notice.  >            COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR?            TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED >            HEREIN, NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES@            RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OFB            THIS MATERIAL. THIS INFORMATION IS PROVIDED "AS IS" AND@            COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES,B            EXPRESS, IMPLIED, OR STATUTORY, AND EXPRESSLY DISCLAIMSA            THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR D            PARTICULAR PURPOSE, GOOD TITLE, AND AGAINST INFRINGEMENT.  =            This publication contains information protected by D            copyright. No part of this publication may be photocopiedB            or reproduced in any form without prior written consent,            from Compaq Computer Corporation.  E             1999 Digital Equipment Corporation. All Rights Reserved.   D            The software described in this guide is furnished under aE            license agreement or nondisclosure agreement. The software E            may be used or copied only in accordance with the terms of             the agreement.   B            Compaq and the Compaq logo are registered in the United.            States Patent and Trademark Office.  C            ACMS, ACMS Desktop, ACMSxp, ACMSxp Desktop, AlphaServer, E            AltaVista, DEC, DECnet, DECthreads, DIGITAL, OpenVMS, VAX, A            and VMS are trademarks of Compaq Computer Corporation.   @            Intel is a registered trademark of Intel Corporation.  @            Java, JavaScript, and JavaBeans are trademarks of Sun            Microsystems, Inc.   A            Microsoft, Microsoft Access, MS, MS-DOS, Visual Basic, >            Visual C++, Windows, Windows 95, and Windows NT are>            registered trademarks and ActiveX is a trademark of!            Microsoft Corporation.   B            Oracle is a registered trademark of Oracle Corporation.  A            UNIX and X/Open are registered trademarks and The Open ?            Group is a trademark of The Open Group in the United &            States and other countries.  A            Other product names mentioned herein may be trademarks ;            and/or registered trademarks of their respective             companies.   @            This document was prepared using DECdocument, Version            3.2-1n.                               C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................     ix     1    Part I  Using the Software Products Library CD   5    1  Before Installing TP Desktop Connector from the "       Software Products Library CD  8          1.1   Overview of the Software Products LibraryC                Installation.................................    1-1 C          1.2   Software and Hardware Prerequisites..........    1-2 C          1.3   Installation Procedure Requirements..........    1-3   7    2  Installing TP Desktop Connector from the Software        Products Library CD   :          2.1   Installing the TP Desktop Connector GatewayC                for ACMS Software............................    2-1 C          2.2   Installing the Client Kit....................    2-2   <    3  After Installing from the Software Products Library CD  C          3.1   After Installing the Gateway Kit.............    3-1 ;          3.2   After Installing TP Desktop Connector Client C                Kit..........................................    3-1 C          3.2.1     Editing Startup Files....................    3-2 C          3.2.2     After Installing Non-VMS Clients.........    3-2 9          3.2.2.1     Transfering Client Files to a 32-bit C                      Microsoft System.......................    3-3 9          3.2.2.2     Transfering Client Files to a 16-bit C                      Microsoft System.......................    3-5       C                                                                 iii                  :            3.2.2.3     Transfering Client Files to a Tru64E                        UNIX System............................    3-6 =            3.2.3     Installing the Client Services Interface E                      on OpenVMS Systems.......................    3-7 9            3.2.4     Verifying the Motif Client Sample on E                      OpenVMS..................................    3-8 >            3.3   Setting Up the Avertz ACMS Sample ApplicationE                  on an OpenVMS System.........................    3-9 :            3.3.1     Using the Avertz ACMS Sample with RdbE                      Version 6.0 with Multiversion............   3-10 9            3.3.2     Building the Avertz ACMS Sample with E                      DECforms V1.4............................   3-10 9            3.3.3     User Name Quotas for the Avertz ACMS E                      Sample...................................   3-11 <            3.3.4     Access Control List for the Avertz ACMSE                      Sample...................................   3-11 E            3.3.5     Rebuilding the Avertz ACMS Sample........   3-11     /      Part II  Using the TPware Product Suite CD   7      4  Before Installing TP Desktop Connector Software   E            4.1   Installation Overview........................    4-1 :            4.2   Preparing to Install TP Desktop ConnectorE                  Software.....................................    4-4 E            4.2.1     Product Licenses.........................    4-4 E            4.2.2     Disk Space...............................    4-4 E            4.3   Removing the Installed Software..............    4-5   9      5  Installing TP Desktop Connector Software on Win32          Systems   ;            5.1   TP Desktop Connector Software Installation E                  Procedure....................................    5-1 6            5.2   After Installing TP Desktop ConnectorE                  Software.....................................    5-2 E            5.2.1     Setting Up the TPware Environment........    5-2 E            5.2.2     Accessing the ACMS System................    5-3 ;            5.2.3     Defining the Network Transport for the E                      Client Services Interface................    5-3 7            5.2.4     Verifying the TP Desktop Connector E                      Installation.............................    5-3           iv                  7               5.2.5     Running the Win32 Sample Client H                         Applications.............................    5-4H               5.2.6     Code Conversion Libraries for Kanji......    5-6    A         6  Installing the TP Desktop Connector Client Services on             Non-Win32 Systems  3               6.1   Overview of the Client Services H                     Installation.................................    6-2H               6.1.1     Software Prerequisites...................    6-2H               6.1.2     Disk Space...............................    6-3H               6.1.3     Resources................................    6-4=               6.2   Installing the Client Services for 16-Bit H                     Microsoft Systems............................    6-5H               6.2.1     Setting Up the Client Services for DOS...    6-6@               6.2.2     Installing the Sample Client ApplicationH                         for DOS..................................    6-75               6.2.3     Verifying the Client Services H                         Installation for DOS.....................    6-7:               6.2.4     Setting Up the Client Services forH                         Windows 3.11.............................    6-8H               6.2.5     Code Conversion Libraries for Kanji......    6-9=               6.2.6     Installing the Sample Application for H                         Windows 3.11.............................    6-95               6.2.7     Verifying the Client Services H                         Installation on Windows 3.11.............   6-10:               6.2.8     Installing the PowerBuilder SampleH                         Application..............................   6-12:               6.2.9     Installing the Visual Basic SampleH                         Applications.............................   6-13;               6.2.9.1     Verifying the Visual Basic Avertz H                           Sample Installation....................   6-14:               6.2.9.2     Verifying the Forced NonblockingH                           Tutorial...............................   6-14H               6.3   Installing the Client Services for OpenVMS...   6-15>               6.3.1     Installing the Motif Sample Client forH                         OpenVMS..................................   6-17?               6.3.2     Verifying the Motif Sample Installation H                         on OpenVMS...............................   6-18          H                                                                        v                 6            6.3.3     Setting Up the Avertz ACMS SampleE                      Application on an OpenVMS System.........   6-19 <            6.3.3.1     Using the Avertz ACMS Sample with RdbE                        Version 6.0 with Multi-Version.........   6-20 ;            6.3.3.2     Building the Avertz ACMS Sample with E                        DECforms V1.4..........................   6-21 ;            6.3.3.3     User Name Quotas for the Avertz ACMS E                        Sample.................................   6-21 >            6.3.3.4     Access Control List for the Avertz ACMSE                        Sample.................................   6-22 E            6.3.3.5     Rebuilding the Avertz ACMS Sample......   6-22 E            6.4   Installing the Tru64 UNIX Client Software....   6-23 :            6.4.1     Installing the Motif Sample Client onE                      Tru64 UNIX Platforms.....................   6-25 <            6.4.2     Verifying the Motif Sample InstallationE                      on Tru64 UNIX Platforms..................   6-25     ;      7  Installing the TP Desktop Connector Client Services          for Macintosh Systems   E            7.1   Macintosh Installation Options...............    7-1 3            7.2   Preparing to Install the Macintosh E                  Software.....................................    7-3 8            7.2.1     Prerequisite Software for MacintoshE                      Systems..................................    7-3 E            7.2.2     Disk Space...............................    7-4 E            7.3   Installing the Macintosh Software............    7-5 5            7.3.1     Copying the TP Desktop Connector E                      Installer to the Macintosh...............    7-5 5            7.3.2     Running the TP Desktop Connector E                      Macintosh Installer......................    7-6   #      Part III  Using the Gateway CD                             vi                  @         8  Preparing to Install TP Desktop Connector Gateway for            ACMS Software  H               8.1   Required Operating System Components.........    8-1H               8.2   Prerequisite Software........................    8-2H               8.3   Installation Procedure Requirements..........    8-2H               8.3.1     Disk Space...............................    8-2H               8.3.2     Privileges and Authorization.............    8-3H               8.3.3     OpenVMS License Management Facility......    8-4H               8.3.4     System Disk Backup.......................    8-4H               8.3.5     Stopping the ACMS System and Gateway ....    8-5H               8.3.6     Locating the Saveset Directory...........    8-5  ;         9  Installing TP Desktop Connector Gateway for ACMS             Software   H               9.1   General Installation Information.............    9-1H               9.1.1     Accessing the Online Release Notes.......    9-1A               9.1.2     Files and Logical Names Installed on Your H                         System...................................    9-2H               9.1.3     Installation Verification Procedure......    9-2H               9.1.4     Aborting the Installation................    9-3H               9.2   Installation Procedure.......................    9-3H               9.2.1     Invoking VMSINSTAL.......................    9-3H               9.2.2     Installation Questions...................    9-4H               9.2.3     Informational Messages...................    9-8=               9.2.4     Running the Installation Verification H                         Procedure................................    9-9H               9.2.5     Completing the Installation Procedure....   9-10;               9.3   Recovering from System and Installation H                     Failures.....................................   9-10H               9.3.1     System Failures..........................   9-10H               9.3.2     Installation Failures....................   9-12H               9.3.3     IVP Error Recovery.......................   9-13  =         10  After Installing TP Desktop Connector Gateway for              ACMS Software   H               10.1  Editing the OpenVMS System Files.............   10-1H               10.1.1    Editing the System Startup File..........   10-1H               10.1.2    Editing the System Shutdown File.........   10-3H               10.2  Performing Cluster Procedures................   10-3H               10.3  Matching Client and Server Versions..........   10-4    H                                                                      vii                 >      11  Running the TP Desktop Connector Gateway for ACMS IVP  E            11.1  IVP Operations...............................   11-1 E            11.2  Running the IVP Independently................   11-1 E            11.2.1    IVP Requirements.........................   11-2 E            11.2.2    IVP Steps................................   11-2 E            11.2.3    IVP Error Recovery.......................   11-3         Part IV  Appendixes          A  Files Installed   #      B  Common Configuration Errors   E            B.1   Errors Related to the Desktop System.........    B-1 E            B.1.1     Errors on DOS or Windows 3.11 Desktops...    B-1 E            B.1.2     Errors on OpenVMS Desktops...............    B-2 E            B.1.3     Errors on Tru64 UNIX Desktops............    B-2 E            B.2   Errors Related to the ACMS System............    B-3   
      Index    
      Examples   E            2-1       Sample Client Installation...............    2-2   E            B-1       Sample startup.bat File..................    B-1e  E            B-2       Sample config.sys File...................    B-2         Tables   4            1-1       TP Desktop Connector Disk SpaceE                      Requirements.............................    1-3   6            2-1       TP Desktop Connector Files on theE                      Software Products Library CD.............    2-1n  E            3-1       Contents of ACMSDI$NONVMS_CLIENTS........    3-3P  E            3-2       VR_DA_BLD_MMS.COM Parameters.............   3-12t  9            4-1       Contents of the TPware Product SuitenE                      CD.......................................    4-3b  4            4-2       TP Desktop Connector Disk SpaceE                      Requirements.............................    4-4d  	      viii                  ;               6-1       Client Services Sample Applications H                         Software Requirements....................    6-3  <               6-2       TP Desktop Connector Client Services<                         Disk Space Requirements on Non-Win32H                         Systems..................................    6-3  H               6-3       VR_DA_BLD_MMS.COM Parameters.............   6-23  H               7-1       Macintosh Disk Space Requirements........    7-5  H               8-1       Disk Space Requirements..................    8-2  @               A-1       Files Installed for TP Desktop ConnectorH                         Client Services for OpenVMS Systems......    A-1  @               A-2       Files Installed for the Motif Sample forH                         OpenVMS Systems..........................    A-2  <               A-3       Files Installed for the PowerBuilderH                         Win32 Sample.............................    A-4  <               A-4       Files Installed for the Visual BasicH                         Win32 Sample.............................    A-5  H               A-5       Files Installed for the DOS Sample.......    A-5  <               A-6       Files Installed for the Windows 3.11H                         Sample...................................    A-7  6               A-7       Files Installed for the 16-BitH                         PowerBuilder Sample......................    A-9  <               A-8       Files Installed for the Visual BasicH                         Avertz Sample............................   A-10  6               A-9       Files Installed for the ForcedH                         NonBlocking Tutorial.....................   A-11  ?               A-10      Files Installed for the Client Services H                         for Tru64 UNIX Systems...................   A-12  @               A-11      Files Installed for the Motif Sample forH                         Tru64 UNIX Systems.......................   A-12  H                                                                       ix o  t                      H         ________________________________________________________________  H                                                                  Preface      B               This guide presents information about installing theH               Compaq TP Desktop Connector software on desktop platforms,G               and the TP Desktop Connector Gateway for ACMS software on                 OpenVMS platforms.           Intended Audiencer  ,               This document is intended for:  C               o  Programmers developing client applications with TPi,                  Desktop Connector software.  H               o  System managers responsible for Compaq ACMS transaction*                  processing installations.  G               To perform the installation and deinstallation procedures G               described in this guide, you must have administrator (for D               Windows NT platforms), SYSTEM (for OpenVMS platforms),A               or superuser (for Tru64 UNIX platforms) privileges, E               and you should be familiar with your operating system's.%               installation procedure..           Related Software  B               Compaq TP Desktop Connector is part of a transactionH               processing software suite that also contains the following               product variants:r  7               o  Compaq TP Desktop Connector for ACMSxp.  <               o  Compaq TP Desktop Connector for Portable TP  (               o  Compaq TP Web Connector  2               o  Compaq Portable TP for Windows NT  H                                                                       ix c  L            9            o  Compaq Application Optimizer for Windows NTy  @            Complete information about the relationships of other?            software products with TP Desktop Connector software B            is available in the Software Product Description (SPD).C            The SPD also identifies which versions of your operating D            system are compatible with TP Desktop Connector software.  C            A copy of the SPD is included in your product kit and on D            the Compaq Web site at www.compaq.com by searching for TPD            Desktop Connector in Software Product Descriptions. ReferD            to Compaq TP Desktop Connector for ACMS Release Notes for            the actual URL.        Related Documents  C            Installation instructions for the ACMSxp and Portable TP B            versions of TP Desktop Connector software appear in the+            following manuals, respectively:   A            o  Compaq TP Desktop Connector for ACMSxp Installations               Guideo  F            o  Compaq TP Desktop Connector for Portable TP Installation               Guide2  C            The following manuals contain information about buildingoB            client applications with TP Desktop Connector products:  9            o  Compaq TP Desktop Connector Getting Started   5            o  Compaq TP Web Connector Getting Started   ?            o  Compaq Portable TP for Windows NT Getting Started   A            o  Compaq Application Optimizer for Windows NT Getting                StartedA  @            The following documents contain information on the TP7            Desktop Connector Client Services Interface:d  E            o  Compaq TP Desktop Connector for ACMS Client Application.               Programming Guide   B            o  Compaq TP Desktop Connector for ACMS Client Services               Reference Manual  E            o  Compaq TP Desktop Connector for ACMS Gateway Managementt               Guide         x    m            B               o  Compaq TP Desktop Connector for ACMS 4D Externals)                  User's Guide-online only   F                  (Look in the acmsdi-examples folder of your Macintosh%                  after installation.)   D               Other manuals contain information about installing andH               managing your ACMS system and TP Desktop Connector Gateway                for ACMS software:  5               o  Compaq ACMS for OpenVMS Installatione  G                  Describes the installation of ACMS software on OpenVMS.                  systems.-  >               o  Compaq ACMS for OpenVMS Managing Applications  H                  Explains how to start and stop the ACMS system, monitorH                  system performance, and perform some tuning operations.E                  It also tells how to install applications and how to-<                  authorize users, devices, and applications.  C               This guide does not provide details about the OpenVMS H               installation procedure. For that information, refer to theH               Installation and Operations for the particular device thatF               you use. That manual describes the following procedures:  =               o  Handling and mounting the distribution media   F               o  Readying the current system and target system devices  B               For information on recommended system management and?               operations policies and procedures, refer to your B               site management guide and the volumes in the OpenVMSE               documentation set that pertain to system management and.               operations.s  D               Finally, the Compaq TP Desktop Connector Release Notes@               contain information about new features and currentE               restrictions for TP Desktop Connector software. In your6D               Web browser, open the dskcon_release_notes.htm file onB               the TPware Product Suite CD. On the OpenVMS SoftwareE               Products Library CD, the Release Notes are contained in.E               the installation procedures. Compaq recommends that you1E               read the Release Notes before you install the software..  H                                                                       xi 6                     Structure  @            This manual is divided into three parts, according toA            how you received the TP Desktop Connector software. If A            you have the OpenVMS Software Products Library CD, younC            should start with Part I. If you have the TPware Product ?            Suite CD, you should start with Part II. If you have.C            the TP Desktop Connector Gateway for ACMS CD, start withe            Part III.  5            The document has the following components.S  E            __________________________________________________________.E            Component___Description___________________________________r  E            Part_I______Using_the_Software_Products_Library_CD________   B            Chapter 1   Explains how to prepare your OpenVMS systemC                        for installing TP Desktop Connector software2=                        from the Software Products Library CD.   C            Chapter 2   Explains how to install TP Desktop Connector =                        and gateway software from the Software +                        Products Library CD..  C            Chapter 3   Describes tasks that might be needed on yourdA                        OpenVMS system after installing TP Desktop.D                        Connector software from the Software ProductsA                        Library CD. It also provides references tofA                        information on post-installation tasks for.D                        TP Desktop Connector client software on other!                        platforms.                                 xii .  .          H               __________________________________________________________H               __________________________________________________________  H               Part_II_____Using_the_TPware_Product_Suite_CD_____________  A               Chapter 4   Explains how to prepare your system forhG                           installing TP Desktop Connector software from26                           the TPware Product Suite CD.  A               Chapter 5   Describes how to install the TP Desktop.B                           Connector software on a 32-bit Microsoft+                           operating system:.  G                           o  Windows NT running on either an Intel or af3                              Compaq Alpha processor.  C                           o  Windows 95 or 98 on an Intel processor   A               Chapter 6   Describes how to install the TP Desktop F                           Connector Client Services Interface software?                           and sample client applications on theo>                           following non-Windows 32-bit desktop$                           platforms:  *                              Microsoft DOS3                              Microsoft Windows 3.11k+                              Compaq OpenVMSa'                              Tru64 UNIXn  A               Chapter 7   Describes how to install the TP DesktopeF                           Connector Client Services Interface softwareA                           and sample client applications on Apple ,                           Macintosh systems.                          H                                                                     xiii .  .          E            __________________________________________________________-E            __________________________________________________________   E            Part_III____Using_the_Gateway_CD__________________________3  B            Chapter 8   Explains how to prepare your OpenVMS systemB                        for installing TP Desktop Connector gateway)                        for ACMS software.v  >            Chapter 9   Describes how to install the TP Desktop>                        Connector gateway for ACMS software andB                        sample server-side applications and run theD                        Installation Verification Procedure (IVP). ItD                        also tells you how to recover from system and-                        installation failures..  A            Chapter 10  Describes postinstallation procedures thattE                        prepare the OpenVMS system for running gateway                          software.  <            Chapter 11  Describes how to run the installationC                        verification procedure (IVP) separately fromy2                        the installation procedure.  E            __________________________________________________________nE            Part_IV_____Appendixes____________________________________e  A            Appendix A  Lists the files that are installed on your.>                        system for the various sample programs.  ?            Appendix B  Contains helpful hints about errors that A                        might occur when you run one of the sample E            ____________applications._________________________________   D            The information in the Appendixes applies no matter which            CD you installed.        Conventions  B            The following icons appear in the margin to distinguish@            information that is specific to either OpenVMS VAX or            OpenVMS Alpha:.  >                        The Alpha icon denotes the beginning ofE                        information specific to OpenVMS Alpha systems.f  <                        The VAX icon denotes the beginning ofC                        information specific to OpenVMS VAX systems.o        xiv    -            F               Additional typographic conventions used in this document               are listed below:.  H               __________________________________________________________H               Convention______Description_______________________________  H               TP Desktop      Represents the Compaq TP Desktop Connector/               Connector       product software.T  H               Gateway         Represents the Compaq TP Desktop Connector8                               Gateway for ACMS software.  H               UPPERCASE       In text, the names of OpenVMS directories,G                               commands, logicals, and so on, are set in32                               all capital letters.  E               FTP             Represents the file transfer program ofrH                               your choice, not necessarily File TransferE                               Protocol. You can substitute any method H                               that works on your installation and target(                               platforms.  C               italics         In text, italics indicate emphasis, a C                               product name, or the title of a book.   H               courier         This font indicates a command, programmingD                               language, or an object on your screen.  D               user input      In examples, letters that you actuallyD                               type are highlighted in boldface type.  C               node            In syntax format and examples, italicwC                               type indicates variables, parameters,sF                               or arguments. You need to substitute the0                               appropriate value.  G               E:\             In examples, the CD-ROM device is assumedED                               to be drive E:. Substitute the correct@                               letter for your system, if needed.  E               C:\TPware_      This is the default destination for the.H               Products\       TPware Product Suite installation program.C                               All the examples in this book use the.G                               default. If you choose a different foldernF                               during the installation, substitute that4                               drive and folder name.  H                                                                       xv .  .          E            __________________________________________________________ E            Convention______Description_______________________________   E            .               In examples, a vertical ellipsis indicatesRC            .               that information not directly related to E            ._______________the_example_has_been_omitted._____________n                                                                                      xvi                       H                                                                   Part IH         ________________________________________________________________  H                                   Using the Software Products Library CD        ?               Part I describes how to install Compaq TP Desktop.C               Connector and Compaq TP Desktop Connector Gateway for.F               ACMS software from the OpenVMS Software Products LibraryG               compact disk, also known as the consolidated distributiont               (CONDIST) CD.   F               For installations using the TPware Product Suite CD, seeG               Part II. For installations using the TP Desktop Connector-0               Gateway for ACMS CD, see Part III.                       H                                                                        1H         ________________________________________________________________  H                 Before Installing TP Desktop Connector from the SoftwareH                                                      Products Library CD      F               This chapter discusses the preparations and requirementsF               necessary for installing Compaq TP Desktop Connector andC               Compaq TP Desktop Connector Gateway for ACMS software.E               on an OpenVMS system from the Software Products LibrarycF               CD. This chapter also provides a general overview of the#               installation process.n  @               If you have the TPware Product Suite or TP Desktop@               Connector Gateway for ACMS CD, see Part II or III,               respectively.   C               TP Desktop Connector software includes online Release-F               Notes and gives you the option of printing or displayingE               them during the installation procedure. Compaq strongly2?               recommends that you read the Release Notes before D               proceeding with the installation, in case they contain>               important information regarding the installation               procedure.  B         1.1 Overview of the Software Products Library Installation  C               The TP Desktop Connector software is delivered in twonE               distinct product savesets, one for the gateway softwareCB               that run on the OpenVMS platform and one for desktop               clients:  3               o  The gateway saveset (ACMSDIA031.*)o  G                  Delivers the software required on an OpenVMS system to G                  enable access to Compaq ACMS from the desktop systems.a?                  Also includes server-side sample applications.p  @                  You install the gateway software with a regular#                  VMSINSTAL command.   /               o  The client saveset (TPWA031.A)m  H  TP          Desktop Connector from the Software Products Library CD 1-1 f  s            <               Delivers the software required for application@               development in a multiplatform, networked, desktop>               systems environment. Also includes sample client               applications.q  @               You install the client software by starting with aD               VMSINSTAL command on an OpenVMS system. The next steps5               depend on your target desktop platform.C  D            The clients are provided as self-extracting archive filesD            that expand upon execution. In general, the procedure forA            installing the client software and accompanying sample D            client application files consists of the following steps:  C            1. Transfer a client archive file to your target desktop B               platform, using a file transfer program such as FTP.  6            2. Expand the archive file by executing it.  ?            3. If your target desktop is a Win32 system, run the C               resulting setup.exe file as explained in Section 5.1.   2               If your target desktop is non-Win32:  @               a. Set up your system for the TP Desktop Connector                  environment.C  /               b. Set up your network transport.P  7               These steps are explained in Section 5.2.i  ?               If your target desktop is an Apple Macintosh, seea               Chapter 7t  ;            4. Run the sample application to verify that thet.               installation functions properly.  >            The following sections discuss the preparations andB            requirements necessary before installing the TP Desktop            Connector software.  ,      1.2 Software and Hardware Prerequisites  ;            The Compaq TP Desktop Connector Software ProductiC            Description (SPD), included in the product kit, containsi?            complete information on software products, networks,PC            and systems required for installing and using TP Desktopc1            Connector client and gateway software.   U      1-2 Before Installing TP Desktop Connector from the Software Products Library CDr                 C               In addition, installing TP Desktop Connector software H               requires a certain amount of free storage space. Table 1-1@               summarizes the storage requirements for TP Desktop6               Connector during and after installation.    H               Table_1-1_TP_Desktop_Connector_Disk_Space_Requirements____  6                                                 BlocksG                                                 During     Blocks AfteryH               __________________________________InstallatioInstallation_  A               TP Desktop Connector Gateway for  23 304      6 500                ACMS softwarel  H               OpenVMS_client_files______________34_383______3_300_______  H               To determine the number of free disk blocks on the currentA               system disk, enter the following command at the DCLC               prompt:p  )               $ SHOW DEVICE SYS$SYSDEVICEf  G               In the output column under the heading Free Blocks is the @               number of 512-byte blocks available on the device.  /         1.3 Installation Procedure Requirementsa  @               Both the gateway and client installations from theD               Software Products Library CD use the VMSINSTAL commandD               (see Section 2.1 and Chapter 8 for gateway and server-B               side instructions). Section 2.2 describes the client#               installation process.p                        H  TP          Desktop Connector from the Software Products Library CD 1-3 t  a                  H                                                                        2H         ________________________________________________________________  H               Installing TP Desktop Connector from the Software ProductsH                                                               Library CD      D               This chapter explains how to install Compaq TP DesktopH               Connector and Compaq TP Desktop Connector gateway for ACMSF               from the OpenVMS Software Products Library CD. Table 2-1F               shows the contents of the TP Desktop Connector directory                on the library CD.  B               Table 2-1 TP Desktop Connector Files on the SoftwareH               __________Products_Library_CD_____________________________  H               Name______________________Description_____________________  H               ACMSDIA031.*              TP Desktop Connector Gateway for5                                         ACMS savesets   @               DSKCON_IG_ACMS.PS         This book, formatted for@               DSKCON_IG_ACMS.TXT        PostScript or plain text  E               DSKCON_ACMS_RBI           Read Before Installing letter.  @               DSKCON_ACMS_RELEASE_      New features and product4               NOTES.PS                  restrictions"               DSKCON_ACMS_RELEASE_               NOTES.TXT   D               DSKCON_ACMS_SPD           Software Product Description0                                         document  C               TPWA031.*                 TP Desktop Connector client H               __________________________savesets________________________  @         2.1 Installing the TP Desktop Connector Gateway for ACMS             Software  C               Installing the gateway kit from the Software Products E               Library CD is the same as from the TP Desktop Connector A               Gateway for ACMS CD, except for the location of the   H  TP          Desktop Connector from the Software Products Library CD 2-1    C            B            product saveset. Refer to the Software Products LibraryA            Master Index for the directory name on the library CD. 7            Instructions for VMSINSTAL are in Chapter 9.a  "      2.2 Installing the Client Kit  A            To install the client kit on the OpenVMS system, whileeE            logged in under the SYSTEM account at the DCL prompt, typeC-            a command in the following format:   G            $ @SYS$UPDATE:VMSINSTAL TPWA031 device-name:[directory-name].  @            The value of device-name: is the specification of theB            drive on which the CD-ROM is mounted and directory-nameC            is the location of the product saveset on the library CD.C            (refer to the Software Products Library Master Index forrC            the directory name). Example 2-1 shows the output from ax            sample installation.   +      Example 2-1 Sample Client Installation_  E              OpenVMS VAX Software Product Installation Procedure V6.2_        It is 8-DEC-1998 at 11:31.I  4      Enter a question mark (?) at any time for help.  E                                              (continued on next page)                                   N      2-2 Installing TP Desktop Connector from the Software Products Library CD e  .            6         Example 2-1 (Cont.) Sample Client Installation  L         %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.F         %VMSINSTAL-W-ACTIVE, The following processes are still active:                 NOTES$0145_11*                 DECW$TE_0C4F                 KNEELAND                 FAL_14260004                 DECW$TE_0688                 _FTA57:                  _FTA58:c                 ACMS01EXC001000o                 ACMS01EXC004000n                 ACMS004SP001000o                 ACMS01EXC00A000                  ACMS00ASP001000                  ACMS00ASP002001o0         * Do you want to continue anyway [NO]? yF         * Are you satisfied with the backup of your system disk [YES]?  1         The following products will be processed:              TPW V3.1  <                 Beginning installation of TPWA V3.1 at 11:31  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...  S         Installation of TP Desktop Connector for ACMS V3.1 client software started.   R         **************************************************************************R         *                      Copyright (C) 1990, 1999 by                       *R         *              COMPAQ Computer Corporation, Houston, Texas               *R         *          ALL RIGHTS RESERVED.  UNPUBLISHED RIGHTS RESERVED UNDER THE   *R         *                COPYRIGHT LAWS OF THE UNITED STATES.                    *R         **************************************************************************  H                                                 (continued on next page)              H  TP          Desktop Connector from the Software Products Library CD 2-3    D            3      Example 2-1 (Cont.) Sample Client Installatione  Z      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$COMMON:[ACMSDI.V      MS_CLIENTS].i;      %VMSINSTAL-I-RESTORE, Restoring product save set B ...lZ      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$COMMON:[ACMSDI.N      ONVMS_CLIENTS].;      %VMSINSTAL-I-RESTORE, Restoring product save set C ... Z      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$COMMON:[SYSHLP.E"      XAMPLES.ACMSDI.AVERTZ.MOTIF].;      %VMSINSTAL-I-RESTORE, Restoring product save set D ...cS      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   R      Installation of TP Desktop Connector for ACMS V3.1 client software has ended.  9              Installation of TPWA V3.1 completed at 11:33   .              VMSINSTAL procedure done at 11:33  A            See Chapter 3 to continue with postinstallation tasks.o                                                  N      2-4 Installing TP Desktop Connector from the Software Products Library CD e  m                  H                                                                        3H         ________________________________________________________________  H                   After Installing from the Software Products Library CD      H               This chapter describes the procedures, on both the OpenVMSD               system where the gateway kit was installed and on yourF               target desktop system, that are required for server-sideB               and client-side applications to run and communicate.  ,         3.1 After Installing the Gateway Kit  F               Post-installation tasks for TP Desktop Connector GatewayE               for ACMS software are the same whether you install fromtD               the Software Products Library CD or the TPware Product(               Suite CD (see Chapter 10).  H               For TP Desktop Connector on the Software Products Library,F               the server-side sample application is part of the clientA               kit, not the gateway kit. The client services files E               for OpenVMS are laid down when you use VMSINSTAL on the F               TPWA031 savesets. See Section 3.3 for information on the4               server-side Avertz sample application.  <         3.2 After Installing TP Desktop Connector Client Kit  H               After installing the client kit from the Software ProductsE               Library CD, all the files needed for OpenVMS client and H               sample applications are in place. If you are developing anH               OpenVMS client application, you should edit a startup fileG               as shown in Section 3.2.1. If you are developing a client F               application for a different desktop platform, you should.               follow Sections 3.2.1 and 3.2.2.              H               After Installing from the Software Products Library CD 3-1 h  f                   3.2.1 Editing Startup Files  >            If TP Desktop Connector Gateway for ACMS is alreadyA            installed on the same system, edit the gateway startup C            file, SYS$STARTUP:ACMSDI$STARTUP.COM. Remove the comment E            character (!)  from the following logical name definitions &            for the client directories:  O      $! The next three logical name definitions pertain to TP Desktop ConnectortV      $! client libraries and Motif samples and should be defined only after installingB      $! clients on the same system where the Gateway is installed.      $! @      $! define/system acmsdi$vms sys$common:[acmsdi.vms_clients]N      $! define/system acmsdi$nonvms_clients sys$common:[acmsdi.nonvms_clients]4      $! define/system acmsdi$examples_avertz_motif -F      $!               sys$common:[syshlp.examples.acmsdi.avertz.motif]  E            If the gateway is on a different system, add the following @            logical name definitions to your system startup file:  ?      $ define/system acmsdi$vms sys$common:[acmsdi.vms_clients] M      $ define/system acmsdi$nonvms_clients sys$common:[acmsdi.nonvms_clients] 3      $ define/system acmsdi$examples_avertz_motif -.E                      sys$common:[syshlp.examples.acmsdi.avertz.motif]_  +      3.2.2 After Installing Non-VMS Clientsi  >            In addition to OpenVMS client libraries, the clientB            installation loads the self-extracting archive files onA            your OpenVMS system (see Table 3-1). (The logical name_>            ACMSDI$NONVMS_CLIENTS is defined in Section 3.2.1.)                            ?      3-2 After Installing from the Software Products Library CD                  H               Table_3-1_Contents_of_ACMSDI$NONVMS_CLIENTS_______________  C               ALPHA32.EXE       Runtime and development kit for the E                                 entire TPware product suite on Compaq A                                 Alpha platforms running Microsoft *                                 Windows NT  G               DUNIX.EXE         TP Desktop Connector client services[1]wB                                 and samples for Tru64 UNIX systems  G               INTEL16.EXE       TP Desktop Connector client services[1]o@                                 and samples for 16-bit MicrosoftH                                 operating systems (DOS, Windows 3.11, or>                                 Windows 95) on Intel platforms  C               INTEL32.EXE       Runtime and development kit for the D                                 entire TPware product suite on IntelB                                 platforms running 32-bit MicrosoftH                                 operating systems (Windows NT or Windows#                                 95)h  G               ACMS_DESKTOP.INSTALLEResktop Connector client services[1]sG                                 and samples for Apple Macintosh systemsTH               [1]Formerly_known_as_the_ACMS_Desktop_"portable_API"______                 services.PH               __________________________________________________________  B               After installing the TP Desktop Connector client kitD               on an OpenVMS system, transfer the appropriate archiveF               file to your desktop system and execute it (see SectionsH               3.2.2.1 through 3.2.2.3). After you expand the appropriate<               archive, the resulting files can then be used.  E         3.2.2.1 Transfering Client Files to a 32-bit Microsoft Systemq  F               To place the client files on a 32-bit system on an IntelF               platform, transfer the appropriate archive file from theH               ACMSDI$NONVMS_CLIENTS directory on the OpenVMS system. For               example:  C               1. Use a network file transfer utility such as FTP to G                  copy from the OpenVMS system the INTEL32.EXE file (see )                  Table 3-1). For example:g  H                  a. On the client system, create a subdirectory to store!                     the software:   &                     > mkdir c:\tpwa031  H               After Installing from the Software Products Library CD 3-3 t  t            D               b. Change directory to the newly created subdirectory:                     > cd c:\tpwa031  @               c. Connect to the OpenVMS system that contains the                  archive file:                    > ftp nodename                      .n                     .                      .C                  login to host                     .                      .                      .w                  FTP>a  A                  The value of nodename is the name of the OpenVMSpE                  system on which the archive is installed. At the FTP D                  prompts, supply the OpenVMS user name and password.B                  If you successfully log on to the OpenVMS system,D                  type commands at the FTP prompt to copy the archiveE                  file from the OpenVMS directory to the client systemi8                  and close the FTP utility. For example:                    FTP> binary/                  FTP> cd ACMSDI$NONVMS_CLIENTS:s%                  FTP> get intel32.exei                  FTP> quit  ?            2. On the client system, expand the archive file andr;               delete it to recover disk space. For example:r                 > intel32                > del intel32.exey  ;            See Section 5.2 for information on setting up an34            environment for 32-bit Microsoft systems.              ?      3-4 After Installing from the Software Products Library CDo i  :            E         3.2.2.2 Transfering Client Files to a 16-bit Microsoft System   F               To place the client files on a 16-bit system on an IntelF               platform, transfer the appropriate archive file from theG               ACMSDI$NONVMS_CLIENTS directory on the OpenVMS system and %               expand it. For example:i  C               1. Use a network file transfer utility such as FTP tolG                  copy from the OpenVMS system the INTEL16.EXE file (see )                  Table 3-1). For example:l  H                  a. On the client system, create a subdirectory to store!                     the software:   &                     > mkdir c:\tpwa031  G                  b. Change directory to the newly created subdirectory:n  #                     > cd c:\tpwa031s  C                  c. Connect to the OpenVMS system that contains thel!                     archive file:   "                     > ftp nodename                        .                        .                        .!                     login to host                         .                        .                        .                     FTP>  D                     The value of nodename is the name of the OpenVMSH                     system on which the archive is installed. At the FTPG                     prompts, supply the OpenVMS user name and password.pE                     If you successfully log on to the OpenVMS system, G                     type commands at the FTP prompt to copy the archive H                     file from the OpenVMS directory to the client system;                     and close the FTP utility. For example:3                       FTP> binarys2                     FTP> cd ACMSDI$NONVMS_CLIENTS:(                     FTP> get intel16.exe                     FTP> quit   H               After Installing from the Software Products Library CD 3-5 i  c            ?            2. On the client system, expand the archive file and$;               delete it to recover disk space. For example:a                 > intel16                > del intel16.exeo  G            For client services installation and setup, see Section 6.2.e  <      3.2.2.3 Transfering Client Files to a Tru64 UNIX System  E            To place the client files on a Tru64 UNIX system, transferm?            the appropriate archive file from the ACMSDI$NONVMS_d@            CLIENTS directory on the OpenVMS system. For example:  @            1. Use a network file transfer utility such as FTP toB               copy from the OpenVMS system the dunix.exe file (see&               Table 3-1). For example:  D               a. On the client system, create a directory under your                   home directory:  #                  > mkdir tpwa031dir   -               b. Change to the new directory.r                     > cd tpwa031dir  @               c. Connect to the OpenVMS system that contains the                  archive file.                    > ftp nodenamet                     .c                     .o                     .                   login to host                     .L                     .                      .o                  ftp>p  A                  The value of nodename is the name of the OpenVMS E                  system on which the archive is installed. At the FTP_D                  prompts, supply the OpenVMS user name and password.E                  If you successfully log on, type commands at the FTP B                  prompt to copy the archive file and close the FTP&                  utility. For example:  ?      3-6 After Installing from the Software Products Library CD, r  t                                 ftp> binary >                     ftp> cd sys$common:[acmsdi.nonvms_clients]&                     ftp> get dunix.exe                     ftp> quitS  B               2. On the client system, expand the archive file and>                  delete it to recover disk space. For example:  &                  > chmod 755 dunix.exe                  > ./dunix.exe                  > rm dunix.exe   G               The archive expands into two tar files (see Section 6.4).D  A         3.2.3 Installing the Client Services Interface on OpenVMSe               Systems_  E               The client services library is preconfigured for DECnet G               network access. To build applications that use NetWare or E               TCP/IP as a transport, you must reconfigure the library 2               before creating executable programs.  D               The following steps are necessary to set up the client<               services library for NetWare or TCP/IP access:  @               1. Copy the library and related files to your home6                  directory with the following command:  -                  $ copy/log ACMSDI$VMS:*.* []r  C               2. Remove the DECnet object from the library with the #                  following command:   G                  $ library/delete = net_decnet acmsdi$client_objlib.olbo  H               3. For NetWare, insert the NetWare transport access module=                  into the library with the following command:   J                  $ library/insert acmsdi$client_objlib.olb net_netware.obj  F                  For TCP/IP, insert the TCP/IP transport access module=                  into the library with the following command:e  H                  $ library/insert acmsdi$client_objlib.olb net_tcpip.obj  B               After these steps, you are ready to build TP DesktopD               Connector applications that use NetWare or TCP/IP as aD               transport. Table A-1 shows the files that are added toC               your desktop system during the installation of the TPn<               Desktop Connector client services for OpenVMS.  H               After Installing from the Software Products Library CD 3-7 l               7      3.2.4 Verifying the Motif Client Sample on OpenVMS   ?            Copy, compile, link, and run the source code for the C            sample client program to verify your capability to buildc            applications.  ?            To build the sample application, follow these steps:   A            1. Copy the client sample files to your home directoryA*               using the following command:  =               $  copy/log ACMSDI$EXAMPLES_AVERTZ_MOTIF:*.* []A  >               Table A-2 lists the files that are added to your               desktop system.S  ?            2. If you have MMS, use the MMS makefile provided toSB               build the m_avertz sample application. In the sample=               directory, run MMS using the following command:b  !               $ MMS/DESC=M_AVERTZ   A               If you download TP Desktop Connector libraries to a1C               different location, edit the makefile to indicate the ,               new location of the libraries.  C               ________________________Note ________________________   @               On OpenVMS Alpha systems, the makefile expects the@               logical ACMSDI$VMS_ALPHA to point to the directory;               that contains the TP Desktop Connector client =               library. In addition, on OpenVMS Alpha systems,oB               the first time that the makefile tries to create the?               DECwindows library, the makefile fails. When this 9               happens, rerun MMS to continue the build.<>   C               _____________________________________________________*  D               If you do not have MMS, use the makefile as a guide to-               build the application yourself.t  D            3. Run the application by entering the following command:  $               > run m_avertz/nodebug  @            The m_avertz application displays the menu bar of the@            AVERTZ Car Reservation System. If you want the sample>            desktop client program to communicate with the ACMSE            application, follow the procedures in Section 6.3.3 to setOB            up the sample application on the ACMS system. After you  ?      3-8 After Installing from the Software Products Library CDu c  t            H               set up the ACMS system, use the Session menu to sign in toH               the ACMS system. After you sign in, you can use the RentalE               menu to run the reserve task of the AVERTZ application.   F               The installation procedure is now complete and verified.  G         3.3 Setting Up the Avertz ACMS Sample Application on an OpenVMS              System  C               The command procedure VR_DA_RUNTIME_SETUP.COM sets up F               the sample application. You need SYSPRV privilege to runE               the procedure. Refer to the file ACMSDI$VR_APPLICATION_ G               INFO.TXT in the ACMSDI$EXAMPLES_AVERTZ directory for more 3               information on setting up the sample._  D               To prepare the AVERTZ sample application on the Compaq/               OpenVMS system, do the following:   E               1. Run the command procedure to set up the application:   >                  $ @ACMSDI$EXAMPLES_AVERTZ:VR_DA_RUNTIME_SETUP                     .                      .t                     .u                  $  F               2. Start the ACMS system (if necessary) and the applica-                  tion:  $                  $ ACMS/START SYSTEM4                  $ ACMS/START APPLICATION VR_DA_APPL  G               3. Perform other management tasks related to your system, E                  for example, authorizing user accounts. Refer to the F                  management information in Compaq TP Desktop Connector?                  for ACMS Client Application Programming Guide.s  C               The following sections provide additional informationeC               about using the Avertz sample application on the ACMSr               OpenVMS system.T          H               After Installing from the Software Products Library CD 3-9                 A      3.3.1 Using the Avertz ACMS Sample with Rdb Version 6.0 with             MultiversionK  C            When you execute the VR_DA_RUNTIME_SETUP.COM file to setrC            up the sample application, this command file invokes twoiE            option files, VR_READ_SERVER.OPT and VR_UPDATE_SERVER.OPT,v@            which refer to the SYS$LIBRARY:SQL$USER library. On aC            system with Rdb Version 6.0 with multiversion installed,rC            the SYS$LIBRARY:SQL$USER file is not available. Instead,k?            the version number is appended to the file name, for ,            instance, SYS$LIBRARY:SQL$USER60.  ?            To work around this naming mismatch problem, you can <            define the logical name SQL$USER to reference the1            appropriate library file. For example:i  3            $ DEFINE SQL$USER SYS$LIBRARY:SQL$USER60   +            Modify the linker options files:.  7               ACMSDI$EXAMPLES_AVERTZ:VR_READ_SERVER.OPTl9               ACMSDI$EXAMPLES_AVERTZ:VR_UPDATE_SERVER.OPT               Replace the linet  -            SYS$LIBRARY:SQL$USERnn.OLB/LIBRARYk              with the following:              SYS$USER/LIBRARYo  =      3.3.2 Building the Avertz ACMS Sample with DECforms V1.4   C            The VR_FORM.IFDL file of the Avertz ACMS sample applica- C            tion cannot be compiled under DECforms Version 1.4. ThissD            is because the DECforms Version 1.4 IFDL parser no longerB            recognizes the colon symbol (:), which the VR_FORM.IFDL            file uses.s  A            To get around this problem, put double quotation marksm?            around the text containing the ":" symbol in the VR_             FORM.IFDL file.  -            For example, change the following:s                     CopyC                        AVERTZ_CDD_FIELD:CUSTOMER_ID from Dictionary                    End Copy  @      3-10 After Installing from the Software Products Library CD a  d                           To look like:a                        Copy H                           "AVERTZ_CDD_FIELD:CUSTOMER_ID" from Dictionary                      End Copyt  9         3.3.3 User Name Quotas for the Avertz ACMS Samplel  E               The VR_DA_RUNTIME_SETUP.COM command file assigns quotasnB               for the AVERTZ_EXC, AVERTZ_UPD, and AVERTZ_READ user@               names that are adequate for running the VR_DA_APPLG               sample application. If your system already has these user E               names defined, the quotas for these user names might be D               inadequate for VR_DA_APPL. If you are using the AVERTZD               sample application, delete the AVERTZ_EXC, AVERTZ_UPD,F               and AVERTZ_READ user names before running VR_DA_RUNTIME_E               SETUP.COM to ensure that you get appropriate quotas for                these user names.s  C               To ensure the success of the operations in the VR_DA_eB               RUNTIME_SETUP.COM command procedure, run it from the               system account.   <         3.3.4 Access Control List for the Avertz ACMS Sample  C               The VR_DA_RUNTIME_SETUP.COM procedure adds the AVERTZEC               application name VR_DA_APPL to the ACMS database. The B               command line to do so includes the ACL qualifier andC               assigns the ID as /ID=SYSTEM. This might fail on your                system.   B               To ensure that the VR_DA_RUNTIME_SETUP.COM procedureC               works, change the ID=SYSTEM to ID=[UIC], where UIC iss@               that of the account SYSTEM; for example, ID=[1,4].  /         3.3.5 Rebuilding the Avertz ACMS Samplee  F               Executables are provided for the sample. You do not needA               to rebuild the sample to run it. However, a DEC/MMS D               description file is provided for rebuilding the sample@               to incorporate any changes you make to the sample.  C               To modify and rebuild the sample, follow these steps:   >               1. Copy the sample sources to another directory.  H              After Installing from the Software Products Library CD 3-11    .            <            2. Use the command procedure VR_DA_BLD_MMS.COM toC               rebuild the sample under a different ADB name in that                directory:  A               a. Create the CDD directories for the AVERTZ compo-T                  nents.S  &               b. Define logical names.  I                  If you are using a directory other than ACMSDI$EXAMPLES_ C                  AVERTZ for rebuilding the sample, edit the logical ?                  name definitions in the VR_DA_BLD_LOGICALS.COMe@                  command procedure to point to your file and CDDE                  directories. Make these edits before running the BLD D                  portion of the VR_DA_BLD_MMS.COM command procedure.  :               c. Perform other setup and build activities.  A            3. Run the command procedure VR_DA_BLD_MMS.COM without                parameters:M  .               $ @ACMSDI$EXAMPLES:VR_DA_BLD_MMS  ?               All the setup and build activities are performed.n  =            To perform a specific activity, specify one of the #            parameters in Table 6-3.   E            Table_3-2_VR_DA_BLD_MMS.COM_Parameters____________________   E            Keyword__________Activity_________________________________   7            BLD              Run MMS to build VR_DA_APPLh  E            CDD              Set up the CDD dictionary and directoriesr*                             for VR_DA_APPL  E            DB_______________Create_the_VEHICLE_RENTALS_database______m              @      3-12 After Installing from the Software Products Library CD e  s                  H                                                                  Part IIH         ________________________________________________________________  H                                        Using the TPware Product Suite CD        D               Part II describes Compaq TP Desktop Connector softwareH               installation from the TPware Product Suite CD on a Windows               32-bit system.  H               This part covers the client-side software and samples, butH               not the server-side software and samples. See Part III for+               the server-side instructions.   D               If you install the software from the Software Products%               Library CD, see Part I.n i                     H                                                                        4H         ________________________________________________________________  H                          Before Installing TP Desktop Connector Software      F               This chapter describes the preparations and requirementsB               necessary for installing Compaq TP Desktop ConnectorC               software and also contains information on removing TPeC               Desktop Connector software from Win32 platforms. Your E               bill of materials (BOM) and indented bills report (BIL)yD               specify the number and contents of your media. Be sureG               to verify the contents of your kit with this information. G               If your kit is damaged or incomplete, contact your Compaqe               representative.   !         4.1 Installation Overview   C               The TPware Product Suite CD contains all the software B               required for development or deployment of TP DesktopC               Connector client applications, except for the gateway G               needed to connect to an ACMS system. The gateway softwarelH               is distributed separately. Table 4-1 lists the contents of*               the TPware Product Suite CD.  C               As shown in Table 4-1, all TP Desktop Connector filesmG               are provided on the TPware Product Suite CD. This compactoH               disk is in ISO9660 standard format and contains executableC               programs that install the appropriate files. You must G               have a Windows NT or Windows 95/98 system with a CD driveTB               on which to run the installation procedures that are%               described in Chapter 5.u  F               TP Desktop Connector supports the following platforms inH               addition to 32-bit Microsoft operating systems (Windows NT!               and Windows 95/98):   D               o  16-bit Microsoft operating systems running on Intel                  platforms  ?               o  Compaq OpenVMS running on VAX or Alpha systemsT  #               o  Tru64 UNIX systems   H                      Before Installing TP Desktop Connector Software 4-1 a  i                        o  Macintosh systemsC  <            If you are developing TP Desktop Connector clientC            applications for any of the above non-Win32 systems, you D            must install the client services files yourself. Refer to            Chapters 6 and 7.                                                                              8      4-2 Before Installing TP Desktop Connector Software                 H               Table_4-1_Contents_of_the_TPware_Product_Suite_CD_________  H               Name__________Contents____________________________________  F               \alpha32      Runtime and development kit for the entire@                             TPware product suite on Compaq AlphaB                             platforms running Microsoft Windows NT  G               \dunix        TP Desktop Connector client services[1] andl:                             samples for Tru64 UNIX systems  E               \install_     Installation guides for all of the TPwarep@               guides        products, formatted for Web browsing  C               \intel16      TP Desktop Connector client services[1] F                             and samples for 16-bit Microsoft operatingF                             systems (DOS, Windows 3.11, or Windows 95).                             on Intel platforms  F               \intel32      Runtime and development kit for the entireC                             TPware product suite on Intel platforms F                             running 32-bit Microsoft operating systems9                             (Windows NT or Windows 95/98)a  G               \mac          TP Desktop Connector client services[1] and ?                             samples for Apple Macintosh systems   G               \vmsalpha     TP Desktop Connector client services[1] and =                             samples for OpenVMS Alpha systems   G               \vmsvax       TP Desktop Connector client services[1] andf;                             samples for OpenVMS VAX systemsn                 dskcon_ A               release_      Information on new features and known A               notes.htm     restrictions for all three TP Desktop *                             Connector kits                 optimizer_A               release_      Information on new features and knownCF               notes.htm     restrictions for Application Optimizer for&                             Windows NT                 portable_IA               tp_release_   Information on new features and knownlD               notes.htm     restrictions for Portable TP for Windows                             NT                 webcon_lA               release_      Information on new features and knownc=               notes.htm     restrictions for TP Web ConnectorgH               [1]Formerly_known_as_the_ACMS_Desktop_"portable_API"______                 services.   H                      Before Installing TP Desktop Connector Software 4-3 i               E            __________________________________________________________i    ;      4.2 Preparing to Install TP Desktop Connector Softwarep  C            Ensure that your system meets the software requirements.oA            Minimum software requirements needed to install the TPAC            Desktop Connector software and build client applicationse?            that run with ACMS systems are shown in the SoftwarecA            Product Description (SPD), a copy of which is includedf            in the product kit.        4.2.1 Product Licenses   B            To install TP Desktop Connector products, you must haveB            a Product License Key. This is a paper certificate thatC            contains information about the license you have to run apC            particular piece of software. You are asked to enter thee9            license key during the installation procedure.o        4.2.2 Disk Space   >            Installing TP Desktop Connector software requires aE            certain amount of free storage space, which depends on thehE            platform you use. Table 4-2 shows the storage requirements -            for TP Desktop Connector software.r  E            Table_4-2_TP_Desktop_Connector_Disk_Space_Requirements____a  E            __________________________Intel_______________Alpha_______   E            Kilobytes_(KB)____________6_063_______________6_517_______t  C               ________________________Note ________________________e  B               These are the minimum disk space requirements. These<               estimates, though conservative, are not always=               an accurate indicator of the disk space used one>               a particular machine. System disk configuration,B               including the size of the disk sector and the number=               of sectors per cluster, cannot be determined byp?               the installation program. Therefore, some systemss!               require more space.n  C               _____________________________________________________r  8      4-4 Before Installing TP Desktop Connector Software _  _            F               See Table 6-2 for the disk space required for TP DesktopF               Connector client services software on non-Win32 systems.  +         4.3 Removing the Installed Softwaren  F               You might decide to remove the installed TPware softwareG               to upgrade to a new TPware software version, or for otherEG               reasons. Note that when you remove the software, you loseiD               the settings defined in the TPware Management Utility.F               Before removing the software, refer to the Release NotesB               for instructions on saving your management settings.  H               You can remove the installed TP Desktop Connector softwareH               from your system using either the shortcut provided in theE               TPware products program group, or the system Add/Remove                Programs utility.h  F                 ________________________Note  ________________________  =                 The uninstall procedure removes all currentlyS*                 installed TPware products.  E                 _____________________________________________________e  F               o  To remove the software using the shortcut provided in*                  the TPware program group:  +                  1. Click the Start button.   -                  2. Choose the Programs menu.f  =                  3. Choose the TPware Products program group.   @                     If you chose a different program group whileD                     installing TP Desktop Connector, that group nameH                     is displayed on the Programs menu in place of TPware                     Products.A  5                  4. Choose the Uninstall TPware item.   C               o  To remove the software using the system Add/Removea"                  Programs utility:  D                  1. Double click the Add/Remove Programs icon in the)                     Control Panel window.C  2                  2. Choose the Compaq TPware item.  3                  3. Click the Add/Remove... button.   H                      Before Installing TP Desktop Connector Software 4-5 m                     H                                                                        5H         ________________________________________________________________  H                Installing TP Desktop Connector Software on Win32 Systems      E               This chapter describes the procedures for installing orlC               reinstalling the Compaq TP Desktop Connector software F               from the TPware Product Suite CD on Microsoft Windows NTF               running on an Intel or a Compaq Alpha system, or WindowsB               95/98 on an Intel system. This chapter also containsD               information on postinstallation tasks on Windows NT or$               Windows 95/98 systems.  @               For information on installing TP Desktop ConnectorD               software on non-Win32 platforms, see Chapters 6 and 7.  H               For information on installing TP Desktop Connector GatewayG               for ACMS software, see Part III of this guide (Chapters 8A               through 11).  @         5.1 TP Desktop Connector Software Installation Procedure  F               To install TP Desktop Connector software, run one of theE               setup programs provided on the TPware Product Suite CD.S0               Double-click one of the following:  "               E:\alpha32\setup.exe"               E:\intel32\setup.exe  G               Replace E: with the correct drive letter for your system.e  G               The setup program displays a splash screen and a progresswC               indicator while it initializes its wizard. When setupdE               starts, you see a series of dialog boxes. The followingMD               table lists the operations associated with the command*               buttons in the dialog boxes.        H            Installing TP Desktop Connector Software on Win32 Systems 5-1 r  g          E            __________________________________________________________ E            To_do_this...___________________Click_this_button:________   /            Complete the choices in a       Next "            dialog box and continue  /            Return to a previous dialog     Back             box  1            Exit without completing the     CancelRE            installation______________________________________________t  @            Follow the instructions in the dialog boxes to select0            installation of TP Desktop Connector.  ?            The setup utility checks whether there is sufficientoC            disk storage, copies the appropriate files, and performsm            registry operations.l  B            If setup finds that a requisite software product is not?            installed or that the minimum version of a requisiteRB            product is not on the system, it displays a Warning boxA            showing the product name and version. The installations=            might continue after the warning or it might fail, =            depending on the prerequisite. If the installationI@            continues, you must install the prerequisite softwareE            before you can actually use TP Desktop Connector software.s  7      5.2 After Installing TP Desktop Connector Softwaree  C            This section describes some procedures you might want tomD            perform after you copy files from the OpenVMS system (seeD            Section 3.2.2.1) or after the setup program finishes (see            Section 5.1).  ,      5.2.1 Setting Up the TPware Environment  A            Before developing TPware client applications, you mustO@            set up the environment variables that TPware softwareB            requires. To do this, run the command file installed by            the setup program:d  2            C:\TPware\stdl\bin\stdl_set_version.bat  C               ________________________Note ________________________t  <               All examples show the default location. If you@               chose a different destination while running setup,  B      5-2 Installing TP Desktop Connector Software on Win32 Systems t  A            C                 substitute your own drive and folder for C:\TPware.d  E                 _____________________________________________________/  '         5.2.2 Accessing the ACMS Systemv  @               For access to a Compaq ACMS transaction processingG               system, the TP Desktop Connector Gateway for ACMS must beaF               installed on the OpenVMS system. The gateway software isG               distributed on a separate CD; instructions for installingr9               it are contained in Part III of this guide.s  D         5.2.3 Defining the Network Transport for the Client Services               InterfaceA  D               TP Desktop Connector software supports both DECnet andG               TCP/IP network transports for Windows NT or Windows 95/98 D               clients. The product files include two versions of theF               client application's dynamic link library (DLL); one forF               DECnet and one for TCP/IP. These files are installed, by               default, in:  0               C:\TPware\stdl_rt\bin\acmsdiDN.dll0               C:\TPware\stdl_rt\bin\acmsdiWS.dll  B               To set up the TP Desktop Connector software for yourB               network transport, copy the appropriate DLL from theG               installation folder to your working directory, and renamecE               it acmsdi.dll. The acmsdiDN.dll provides DECnet support D               and works with PATHWORKS 32. The acmsdiWS.dll provides>               TCP/IP support and also works with PATHWORKS 32.  =         5.2.4 Verifying the TP Desktop Connector InstallationT  B               To verify that your TP Desktop Connector software is@               installed correctly, you can run one of the sample$               applications provided.  @               If you are developing an application that uses theE               Adapter Interface (refer to Compaq TP Desktop Connector D               Getting Started), both the sample applications and theC               instructions for running them are online. To read thefD               instructions, choose the ACMS Samples item from the TPD               Desktop Connector for ACMS menu in the TPware Products               program group.  H            Installing TP Desktop Connector Software on Win32 Systems 5-3    U            ?            For a TP Desktop Connector application that uses thep@            Client Services Interface,[*] you must have platform-@            specific TP Desktop Connector client software on yourC            development system. All the client services files are onaB            the TPware Product Suite CD. If you are developing a TPD            Desktop Connector client application that uses the ClientC            Services Interface, in a non-Win32 operating system, you A            must transfer the TP Desktop Connector client services D            files to your desktop development system yourself. How to0            do this varies according to platform:  E            o  For 16-bit Microsoft systems, Compaq OpenVMS, and Tru64k*               UNIX systems, see Chapter 6.  9            o  For Apple Macintosh systems, see Chapter 7.   >            If you are developing a TP Desktop Connector clientA            application that uses the Client Services Interface on B            a Win32 system, the client services files are installedD            on your desktop by the setup program with the rest of theA            development tools. The instructions for setting up the A            client services and running the sample programs are infE            Sections 5.2.5 and 5.2.6. You do not need to read Chapters             6 and 7.   7      5.2.5 Running the Win32 Sample Client Applications   B            TP Desktop Connector client services include two sample*            applications for Win32 clients:  C            o  For Windows 95, in PowerBuilder, a simplified version,A               of the original AVERTZ for Windows described in theSD               ACMS manuals. This sample illustrates the execution of0               an ACMS task with no exchange I/O.  B               Table A-3 describes the contents of the PowerBuilder:               sample folder TPware\STDL\Samples\acmsdi\PB.  E               For directions on running the PowerBuilder sample, readO8               the three .doc files in the sample folder.  D            o  For Windows 95/98 or Windows NT, the same Visual BasicD               AVERTZ sample that was provided for ACMS Desktop V2.0;7               it is a blocking, no exchange I/O client.               ___________________E            [*]Formerly  known as the ACMS Desktop "portable API", ando  A                as opposed to the new TPware automation interface.(  B      5-4 Installing TP Desktop Connector Software on Win32 Systems    r            E                  Table A-4 describes the contents of the Visual Basic =                  sample folder TPware\STDL\Samples\acmsdi\VB.   D               The following files provide memory copy procedures andE               can be used to help with interfacing Visual Basic Win32iE               programs with the TP Desktop Connector client services:   ,                  C:\TPware\STDL\lib\divb.lib/                  C:\TPware\STDL_RT\bin\divb.dllt3                  C:\TPware\STDL_RT\bin\msvcrt40.dll   G               To verify the success of your TP Desktop Connector client H               services installation, you can run the Visual Basic sample.               application. Follow these steps:  E               1. Start up the Visual Basic development environment in                   Windows 95.  +               2. Open the VBAVERTZ project.a                                                    H            Installing TP Desktop Connector Software on Win32 Systems 5-5                 E            3. Verify that all the required files were loaded (see the '               VBAVERTZ project window):                     vbavertz.bas                   mainmenu.frm                   reserve.frm                  signin.frmf  D               Double click each item in the project window to verify%               that it loads properly.P  A            4. Run the interpreted version of VBAVERTZ (choose then/               Start command from the Run menu).   .      5.2.6 Code Conversion Libraries for Kanji  >            TP Desktop Connector client services (on Windows 95E            systems only) provides code conversion libraries for Kanji @            users, which convert Shift JIS code to DEC Kanji codeC            and DEC Kanji code to Shift JIS code. You can link theseeA            libraries with your client application, if it requires !            Kanji code conversion.p  D            The following files are installed for Kanji applications:  ,               C:\TPware\stdl\lib\jcnvwin.lib.               C:\TPware\stdl\include\jcnvwin.h-               C:\TPware\help\jcnvwin_guide.pso.               C:\TPware\help\jcnvwin_guide.txt  C            For usage information, refer to either the PostScript or =            the text version of the Japanese conversion guide.c                          B      5-6 Installing TP Desktop Connector Software on Win32 Systems                       H                                                                        6H         ________________________________________________________________  H         Installing the TP Desktop Connector Client Services on Non-Win32H                                                                  Systems      C               The TP Desktop Connector client services software was D               previously released as the ACMS Desktop "portable API"B               services. It allows client applications running on aF               variety of desktop platforms to call ACMS tasks. For theG               current TP Desktop Connector release, the client servicesnG               software is distributed on the TPware Product Suite CD in F               folders (directories) according to the desktop platform.9               This chapter is also organized by platform:_  H               __________________________________________________________H               For_this_platform_________________________See_._._._______  C               16-bit[1] Microsoft operating systems,    Section 6.2 6               that is, DOS or Windows 3.11 (also known.               as Windows for Workgroups (WfW))  C               Compaq OpenVMS systems                    Section 6.3D  C               Tru64 UNIX systems                        Section 6.4cH               [1]For_Win32_Microsoft_operating_systems,_see_Section_5.2_  H               __________________________________________________________  F               Section 6.1 presents a general overview of the installa-1               tion process and its prerequisites.   E               For information on TP Desktop Connector client servicesh9               for Apple Macintosh systems, see Chapter 7.   A               For information on how to design and develop client @               applications using the TP Desktop Connector clientC               services software, refer to the following ACMS books:   H               o  Compaq TP Desktop Connector for ACMS Client Application"                  Programming Guide  E               o  Compaq TP Desktop Connector for ACMS Client Services_!                  Reference Manual_  H  the       TP Desktop Connector Client Services on Non-Win32 Systems 6-1 _  _            5      6.1 Overview of the Client Services Installationi  >            The TPware Product Suite CD is in ISO 9660 standard?            format. The instructions in this chapter assume thatoA            you can mount this CD directly on your desktop system.yA            If you can not, you will have to use ftp or some otheriD            network file transport to get the files from a Windows 95?            or Windows NT system that has the TPware CD mounted.f  >            The client services are provided as self-extracting@            archive files that expand upon execution. In general,?            the procedure for installing the client services and @            accompanying sample client application files consists"            of the following steps:  @            1. Transfer a client services archive to your desktop               platform              2. Execute it  ;            3. Set up your system for the TPware environment   C            4. Set up the client services for your network transport   :            5. Transfer and execute a sample client archive  <            6. Run the sample to verify that the installation!               functions properly.v  >            The following sections discuss the preparations andB            requirements necessary before installing the TP Desktop6            Connector client services and sample files.  !      6.1.1 Software Prerequisitese  <            The TP Desktop Connector SPD contains information>            on software prerequisites for installing TP DesktopB            Connector. Table 6-1 lists the products required to use;            the various client services sample applications.             Q      6-2 Installing the TP Desktop Connector Client Services on Non-Win32 Systems_ _  _            D               Table 6-1 Client Services Sample Applications SoftwareH               __________Requirements____________________________________  H               Platform___________Products_Required______________________  F               DOS                Microsoft COBOL Version 5.0 or higherE                                  Microsoft Visual C++ Version 1.52 oro'                                  higherT  B               Windows 3.11 SDK   Microsoft Windows Version 3.11 or'                                  higher E                                  Microsoft Visual C++ Version 1.52 ora'                                  highere  B               Visual Basic       Microsoft Windows Version 3.11 or'                                  highereC                                  Microsoft Visual Basic Version 4.0o  H               Motif on OpenVMS   VAX C for OpenVMS Version 3.0 or higherC                                  DECwindows Motif for OpenVMS Alpha ,                                  Version 1.0  D               Motif on Tru64     DEC C, DECwindows Developers Kit onH               UNIX_______________Tru64_UNIX_for_OSF/Motif_Version_1.1___           6.1.2 Disk Space  E               Table 6-2 lists the disk space required for each of theW               desktop systems.  G               Table 6-2 TP Desktop Connector Client Services Disk SpaceeH               __________Requirements_on_Non-Win32_Systems_______________  H               OpenVMS_VAX_Client___________________Number_of_Blocks_____  <               Client services library and network        322               software  <               Common headers                              31  <               Motif sample files                         305  H                                                 (continued on next page)    H  the       TP Desktop Connector Client Services on Non-Win32 Systems 6-3                 A            Table 6-2 (Cont.) TP Desktop Connector Client ServicesCA                              Disk Space Requirements on Non-Win32 E            __________________________________________________________P  E            OpenVMS_Alpha_Client_________________Number_of_Blocks_____n  9            Client services library and network        709             software   9            Common headers                              31   9            Motif sample files                         489   E            __________________________________________________________ E            DOS_and_Windows_3.11_Client__________Number_of_Bytes______s  9            Client services libraries and        2 187 264W            network softwarer  9            Common files                            70 222   9            Kanji conversion libraries             182 748   9            COBOL sample files                     421 888   9            Windows sample files                   437 2481  E            ___________________________________________________________E            Macintosh_Client_____________________Number_of_Blocks______  9            Client services library, network         2 538 %            software, and sample filesn  9            Common headers                              31   E            __________________________________________________________ E            Tru64_UNIX_Client____________________Number_of_Bytes______   9            Client services library and TCP/IP     261 748             module   9            Motif sample files                     291 826k  E            Common_headers__________________________30_206____________p        6.1.3 Resources  B            Before you start the installation procedure, obtain the            following:r  D            o  DECnet node name (host name on TCP/IP) for the OpenVMSB               system on which the TP Desktop Connector Gateway for               ACMS is installedo  Q      6-4 Installing the TP Desktop Connector Client Services on Non-Win32 Systems  i  i            F               o  Valid account (user name and password) on the OpenVMSE                  system on which the TP Desktop Connector Gateway forf"                  ACMS is installed  H               o  Directory of the network file transfer software in your8                  directory search path or on your CD-ROM  A               o  Directory in which the TPware files reside on anOD                  OpenVMS system, or your CD-ROM device (usually E:\)  B               o  Directory in which to install the client services                  software   =               o  Sufficient disk space, as shown in Table 6-2   %               o  Host name for TCP/IPe  G         6.2 Installing the Client Services for 16-Bit Microsoft Systemsl  G               TP Desktop Connector provides one self-extracting archive\F               named i16clint.exe that contains all the client servicesD               files for both DOS and Windows 3.11 clients. The filesH               contained within the archive include the static-link (LIB)C               and the dynamic-linked (DLL) libraries. Also includednD               are individual object files and DLLs for the supported               transports.e  G               If you install the software from the TPware Product Suite/F               CD (see Section 5.1), transfer the archive file from theD               Windows NT system to your desktop system. For example:  E               1. On the client system, create a subdirectory to storet                  the software:  "                  C:\> mkdir ACMSDI  D               2. Change directory to the newly created subdirectory:                    C:\> cd ACMSDI   E               3. Copy the archive file to the newly created subdirec-                   tory.  8                  C:\ACMSDI> copy E:\intel16\i16clint.exe  D               If you install the software from the Software ProductsG               Library CD (see Section 3.2.2.2), change directory to then3               location containing the client files.l  H  the       TP Desktop Connector Client Services on Non-Win32 Systems 6-5 s  e            ?            To install the client services software, execute the\@            archive file and delete it to recover disk space. For            example:s              > i16clinte            > del i16clint.exe   C            The archive expands, and the resulting files can then be             used.  C            If this is to be your working directory, you need to set.B            the environment variables that define the paths for theE            libraries, include files, and executables. Add commands too/            your autoexec.bat file. For example:.              set LIB=%LIB%;ACMSDIt'            set INCLUDE=%INCLUDE%;ACMSDIf!            set PATH=%PATH%;ACMSDIf  1      6.2.1 Setting Up the Client Services for DOSr  >            The DOS client services use the static-link libraryD            ACMSDIL.LIB, which supports DECnet by default. AdditionalE            network transport object files are provided for the large- @            memory model, whose names reflects the transport they            support.s  E            __________________________________________________________hE            Memory_Model__DECnet________TCP/IP________Netware_________   E            Large_________netdecl.obj___nettcpl.obj___netwarel.obj____   D            If you are not using DECnet, remove the DECnet module andB            insert the module that corresponds to the transport youC            are using. For example, to set up up the large model fore            TCP/IP:  $            LIB ACMSDIL.LIB -NETDECL;$            LIB ACMSDIL.LIB +NETTCPL;            Q      6-6 Installing the TP Desktop Connector Client Services on Non-Win32 Systemsu e  v            >         6.2.2 Installing the Sample Client Application for DOS  H               The client services sample for DOS is written in MicrosoftB               COBOL and is in a self-extracting archive file namedG               i16cobol.exe. If you install the software from the TPware F               Product Suite CD (see Section 5.1), transfer the archiveE               file from the Windows NT system to your desktop system.s               For example:  %               C:\ACMSDI\> mkdir cobole"               C:\ACMSDI\> cd cobolC               C:\ACMSDI\COBOL> copy e:\intel16\Samples\i16cobol.exea  D               If you install the software from the Software ProductsG               Library CD (see Section 3.2.2.2), change directory to thee3               location containing the client files.e  D               To install the client services sample for DOS, executeG               the archive file and delete it to recover disk space. For                example:  +               C:\ACMSDI\COBOL> i16cobol.exe5/               C:\ACMSDI\COBOL> del i16cobol.exe   2               Table A-5 shows the resulting files.  >               The sample executable was built using the DECnetC               libraries. If you are not running DECnet, you need to 6               relink the sample before you can run it.  @         6.2.3 Verifying the Client Services Installation for DOS  C               Compile, link, and run the source code for the sample ?               client program to verify your capability to build C               applications. You need the following products on your =               desktop system to build the sample application:   B               o  Compiler (preferably Microsoft C) that can accessH                  objects compiled by Microsoft Visual C++ Version 1.5 or                  higher   D               o  C runtime library that is compatible with Microsoft'                  Visual C++ Version 1.5_  H               o  COBOL compiler compatible with Microsoft COBOL software@                  (required only to build the sample application)  H  the       TP Desktop Connector Client Services on Non-Win32 Systems 6-7                 A            The client services samples include two batch files to E            build the COBOL client program. You can modify these files B            according to your own software development environment.=            After you modify the files, run them. For example:3  #            C:\ACMSDI\COBOL> bld-ppsD               .c               .                . #            C:\ACMSDI\COBOL> bld-cli                .e               ..               .   @            To run the sample client program, enter the following            command:P  "            C:\ACMSDI\COBOL> client  B            The client program displays the main menu of the AVERTZ-            Vehicle Rental System application.   =            To connect the sample program to the AVERTZ sample A            application, follow the procedures in Section 6.3.3 toZD            set up the sample application on the ACMS system. You canE            sign in to the ACMS system and use the reserve task of the             application.   =            The DOS installation procedure is now complete and             verified.  :      6.2.4 Setting Up the Client Services for Windows 3.11  B            You would normally use a DLL when building applications>            under Windows. However, you can use the static-link>            libraries provided with TP Desktop Connector if you0            prefer, when the transport is DECnet.  A            The client services sample for Windows 3.11 expects to E            find a DLL called acmsdi.dll To set up the client servicesnE            for your network transport, copy one of the files below to ;            your working directory and rename it acmsdi.dll.   E            __________________________________________________________oE            DECnet___________TCP/IP___________Netware_________________i  E            acmsdiDN.dll_____acmsdiWS.dll_____acmsdiNW.dll____________   Q      6-8 Installing the TP Desktop Connector Client Services on Non-Win32 Systems: w  \            D               For example, to use TCP/IP with the Winsock interface:  %               C:\ACMSDI> mkdir sdk311 <               C:\ACMSDI> copy acmsdiWS.dll sdk311\acmsdi.dll  F               There is an executable file, diTskLnk.exe, that supportsD               multiple executables sharing a submitter session underB               Windows Version 3.1 using TCP/IP. Refer to Compaq TPE               Desktop Connector for ACMS Gateway Management Guide for 2               information on this executable file.  1         6.2.5 Code Conversion Libraries for Kanji   E               TP Desktop Connector provides code conversion libraries B               for Kanji users, which convert Shift JIS code to DECF               Kanji code and DEC Kanji code to Shift JIS code. You canF               link these libraries with your client application, if it-               requires Kanji code conversion.p  H               These libraries are located in the following archive file:  *               E:\intel16\win16\jcnvwin.exe  A               For usage information, refer to JCNVWIN_GUIDE.PS oreD               JCNVWIN_GUIDE.TXT, which are installed when you expand               the archive.  @         6.2.6 Installing the Sample Application for Windows 3.11  G               The client services sample for Windows 3.11 is written in_H               C and is provided in the following self-extracting archive               files.  G               i16sdklb.exe     Contains both the sample sources and the D                                make file for using the DECnet medium9                                model static-link library.s  G               i16sdkdl.exe     Contains just the alternate files needed C                                to rebuild the sample client againsttB                                DLLs. The resulting executable fileA                                can work with any of the supportedo*                                transports.  A               If you install the software from the TPware Product C               Suite CD (see Section 5.1), transfer the archive file E               i16sdklb.exe from the Windows NT system to your desktopo"               system. For example:  H  the       TP Desktop Connector Client Services on Non-Win32 Systems 6-9 t                           C:\ACMSDI> cd sdk311oA            C:\ACMSDI\SDK311> copy e:\intel16\Samples\i16sdklb.exer  A            If you install the software from the Software Products D            Library CD (see Section 3.2.2.2), change directory to the0            location containing the client files.  @            To install the software, execute the archive file and8            delete it to recover disk space. For example:  )            C:\ACMSDI\SDK311> i16sdklb.exeu-            C:\ACMSDI\SDK311> del i16sdklb.exea  @            If you want the DLL version, first get the sources asB            above, then get the other archive i16sdkdl.exe, and runE            it. This overrides the static-link makefiles. For example:l  A            C:\ACMSDI\SDK311> copy e:\intel16\Samples\i16sdkdl.exe )            C:\ACMSDI\SDK311> i16sdkdl.exe -            C:\ACMSDI\SDK311> del i16sdkdl.exes  /            Table A-6 shows the resulting files.a  @      6.2.7 Verifying the Client Services Installation on Windows            3.11r  @            Compile, link, and run the source code for the sample<            client program to verify your capability to build@            applications. You need the following products on yourE            desktop system to build the C language sample application:m  ?            o  Compiler (preferably Microsoft C) that can accessvC               objects compiled by Microsoft Visual C++ Version 1.52e               or higher   A            o  C runtime library that is compatible with Microsoft %               Visual C++ Version 1.52   <            o  Microsoft Windows for Workgroups Version 3.11.  E            o  If building against static link libraries, you need then=               PATHWORKS Version 5.1 Software Developer's Kit.   A            To verify the installation of the TP Desktop Connectorf@            client services for Windows 3.11, follow these steps:  E            1. Using the AVERTZ makefile, build the sample applicationeA               by running nmake in the directory that contains the                sample files.h  R      6-10 Installing the TP Desktop Connector Client Services on Non-Win32 Systems                 2                  C:\ACMSDI\SDK311> nmake -f avertz  ?               2. Run Windows by entering the following command:   &                  C:\ACMSDI\SDK311> win  ?               3. Run the AVERTZ program by one of the following                   methods:0  (                  o  Use the Run command:  G                     a. In the Program Manager File menu, select the Rung                        command.1  ?                     b. In the dialog box that appears, type the                          location:  ,                        \ACMSDI\SDK311\avertz  H                  o  Add the AVERTZ program icon to the screen and double                      click on it:  G                     a. In the Program Manager File menu, select the New                         command.s  G                        This creates a group window to contain the icon.o  F                     b. In the dialog box, select the new program group/                        and click the OK button.0  E                     c. At the description prompt, type a name for the 1                        group window. For example:/  +                        ACMS Desktop Samplese  A                     d. Give a file name for the group window. For                         example:m  .                        C:\ACMSDI\SDK311\sample  H                        After you enter the name, a window appears having-                        the group window name.n  B                     e. Click on the new group window to select it.  E                     f. In the Program Manager's File menu, select the F                        New command to add the AVERTZ icon to the group                        window.  B                     g. In the dialog box, select new Program Item.  H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-11 e  n            E                  h. In the description prompt, type the icon caption.                       For example:                       AVERTZ  D                  i. After the command-line prompt, type the location?                     of the AVERTZ executable file. For example:_  $                     C:\ACMSDI\SDK311  ;                  j. In the dialog box, click the OK button.   @                     The AVERTZ icon appears in the group window.  B                  k. Double click the AVERTZ icon to run the sample#                     client program._  A            The AVERTZ program displays the menu bar of the AVERTZ3-            Vehicle Rental System application.   ;            If you want the sample desktop client program to <            communicate with the ACMS application, follow the;            procedures in Section 6.3.3 to set up the samplee?            application on the ACMS system. After you set up the C            ACMS system, use the Session menu to sign in to the ACMS D            system. After you sign in, you can use the Rental menu to:            run the reserve task of the AVERTZ application.  B            The Windows 3.11 installation procedure is now complete            and verified.  9      6.2.8 Installing the PowerBuilder Sample Application   A            There is a PowerBuilder Version 5.0 sample application_;            provided as a self-extracting archive file namedlC            i16pbkit.exe. This sample is a simplified version of theeD            original Avertz for Windows; it illustrates the execution0            of an ACMS task with no exchange I/O.  D            The archive provides a PowerBuilder library, pbaverz.pbl,@            that contains the PowerBuilder objects for the Avertz>            client application, and a dynamic-link library, pb-A            pointr.dll that is required for memory management when A            building PowerBuilder applications that use TP Desktop /            Connector gateway for ACMS services.n  R      6-12 Installing the TP Desktop Connector Client Services on Non-Win32 Systems                 G               If you install the software from the TPware Product SuiteeF               CD (see Section 5.1), transfer the archive file from theD               Windows NT system to your desktop system. For example:  $               C:\ACMSDI> mkdir pbsmp!               C:\ACMSDI> cd pbsmpM;               C:\ACMSDI\PBSMP> copy e:\intel16\i16pbkit.exed  D               If you install the software from the Software ProductsG               Library CD (see Section 3.2.2.2), change directory to thec3               location containing the client files.f  C               To install the software, execute the archive file ande;               delete it to recover disk space. For example:r  +               C:\ACMSDI\PBSMP> i16pbkit.exeD/               C:\ACMSDI\PBSMP> del i16pbkit.exeh  F               Table A-7 lists the files that are added to your system.E               For instructions on using the PowerBuilder sample, reads6               the three .doc files shown in Table A-7.  =         6.2.9 Installing the Visual Basic Sample Applicationsb  E               There are two Visual Basic sample applications providedsD               in the form of self-extracting archive files. The fileF               \intel16\Samples\i16vbavz.exe contains the files for theH               same sample that was provided for ACMS Desktop V2.0; it is1               a blocking, no exchange I/O client.   E               The file i16vbfnb.exe (in the same folder) contains the F               files of a tutorial sample showing how to program to theC               new TP Desktop Connector gateway for ACMS forced non- F               blocking interface. This interface allows languages likeD               Visual Basic to issue non-blocking calls to TP DesktopA               Connector gateway for ACMS and provides support forf<               programming ACMS exchange I/O interface calls.  G               If you install the software from the TPware Product Suite F               CD (see Section 5.1), transfer the archive file from theD               Windows NT system to your desktop system. For example:  '               C:\ACMSDI> mkdir vbavertzt$               C:\ACMSDI> cd vbavertz>               C:\ACMSDI\VBAVERTZ> copy e:\Samples\i16vbavz.exe  H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-13 e  c            A            If you install the software from the Software Products D            Library CD (see Section 3.2.2.2), change directory to the0            location containing the client files.  C            To install the sample software, execute the archive filem<            and delete it to recover disk space. For example:  +            C:\ACMSDI\VBAVERTZ> i16vbavz.exet/            C:\ACMSDI\VBAVERTZ> del i16vbavz.exeP  B            Table A-8 lists the files added to your system from theD            Avertz archive; Table A-9 lists the files from the Forced             Nonblocking tutorial.  B      6.2.9.1 Verifying the Visual Basic Avertz Sample Installation  ;            To verify the success of the Visual Basic samplen>            installation, bring up the Visual Basic development/            environment under Microsoft Windows:_  E            1. Open the VBAVERTZ.MAK project using the Open command ina               the File menu.  B            2. Verify that all the required files were loaded. (See/               the VBAVERTZ.MAK project window):o                    VBAVERTZ.BASo                  MAINMENU.FRMa                  RESERVE.FRM                  SIGNIN.FRM   A               Double click on each entry in the project window toB,               verify that it loads properly.  C            3. Run the interpreted version of VBAVERTZ, by selectingv0               the Start command in the Run menu.  6      6.2.9.2 Verifying the Forced Nonblocking Tutorial  >            To verify the successful installation of the ForcedB            Nonblocking tutorial (from file i16vbfnb.exe), bring up@            the Visual Basic development environment in Microsoft            Windows:   E            1. Open the FNBSAMPL.MAK project using the Open command in                the File menu.  R      6-14 Installing the TP Desktop Connector Client Services on Non-Win32 Systems M  \            C               2. Add files ACMSDI.BAS and FORMS.BAS to the FNBSAMPL>B                  project by selecting Add File from the File menu.  F                 ________________________Note  ________________________  ?                 ACMSDI.BAS and FORMS.BAS were installed on yourc3                 system as described in Section 6.2.a  E                 _____________________________________________________   @               3. Add file CONSTANT.TXT from the C:\VB directory.  H               4. Verify that all of the required files were loaded. (See2                  the FMBSAMPL.MAK project window):                       FORM1.FRM                       FRMLOGIN.FRM                      FRMRECVC.FRM                     ACMSDI.BAS                      CONSTANT.TXT                     FORMS.BASo                     MTEXT.BAS.                     NONBLK.BAS  H                  Double click each entry in the project window to verify(                  that it loads properly.  E               5. Run the interpreted version of FNBSAMPL by selectingo5                  the Start command from the Run menu.e  6         6.3 Installing the Client Services for OpenVMS  E               The client services files for OpenVMS are provided as a E               compressed saveset that you can copy from the TPware CD H               mounted on your desktop platform. After copying the clientH               services software, you decompress the file and restore the               saveset.  F               Follow these instructions to install the client services               for OpenVMS:  D               1. Create the client services directory on the desktop                  system.  E                  Note that this directory must be created from a userb6                  account, not from the system account.  '                  $ create/dir [.acmsdi]r  H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-15 r  a            ;            2. Copy the file to the newly created directory.   &               For OpenVMS VAX systems:  !               $ set def [.acmsdi] 1               $ copy cd:[vmsvax]vms_client.exe [] "               $ run vms_client.exe                  .                  .                  .
      <Return>e1                accept the default output filenamei                  .                  .                  .6               $ backup vms_client.sav/save *.*/log  <>  (               For OpenVMS Alpha systems:  !               $ set def [.acmsdi]33               $ copy cd:[vmsalpha]vms_client.exe [] "               $ run vms_client.exe                  .                  .                  .
      <Return>a1                accept the default output filename                   .                  .                  .6               $ backup vms_client.sav/save *.*/log  <>  C            3. The TP Desktop Connector library is preconfigured foruC               DECnet network access. To build applications that useiD               NetWare or TCP/IP as a transport, you must reconfigure>               the library before creating executable programs.  =               The following steps are necessary to set up thed@               TP Desktop Connector library for NetWare or TCP/IP               access:t  C               a. Remove the DECnet object from the library with thes#                  following command:_  G                  $ library/delete = net_decnet acmsdi$client_objlib.olbC  R      6-16 Installing the TP Desktop Connector Client Services on Non-Win32 Systems a  d            D                  b. For NetWare, insert the NetWare transport accessG                     module into the library with the following command:t  M                     $ library/insert acmsdi$client_objlib.olb net_netware.obj   B                     For TCP/IP, insert the TCP/IP transport accessG                     module into the library with the following command:   K                     $ library/insert acmsdi$client_objlib.olb net_tcpip.obji  B               After these steps, you are ready to build TP DesktopD               Connector applications that use NetWare or TCP/IP as aD               transport. Table A-1 shows the files that are added toC               your desktop system during the installation of the TPe<               Desktop Connector client services for OpenVMS.  <         6.3.1 Installing the Motif Sample Client for OpenVMS  F               To install the Motif sample files on the OpenVMS desktop2               system, perform the following steps:  H               1. Create a directory on the desktop system to contain the9                  sample files and move to that directory:w  -                  $ create/dir [.motif_avertz]m*                  $ set def [.motif_avertz]  ,               2. Copy the Motif sample file.  )                  For OpenVMS VAX systems:   ?                  $ copy cd:[vmsvax.samples]vms_avertz.exe [] <>   +                  For OpenVMS Alpha systems:n  A                  $ copy cd:[vmsalpha.samples]vms_avertz.exe [] <>o  C               3. Decompress the executable and restore the saveset:s  %                  $ run vms_avertz.exer                     .                      .k                     .C         <Return>4                   accept the default output filename                     .l                     .t                     .e=                  $ backup/restore vms_avertz.sav/save *.*/log   H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-17                 B            4. Copy the Motif resource file to your home directory:  9               $ copy m_avertz.dat  sys$login:m_avertz.dats  C            Table A-2 lists the files that are added to your desktop.            system.  =      6.3.2 Verifying the Motif Sample Installation on OpenVMS   @            Compile, link, and run the source code for the sample<            client program to verify your capability to build            applications.  ?            To build the sample application, follow these steps:t  ?            1. If you have MMS, use the MMS makefile provided toeB               build the m_avertz sample application. In the sample=               directory, run MMS using the following command:t                 $ MMS   A               If you download TP Desktop Connector libraries to a C               different location, edit the makefile to indicate theS,               new location of the libraries.                                          R      6-18 Installing the TP Desktop Connector Client Services on Non-Win32 Systems h  a            F                 ________________________Note  ________________________  B                 On OpenVMS Alpha systems, the makefile expects theB                 logical ACMSDI$VMS_ALPHA to point to the directory=                 that contains the TP Desktop Connector client6?                 library. In addition, on OpenVMS Alpha systems,eD                 the first time that the makefile tries to create theA                 DECwindows library, the makefile fails. When thisr;                 happens, rerun MMS to continue the build.<>i  E                 _____________________________________________________o  G                  If you do not have MMS, use the makefile as a guide tor0                  build the application yourself.  G               2. Run the application by entering the following command:g  '                  > run m_avertz/nodebugt  C               The m_avertz application displays the menu bar of the C               AVERTZ Car Reservation System. If you want the sample A               desktop client program to communicate with the ACMS H               application, follow the procedures in Section 6.3.3 to setE               up the sample application on the ACMS system. After youcH               set up the ACMS system, use the Session menu to sign in toH               the ACMS system. After you sign in, you can use the RentalE               menu to run the reserve task of the AVERTZ application.l  F               The installation procedure is now complete and verified.  A         6.3.3 Setting Up the Avertz ACMS Sample Application on an1               OpenVMS System  G               The command procedure VR_DA_RUNTIME_SETUP.COM sets up the F               sample application. You need SYSPRV privilege to run theG               procedure. See the file ACMSDI$VR_APPLICATION_INFO.TXT in G               the ACMSDI$EXAMPLES_AVERTZ directory for more informationn'               on setting up the sample.   B               To prepare the AVERTZ sample application on a Compaq/               OpenVMS system, do the following:   E               1. Run the command procedure to set up the application:V    H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-19                 ;               $ @ACMSDI$EXAMPLES_AVERTZ:VR_DA_RUNTIME_SETUP                   .                  .                  .               $d  C            2. Start the ACMS system (if necessary) and the applica-e               tion:g  !               $ ACMS/START SYSTEMk1               $ ACMS/START APPLICATION VR_DA_APPLe  D            3. Perform other management tasks related to your system,B               for example, authorizing user accounts. Refer to theC               management information in Compaq TP Desktop Connector <               for ACMS Client Application Programming Guide.  @            The following sections provide additional information@            about using the Avertz sample application on the ACMS            OpenVMS system.  C      6.3.3.1 Using the Avertz ACMS Sample with Rdb Version 6.0 with               Multi-Version  C            When you execute the VR_DA_RUNTIME_SETUP.COM file to sethC            up the sample application, this command file invokes two E            option files, VR_READ_SERVER.OPT and VR_UPDATE_SERVER.OPT, A            which reference the SYS$LIBRARY:SQL$USER library. On a D            system with Rdb Version 6.0 with multi-version installed,C            the SYS$LIBRARY:SQL$USER file is not available. Instead, ?            the version number is appended to the file name, fort,            instance, SYS$LIBRARY:SQL$USER60.  ?            To work around this naming mismatch problem, you canD<            define the logical name SQL$USER to reference the1            appropriate library file. For example:p  3            $ DEFINE SQL$USER SYS$LIBRARY:SQL$USER60e  +            Modify the linker options files:   7               ACMSDI$EXAMPLES_AVERTZ:VR_READ_SERVER.OPTg9               ACMSDI$EXAMPLES_AVERTZ:VR_UPDATE_SERVER.OPTe              Replace the line   -            SYS$LIBRARY:SQL$USERnn.OLB/LIBRARYp  R      6-20 Installing the TP Desktop Connector Client Services on Non-Win32 Systems e  e            !               with the following:                  SYS$USER/LIBRARY  B         6.3.3.2 Building the Avertz ACMS Sample with DECforms V1.4  F               The VR_FORM.IFDL file of the Avertz ACMS sample applica-G               tion can not be compiled under DECforms Version 1.4. ThiscG               is because the DECforms Version 1.4 IFDL parser no longereE               recognizes the colon symbol (:), which the VR_FORM.IFDLS               file uses.  D               To get around this problem, put double quotation marksB               around the text containing the ":" symbol in the VR_               FORM.IFDL file.p  0               For example, change the following:                        CopyeF                           AVERTZ_CDD_FIELD:CUSTOMER_ID from Dictionary                      End CopyB                 To look like:                         CopywH                           "AVERTZ_CDD_FIELD:CUSTOMER_ID" from Dictionary                      End Copy   ;         6.3.3.3 User Name Quotas for the Avertz ACMS Sample   E               The VR_DA_RUNTIME_SETUP.COM command file assigns quotas B               for the AVERTZ_EXC, AVERTZ_UPD, and AVERTZ_READ user@               names that are adequate for running the VR_DA_APPLG               sample application. If your system already has these userdE               names defined, the quotas for these user names might belD               inadequate for VR_DA_APPL. If you are using the AVERTZD               sample application, delete AVERTZ_EXC, AVERTZ_UPD, andB               AVERTZ_READ user names before running VR_DA_RUNTIME_E               SETUP.COM to ensure that you get appropriate quotas forr               these user names.   C               To ensure the success of the operations in the VR_DA_iB               RUNTIME_SETUP.COM command procedure, run it from the               system account.   H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-21                 ;      6.3.3.4 Access Control List for the Avertz ACMS Samplei  @            The VR_DA_RUNTIME_SETUP.COM procedure adds the AVERTZ@            application name VR_DA_APPL to the ACMS database. The?            command line to do so includes the ACL qualifier anda@            assigns the ID as /ID=SYSTEM. This might fail on your            system.  ?            To ensure that the VR_DA_RUNTIME_SETUP.COM procedure @            works, change the ID=SYSTEM to ID=[UIC], where UIC is=            that of the account SYSTEM; for example, ID=[1,4].f  .      6.3.3.5 Rebuilding the Avertz ACMS Sample  C            Executables are provided for the sample. You do not need/>            to rebuild the sample to run it. However, a DEC/MMSA            description file is provided for rebuilding the samplei=            to incorporate any changes you make to the sample.r  @            To modify and rebuild the sample, follow these steps:  ;            1. Copy the sample sources to another directory.t  <            2. Use the command procedure VR_DA_BLD_MMS.COM toC               rebuild the sample under a different ADB name in thatn               directory:  A               a. Create the CDD directories for the AVERTZ compo-r                  nents.   &               b. Define logical names.  I                  If you are using a directory other than ACMSDI$EXAMPLES_ C                  AVERTZ for rebuilding the sample, edit the logical ?                  name definitions in the VR_DA_BLD_LOGICALS.COMe@                  command procedure to point to your file and CDDE                  directories. Make these edits before running the BLD D                  portion of the VR_DA_BLD_MMS.COM command procedure.  :               c. Perform other setup and build activities.  A            3. Run the command procedure VR_DA_BLD_MMS.COM withoutp               parameters:c  .               $ @ACMSDI$EXAMPLES:VR_DA_BLD_MMS  ?               All the setup and build activities are performed.x  R      6-22 Installing the TP Desktop Connector Client Services on Non-Win32 Systems l  a            @               To perform a specific activity, specify one of the&               parameters in Table 6-3.    H               Table_6-3_VR_DA_BLD_MMS.COM_Parameters____________________  H               Keyword__________Activity_________________________________  :               BLD              Run MMS to build VR_DA_APPL  H               CDD              Set up the CDD dictionary and directories-                                for VR_DA_APPL   H               DB_______________Create_the_VEHICLE_RENTALS_database______  5         6.4 Installing the Tru64 UNIX Client Softwaree  A               The TP Desktop Connector client services and sampleMH               application files are distributed on the Software ProductsG               Library CD and on the TPware Product Suite CD. If you are F               installing the software from the TPware Product Suite CDE               (see Section 6.1), you have archive (tar(1)) files thatnE               you install on a Tru64 UNIX desktop system. Perform thel               following steps.  D               1. Create the client services directory on the desktopC                  system, and change to that directory. For example:n                    > mkdir acmsdi                   > cd acmsdi  G               2. Copy the archive file from the TPware CD to the client 1                  services directory. For example:o  .                  > cp e:/dunix/du_client.tar .  H               If you install the client files from the Software ProductsG               Library CD (see Section 3.2.2.3), change directory to thenD               location of the tar files that you placed on the Tru64               UNIX system.  G               The du_client.tar archive file contains the client files.e*               Perform the following steps.  A               1. Extract the files from the archive. For example:   H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-23    t            +               acmsdi> tar xvf du_client.tar                   .                  .                  .  D               The list of files printed because of the v flag should4               match the list of files in Table A-10.  A            2. If you want to use the DECnet transport, change the *               client library. For example:                 > su,               # ar d libacmsdi.a net_tcpip.o-               # ar r libacmsdi.a net_decnet.oe                # ar t libacmsdi.a                  .                  .                  .!               # ar qs libacmsdi.ae  >               Also edit the Makefile to add -ldnet to the link               library list.i  O            3. You can copy the client services library to /usr/lib/libacmsdi.a, D               so that you can refer to it in your link command as '-B               lacmsdi'. You need superuser privileges to copy into%               the /usr/lib directory.   A               Copy the TP Desktop Connector client library to thei               system directory:   3               # cp libacmsdi.a /usr/lib/libacmsdi.ae                  .                  .                  .  C               You can leave the TP Desktop Connector library in theuE               client services directory. If you do, use the full path C               to the library in your link command, instead of usingi$               the '-lacmsdi' option.  -            4. Update the copied library file:   *               # ar qs /usr/lib/libacmsdi.a  R      6-24 Installing the TP Desktop Connector Client Services on Non-Win32 Systems c  v            %               5. Exit superuser mode:l                    # <Ctrl/D>                   >  E               See Section 6.4.1 for instructions on installing samplet               files.  >         6.4.1 Installing the Motif Sample Client on Tru64 UNIX               Platformse  A               To install the Motif sample files on the Tru64 UNIX 2               system, perform the following steps:  H               1. Create a directory on the desktop to contain the sample2                  files and move to that directory:                    > mkdir avertzh                  > cd avertz  E               2. Copy the sample archive from the TPware products CD:   .                  > cp e:\dunix\du_avertz.tar .  *               3. Extract the sample files:  (                  > tar xvf du_avertz.tar                     .c                     .                      .I  C                  The list of files printed should match the list ine                  Table A-11.  D               The sample makefile and executables for Motif on Tru64C               UNIX use TCP/IP as the default transport. If you have D               changed the client services library to use DECnet, youC               must relink the sample application before you run it.   C         6.4.2 Verifying the Motif Sample Installation on Tru64 UNIX1               Platformso  C               Compile, link, and run the source code for the sample ?               client program to verify your capability to buildsC               applications. To build the sample application, followa               these steps:  G               1. Use the makefile provided to build the m_avertz sample @                  application. In the sample directory, run make:  H  the      TP Desktop Connector Client Services on Non-Win32 Systems 6-25                                > make  D            2. Run the application by entering the following command:                 > m_avertz  @            The m_avertz application displays the menu bar of the@            AVERTZ Car Reservation System. If you want the sample>            desktop client program to communicate with the ACMSE            application, follow the procedures in Section 6.3.3 to set B            up the sample application on the ACMS system. After youE            set up the ACMS system, use the Session menu to sign in to E            the ACMS system. After you sign in, you can use the Rental B            menu to run the reserve task of the AVERTZ application.  C            The installation procedure is now complete and verified.i                                                          R      6-26 Installing the TP Desktop Connector Client Services on Non-Win32 Systems X  s                  H                                                                        7H         ________________________________________________________________  H                  Installing the TP Desktop Connector Client Services forH                                                        Macintosh Systems      G               This chapter describes the installation of the TP Desktop>G               Connector client services and samples for Apple Macintosh                clients.  D               After you install the TP Desktop Connector gateway forA               ACMS software on the Compaq OpenVMS system, you cancG               install the TP Desktop Connector client services softwareM,               on individual desktop systems.  *         7.1 Macintosh Installation Options  @               You can choose any of several installation optionsC               depending on the type of services you want to installf&               on the target Macintosh:  )               o  Run-Time Services option   E                  Permits the execution of TP Desktop Connector clientiB                  applications, but does not include files that areA                  helpful for developing new applications. You cantF                  install Run-Time Services with or without the CalypsoH                  Tool, which provides support for dialin applications toG                  the host ACMS Desktop server. Choose this option (withPD                  or without Calypso) if you do not intend to developD                  new TP Desktop Connector applications on the target                  Macintosh.   '               o  System Services optiong  H                  Includes the Run-Time Services plus a set of files thatD                  aids in the development of new TP Desktop ConnectorB                  client applications on the target Macintosh. ThisB                  option does not include the various examples thatF                  illustrate the use of the TP Desktop Connector clientF                  services. Choose the System Services option if you do  H  the      TP Desktop Connector Client Services for Macintosh Systems 7-1                 E               not require the assistance of the examples, and want toM?               conserve the disk space that the examples occupy._                                                                                      R      7-2 Installing the TP Desktop Connector Client Services for Macintosh Systems                                 o  Examples option  (                  Includes the following:  A                  -  Sample applications written in 4th Dimension, %                     HyperCard, and C.C  G                  -  Two sets of 4th Dimension Externals that invoke thetF                     TP Desktop Connector client services, one of whichE                     includes C source code to illustrate how to writep5                     your own 4th Dimension Externals.   G                  -  A set of HyperCard XFCNs that invoke the TP DesktophG                     Connector client services, including C source code.e  C                  -  A set of utility files containing C source code G                     for date and data conversion functions and programs A                     useful in managing your development platform.   F                  You can install the Examples option separately, after2                  installing the Run-Time Services.  7         7.2 Preparing to Install the Macintosh Softwarer  F               This section describes the preparations and requirementsE               for installing the TP Desktop Connector client servicest-               software for Macintosh systems.e  9         7.2.1 Prerequisite Software for Macintosh Systemsn  @               Before you install the software, do the following:  G               1. Install TP Desktop Connector gateway for ACMS softwarei=                  on the OpenVMS system running ACMS software.   E               2. If you choose to use a VAXshare volume as the source ?                  from which to copy the client software to your D                  Macintosh, identify a disk device on which to build#                  a VAXshare volume.   B                  If you choose not to use a VAXshare volume as the?                  source from which to copy the client software:s  D                  a. Install a file transfer tool such as XMODEM or aC                     DECnet file server on your host OpenVMS system.o  F                  b. Install a corresponding file transfer tool such as<                     MacTerminal or NetCopy on the Macintosh.  H  the      TP Desktop Connector Client Services for Macintosh Systems 7-3 V  s            B            3. Install the appropriate Communications Tools on your;               Macintosh for the transports you plan to use:   &               -  AppleTalk-DECnet Tool  4                  To use the AppleTalk-DECnet Gateway                 -  DECnet Tool  :                  To manage your Macintosh as a DECnet node                 -  MacTCPA  9                  To use a TCP/IP communications transportn  $               -  AppleTalk ADSP Tool  C                  To manage your host OpenVMS node as a socket in an #                  AppleTalk Interneto  =               -  A tool that implements serial communications.@                  protocols, such as the Serial Tool or the Apple                  Modem Tool.  -                  To use serial communicationsp  D            4. If you plan to manage your OpenVMS node as a socket inD               an AppleTalk Internet, install the PATHWORKS AppleTalk;               for OpenVMS Transport on your OpenVMS system.   @            5. Log in to the OpenVMS system using an account with@               sufficient privileges. Using the SYSTEM account is               recommended.        7.2.2 Disk Space   C            The required disk space on your Macintosh depends on the B            installation option you choose, as listed in Table 7-1.              R      7-4 Installing the TP Desktop Connector Client Services for Macintosh Systems e  e            H               Table_7-1_Macintosh_Disk_Space_Requirements_______________  H               Option_____________________Disk_Space_____________________  4               Run-Time Services           138K bytes  4               Run-Time Services and       263K bytes               Calypsoo  4               System Services             183K bytes  4               System Services and         308K bytes               CalypsoD  4               Examples                   2612K bytes  4               System Services, Calypso,  2920K bytesH               and_Examples______________________________________________  -         7.3 Installing the Macintosh Software   B               This section describes how to install the TP DesktopC               Connector client services software for Macintosh on a.               Macintosh system.e  ?         7.3.1 Copying the TP Desktop Connector Installer to then               Macintosh   B               All the files that comprise the TP Desktop ConnectorC               Macintosh client software are compacted into a single >               installation file, ACMSDI_DESKTOP.INSTALLER. TheE               installation procedure consists of the following steps:l  C               1. Copy or FTP ACMSDI_DESKTOP.INSTALLER to the target                   Macintosh.i  1               2. Double click the installer file.   <               3. Follow the instructions that are displayed.  @               The files on the TPware Product Suite and SoftwareE               Products Library CDs are in MacBinary format. Many fileeA               transfer facilities such as NetCopy and MacTerminal D               automatically convert files from MacBinary to standardE               Macintosh format as part of the copy operation. If your E               file transfer utility does not automatically do so, uselF               a tool such as MacBinary Converter (mBin) to convert theC               ACMSDI_DESKTOP.INSTALLER to standard Macintosh format                 after you copy it.  H  the      TP Desktop Connector Client Services for Macintosh Systems 7-5    l            J            After you have successfully copied the ACMSDI_DESKTOP.INSTALLER<            file to your Macintosh, proceed to Section 7.3.2.  ?      7.3.2 Running the TP Desktop Connector Macintosh InstallerD  A            The ACMSDI_DESKTOP.INSTALLER file is a self-extracting A            file containing all the TP Desktop Connector Macintosh ;            client services files in compressed form. During =            installation, files are automatically moved to the A            appropriate folders. The installation process provides '            instructions with each step:,  B            1. Begin the installation process by double clicking on               the ,               ACMSDI_DESKTOP.INSTALLER file.  @            2. A window appears that identifies the product as TPB               Desktop Connector Version 2.3. Click on the Continue               button.   D            3. A second window appears containing a copyright notice.>               Read the copyright notice. Buttons are available=               to save or print the notice. You can cancel thel?               installation at this point by clicking the Canceli?               button, in which case nothing is installed. ClickeA               the Continue button if you want to proceed with thea               installation.   A            4. The next window provides some information about therE               installer. It tells you where the files to be installed =               will be placed and tells how much disk space ish@               required for the (standard) full installation. TheA               Calypso Tool mentioned is the software that enabless>               serial (dialin) communication between TP DesktopE               Connector client applications and the host ACMS Desktop                server.   B               You have three buttons to choose from at this point:                 a. Custom button:L  B                  Allows you to proceed to another window where youC                  can choose which parts of the software you want to                   install.                  b. Quit button:   R      7-6 Installing the TP Desktop Connector Client Services for Macintosh Systems V  A            H                     Allows you to cancel the installation at this point;)                     nothing is installed.t  #                  c. Install button:t  F                     Causes a full installation to occur; everything is                     installed.  E                  If you want a standard, full installation, click the G                  Install button now, and skip to step 6. If you want touH                  examine additional options, click the Custom button and#                  proceed to step 5.T  F               5. If you choose a custom installation, a window appearsH                  with six installation options. Text appears to describeC                  each option and how much disk storage it requires. H                  Section 7.1 presents a more complete description of the&                  installation options.  G                  -  System Services, Calypso, and Examples: This option H                     installs everything. It is identical to the standardB                     installation presented on the previous window.  D                  -  System Services: This option installs everything=                     except the examples and Calypso software.   E                  -  System Services and Calypso: This option installsn3                     everything except the examples.w  E                  -  Examples: This option installs the examples only.aB                     Use it as a follow-up installation to a systemH                     services or run-time services option with or without                     Calypso.  D                  -  Run-Time Services: This option installs only theC                     basic software needed for run-time support. The B                     development aids, the Examples and the Calypso/                     software are not installed.a  G                  -  Run-Time Services and Calypso: This option installstB                     the basic software needed for run-time supportF                     and the Calypso software. The development aids and/                     examples are not installed.   C                  You again have three buttons from which to choose:   $                  a. Standard button:  E                     Allows you to return to the standard installation                      window.o  H  the      TP Desktop Connector Client Services for Macintosh Systems 7-7 i  e                           b. Quit button:d  E                  Allows you to cancel the installation at this point;t&                  nothing is installed.                  c. Install button:  C                  Cause an installation to occur. Before clicking on D                  this button, select one of the installation options3                  by clicking on it to highlight it.I  E            6. Clicking on the Install button from either the standardoE               or custom installation window causes a window to appear A               from which you can select the location to place theuC               folder "TP Desktop Connector folder (2.3)". All filesl?               except the DDEV and Calypso Tool are installed in A               this folder. Clicking the Cancel button cancels the ?               installation, in which case nothing is installed.oA               Clicking the Save button causes the installation toi7               occur, as indicated by a progress window.l  E            7. If the installation is successful, a dialog box appearsUC               indicating success. From this window, you can quit or 5               continue with additional installations.                                           R      7-8 Installing the TP Desktop Connector Client Services for Macintosh Systems                       H                                                                 Part IIIH         ________________________________________________________________  H                                                     Using the Gateway CD        H               Part III describes Compaq TP Desktop Connector Gateway forF               ACMS software installation from the TP Desktop Connector7               Gateway for ACMS CD on an OpenVMS system.   D               This part covers the server-side software and samples,?               but not the client-side software and samples. For C               installations using the Software Products Library CD, D               see Part I. For installations using the TPware Product$               Suite CD, see Part II.    o                  H                                                                        8H         ________________________________________________________________  H               Preparing to Install TP Desktop Connector Gateway for ACMSH                                                                 Software      F               This chapter discusses the preparations and requirementsB               necessary for installing Compaq TP Desktop ConnectorE               gateway for ACMS software. Your bill of materials (BOM)lD               and indented bills report (BIL) specify the number andG               contents of your media. Be sure to verify the contents ofoG               your kit with this information. If your kit is damaged orm=               incomplete, contact your Compaq representative.e  D               The gateway software includes online Release Notes andH               gives you the option of printing or displaying them duringD               the installation procedure. Compaq strongly recommendsH               that you read the Release Notes before proceeding with theF               installation, in case they contain important information3               regarding the installation procedure.   0         8.1 Required Operating System Components  C               To install gateway software, you must have one of the 4               following operating systems installed:  *               OpenVMS VAX operating system                 o  Version 5.5-2                 o  Version 6.2                 o  Version 7.1                 o  Version 7.2 <>r  ,               OpenVMS Alpha operating system                 o  Version 6.2                 o  Version 7.1                 o  Version 7.2 <>e  H  Preparing to Install TP Desktop Connector Gateway for ACMS Software 8-1                       8.2 Prerequisite Software  B            The Software Product Description (SPD), a copy of which=            is included in the product kit, contains a list ofn@            the prerequisite software, and a complete list of theD            products that are compatible with this version of gateway            software.  ,      8.3 Installation Procedure Requirements  D            The installation procedure, VMSINSTAL, checks for various>            conditions on your system. If VMSINSTAL detects any?            problems during the installation, it notifies you ofe@            the problem and asks whether you want to continue theA            installation. In some instances, you can answer YES tofE            continue. To stop the installation process and correct theT3            situation, answer NO or press <Return> .   @            You can avoid having to stop and restart VMSINSTAL by>            following the directions in this section before youB            run VMSINSTAL. The time required for installing gateway2            software is approximately five minutes.        8.3.1 Disk Space   @            Installing gateway software requires a certain amountC            of free storage space during the installation. Table 8-1iC            summarizes the storage requirements for gateway softwareC)            during and after installation.o  E            Table_8-1_Disk_Space_Requirements_________________________e  /                                          BlocksrC                                          During        Blocks AfteriE            ______________________________Installation__Installation__p  E            Gateway_______________________23_304_________6_500________   E            To determine the number of free disk blocks on the current >            system disk, enter the following command at the DCL            prompt:  &            $ SHOW DEVICE SYS$SYSDEVICE  D            In the output column under the heading Free Blocks is the=            number of 512-byte blocks available on the device.   L      8-2 Preparing to Install TP Desktop Connector Gateway for ACMS Software                 *         8.3.2 Privileges and Authorization  F               To install gateway software, you must be logged in to an4               account with the following privileges:                    NETMBXi                  SETPRVh                  TMPMBXl  G               The SYSTEM account has all the privileges you require forn               the installation.   F               VMSINSTAL turns off the BYPASS privilege at the start ofD               the installation and sets whatever privileges it needs&               during the installation.  F               At the end of the installation procedure, if the gatewayF               system components were installed, the gateway process onF               OpenVMS is started using the same user name that you useH               to install the product. Compaq recommends that you run theE               gateway under the user name SYSTEM or another user name                with a [1,4] UIC.s  A               For the gateway process to be properly started, theTD               user name under which the installation is done must beB               an authorized ACMS agent. Use the ACMSUDU Utility to3               authorize the user name. For example:w  &               $ SET DEFAULT SYS$SYSTEM               $ RUN ACMSUDU #               UDU> ADD SYSTEM/AGENT                UDU>  E               If the user name is not authorized as a ACMS agent, the C               IVP can fail and TP Desktop Connector client programs @               cannot sign in to the ACMS system. To allow clientG               programs to successfully sign in to the ACMS system, stop F               the gateway, and restart it under a user name that is an$               authorized ACMS agent.            H  Preparing to Install TP Desktop Connector Gateway for ACMS Software 8-3    a            .      8.3.3 OpenVMS License Management Facility  >            The gateway supports the OpenVMS License ManagementD            Facility (LMF). To install gateway software on an OpenVMS;            system, you must register your software license.f  C            LMF requires registration of a Product Authorization Key ?            (PAK). The license registration information you need ?            is contained in the PAK that is shipped with gatewaykA            software. The PAK is a paper certificate that containsyE            information about the license you have to run a particulari            piece of software.   ?            Register your gateway license before you perform then?            installation. During the installation, you are asked E            whether you have registered the gateway license and loaded C            the appropriate authorization key. You cannot run eithereA            the gateway software or its IVP unless your license islA            loaded. After you perform the license registration and E            load an authorization key, you can run the IVP and use theo            gateway software.  D            To register a license, first log in to the system managerA            account, SYSTEM. You then have a choice of two ways to             register:  B            o  Run the SYS$UPDATE:VMSLICENSE.COM procedure. When itA               prompts you for information, respond with data from                your PAK.   E            o  Issue the LICENSE REGISTER command with the appropriate C               qualifiers that correspond to information on the PAK.   A            For complete information on using LMF, see VMS Licenser%            Management Utility Manual.         8.3.4 System Disk Backup_  ?            At the beginning of the installation, VMSINSTAL asks_C            whether your system disk is backed up. Compaq recommendsiD            that you always do a system disk backup before installing0            new software on the operating system.  A            Use the backup procedures that are established at yourtE            site to do this backup. For details on performing a system D            disk backup, see the section on the Backup Utility in the%            OpenVMS documentation set.   L      8-4 Preparing to Install TP Desktop Connector Gateway for ACMS Software l  g            2         8.3.5 Stopping the ACMS System and Gateway  A               If you have TPware components already installed andeD               running, shut them down. While logged in to the system@               under an account having the appropriate privilegesB               as described in Section 8.3.2, execute the following               commands.   H               1. Stop the TP Web Connector Gateway for ACMS process. For                  example:A  /                  $ @SYS$STARTUP:ACMSDI$SHUTDOWNa                  $  @               2. If you have ACMS software already installed andG                  running, shut it down. Execute the following commands.   6                  a. Stop the ACMS system. For example:  '                     $  ACMS/STOP SYSTEMa                        .                        .                        .                     $a  :                  b. Stop the ACMS controller. For example:  +                     $  @SYS$STARTUP:ACMSTOP                         .                        .                        .                     $t  ,         8.3.6 Locating the Saveset Directory  D               If you have not already inserted the compact disk (CD)/               media in the CD drive, do so now.   E               To obtain the directory location of the saveset for theoB               gateway software on the CD-ROM, refer to the OpenVMSD               Layered Products Compact Disc User's Guide, or, before>               starting the installation, complete these steps:  A               1. To determine whether the CD-ROM drive is already @                  mounted (MOUNT command), enter a command in the"                  following format:  (                  SHOW DEVICE device-name  H  Preparing to Install TP Desktop Connector Gateway for ACMS Software 8-5 c  n            B            2. If the device is not mounted, enter a command in the               following format:   +               MOUNT/OVERRIDE=ID device-nameo                 For example:  )               $ MOUNT/OVERRIDE=ID DKA200:e  ?            3. Locate the distribution files. The directory-nameh:               depends on the OpenVMS platform, as follows:  E               _______________________________________________________eE               OpenVMS_Platform______Directory_Name___________________n  ,               Alpha                 VMSALPHA  E               VAX___________________VMSVAX___________________________o  D            4. To obtain the saveset name, use a DIRECTORY command inD               the following format and specify the saveset name from#               the previous command.c  .               DIRECTORY device-name:ACMSDIA031                                          L      8-6 Preparing to Install TP Desktop Connector Gateway for ACMS Software s                     H                                                                        9H         ________________________________________________________________  H                Installing TP Desktop Connector Gateway for ACMS Software      E               This chapter describes how to install Compaq TP DesktoplG               Connector gateway for ACMS software. Section 9.1 providesiH               helpful information about installing the gateway software.D               Section 9.2 contains a step-by-step description of the%               installation procedure.   ,         9.1 General Installation Information  >               This section includes the following information.  <               o  Accessing Release Notes (see Section 9.1.1)  F               o  Determining the files and logical names added to your+                  system (see Section 9.1.2)   F               o  Running the Installation Verification Procedure (IVP)$                  (see Section 9.1.3)  >               o  Aborting the installation (see Section 9.1.4)  0         9.1.1 Accessing the Online Release Notes  A               The gateway software provides online Release Notes.fA               To activate the prompt about displaying or printingaD               the Release Notes, invoke VMSINSTAL with the OPTIONS N               parameter.  H               After the gateway software has been installed, the ReleaseB               Notes are located in a directory with public access.            H            Installing TP Desktop Connector Gateway for ACMS Software 9-1 h  m            ;      9.1.2 Files and Logical Names Installed on Your Systemo  C            The following files contain a list of the files added to 3            your system by the gateway installation:x  <            SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$FIRST_FILES.DATA            SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_ADD_FILES.DATeD            SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_AVERTZ_FILES.DATD            SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_COMMON_FILES.DATF            SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_EMPLOYEE_FILES.DATG            SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_MACINTOSH_FILES.DATx=            SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SYSTEM_FILES.DATt  E            You can display or print these files after you install then            gateway software.  @            After the installation, if the gateway is started (byE            ACMSDI$STARTUP.COM), the following logical names are addedn            to your system:              ACMSDI$EXAMPLES            ACMSDI$EXAMPLES_ACMS             ACMSDI$EXAMPLES_ADD!            ACMSDI$EXAMPLES_AVERTZ #            ACMSDI$EXAMPLES_EMPLOYEEs             ACMSDI_AVERTZ_DEFAULT            AVERTZ_TDBy  B            These logical names are entered into the system logicalD            name table. The names are used in various gateway startup?            files. Thus, they are automatically entered into theiA            system logical name table whenever the gateway startupi$            command file is executed.  .      9.1.3 Installation Verification Procedure  <            The Installation Verification Procedure (IVP) forA            gateway software verifies the installation. During theo>            installation, you are asked whether you want to runB            the IVP as part of the installation. If you answer YES,E            VMSINSTAL runs the IVP. It is recommended that you run thesC            IVP to be sure that the software is installed correctly.r  B            After you install the gateway software, you can run theE            IVP independently to verify that the software is available C            on your system. You might also want to run the IVP afteroD            a system failure to be sure that users can access gateway  B      9-2 Installing TP Desktop Connector Gateway for ACMS Software                 H               software. See Chapter 11 for information about running the=               IVP separately from the installation procedure.f  '         9.1.4 Aborting the Installationh  D               To abort the installation procedure at any time, pressB               <Ctrl/Y> . When you press <Ctrl/Y>, the installationC               procedure deletes all files it has created up to that7B               point and exits. You can then start the installation               again.  "         9.2 Installation Procedure  H               Perform the steps in the following sections to install the               gateway software.I            9.2.1 Invoking VMSINSTAL  C               Perform the following steps to start the installation                process.  C               1. Log to a privileged account (see Section 8.3.2 for_G                  details) and set the default to the desired directory.                   For example:h  )                  $ SET DEFAULT SYS$UPDATEd                  $  4                  SYS$UPDATE is used in this example.  >               2. Use the following syntax to invoke VMSINSTAL:  G                  @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONSs	         Ns  G                  The parameter saveset-name represents the installationmF                  name for the component. For the gateway software, use1                  the following installation name:n                    ACMSDIA  A                  If you do not supply the saveset name, VMSINSTAL H                  prompts you for it later in the installation procedure.  E                  The parameter device-name represents the location of E                  the saveset files (see Section 8.3.6). If you do not C                  supply device-name, VMSINSTAL prompts you for thiseA                  information later in the installation procedure.e  H            Installing TP Desktop Connector Gateway for ACMS Software 9-3                 D               OPTIONS N is an optional parameter indicating that youA               want to be prompted to display or print the Release C               Notes. If you do not include the OPTIONS N parameter, C               VMSINSTAL does not prompt you to display or print the                Release Notes.  ;               VMSINSTAL supports several other options. Fora@               information, refer to the OpenVMS documentation on$               software installation.  >            3. Execute the installation procedure. For example:  D               $ @SYS$UPDATE:VMSINSTAL ACMSDIA DKA200[KIT]: OPTIONS N  @               This command begins installing the ACMSDIA saveset?               found in the directory KIT on the CD device namedu               DKA200.u  E            VMSINSTAL asks several installation questions as describedw            in Section 9.2.2.  !      9.2.2 Installation Questionsy  B            This section discusses the questions that appear duringA            the installation. Each question in the installation is E            marked with an asterisk (*)  at the beginning of the line. @            Some questions show the default response in brackets,B            for example, [YES]. To give the default response, press            <Return> .l  )            1. Confirming active processesa  @               VMSINSTAL displays a list of all active processes.;               It then asks whether you want to continue the =               installation. Install the gateway software on a @               standalone system or cluster with DECnet shut down9               to minimize possible installation problems.f  L               %VMSINSTAL-W-ACTIVE, The following processes are still active:                  .                  .                  .9               * Do you want to continue anyway [NO]?  YEST  #            2. Confirm system backupi  B      9-4 Installing TP Desktop Connector Gateway for ACMS Software    t            C                  VMSINSTAL asks whether you are satisfied with your F                  system backup. Always back up your system disk beforeF                  performing an installation. If you are satisfied withH                  the backup of your system disk, press <Return> . AnswerF                  NO to discontinue the installation. After you back up<                  your system disk, restart the installation.  O                  * Are you satisfied with the backup of your system disk [YES]?s  #               3. Mounting the mediat  >                  VMSINSTAL now displays the CD device name and@                  asks whether you are ready to continue with the                  installation.  ?                  Answer YES to indicate that the CD is mounted.eG                  VMSINSTAL displays a message that the media containing H                  gateway software is mounted on the specified device andA                  that the installation is beginning. For example:I  E                  Please mount the first volume of the set on DKA200:._%                  * Are you ready? YESn<                  %MOUNT-I-MOUNTED, ACMSDI mounted on DKA200:  :                  The following products will be processed:                      ACMSDIA V3.1E  H                          Beginning installation of ACMSDIA V3.1 at 13:14  F                  %VMSINSTAL-I-RESTORE, Restoring product save set A...  C                  If you enter the wrong device name when you invoke G                  VMSINSTAL and need to restart the installation, answer C                  NO in response to the Are you ready? question. See C                  Section 8.3.6 for instructions on mounting the CD.   C                  To abort the installation for other reasons, press                   <Ctrl/Y> .t                 4. Release Notes  G                  If you specified OPTIONS N when you invoked VMSINSTAL,fB                  you see several options for reviewing the Release<                  Notes. The following options are displayed:  H            Installing TP Desktop Connector Gateway for ACMS Software 9-5 f  e            Q               Release Notes included with this kit are always copied to SYS$HELP.   /               Additional Release Notes Options:u  *                   1. Display release notes(                   2. Print release notes!                   3. Both 1 and 2Y&                   4. None of the above  $               * Select option [2]: 1                 o  Option 1r  ?                  If you select option 1, VMSINSTAL displays thelC                  Release Notes immediately on the console terminal.h=                  You can terminate the display at any time byr>                  pressing <Ctrl/C> . Because the Release NotesC                  are several pages long, it is recommended that you B                  choose option 2 to print the Release Notes rather-                  than reviewing them on line.                  o  Option 2r  B                  If you select option 2, VMSINSTAL prompts for the0                  name of the print queue to use:  *                  * Queue name [SYS$PRINT]:  >                  Enter the name of an ANSI print queue on yourB                  system, or press <Return> to send the file to the@                  default queue shown within the square brackets.                 o  Option 3m  ?                  If you select option 3, VMSINSTAL displays the C                  Release Notes and prompts for a queue name for the !                  printed version.m                 o  Option 4c  @                  If you select option 4, VMSINSTAL continues the                  installation.      B      9-6 Installing TP Desktop Connector Gateway for ACMS Software P  t            ,               5. Continuing the installation  D                  The installation procedure asks whether you want toD                  continue the installation. To continue, answer YES.H                  Otherwise, press <Return> . In either case, the ReleaseF                  Notes are copied to a file in the SYS$HELP directory.                  For example:e  E                  * Do you want to continue the installation [N]?: YESy\                  %VMSINSTAL-I-RELMOVED, Product's Release Notes have been moved to SYS$HELP.  L                   Digital Equipment Corporation. 1998. All Rights Reserved.  @                  The name of the Release Notes file installed byC                  VMSINSTAL consists of the current product name andn@                  version number. If you plan to compare previousH                  versions of gateway software, do not delete the Release<                  Notes for previous versions of the gateway.  (               6. Choosing to purge files  B                  You can purge files from previous versions of theB                  gateway that are superseded by this installation.E                  Purging is recommended, however, if you need to keeptH                  files from a previous version, answer NO in response to                  this question:_  R                  * Do you want to purge files replaced by this installation [YES]?  (               7. Choosing to run the IVP  E                  If you are installing the gateway system components,lH                  the installation procedure asks whether you want to runG                  the IVP. The IVP checks that the software is installed C                  correctly. It is recommended that you run the IVP.k  O                  * Do you want to run the IVP after the installation [YES]? YESs  G                  Press <Return> to run the IVP after installing gateway A                  software. Answer NO to omit the IVP. Run the IVPmB                  independently after the installation to check theD                  consistency of the gateway software. See Chapter 11A                  for information about how to run the gateway IVPt=                  independently of the installation procedure.u  1               8. Installing Macintosh sample code   H            Installing TP Desktop Connector Gateway for ACMS Software 9-7    e            C               You have the option of installing the gateway samples )               for the Macintosh platform.e  E               * Do you want to install the Macintosh sample [YES]? NOh  E               Press <Return> to load the server-side Macintosh samplexB               application code in the [.MACINTOSH] subdirectory ofB               the ACMSDI$EXAMPLES directory. Answer NO to omit theA               Macintosh sample code. Note that only the MacintoshoA               samples are optional; the Add, Avertz, and Employee C               server-side sample files are installed automatically.   -            9. Confirming license registrationt  B               VMSINSTAL asks whether you have a PAK installed. YouA               can install gateway software prior to registration;nB               however, the software is unusable until you register               the license.  @                Looking up the Product Authorization Information.  3                      Product:       TP-DESKTOP-ACMS '                      Producer:      DECm'                      Version:       3.1 /                      Release Date:  18-AUG-1999   V               * Does this product have an authorization key registered and loaded? YES  B               If you answer NO, the installation completes but theB               IVP is not run. If you answer YES and the license is,               not registered, the IVP fails.  !      9.2.3 Informational Messages   ?            At this point, the installation procedure displays ai>            number of informational messages that report on theB            progress of the installation and advise about different?            uses of the product. There are no further questions.r              B      9-8 Installing TP Desktop Connector Gateway for ACMS Software _               c               %ACMSDI-I-PROCEED, There are no further questions and all checks have been completed.AV               -ACMSDI-I-PROCEED, It will take approximately 15 minutes to complete the               installation. `               %VMSINSTAL-I-ACCOUNT, This installation updates an identifier named ACMSDI$CLIENT.B               %UAF-I-RDBMDFYMSG, identifier ACMSDI$CLIENT modified                  .                  .                  .  E               Read the instructions, because they might apply to yourM               installation.   E               If the installation procedure has been successful up to C               this point, VMSINSTAL moves the new or modified files_D               to their target directories and updates help files. IfF               you asked for files to be purged, that work is done. The-               following message is displayed:                     .                  .                  .\               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...                  .                  .                  .  @               If you are installing gateway software on a systemC               disk that has limited free space, VMSINSTAL might not B               be operating in safety mode. In this case, VMSINSTALF               processes all files immediately and does not display the0               %VMSINSTAL-I-MOVEFILES... message.  E               If the disk has quotas enabled, a message is displayed. F               The account must have sufficient disk quotas to install.!               Refer to Table 8-1.   =         9.2.4 Running the Installation Verification Procedureo  G               If you chose to run the IVP, VMSINSTAL runs it next. WhentG               the IVP runs successfully, you see the following messagesM               displayed:        H            Installing TP Desktop Connector Gateway for ACMS Software 9-9 l  ,            H            %RUN-S-PROC_ID, identification of created process is 210031D5(            Starting Server ACMSDI$SERVERT            The TP Desktop Connector V3.1 Gateway for ACMS IVP completed successfullyG                         Installation of ACMSDIA V3.1 completed at 13:32a               .f               .                .tT            The TP Desktop Connector V3.1 Gateway for ACMS IVP completed successfully  0      9.2.5 Completing the Installation Procedure  @            The following messages indicate that the installation!            procedure is complete:   <              Installation of ACMSDIA V3.1 completed at 13:32  .              VMSINSTAL procedure done at 13:33            $  9            You can now log out of the privileged account:A              $ LOGOUT ;            SYSTEM     logged out at 04-JAN-1999 13:34:12.28   E            VMSINSTAL deletes or changes entries in the process symbol A            tables during the installation. Therefore, to continue B            using the system account and restore these symbols, log@            out and log in again. Proceed to Chapter 10 to follow'            postinstallation procedures.$  9      9.3 Recovering from System and Installation FailuresM  @            An unsuccessful installation can result from a systemC            failure (see Section 9.3.1) or errors encountered duringl:            the installation procedure (see Section 9.3.2).        9.3.1 System Failures  C            If you experience a system failure, such as a power losscB            during installation, VMSINSTAL attempts to continue theD            installation when you reboot the system. Depending on theC            point in the installation at which the system fails, oneo&            of three conditions exists:  D            o  The system disk did not undergo any changes before theD               system failure. VMSINSTAL instructs you to restart the               installation.i  C      9-10 Installing TP Desktop Connector Gateway for ACMS Softwaree d  a            H               o  The system disk used by the installation was corrupted.H                  VMSINSTAL instructs you to restore the system disk from>                  the backup copy and restart the installation.  F               o  VMSINSTAL continues the installation and can tell youF                  to manually purge replaced files, even if you requestH                  that they be purged automatically. You can purge files,E                  but remember that purging deletes all but the latestoF                  version of all files on your system disk. If you haveC                  multiple versions of system files to save, you canoF                  delete just the gateway files you want to remove from$                  system directories.  =                  To purge files, perform the following steps:t  &                  1. Reboot the system.  1                  2. Log in to the SYSTEM account.   G                  3. Purge all system files using the following command:   5                     $ PURGE/LOG SYS$SYSROOT:[*...]*.*                         .                        .                        .  A                  After you perform this task, the installation isr                  complete.  D               After you see the message that indicates the beginningD               of the IVP, the installation of the component softwareF               is complete. If the system fails subsequently, VMSINSTAL=               displays the following message when you reboot..  f         %VMSINSTAL-I-RECOVER, TP Desktop Gateway for ACMS was being installed when the system crashed.  2         The installation completed satisfactorily.  A               This message indicates that VMSINSTAL finished suc-mE               cessfully, not that the installation of the gateway wase               successful.o  C               VMSINSTAL does not automatically restart the IVP. Run G               the IVP independently by following the steps described inp               Chapter 11.i  H           Installing TP Desktop Connector Gateway for ACMS Software 9-11                        9.3.2 Installation Failures  >            If the installation of the gateway software or a TPE            Desktop Connector sample application fails for some reasonnB            other than a system failure, the installation procedureB            displays a message describing the cause of the failure.C            To continue with the installation, correct the condition C            causing the error and restart the installation procedure             from the beginning.  A            Errors can occur during the installation if any of thep&            following conditions exist:  8            o  The operating system version is incorrect.  ;            o  A prerequisite software version is incorrect.t  >            o  Quotas necessary for successful installation are               insufficient.h  E            o  System parameter values for successful installation areI               insufficient.T  ;            o  The OpenVMS help library is currently in use.D  D            For descriptions of the error messages generated by these>            conditions, see the OpenVMS documentation on system>            messages, recovery procedures, and OpenVMS software?            installations. If you are notified that any of thesetE            conditions exist, take the appropriate action as describedt=            in the message. (You might need to change a systemi@            parameter or increase a quota value.) For information7            on installation requirements, see Chapter 8.   B            If the installation of the component software completesC            satisfactorily, but a test fails during the IVP, the IVP C            displays a message describing the failure and suggests a             course of action.  >            In most cases, the suggested course of action is toA            reinstall the gateway software. If the IVP fails after B            you reinstall the gateway software, contact your Compaq            software specialist.T    C      9-12 Installing TP Desktop Connector Gateway for ACMS Software.                           9.3.3 IVP Error Recovery  E               As the IVP executes, it checks the success of each testyH               and operation it performs. If any test or operation fails,C               the IVP displays a message describing the failure and *               suggests a course of action.  H               Follow the suggested course of action and then restart theF               IVP as described in Chapter 11. If you reinstall gatewayG               software, the IVP runs automatically if you answer YES toNH               the IVP question. If you still cannot successfully run the;               IVP, contact your Compaq software specialist.*                                                                  H           Installing TP Desktop Connector Gateway for ACMS Software 9-13 y  h                  H                                                                       10H         ________________________________________________________________  H          After Installing TP Desktop Connector Gateway for ACMS Software      D               After installing gateway software from the Gateway CD,*               perform the following tasks:  D               o  Edit OpenVMS system startup and shutdown files (see                  Section 10.1).D  C               o  Perform any cluster operations (see Section 10.2).N  E               o  Match client and server versions (see Section 10.3).p  @               o  Read the management chapters in the appropriate                  document:  ?                  -  Compaq TP Desktop Connector for ACMS ClientI1                     Application Programming Guide   ?                  -  Compaq TP Desktop Connector Getting Started   A               See Chapter 11 for information about how to run thesA               Installation Verification Procedure (IVP) after then*               software has been installed.  -         10.1 Editing the OpenVMS System Files   C               You must edit the OpenVMS system startup and shutdown G               files to provide for automatic startup and shutdown of TP G               Desktop software when your system is rebooted. (This stepe<               is usually not necessary for system upgrades.)  .         10.1.1 Editing the System Startup File  @               The following files are located in the SYS$STARTUP               directory.  !               ACMSDI$SHUTDOWN.COM                 ACMSDI$STARTUP.COM  H     After Installing TP Desktop Connector Gateway for ACMS Software 10-1    D            B            Add to the OpenVMS system startup file the command line>            that starts TP Desktop. If you separate the startupE            procedures into modules, be sure that you add the lines to             the correct file.  A            Position the TP Desktop startup command line after theaD            line that invokes the ACMS startup command procedure. For            example:b  &            $ @SYS$STARTUP:ACMSTART.COM               .e               .                .l,            $ @SYS$STARTUP:ACMSDI$STARTUP.COM  C               ________________________Note ________________________   =               Start ACMS software before you start TP Desktop                software.   C               _____________________________________________________f  E            Starting TP Desktop software automatically enables the use C            of the DECnet communication transport. To use NetWare or C            TCP/IP protocols as well, or instead of DECnet, list the B            transports you want to use in a parameter file. Specify>            the parameter file as a qualifier on the TP Desktop             startup command line.  D            The parameter file is a simple ASCII text file that lists?            customer overrides to TP Desktop run-time quotas and B            defaults. These overrides can include the specificationB            of the communication libraries that have been installedC            on the OpenVMS system. For example, to enable TP DesktopuB            to use all transports, create the following file in the!            SYS$MANAGER directory:   "            ACMS_DESKTOP_SERVER.DAT  2            Include in the file the following line:  5            transport=(tcpip,netware,decnet,appletalk)   C            Modify the startup command line to specify the parameter             file. For example:   P            $ @SYS$STARTUP:ACMSDI$STARTUP.COM SYS$MANAGER:ACMS_DESKTOP_SERVER.DAT  I      10-2 After Installing TP Desktop Connector Gateway for ACMS Software                  D               To perform this same function in batch from DCL-level,2               issue a SUBMIT command. For example:  D               $ SUBMIT/USER=SYSTEM/NOLOG SYS$STARTUP:ACMSDI$STARTUP-A               _$ /PARAMETER=(SYS$MANAGER:ACMS_DESKTOP_SERVER.DAT)   C               This command starts a batch job that runs the startup E               command procedure using the input file specified in the G               parameter qualifier. When the batch job completes, the TPr*               Desktop software is started.  /         10.1.2 Editing the System Shutdown File   F               Find the following line, which stops the ACMS system, in/               the OpenVMS system shutdown file:N                 $ @ACMSTOP.COM  G               At some point before this line, add the following commandd               line:   0               $ @SYS$STARTUP:ACMSDI$SHUTDOWN.COM  F               The command procedure cancels all active tasks and shutsC               down the TP Desktop process. This ensures that the TPrA               Desktop system processes are run down properly. ThenH               command procedure also deinstalls TP Desktop images (usingG               the Install Utility of OpenVMS) and deassigns the logicali               names.  *         10.2 Performing Cluster Procedures  @               Because TP Desktop software treats a VAXcluster orB               VMScluster system as if it were a local area networkC               (LAN), you must prepare system-specific roots on eacho/               node of the cluster. For example:r  H               $ CREATE/DIRECTORY SYS$SPECIFIC:[ACMSDI]/OWNER_UIC=SYSTEM-5               _$  /PROTECTION=(S:RWE,O:RWE,G:RE,W:RE)lP               $ CREATE/DIRECTORY SYS$SPECIFIC:[SYSTEST.ACMSDI]/OWNER_UIC=SYSTEM-5               _$  /PROTECTION=(S:RWE,O:RWE,G:RE,W:RE) X               $ CREATE/DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.ACMSDI]/OWNER_UIC=SYSTEM-5               _$  /PROTECTION=(S:RWE,O:RWE,G:RE,W:RE)M               $Y  H     After Installing TP Desktop Connector Gateway for ACMS Software 10-3 l               ?            Executed on each node in the cluster, these commands B            create directory roots for the TP Desktop software. SeeB            Section 9.1.2 for the locations of files describing the,            directories added to your system.  -      10.3 Matching Client and Server Versionss  @            If you are upgrading from ACMS Desktop Version 2.n toC            TP Desktop Version 3.m, you can use your existing clientn@            programs with the new server. But, if you build a newB            client program under TP Desktop Version 3.m, you cannotE            use this new program with the old ACMS Desktop Version 2.n             server.  C            When the ACMS communication protocols do not match thoseMC            of the desktop client, the gateway rejects the attemptedrC            connection. The gateway writes a message to the software             event log (SWL).d  @            The error code returned on the client side depends onD            the nature of the mismatch. The following error codes can+            indicate a mismatched condition:   $            ACMSDI_SRVDEAD      -3020$            ACMSDI_INVPROTOCOL  -3025                                        I      10-4 After Installing TP Desktop Connector Gateway for ACMS Softwarei l  s                  H                                                                       11H         ________________________________________________________________  H                    Running the TP Desktop Connector Gateway for ACMS IVP      H               This chapter describes how to run the gateway installation>               verification procedure (IVP) separately from theE               installation procedure. The IVP can be run as a part of D               the normal installation when you answer YES to the IVPD               question. If the IVP fails for any reason, correct theD               error and rerun the IVP. See Chapter 9 for information@               on providing the IVP with information required forA               the installation procedure. Run separately from thelH               installation procedure, the IVP can check the integrity of,               installed files on the system.           11.1 IVP Operations_  "               The IVP checks that:  B               1. The installation procedure successfully completed0                  installing TP Desktop software.  H               2. The installed software can be used to set up and run TP"                  Desktop software.  ;               3. All the necessary files are on the system.i  >               The IVP does not check that the applications run               correctly.  *         11.2 Running the IVP Independently  F               This section describes the requirements and steps to run               the IVP.          H               Running the TP Desktop Connector Gateway for ACMS IVP 11-1 l  n                  11.2.1 IVP Requirements  >            If disk quotas are enabled, the IVP cannot run. TheB            procedure checks to see whether disk quotas are enabledE            just after checking the process quotas. If disk quotas areeC            enabled, the procedure provides an informational messager)            to that effect and terminates.         11.2.2 IVP Stepsx  ;            To run the IVP independently of the installationf)            procedure, follow these steps::  +            1. Log in to the SYSTEM account:e                 Username: SYSTEM               Password:   5            2. Set your default to the test directory:i  $               $ SET DEFAULT SYS$TEST               $   A            3. Run the IVP using the following file specification:u                 ACMSDI$IVP.COM  E               You can run the IVP only on your current booted system. A               You cannot run the IVP over a networked connection.o  9            To start the IVP, enter the following command:2              $ @ACMSDI$IVPT            The TP Desktop Connector V3.1 Gateway for ACMS IVP completed successfully               .i               .                .lT            The TP Desktop Connector V3.1 Gateway for ACMS IVP completed successfully  E            The IVP takes no more than 30 seconds to run, depending onc#            the current system load.         ?      11-2 Running the TP Desktop Connector Gateway for ACMS IVPN L  l            !         11.2.3 IVP Error Recovery   E               As the IVP executes, it checks the success of each test H               and operation it performs. If any test or operation fails,)               the IVP does the following:t  "               1. Stops processing.  ;               2. Displays a message describing the failure.n  F               3. Suggests a course of action to eliminate the cause of                  the failure.e  H               Follow the suggested course of action and then restart the               IVP.                                                            H               Running the TP Desktop Connector Gateway for ACMS IVP 11-3 i                     H                                                                  Part IVH         ________________________________________________________________  H                                                               Appendixes        E               Part IV provides reference material related to softwareI'               installation on a system.   C               Appendix A lists the files that are installed on youre5               system for the various sample programs.   G               Appendix B contains helpful hints about errors that might @               occur when you run one of the sample applications.                       H                                                                        AH         ________________________________________________________________  H                                                          Files Installed      G               The following tables list the files that are installed ona?               your systems for the various sample applications.   G               Table A-1 Files Installed for TP Desktop Connector ClientsH               __________Services_for_OpenVMS_Systems____________________  H               Files____________Description______________________________  H               ACMSDI.H         Include file for the TP Desktop Connector;                                client services declarationst  C               ACMSDI$CLIENT_   Library for the TP Desktop Connectorm.               OBJLIB.OLB       client services  8               FORMS.H          Include file for DECforms  E               NET_APPLETALK.OBJAppleTalk object file (for OpenVMS VAXt,                                systems only)  1               NET_DECNET.OBJ   DECnet object fileg  5               NET_NETWARE.OBJ  NetWare object file[1]   1               NET_TCPIP.OBJ    TCP/IP object file   H               PPSTUBS.C        Presentation procedure and action routine$                                stubs  4               TDMS.H           Include file for TDMSH               [1]For_testing_purposes_only,_not_officially_supported.___  H               __________________________________________________________      H                                                      Files Installed A-1 i  o            =            Table A-2 Files Installed for the Motif Sample foroE            __________OpenVMS_Systems_________________________________e  E            Name_____________Description______________________________   <            Makefile         Makefile for building the sample  E            acmsdi.h         Include file for the TP Desktop Connector +                             client servicesa  D            forms.h          Sample include file with DECforms status"                             values  A            help.txt         Overview of the AVERTZ user interfaces  6            sys$login:m_     Motif sample resource file            avertz.data  C            m_avertz.c       Entry point for the sample; manages thet5                             main window of the samplen  D            m_avertz.h       AVERTZ header file; defines global names  B            m_avertz.opt     Linker-purge options file for building&                             the sample  B            m_avertz.uid     Runtime representation of the sample's*                             UIL definition  @            m_avertz.uil     User interface template; defines theE                             layout of the main window and the sessionT&                             dialog box  A            m_avertzpp.c     Reserve task presentation procedures;mB                             stubs for the checkin and the checkout:                             tasks' presentation procedures  8            m_avertzpp.h     Header file for m_avertzpp.c  7            m_disable.c      Presentation procedure stubs  7            m_enable.c       Presentation procedure stub   @            m_icons.uil      User interface template; defines the1                             various session icons   8            m_list_pkg.c     Provides linked list feature  6            m_list_pkg.h     Header file for list_pkg.c  @            m_message.c      Performs message box handling in the"                             sample  E                                              (continued on next page)         A-2 Files Installed u  s            D               Table A-2 (Cont.) Files Installed for the Motif SampleH               __________________for_OpenVMS_Systems_____________________  H               Name_____________Description______________________________  :               m_message.h      Header file for m_message.c  :               m_read_write.c   Presentation procedure stub  :               m_receive.c      Presentation procedure stub  :               m_request.c      Presentation procedure stub  F               m_resvform.c     Management and convenience routines for<                                handling the reservation form  ;               m_resvform.h     Header file for m_resvform.cV  C               m_resvform.uil   User interface template; defines theo=                                layout of the reservation form   D               m_send.c         Presentation procedure to dispatch to@                                specific routines in m_avertzpp.c  B               m_session.c      Manages multiple sessions; switchesE                                context for using TP Desktop Connector H                                gateway for ACMS routines and updates the-                                user interface_  :               m_session.h      Header file for m_session.c  F               m_sitelist.c     Creates (using m_sites.dat) and manages;                                the list box of AVERTZ sites   ;               m_sitelist.h     Header file for m_sitelist.c   H               m_sites.dat      Contains data about AVERTZ sites; read in*                                at run time  H               m_transceive.c   Presentation procedure that dispatches to<                                specific routines in avertzpp  C               m_version.c      Version-checking action routine stub   D               m_wkspaces.c     Support routines for AVERTZ workspace)                                structures   F               m_wkspaces.h     Defines the AVERTZ workspace structures  C               tdms.h           Sample include file with TDMS status H               _________________values___________________________________  H                                                      Files Installed A-3                 ?            Table A-3 Files Installed for the PowerBuilder Win32 E            __________Sample__________________________________________   E            Name_____________Description______________________________   A            pbreadme.doc     Contents of the folder in text formatE  ;            pbavertz.pbl     PowerBuilder library containingiA                             PowerBuilder objects for the blocking E                             sample that does not support exchange I/O   B            pbavertz.exe     Executable form of the PBAVERTZ sample  E            pbavertz.doc     Declarations and scripts used by PBAVERTZ *                             in text format  D            pbpointr.dll     Dynamic link library required for memoryE                             management with PowerBuilder applications E                             that use TP Desktop Connector gateway for *                             ACMS services.  =            pbpointr.h       Interface definition file for pb-:&                             pointr.dll  E            acmsdipb.doc     Microsoft Word document that explains how =                             to use the pbpointr.dll services._  1            cars.ico         Icon used by PBAVERTZu  ?            fnbsampl.pbl     A PowerBuilder library containing a_D                             sample application that executes an ACMSC                             task with exchange I/O using the forcedhC                             nonblocking extension to the TP DesktopI6                             Connector client services.  E            fnbsampl.exe     Executable form of the forced nonblocking "                             sample  B            fnbsampl.doc     Microsoft Word document that describesE            _________________forced_nonblocking_______________________o                A-4 Files Installed o               B               Table A-4 Files Installed for the Visual Basic Win32H               __________Sample__________________________________________  H               Name_____________Description______________________________  G               mainmenu.frm     GUI objects and code for the main windowr5                                of Visual Basic AVERTZ   F               reserve.frm      GUI objects and code for the car rentalB                                reservations screen of Visual Basic%                                AVERTZ   D               signin.frm       GUI objects and code for the session-B                                login screen of Visual Basic AVERTZ  D               readme.1st       Contents of the folder in text format  E               readme.txt       Text document that explains how to use 7                                the helper DLL, divb.dll   B               vbavertz.bas     Global source code for Visual Basic%                                AVERTZO  H               vbavertz.exe     Executable version of Visual Basic AVERTZ  H               vbavertz.mak_____Project_makefile_for_Visual_Basic_AVERTZ_  H               Table_A-5_Files_Installed_for_the_DOS_Sample______________  H               Name_____________Description______________________________  F               ACMSDI.H         Include file for ACMS desktop interface'                                programsh  H               BLD-CLI.BAT      Batch file to compile and link the sample-                                client programo  G               BLD-PPS.BAT      Batch file to compile and link presenta-DH                                tion procedures used by the sample client&                                program  >               CHK-DATE.CBL     COBOL program to validate dates  /               CLASSES.CBL      Sample workspace   ;               CLIENT.C         Sample client C main programu  4               CLIENT.EXE       Sample client program  /               CONTROL.CBL      Sample workspace   H                                                 (continued on next page)  H                                                      Files Installed A-5    a            E            Table_A-5_(Cont.)_Files_Installed_for_the_DOS_Sample______o  E            Name_____________Description______________________________A  ,            CUSTOMER.CBL     Sample workspace  ,            CUSTSHDW.CBL     Sample workspace  ,            CU_TRANS.CBL     Sample workspace  9            DISABLE.C        Sample presentation procedure   9            ENABLE.C         Sample presentation procedureA  D            FORMS.H          Sample include file with DECforms status"                             values  9            GETSITE.CBL      Sample presentation procedure   B            LOGIN.CBL        Sample client initialization procedure  ?            LOGOFF.CBL       Sample client termination procedure   8            MENU.CBL         Sample client menu procedure  9            RECV.C           Sample presentation procedurec  9            REQUEST.C        Sample presentation procedure   ,            RESERVTN.CBL     Sample workspace  9            SELCUST.CBL      Sample presentation procedure   9            SELSITE.CBL      Sample presentation procedurei  9            SEND.C           Sample presentation procedurey  ,            SENDCTRL.CBL     Sample workspace  9            SHWCUST.CBL      Sample presentation procedurer  9            SHWRESV.CBL      Sample presentation proceduree  ,            SITES.CBL        Sample workspace  ,            SI_TRANS.CBL     Sample workspace  @            TDMS.H           Sample include file with TDMS status"                             values  9            TRANS.C          Sample presentation proceduree  ,            TRANS.CBL        Sample workspace  ,            TRANSHDW.CBL     Sample workspace  E            VERSION.C________Sample_version-checking_procedure________         A-6 Files Installed -  0            H               Table_A-6_Files_Installed_for_the_Windows_3.11_Sample_____  H               Name_____________Description______________________________  @               ACMSDI.H         Include file for the ACMS desktop(                                interface  ?               AVERTZ           Makefile for building the sample   F               AVERTZ.C         Entry point for the sample; manages the*                                main window  F               AVERTZ.DEF       Defines entry points and stack size for0                                Microsoft Windows  G               AVERTZ.EXE       Microsoft Windows sample executable fileo  B               AVERTZ.H         AVERTZ header file; defines globals  C               AVERTZ.RC        User interface template; defines the.G                                main window, menus, and reservation formn%                                layouth  C               AVERTZMM.C       Handles memory management for AVERTZl)                                structurese  9               AVERTZMM.H       Header file for AVERTZMM.C   D               AVERTZPP.C       Reserve task presentation procedures;G                                stubs for checkin and checkout tasks and 6                                presentation procedures  9               AVERTZPP.H       Header file for AVERTZPP.C   :               DISABLEW.C       Presentation procedure stub  G               DRIVING.ICO      Icon for (an unselected) session that isa:                                currently processing a task  C               ENABLEW.C        Presentation procedure to define theb)                                session ID   G               FORMS.H          Sample include file with DECforms statusG%                                values   D               HELP.TXT         Overview of the AVERTZ user interface  C               LIST_PKG.C       Provides linked list feature; preal-rD                                locates memory using arrays to reduce>                                fragmentation of the local heap  9               LIST_PKG.H       Header file for LIST_PKG.Cn  H                                                 (continued on next page)  H                                                      Files Installed A-7                 A            Table A-6 (Cont.) Files Installed for the Windows 3.11 E            __________________Sample__________________________________y  E            Name_____________Description______________________________   7            RECVW.C          Presentation procedure stub   D            REDCAR.ICO       Icon for (an unselected) session that is;                             not currently processing a taskt  7            REQUESTW.C       Presentation procedure stub   C            RESVFORM.C       Management and convenience routines for 9                             handling the reservation formo  6            RESVFORM.H       Header file for RESVFORM.C  ?            SDRIVING.ICO     Icon for a selected session that isf7                             currently processing a taskt  A            SENDW.C          Presentation procedure to dispatch tor;                             specific routines in AVERTZPP.CC  ?            SESSION.C        Manages multiple sessions; switchesIB                             context for using TP Desktop ConnectorE                             gateway for ACMS routines and updates then*                             user interface  ?            SESSION.H        Header file for to obtain the files @                             for building against the static link/                             libraries SESSION.Cm  A            SITELIST.C       Creates (using SITES.DAT) and manageso4                             list box of AVERTZ sites  6            SITELIST.H       Header file for SITELIST.C  E            SITES.DAT        Contains data about AVERTZ sites; read inG'                             at run time   C            SREDCAR.ICO      Icon for a selected session that is not 7                             currently processing a task_  E                                              (continued on next page)         A-8 Files Installed                 D               Table A-6 (Cont.) Files Installed for the Windows 3.11H               __________________Sample__________________________________  H               Name_____________Description______________________________  C               TDMS.H           Sample include file with TDMS statuso%                                valuesn  H               TRANSW.C         Presentation procedure that dispatches to>                                specific routines in AVERTZPP.C  >               VERSIONW.C       Version-checking procedure stub  C               WKSPACES.C       String conversion support for AVERTZl3                                workspace structuress  H               WKSPACES.H_______Defines_the_AVERTZ_workspace_structures__  C               Table A-7 Files Installed for the 16-Bit PowerBuilder H               __________Sample__________________________________________  H               Name_____________Description______________________________  G               ACMSDIPB.DOC     Document discussing TP Desktop ConnectorfH                                gateway for ACMS support for PowerBuilder  B               PBAVERTZ.PBL     PowerBuilder library containing theE                                blocking sample which does not support +                                exchange I/O   E               PBAVERTZ.EXE     Executable form of the PBAVERTZ sample   H               PBAVERTZ.DOC     Declarations and scripts used by PBAVERTZ-                                in text format   4               CARS.ICO         Icon used by PBAVERTZ  B               PBPOINTR.DLL     Dynamic link library containing theA                                required memory management program   I               PBPOINTR.H_______Interface_definition_file_for_PBPOINTR.DLL         H                                                      Files Installed A-9                 @            Table A-8 Files Installed for the Visual Basic AvertzE            __________Sample__________________________________________   E            Name_____________Description______________________________   B            ACMSDI.BAS       Include file of the ACMSDI declaration9                             for Visual Basic applications_  A            HELP.TXT         Online help file for the Visual Basich"                             sample  C            MAINMENU.FRM     GUI objects and code for main window of /                             Visual Basic AVERTZ   E            RESERVE.FRM      GUI objects and code for reservation forma2                             of Visual Basic AVERTZ  B            SIGNIN.FRM       GUI objects and code for session-login9                             screen of Visual Basic AVERTZ   ?            VBAVERTZ.BAS     Global module file for Visual Basic "                             AVERTZ  ?            VBAVERTZ.EXE     Visual Basic sample executable filem  E            VBAVERTZ.MAK_____Visual_Basic_makefile_for_AVERTZ_sample__                                             A-10 Files Installed     t            B               Table A-9 Files Installed for the Forced NonBlockingH               __________Tutorial________________________________________  H               Name_____________Description______________________________  C               ACMSDI.BAS       ACMSDI declarations for Visual Basick+                                applications   B               FORM1.FRM        GUI objects and code for the Forced?                                Nonblocking Tutorial main window   D               FORMS.BAS        DECforms message code definitions for+                                Visual Basic   D               FNBSAMPL.MAK     Visual Basic make file for the Forced3                                Nonblocking Tutorial   B               FRMLOGIN.FRM     GUI objects and code for the ForcedH                                Nonblocking Tutorial session login window  B               FRMRECVC.FRM     GUI objects and code for the ForcedC                                Nonblocking Tutorial receive control *                                text window  B               MTEXT.BAS        Declarations and code to initializeC                                ACMSDI message text for Visual Basic_+                                applications_  G               NONBLK.BAS       Global declarations for the Visual Basic_H               _________________Forced_Nonblocking_Tutorial______________                              H                                                     Files Installed A-11 r  t            A            Table A-10 Files Installed for the Client Services for E            ___________Tru64_UNIX_Systems_____________________________   E            Name_____________Description______________________________o  E            acmsdi.h         Include file for the TP Desktop ConnectorU+                             client services   5            forms.h          Include file for DECforms   C            libacmsdi.a      Library for TP Desktop Connector client $                             services  @            net_tcpip.o      TCP/IP file for TP Desktop Connector+                             client services   @            net_decnet.o     DECnet file for TP Desktop Connector+                             client servicesd  E            ppstubs.c        Presentation procedure and action routine !                             stubsr  E            tdms.h___________Include_file_for_TDMS____________________)  D            Table A-11 Files Installed for the Motif Sample for Tru64E            ___________UNIX_Systems___________________________________   E            Name_____________Description______________________________   <            makefile         Makefile for building the sample  E            acmsdi.h         Include file for the TP Desktop Connector +                             client services   D            forms.h          Sample include file with DECforms status"                             values  =            help.txt         Overview of AVERTZ user interfacer  ?            load_motif.sh    Command shell to download the Motifp:                             sample from the OpenVMS system  8            m_avertz         Motif sample executable file  C            m_avertz.c       Entry point for the sample; manages the 5                             main window of the sample   C            m_avertz.dat     Font definitions for the sample screens3  ?            m_avertz.h       AVERTZ header file; defines globals_  E                                              (continued on next page)_        A-12 Files Installed.                 E               Table A-11 (Cont.) Files Installed for the Motif SamplelH               ___________________for_Tru64_UNIX_Systems_________________  H               Name_____________Description______________________________  G               m_avertz.uid     Runtime representation of the sample UILp)                                definitiono  C               m_avertz.uil     User interface template; defines theoH                                layout of the main window and the session)                                dialog boxw  D               m_avertzpp.c     Reserve task presentation procedures;E                                stubs for the checkin and the checkoute=                                tasks' presentation procedures   ;               m_avertzpp.h     Header file for m_avertzpp.cd  :               m_disable.c      Presentation procedure stub  :               m_enable.c       Presentation procedure stub  C               m_icons.uil      User interface template; defines the.4                                various session icons  ;               m_list_pkg.c     Provides linked list feature   9               m_list_pkg.h     Header file for list_pkg.cr  C               m_message.c      Performs message box handling in theo%                                sampleo  :               m_message.h      Header file for m_message.c  :               m_read_write.c   Presentation procedure stub  :               m_receive.c      Presentation procedure stub  :               m_request.c      Presentation procedure stub  F               m_resvform.c     Management and convenience routines for<                                handling the reservation form  ;               m_resvform.h     Header file for m_resvform.c_  C               m_resvform.uil   User interface template; defines the_=                                layout of the reservation formo  D               m_send.c         Presentation procedure to dispatch to>                                specific routines in m_avertzpp  H                                                 (continued on next page)  H                                                     Files Installed A-13    n            B            Table A-11 (Cont.) Files Installed for the Motif SampleE            ___________________for_Tru64_UNIX_Systems_________________   E            Name_____________Description______________________________T  ?            m_session.c      Manages multiple sessions; switches B                             context for using TP Desktop ConnectorE                             gateway for ACMS routines and updates the *                             user interface  7            m_session.h      Header file for m_session.ck  C            m_sitelist.c     Creates (using m_sites.dat) and manages-8                             the list box of AVERTZ sites  8            m_sitelist.h     Header file for m_sitelist.c  E            m_sites.dat      Contains data about AVERTZ sites; read ini'                             at run timep  E            m_transceive.c   Presentation procedure that dispatches to =                             specific routines in m_avertzpp.c   @            m_version.c      Version-checking action routine stub  A            m_wkspaces.c     Support routines for AVERTZ workspace &                             structures  C            m_wkspaces.h     Defines the AVERTZ workspace structuress  @            tdms.h           Sample include file with TDMS statusE            _________________values___________________________________T                                A-14 Files InstalledT .                     H                                                                        BH         ________________________________________________________________  H                                              Common Configuration Errors      D               The following sections discuss some of the errors thatE               can occur while running the TP Desktop Connector client +               services sample applications.e  0         B.1 Errors Related to the Desktop System  C               Errors can arise when any of the following conditions                exits:  F               o  The TP Desktop Connector client program node does notA                  have the network software functioning correctly.   F               o  The TP Desktop Connector client program node does not?                  have the network in the directory search path.L  A               o  The TP Desktop Connector client program node hasN)                  insufficient disk space.   4         B.1.1 Errors on DOS or Windows 3.11 Desktops  H               Problems might be caused by a faulty startup or configura-E               tion file. Example B-1 shows a sample startup.bat file.a  1               Example B-1 Sample startup.bat FileL  [               path=c:\;c:\PWV51;c:\dos;c:\MSVC\bin;c:\windows;c:\windev;c:\acmsdi mouse setrG               lib=c:\MSVC\lib;c:\windev\lib;c:\acmsdi;c:\decnet\src setCS               include=c:\MSVC\include;c:\windev\include;o:\acmsdi;c:\decnet\src sett@               helpfiles=c:\MSVC\help\*.hlp set init=c:\MSVC\init            H                                          Common Configuration Errors B-1 e  l            6            Example B-2 shows a sample config.sys file.    -            Example B-2 Sample config.sys File               files= 30            buffers=10             device=C:\himem.sys(            shell=\command.com /P /e:10243            device=C:\WINDOWS\smartdrv.sys 2048 1024A            lastdrive=z  B            Use the samples as guidelines to finding and fixing the            problem.   %      B.1.2 Errors on OpenVMS Desktopsn  ?            If errors occur in running the Motif Avertz program,c             verify the following:  B            o  The m_avertz.uid file is in the directory from which/               you run the m_avertz application.   D            o  The m_avertz.dat file (your resources file) is located%               in your home directory.   =            If you encounter font-support problems running ther@            program, you can modify the fonts used by editing theC            m_avertz resources file (m_avertz.dat in the user's home             directory).  (      B.1.3 Errors on Tru64 UNIX Desktops  ?            If errors occur in running the Motif Avertz program,              verify the following:  B            o  The m_avertz.uid file is in the directory from which/               you run the m_avertz application.m  C            o  The m_avertz file (your resources file) is located ine"               your home directory.  A            If you are installing this application once for use byt@            many users, make sure that the users copy m_avertz to"            their home directories.  =            If you encounter font-support problems running the A            program, modify the fonts used by editing the m_avertz B            resources file (m_avertz in the user's home directory).  $      B-2 Common Configuration Errors o  h            -         B.2 Errors Related to the ACMS System   H               If you have used the client services sample to communicateC               with the ACMS system, errors will occur if any of the.*               following conditions exists:  A               o  The TP Desktop Connector gateway for ACMS systemPF                  directory ACMSDI$EXAMPLES, ACMSDI$EXAMPLES_AVERTZ, orF                  ACMSDI$EXAMPLES_ADD is protected against read access.  F               o  The TP Desktop Connector gateway for ACMS system does5                  not have the sample files installed.   F               o  The TP Desktop Connector gateway for ACMS system doesE                  not have the network software functioning correctly.   D               o  The TP Desktop Connector gateway for ACMS system is                  unavailable.l  F               o  The TP Desktop Connector gateway for ACMS system name                  is invalid.  H               o  The TP Desktop Connector gateway for ACMS system is not+                  running the ACMS software.p  E               o  The TP Desktop Connector gateway for ACMS system hassF                  not invoked ACMSDI$STARTUP.COM and ACMS/START SYSTEM.  F               o  The TP Desktop Connector gateway for ACMS software is:                  not installed or is improperly installed.  E               o  The TP Desktop Connector gateway for ACMS system IVP                   failed.                        H                                          Common Configuration Errors B-3                               E      ________________________________________________________________i  E                                                                 Index       E      A__________________________          B__________________________   :      ACMS                                 Back button, 5-22        starting, 10-2                     BlockingD        stopping system, 8-5                Visual Basic Sample Files4      ACMSADU utility use,  8-3                ,  A-9       ACMSDI$CLIENT modification,+         9-8                               C E      ACMSDI$SYSTEM_FILES.DAT,             ___________________________r2         9-2                               C++, 6-3<      ACMS_DESKTOP_SERVER.DAT,             Cancel button, 5-2D         10-2                              Client Services interface,/      Administrator privileges,              5-4 B         ix                                Cluster procedures, 10-34      API                                  COBOL, 6-34        see TP Desktop Connector           ComponentsE                                            TP Desktop Connector,  4-1F1          client services                  CONDISTa@      Appletalk enabling,  10-2             See Software Products5      Authorization,  8-3                      Library_C      Authorizing gateway user             Configuration errors, B-1_         name, 8-3 +      AVERTZ                               DwE        access control list,               ___________________________ 4          3-11, 6-22                       DEC C, 6-3>        application notes, 3-10,           DECforms, 3-10, 6-215          6-20                             DECnet, 5-3n?        rebuilding, 3-11, 6-22             DECnet enabling, 10-2i?        user name quota values,            DECwindows Motif, 6-3sC          3-11, 6-21                       Disk space, 4-4, 7-4, 8-2pB                                            determining free,  1-3,1                                               8-2e7                                            requirements   E                                                               Index-1     S            1      Disk space                           FTP, xv         requirements (cont'd)E           desktops, 6-3                   H__________________________w  2           gateway, 1-3                    HardwareA      Disk space requirements,              for installation,  4-1          4-4 E      divb.dll,  5-5                       I__________________________ 6      divb.lib,  5-5                       Installation  9      E                                     aborting,  9-3 A      ___________________________           dialog box usage,  5-1bA      Editing                               procedure,  5-1 to 5-2o?        system shutdown file,               procedures for,  9-1g:          10-3                              questions,  9-4A        system startup file, 10-1           tasks following,  3-1, 2      Environment variables,  5-2              10-14      Error recovery,  9-13                InstallingD      Errors,  B-1                          DOS client services,  6-5D      Examples                              DOS link library options,1        logical name, 9-2                      6-6DC        Macintosh question, 9-7             DOS memory options,  6-6 ;        system-specific root,               DOS sample,  6-5XB          10-3                              DOS Sample Application,1      Examples option,  7-3                    6-7   A                                            DOS transport options,u1      F__________________________              6-6   8      Failure recovery,  9-10               gateway,  2-1C      Files                                 OpenVMS client services,e2        client services                        6-15@           added to OpenVMS                 OpenVMS Motif sample,2             Desktop system,                   6-17<             A-1                            Tru64 UNIX client=        installed on system, 9-2               services,  6-23iC        purge, 9-7                          Tru64 UNIX Motif sample, 2        sample                                 6-25@           added to OpenVMS                 Visual Basic Samples,2             desktop system,                   6-13C             A-1                            Windows client services,p1           added to Windows                    6-5 ?             system,  6-10                  Windows link library ;        sample applications, A-1               options,  6-8 ?      Forced Nonblocking                    Windows sample,  6-5 9        Visual Basic Sample Files           Windows Sample ?          ,  A-10                              Application,  6-9         Index-2    s            C         Installing (cont'd)                 Microsoft Visual Basic,d2          Windows transport options             6-3F             ,  6-8                          Microsoft Visual C++,  6-37         Installing PowerBuilder             Motif,  6-3s>           sample,  6-12                     msvcrt40.dll,  5-5           ISO format, 6-2 G         IVP                                 N__________________________   C          error recovery,  11-3              Netware enabling,  10-2cD          operations performed by,           Network transports,  5-3=             11-1                            Next button,  5-1 #          requirements to run,  11-2KG          running independently,             O___________________________G             11-1                            Operating system components 4          steps to run,  11-2                   , 8-1  ;         K                                   OSF/Motif,  6-3b#         ___________________________tG         Kanji, 5-6, 6-9                     P___________________________  5         L                                   PAK,  8-4_A         ___________________________         Parameter file,  10-2 E         License                               specifying,  10-2, 10-3s;          checking,  8-4                     PATHWORKS,  5-3o8          installation question,             Portable APIF             9-8                               see TP Desktop Connector@          registration,  8-4                      client services?         License, product, 4-4               PowerBuilder,  6-12EG         LMF requirement, 8-4                PowerBuilder sample client,r2         Logical name                           A-3@          added to system,  9-2              Preparing to installF         Logical names                          Macintosh software, 7-38          defining,  3-2                     Prerequisite  <         M                                     hardware,  1-2<         ___________________________           software,  1-29         Macintosh installation              Prerequisites ?           options,  7-1                       gateway kit,  8-1 A         Macintosh sample code               Prerequisite software F           installation,  9-7                  sample application,  6-2E         Memory copy procedures,             Prerequisite software for E           5-5                                  Macintosh systems, 7-3a@         Microsoft COBOL, 6-3                Privileges,  ix, 8-3>                                               BYPASS use,  8-39                                             Program groupe<                                               creating,  5-2  H                                                                  Index-3 o  d                  Protocol mismatch,  10-4 E      Purge files,  9-7                    T__________________________   5                                           TCP/IP, 5-3e?      R__________________________          TCP/IP enabling, 10-2   D      Rdb with multi-version,              Time for installation, 8-2>         6-20                              TP Desktop ConnectorC      Rdb with multiversion,                client services,  6-1 to_2         3-10                                  6-26;      Release Notes                         components,  4-1f7        accessing, 9-1                      installation A      Removing installed software              Win32 systems,  5-1e3         , 4-5                             Transport D      Resources,  6-4                       automatic enabling,  10-2C      Running the Installer,  7-6           parameter file enabling,e2      Run-Time Services option,                10-2           7-1nE                                           U__________________________a  D      S__________________________          User name requirement, 8-3        Sample E        OpenVMS, 6-17                      V__________________________.  4        Tru64 UNIX, 6-25                   VAX C, 6-33      Sample application setup             Verifying ;        on OpenVMS, 3-9, 6-19               DOS sample,  6-7 D      Saveset name,  9-3                    Motif client sample,  3-8@      Self-extracting archives,             OpenVMS Motif sample,2         1-2, 6-2                              6-18C      Shutdown,  10-3                       Tru64 UNIX sample,  6-25e@      Software Products Library             Windows sample,  6-101        installing, 2-1 to 2-4             Versionu>      SQL$USER library file,                matching client and;         3-10, 6-20                            server,  10-4 A      STDL version,  5-2                    operating system,  8-1_;      Storage requirements,  4-4           Visual Basic, 6-3 D      Superuser privileges,  ix            Visual Basic Avertz SampleB      System privileges,  ix                Verifying installation,2      System Services option,                  6-14D         7-1                               Visual Basic AVERTZ SampleB      System-specific roots,                Verifying installation,1         10-3                                  5-5 9      System startup file                  Visual C++, 6-3T3        editing, 3-2                       VMSINSTALe  9                                            invoking,  9-3_D                                            requirements,  8-2 to 8-6        Index-4                 H         VMSINSTAL (cont'd)                    sample application,  3-10,5          syntax,  9-3                            6-20 =         VMSLICENSE.COM, 8-4                 VR_DA_BLD_MMS.COM E         VR_DA_APPL                            parameters,  3-12, 6-23d  G                                             W__________________________t  A                                             Windows Sockets,  5-3R                                                                          H                                                                  Index-5