|
HP OpenVMS Systems Documentation |
|
HP DECwindows Motif for OpenVMS
|
| Previous | Contents | Index |
This section contains release notes pertaining to the Session Manager
application.
2.4.9.1 Specifying Authorized User Node Names That Contain Reserved Characters
V1.2
When specifying a list of users who can access the X server in the Authorized Users dialog box, place the node name within quotation marks if the name contains any of the following:
Session Manager automatically adds quotation marks to the node name if they are needed, unless the node name begins with a double quotation mark. If the node name begins with a double quotation mark, Session Manager assumes that the user has already quoted the node name and does not change it.
Within a quoted string, a double quotation mark should be replaced by two double quotation marks (""). For example, the quoted string "DEC:.zko."my node"" should be changed to the following:
("DEC:.zko.""my node""").
|
V1.2
If you are using the color customizer example program provided in the
directory DECW$EXAMPLES to control Session Manager colors, the Session
Manager color customization dialog boxes used to modify those colors
may not reflect the correct current color values. This is normal
behavior; use the color customizer instead of the Session Manager color
customization dialog boxes to change these values. Alternatively, exit
the color customizer and restart your session.
2.4.9.3 Detached Processes Created by Default May Prevent Other Applications from Opening
Applications created by FileView and Session Manager are detached processes.
The implication is that during application startup,
SYS$MANAGER:SYLOGIN.COM and SYS$LOGIN:LOGIN.COM command procedures are
executed. Any command executed by these command procedures which reads
from SYS$INPUT reads data intended to be used by FileView or Session
Manager for the application startup. This prevents the application from
starting. Examples of such commands are INQUIRE, READ/PROMPT, and SET
TERMINAL/INQUIRE.
2.4.9.4 Change in Input Focus When Using a Private Logo
If you are logging into DECwindows Motif and using a private logo command
file, input focus might revert unexpectedly to the Username field when
the private logo starts up.
2.4.9.5 Stopping a Session Manager Process
Stopping the Session Manager process abruptly can have the following serious consequences for nonprivileged workstation users:
To avoid these problems, use the STOP/NOEXIT command to stop the process. Otherwise, stop the Session Manager process, and restart DECwindows from the SYSTEM account (or an account with system manager privileges):
$ @SYS$MANAGER:DECW$STARTUP RESTART |
This section contains release notes pertaining to the DECwindows Motif
Window Manager.
2.4.10.1 Help Text Does Not Display on All Screens in a Multihead System
V1.3
On the Traditional DECwindows Desktop, invoking help (by right-clicking) on a screen other than screen 0, displays an empty Bookreader window.
If you want to display help on a multihead configuration using the
right-click method, initiate the request from screen 0.
2.4.10.2 Alt + Space Key Does Not Post the Window Menu
With most Motif implementations, the Alt+space key combination prompts the Window Manager to display the Window menu. However, DECwindows Motif maps the Alt+space key binding to the Compose Character function. This provides a method for character composition on keyboards which do not supply a specific Compose Character key.
To change the Alt+space key binding so that it displays the Window menu, follow the procedure appropriate to your desktop environment.
For New Desktop systems:
Alt<Key>space icon|window f.post_wmenu |
For Traditional DECwindows Desktop systems:
Alt<Key>space icon|window f.post_wmenu |
V1.2
If you are using the color customizer provided in the DECW$EXAMPLES
directory to control Motif Window Manager colors, the Motif Window
Manager customization dialog boxes used to modify those colors may not
reflect the correct current color values. This is normal behavior; use
the color customizer instead of the Motif Window Manager color
customization dialog boxes to change these values. Alternatively, exit
the color customizer and then restart Motif Window Manager. See
HP DECwindows Motif for OpenVMS New Features for more information about the color customizer.
2.4.10.4 Changing Function Key Bindings Using the Window Manager Configuration File
The configuration file DECW$MWM_RC.DAT defines how the Window Manager uses the function keys. Most of the accelerators use the form Alt key (or Compose Character key) and function key, for example Alt+F7.
If any application needs to use these keys, you must either comment them out by placing an exclamation point (!) at the beginning of the line, or create new keyboard bindings. Then change Mwm*keyBindings:DefaultKeyBindings in the MWM resource file to point to the new bindings.
With the Motif binding, you can no longer use the Alt+spacebar or the Compose Character+spacebar to bring up the Window menu because it interferes with Compose Character sequences in DECterm. Use Shift+F11 to bring up the Window menu.
To reenable Alt+space, select the appropriate option in the Workspace
Options dialog box and apply the current settings. You can also remove
the comment for the default button bindings for Alt+space in the
DECW$MWM_RC.DAT file.
2.4.10.5 Restarting the Window Manager
The file SYS$MANAGER:DECW$MWM.COM contains settings that specify how
the Window Manager is restarted. By default, it is always restarted on
all the screens that are available. However, if you are not starting
the Window Manager from the Session Manager, then the Window Manager
might not have been initially started on all the available screens. You
can modify this file to change the way the Window Manager is restarted
for your system.
2.4.10.6 Customizing Color-Related Resources for Monochrome Monitors
The Motif Window Manager does not support full customization of color-related resources for monochrome monitors in the Options dialog box. In order to change the colors, you might need to modify the pixmap resources by directly editing the DECW$MWM_BW.DAT resource file. For example, to change the color of the active window's title background, you must change the Mwm*activeBackgroundPixmap resource. Some values include 25_foreground, 50_foreground, 75_foreground, and unspecified pixmap.
In addition, by default, the title text is created with a white
background. To use the same color as the rest of the title, set the
Mwm*cleanText
resource to FALSE.
2.4.10.7 Customizing Colors on Multihead Systems
If you have a multihead system with different monitor types (color,
monochrome, or gray-scale), you can customize the colors only by using
the Options dialog box on the monitors that match the type of your main
monitor (screen 0). To customize the other monitors, you must either
log in to a system with that monitor type or directly edit the resource
files.
2.4.10.8 Moving the Icon Box Off Screen
If you move the icon box to the edge of the screen and then resize it
using the keyboard, you can move it off the screen. To retrieve the
icon box, press Alt+Tab until you reach that window and then press
Shift+Escape (F11) to bring up the Window menu for that window. You can
then move the window back onto the screen.
2.4.10.9 Multiline Icon Title Not Centered
The Window Manager does not center all the lines of a multiline icon
title.
2.5 Tools and Utilities
This section contains notes related to X Window System utilities that
have been ported to DECwindows Motif.
2.5.1 X Authority Utility (xauth)
This section contains release notes pertaining to the X Authority
utility (xauth).
2.5.1.1 File Locking Not Supported with Logical Names
V1.3
The X Authority utility (xauth) does not support file locking when files are specified using a logical name. Since xauth does not translate OpenVMS logicals, it creates the lock files in the current default directory versus the directory specified by the logical.
For example, the following xauth command creates the lock files in the current default directory not in the USER directory specified by the logical XAUTH_FILE:
$ DEFINE XAUTH_FILE DISK:[USER]FILE.DECW$XAUTH $ XAUTH -f XAUTH_FILE |
In order to use logical names with xauth, translate each logical before invoking xauth, for example:
$ XAUTH_FILE = F$TRNLNM ("XAUTH_FILE")
$ XAUTH -f 'XAUTH_FILE'
|
Note that this restriction only pertains to using logical names with
xauth and does not apply when using logical names with the SET
DISPLAY/XAUTHORITY_FILE command.
2.5.1.2 Specifying File Names without File Types Can Result in Failure
V1.3
The X Authority utility (xauth) cannot differentiate between files and directories of the same name if the file does not yet exist and the type is not specified. For example, the following xauth command creates a set of lock files but does not create the X authority file:
$ CREATE/DIRECTORY [.TEST] $ XAUTH -f TEST |
In this case, xauth fails without reporting an error.
To prevent this problem from occurring, always specify a file type when
entering an X authority file specification.
2.5.2 Font Server Information Utility (fsinfo)
This section contains release notes pertaining to the Font Server
Information utility (fsinfo).
2.5.2.1 Font Server Information Utility Fails After Invoking
V1.3
In some cases, the Font Server Information utility (fsinfo) terminates
with an access violation after it is first invoked. If this situation
occurs, rerun fsinfo. Subsequent fsinfo sessions should be successful.
2.5.3 Print Screen
This section contains release notes pertaining to the Print Screen
utility.
2.5.3.1 Print Screen Truncates PostScript Output
V1.2--3
When using the Print Screen application to produce PostScript output on some printers, part of the output may be lost. Usually, the upper and left portion is missing when printing in landscape mode and the lower and left portion is missing when printing in portrait mode. This problem is caused by differences between PostScript printers.
To correct this problem, DECwindows Motif for OpenVMS Version 1.2--5 added support for four resources that can be specified in DECW$PRINTSCREEN.DAT:
PrintScreen.plxtranslate PrintScreen.plytranslate PrintScreen.plxscale PrintScreen.plyscale |
These resources control the size and position of the PostScript image on the page. The plxtranslate and plytranslate resources control the x and y offsets of the image in inches from the origin. The plxscale and plyscale resources are an x and y scale factor to allow the entire image to be displayed on the page after the origin is moved.
This chapter describes changes, corrections, restrictions, and known
problems that pertain to managing a DECwindows Motif system.
3.1 Installation and Upgrade Information
This section contains release notes related to the DECwindows Motif
installation and upgrade procedures.
3.1.1 DECwindows Motif Version Support and Compatibility
V1.5
The following table lists which versions of DECwindows Motif are supported on various platforms and versions of the HP OpenVMS operating system. Support is defined to mean all features and functionality are available, except for Display PostScript, which has been withdrawn from all DECwindows X display servers since OpenVMS Version 7.3.
| DECwindows Motif Version | OpenVMS Version |
|---|---|
| Version 1.5 |
OpenVMS I64 Version 8.2
OpenVMS Alpha Version 8.2 |
| Version 1.3--1 | OpenVMS Alpha Version 7.3--2 |
| Version 1.3 | OpenVMS Alpha Version 7.3--1 |
| Version 1.2--6 |
OpenVMS Alpha Versions 7.3, 7.3--1, 6.2
OpenVMS VAX Versions 7.3, 6.2 |
| Version 1.2--5 |
OpenVMS Alpha Versions 7.3, 7.3--1, 6.2
OpenVMS VAX Versions 7.3, 6.2 |
Note that since the DECwindows Motif Version 1.3 and higher releases are based upon specific OpenVMS server and device driver images, only install these releases of DECwindows Motif on the operating system versions listed above.
Mixed version clusters are supported as long as each system in the
cluster is running one of the supported combinations of DECwindows Motif
and OpenVMS listed in Table 3-1. Each version of OpenVMS must also
support cluster configurations. See the Software Product Description
(SPD) associated with each version of OpenVMS to determine whether
mixed-version cluster support is available.
3.1.2 Limited Support for Third-Party TCP/IP Products (Alpha Only)
V1.5
Significant changes were made to the DECwindows Motif TCP/IP transport interface in support of newer socket interfaces (getaddrinfo and getnameinfo) and their address formats. As a result, some third-party TCP/IP products may not be compatible with the updated interface. Specifically, older versions of MultiNet (prior to Version 5.1) and TCPware (prior to Version 5.7) from Process Software do not support the capabilities available with the updated DECwindows transport and prevent successful server connections.
Contact the TCP/IP product vendor to check for availability of software
patches or releases that support these newer interfaces.
3.1.3 DECW$STARTUP Requires SHARED Privilege
V1.5
The DECW$STARTUP.COM command file now requires the SHARED privilege in addition to those system privileges required previously. This enables a user whose account does not have all system privileges enabled to run the DECW$STARTUP RESTART command successfully from the serial console.
Note that to prevent any difficulties with system startup, HP
recommends that you start or restart DECwindows Motif from the SYSTEM
account.
3.1.4 Using Shareable Linkages to Install Images
V1.2--4
Using shareable linkages to install images on DECwindows Motif systems can offer the following advantages:
V1.3
By default, the following images are installed using shareable linkages:
DECW$XLIBSHR.EXE (X Library)
DECW$XTLIBSHRR5.EXE (X Toolkit Intrinsics)
DECW$XMLIBSHR12.EXE (Motif Toolkit)
DECW$MRMLIBSHR12.EXE (Motif Resource Manager)
DECW$DXMLIBSHR12.EXE (DECwindows Extensions to the Motif Toolkit)
CDE$UNIX_ROUTINES.EXE (UNIX emulation routines)
DECW$TRANSPORT_COMMON.EXE (Transport)
DECW$XPORT_SERVICES.EXE (Transport)
DECW$LCNLIBSHR.EXE (Logical Connection Number)
DECW$SETSHODISSHR.EXE (OpenVMS Display Device)
DECW$XAUSHR.EXE
DECW$ICELIB.EXE (ICE)
DECW$ICELIB_PTHREAD.EXE (ICE)
DECW$SMSHR.EXE (X Session Manager Protocol)
These images are installed using the /SHARE=ADDRESS_DATA and /RESIDENT options. Note that if you accept the default values, these images are installed as memory resident and cannot be replaced during a restart. As a result, the following message is displayed when you restart DECwindows Motif:
Shared linkage sections are in use on this system and no images will be reinstalled. If you are restarting DECwindows to reinstall images then you must reboot the system. |
To replace new images installed with this option, reboot the system.
Note that you can disable shared-linkage sections by defining the
logical name DECW$IGNORE_SHARE_ADDRESS in the SYSTARTUP_VMS.COM command
procedure.
3.1.5 DECW$COMPARE_VERSIONS Command File Limitation
V1.2--4
The DECW$COMPARE_VERSIONS command file compares version identifications
using two-digit years. Therefore, it will not compare version
identifiers correctly for images generated in the year 2000 and later
with version identifiers for images generated before the year 2000.
3.1.6 Restarting DECwindows Motif from the Operator Console (OPA0:)
V1.0
Starting or restarting DECwindows Motif by running DECW$STARTUP.COM from a serial console attached to OPA0: can change the characteristics of the terminal. For example, starting DECwindows Motif in this manner can change the current device type setting and prevent the subsequent use of an editor.
To prevent this from occurring, set the terminal characteristics permanently before invoking the DECW$STARTUP.COM procedure, as follows:
$ SET TERMINAL/INQUIRE/PERMANENT $ @SYS$MANAGER:DECW$STARTUP RESTART |
This section describes important issues and considerations related to
the tuning of DECwindows Motif.
3.2.1 Changes in Recommended UAF and System Parameter Values
V1.5
With this release of DECwindows Motif, many of the recommended minimum values for user authorization file (UAF) and system parameters on the OpenVMS Alpha platform have been significantly increased. In addition, a separate set of system parameter values has been generated for the OpenVMS I64 platform.
To optimize the performance of the DECwindows display server and client
applications, scan the current UAF and system parameter values on
systems running DECwindows Motif for OpenVMS Version 1.5 and make sure that they meet the
suggested minimum values listed in Appendix A of the Managing DECwindows Motif for OpenVMS Systems.
3.3 Security and Authorization
This section describes important issues and considerations related to
system security.
3.3.1 GENPWD Flag Now Handled Properly (Alpha Only)
V1.5
When a system manager sets the GENPWD flag on a user account, that user is restricted to using a generated password versus setting their own. Once the user's generated password expires, they must choose a new password from the generated list.
Previously when this flag was set on a user account, the following problems occurred:
These problems have been fixed with DECwindows Motif for OpenVMS Version 1.5.
3.3.2 BadAuthorizationProtocol Error Displayed When Generating Authorization Keys with Kerberos Enabled
V1.3--1
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 New Features manual to learn when and how to manually create X authority file entries for Kerberos-enabled servers.
| Previous | Next | Contents | Index |