Compaq TP Desktop Connector
for ACMS
Installation Guide


Previous Contents Index


Chapter 6
Installing the TP Desktop Connector Client Services on Non--Win32 Systems

The TP Desktop Connector client services software was previously released as the ACMS Desktop "portable API" services. It allows client applications running on a variety of desktop platforms to call ACMS tasks. For the current TP Desktop Connector release, the client services software is distributed on the TPware Product Suite CD in folders (directories) according to the desktop platform. This chapter is also organized by platform:
For this platform See...
16-bit 1 Microsoft operating systems, that is, DOS or Windows 3.11 (also known as Windows for Workgroups (WfW)) Section 6.2
Compaq OpenVMS systems Section 6.3
Tru64 UNIX systems Section 6.4


1For Win32 Microsoft operating systems, see Section 5.2

Section 6.1 presents a general overview of the installation process and its prerequisites.

For information on TP Desktop Connector client services for Apple Macintosh systems, see Chapter 7.

For information on how to design and develop client applications using the TP Desktop Connector client services software, refer to the following ACMS books:

6.1 Overview of the Client Services Installation

The TPware Product Suite CD is in ISO 9660 standard format. The instructions in this chapter assume that you can mount this CD directly on your desktop system. If you can not, you will have to use ftp or some other network file transport to get the files from a Windows 95 or Windows NT system that has the TPware CD mounted.

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
  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.

The following sections discuss the preparations and requirements necessary before installing the TP Desktop Connector client services and sample files.

6.1.1 Software Prerequisites

The TP Desktop Connector SPD contains information on software prerequisites for installing TP Desktop Connector. Table 6-1 lists the products required to use the various client services sample applications.

Table 6-1 Client Services Sample Applications Software Requirements
Platform Products Required
DOS Microsoft COBOL Version 5.0 or higher
Microsoft Visual C++ Version 1.52 or higher
Windows 3.11 SDK Microsoft Windows Version 3.11 or higher
Microsoft Visual C++ Version 1.52 or higher
Visual Basic Microsoft Windows Version 3.11 or higher
Microsoft Visual Basic Version 4.0
Motif on OpenVMS VAX C for OpenVMS Version 3.0 or higher
DECwindows Motif for OpenVMS Alpha Version 1.0
Motif on Tru64 UNIX DEC C, DECwindows Developers Kit on Tru64 UNIX for OSF/Motif Version 1.1

6.1.2 Disk Space

Table 6-2 lists the disk space required for each of the desktop systems.

Table 6-2 TP Desktop Connector Client Services Disk Space Requirements on Non--Win32 Systems
OpenVMS VAX Client Number of Blocks
Client services library and network software 322
Common headers 31
Motif sample files 305
OpenVMS Alpha Client Number of Blocks
Client services library and network software 709
Common headers 31
Motif sample files 489
DOS and Windows 3.11 Client Number of Bytes
Client services libraries and network software 2 187 264
Common files 70 222
Kanji conversion libraries 182 748
COBOL sample files 421 888
Windows sample files 437 248
Macintosh Client Number of Blocks
Client services library, network software, and sample files 2 538
Common headers 31
Tru64 UNIX Client Number of Bytes
Client services library and TCP/IP module 261 748
Motif sample files 291 826
Common headers 30 206

6.1.3 Resources

Before you start the installation procedure, obtain the following:

6.2 Installing the Client Services for 16-Bit Microsoft Systems

TP Desktop Connector provides one self-extracting archive named i16clint.exe that contains all the client services files for both DOS and Windows 3.11 clients. The files contained within the archive include the static-link (LIB) and the dynamic-linked (DLL) libraries. Also included are individual object files and DLLs for the supported transports.

If you install the software from the TPware Product Suite CD (see Section 5.1), transfer the archive file from the Windows NT system to your desktop system. For example:

  1. On the client system, create a subdirectory to store the software:


    C:\> mkdir ACMSDI
    

  2. Change directory to the newly created subdirectory:


    C:\> cd ACMSDI
    

  3. Copy the archive file to the newly created subdirectory.


    C:\ACMSDI> copy E:\intel16\i16clint.exe
    

If you install the software from the Software Products Library CD (see Section 3.2.2.2), change directory to the location containing the client files.

To install the client services software, execute the archive file and delete it to recover disk space. For example:


> i16clint
> del i16clint.exe

The archive expands, and the resulting files can then be used.

If this is to be your working directory, you need to set the environment variables that define the paths for the libraries, include files, and executables. Add commands to your autoexec.bat file. For example:


set LIB=%LIB%;ACMSDI 
set INCLUDE=%INCLUDE%;ACMSDI 
set PATH=%PATH%;ACMSDI 

6.2.1 Setting Up the Client Services for DOS

The DOS client services use the static-link library ACMSDIL.LIB, which supports DECnet by default. Additional network transport object files are provided for the large-memory model, whose names reflects the transport they support.
Memory Model DECnet TCP/IP Netware
Large netdecl.obj nettcpl.obj netwarel.obj

If you are not using DECnet, remove the DECnet module and insert the module that corresponds to the transport you are using. For example, to set up up the large model for TCP/IP:


LIB ACMSDIL.LIB -NETDECL; 
LIB ACMSDIL.LIB +NETTCPL; 

6.2.2 Installing the Sample Client Application for DOS

The client services sample for DOS is written in Microsoft COBOL and is in a self-extracting archive file named i16cobol.exe. If you install the software from the TPware Product Suite CD (see Section 5.1), transfer the archive file from the Windows NT system to your desktop system. For example:


C:\ACMSDI\> mkdir cobol 
C:\ACMSDI\> cd cobol 
C:\ACMSDI\COBOL> copy e:\intel16\Samples\i16cobol.exe  

If you install the software from the Software Products Library CD (see Section 3.2.2.2), change directory to the location containing the client files.

To install the client services sample for DOS, execute the archive file and delete it to recover disk space. For example:


C:\ACMSDI\COBOL> i16cobol.exe 
C:\ACMSDI\COBOL> del i16cobol.exe

Table A-5 shows the resulting files.

The sample executable was built using the DECnet libraries. If you are not running DECnet, you need to relink the sample before you can run it.

6.2.3 Verifying the Client Services Installation for DOS

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 your desktop system to build the sample application:

The client services samples include two batch files to build the COBOL client program. You can modify these files according to your own software development environment. After you modify the files, run them. For example:


C:\ACMSDI\COBOL> bld-pps
   .
   .
   .
C:\ACMSDI\COBOL> bld-cli
   .
   .
   .

To run the sample client program, enter the following command:


C:\ACMSDI\COBOL> client

The client program displays the main menu of the AVERTZ Vehicle Rental System application.

To connect the sample program to the AVERTZ sample application, follow the procedures in Section 6.3.3 to set up the sample application on the ACMS system. You can 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

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 you prefer, when the transport is DECnet.

The client services sample for Windows 3.11 expects to find a DLL called acmsdi.dll To set up the client services for your network transport, copy one of the files below to your working directory and rename it acmsdi.dll.
DECnet TCP/IP Netware
acmsdiDN.dll acmsdiWS.dll acmsdiNW.dll

For example, to use TCP/IP with the Winsock interface:


C:\ACMSDI> mkdir sdk311 
C:\ACMSDI> copy acmsdiWS.dll sdk311\acmsdi.dll

There is an executable file, diTskLnk.exe, that supports multiple executables sharing a submitter session under Windows Version 3.1 using TCP/IP. Refer to Compaq TP Desktop Connector for ACMS Gateway Management Guide for information on this executable file.

6.2.5 Code Conversion Libraries for Kanji

TP Desktop Connector provides code conversion libraries for Kanji users, which convert Shift JIS code to DEC Kanji code and DEC Kanji code to Shift JIS code. You can link these libraries with your client application, if it requires Kanji code conversion.

These libraries are located in the following archive file:


E:\intel16\win16\jcnvwin.exe 

For usage information, refer to JCNVWIN_GUIDE.PS or JCNVWIN_GUIDE.TXT, which are installed when you expand the archive.

6.2.6 Installing the Sample Application for Windows 3.11

The client services sample for Windows 3.11 is written in C and is provided in the following self-extracting archive files.
i16sdklb.exe Contains both the sample sources and the make file for using the DECnet medium model static-link library.
i16sdkdl.exe Contains just the alternate files needed to rebuild the sample client against DLLs. The resulting executable file can work with any of the supported transports.

If you install the software from the TPware Product Suite CD (see Section 5.1), transfer the archive file i16sdklb.exe from the Windows NT system to your desktop system. For example:


C:\ACMSDI> cd sdk311 
C:\ACMSDI\SDK311> copy e:\intel16\Samples\i16sdklb.exe  

If you install the software from the Software Products Library CD (see Section 3.2.2.2), change directory to the location containing the client files.

To install the software, execute the archive file and delete it to recover disk space. For example:


C:\ACMSDI\SDK311> i16sdklb.exe 
C:\ACMSDI\SDK311> del i16sdklb.exe 

If you want the DLL version, first get the sources as above, then get the other archive i16sdkdl.exe, and run it. This overrides the static-link makefiles. For example:


C:\ACMSDI\SDK311> copy e:\intel16\Samples\i16sdkdl.exe  
C:\ACMSDI\SDK311> i16sdkdl.exe 
C:\ACMSDI\SDK311> del i16sdkdl.exe 

Table A-6 shows the resulting files.

6.2.7 Verifying the Client Services Installation on Windows 3.11

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 your desktop system to build the C language sample application:

To verify the installation of the TP Desktop Connector client services for Windows 3.11, follow these steps:

  1. Using the AVERTZ makefile, build the sample application by running nmake in the directory that contains the sample files.


    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:

The AVERTZ program displays the menu bar of the AVERTZ 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 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 Windows 3.11 installation procedure is now complete and verified.


Previous Next Contents Index