HP DECwindows Motif
for OpenVMS Alpha
New Features


Previous Contents Index

3.6.1.1.2 LBXPROXY Qualifiers

Enter LBXPROXY command qualifiers in the same manner as you would for any other DCL command. For managed servers, specify these qualifiers on the LBX service line in the proxy manager's configuration file.

/ATOMS=file-specification

Specifies the file that the proxy server should use for atoms control. The file SYS$MANAGER:DECW$ATOMCONTROL.TEMPLATE contains an example of an atom control file. This qualifier cannot be specified if the NOATOMS or NOLBX option is specified for the /OPTION qualifier.

The default is /ATOMS=SYS$MANAGER:DECW$ATOMCONTROL.DAT. However, effectively the default is not to use atom control because the installation process does not convert the SYS$MANAGER:DECW$ATOMCONTROL.TEMPLATE file to the SYS$MANAGER:DECW$ATOMCONTROL.DAT file.

At startup, the LBX proxy server "pre-interns" the atoms specified in the atom control file. The atom control file also controls when the proxy server should delay sending data to the X server. This is done by specifying the following:

The format of the atom control file is documented in the SYS$MANAGER:DECW$ATOMCONTROL.TEMPLATE file.

/CHEAT={ERRORS | EVENTS | NONE}

Specifies the level of cheating allowed on the X protocol for the sake of improved performance. The X protocol guarantees to the requesting party that all corresponding replies, events, or errors are returned to the requester in the same order as the original requests. The ERRORS option allows the proxy server to violate the X protocol with respect to errors. The EVENTS option allows the proxy server to violate the X protocol with respect to errors and events. The NONE option specifies that no protocol cheating is allowed.

The default is /CHEAT=NONE.

Warning

Some X applications may rely upon the correct ordering of events and errors. Enabling cheating may cause these applications to fail. Use this option at your own risk.

/DISPLAY={"network-address" | logical-name | device-name}

Specifies a network address, logical name, or device name that references the X server to which the proxy server should connect. A network address must be in the following form: "[transport/][node][:]:display[.screen]"

This option is ignored for managed proxy servers.

The default is /DISPLAY=DECW$DISPLAY.

/FIXED_SERVER
/NOFIXED_SERVER

Specifies that the proxy server should fail to start if the server number specified by the /SERVER qualifier is not available. See /SERVER qualifier for more information about server numbers. This option is useful for starting standalone servers as detached processes. In this case, the proxy server has no method to return the selected server number. This option is ignored for managed proxy servers.

The default is /NOFIXED_SERVER.

/MAXSERVER=value

Specifies the maximum number of X servers to which this proxy server can connect. This option is ignored for standalone servers. Specify a value from 1 to 63.

The default is /MAXSERVER=20.

/MOTION=value

Specifies the maximum number of pointer motion events that are allowed to remain unanswered between the proxy server and the X server. Specify a value from 1 to 32767.

The default is /MOTION=8.

/ONERROR={RECONNECT | TERMINATE}

Specifies the action taken when the proxy server encounters an internal error. This usually occurs when the proxy server loses its connection to the X server.
RECONNECT Specifies that the proxy server should clean up its internal state information and await further requests. If the proxy server is a standalone server, this option also specifies that the proxy server should reconnect to the X server. For managed proxy servers with multiple connected X servers, the proxy server will try to reconnect each server connection when it fails.
TERMINATE Specifies that the proxy server should exit. For managed proxy servers with multiple connected X servers, the proxy server will terminate only if all X server connections fail.

The default is /ONERROR=TERMINATE.

/ONEXIT={NOACTION | RESET | TERMINATE}

Specifies the action taken by this proxy server when the last client exits.
NOACTION Specifies that the proxy server should continue running.
RESET Specifies that the proxy server should clean up its internal state information and await further requests. If the proxy server is a standalone server, this option also specifies that the proxy server should reconnect to the X server.
TERMINATE Specifies that the proxy server should exit.

The default is /ONEXIT=NOACTION.

/OPTIONS=(option-list)

Specifies the optimizations to use for this proxy server. With the exception of ALL and NONE, each option has a NOoption form that disables the option. To enable a small number of options, use a combination of the NONE and the desired options. For example, /OPTIONS=(NONE,IMAGE) suppresses all optimization with the exception of image compression. To disable a small number of options, use a combination of the ALL and the undesired options. For example, /OPTIONS=(ALL,NOIMAGE,NOGRAPHICS) suppresses image and graphics optimization.
ALL Enables all optimizations. The ALL and NONE options are mutually exclusive.
NONE Disables all optimizations. The ALL and NONE options are mutually exclusive.
[NO]ATOMS Enables [disables] reading of the atoms control file. The NOATOMS option is mutually exclusive with the /ATOMS qualifier.
[NO]GRABCMAP Enables [disables] color map grabbing.
[NO]COMP Enables [disables] stream compression.
[NO]DELTA Enables [disables] delta request substitutions.
[NO]GRAPHICS Enables [disables] reencoding of graphics requests (other than image-related requests).
[NO]IMAGE Enables [disables] image compression.
[NO]INTERNSC Enables [disables] short circuiting of InternAtom requests.
[NO]LBX Enables [disables] all LBX optimizations (equivalent to [NO]ATOMS, [NO]GRABCMAP, [NO]GRAPHICS, [NO]IMAGE, [NO]INTERNSC, and [NO]WINATTR). The [NO]LBX option is mutually exclusive with any of the options controlled by [NO]LBX. The NOLBX option is mutually exclusive with the /ATOMS qualifier.
[NO]RGB Enables [disables] color name to RGB mapping in the server. The NORGB option is mutually exclusive with the /RGB qualifier.
[NO]SQUISH Enables [disables] squishing of X events.
[NO]TAGS Enables [disables] use of tags.
[NO]WINATTR Enables [disables] GetWindowAttributes/GetGeometry grouping into one round trip.
[NO]ZEROPAD Enables [disables] zeroing out unused pad bytes in X requests, replies, and events.

The default is /OPTIONS=ALL.

/PARTIAL
/NOPARTIAL

Specifies that this proxy server is allowed to initialize even when it cannot open all transport sockets specified by the /TRANSPORT qualifier. These transport sockets are used to receive client requests. Note that if the proxy server detects that one of the sockets is in use by another task, the server fails to initialize with the server number in use, and the next server number is tried (as discussed in the description of the /SERVER qualifier).

The default is /NOPARTIAL.

/RGB=file-specification

Specifies the file describing the color name to RGB resolution in this proxy server. This qualifier cannot be specified if the NORGB option is specified for the /OPTION qualifier.

The default is /RGB=SYS$MANAGER:DECW$RGB.DAT.

/SERVER=server-number

Specifies the server number to assign to this proxy server. Specify an integer from 0 to 63.

The proxy server first attempts to initialize using the specified server number. If an active server is already using the specified number, the proxy server tries the next lower number. This process is repeated until an unused server number is found or until the proxy server tries the number 0 and fails. If the number 0 fails and the number specified was not 63, the server number wraps and attempts are tried starting with the number 63. The process continues until all numbers have been tried. If all numbers are in use, the proxy server fails to initialize and terminates.

For managed proxy servers, the search for a free server number always starts at 63; any number specified by this qualifier is ignored.

A standalone server started as a subprocess always prints out the server number used on SYS$ERROR. For standalone proxy servers that are detached processes, use the /FIXED_SERVER qualifier to force the server to use the specified server number or fail. Otherwise, there is no method to determine the server number actually used by the server.

The default is /SERVER=63.

/TAGCACHE=cache-size

Specifies the size of this proxy server's tag cache (in bytes). Specify the value 0 to disable tag caching.

The default is /TAGCACHE=1048576 (2^20).

/TRANSPORTS="transport-string"

Specifies the transports that this proxy server monitors for incoming client requests. If the /PARTIAL qualifier is not used, all transports specified by this qualifier must initialize successfully or the proxy server fails to initialize with the server number in use and the next server number is tried, as discussed in the description of the /SERVER qualifier.

The default is /TRANSPORTS="LOCAL,DECNET,TCPIP".

/ZLEVEL=compression-level

Specifies the Zlib compression level used for stream compression. Specify an integer from 1 (least compression) to 9 (most compression).

The default is /ZLEVEL=6.

3.6.1.1.3 Stopping LBX Proxy Servers

You can stop LBX proxy servers either automatically or manually.

Stopping Servers 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.

Note

If not already terminated, all managed proxy servers automatically terminate when their proxy manager is terminated.

Stopping Servers Manually

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

3.6.1.2 Proxy Manager

The proxy manager handles connection requests between client applications, the proxy server, and X server in managed configurations. The following sections describe how to configure and start the proxy manager.

3.6.1.2.1 The Proxy Manager Configuration File

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

3.6.1.2.2 Starting the Proxy Manager

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

Starting at DECwindows Motif Startup

To start the proxy manager at DECwindows Motif startup, either edit the existing SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file or copy the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE file to SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM and edit the newly created file. For more information, see the section in the Managing DECwindows Motif for OpenVMS Systems manual that describes how to customize the Session Manager environment.

The DECW$PRIVATE_APPS_SETUP.TEMPLATE file contains global symbols that are used to control the behavior of a DECwindows session and its applications. Table 3-4 describes the symbols present in this file that control the proxy manager.

Table 3-4 Global Symbols Controlling the Proxy Manager
Symbol Description
DECW$PROXY_MANAGER_CONFIG Specifies the name of the proxy manager's configuration file. The definition of this symbol causes the DECwindows startup process to start the proxy manager. The file name specified by this symbol overrides any configuration file specified in the DECW$PROXY_MANAGER_OPTIONS symbol. A default configuration file, SYS$MANAGER:DECW$LBXPROXY.DECW$PMCFG, is provided at installation time. This file has a single service entry for the LBX service.
DECW$PROXY_MANAGER_LOG Specifies the name of the file that the proxy manager should use to log events. If the proxy manager starts and this symbol is undefined, the default log file is SYS$MANAGER:DECW$PROXYMANAGER.LOG.
DECW$PROXY_MANAGER_OPTIONS Specifies any qualifiers that should be included on the XPROXYMANAGER command when the proxy manager is started. Note that the configuration file specified by the DECW$PROXY_MANAGER_CONFIG symbol always has precedence over any value specified by this symbol.
DECW$PROXY_MANAGER_QUOTAS Specifies any qualifiers to include on the RUN command line used to start the proxy manager.

Notes

If you restart DECwindows Motif while a proxy manager process is running, the proxy manager does not restart automatically. To ensure that the proxy manager restarts (with any associated options) during DECwindows startup, stop the proxy manager process prior to restarting DECwindows, as described in Section 3.6.1.2.4.

Also note that when restarting the proxy manager as part of DECwindows startup, the owner of the proxy manager process is the user who issues the DECwindows Motif startup command. If DECwindows is started as part of system startup, the owner is the SYSTEM account. If DECwindows is started from another account, verify that the owner of that account has been granted access to the X display server.

Starting Manually

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_FILE=SYS$MANAGER:DECW$LBXPROXY.DECW$PMCFG -
_$ /LOG=SYS$MANAGER:DECW$PM.LOG

3.6.1.2.3 Qualifiers

Enter XPROXYMANAGER command qualifiers in the same manner as you would for any other DCL command. For proxy managers started at DECwindows startup, you can specify these qualifiers in the definition of the DECW$PROXY_MANAGER_OPTIONS symbol.

/CONFIGURATION_FILE=file-specification

Specifies the configuration file that the proxy manager should use to define the available proxy services.

The default is SYS$LOGIN:DECW$XPROXYMANAGER.DECW$PMCFG.

/LOG=file-specification
/NOLOG

Specifies the log file that the proxy manager should use to log errors. The proxy manager uses this file to record each request for a proxy server. The default is /NOLOG. If the /VERBOSE qualifier is specified, the default is /LOG. If /LOG is specified without a value, the output is sent to SYS$ERROR by default.

If an incomplete specification is entered, the following directory specification is used to complete the command:


SYS$SYSDEVICE:[]DECW$XPROXYMANAGER.LOG 

/PORT=integer

Specifies the port number that this server monitors for incoming requests. For the TCP/IP transport, this qualifier specifies an IP port number from the port number space shared by all users of TCP/IP. For the DECnet and Local transports, this qualifier specifies a number that is used to create a unique resource name from the name space of all users of the Inter-Client Exchange (ICE) protocol. Specify a value from 1 to 16383.

The default port number is 6500.

/TRANSPORT="transport-string"

Specifies the transports which this proxy manager monitors for incoming client requests.

The default is /TRANSPORT="LOCAL,DECNET,TCPIP".

/VERBOSE
/NOVERBOSE

Specifies whether the proxy manager should log each proxy request to the proxy manager log file, in addition to error messages.

If the /LOG qualifier is specified, the default is /VERBOSE. If the /LOG qualifier is not specified, the default is /NOVERBOSE.

3.6.1.2.4 Stopping a Proxy Manager

To stop a proxy manager, you must use the DCL STOP command. The STOP/EXIT=USER_MODE option (new to OpenVMS Alpha Version 7.3-1) is recommended.

Stopping the proxy manager also stops all managed proxy servers controlled by the proxy manager.

3.6.1.3 Authentication in an LBX 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 OpenVMS DCL Dictionary: N--Z.

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

Note

Clients connecting to an X server through an LBX proxy server must have a valid entry for the proxy server in the client X authority file. If the associated entry contains a generated, untrusted cookie, access to the X server is only granted for the initial proxy server connection. Subsequent client connections cannot use the same cookie to gain access to the X server.


Previous Next Contents Index