| Previous | Contents | Index |
V1.3--1
The Low-Bandwidth X (LBX) proxy server (and other third-party proxy servers) do not support use of XC-QUERY-SECURITY-1 authentication protocol. This authentication protocol, which is enabled by the SECURITY server extension, is typically used by firewall servers to verify the security configuration of the display server to which they are connecting. Normally, firewall servers connect directly to a display server and do not use a proxy server as an intermediary.
If a client application uses a third-party proxy server to connect to an X display server using the XC-QUERY-SECURITY-1 protocol, the application may loop, block, or crash. The LBX proxy server has been modified to detect whether the protocol is in use, and in this situation, produces the following error message:
Multi-pass authentication not supported by LBX |
When using a proxy server to process connections to one or more X display servers, verify that the SECURITY extension is not enabled on the X servers. Do this by scanning the DECW$PRIVATE_SERVER_SETUP.COM file on each server system and checking that the parameter DECW$SERVER_EXTENSIONS does not contain a value of SEC_XAG.
3.6.2 Proxy Manager Process Does Not Restart Automatically
V1.3
The following problems can occur with the proxy manager when DECwindows Motif is configured to restart the proxy manager process automatically and the DECwindows Motif session is manually restarted:
Note that these problems do not occur when DECwindows Motif is restarted as part of an ordered system shutdown (reboot).
To manually restart the proxy manager, enter the following command for the active proxy manager process before restarting DECwindows Motif:
$ STOP DECW$PROXY |
Note that this command not only stops the active proxy manager process, but also terminates all proxy server connections managed by the process.
To ensure that the owner of the proxy manager process is the SYSTEM
account, always log in as SYSTEM when restarting DECwindows Motif.
3.6.3 Proxy Manager Configuration File Restriction
V1.3
The proxy manager does not support specifying more then one managed or
unmanaged entry for the same proxy service in the configuration file.
If there are multiple entries, only the first one will be processed.
3.7 X Display Server Management
The following sections contain release notes pertaining to the
management of the DECwindows X11 Display Server.
3.7.1 Using XINERAMA on New Desktop Systems
V1.3--1
The following restriction exists when using the New Desktop on a multiheaded system based on XINERAMA.
Some DECwindows Motif dialog boxes are designed to display at the center of the screen. If there are an even number of screens in any one direction, the dialog boxes are displayed at the junction of two screens, making them difficult to view. Some dialog boxes can be repositioned on screen; however, the following cannot since they are displayed while the Window Manager is not running:
You can manually reposition the login dialog box by setting the following resources in the XRESOURCES.DAT file located in CDE$SYSTEM_DEFAULTS:[CONFIG.C]:
Dtlogin*matte.x: 50 Dtlogin*matte.y: 100 |
The XRESOURCES.DAT file in CDE$SYSTEM_DEFAULTS is replaced each time you install DECwindows Motif. HP recommends that you store modified copies of this file in CDE$USER_DEFAULTS:[CONFIG.C] to save any customized settings. |
Once you have redefined the Dtlogin*matte resources, restart the login process. The login dialog box will be displayed at the specified (x, y) coordinates. If either position is omitted, or is set to zero, the screen will be centered on that axis.
Note that the vertical position of the screen may be slightly above
center if the console window is in use.
3.7.2 Some Combinations of Server Extensions Not Supported
V1.3
Currently, the following combinations of X server extensions are not supported:
Note that these extensions may be enabled concurrently on the same
DECwindows Motif system. However, due to resource or function conflicts,
concurrent use of these extensions on the same system is not supported.
3.7.3 Extraneous Characters Displayed When Running XMAG in a Vertical Multihead Configuration Using XINERAMA
V1.3
When using XMAG to display an image on a multihead system using
XINERAMA, a one-pixel line of extraneous characters might appear
between the screens when the screens are configured vertically. This
problem does not occur when the screens are configured horizontally.
3.7.4 Incorrect Placement of Cascade Menus in Multihead Configurations Using XINERAMA
V1.3
In some cases, DECwindows Motif cascade menus may not appear on the
correct screen in a multihead configuration using XINERAMA. The menu is
displayed in the correct position on the wrong screen. Currently, there
is no workaround.
3.7.5 XINERAMA Supported in 2D Mode Only
V1.3
Using the XINERAMA extension to the X server with 3D applications, such as OpenGL, is not supported. This extension should be used in a 2D environment only.
This chapter contains release notes related to programming in the
DECwindows Motif environment.
4.1 General Programming
This section contains release notes pertaining to the general
DECwindows Motif programming environment.
4.1.1 OSF/Motif Toolkit Support and Compatibility
V1.3--1
The following table lists the versions of the OSF/Motif Toolkit and X Window System upon which each release of DECwindows Motif is based.
| DECwindows Motif | OSF/Motif Toolkit | X Window System |
|---|---|---|
| Versions 1.3 and 1.3--1 | CDE Motif 1.0 (OSF/Motif Release 1.2.5) | Version 11 Release 6.6 (X11R6.6) |
| Versions 1.2--4, 1.2--5, and 1.2--6 | CDE Motif 1.0 (OSF/Motif Release 1.2.5) | Version 11 Release 5 (X11R5) |
| Version 1.2--3 | OSF/Motif 1.2.3 (with extensions for the Common Desktop Environment (CDE)) | X11R5 |
| Version 1.2 | OSF/Motif 1.2.2 | X11R5 |
| Version 1.1 | OSF/Motif 1.1.3 | Version 11 Release 4 (X11R4) |
| Version 1.0 | OSF/Motif 1.1.1 | X11R4 |
Note that although DECwindows Motif for OpenVMS Version 1.1 applications will continue to run without modification with current version of DECwindows Motif, only those applications that have been built against the OSF/Motif Release 1.2.2 Toolkit can take advantage of Version 1.2 features, such as drag-and-drop functionality and tear-off menus.
See Appendix B for additional information related to the OSF/Motif
Toolkit.
4.1.2 Run-Time and Programming Environment Support
The following run-time and programming environments are provided with the HP DECwindows Motif for OpenVMS Alpha Version 1.3--1 software:
V1.3--1
The UIL compiler has a maximum number of top-level widgets that it can write to the UID file. A top-level widget is one that is named and not referenced within the UIL compilation. By default, the maximum number of widgets is set to 1000. If this limit is exceeded, the following error message is displayed by the UIL compiler:
$ UIL test.uil %UIL-F-SUBMIT_SPR, internal error - submit defect report |
To change this limit and prevent this error from occurring, use the logical DECW$MRM$MAX_MODULE_WIDGET. Make sure that you define the logical prior to running the UIL compiler, as follows:
$ DEFINE DECW$MRM$MAX_MODULE_WIDGET 2000 $ UIL test.uil |
The error message noted above can also result from other compilation problems. If you have already used the DECW$MRM$MAX_MODULE_WIDGET logical to increase the maximum number of top-level widgets, and the error continues to be displayed during compilation, examine the UIL file for other build issues and dependencies. |
V1.3
The addition of significant new functionality in the DECwindows Motif client libraries may increase the stack space used by DECwindows Motif at run time. Client applications that call DECwindows Motif functions from threads other than the main thread may experience a stack overflow.
If an overflow occurs, rebuild the application using a larger stack size for created threads.
Note that this problem does not occur with single-threaded applications
or those multithreaded applications that make all their calls to
DECwindows Motif from the main application thread.
4.1.5 Privileges Required for ICE, Proxy Manager, and LBX Server Processes
V1.3
The Inter-Client Exchange (ICE), proxy manager, and Low-Bandwidth X (LBX) proxy server each provide functions that can establish separate server processes. These server processes may require certain system resources to gain access to one or more transport interfaces and to manage client connections.
The following table shows the minimum privileges required, according to network transport, to gain access to the appropriate resources:
| Transport | Privilege |
|---|---|
| TCPIP | NETMBX |
| DECNET | TMPMBX, NETMBX, and SYSNAM |
| LOCAL | PRMMBX and SYSGBL |
V1.2--6
Starting August 1, 1998, support was discontinued for the Display PostScript software licensed by Adobe Systems Incorporated. This action resulted from Adobe ending their former ongoing support of Display PostScript.
Due to this decision, HP is contractually obligated to remove all Display PostScript capability from the DECwindows Motif software. This includes all related translated-image support and any functionality described in the following programming reference manuals:
Currently, there is no workaround. See the following sections for more
information on the potential impact to applications in the
DECwindows Motif environment.
4.1.6.1 Impact on DECwindows Motif Applications
Removing Display PostScript from DECwindows Motif impacts any application that relies on its capabilities to present and display graphics and documents in PostScript format.
Unfortunately, this includes not only those applications developed by HP, such as the CDA Viewer, but also any third-party, user-written, or translated VAX applications that depend on one or more of the following files and libraries. These items are no longer a part the product kit and are removed from your system when upgrading from a previous version of DECwindows Motif client software.
The actual effect of removing Display PostScript depends on the extent to which it was implemented in the application. Applications that call the PSWRAP command, may fail only at the point where the command is invoked. However, applications that link against one or more of the XDPS libraries or TIS images will fail to function entirely due to unresolved links at run time.
As a result, you may need to modify those portions of DECwindows Motif
applications that rely on these files to run successfully in the
DECwindows Motif for OpenVMS Alpha Version 1.3 environment.
4.1.6.2 Impact on Java Applications
The Java Development Kit (JDK) for OpenVMS Version 1.2.2-1 contains two shareable images (JAVA$FONT_MANAGER_SHR.EXE and JAVA$FONT_MANAGER_G_SHR.EXE) that link against the Display PostScript (XDPS) libraries. As a result, all Java applications built with this kit that use Display PostScript capabilities will fail in the DECwindows Motif for OpenVMS Version 1.2--6 environment.
Note that this restriction only applies to the Version 1.2.2-1 kit. The
Java machine for the 1.1* series, as well as all releases of the JDK
subsequent to Version 1.2.2-1, are not dependent on the Adobe Display
PostScript software or its libraries.
4.1.7 Problems Using the DECW$INCLUDE:INTRINSIC.H File
V1.2--5
The DECwindows header file, DECW$INCLUDE:INTRINSIC.H, redefines the globalref macro to be extern when using the DEC C compiler, even when the /STANDARD=VAXC compiler switch is specified. This could have a wide impact on user applications.
This redefinition in INTRINSIC.H is required because DECwindows needs to ensure that references to data located in the DECwindows shared images by user-written applications use the same extern model that was used when the DECwindows shared images were compiled.
To workaround this problem, rather than having your application use globalref and globaldef for its own variables, use the following preprocessor directive:
#pragma extern_model strict_refdef |
This workaround has the advantage of being strictly ANSI compliant.
This pragma directive is described in the DEC C User's Guide for
OpenVMS Systems manual.
4.1.8 DECW$WML.EXE Looks in Current Directory For DECW$WML_TOKENS.DAT
1.2--4
The program SYS$SYSTEM:DECW$WML.EXE can be used to customize the
parsing of UIL files. It reads a list of tokens from the file
DECW$WML_TOKENS.DAT. In previous versions of DECwindows Motif, this tokens
file was always read from SYS$LIBRARY. However, starting with
DECwindows Motif for OpenVMS Version 1.2--4, DECW$WML.EXE first looks for this file in the current
directory before looking for it in SYS$LIBRARY. This allows a
customized tokens file to be used.
4.1.9 UIL Compilation Problems with Looped Object References
V1.2
The UIL compiler can omit information about some objects from the UID file when there is a self-contained hierarchy of objects and each named object is only referenced internally (by another object in the hierarchy). Minimally, one of the references in the hierarchy must be something other than a child relationship.
To determine which objects contain omissions, use the /LIST and /MACHINE_CODE qualifiers during compilation. The resulting list file indicates the objects that are missing information.
To prevent this from occurring, add a name to one of the unnamed
objects in the hierarchy.
4.1.10 Use of _Xm Routines
The OSF/Motif Toolkit libraries contain many undocumented routines, which are prefixed with _Xm. These routines are intended to be used only by the standard Motif widgets. OSF reserves the right to modify the API or functionality of these routines, or to delete them altogether in future releases.
HP supplies access to the _Xm routines by copying them into the shareable image transfer vector for the OSF/Motif Release 1.2.2 Toolkit. HP does not document or support these routines or guarantee their continued existence in future releases. Application developers who use these routines do so at their own risk. |
V1.1
On OpenVMS Alpha systems, some of the include files used for writing DECwindows Motif applications in Fortran, such as the DECW$MOTIF.FOR file, contain structure definitions that cause memory layout changes, depending on the compiler switches used.
You can do one of the following:
CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL |
CDEC$ END OPTIONS |
CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL INCLUDE "DECW$MOTIF.FOR" CDEC$ END OPTIONS |
During the VAX C layered-product installation procedure, you have the option of extracting the VAX C definition files (.h files) or leaving the .h files in the text library. If you extract the definition files, you can use #include control lines of the following form:
#include <filename.h> |
The DECwindows header files assume that the .h files were extracted. They contain #include <module_name.h> notation for the included files. The DECwindows Motif programming documentation also makes this assumption.
VAX C should, therefore, be installed using the option to extract the library modules.
If you have already installed VAX C and you did not extract the .h files, the DECwindows sample C programs do not work. To correct this problem, reinstall VAX C and extract the .h files.
With DEC C, the header files do not need to be extracted from the text library if you define the DECC$TEXT_LIBRARY logical name as follows:
$ DEFINE DECC$TEXT_LIBRARY SYS$LIBRARY:DECC$RTLDEF.TLB |
| Previous | Next | Contents | Index |