![](/images/new-backgrounds/1165546/16554651x1.webp)
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 on your OpenVMS system (see Table
Table
DUNIX.EXE | TP Desktop Connector client services1 and samples for |
| Tru64 UNIX systems |
INTEL32.EXE | Runtime and development software for the entire TPware |
| product suite on platforms running Windows systems. |
1Formerly known as the ACMS Desktop ‘‘portable API’’ services.
After installing the TP Desktop Connector client software on an OpenVMS system, transfer the appropriate archive file to your desktop system and execute it (see Sections 3.2.2.1 through 3.2.2.2). After you expand the appropriate archive, the resulting files can then be used.