HP OpenVMS Systems Documentation

Content starts here HP DECwindows Motif for OpenVMS Alpha

HP DECwindows Motif
for OpenVMS Alpha

Release Notes

October 2003

This manual describes corrections, known problems, and restrictions 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 Release Notes 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


These release notes describe corrections, known problems, and restrictions that pertain to the HP DECwindows Motif for OpenVMS Alpha Version 1.3--1 (DECwindows Motif) software.

The notes in this manual are cumulative from DECwindows Motif for OpenVMS Version 1.0 and indicate any undocumented items that still pertain to the software. A label within each note specifies when the correction or problem was introduced.

Intended Audience

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

Document Structure

This manual is structured as follows:

  • Chapter 1 provides an overview of the current release.
  • Chapter 2 contains general user release notes for all users.
  • Chapter 3 contains release notes intended for system managers.
  • Chapter 4 contains release notes intended for application and system programmers.
  • Chapter 5 contains corrections to the DECwindows Motif documentation set.
  • Appendix A contains a subset of the release notes for OSF/Motif Release 1.2.
  • Appendix B contains release notes for the DECwindows OSF/Motif Toolkit.

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
Postal 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 the 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 corrections, restrictions, and known problems associated with the HP DECwindows Motif for OpenVMS Alpha Version 1.3--1 software. Table 1-1 lists all the notes added during this release and cross-references the sections in which they are described.

For a detailed description of the features and enhancements introduced with this release, see the HP DECwindows Motif for OpenVMS Alpha New Features manual.

Table 1-1 Directory of Notes for DECwindows Motif Version 1.3--1
Title Section
OpenVMS Display Device and Layered Product Interface Notes  
BadAuthorizationProtocol Error Displayed When Generating Authorization Keys with Kerberos Enabled Section
New Desktop Notes  
Style Manager Now Sets Background on Correct Workspace in Multihead Configurations Section 2.3.1
Screen Saver No Longer Fills Session Manager Log File (DECW$SM.LOG) with Error Messages Section 2.3.2
Security Options Dialog Box Allows Selection of All Valid Option Combinations Section 2.3.3
Screen Saver and Screen Lock Set by Default Section 2.3.6
Traditional DECwindows Desktop Notes  
FileView Supports Variable Case Filenames Section 2.4.1
Tool and Utility Notes  
Change in Location of AccessX Configuration File Section
Use ignoreVisibility Resource When Displaying DECterm Windows with eXcursion or on a Multihead XINERAMA System Section
Installation and Upgrade Notes  
DECwindows Motif Version Support and Compatibility Section 3.1.1
Restarting DECwindows Motif from the Operator Console (OPA0:) Section 3.1.4
System Tuning and Performance  
Support for SYSMAN STARTUP OPTION Settings Section 3.2.1
Security and Authorization Notes  
Kerberos No Longer Requires SECURITY Extension Section 3.3.1
Proxy Server Management Notes  
Proxy Servers Do Not Support Use of XC-QUERY-SECURITY-1 Protocol Section 3.6.1
X Display Server Management Notes  
Using XINERAMA on New Desktop Systems Section 3.7.1
General Programming Notes  
OSF/Motif Toolkit Support and Compatibility Section 4.1.1
Increasing the Limit of Top-Level Widgets Allowed by the UIL Compiler Section 4.1.3
UIL Compilation Problems with Looped Object References Section 4.1.9
X Window System Library (Xlib) Notes  
External Declarations for Functions Returning Null Value Added to DECW$XLIBDEF.FOR Section 4.3.1
Changed Record Format for Connection Failure Error Message Section 4.3.2
X Window System Extension and Protocol Notes  
Using XCopyArea with XINERAMA Section 4.5.1
XINERAMA Does Not Correctly Report VisibilityNotify Section 4.5.2
CreateWindow Functions Correctly on Multihead Configurations Using XINERAMA Section 4.5.3

Chapter 2
General User Release Notes

This chapter contains information about DECwindows Motif for general users.

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 OpenVMS Display Device (SET DISPLAY)

This section contains notes pertaining to OpenVMS display devices created and managed using the SET DISPLAY and SHOW DISPLAY commands. For more information on these commands, see the OpenVMS DCL Dictionary: N--Z or online help. BadAuthorizationProtocol Error Displayed When Generating Authorization Keys with Kerberos Enabled


The SECURITY extension to the X display server does not support on-demand generation of authorization keys for the Kerberos authentication protocol. Non-support of key generation is consistent with the standard implementation of the server extension, as published by X.Org.

Consequently, the following DCL commands produce a BadAuthorizationProtocol error or unwanted results when used to generate an authorization key on an X server that has Kerberos enabled:


This is expected behavior; do not use these commands to generate authorization keys for X servers that use the Kerberos protocol. See the HP DECwindows Motif for OpenVMS Alpha New Features manual to learn when and how to manually create X authority file entries for Kerberos-enabled servers. SET DISPLAY/REVOKE Error Message is Misleading


The error message for revoking a cookie that has timed out is misleading. The error message indicates there is a %SYSTEM-F-BADPARAM, bad parameter value. This does not indicate the nature of the error. I/O Error Displayed When Using SET DISPLAY/REVOKE


Using the SET DISPLAY/REVOKE command to revoke a generated, trusted, cookie can sometimes result in an I/O error similar to the following:

XIO:  fatal IO error 65535 (connection aborted) on X server ":0.0"
      after 10 requests (8 known processed) with 0 events remaining.

This error results from the cookie being used by the SET DISPLAY/REVOKE command to connect to the server. Revoking the cookie breaks the connection to the display server.

Although the error appears fatal, the revoke operation actually completes successfully. Display Devices Not Deleted Upon Exit


When creating user-mode display devices with the DCL SET DISPLAY command, note that any unused devices may not be deleted when you log out of DECwindows Motif. Display devices created with SET DISPLAY are seen as permanent devices until used by an X client application and are not destroyed upon exit.

To avoid this problem, create supervisor-mode display devices.

2.1.2 DECTPU

This section contains release notes related to the DECwindows Motif interface to DECTPU. Small Display Monitors and DECTPU


When running DECTPU for DECwindows Motif on small display monitors, the main window can be less than fully visible.

To correct this condition, follow these steps:

  1. Add the following resources to the DECTPU section of your X resource file:

    Tpu.Tpu$MainWindow.X:                             0
    Tpu.Tpu$MainWindow.Y:                             0
    Tpu.Tpu$MainWindow.Rows:                          21
    Tpu*condensedFont:                                on
    Tpu*fontSetSelection:                             1
  2. Copy the resource file from SYS$LIBRARY:EVE.DAT and add the previous lines.
  3. Use the logical name TPU$DEFAULTS to point at the new resource file.
    The following example invokes the EVE DECwindows Motif user interface using the X resource file names eve_small_window.dat in your login directory to edit the file LOGIN.COM.


2.2 General DECwindows Motif Environment

This section contains release notes that pertain to the general DECwindows Motif user environment. This includes corrections, restrictions, and known problems that are common to both the New Desktop and the Traditional DECwindows Desktop environments.

2.2.1 Web Browser Support


The HP Secure Web Browser (SWB) is the officially supported web browser for HP OpenVMS Alpha and is a licensed part of the operating system. SWB is based on the Mozilla Web Browser, which is designed for standards compliance, performance, and portability.

SWB is available from the following OpenVMS web page:


This page contains installation and running instructions, as well as information about hardware and software prerequisites, system parameters, account quotas, and problem reporting.

2.2.2 Request-Intensive Applications May Pause Before Closing


There may be a slight delay when a request-intensive application running over a LOCAL network connection is forced to close via the Window Manager. For example, an attempt to close the DECW$EXAMPLES:ICO application from a LOCAL display results in a slight pause before the application window closes.

This is a result of resource contention between the Window Manager (DTWM) and server processes. To prevent this problem from occurring, decrease the priority of the server process using the DECW$SERVER_PRIORITY parameter, as described in HP DECwindows Motif for OpenVMS Alpha New Features.

2.2.3 Support Discontinued for Display PostScript


Starting August 1, 1998, support was discontinued for Adobe Display PostScript software resulting from Adobe Systems Incorporated discontinuing its former ongoing support for Display PostScript.

This action has had a varying degree of impact on the behavior of those DECwindows Motif applications that used the Adobe Display PostScript software. For example, starting with DECwindows Motif for OpenVMS Version 1.2--6, Bookreader can no longer display graphics in PostScript format.

For information about the effects of this action on specific DECwindows applications, see the following release notes:

To learn about the possible impact to user-written and third-party applications designed for the DECwindows Motif environment, see Section 4.1.6.

2.2.4 Limited Support for Tear-Off Menus


The following applications do not support tear-off menus:

  • CDA Viewer
  • Notepad
  • Print Screen

2.2.5 Implications of the Message, "System Menu Bar: Pseudo Mouse Not Available"


"System Menu Bar: Pseudo Mouse not available" is an informational message that is included in the user's SYS$LOGIN:DECW$SM.LOG file when you run a session. It is not an error message. The message occurs when the OpenVMS Session Manager is run remotely to a non-OpenVMS server. The OpenVMS server provides pseudomouse mode, a mode that allows you to use arrow keys to move the mouse cursor.

2.2.6 Printing from Applications Linked Against OSF/Motif Release 1.1.3


Applications that are linked against OSF/Motif Release 1.1.3 may end abruptly when you attempt to print on systems that do not have print queues. Any layered products that linked against the OSF/Motif Release 1.1.3 libraries and use the standard DECwindows print dialog ("print widget") are also affected.

As a possible solution, either avoid displaying the DECwindows print dialog, or define a print queue on your system. The print queue does not have to be connected to a printer to accept print jobs. Assign a name to the print queue that indicates the print queue is not connected to a printer, for example, NULL_PRINTER.

Next Contents Index