[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

HP DECwindows Motif for OpenVMS

New Features

Order Number: AA--RT2CC--TE

January 2005

This manual describes new features and enhancements that pertain to the DECwindows Motif Version 1.5 software.

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

Operating Systems: OpenVMS I64 Version 8.2

OpenVMS Alpha Version 8.2

Software Versions: DECwindows Motif for OpenVMS I64 Version 1.5

DECwindows Motif for OpenVMS Alpha Version 1.5

Hewlett-Packard Company
Palo Alto, California

Confidential 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 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.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Java is a US trademark of Sun Microsystems, Inc.

UNIX is a registered trademark of The Open Group.

The X device is a trademark of X/Open Company Ltd. in the UK and other countries.

Printed in the US

ZK6663

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

Contents

Index

Preface

This document describes the new features introduced with the HP DECwindows Motif for OpenVMS Version 1.5 (DECwindows Motif) software on the OpenVMS I64 and OpenVMS Alpha platforms. 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.5 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 DECwindows Motif.

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.

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:

http://www.hp.com/go/openvms/doc/order

Conventions

The following product names may appear in this manual:

HP OpenVMS Industry Standard 64 for Integrity servers
OpenVMS I64
I64

All three names---the longer form and the two abbreviated forms---refer to the version of the OpenVMS operating system that runs on the Intel Itanium architecture.

All uses of DECwindows and DECwindows Motif refer to the HP DECwindows Motif for OpenVMS 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 typographic conventions may be 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
Introduction

This chapter summarizes the features associated with the DECwindows Motif Version 1.5 software. Version 1.5 is a major release that includes support for the HP OpenVMS Industry Standard 64 for Integrity Servers (OpenVMS I64) platform, the Internet Protocol Version 6 (IPv6) transport, and ACME security (Alpha only).

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 Release Notes manual.

**Table 1-1 Directory of Features for DECwindows Motif Version 1.5**
Title	Section
General User Features
Support for Internet Protocol Version 6 (IPv6) Transport	Section 2.1.1
Tool and Utility Features
xauth: IPv6 Considerations	Section 2.5.2.3
Installation and Upgrade Features
DECW$STARTUP Log File	Section 3.1.1
Security and Authorization Features
Support for ACME Subsystem (Alpha Only)	Section 3.2.1
X Display Server Management Features
New Parameter for Enabling IPv6 Support in the Font Server	Section 3.3.1
X Window System Library (Xlib) Features
IPv6 Considerations	Section 4.6.1
X Window System Extension and Protocol Features
ICE: IPv6 Considerations	Section 4.7.3.3

Chapter 2
General User Features

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

2.1 General DECwindows Motif Environment

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

2.1.1 Support for Internet Protocol Version 6 (IPv6) Transport

V1.5

DECwindows Motif now supports the Internet Protocol Version 6 (IPv6) transport in addition to the existing support for the Internet Protocol Version 4 (IPv4) transport. Included in this release is support for the transport names described in the X11R6.6 and X11R6.7 specifications published by the X.Org Foundation (formerly X.Org).

Use of the IPv6 transport is enabled with the new global symbol DECW$IPV6_SUPPORT, which can be defined in the startup file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM.

Support for the IPv6 transport affects many DECwindows Motif components--from the display device to functions in the Inter-Client Exchange (ICE) library. See one or more of the following manuals (or sections in this manual) to learn about IPv6 support and its use.

For information about...	See the...
X Window System support for transport names	X.Org Foundation web site (http://www.x.org)
Enabling IPv6 support, valid display name formats, host name translation, and using with font and proxy servers	HP DECwindows Motif for OpenVMS Management Guide
Impact on the SET DISPLAY command	HP OpenVMS DCL Dictionary and DCL online help
Impact on the xauth utility	Section 2.5.2.3
Impact on X Library (Xlib) routines	Section 4.6.1
Impact on ICE library routines	Section 4.7.3.3

2.1.2 Extended File Specification (EFS) Support

V1.2--5

In general, DECwindows Motif supports the Extended File Specifications (EFS) option available with OpenVMS. The interface either supports the new ODS-5 file names, as described in the following sections, or provides an error message indicating that the particular component does not support the new names.

2.1.2.1 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.

2.1.2.2 New Desktop and the File Manager Application

With an ODS-5 volume, the File Manager application supports deep directories, case preservation, and extended-length file names. File Manager 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 (^).

Any custom File Manager command extensions must be modified to support EFS.

See the current OpenVMS documentation for more specific information about using deep directories and the extended file name character set.

2.1.2.3 Traditional Desktop and the FileView Application

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

FileView also 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.

2.1.2.4 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.

2.1.2.5 Translated Image Support (TIS) Library

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

2.1.3 Color Customizer Example Program

V1.2

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.

2.1.3.1 Supported Displays

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

2.1.3.2 Supported Applications

The color customizer can affect the colors of any applications that use the current release of the X Toolkit Intrinsics (Xt) included with X Window System Version 11 Release 5 (X11R5) or greater. Applications from other vendors and versions of the library previous to X11R5 are unaffected.

Note

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.

2.1.3.3 Building the Color Customizer on OpenVMS Systems

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

Copy the files to a private directory. For example:

$ SET DEFAULT SYS$LOGIN
$ CREATE/DIRECTORY [.CUSTOMIZER]
$ SET DEFAULT [.CUSTOMIZER]
$ COPY DECW$EXAMPLES:CUSTOM.C []
$ COPY DECW$EXAMPLES:CUSTOM.UIL []
$ COPY DECW$EXAMPLES:CUSTOMIMAGE.DAT []
$ COPY DECW$EXAMPLES:XSETROOT_CUST.C []
$ COPY DECW$EXAMPLES:BUILD_CUSTOMIZER.COM []

Build the customizer using the following command:
$ @BUILD_CUSTOMIZER.COM

This command procedure creates the following output files:

CUSTOM.UID
CUSTOM.EXE
XSETROOT_CUST.EXE

2.1.3.4 Running the Color Customizer

To run the color customizer, perform the following steps:

Copy the files CUSTOM.UID and CUSTOM.EXE, which were created during the customizer build, to the directory where the customizer will be run. A typical location is the directory SYS$LOGIN or the directory DECW$USER_DEFAULTS.
Copy the files CUSTOM.DAT and DXMDEFAULTS.DAT from the directory DECW$EXAMPLES to the directory DECW$USER_DEFAULTS.
Run the executable file CUSTOM.EXE as follows:
$ RUN CUSTOM

Note

Only the colors of applications invoked after the customizer starts will be affected. For this reason, start the customizer as the first X application during the login process.

2.1.3.5 Modifying the DECW$LOGIN.COM File

As noted in Section 2.1.3.4, the color customizer should be the first X application started during the login process. Do this by starting it as a subprocess from within the DECW$LOGIN.COM file. Add a command to wait approximately 10 seconds between customizer startup and the startup of other applications.

For example, add the following lines to the DECW$LOGIN.COM file:

$! Starting the color customizer
$ DISPLAY = F$LOGICAL("DECW$DISPLAY")
$ SPAWN/NOWAIT/OUTPUT='DISPLAY' RUN SYS$LOGIN:CUSTOM.EXE
$ WAIT 0:0:10

See Using DECwindows Motif for OpenVMS and HP DECwindows Motif for OpenVMS Management Guide for more information on modifying DECW$LOGIN.COM.

2.1.3.6 Command Interface Summary

A box containing a list of available palettes is in the leftmost section of the Color Customizer window. Click on the desired palette to see the colors take affect.

Below the palettes are two arrays of colored buttons, representing the dynamically allocated color cells for normal and shadow colors. To find out what resources are affected by a color cell, click and hold the arrow button next to the color cell.

Hint

As a shortcut, you can click on the screen facsimile in the rightmost corner of the dialog box. If the portion you click on is colored by one of the resource values controlled by the customizer, the pop-up window for the appropriate color button is displayed.

To modify a single color cell, click on the corresponding color button. A colormix widget pops up; as you modify the color, these modifications are reflected in your workstation environment. Use the colormix widget reset button to return to the starting color at any time. You can also change the color cell you are modifying by clicking on a different color button while the colormix widget is displayed.

The automatic shadowing option causes shadow and select colors to be automatically updated when their corresponding background colors are changed. The standard Motif shadowing algorithms are used for these calculations.

Use the File menu to modify, add, and delete color palettes as follows:

To modify an existing palette, select the palette, change the colors, and choose Save Palette from the File menu.
To add a new palette, select an existing palette, modify the colors as necessary, and choose Save Palette As... from the File menu. A message box prompts you for the name of the new palette.
To delete a palette, select the palette and choose Delete Palette from the File menu.

Changes made through the File menu automatically update the CUSTOM.DAT file, which contains the resource defaults.

The File menu Exit button causes the customizer application to exit. A warning dialog is displayed first. Note that the color cells allocated by the customizer (and used by the currently running applications) will be deallocated. After the customizer exits, if the colors of the currently running applications are not correct, the applications should be restarted to restore normal colors. Usually, there is no need to exit the color customizer; it is typically kept running at all times, like the Session Manager.