[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

Content starts here

HP DECwindows Motif
for HP OpenVMS Alpha
Release Notes


Previous Contents Index


Chapter 2
General User Release Notes

This chapter contains information about HP DECwindows Motif for HP OpenVMS Alpha Version 1.3 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.

2.1.1.1 SET DISPLAY/REVOKE Error Message is Misleading

V1.3

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.

2.1.1.2 SET DISPLAY/GENERATE Fails When Kerberos is Enabled

V1.3

When using the Kerberos authentication protocol, the following command does not work:


$ SET DISPLAY/GENERATE=(PROTOCOL=MIT-KERBEROS-5)

There is no workaround to this problem.

2.1.1.3 I/O Error Displayed When Using SET DISPLAY/REVOKE

V1.3

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.

2.1.1.4 SET DISPLAY/REVOKE Can Crash the X Server

V1.3

The following sequence of commands can cause an X server crash.


$ SET DISPLAY/CREATE/TRANSPORT=DECNET/GENERATE=(TRUSTED)
$ SET DISPLAY/REVOKE

The problem also occurs if you substitute TCPIP for DECNET.

To avoid this problem, do one of the following:

  • Do not activate the Security (SECURITY) and Application Group (XC-APPGROUP) extensions. In SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM, make sure that SEC_XAG is not included in the definition for DECW$SERVER_EXTENSIONS.
  • Use the LOCAL transport.


    $ SET DISPLAY/CREATE/TRANSPORT=LOCAL/GENERATE=(TRUSTED)
    
  • Enable security auditing by setting the DECW$SERVER_AUDIT_LEVEL server parameter to a value of 4 or greater in the file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM.

2.1.1.5 Display Devices Not Deleted Upon Exit

V1.2

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 Debugger

This section contains notes pertaining to the DECwindows Motif interface to the OpenVMS Debugger.

2.1.2.1 DECwindows Motif Interface to the OpenVMS Debugger Not Working Properly

V1.3

The DECwindows Motif interface to the OpenVMS Alpha Version 7.3--1 Debugger does not function as expected with HP DECwindows Motif for HP OpenVMS Alpha Version 1.3. An update kit for the OpenVMS Alpha Debugger is available that corrects this problem. Contact your HP customer support representative to obtain the TIMA kit for OpenVMS Alpha Version 7.3--1 related to this issue.

2.1.3 DECTPU

This section contains release notes related to the DECwindows Motif interface to DECTPU.

2.1.3.1 Small Display Monitors and DECTPU

V1.0

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 your DECTPU 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.


    $  DEFINE TPU$DEFAULTS SYS$LOGIN:EVE_SMALL_WINDOW.DAT
    $  EDIT/TPU/INTER=DECWINDOWS 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

V1.3

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

CSWB is available from the following OpenVMS web page:


http://www.openvms.compaq.com/openvms/products/ips/cswb/cswb.html

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

V1.3

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 startup priority of the server process (DECW$SERVER_0) to 4.

2.2.3 Application Race Condition Can Crash the X Server

V1.2-6

Quickly spawning and killing multiple client application processes on a multihead system has occasionally caused a crash of the X server. Abruptly stopping a client application before it has finished connecting to the server can prompt a race condition that causes the server to crash.

To avoid this problem, allow sufficient time for each application to connect to the server before stopping the application process.

2.2.4 Support Discontinued for Display PostScript

V1.2--6

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

2.2.5 Limited Support for Tear-Off Menus

V1.2--3

The following applications do not support tear-off menus:

  • CDA Viewer
  • Notepad
  • Print Screen

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

V1.2--3

"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.7 Printing from Applications Linked Against OSF/Motif Release 1.1.3

V1.2

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.

2.3 New Desktop Environment

This section contains release notes that pertain to the New Desktop environment.

2.3.1 Full File Specification No Longer Displayed in DTPAD Banner

V1.3

When selecting a file from the File Manager (DTFILE) and opening that file for editing (using DTPAD), the full file specification (node, disk, directory, and filename) is no longer displayed in the window banner. Only the filename portion of the specification is displayed.

2.3.2 Style Manager Displays Incorrect Security Options on Multihead Systems

V1.3

When the using the Style Manager to access the Security Options dialog box from a screen other than screen 0, the settings shown in the dialog box may be incorrect.

To prevent this from occurring, always display the Security Options dialog box from screen 0. Use the Set Default Screen tool to select the screen on which the Style Manager displays.

Note that this problem only occurs on multiheaded systems configured without XINERAMA. In the XINERAMA case, there is only one logical screen.

2.3.3 Desktop Applications Disappear When Setting a Home Session

V1.2--6

In the Style Manager, selecting Startup and then Set Home Session can cause applications that you previously started using the Application Manager to disappear. This can happen if you start these applications with the Application Manager and then close the Application Manager before setting your home session.

The workaround is to keep the Application Manager window open.

2.3.4 DTSESSION Logging Problem

V1.2--5

In some cases, DTSESSION continues to log errors to its log file until all free disk space is filled. These errors could occur, for example, if DECW$DISPLAY is set to an incorrect value, or if CDE$SYSTEM_DEFAULTS:[BIN]DTSCREEN.EXE is not properly installed.

If on the New Desktop the Session Manager (DTSESSION) is unable to start the Screen Saver (DTSCREEN), it logs an error to the log file device:[user.DT]ERRORLOG. DTSESSION logs this error at a user-settable interval controlled by the Style Manager's "Time Per Background" parameter.

To workaround this problem, increase the "Time Per Background" parameter to the maximum (120 minutes), or exit the New Desktop when you are done with it, rather than locking the screen.

2.3.5 File Manager Problems with Extended File Specifications

V1.2--5

  • The "Selected/Move to" menu item does not support case preservation. The files are moved correctly, but case is not preserved.
  • The File Manager currently does not support case preservation when you create file names that contain special characters. For example, "Special^&Characters" will be converted to "SPECIAL^&CHARACTERS.;1".
  • The "Selected/Put in Trash" menu item does not work on ODS-5 volumes marked for EFS (Extended File Specifications). This applies only to folders with extended file names. An error message similar to the following is displayed:


    File Manipulation Error
    
    Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm-
      QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1"
    The most common cause is that you do not have
    the correct permissions for the involved
    files or folders.
    To view permissions, select the object and
    then select "Change Permissions..." from the
    Selected or popup menu.
    

    These files can be deleted at the DCL level.
  • Dragging a file or folder with an extended file name to Trash causes an error message. On an ODS-2 volume you can drag a file or folder with a short file name to Trash and still be able to restore it. On an ODS-5 volume you can drag a file or folder with a short name to Trash, but you cannot restore even files with short names from an ODS-5 volume. These files can be deleted at the DCL level.
  • The "File/New Folder" menu item can handle the creation of a folder when the path length exceeds 255 characters, but the folder cannot be displayed (it is hidden). These files can be viewed at the DCL level.
  • The "File/Find/File" menu item cannot find a file with file name that exceeds 235 characters if the full file name has been entered in the dialog's form field. To avoid the problem, use wildcards to conduct the search.
  • The "Selected/Purge" menu item does not work for long file names on ODS-5 volumes marked for EFS (Extended File Specifications). "Short" file names do not present this problem. An error similar to the following is displayed:


    File Manipulation Error
    
    Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm-
      QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1"
    The most common cause is that you do not have
    the correct permissions for the involved
    files or folders.
    To view permissions, select the object and
    then select "Change Permissions..." from the
    Selected or popup menu.
    

    These files with long file names can still be purged at the DCL level.
  • Updated protection settings are not displayed when invoking "Fileview/Command/Protection," although the settings have actually been updated. However, the new settings can be verified by either issuing a DCL command or invoking "Fileview/Command/Show File."

2.3.6 DECwrite Icon Does Not Open DECwrite Program

V1.2--5

DECwindows does not include the DECwrite program. However, it does include the DECwrite icon on the New Desktop. If the DECwrite product has not been installed, clicking on the DECwrite icon results in the following error messages:


> RCV'D (pid 000000CA): %DCL-W-IVVERB, unrecognized command verb -
                         check validity and spelling
-> RCV'D (pid 000000CA):  \DECWRITE\
-> RCV'D (pid 000000CA):   TESTER       logged out at
29-JUL-1998 17:56:44.63

If the DECwrite product is installed and you still get this error, ensure that DECwrite is started in SYSTARTUP_VMS.COM.

2.3.7 Delay When Exiting a Session with Open TPU Windows

V1.2--4

Users will experience a one-minute delay for each DECwindows Text Processing utility (TPU) window displayed when exiting the session or when saving a home session.

The DECwindows interface for TPU (EVE editor) requires notification if its state needs to be saved, but it does not respond to that notification sent by Session Manager. The Session Manager waits one minute for a response before continuing, resulting in the delay.

2.3.8 Viewing TIF Files with dximageview

V1.2--4

When using dximageview to view TIF formatted files from the CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS] directory, the following warning messages are displayed:


TIFFOpen: Warning, unknown field with tag 34209 (0x85a1) ignored.
TIFFOpen: XResolution: Rational with zero denominator (num = 200).

Note this error only occurs with the TIF files in CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS]; it is only a warning. The file is still displayed correctly by the image viewer.

2.3.9 Text Editor Restrictions

V1.2--4

The Text Editor application, which is part of the New Desktop, is described in Chapter 10 of the Common Desktop Environment: User's Guide. Currently, it has the following issues and restrictions:

  • The reference page for Text Editor describes a client/server implementation of the Text Editor. This release of the Text Editor supports the -"standAlone" option only and is not built as a client/server application.
  • The spell-checking function described in the section "To Correct Misspelled Words" is not implemented in this version of the Text Editor.
  • The Text Widget upon which the New Desktop Text Editor is based does not set the size of a tab to exactly the width of eight (8) characters; it is usually slightly larger. When displaying text with a combination of spaces and tabs, text may not appear vertically aligned.

2.3.10 Some File Names Displayed in UNIX Format

V1.2--4

In the Application Manager Find dialog box and in error messages reported by the Help Viewer, file names are displayed in UNIX format rather than in standard OpenVMS format. For example, SYS$SYSROOT:[SYSMGR]LOGIN.COM appears as /sys$sysroot/sysmgr/login.com.

2.3.11 Front Panel Clock is an Icon Only

V1.2--4

The New Desktop Front Panel Clock is an animated icon that displays the current system time using an analog display. The icon has no other function and does not support single-click or double-click operations.

2.3.12 ToolTalk Actions Not Supported

V1.2--4

Creation of ToolTalk Action definitions in the Action Definition files (*.dt) as described in the Common Desktop Environment: Advanced User's and System Administrator's Guide is not supported. Although some ToolTalk actions exist in the Action Definition files installed with this product, modification of these actions is not supported and could cause some New Desktop functions to fail.

2.3.13 Session Manager Save and Restore Limitations

V1.2--4

The Session Manager supplied with the New Desktop supports the WM_SAVE_YOURSELF protocol for the following DECwindows Motif applications: Bookreader, DECterm, and Calendar.

Note

This Session Manager application should not be confused with the Session Manager protocol that is part of X11R6.6 and available with HP DECwindows Motif for HP OpenVMS Alpha Version 1.3 systems.

Applications that have been written to take advantage of this protocol can:

  • Save their state when the user exits a session.
  • Restore a state when the user starts a new session.

The New Desktop applications support save/restore, but many existing DECwindows Motif applications have not been modified to support the WM_SAVE_YOURSELF protocol.

The impact of this difference between existing and new applications can be seen during a logout/login sequence as follows:

  • Applications supporting save/restore create a main window if they were running when the user logged out.
  • Applications that do not support save/restore do not automatically restart.

An example of an existing DECwindows Motif application that supports save/restore is DECwindows Mail.

2.3.14 File Manager Search List Limitations

V1.2--4

The File Manager application has the following limitations with search lists in the New Desktop environment.

  • If you specify a folder (directory) name, which is strictly a logical name, and the logical name translates to a search list, only the first directory encountered in the search list is displayed.
  • When displaying a directory whose name includes a search-listed device, all directories in the search path are displayed. If more than one directory with the same name exists in the search path, an icon appears for each instance of that directory. If more than one file with the same name exists in the search path, the behavior depends on whether the Show Top Version Only filter option has been selected. If selected, only one icon of the file with the highest version is displayed. If not selected, all versions from all locations are displayed. However, if more than one of the files has the same version number, any action to any of the files with that version applies to the first occurrence of the file in the search path.
    For example, suppose the files SYS$SPECIFIC:[SYSMGR]TOOLS.DIR;1 and SYS$COMMON:[SYSMGR]TOOLS.DIR;1 both exist in a system. If a user switches to the directory SYS$SYSROOT:[SYSMGR], two icons represent the file TOOLS.DIR. Operations performed on either of the two icons work identically. New files are created in the first directory in the search path. In addition, some actions for these icons may not work properly.
    To work around this problem, specify explicit directory names when a conflict occurs, for example, SYS$SPECIFIC:[SYSMGR] or SYS$COMMON:[SYSMGR].

2.3.15 Login and Pause Screen Text Field Restrictions

V1.2--4

The following sections provide information about the Login Screen and Pause Screen text fields.


Previous Next Contents Index