HP OpenVMS Systems Documentation

HP DECwindows Motif for OpenVMS
Management Guide

The use of LBX requires that the X display server be capable of interpreting the LBX protocol. On DECwindows Motif systems, you must enable the use of the LBX protocol through the DECW$SERVER_EXTENSIONS parameter.

To enable the LBX extension, modify the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file and redefine the DECW$SERVER_EXTENSIONS parameter so that it includes a value of "LBX." For example:

$ DECW$SERVER_EXTENSIONS == "LBX"

Save the file and restart the server.

3.7.2 Starting the Proxy Server

How you start an LBX proxy server determines the proxy server's type and how a client accesses the proxy server. Both methods use the LBXPROXY command; see the online help for the command to learn more about the available qualifiers and their values.

Before you start an LBX proxy server, ensure that the proxy server is properly authorized to connect to the X display server, as described in Section 3.7.2.1.

3.7.2.1 Authentication in a Proxy Server Environment

When the proxy server connects to an X server, the proxy server undergoes authentication in the same manner as a client. How the proxy server obtains its authentication information depends on the type of proxy server.

A managed proxy server obtains its authentication information from the proxy manager. The proxy manager in turn receives the authentication information from the client. The client's default authentication information is contained in the client's X authority file. The client can control which X authority file is used by using the /XAUTHORITY qualifier to the SET DISPLAY command. The client can supply explicit authentication information on the SET DISPLAY command using the /LBXAUTHENTICATE and /LBXDATA qualifiers. The client also has the option of using the /NOLBXAUTHENTICATE qualifier to specify that the authentication information come from the proxy server's current X authority file. For more information about the SET DISPLAY command qualifiers for LBX, see HP OpenVMS DCL Dictionary: N--Z.

A standalone proxy server obtains its authentication information from the information present in the current X authority file.

3.7.2.2 Starting a Managed Proxy Server

To start a managed LBX proxy server, place the following LBX service entry in the proxy manager's configuration file (see Section 3.7.6).

LBX MANAGED COMMAND SYS$MANAGER:DECW$LBXPROXY_SUB ["qualifiers"]

After the proxy manager is configured, no specific action is required to start the proxy server; the proxy manager starts the server when the manager receives the first client request.

3.7.2.3 Starting a Standalone Proxy Server

You can start a standalone LBX proxy server either in the current process or as a detached process. To start a standalone proxy server in the current process, use the LBXPROXY command.

LBXPROXY [qualifiers]

For example, to start a proxy server in the current process, assign it a server number of 50, and have the server act as a proxy for the X display server on remote1.cmp.com, use the following command:

$ LBXPROXY /DISPLAY="REMOTE1.CMP.COM:0"/SERVER=50/FIXED_SERVER

To start a proxy server as a detached process, use the DECW$LBXPROXY command procedure.

@SYS$MANAGER:DECW$LBXPROXY ["lbxproxy-qualifiers"] ["run-qualifiers"]

For example, to start a proxy server as a detached process, assign it a server number of 50, and have the server act as a proxy for the X display server on remote1.cmp.com, use the following command:

$ @SYS$MANAGER:DECW$LBXPROXY "/DISPLAY=""REMOTE1.CMP.COM:0""" + -
_$ "/SERVER=50/FIXED_SERVER"

Use the run-qualifiers parameter to pass any qualifiers to the RUN command used to invoke the LBXPROXY image. One use of this parameter might be to override the default LBXPROXY process characteristics or any values set by the logicals provided to modify these defaults.

See the online help for the LBXPROXY command to learn more about the available qualifiers and their values.

The proxy server listens on all configured transports specified with the /TRANSPORT qualifier when the proxy server is started. If the TCPIP transport has been selected, then the proxy server listens on all configured TCP/IP interfaces, regardless of whether they are IPv4- or IPv6-compatible.

The /DISPLAY qualifier allows the additional transport names discussed in Chapter 4. The interpretation of the TCP and TCPIP transport names as seen by the proxy server process is governed by the DECW$IPV6_SUPPORT logical name defined in the DECW$PRIVATE_APPS_SETUP.COM file.

3.7.4 Modifying the Default Proxy Server Process Characteristics

Table 3-4 lists the logicals that are provided to override the default LBXPROXY process characteristics specified on the RUN command generated by SYS$MANAGER:DECW$LBXPROXY.

You can stop an LBX proxy server either automatically or manually.

3.7.5.1 Stopping Automatically

To stop an LBX proxy server automatically, use the /ONEXIT=TERMINATE qualifier when you start the server. For standalone proxy servers, specify this qualifier either on the LBXPROXY command line or in the lbxproxy-qualifiers parameter of the SYS$MANAGER:DECW$LBXPROXY command procedure.

For managed servers, specify this qualifier in the parameters argument in the LBX service definition in the proxy manager's configuration file.

To stop an LBX proxy server manually, use the DCL STOP command.

3.7.6 The Proxy Manager Configuration File

The proxy manager configuration file contains the information that the proxy manager needs in order to locate proxy services. Each line in the configuration file can contain one of the following:

• Comment -- Comment lines must begin with an exclamation character (!) in the first character position. All other characters in the line are ignored.
• Managed service entry -- Managed service entries have the following format:

  service-name MANAGED COMMAND command-file [parameters]

  
  where:

  service-name	Specifies the name of the managed service. The service name is case-insensitive. If the file contains multiple entries with the same service name, only the first occurrence has any effect. For the LBX service, the service name must be LBX. Service names must use characters in the X Portable Character Set with the exception of the Space, Tab, and Newline characters.
  command-file	Specifies the name of the command procedure that the proxy manager should invoke to create a new instance of a proxy server for this service. For the LBX service, this argument is usually SYS$MANAGER:DECW$LBXPROXY_SUB.COM.
  parameters	Specifies any parameters to pass to the command procedure specified in the command-file argument. All characters following the space after the command-file argument are passed as parameters to the command procedure. For the LBX service, the command procedure expects one quoted parameter, that is, one or more command qualifiers.

  
  Currently, the only managed service supplied with DECwindows Motif is LBX.
• Unmanaged service entry -- Unmanaged service entries have the following format:

  service-name UNMANAGED address

  
  where:

  service-name	Specifies the name of the unmanaged service. The service name is case-insensitive. If the file contains multiple entries with the same service name, the manager tries each entry in order until an active and available proxy server is found. Service names must use characters in the X Portable Character Set with the exception of the Space, Tab, and Newline characters.
  address	Specifies the address of the proxy server in Inter-Client Exchange (ICE) format.

  
  Currently, no unmanaged service is supplied with DECwindows Motif.

You can configure the proxy manager either to start automatically when DECwindows Motif starts or to start manually at a later time.

3.7.7.1 Starting Automatically at DECwindows Motif Startup

To start the proxy manager at DECwindows Motif startup, edit the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file. For more information on customizing the Session Manager environment, see Chapter 4.

Table 3-5 describes the symbols present in this file that control the proxy manager.

To start the proxy manager manually, use the XPROXYMANAGER command:

XPROXYMANAGER [qualifiers]

For example, to start a proxy manager using the configuration file SYS$MANAGER:DECW$LBXPROXY.DECW$PMCFG and the log file SYS$MANAGER:DECW$PM.LOG, use the following command:

$ XPROXYMANAGER/CONFIGURATION=SYS$MANAGER:DECW$LBXPROXY.DECW$PMCFG -
_$ /LOG=SYS$MANAGER:DECW$PM.LOG

See the online help for the XPROXYMANAGER command to learn more about the available qualifiers and their values.

This chapter includes the following information that you can use after DECwindows has started. It describes the following topics:

• Setting the display
• Understanding the DECwindows Motif login process on both the New Desktop and Traditional DECwindows Desktop
• Customizing the login environment
• Customizing the startup environment
• Modifying the default behavior of the Session Manager
• Modifying system resource files
• Specifying client access control
• Customizing print formats

When a client application starts up, it opens one or more connections to a display server. The display server can be on the local system or on a remote system. The application needs to tell the underlying Xm, Xt, or Xlib routines the display server's node name and other connection information. This information is contained in a string called a display name.

In X Window System terms, the display name "specifies the hardware display name, which determines the display and communications domain to be used. [...] if the display name is NULL, it defaults to the value of the DISPLAY environment variable."

On OpenVMS systems, the display name takes the form of either a WSA device that contains the necessary server information or a display name string that specifies the necessary server information explicitly. If neither form of display name is provided, Xlib translates the logical name DECW$DISPLAY to obtain the display name. If the DECW$DISPLAY logical name is undefined, then Xlib translates the logical name DISPLAY. If the DISPLAY logical name is undefined, then Xlib translates the logical name SYS$OUTPUT.

You must have previously created the WSA device and specified the display server information using one or more SET DISPLAY commands. If no SET DISPLAY commands are issued, the DECW$DISPLAY and DISPLAY logical names are inherited from the parent process. Note that the SET DISPLAY command also sets the DECW$DISPLAY and DISPLAY logical names when the /CREATE qualifier is used and no logical name is specified.

4.1.1 The Display Name Format

The display name string format is as follows:

[transport/]node:[:]server[.screen]

transport

Specifies the transport to use to connect to the display server. You can specify any of the following transports. Table 4-1 lists all transport names supported by DECwindows Motif and their meaning. Note that the implementation of some transport names may differ slightly from that defined in the X specifications.

Table 4-1 Supported DECwindows Motif Transport Names

Transport Name	Meaning
DECNET	Uses the DECnet network protocols.
DNET	The X Window System name for the DECnet network protocols. DNET is equivalent to DECNET, in most instances.
INET	Uses the TCP over the IPv4 protocol. This option adds support for the X synonym for TCPIP. With the addition of IPv6 support, this is one of two transports to which TCPIP equates.
INET6	Uses the TCP over the IPv6 protocol, if available. If the IPv6 protocol is not available, the IPv4 protocol is used. This is one of two transports to which TCPIP equates.
LAT	Uses the LAT protocol. There is no X equivalent for this transport.
LOCAL	Uses shared memory between the server and client processes within the same host.
TCP	The X Window System name for the TCPIP protocol option. TCP is equivalent to TCPIP.
TCPIP	Uses the TCP protocol over a version of IP. Previously, this option was an X synonym for INET. With the addition of IPv6 support, this option now equates to either INET or INET6 depending on the setting of the DECW$IPV6_SUPPORT logical name. (See Section 4.4.3 for information about setting this logical name.)

This parameter is optional. By default, node names ending in a single colon use the TCPIP transport. If you specify a second colon instead of a transport name, the DECNET transport is used. If a DECnet node name ends in a colon, enclose the node name in double quotation marks (""). Addresses ending in a triple colon (:::) are interpreted either as INET6 or DECnet.

The node parameter must specify a node value compatible with the specified transport. When parsing the display name string, DECwindows Motif does not verify that the node and transport parameters are compatible. Incompatible parameters will cause a failure when the connection is actually attempted. If both the transport and node display name parameters are omitted, the LOCAL transport is assumed.

node

Specifies the DECnet node, TCP/IP host, LAT address, or local system name of the display server. Specify one of the following:

DECnet node	For the DECNET or DNET transport, specify a DECnet Phase-IV node name, a DECnet Phase-IV address, a DECnet Phase-V node name or alias, or a DECnet Phase-V address. Use 0 to specify the local node. DECnet node names can be enclosed in quotes (" ").
TCP/IP host	For the TCPIP, TCP, INET, or INET6 transport, specify a TCP/IP host name or address. See Table 4-2 and Table 4-3 for more information. Use 0 to specify the local node.
LAT service name	For the LAT transport, specify the name of the local system. The transport uses this value as a service name only.
Local system name	For the LOCAL transport, specify the name of the local system or 0.

All node names or addresses must be followed by a colon in addition to any trailing colons within the actual node parameter. You can optionally include a second colon to specify the DECNET transport; see the transport parameter description for more information. If both the transport and node display name parameters are omitted, the LOCAL transport is assumed.

When specifying a TCP/IP host name or address for the INET6 transport (or the TCPIP or TCP transports if DECW$IPV6_SUPPORT is defined as TCP_IS_INET6), specify any of the IPv6 formats in Table 4-2.

Table 4-2 Supported IPv6 Host Name and Address Formats

Format	Example
IPv6 host name or fully-qualified domain name	ashfld.franklin.mass.us
IPv6 normal address	FEDC:BA98:7694:3210:FEDC:BA98:7654:3210
IPv6 compressed address	::7654:3210
IPv4-compatible IPv6 address	::978.765.432.1
IPv4-mapped IPv6 address	::FFFF:978.765.432.1
RFC 2732 style IPv6 literal address	[FEDC:BA98:7694:3210:FEDC:BA98:7654:3210]

When specifying a TCP/IP host name or address for the INET, INET6, TCPIP, or TCP transport, specify any of the IPv4 formats in Table 4-3.

Table 4-3 Supported IPv4 Host Name and Address Formats

Format	Example
IPv4 host name or fully-qualified domain name	ashfld.franklin.mass.us
IPv4 normal address	978.765.432.10

server

Specifies the decimal number of the display server on the X server display system. Display numbers usually start at 0. A single display server system usually uses the number 0.

screen

Specifies the decimal number of the screen to be used on the specified X display server. Screen numbers start at 0. This parameter is optional. The default is screen number 0.