Compaq TP Desktop Connector Installation Manual
Compaq TP Desktop Connector Installation Manual

Compaq TP Desktop Connector Installation Manual

Tp desktop connector for acms
Table of Contents

Advertisement

Quick Links

Compaq TP Desktop Connector
for ACMS

Installation Guide

Order Number: AA–PG9DK–TE
May 2002
This document provides information about installing the Compaq TP
Desktop Connector software on desktop systems, and about installing the
Compaq TP Desktop Connector Gateway for ACMS software on systems
running the Compaq OpenVMS operating system and Compaq ACMS
software. It also describes activities associated with these installations,
such as the verification procedure.
Revision/Update Information:
Software Version:
Compaq Computer Corporation
Houston, Texas
This is a revised manual.
Compaq TP Desktop Connector
Version 3.2

Advertisement

Table of Contents
loading

Summary of Contents for Compaq TP Desktop Connector

  • Page 1: Installation Guide

    This document provides information about installing the Compaq TP Desktop Connector software on desktop systems, and about installing the Compaq TP Desktop Connector Gateway for ACMS software on systems running the Compaq OpenVMS operating system and Compaq ACMS software. It also describes activities associated with these installations, such as the verification procedure.
  • Page 2 Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice.
  • Page 3: Table Of Contents

    Contents Preface ........... . . Part I Using the Software Products Library CD 1 Before Installing TP Desktop Connector from the Software Products Library CD...
  • Page 4 3.3.1 Using the Avertz ACMS Sample with Rdb Version 6.0 with Multiversion ........3–7 User Name Quotas for the Avertz ACMS Sample .
  • Page 5 7 Installing the TP Desktop Connector Client Services on Non-Windows Systems Overview of the Client Services Installation ....7–1 7.1.1 Software Prerequisites ......7–2 Disk Space .
  • Page 6 9 Installing TP Desktop Connector Gateway for ACMS Software General Installation Information ......9–1 9.1.1 Accessing the Online Release Notes ....9–1 9.1.2 Files and Logical Names Installed on Your System .
  • Page 7 A Files Installed B Common Configuration Errors Errors Related to the Desktop System ..... B–1 B.1.1 Errors on OpenVMS Desktops ......B–1 B.1.2 Errors on Tru64 UNIX Desktops .
  • Page 9: Intended Audience

    OpenVMS platforms), or superuser (for Tru64 UNIX platforms) privileges, and you should be familiar with your operating system’s installation procedure. Related Software Compaq TP Desktop Connector is part of a transaction processing software suite that also contains the following product variants: •...
  • Page 10 • Compaq TP Desktop Connector for ACMS Client Application Programming Guide • Compaq TP Desktop Connector for ACMS Client Services Reference Manual • Compaq TP Desktop Connector for ACMS Gateway Management Guide Other manuals contain information about installing and managing your ACMS system and TP Desktop Connector Gateway for ACMS software: •...
  • Page 11 Finally, the Compaq TP Desktop Connector Release Notes contain informa- tion about new features and current restrictions for TP Desktop Connector software. In your Web browser, open the file in dskcon_release_notes.htm directory on the TPware Product Suite CD. On the OpenVMS...
  • Page 12 TP Desktop Connector Represents the Compaq TP Desktop Connector product software. Gateway Represents the Compaq TP Desktop Connector Gateway for ACMS software. UPPERCASE In text, the names of OpenVMS directories, commands, logicals, and so on, are set in all capital letters.
  • Page 13: Systems

    Convention Description courier This font indicates a command, programming language, or an object on your screen. user input In examples, letters that you actually type are highlighted in boldface type. node In syntax format and examples, italic type indicates variables, parameters, or arguments.
  • Page 15: Before Installing Tp Desktop Connector From The Software

    Part I Using the Software Products Library CD Part I describes how to install Compaq TP Desktop Connector and Compaq TP Desktop Connector Gateway for ACMS software from the OpenVMS Software Products Library compact disk. Part I presents the following major topics: •...
  • Page 17 1.1 Overview of the Software Products Library Installation The Compaq TP Desktop Connector software is delivered in two distinct product savesets, one for the gateway software that runs on the OpenVMS platform and one for all types of desktop clients: •...
  • Page 18 Compaq TP Desktop Connector software. 1.2 Software and Hardware Prerequisites The Compaq TP Desktop Connector Software Product Description (SPD), included in the product kit, contains complete information on software products, networks, and systems required for installing and using TP Desktop Connector client and gateway software.
  • Page 19: Tp Desktop Connector Disk Space Requirements

    In addition, installing TP Desktop Connector software requires a certain amount of free storage space. Table 1–1 summarizes the storage requirements for TP Desktop Connector during and after installation. Table 1–1 TP Desktop Connector Disk Space Requirements Blocks During Blocks After Installation Installation TP Desktop Connector Gateway for ACMS software...
  • Page 21: Tp Desktop Connector Files On The Software Products

    Installing TP Desktop Connector from the Software Products Library CD This chapter explains how to install Compaq TP Desktop Connector and Compaq TP Desktop Connector gateway for ACMS from the Software Products Library CD. Table 2–1 shows the contents of the TP Desktop Connector directory on the Software Products Library CD.
  • Page 22 After you locate the product saveset, follow the instructions for VMSINSTAL 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 TPW032 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...
  • Page 23 Example 2–1 (Cont.) Sample Client Installation Installation of TP Desktop Connector for ACMS V3.2 client software started. ************************************************************************** Copyright (C) 1990, 1999, 2000, 2002 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...
  • Page 25: Library Cd

    After Installing from the Software Products Library CD 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 the Gateway Software Post-installation tasks for TP Desktop Connector Gateway for ACMS software are the same whether you install from the Software Products Library CD or...
  • Page 26: Contents Of Acmsdi$Nonvms_Clients

    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.
  • Page 27 3.2.2.1 Transferring Client Files to a Windows System To place the client files on a Windows system, transfer the appropriate archive file from the ACMSDI$NONVMS_CLIENTS directory on the OpenVMS system. For example: 1. Use a network file transfer utility such as FTP to copy from the OpenVMS system the INTEL32.EXE file (see Table 3–1).
  • Page 28 3.2.2.2 Transferring Client Files to a Tru64 UNIX System To place the client files on a Tru64 UNIX system, transfer the appropriate archive file from the ACMSDI$NONVMS_CLIENTS directory on the OpenVMS system. For example: 1. Use a network file transfer utility such as FTP to copy from the OpenVMS system the file (see Table 3–1).
  • Page 29: Installing The Client Services Interface On Openvms

    3.2.3 Installing the Client Services Interface on OpenVMS Systems The client services library is preconfigured for DECnet network access. To build applications that use 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 TCP/IP access: 1.
  • Page 30: Setting Up The Avertz Acms Sample Application On An

    You need SYSPRV privilege to run the procedure. Refer to 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 Compaq OpenVMS system, do the following: 1. Run the command procedure to set up the application:...
  • Page 31: Multiversion

    3. Perform other management tasks related to your system, for example, authorizing user accounts. Refer to the 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.
  • Page 32: User Name Quotas For The Avertz Acms Sample

    3.3.2 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.
  • Page 33: Vr_Da_Bld_Mms.com Parameters

    3. Run the command procedure VR_DA_BLD_MMS.COM without parameters: $ @ACMSDI$EXAMPLES:VR_DA_BLD_MMS All the setup and build activities are performed. To perform a specific activity, specify one of the parameters in Table 7–1. Table 3–2 VR_DA_BLD_MMS.COM Parameters Keyword Activity Run MMS to build VR_DA_APPL Set up the CDD dictionary and directories for VR_DA_APPL Create the VEHICLE_RENTALS database After Installing from the Software Products Library CD 3–9...
  • Page 35 Part II Installing the TP Desktop Connector Client Software Part II describes Compaq TP Desktop Connector software installation from the TPware Product Suite CD on a client system and presents the following major topics: • TPware Product Suite CD-ROM Overview •...
  • Page 37: Tpware Product Suite Cd-Rom Contents

    TPware Product Suite CD-ROM Overview This chapter describes the TPware Product Suite CD distribution medium from which you install TP Desktop Connector software and related components. 4.1 TPware Product Suite CD-ROM Contents The TPware Product Suite CD contains all the software required for development and deployment of TP Desktop Connector client applications.
  • Page 38 Table 4–1 (Cont.) Contents of the TPware Product Suite CD Name Contents dskcon_release_notes.htm Compaq TP Web Connector Release Notes (HTML dskcon_release_notes.pdf and PDF editions) tpware_readme.txt Text file to read before proceeding with product installation webcon_release_notes.htm Compaq TP Web Connector Release Notes (HTML webcon_release_notes.pdf...
  • Page 39: Installation Overview

    Your bill of materials (BOM) specifies the number and contents of your distribution media. Be sure to verify the contents of your kit with this information. If your kit is damaged or incomplete, contact your Compaq representative. 5.1 Installation Overview The TPware Product Suite CD contains all the software required for development or deployment of TP Desktop Connector client applications.
  • Page 40: Product Licenses

    5.2.1 Product Licenses To install TP Desktop Connector products, you must have a Product License Key. This is a paper certificate that contains information about the license you have to run a particular piece of software. You are asked to enter the license key during the installation procedure.
  • Page 41: Removing The Installed Software

    Programs 3. Choose the program group. TPware Products If you chose a different program group while installing Compaq TP Desktop Connector, that group name is displayed on the Programs menu in place of TPware Products Before Installing TP Desktop Connector Software 5–3...
  • Page 42 To remove the software using the system Add/Remove Programs utility: 1. Double click the icon in the Add/Remove Programs Control Panel window. 2. Choose the item. Compaq TPware 3. Click the button. Add/Remove... 5–4 Before Installing TP Desktop Connector Software...
  • Page 43: Installation Procedure On Windows Operating Systems

    Installing TP Desktop Connector Software on Windows Operating Systems This chapter describes the procedures for installing or reinstalling the Compaq TP Desktop Connector software from the TPware Product Suite CD running on a Windows system and also contains information on postinstallation tasks on Windows systems.
  • Page 44: After Installing Tp Desktop Connector Software

    Return to a previous dialog box Back Exit without completing the installation Cancel Follow the instructions in the dialog boxes to select installation of Compaq TP Desktop Connector. program checks whether there is sufficient disk storage, copies setup appropriate files, and performs registry operations.
  • Page 45: Accessing The Acms System

    6.2.2 Accessing the ACMS System For access to a Compaq ACMS transaction processing system, the TP Desktop Connector Gateway for ACMS must be installed on the OpenVMS system. The gateway software is distributed on a separate CD included in the distribution kit;...
  • Page 46: Code Conversion Libraries For Kanji

    C:\TPware\STDL_RT\bin\divb.dll C:\TPware\STDL_RT\bin\msvcrt40.dll To verify the success of your TP Desktop Connector client services installation, you can run the Visual Basic sample application. Follow these steps: 1. Open the VBAVERTZ project. 2. Verify that all the required files were loaded (see the VBAVERTZ project window): vbavertz.bas mainmenu.frm...
  • Page 47: Overview Of The Client Services Installation

    Compaq TP Desktop Connector for ACMS Client Application Programming Guide • Compaq TP Desktop Connector for ACMS Client Services Reference Manual 7.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 not mount this CD directly on your desktop system.
  • Page 48: Software Prerequisites

    Sections 7.1.1 through 7.1.3 discuss the prerequisites and requirements necessary before installing the TP Desktop Connector client services and sample files. Installation instructions are organized by platform: For this platform See . . . Compaq OpenVMS systems Section 7.2 Tru64 UNIX systems Section 7.3 7.1.1 Software Prerequisites...
  • Page 49: Installing The Client Services For Openvms

    7.2 Installing the Client Services for OpenVMS The client services files for OpenVMS are provided as a compressed saveset that you can copy from the TPware Product Suite CD mounted on your desktop platform. After you copy the client services software to the client system, decompress the file and restore the saveset.
  • Page 50: Installing The Motif Sample Client For Openvms

    3. The TP Desktop Connector library is preconfigured for DECnet network access. To build applications that use TCP/IP as a transport, you must reconfigure the library before creating executable programs. The following steps are necessary to set up the TP Desktop Connector library for TCP/IP access: a.
  • Page 51: Verifying The Motif Sample Installation On Openvms

    $ run vms_avertz.exe accept the default output filename Return $ 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. 7.2.3 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.
  • Page 52: Openvms System

    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 a Compaq OpenVMS system, do the following: 1. Run the command procedure to set up the application: $ @ACMSDI$EXAMPLES_AVERTZ:VR_DA_RUNTIME_SETUP 2.
  • Page 53: Using The Avertz Acms Sample With Rdb Version

    7.2.4.1 Using the Avertz ACMS Sample with Rdb Version 6.0 with Multi-Version 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 reference the SYS$LIBRARY:SQL$USER library. On a system with Rdb Version 6.0 with multi-version installed, the SYS$LIBRARY:SQL$USER file is not available.
  • Page 54: Rebuilding The Avertz Acms Sample

    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]. 7.2.4.4 Rebuilding the Avertz ACMS Sample Executables are provided for the sample. You do not need to rebuild the sample to run it.
  • Page 55: Installing The Tru64 Unix Client Software

    7.3 Installing the Tru64 UNIX Client Software The TP Desktop Connector client services and sample application files are distributed on the Software Products Library CD and on the TPware Product Suite CD. If you are installing the software from the TPware Product Suite CD (see Section 5.1), you have two files that you transfer to a Tru64 UNIX desktop system.
  • Page 56: Platforms

    3. You can copy the client services library to , so /usr/lib/libacmsdi.a that you can refer to it in your link command as ’-lacmsdi’ . You need superuser privileges to copy into the directory. /usr/lib Copy the TP Desktop Connector client library to the system directory: # cp libacmsdi.a /usr/lib/libacmsdi.a You can leave the TP Desktop Connector library in the client services directory.
  • Page 57: Platforms

    The sample makefile and executables for Motif on Tru64 UNIX use TCP/IP as the default transport. If you have changed the client services library to use DECnet, you must relink the sample application before you run it. 7.3.2 Verifying the Motif Sample Installation on Tru64 UNIX Platforms Compile, link, and run the source code for the sample client program to verify your capability to build applications.
  • Page 59 Part III Installing the Gateway Software Part III describes Compaq TP Desktop Connector Gateway for ACMS software installation from the TPware Product Suite CD on an OpenVMS system and presents the following major topics: • Preparing to Install TP Desktop Connector Gateway for ACMS Software •...
  • Page 61: Required Operating System Components

    8.1 Required Operating System Components See the Compaq TP Desktop Connector Software Product Description (SPD) for a complete list of required operating systems for the Compaq TP Desktop Connector gateway for ACMS. 8.2 Prerequisite Software The Software Product Description (SPD), a copy of which is included in the product kit, contains a list of the prerequisite software, and a complete list of the products that are compatible with this version of gateway software.
  • Page 62: Privileges And Authorization

    At the end of the installation procedure, if the gateway system components were installed, the gateway process on OpenVMS is started using the same user name that you use to install the product. Compaq recommends that you run the gateway under the user name SYSTEM or another user name with a [1,4] UIC.
  • Page 63: Openvms License Management Facility

    For the gateway process to be properly started, the user name under which the installation is done must be an authorized ACMS agent. Use the ACMSUDU Utility to authorize the user name. For example: $ SET DEFAULT SYS$SYSTEM $ RUN ACMSUDU UDU>...
  • Page 64: System Disk Backup

    8.3.4 System Disk Backup At the beginning of the installation, VMSINSTAL asks whether your system disk is backed up. Compaq recommends that you always do a system disk backup before installing new software on the operating system. Use the backup procedures that are established at your site to do this backup.
  • Page 65 2. If the device is not mounted, enter a command in the following format: MOUNT/OVERRIDE=ID device-name For example: $ MOUNT/OVERRIDE=ID DKA200: 3. Locate the distribution files. Use a DIRECTORY command in the following format and specify the indicated directory specification and saveset name. DIRECTORY device-name:[000000]ACMSDI*.* The command lists the various backup savesets.
  • Page 67: General Installation Information

    Installing TP Desktop Connector Gateway for ACMS Software This chapter describes how to install Compaq TP Desktop Connector gateway for ACMS software. Section 9.1 provides helpful information about installing the gateway software. Section 9.2 contains a step-by-step description of the installation procedure.
  • Page 68: Files And Logical Names Installed On Your System

    9.1.2 Files and Logical Names Installed on Your System The following files contain a list of the files added to your system by the gateway installation: SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$FIRST_FILES.DAT SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_ADD_FILES.DAT SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_AVERTZ_FILES.DAT SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_COMMON_FILES.DAT SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SAMPLE_EMPLOYEE_FILES.DAT SYS$COMMON:[SYSTEST.ACMSDI]ACMSDI$SYSTEM_FILES.DAT You can display or print these files after you install the gateway software. After the installation, if the gateway is started (by ACMSDI$STARTUP.COM), the following logical names are added to your system: ACMSDI$EXAMPLES...
  • Page 69: Aborting The Installation

    9.1.4 Aborting the Installation To abort the installation procedure at any time, press . When you press Ctrl/Y , the installation procedure deletes all files it has created up to that point Ctrl/Y and exits. You can then start the installation again. 9.2 Installation Procedure Perform the steps in the following sections to install the gateway software.
  • Page 70: Installation Questions

    3. Execute the installation procedure. For example: $ @SYS$UPDATE:VMSINSTAL ACMSDI DKA200:[000000] OPTIONS N This command begins installing the ACMSDI saveset found in the directory [000000] on the CD device named DKA200. VMSINSTAL asks several installation questions as described in Section 9.2.2. 9.2.2 Installation Questions This section discusses the questions that appear during the installation.
  • Page 71 Please mount the first volume of the set on DKA200:. * Are you ready? YES %MOUNT-I-MOUNTED, ACMSDI mounted on DKA200: The following products will be processed: ACMSDI V3.1A Beginning installation of ACMSDI V3.1A at 13:14 %VMSINSTAL-I-RESTORE, Restoring product save set A... If you enter the wrong device name when you invoke VMSINSTAL and need to restart the installation, answer NO in response to the Are you...
  • Page 72 * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, Product’s Release Notes have been moved to SYS$HELP. c Compaq Computer Corporation. 1999. All Rights Reserved. The name of the Release Notes file installed by VMSINSTAL consists of the current product name and version number.
  • Page 73: Informational Messages

    VMSINSTAL asks whether you have a PAK installed. You can install gateway software prior to registration; however, the software is unusable until you register the license. Looking up the Product Authorization Information. Product: TP-DESKTOP-ACMS Producer: Version: 3.1A Release Date: 31-AUG-1999 * Does this product have an authorization key registered and loaded? YES If you answer NO, the installation completes but the IVP is not run.
  • Page 74: Running The Installation Verification Procedure

    If the disk has quotas enabled, a message is displayed. The account must have sufficient disk quotas to install. Refer to Table 8–1. 9.2.4 Running the Installation Verification Procedure If you chose to run the IVP, VMSINSTAL runs it next. When the IVP runs successfully, you see the following messages displayed: %RUN-S-PROC_ID, identification of created process is 210031D5 Starting Server ACMSDI$SERVER...
  • Page 75: Installation Failures

    • The system disk used by the installation was corrupted. VMSINSTAL instructs you to restore the system disk from the backup copy and restart the installation. • VMSINSTAL continues the installation and can tell you to manually purge replaced files, even if you request that they be purged automatically. You can purge files, but remember that purging deletes all but the latest version of all files on your system disk.
  • Page 76: Ivp Error Recovery

    Chapter 11. If you reinstall gateway software, the IVP runs automatically if you answer YES to the IVP question. If you still cannot successfully run the IVP, contact your Compaq software specialist. 9–10 Installing TP Desktop Connector Gateway for ACMS Software...
  • Page 77: Editing The Openvms System Files

    Match client and server versions (see Section 10.3). • Read the management chapters in the appropriate document: Compaq TP Desktop Connector for ACMS Client Application Programming Guide Compaq TP Desktop Connector Getting Started See Chapter 11 for information about how to run the Installation Verification Procedure (IVP) after the software has been installed.
  • Page 78 Position the TP Desktop startup command line after the line that invokes the ACMS startup command procedure. For example: $ @SYS$STARTUP:ACMSTART.COM $ @SYS$STARTUP:ACMSDI$STARTUP.COM Note Start ACMS software before you start TP Desktop software. Starting TP Desktop software automatically enables the use of the DECnet communication transport.
  • Page 79: Editing The System Shutdown File

    10.1.2 Editing the System Shutdown File Find the following line, which stops the ACMS system, in the OpenVMS system shutdown file: $ @ACMSTOP.COM At some point before this line, add the following command line: $ @SYS$STARTUP:ACMSDI$SHUTDOWN.COM The command procedure cancels all active tasks and shuts down the TP Desktop process.
  • Page 80 ACMSDI_SRVDEAD -3020 ACMSDI_INVPROTOCOL -3025 10–4 After Installing TP Desktop Connector Gateway for ACMS Software...
  • Page 81: Ivp Operations

    Running the TP Desktop Connector Gateway for ACMS IVP This chapter describes how to run the gateway installation verification procedure (IVP) separately from the installation procedure. The IVP can be run as a part of the normal installation when you answer YES to the IVP question.
  • Page 82: Ivp Steps

    11.2.2 IVP Steps To run the IVP independently of the installation procedure, follow these steps: 1. Log in to the SYSTEM account: Username: SYSTEM Password: 2. Set your default to the test directory: $ SET DEFAULT SYS$TEST 3. Run the IVP using the following file specification: ACMSDI$IVP.COM You can run the IVP only on your current booted system.
  • Page 83 Part IV Appendixes Part IV provides reference material related to software installation on a system. Appendix A lists the files that are installed on your system for the various sample programs. Appendix B contains helpful hints about errors that might occur when you run one of the sample applications.
  • Page 85: A Files Installed

    Files Installed The following tables list the files that are installed on your systems for the various sample applications. Table A–1 Files Installed for TP Desktop Connector Client Services for OpenVMS Systems Files Description ACMSDI.H Include file for the TP Desktop Connector client services declarations ACMSDI$CLIENT_ Library for the TP Desktop Connector client services...
  • Page 86 Table A–2 (Cont.) Files Installed for the Motif Sample for OpenVMS Systems Name Description m_avertz.c Entry point for the sample; manages the main window of the sample m_avertz.h AVERTZ header file; defines global names m_avertz.opt Linker-purge options file for building the sample m_avertz.uid Runtime representation of the sample’s UIL definition m_avertz.uil...
  • Page 87: Files Installed For The Visual Basic Windows Sample

    Table A–2 (Cont.) Files Installed for the Motif Sample for OpenVMS Systems Name Description 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 m_sites.dat Contains data about AVERTZ sites; read in at run time m_transceive.c Presentation procedure that dispatches to specific routines in avertzpp...
  • Page 88: Files Installed For The Forced Nonblocking Tutorial

    Table A–4 Files Installed for the Forced NonBlocking Tutorial Name Description ACMSDI.BAS ACMSDI declarations for Visual Basic applications FORM1.FRM GUI objects and code for the Forced Nonblocking Tutorial main window FORMS.BAS DECforms message code definitions for Visual Basic FNBSAMPL.MAK Visual Basic make file for the Forced Nonblocking Tutorial FRMLOGIN.FRM GUI objects and code for the Forced Nonblocking Tutorial session login window...
  • Page 89 Table A–6 (Cont.) Files Installed for the Motif Sample for Tru64 UNIX Systems Name Description load_motif.sh Command shell to download the Motif sample from the OpenVMS system m_avertz Motif sample executable file m_avertz.c Entry point for the sample; manages the main window of the sample m_avertz.dat Font definitions for the sample screens...
  • Page 90 Table A–6 (Cont.) Files Installed for the Motif Sample for Tru64 UNIX Systems Name Description m_session.c Manages multiple sessions; switches context for using TP Desktop Connector gateway for ACMS routines and updates the user interface m_session.h Header file for m_session.c m_sitelist.c Creates (using m_sites.dat) and manages the list box of AVERTZ sites...
  • Page 91: B Common Configuration Errors

    Common Configuration Errors The following sections discuss some of the errors that can occur while running the TP Desktop Connector client services sample applications. B.1 Errors Related to the Desktop System Errors can arise when any of the following conditions exits: •...
  • Page 92: Errors Related To The Acms System

    If you encounter font-support problems running the program, modify the fonts used by editing the m_avertz resources file (m_avertz in the user’s home directory). B.2 Errors Related to the ACMS System If you have used the client services sample to communicate with the ACMS system, errors will occur if any of the following conditions exists: •...
  • Page 93: Index

    Index Configuration errors, B–1 ACMS starting, 10–2 DECnet, 6–3 stopping system, 8–4 DECnet enabling, 10–2 ACMSADU utility use, 8–3 Disk space, 5–2, 8–2 ACMSDI$CLIENT modification, 9–7 determining free, 1–3, 8–2 ACMSDI$SYSTEM_FILES.DAT, 9–2 requirements ACMS_DESKTOP_SERVER.DAT, 10–2 gateway, 1–3 Administrator privileges, ix non-Windows, 5–2 Windows, 5–2 see TP Desktop Connector client services...
  • Page 94 Files (cont’d) purge, 9–6 sample added to OpenVMS desktop system, License A–1 checking, 8–3 sample applications, A–1 installation question, 9–6 Forced Nonblocking product, 5–2 Visual Basic Sample Files, A–3 registration, 8–3 FTP, xii LMF requirement, 8–3 Logical name added to system, 9–2 Logical names Hardware defining, 3–2...
  • Page 95 Program group Transport creating, 6–2 automatic enabling, 10–2 Protocol mismatch, 10–3 parameter file enabling, 10–2 Purge files, 9–6 User name requirement, 8–3 Rdb with multi-version, 7–7 Rdb with multiversion, 3–7 Release Notes Verifying accessing, 9–1 Motif client sample, 3–5 Removing installed software, 5–3 OpenVMS Motif sample, 7–5 Resources, 7–2 Tru64 UNIX sample, 7–11...

Table of Contents