DECwindows Transport Interface
This chapter describes how to configure and manage the TCPware DECwindows Transport Interface if you are running OpenVMS version 5.5-2.
You may want to run local DECwindows applications remotely, or remote X Window System applications locally. If you are running OpenVMS version 5.5-2 (the minimum supported version of OpenVMS), you need to configure the DECwindows Transport Interface. If you have a later version of OpenVMS, simply use the transport interface supplied with HP's DECwindows product.
Note! The TCPware DECwindows Transport Interface is not available on OpenVMS Alpha v1.5 and OpenVMS VAX v6.1 (and later) systems. Use HP's DECwindows Transport Interface provided with DECwindows instead.
To configure the DECwindows Transport Interface, the remote system must have X Window System and TCP/IP support.
Check the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file that it contains the proper information. The transport name in the file can be either TCPWARE or TCPIP. If you are running OpenVMS v5.5-2, you can choose between using the TCPDRIVER or BGDRIVER transport interface:
If you enter TCPWARE, the server uses the TCPware transport (TCPDRIVER)
If you enter TCPIP, the server uses the UCX Compatibility Services (BGDRIVER)
If you are running OpenVMS Alpha v1.5 or OpenVMS VAX v6.1 and later, make sure to configure TCPIP as the DECwindows transport name instead of TCPWARE. The TCPware interface is not available with the latter versions of OpenVMS.
To use the TCPware DECwindows Transport Interface, perform these steps:
1 Configure the DECwindows Transport Interface during TCPware configuration, or at a later date, by entering the following command: $ @TCPWARE:CNFNET DECW
2 If the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file does not exist, create it by copying the DECW$PRIVATE_SERVER_SETUP.TEMPLATE file to *.COM. Then edit the file as follows:
a Locate the following commented-out line in the file:
$ ! DECW$SERVER_TRANSPORTS ==
(Ignore the DECW$SERVER_TRANSPORTS line in the later $DO_TCPIP section.)
b Remove the comment character ( ! ) and:
If configuring the TCPware transport, add the following to the line:
$ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,LAT,TCPWARE"
If configuring for UCX Compatibility Services, add the following to the line:
$ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,LAT,TCPIP"
3 If you are running DECnet, be sure to start the products in the order DECnet, TCPware, and DECwindows. (In any case, start TCPware before starting DECwindows.)
4 Restart DECwindows:
$ @SYS$MANAGER:DECW$STARTUP RESTART
If the DECwindows Transport Interface does not work, see Troubleshooting.
For security reasons, you usually must configure the target display host to allow incoming X Window System applications from the OpenVMS system host. You may need to enter the OpenVMS host name in a file on the target display host. Check the remote host system's documentation for details.
If the remote host is another OpenVMS system, its SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file should have the same changes as described in the previous section.
If the remote host is not an OpenVMS system, configure "security" there to allow incoming connections on the currently active session. Check the remote host system's documentation for details.
To display a locally run DECwindows application on a remote host:
1 Verify that your system manager configured the target display host to accept incoming X Window System connections.
2 When you are ready to run your DECwindows application, enter the following commands at the DCL prompt:
$ SET DISPLAY/CREATE/NODE=remote-node/TRANSPORT=TCPIP
$ RUN local-application
where remote-node is the remote workstation on which you want the application to display, and local-application is the name of the local application you want to display on the remote host.
For example, to display the DECW$CALC application on host DAISY:
$ SET DISPLAY/CREATE/NODE=DAISY/TRANSPORT=TCPIP
$ RUN SYS$SYSTEM:DECW$CALC
If you want to run a DECwindows application on a remote host and display it locally on the OpenVMS system running TCPware (see the matching items in the example shown in
1 Verify that your system manager configured DECW$PRIVATE_SERVER_SETUP.COM to use the TCPware transport or the TCP/IP transport. You need to know which transport is being used for step 6 of this procedure.
2 Verify that the Session Manager is running on the local system.
3 Select the Security... option from the Session Manager's Options menu.
4 Enter the remote node name in the security database next to the Node field.
If you want to display the application on your own node, use a zero (0) for the node name.
If the remote node is a new entry, add it first so that it appears in the Authorized Users field, in the format transport node username.
5 Enter an asterisk (*) as the Username (you cannot restrict sessions based on usernames with TCP/IP).
6 Enter TCPIP or TCPware as the Transport based on how you set the transport in the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file, as described in the Setting up the DECwindows Transport Interface section.
Figure 30-1 DECwindows Security Options Screen see graphic
Note! The security records in the database are OpenVMS account-specific. If you enter the remote node name and TCPIP while you are in OpenVMS account SMITH, someone must be logged in as SMITH at the time you try to display the remote application.
See your DECwindows or Motif documentation for more information. Also see the remote host documentation for details on how to direct the application's display to the OpenVMS system.
If the DECwindows Transport Interface is not working:
Reinstall TCPware if you originally installed TCPware on VMS or OpenVMS versions 5.0, 5.1 or 5.2, and upgraded to version 5.3 or later. You need only reinstall TCP-OpenVMS, and not the FTP, TELNET, SMTP, or NFS products. Then reconfigure the DECwindows Transport Interface.
After reinstalling TCP-OpenVMS, you will have these files on your OpenVMS system:
Make sure you have basic connectivity between the two systems in both directions. You can use any utility, such as TELNET or PING, that is supported on both systems.
Check the TCPWARE:HOSTS. file on the OpenVMS system and make sure the other system's internet address is in it.
Make sure "Security" is configured to allow incoming connections on the currently active session. (See your DECwindows or Motif documentation for information.)
Use the NETCU SHOW CONNECTIONS command on the TCPware for OpenVMS system to make sure the server is listening for incoming connections.
You should see an entry for *.6000 in the Local Address column, in the LISTEN state. If this entry is not there, double-check the configuration steps above.
Check if the SYS$MANAGER:DECW$SERVER_x_ERROR.LOG file exists, and see if it contains any useful messages.
Error messages about fonts or font files usually indicate that the target system does not have the necessary fonts to display the application.
Double-check your OpenVMS system startup file to be sure that DECwindows starts after TCPware.