V1.0

To create a process that uses a virtual terminal, enter the following command:

$ CREATE/TERMINAL/NOPROCESS

Then establish focus to the newly created DECterm, press Return, and log in. Note that the /DEFINE qualifier is not required.

2.17.7 DTSESSION Logging Problem (New Desktop Only)

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 the New Desktop's 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.18 Console Window Application

V1.2--3

DECwindows Motif Version 1.2-3 for OpenVMS introduced the feature of displaying console messages in the Console Window application. Previous versions of DECwindows Motif displayed the console window by default.

Specify how to display messages by defining the global symbol DECW$CONSOLE_SELECTION in the customized startup file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM. Enter one of the following values: WINDOW, DISABLE, or ENABLE.

• WINDOW
  Displays console messages in the Console Window application. This is a new application starting with the DECwindows Motif Version 1.2-3 for OpenVMS software. If you specify the WINDOW value, the Console Window is displayed in the lower right corner of the login screen by default and continues to be displayed after the user logs in to the system.
  The Console Window application shares the same executable file and looks similar to the Message Window. However, a menu bar is not displayed in the Console Window; it reads its resources from the DECW$CONSOLE.DAT file instead of from the DECW$MESSAGEPANEL.DAT file. Internally, the Console Window is invoked by running the DECW$MESSAGEPANEL.EXE executable with the command line option -console.
  To control the initial position of the Console Window and the classes of OPCOM output that are enabled, you can the define the following global symbol in the file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM:
  • DECW$CONSOLE_GEOMETRY
    This symbol specifies the value of the -geometry option in the DECW$MESSAGEPANEL.EXE command line; this command is used to start the Console Window application. The default value is "-0-0", which specifies the location of the window in the lower right corner of the screen.
    To position the window at the lower left corner of the screen, for example, add the following line to the command file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM:

    $ DECW$CONSOLE_GEOMETRY == "+0-0"

• DISABLE (default)
  Disables broadcasts to the OPA0: device. Console messages are not displayed.
• ENABLE
  Displays console messages in the console window. The console window is a six-line display area at the top of the workstation screen.

  Note Although ENABLE was the default value in previous releases of DECwindows Motif, it is recommended that you do not use this option with DECwindows Motif Version 1.2-3 for OpenVMS and later versions. Displaying console messages by default in the console window can corrupt the contents of the workstation display.

Refer to Managing DECwindows Motif for OpenVMS Systems for information about defining global symbols in the file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM.

2.19 Window Manager Overlay Support

V1.2--3

The latest version of the Window Manager (MWM) is modified to support overlays and utilize additional planes of memory, which are available on several 3D graphics accelerators: ZLX-M1, ZLX-M2, ZLX- L1, ZLX-E2, ZLX-E3, ZLXp-E2, and ZLXp-E3. The Window Manager places borders and banners for all the windows into these extra planes of memory and thereby reduces the number of expose events for your applications that use overlays.

Modify your existing applications that use overlays to avoid potential problems with the colormap. Set up your system to share the overlay colormap with the Window Manager, as the hardware supports only one colormap for the overlay planes.

To modify your applications to share the overlay colormap with the Window Manager, query the server property name SERVER_OVERLAY_COLORMAPS. When you make the query, the server returns the 32-bit value for the overlay Colormap ID.

To set up your system to share the overlay colormap with the Window Manager, edit the files SYS$COMMON:[VUE$LIBRARY.SYSTEM]VUE$MWM.COM and SYS$COMMON:[SYSMGR]DECW$MWM.COM. Change the following line in each file:

$ mwm -multiscreen

Edit this line by adding the -Overlay command-line option as follows:

$ mwm -multiscreen "-Overlay"

Note that if you create and install your own colormap, the following problems can result:

• Colors flash on the screen when the colormap is changed.
• Border and banner colors also change when you change the colors of your colormap.

Restrictions

The following restrictions apply when you enable the Window Manager to use overlays:

• The Window Manager supports only single-screen systems and does not function correctly with multiple graphics devices (multihead).
• If you select a Matte Size value other than "None" from the Window Manager options list, the Matte color is not correct; that is, the color does not match the selection and is occasionally transparent.
• If you select "Show feedback when moving or resizing windows" from the Workspace Options menu, the window with the feedback information causes expose events.
• When you move windows by showing the outline of the window, the outline appears to go below the window borders and banners.
• Window borders are occasionally and randomly displayed in clear or black. If this problem occurs, select the restart option from the Workspace menu to restart the Window Manager.
• The ZLXp-E2 and ZLXp-E3 3D graphics accelerators are not currently supported when you run the Window Manager with the -Overlay command-line option.

This chapter contains programmer release notes.

3.1 Programming Release Notes Specific to DECwindows Motif for OpenVMS Software

The release notes in this chapter are cumulative from DECwindows Motif Version 1.0 and still apply to the DECwindows Motif Version 1.2-5 for OpenVMS software.

3.2 DECwindows Motif for OpenVMS Toolkit Versions

V1.2--5

The DECwindows Motif Version 1.2-5 for OpenVMS release is based on the CDE Motif 1.0 Toolkit (OSF/Motif Release 1.2.5) and X11 Release 5.

V1.2--4

The DECwindows Motif Version 1.2-4 for OpenVMS release was based on the CDE Motif 1.0 Toolkit (OSF/Motif Release 1.2.5) and X11 Release 5.

V1.2--3

The DECwindows Motif Version 1.2-3 for OpenVMS release was based on the OSF/Motif Release 1.2.3 Toolkit (with extensions for the Common Desktop Environment (CDE)) and X11 Release 5 (R5).

V1.2

The DECwindows Motif Version 1.2 for OpenVMS release was based on the OSF/Motif Release 1.2.2 Toolkit and MIT X11 Release 5 (R5).

V1.1

The DECwindows Motif Version 1.1 for OpenVMS release was based on the OSF/Motif Release 1.1.3 Toolkit and MIT X11 Release 4 (R4).

V1.0

The DECwindows Motif Version 1.0 for OpenVMS release was based on the OSF/Motif Release 1.1.1 Toolkit and MIT X11 Release 4 (R4).

3.3 Run-Time and Programming Environments

V1.2--4

The following run-time and programming environments are provided with the DECwindows Motif for OpenVMS software:

• Run-time support is provided for the CDE Motif 1.0 Toolkit (OSF/Motif Release 1.2.5), OSF/Motif Release 1.1.3 Toolkit, and the XUI Toolkits.
• Development support is provided for the CDE Motif 1.0 Toolkit only.
  However, you can choose during installation to save the OSF/Motif Release 1.1.3 programming files that existed on your system prior to the DECwindows Motif Version 1.2-4 for OpenVMS product. Refer to the DECwindows Motif Version 1.2--4 for OpenVMS Installation Guide for details about saving the OSF/Motif Release 1.1.3 programming environment.
  • If you install the software using the VMSINSTAL procedure and choose to save these programming files, the files are moved to subdirectories and can be accessed for programming.
  • If you install the software using the POLYCENTER Software Installation utility and if programming support for the OSF/Motif Release 1.1.3 Toolkit is present, then you can choose to save the header files and UIL compiler that were used to develop OSF/Motif Release 1.1.3 applications. If selected, the installation procedure creates a subdirectory called [.DECW$113], and the previous programming files are moved into the new subdirectory.
  
  See the DECwindows Motif Version 1.2--4 for OpenVMS Installation Guide for additional information about saving the Release 1.1.3 programming environment.
• Application development with the DECwindows Motif for OpenVMS product is supported for DEC C++ as well as for updated Motif language bindings for Ada, Pascal, Fortran, and C. Language bindings for Ada are available in the DEC Ada Version 3.0A for OpenVMS (VAX and Alpha) layered products.

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 Version 1.2-4 for OpenVMS, 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.

3.5 DECW$COMPARE_VERSIONS Command File Problem

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.6 OSF/Motif Toolkit Compatibility

V1.2--3

You cannot code and compile an application with DECwindows Motif Versions 1.2 or 1.2-3 include files, transport the resulting object files to a system running DECwindows Motif Version 1.1 software, link the object files against DECwindows Motif Version 1.1, and expect the executable image (.EXE) to run. Differences in structures defined in the .h files cause the offsets to be misaligned and thereby prevent you from creating a meaningful executable.

V1.2

The OSF/Motif Release 1.1.3 and Release 1.2.2 Toolkits, on which the DECwindows Motif Versions 1.1 and 1.2 layered products are based, are not compatible. However, applications built against the OSF/Motif Release 1.1.3 Toolkit will continue to run without modification with DECwindows Motif Version 1.2 for OpenVMS; the OSF/Motif Release 1.1.3 Toolkit shareable libraries will continue to be supplied with the DECwindows Motif Version 1.2 for OpenVMS layered product and will be available to existing DECwindows applications on the system.

Although DECwindows Motif Version 1.1 applications will continue to run without modification with DECwindows Motif Version 1.2 for OpenVMS, it is important to note that only those applications that have been built against the OSF/Motif Release 1.2.2 Toolkit can take advantage of new Version 1.2 features, such as drag-and-drop functionality and tear-off menus.

In most cases, simple applications (for example, applications that do not contain private toolkit routines or user-written widgets) can be recompiled and relinked against the OSF/Motif Release 1.2.2 Toolkit to include the new Version 1.2 features. However, previously unidentified problems in a DECwindows Motif Version 1.1 application might be exposed by relinking against the new OSF/Motif Release 1.2.2 Toolkit, and behavior and widget layout changes in the Release 1.2.2 Toolkit might require other modifications to your application as well.

More complex applications will probably require more substantial modifications with the new DECwindows Motif Version 1.2 for OpenVMS Toolkit to use the macros and functions provided.

If the code generates errors because of references to display structure fields, define the constant XLIB_ILLEGAL_ACCESS for X11 R5 compatible structure access.

For example:

$ CC/DEFINE=XLIB_ILLEGAL_ACCESS DECBURGER.C

3.6.1 _Xm Routines

V1.2

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.

V1.2

Because the OSF/Motif Release 1.2.2 Toolkit and the OSF/Motif Release 1.1.3 Toolkit are not binary compatible, applications must link with one toolkit or the other. Applications based on OSF/Motif Release 1.2.2 can only link against OSF/Motif 1.2.2-based and X11 R5-based shareable libraries. Applications based on OSF/Motif Release 1.1.3 can only link against OSF/Motif 1.1.3-based and X11 R4-based shareable libraries.

To provide both OSF/Motif Release 1.2.2-based and OSF/Motif Release 1.1.3-based shareable libraries, the Release 1.1.3-based libraries have the same file names as in DECwindows Motif Version 1.1, and the Release 1.2.2-based libraries contain a suffix of either "R5" or "12".

Shareable libraries that work with either the OSF/Motif Release 1.1.3 Toolkit or the OSF/Motif Release 1.2.2 Toolkit do not have a suffix. These libraries are as follows:

• CDA$ACCESS.EXE
• DECW$D2DXLIBSHR.EXE
• DECW$XEXTLIBSHR.EXE
• DECW$XLIBSHR.EXE
• XDPS$DPSBINDINGSSSHR.EXE
• XDPS$DPSCLIENTSHR.EXE
• XDPS$DPSLIBSHR.EXE
• XIE$SHRLIB.EXE

Shareable libraries that are linked with Release 5 (R5) of the Xt Toolkit have a suffix of "R5". Libraries based on the XUI Toolkit have no R5 equivalent libraries and should not be included in a linker options file based on X11 R5 or OSF/Motif Release 1.2.2. Table 3-1 lists these file names.

Table 3-1 Names of Shareable Libraries Based on R5

Names of Files Based on R4	Names of Files Based on R5
DECW$DWTLIBSHR.EXE	(None)
DECW$DWTSHR.EXE	(None)
DECW$XMULIBSHR.EXE	DECW$XMULIBSHRR5.EXE
DECW$XTRAPLIBSHR.EXE	DECW$XTRAPLIBSHRR5.EXE
DECW$XTSHR.EXE	DECW$XTLIBSHRR5.EXE

Release 5 does not provide an equivalent file for DECW$DWTLIBSHR.EXE or DECW$DWTSHR.EXE. Applications that are built for Release 5 cannot link against these files.

Shareable libraries that are linked with OSF/Motif Release 1.2.2 have a suffix of "12". They should be linked only with libraries compatible with R5 and OSF/Motif Release 1.2.2. Table 3-2 lists these file names.

Table 3-2 Names of Shareable Libraries Based on OSF/Motif Release 1.2.2

Names of Files Based on Release 1.1.3	Names of Files Based on Release 1.2.2
DDIF$VIEWSHR.EXE	DDIF$VIEWSHR12.EXE
DECW$BKRSHR.EXE	DECW$BKRSHR12.EXE
DECW$DXMLIBSHR.EXE	DECW$DXMLIBSHR12.EXE
DECW$MAILSHR.EXE	DECW$MAILSHR12.EXE
(None)	DECW$MRMLIBSHR12.EXE
DECW$PRINTWGTSHR.EXE	(None)
DECW$TERMINALSHR.EXE	DECW$TERMINALSHR12.EXE
DECW$XMLIBSHR.EXE	DECW$XMLIBSHR12.EXE
DGIT$LIBSHR.EXE	DGIT$LIBSHR12.EXE
IMG$SHRLIB.EXE	IMG$SHRLIB12.EXE
LWK$DXMSHR.EXE	LWK$DXMSHR12.EXE
XNL$SHR.EXE	XNL$SHR12.EXE

There is no DECW$PRINTWGTSHR12.EXE file; the Print Widget is part of the DECW$DXMLIBSHR12.EXE file.

The DECW$MRMLIBSHR12.EXE file is a new image that includes Motif Resource Manager (Mrm) routines that were formerly part of the DECW$XMLIBSHR.EXE file. Any program based on OSF/Motif Release 1.2.2 that calls Mrm routines to access .UID files should link with this library.

For example, a typical linker options file for a program based on OSF/Motif Release 1.1.3 might be as follows:

SYS$SHARE:DECW$XLIBSHR/SHARE SYS$SHARE:DECW$XTSHR/SHARE SYS$SHARE:DECW$DWTLIBSHR/SHARE SYS$SHARE:DECW$XMLIBSHR/SHARE SYS$SHARE:DECW$DXMLIBSHR/SHARE

To link this program with OSF/Motif Release 1.2.2, the linker options file should be changed to:

SYS$SHARE:DECW$XLIBSHR/SHARE SYS$SHARE:DECW$XTLIBSHRR5/SHARE SYS$SHARE:DECW$XMLIBSHR12/SHARE SYS$SHARE:DECW$MRMLIBSHR12/SHARE SYS$SHARE:DECW$DXMLIBSHR12/SHARE

These changes eliminate the reference to the XUI Toolkit (DECW$DWTLIBSHR.EXE) and links with the Motif Resource Manager (DECW$MRMLIBSHR12.EXE).

3.7 Language Bindings

V1.2--3

Fortran, Pascal, C, and C++ language bindings are provided to support software development for the following DECwindows components:

• Xlib (Release 5)
• Xt (Release 5)
• Xm (Release 1.2.3)
• Mrm (Release 1.2.3)
• DXm

V1.2

This release of DECwindows Motif does not include Ada bindings for either the OSF/Motif Release 1.1.3 Toolkit or the OSF/Motif Release 1.2.2 Toolkit. Strongly typed bindings for both toolkits are part of the DEC Ada Version 3.0A language product.

If DECwindows Motif is installed on OpenVMS DECwindows Motif Version 1.1, then the existing OSF/Motif Release 1.1.3 Ada bindings, located in the DECW$INCLUDE directory, are not deleted or moved.

3.8 OSF/Motif Release 1.1.3 Programming Support and XUI

V1.2--3

Restrictions

• Problem:
  You will encounter problems if you save the previous (Release 1.1.3) programming environment and attempt to run an OSF/Motif Release 1.1.3 (Xlib Release 4) program that is created on a DECwindows Motif Version 1.2 or Version 1.2--3 system by running the executable on a DECwindows Motif Version 1.1 target system. That is, if you build an application on a DECwindows Motif Version 1.2 or Version 1.2--3 for OpenVMS system, the image is linked with Xlib Release 5, by default. If you attempt to run that executable on a system where OSF/Motif Release 1.1.3 is installed, the result is an ident mismatch fatal error.
  In addition, the OSF/Motif Release 1.1.3 and the Release 1.2.2 files produce different output; they have different structures and are therefore not compatible. Use the appropriate UIL compiler to produce the correct UID file.
• Resolution:
  1. Rename the DECwindows Motif Version Version 1.1 executable compiler, DECW$UILMOTIF.EXE, to DECW$UILMOTIF113.EXE and keep the file in the SYS$COMMON directory. By doing this, the name of the new Version 1.2--3 compiler, DECW$UILMOTIF.EXE, does not conflict with the previous compiler.
  2. Copy the DECW$XLIBSHR.EXE file (Xlib Release 4) to the SYS$COMMON:[SYSEXE.DECW$113] directory.
     The Xlib Release 5 version of Xlib has the same name; however, a logical name is defined to use the Release 4 version when the programs are linked. The changes in minor ident of DECW$XLIBSHR.EXE between DECwindows Motif Version 1.1 and DECwindows Motif Version 1.2 for OpenVMS caused a loss of backward compatibility with DECwindows Motif Version 1.1 systems.
  3. If you save the previous programming environment during installation, create the following two files and copy them to the SYS$COMMON:[SYSEXE.DECW$113] directory:
     • DECW$UILCOMPILER113.CLD
       This file enables UIL/OSF Motif and UIL/XUI to function for either XUI or OSF/Motif Release 1.1.3 if you select DECW$UILMOTIF113.EXE for OSF/Motif Release 1.1.3 or DECW$UILCOMPILER.EXE for XUI.

     • DECW$DEFINE113_LOGICALS.COM
       This file points to the saved header files, which in turn point to the Xlib Release 4 version of the DECW$XLIBSHR.EXE file.
  4. An application must be run on the same version (or higher) of the operating system as the version where it is linked. For example, an application that is linked on a VMS Version 5.4--3 system must be run on a VMS Version 5.4--3 (or higher) system.
     DECwindows Motif Version 1.1 applications that are compiled for OpenVMS Version 6.1 systems will run only on OpenVMS Version 6.1 systems and not on systems prior to Version 6.1.

V1.2

The X Window and OSF/Motif libraries that are shipped with DECwindows Motif Version 1.2 for OpenVMS software are incompatible with those shipped with previous versions. Run-time compatibility has been preserved, but the programming environment is not compatible.

Programming in the XUI or Motif Release 1.1.3 environment that is provided in previous versions of DECwindows Motif is no longer supported in DECwindows Motif Version 1.2 for OpenVMS. However, the installation procedure gives you the option of saving the programming files that already exist on your system. If you choose to save these programming files, they are moved to subdirectories where you can access them for programming. Specifically, the installation creates a subdirectory called [.DECW$113] in each of the directories listed in Table 3-3 and moves the previous files into the new subdirectory.

For more information about saving the programming files, see the DECwindows Motif Version 1.2 for OpenVMS Installation Guide.

Table 3-3 Directories for Previous XUI or Motif Programming Environment

Directory	Contents	New Location
DECW$INCLUDE	C header files	SYS$SYSROOT:[DECW$INCLUDE.DECW$113]
SYS$SYSTEM	UIL compiler	SYS$SYSROOT:[SYSEXE.DECW$113]
SYS$LIBRARY	Non-C language bindings	SYS$SYSROOT:[SYSLIB.DECW$113]

To program with these files, include the new [.DECW$113] subdirectories in the search path for each of the logical names. For example, perform the following:

• Change the definition of DECW$INCLUDE as follows:

  $ SHOW LOGICAL DECW$INCLUDE "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES) = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]" $ DEFINE/EXECUTIVE/TABLE=DECW$LOGICAL_NAMES DECW$INCLUDE - SYS$SYSROOT:[DECW$INCLUDE.DECW$113], - SYS$SYSROOT:[DECW$INCLUDE], - SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]

Place the new [.DECW$113] subdirectory first in the search list, since many of the files that have been updated for this release have the same name as the files that were moved to the [.DECW$113] subdirectory. Thus, the files in [.DECW$113] are used for software development.

If DECW$INCLUDE is redefined in the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM command procedure, then modify the previous instructions accordingly.