V1.1

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.

Extensive SYLOGIN.COM or LOGIN.COM command procedures slow down application startup. Many of the operations performed in a SYLOGIN.COM or LOGIN.COM are meaningless for DECwindows application startup. Therefore, the SYLOGIN.COM and LOGIN.COM files should be conditionalized for DECwindows application startup performance. When starting a DECwindows application, only a minimum of SYLOGIN.COM and LOGIN.COM commands should be executed. Typically, the commands that should be executed are the redefinition of DECW$USER_DEFAULTS (if present), and other logical name definitions if the user will be referencing them from within the context of a DECwindows application. The following code segment can be inserted into SYLOGIN.COM and LOGIN.COM immediately following the commands necessary for DECwindows:

$ mode = f$mode() $ tt_devname = f$trnlnm("TT") $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and. - (f$locate("WSA",tt_devname) .ne. f$len(tt_devname)) $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. - (f$locate("MBA",tt_devname) .ne. f$len(tt_devname)) $ if session_mgr_login .or. session_detached_process then exit

Applications continue to run even if these lines are not added to the SYLOGIN.COM and LOGIN.COM files.

2.5.8.4 Change in Input Focus When Using a Private Logo

V1.0

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.5.8.5 Stopping a Session Manager Process

V1.0

Stopping the Session Manager process abruptly can have serious consequences for nonprivileged workstation users. DECwindows must be restarted to avoid the following problems:

• A nonprivileged user cannot start a new Session Manager or create a new login box.
• If the session is paused, the Pause cover window is deleted and unauthorized users can access windows on that workstation.
• The workstation can also become unusable if the Session Manager process is terminated by the job controller (for example, when the user's access hours, which might be from 8 a.m. to 5 p.m., are exceeded).
  As a possible solution, restart DECwindows on each workstation in a batch job that runs during off-hours.

Use the STOP/NOEXIT command to stop the process. Otherwise, stop the Session Manager process, and restart DECwindows (if you have system manager privileges) with the following command:

$ @SYS$MANAGER:DECW$STARTUP RESTART

2.5.9 Window Manager

This section contains release notes pertaining to the DECwindows Motif Window Manager.

2.5.9.1 Help Text Does Not Display on All Screens in a Multihead System

V1.3

Invoking help (by right-clicking) on a screen other than screen 0, displays a Bookreader window with no content.

If you want to display help on a multihead configuration using the right-click method, initiate the request from screen 0.

2.5.9.2 Alt + Space Key Does Not Post the Window Menu

V1.2--4

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:

1. Copy CDE$SYSTEM_DEFAULTS:[CONFIG.lang]SYS.DTWMRC to DISK$:[LOGIN.DT]DTWMRC.DAT.
2. In the Keys DtKeyBindings section, uncomment the following line:

   Alt<Key>space icon|window f.post_wmenu

3. Restart the Workspace Manager.

For Traditional DECwindows Desktop systems:

1. Copy DECW$SYSTEM_DEFAULTS:DECW$MWM_RC.DAT to DECW$USER_DEFAULTS:DECW$MWM_RC.DAT.
2. In the Keys DtKeyBindings section, uncomment the line:

   Alt<Key>space icon|window f.post_wmenu

3. Restart the Window Manager.

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 Alpha New Features for more information about the color customizer.

2.5.9.4 Changing Function Key Bindings Using the Window Manager Configuration File

V1.0

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.5.9.5 Restarting the Window Manager

V1.0

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.5.9.6 Customizing Color-Related Resources for Monochrome Monitors

V1.0

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.5.9.7 Customizing Colors on Multihead Systems

V1.0

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.5.9.8 Moving the Icon Box Off Screen

V1.0

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.5.9.9 Multiline Icon Title Not Centered

V1.0

The Window Manager does not center all the lines of a multiline icon title.

2.6 Tools and Utilities

This section contains notes related to X Window System utilities that have been ported to DECwindows Motif.

2.6.1 AccessX Keyboard Utility (accessx)

This section contains release notes pertaining to the AccessX Keyboard utility (accessx).

2.6.1.1 Change in Location of AccessX Configuration File

V1.3--1

With DECwindows Motif for OpenVMS Alpha Version 1.3--1, the location for the default AccessX configuration file has been changed from SYS$LOGIN:ACCESSX.DAT to DECW$USER_DEFAULTS:ACCESSX.DAT.

2.6.2 X Authority Utility (xauth)

This section contains release notes pertaining to the X Authority utility (xauth).

2.6.2.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.6.2.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 specifying an X authority file.

2.6.3 Print Screen

This section contains release notes pertaining to the Print Screen utility.

2.6.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.3--1

The following table lists which versions of DECwindows Motif are supported on various OpenVMS versions. Support is defined to mean all features and functionality are available, except for Display PostScript, which has been withdrawn from all servers since OpenVMS Version 7.3.

Table 3-1 Supported Versions of DECwindows Motif

DECwindows Motif	OpenVMS Version
Version 1.3--1	OpenVMS Alpha Version 7.3--2
Version 1.3	OpenVMS Alpha Version 7.3--1
Version 1.2--6	OpenVMS Versions 7.3--1, 7.3, 7.2-2, 7.2, 6.2
Version 1.2--5	OpenVMS Versions 7.3, 7.2--2, 7.2, 6.2

Note that since the DECwindows Motif Version 1.3 and 1.3--1 releases are based upon specific OpenVMS Alpha server and device driver images, only install these releases of DECwindows Motif on the operating system versions listed above.

3.1.2 Using Shareable Linkages to Install Images

V1.2--4

On OpenVMS Alpha systems, using shareable linkages to install images on DECwindows Motif software offers the following advantages:

• Enhanced startup performance by decreasing image-activation time
• Conserved memory usage by decreasing the total of memory pages used by the image

V1.3

By default, the following images are installed using shareable linkages on Alpha systems:

• DECW$XLIBSHR.EXE (Xlib)
• DECW$XTLIBSHRR5.EXE (Xt 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 option. Note that if you accept the default, these images cannot be replaced during a restart of DECwindows Motif software. As a result, when you restart DECwindows, the images are not replaced and the following message is displayed:

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.3 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.4 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

3.2 System Tuning and Performance

This section describes important issues and considerations related to the tuning of DECwindows Motif.

3.2.1 Support for SYSMAN STARTUP OPTION Settings

V1.3--1

In previous releases, the DECwindows Motif startup command files interfered with the use of SYSMAN startup options. The STARTUP OPTION settings (set using SYSMAN or STARTUP_P2 during a conversational boot) enable the logging of output during startup and DCL command line verification. The DECwindows Motif startup files disabled the logging or verification process partway through the system startup sequence, resulting in data loss.

With DECwindows Motif for OpenVMS Alpha Version 1.3--1, this problem has been corrected.

V1.2--5

On systems with Powerstorm 4d20 or ZLXp-E2 graphics cards, the operating system may hang or become extremely sluggish if you have a large number of open application windows or if certain CDA documents are opened. To verify that a system hang is caused by this problem, use the Watch Errors utility in the Desktop Tools drawer of the Application Manager. If the system hang is due to this problem, you will see the following:

-> RCV'D (pid nnnnnnnn): RCV'D (pid nnnnnnnn %SYSTEM-F-EXBUFOBJLM, exceeded systemwide buffer object page limit (MAXBOBMEM)

At the present time, there is no workaround for this problem other than using fewer windows (increasing the MAXBOBMEM value doesn't fix the problem). If you experience this problem, you may want to keep a DECterm window free so that you can perform a graceful system reboot. Otherwise, you will need to perform a hard reboot.

3.2.3 Error Messages Displayed During Startup

V1.2--4

At startup, error messages similar to those shown in Example 3-1 are displayed when:

• Shareable address linkage is being used (the default setting).
• DECwindows is not started as part of system startup but is started later.

These error messages are generated because there is not enough memory in the granularity hints region to install images resident. The images are installed nonresident, without shared address linkage, so DECwindows startup can complete. However, the performance and memory advantages of using shared address linkage are lost.

The amount of memory in the granularity hints region is determined by the system parameter GH_RSRVPGCNT. In DECwindows Motif for OpenVMS Version 1.2--3 and earlier versions, this parameter was set to 512, which allowed DECwindows to start at any time with shared address linkage. However, this also consumed a large amount of physical memory.

To prevent memory from being wasted, OpenVMS temporarily increases the size of the granularity hints region during system startup and releases the unused memory once startup has completed. Starting with DECwindows Motif for OpenVMS Version 1.2--4 DECwindows Motif takes advantage of this by allowing GH_RSRVPGCNT to remain at its default value of zero. DECwindows images can be installed resident and with shared address linkage as long as DECwindows is started during system startup, as it is by default.

Example 3-1 Error Messages Displayed Due to Low Memory in Granularity Hints Region

%INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %INSTALL-I-NONRES, installed image non-resident with other specified options -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %RUN-S-PROC_ID, identification of created process is 00000092 %RUN-S-PROC_ID, identification of created process is 00000093 %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %INSTALL-I-NONRES, installed image non-resident with other specified options -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. -SYSTEM-F-PAGOWNVIO, page owner violation -SYSTEM-S-NORMAL, normal successful completion -DEBUG-W-NOIOCHAN, no I/O channel available %INSTALL-I-NONRES, installed image non-resident with other specified options -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. -SYSTEM-F-VA_IN_USE, virtual address already in use -SYSTEM-S-NORMAL, normal successful completion -DEBUG-W-NOIOCHAN, no I/O channel available %INSTALL-I-NONRES, installed image non-resident with other specified options -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. -SYSTEM-F-VA_IN_USE, virtual address already in use -SYSTEM-S-NORMAL, normal successful completion -DEBUG-W-NOIOCHAN, no I/O channel available %INSTALL-I-NONRES, installed image non-resident with other specified options -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. -SYSTEM-F-VA_IN_USE, virtual address already in use -SYSTEM-S-NORMAL, normal successful completion -DEBUG-W-NOIOCHAN, no I/O channel available %INSTALL-I-NONRES, installed image non-resident with other specified options -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. -SYSTEM-F-VA_IN_USE, virtual address already in use -SYSTEM-S-NORMAL, normal successful completion -DEBUG-W-NOIOCHAN, no I/O channel available %INSTALL-I-NONRES, installed image non-resident with other specified options -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint region