Technical data

Configuring XDMCP-Compatible X Displays
19.6 Configuring the XDM Server
If the DECwindows components are not found, TCPIP$CONFIG notifies you
and gives you the option of configuring XDM, with the assumption that before
you attempt to activate XDM you will install the DECwindows components.
TCPIP$CONFIG notifies you of this situation with the following prompt:
XDM requires DECwindows components that are not installed.
Attempts to activate XDM will fail.
Type C to continue with XDM configuration, or E to exit [ E ]:
• If necessary, use the template files located in SYS$SPECIFIC:[TCPIP$XDM]
to create an XDM_CONFIG.CONF, XSERVERS.TXT, XACCESS.TXT, and
XDM_KEYS.TXT file. These files are not required unless you want to:
Configure a non-XDMCP X display
Restrict access to a remote X server
Provide XDMCP authentication
Change the way XDM computes the display name for XDMCP clients.
• Run SYS$MANAGER:TCPIP$CONFIG to enable XDM.
19.6.1 Ensuring XDM Is Enabled and Running
To make sure that the XDM service is enabled and that the XDM process is
running, enter the following TCPIP command:
$ TCPIP SHOW SERVICE XDM
Service Port Proto Process Address State
XDM 177 UDP TCPIP$XDM 0.0.0.0 Enabled
19.7 Configuring Other X Displays
If you have an X terminal that does not support the XDMCP protocol, you
can manage this terminal by using an XSERVERS.TXT configuration file. See
Section 19.3.3 for information about how to create the configuration file.
If you are running Compaq eXcursion, refer to the Compaq PATHWORKS 32
eXcursion User’s Guide for configuration information. For all other X servers,
refer to the third-party X Window System software documentation for information
about how to configure their product.
19–8 Configuring XDMCP-Compatible X Displays