HP OpenVMS Systems Documentation

Content starts here HP DECwindows Motif for OpenVMS Alpha

HP DECwindows Motif
for OpenVMS Alpha

New Features

Order Number: AA--RT2CB--TE

October 2003

This manual describes new features and enhancements that pertain to the HP DECwindows Motif for OpenVMS Alpha Version 1.3--1 software.

Revision/Update Information: This manual supersedes the HP DECwindows Motif for HP OpenVMS Alpha New Features for Version 1.3.

Operating System: HP OpenVMS Alpha Version 7.3--2

Software Version: HP DECwindows Motif for OpenVMS Alpha Version 1.3--1

Hewlett-Packard Company
Palo Alto, California

© Copyright 2003 Hewlett-Packard Development Company, L.P.

Motif, OSF/1, UNIX, and the "X" device are registered trademarks and The Open Group is a trademark of The Open Group in the U.S. and other countries.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.


The HP DECwindows Motif for OpenVMS Alpha Version 1.3--1 documentation set is available on CD-ROM.

This document was prepared using VAX DOCUMENT, Version V3.2n.

Contents Index


This document describes the new features introduced with the HP DECwindows Motif for OpenVMS Alpha Version 1.3--1 (DECwindows Motif) software. For information about how these features might affect your system, read the release notes before you install, upgrade, or use the DECwindows Motif Version 1.3--1 software.

The features in this manual are cumulative from DECwindows Motif for OpenVMS Version 1.0 and indicate any undocumented items that still pertain to the software. For previous features, a label within the description indicates when the feature was introduced.

Intended Audience

This manual is intended for system managers, users, and programmers who work with the DECwindows Motif software.

Document Structure

This manual is structured as follows:

  • Chapter 1 provides an overview of the current release.
  • Chapter 2 describes features of interest to general users of the DECwindows Motif software.
  • Chapter 3 describes features related to system and network management.
  • Chapter 4 describes features that support application and system programmers.

Related Documents

For additional information about OpenVMS or DECwindows Motif products and services, visit the following web site:


Reader's Comments

HP welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet openvmsdoc@hp.com
Mail Hewlett-Packard Company
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How To Order Additional Documentation

For information about how to order additional documentation, visit the following World Wide Web address:



In this manual, references to OpenVMS are synonymous with the HP OpenVMS Alpha Operating System.

Unless otherwise specified, references to OpenVMS Clusters, VMSclusters, or clusters in this document are synonymous with HP OpenVMS Clusters.

All uses of DECwindows and DECwindows Motif refer to the HP DECwindows Motif for OpenVMS Alpha software; and all uses of X server and X display server refer to the DECwindows X11 Display Server. Additionally, all uses of DECwindows XUI (X User Interface) refer to the DECwindows product prior to DECwindows Motif Version 1.0.

The following conventions are also used in this manual:

Ctrl/ x A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
[Return] In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)

In the HTML version of this document, this convention appears as brackets, rather than a box.

... Horizontal ellipsis points in examples indicate one of the following possibilities:
  • Additional optional arguments in a statement have been omitted.
  • The preceding item or items can be repeated one or more times.
  • Additional parameters, values, or other information can be entered.
Vertical ellipsis points indicate the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( ) In command format descriptions, parentheses indicate that you must enclose the choices in parentheses if you choose more than one.
[ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.)
[|] In command format descriptions, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options.
{ } In command format descriptions, braces indicate required elements; you must choose one of the options listed.
text style This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason.

In the HTML version of this document, this convention appears as italic text.

italic text Italic text emphasizes important information and indicates complete titles of manuals and variables. Variables include information that varies in system messages (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).
UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace type

Monospace type indicates code examples and interactive screen displays.

In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.

- A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.

Chapter 1

This chapter summarizes the features associated with the HP DECwindows Motif for OpenVMS Alpha Version 1.3--1 software. DECwindows Motif Version 1.3--1 is a minor release that includes restoration of the LAT transport interface and support for displaying customized welcome messages prior to logging into the New Desktop.

Table 1-1 lists all the items added during this release and cross-references the sections in which they are described.

For a detailed description of the corrections, changes, and known problems associated with this release, see the HP DECwindows Motif for OpenVMS Alpha Release Notes manual.

Table 1-1 Directory of Features for DECwindows Motif Version 1.3--1
Title Section
Desktop Management Features  
Displaying Custom Messages Prior to Login Section 3.4.1
X Display Server Management Features  
New Server Parameter for Setting Process Priority Section 3.7.1
Transport Programming Features  
Support for the LAT Transport Interface Restored Section 4.2.1

Chapter 2
General User Features

This chapter provides information about new features that pertain to all users of DECwindows Motif.

2.1 OpenVMS Display Device and Layered Product Interfaces

This section contains release notes that pertain to the OpenVMS display device (SET DISPLAY) and DECwindows Motif layered product interfaces.

2.1.1 Enhanced DECwindows Motif Display Device Capabilities


To support the new X display server access control and proxy features available as part of the X11R6.6 upgrade, many SET DISPLAY and SHOW DISPLAY command qualifiers have been either added or modified for use on systems running OpenVMS Alpha Version 7.3--1 or higher.

Table 2-1 lists these new and changed qualifiers that provide the following added functionality for DECwindows Motif display devices:

  • Ability to define and view a set of named properties associated with a particular display device and assign their values. Named properties are intended to store such information as the network address or transport for the display device. Once defined, you can use these properties as the basis for subsequent DCL global symbol definitions.
  • Access to a subset of commands from the X Authority utility (xauth). This utility enables you to manage the contents of one or more X authority files, which are used by the MIT-KERBEROS-5 and MIT-MAGIC-COOKIE-1 protocols to control access to an X server. Use the new qualifiers to create and use an alternate X authority file, manually generate or revoke authorization keys, or extract entries from the X authority file.
  • Access to the proxy manager and Low-Bandwidth X (LBX) proxy server. The proxy manager and LBX proxy server assist in managing connections over low-bandwidth networks, such as the Internet. Use the new qualifiers to specify a standalone proxy server or to specify a proxy manager (and the manager's port and transport information). You can also enable authentication on proxy server connections and specify data values, such as a magic cookie, to be passed to the authentication protocol.

Table 2-1 New and Changed DCL SET DISPLAY and SHOW DISPLAY Command Qualifiers
Command Qualifier Description
SET DISPLAY /GENERATE Connects to the X server and generates a new authorization key.
Specifies the authentication protocol used to grant the proxy server access to the X server.
  /LBXDATA Specifies a data value to be processed by the authentication protocol.
  /PMPORT Indicates the port number for the proxy manager.
  /PMTRANSPORT Specifies the network transport used by a display device to connect to the proxy manager.
  /PROXY Specifies that a proxy manager be used to assign an LBX proxy server to act as an intermediary between the client and the X server specified in the command.
  /QUOTA Modifies the value of the name count or data space quota for the display device.
  /REVOKE Revokes the authorization key for the display device produced by the /GENERATE qualifier.
  /SERVER Specifies the server number. This qualifier takes on the additional meaning of specifying a standalone LBX proxy server.
  /TRANSPORT Specifies the network transport used to connect to the X server. When using the proxy manager, selects transport used between the selected proxy server and the X server. When using a standalone proxy server, selects the transport between the client and the proxy server. This qualifier also provides a default value for the /PMTRANSPORT qualifier.
  /VALUE Sets, deletes, or modifies a named property value.
Specifies the location for an alternate X authority file. The /NOXAUTHORITY qualifier clears this setting.
SHOW DISPLAY /ALL Displays all named properties associated with the display device and their current values.
  /EXTRACT Obtains the authorization data from the current X authority file and writes it to SYS$OUTPUT.
  /QUOTA Displays the name count and data space quota values associated with the display device.
  /SYMBOLS Defines a DCL symbol for each named property.
  /VALUES Displays the set of values associated with the specified named properties.

For detailed information on these new qualifiers, see the online help for each command, or refer to the OpenVMS DCL Dictionary: N--Z.

2.1.2 Additional Display Device Logicals for Default Transport and Name Count Values


Use the following logicals to override the normal defaults when creating display devices:

  • DECW$SETDISPLAY_DEFAULT_TRANSPORT -- Specifies the default transport to use when creating a display device without the /TRANSPORT qualifier.
  • DECW$WS_DEFAULT_NAME_COUNT -- Specifies the default name count quota for a new display device. This logical must be defined in executive mode and in the system logical name table.
  • DECW$WS_DEFAULT_DATA_SPACE -- Specifies the default data space quota for a new display device. This logical must be defined in executive mode and in the system logical name table.

2.2 General DECwindows Motif Environment

This section describes new features that are common to both the New Desktop and Traditional DECwindows Desktop environments.

2.2.1 Extended File Specification (EFS) Support


In general, DECwindows Motif supports the Extended File Specifications (EFS) option provided in OpenVMS Alpha. The interface either supports the new ODS-5 file names or provides an error message indicating that the particular component does not support the new names. File Selection Popup Window

The standard file selection popup window used by most DECwindows Motif applications fully supports ODS-5 style file names. The window supports deep directories, case preservation, and extended-length file names. The window supports entry of file names using the extended file name character and displays files using the extended file name character set using the circumflex character (^). See the current OpenVMS documentation for more specific information about using deep directories and the extended file name character set. New Desktop and the FileView Application

With an ODS-5 volume, the FileView application supports deep directories, case preservation, and extended-length file names. FileView supports entry of file names using the extended file name character and displays files using the extended file name character set using the circumflex character (^). See the current OpenVMS documentation for more specific information about using deep directories and the extended file name character set.

Any custom FileView command extensions must be modified to support EFS. Traditional Desktop and the File Manager Application

The File Manager application supports case preservation and creates files with the extended file name character set, but does not support any operations on its files.

The File Manager application supports deep directories and extended-length file names with the following restriction. ODS-5 volumes allow file names up to 236 8-bit characters in length and deep directory structures if the total file specification does not exceed 512 8-bit characters in length. The current version of the File Manager supports extended-length file names and deep directory structures with the additional restriction that a total file specification cannot exceed 235 8-bit characters in length. Exceeding this limit causes an error message for some menu items. The Programming Libraries

The programming libraries fully support deep directories and extended-length file names. However, the libraries do not support case preservation or the extended file name character set. Translated Image Support (TIS) Library

The translated image support (TIS) library has not been updated to support EFS.

2.2.2 Color Customizer Example Program


The color customizer example program allows you to dynamically control the colors of your workstation environment. Window, icon, and window manager colors can be changed individually or as part of a palette switch. You can control mapping between resources and color cells, as well as the size and contents of the palette set. Also, automatic shadowing with the standard Motif shadowing algorithms is supported. Supported Displays

The color customizer supports any display using pseudocolor or grayscale visuals. This includes most 4- and 8-plane workstation displays. Supported Applications

The color customizer can affect the colors of any applications that use the current release of the DECwindows X Toolkit Library. Applications from other vendors and previous versions of the X Toolkit Library are unaffected.


If the color customizer is used to control the colors of applications that have their own color customization dialog boxes (like the Session Manager, Window Manager, and DECwindows Mail), those application-specific color customization dialog boxes may not reflect the correct current color values while the customizer is running the application. This is normal; use the customizer instead of the application-specific dialog box to change these color values. Building the Color Customizer on OpenVMS Systems

To build the color customizer on OpenVMS systems, perform the following steps:

  1. Copy the files to a private directory. For example:

  2. Build the customizer using the following command:


This command procedure creates the following output files:


Next Contents Index