Document revision date: 10 November 2000

## Managing DECwindows Motif for OpenVMS Systems

Previous | Contents | Index

### C.2.11 X Terminals and Third-Party Workstations

> You cannot display from a DECwindows workstation to a third-party workstation.
> - The third-party workstation is not running the X Window System.

>   > Make sure the third-party workstation is running the X Window System.

> - The network software is incompatible.

>   > If you are running DECnet software, make sure that the third-party workstation is also running DECnet. If you are using TCP/IP, install the OpenVMS/ULTRIX Connection software (UCX) on the OpenVMS workstation, or install a third-party vendor's TCP/IP networking product. You do not need a UCX Product Authorization Key (PAK) to use UCX with DECwindows.

> - The network database definitions are incorrect.

>   > Make sure the DECnet or TCP/IP node name and node number definitions for both workstations are correct on both workstations.

> - The node name contains lowercase letters.

>   > Add an uppercase node name alias for the node name, or enclose the node name in double quotes, as in the following example:

>   >     $ SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE="ultrixnode"

> - Access control is not enabled on the third-party workstation.

>   > Consult the documentation for the third-party workstation for information about adding the OpenVMS node name to the server's access control list.

> You cannot display from a third-party workstation to a DECwindows workstation.
> - The third-party workstation is not running the X Window System.

>   > Make sure the third-party workstation is running the X Window System.

> - The network software is incompatible.

>   > If you are running DECnet software, make sure the third-party workstation is also running DECnet. If you are using TCP/IP, install the OpenVMS/ULTRIX Connection software (UCX) on the OpenVMS workstation, or install a third-party vendor's TCP/IP networking product. You do not need a UCX Product Authorization Key (PAK) to use UCX with DECwindows.

> - The network database definitions are incorrect.

>   > Make sure the DECnet or TCP/IP node name and node number definitions for both workstations are correct on both workstations.

> - The network software is not running.

>   > If you are using UCX, use the UCX$UCP loop command to verify that the other workstation responds to notification from your workstation, as follows:

>   >     $ RUN SYS$SYSTEM:UCX$UCP
>   >     UCX> LOOP DECW2
>   >     DECW2 is alive
>   >     UCX> EXIT

>   > The message DECW2 is alive means that UCX was started properly. If UCX was not started properly, a message similar to the following is displayed:

>   >     $ RUN SYS$SYSTEM:UCX$UCP
>   >     UCX> LOOP DECW2
>   >     DECW2 does not respond

>   > UCX must be started with the command file UCX$STARTUP. Add the following line to your SYS$MANAGER:SYSTARTUP_V5.COM file:

>   >     @SYS$STARTUP:UCX$STARTUP

>   > UCX should be started after DECnet has been started.

> - A network-specific OpenVMS DECwindows transport interface is not supplied.

>   > If you are using a third-party TCP/IP networking product, it must supply the file SYS$SHARE:DECW_TRANSPORT_name, where name is the product name.

> - The transport interface is not installed.

>   > If you are using a third-party TCP/IP networking product, the DECW_TRANSPORT_name file must be installed from the SYS$MANAGER:SYSTARTUP_V5.COM file with the following command:

>   >     $ INSTALL CREATE SYS$SHARE:DECW_TRANSPORT_name -
>   >     _$ /OPEN/SHARED/HEADER_RES/PROTECTED

>   > Use the following command from a privileged account to verify that the file is installed:

>   >     $ INSTALL LIST SYS$SHARE:DECW_TRANSPORT_name

> - The server is not listening for connections. Choose either of the following options:
>   - If you are using TCP/IP, you must use the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM customization file. If you do not have that file, copy the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE file to SYS$MANAGER: DECW$PRIVATE_SERVER_SETUP.COM. Add the following line to the .COM file:

>         DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"

>     Restart the server with the following command:

>         $ @SYS$MANAGER:DECW$STARTUP RESTART

>     This command stops all applications and restarts DECwindows. All workstations in the cluster will listen for TCP/IP connections. See Chapter 3 for more information about the private server setup file and for information about how to change individual workstations in a cluster. After restarting DECwindows, you should see messages similar to the following in SYS$MANAGER: DECW$SERVER_0_ERROR.LOG:

>             Now attach all known txport images
>             %DECW-I-ATTACHED, transport DECNET attached to its network
>             %DECW-I-ATTACHED, transport TCPIP attached to its network

>     There should be one message for each transport you listed in DECW$SERVER_TRANSPORTS, except for local.
> - Access control is not enabled on the OpenVMS workstation.

>   > Pull down Session Manager's Options menu and choose the Security menu item. Type the third-party node name in the Node entry box. If you are using DECnet, type the user name in the Username entry box and add it. Then type the user ID (UID) in the Username entry box and add it. If you are using the OpenVMS/ULTRIX Connection software (UCX) TCP/IP, type an asterisk (*) in the Username entry box, and type TCPIP in the Transport entry box. If you are using a third-party TCP/IP, follow the directions supplied by the third-party vendor.

>   > Note All node names are shown in the security list in uppercase, but they will match both uppercase and lowercase node names.

> You cannot display PostScript images on X terminals or on third-party workstations.
> - The X terminal or third-party workstation does not support the Display PostScript extension.

>   > The only solution is to get an X terminal workstation that supports the Display PostScript extension. The PostScript commands are performed by an extension to the server, not by a library on the client (application) side.

### C.2.12 X Server

> You cannot start a session on the workstation. Your keystrokes are not displayed on the screen.
> - The DECwindows X server has stopped working.

>   > Press Return. A user name prompt should appear. If it does not appear, set host to the workstation from another node. Log in to a privileged account and restart the server with the following command:

>   >     $ @SYS$MANAGER:DECW$STARTUP RESTART

>   > Then log out. If you cannot log in again, halt the workstation and reboot the operating system. After the system reboots, check the server error log file SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for possible problems. The server process runs with the name DECW$SERVER_0. It creates the SYS$MANAGER:DECW$SERVER_0_ERROR.LOG log file every time DECwindows Motif is activated. Always check this log file for error messages when you are experiencing problems. Always save the complete contents of the log file in case you must contact your Customer Support Center.
>   > The screen seems to be frozen. Your keystrokes are not displayed and cursors do not blink.
>   > - The DECwindows X server is performing a long operation for PEX, XIE, or PostScript.

>   >   > Wait for the operation to complete only if you are using one of the three server extensions. Some PEX operations might last minutes. XIE and PostScript should hold the server for no more than a few seconds before yielding.

>   > - The DECwindows X server is waiting for network I/O.

>   >   > Wait 30 seconds. The DECwindows X server will wait 30 seconds after its transport buffers fill. If the I/O still does not complete, the server will terminate the client connection and continue without intervention.

>   > - A client has grabbed the X server.
>   >   - Identify the client application and respond to any outstanding output requests. If the client application does not respond, set host to the workstation from another node. Use the SHOW SYSTEM command to identify the process id number of the application. Stop the application with the following command:

>   >         $ STOP/ID=process_id_number

>   >     If the screen does not free itself at this time, continue with the next problem resolution.
>   >   - The DECwindows X server has stopped working.
>   >     - Press Return. A user name prompt should appear. If it does not appear, set host to the workstation from another node. Log in to a privileged account and restart the server with the following command:

>   >           $ @SYS$MANAGER:DECW$STARTUP RESTART

>   >       Then log out. If you cannot log in, halt the workstation and reboot the operating system. After the system reboots, check the server error log file SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for possible problems. The server process runs with the name DECW$SERVER_0. It creates the SYS$MANAGER:DECW$SERVER_0_ERROR.LOG log file every time DECwindows Motif is activated. Always check this log file for error messages when you are experiencing problems. Always save the complete contents of the log file in case you must contact your Customer Support Center.
>   >     - See the problem statement titled "The top of the screen goes black..." in Section C.2.6.

>   Index | Contents

>   | privacy and legal statement |
>   6300PRO_010.HTML