This chapter explains how to install DIGITAL TP Desktop Connector for ACMS and DIGITAL TP Desktop Connector Gateway for ACMS from the OpenVMS Software Products Library CD. Table 2-1 shows the contents of the TP Desktop Connector directory on the library CD.

Table 2-1 TP Desktop Connector Files on the Software Products Library CD

Name	Description
ACMSDI031.*	TP Desktop Connector Gateway for ACMS savesets
DSKCON_ACMS_INSTALL_GUIDE.PS DSKCON_ACMS_INSTALL_GUIDE.TXT	This book, formatted for PostScript or plain text
DSKCON_ACMS_RBI	Read Before Installing letter
DSKCON_ACMS_RELEASE_NOTES.PS DSKCON_ACMS_RELEASE_NOTES.TXT	New features and product restrictions
DSKCON_ACMS_SPD	Software Product Description document
TPW031.*	TP Desktop Connector client savesets

2.1 Installing the TP Desktop Connector Gateway for ACMS

Installing the gateway kit from the Software Products Library CD is the same as from the TP Desktop Connector Gateway for ACMS CD, except for the location of the product saveset. Refer to the Software Products Library Master Index for the directory name on the library CD. Instructions for VMSINSTAL are in Chapter 9.

2.2 Installing the Client Kit

To install the client kit on the OpenVMS system, while logged in under the SYSTEM account at the DCL prompt, type a command in the following format:

$ @SYS$UPDATE:VMSINSTAL TPW031 device-name:[directory-name]

The value of device-name: is the specification of the drive on which the :CD-ROM is mounted and directory-name is the location of the product saveset on the library CD (refer to the Software Products Library Master Index for the directory name). Example 2-1 shows the output from a sample installation.

Example 2-1 Sample Client Installation

OpenVMS VAX Software Product Installation Procedure V6.2 It is 8-DEC-1998 at 11:31. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: NOTES$0145_11* DECW$TE_0C4F KNEELAND FAL_14260004 DECW$TE_0688 _FTA57: _FTA58: ACMS01EXC001000 ACMS01EXC004000 ACMS004SP001000 ACMS01EXC00A000 ACMS00ASP001000 ACMS00ASP002001 * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: TPW V3.1 Beginning installation of TPW V3.1 at 11:31 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Installation of TP Desktop Connector for ACMS V3.1 client software started. ************************************************************************** * Copyright (C) 1990, 1999 by * * COMPAQ Computer Corporation, Houston, Texas * * ALL RIGHTS RESERVED. UNPUBLISHED RIGHTS RESERVED UNDER THE * * COPYRIGHT LAWS OF THE UNITED STATES. * ************************************************************************** %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[ACMSDI.V MS_CLIENTS]. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[ACMSDI.N ONVMS_CLIENTS]. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %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 ... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of TP Desktop Connector for ACMS V3.1 client software has ended. Installation of TPW V3.1 completed at 11:33 VMSINSTAL procedure done at 11:33

See Chapter 3 to continue with postinstallation tasks.

This chapter describes the procedures, on both the OpenVMS system where the gateway kit was installed and on your target desktop system, that are required for server-side and client-side applications to run and communicate.

3.1 After Installing TP Desktop Connector Gateway Kit

Post-installation tasks for TP Desktop Connector Gateway for ACMS are the same whether you install from the Software Products Library CD or the TPware Product Suite CD. See Chapter 10 for information.

For TP Desktop Connector Version 3.1 on the Software Products Library, the server-side sample application is part of the client kit, not the gateway kit. The client services files for OpenVMS are laid down when you use VMSINSTAL on the TPW031 saveset. See Section 3.3 for information on the server-side Avertz sample application.

3.2 After Installing TP Desktop Connector Client Kit

After installing the client kit from the Software Products Library CD, all the files needed for OpenVMS client applications are in place. If you are developing an OpenVMS client application, you should edit a startup file as shown in Section 3.2.1. If you are developing a client application for a different desktop platform, you should follow Sections Section 3.2.1 and Section 3.2.2.

3.2.1 Editing Startup Files

If TP Desktop Connector Gateway for ACMS is already installed on the same system, edit the gateway startup file, SYS$STARTUP:ACMSDI$STARTUP.COM. Remove the comment character (!) from the following logical name definitions for the client directories:

$! The next three logical name definitions pertain to TP Desktop Connector $! client libraries and Motif samples and should be defined only after installing $! clients on the same system where the Gateway is installed. $! $! define/system acmsdi$vms sys$common:[acmsdi.vms_clients] $! define/system acmsdi$nonvms_clients sys$common:[acmsdi.nonvms_clients] $! define/system acmsdi$examples_avertz_motif sys$common:[syshlp.examples.acmsdi.avertz.motif]

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] $ define/system acmsdi$nonvms_clients sys$common:[acmsdi.nonvms_clients] $ define/system acmsdi$examples_avertz_motif sys$common:[syshlp.examples.acmsdi.avertz.motif]

3.2.2 After Installing Non--VMS Clients

In addition to OpenVMS client libraries, the client installation loads the self-extracting archive files shown in Table 3-1 on your OpenVMS system. (The logical name ACMSDI$NONVMS_CLIENTS is defined in Section 3.2.1.)

Table 3-1 Contents of ACMSDI$NONVMS_CLIENTS

ALPHA32.EXE	Runtime and development kit for the entire TPware product suite on DIGITAL Alpha platforms running Microsoft Windows NT
DUNIX.EXE	TP Desktop Connector client services 1 and samples for DIGITAL UNIX systems
INTEL16.EXE	TP Desktop Connector client services 1 and samples for 16-bit Microsoft operating systems (DOS, Windows 3.11, or Windows 95) on Intel platforms
INTEL32.EXE	Runtime and development kit for the entire TPware product suite on Intel platforms running 32-bit Microsoft operating systems (Windows NT or Windows 95)
ACMS_DESKTOP.INSTALLER	TP Desktop Connector client services 1 and samples for Apple Macintosh systems

After installing the TP Desktop Connector client kit on an OpenVMS system, transfer the appropriate archive file to your desktop system and execute it. The archive expands, and the resulting files can then be used.

For example, to transfer the client files to a Windows NT system on an Intel platform:

1. Copy from the OpenVMS system the INTEL32.EXE file. Use a network file transfer utility such as FTP. For example:
   1. On the client system, create a subdirectory to store the software:

      > mkdir c:\tpw031

   2. Change directory to the newly created subdirectory:

      > cd c:\tpw031

   3. Connect to the OpenVMS system that contains the archive file:

      > ftp nodename . . . login to host . . . FTP>

      
      The value of nodename is the name of the OpenVMS system on which the archive is installed. At the FTP prompts, supply the OpenVMS user name and password. If you successfully log on to the OpenVMS system, type commands at the FTP prompt to copy the archive file from the OpenVMS directory to the client system and close the FTP utility. For example:

      FTP> binary FTP> cd sys$common:[acmsdi.nonvms_clients] FTP> get intel32.exe FTP> quit

2. On the client system, expand the archive file and delete it to recover disk space. For example:

   > intel32 > del intel32.exe

3. If you are developing an application for Win32 systems, see Chapter 5. For non--Win32 systems, see Chapters 6 and 7.

Or, to transfer the client files to a DIGITAL UNIX system:

1. Copy from the OpenVMS system the dunix.exe file. Use a file transfer utility such as FTP. For example:
   1. On the client system, create a directory under your home directory:

      > mkdir tpw031dir

   2. Change to the new directory:

      > cd tpw031dir

   3. Connect to the OpenVMS system that contains the archive file:

      > ftp nodename . . . login to host . . . ftp>

      
      The value of nodename is the name of the OpenVMS system on which the archive is installed. At the FTP prompts, supply the OpenVMS user name and password. If you successfully log on, type commands at the FTP prompt to copy the archive file and close the FTP utility. For example:

      ftp> binary ftp> cd sys$common:[acmsdi.nonvms_clients] ftp> get dunix.exe ftp> quit

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

3. The archive expands into two tar files. See Section 6.4.

The client services library is preconfigured for DECnet network access. To build applications that use NetWare or TCP/IP as a transport, you must reconfigure the library before creating executable programs.

The following steps are necessary to set up the client services library for NetWare or TCP/IP access:

1. Remove the DECnet object from the library with the following command:

   $ library/delete = net_decnet acmsdi$client_objlib.olb

2. For NetWare, insert the NetWare transport access module into the library with the following command:

   $ library/insert acmsdi$client_objlib.olb net_netware.obj

   
   For TCP/IP, insert the TCP/IP transport access module into the library with the following command:

   $ library/insert acmsdi$client_objlib.olb net_tcpip.obj

After these steps, you are ready to build TP Desktop Connector applications that use NetWare or TCP/IP as a transport. Table A-1 shows the files that are added to your desktop system during the installation of the TP Desktop Connector client services for OpenVMS.

3.2.4 Installing the Motif Sample Client for OpenVMS

To install the Motif sample files on the OpenVMS desktop system, perform the following steps:

1. Create a directory on the desktop system to contain the sample files and move to that directory:

   $ create/dir [.motif_avertz] $ 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:

   $ copy cd:[vmsalpha.samples]vms_avertz.exe [] <>

3. Decompress the executable and restore the saveset:

   $ run vms_avertz.exe . . . [Return] accept the default output filename . . . $ backup/restore vms_avertz.sav/save *.*/log

4. Copy the Motif resource file to your home directory:

   $ copy m_avertz.dat sys$login:m_avertz.dat

Table A-2 lists the files that are added to your desktop system.

3.2.5 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:

1. If you have MMS, use the MMS makefile provided to build the m_avertz sample application. In the sample directory, run MMS using the following command:

   $ MMS

   
   If you download TP Desktop Connector libraries to a different location, edit the makefile to indicate the new location of the libraries.
   

   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, the first time that the makefile tries to create the DECwindows library, the makefile fails. When this happens, rerun MMS to continue the build.<>

   
   If you do not have MMS, use the makefile as a guide to build the application yourself.
2. 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 ACMS application, follow the procedures in Section 6.3.3 to set up the sample application on the ACMS system. After you set up the ACMS system, use the Session menu to sign in to the ACMS system. After you sign in, you can use the Rental menu to run the reserve task of the AVERTZ application.

The installation procedure is now complete and verified.

3.3 Setting Up the Avertz ACMS Sample Application on an OpenVMS System

The command procedure VR_DA_RUNTIME_SETUP.COM sets up the sample application. You need SYSPRV privilege to run the procedure. See the file ACMSDI$VR_APPLICATION_INFO.TXT in the ACMSDI$EXAMPLES_AVERTZ directory for more information on setting up the sample.

To prepare the AVERTZ sample application on the DIGITAL OpenVMS system, do the following:

1. Run the command procedure to set up the application:

   $ @ACMSDI$EXAMPLES_AVERTZ:VR_DA_RUNTIME_SETUP . . . $

2. Start the ACMS system (if necessary) and the application:

   $ ACMS/START SYSTEM $ ACMS/START APPLICATION VR_DA_APPL

3. Perform other management tasks related to your system, for example, authorizing user accounts. See the management information in DIGITAL 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.

3.3.1 Using the Avertz ACMS Sample with Rdb Version 6.0 with Multiversion

When you execute the VR_DA_RUNTIME_SETUP.COM file to set up the sample application, this command file invokes two option files, VR_READ_SERVER.OPT and VR_UPDATE_SERVER.OPT, which refer to the SYS$LIBRARY:SQL$USER library. On a system with Rdb Version 6.0 with multiversion installed, the SYS$LIBRARY:SQL$USER file is not available. Instead, 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 the appropriate library file. For example:

$ DEFINE SQL$USER SYS$LIBRARY:SQL$USER60

Modify the linker options files:

• ACMSDI$EXAMPLES_AVERTZ:VR_READ_SERVER.OPT
• ACMSDI$EXAMPLES_AVERTZ:VR_UPDATE_SERVER.OPT

Replace the line

SYS$LIBRARY:SQL$USERnn.OLB/LIBRARY

with the following:

SYS$USER/LIBRARY

3.3.2 Building the Avertz ACMS Sample with DECforms V1.4

The VR_FORM.IFDL file of the Avertz ACMS sample application cannot be compiled under DECforms Version 1.4. This is because the DECforms Version 1.4 IFDL parser no longer recognizes the colon symbol (:), which the VR_FORM.IFDL file uses.

To get around this problem, put double quotation marks around the text containing the ":" symbol in the VR_FORM.IFDL file.

For example, change the following:

Copy AVERTZ_CDD_FIELD:CUSTOMER_ID from Dictionary End Copy

To look like:

Copy "AVERTZ_CDD_FIELD:CUSTOMER_ID" from Dictionary End Copy

3.3.3 User Name Quotas for the Avertz ACMS Sample

The VR_DA_RUNTIME_SETUP.COM command file assigns quotas for the AVERTZ_EXC, AVERTZ_UPD, and AVERTZ_READ user names that are adequate for running the VR_DA_APPL sample application. If your system already has these user names defined, the quotas for these user names might be inadequate for VR_DA_APPL. If you are using the AVERTZ sample application, delete the AVERTZ_EXC, AVERTZ_UPD, and AVERTZ_READ user names before running VR_DA_RUNTIME_SETUP.COM to ensure that you get appropriate quotas for these user names.

To ensure the success of the operations in the VR_DA_RUNTIME_SETUP.COM command procedure, run it from the system account.