=;The OpenVMS Frequently Asked Questions (FAQ)D

The OpenVMS Frequently Asked Questions (FAQ)



 r \ ^  
PreviousContentsIndex




>

Chapter 11
DECwindows


A

If you are searching for something here, please (consider using the text-format FAQ.

z

11.1 How do I let someone else display something on my workstation?



FOn a workstation, you will want to use the "Customize" menu Eof the session manager utility and select "Security". When Dthe pop-up box appears, you can select the host node, username, and Gtranport that will allow you to launch an application that targets the workstation display.

DIf this does not provide you with access to the display, You need a checklist of sorts:

m

11.2 How do I create a display on another workstation?



HTo create a display from an OpenVMS host to a remote X Windows display, &use one of the following DCL commands:

 

"
A$ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node 7$ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=remote_node :$ SET DISPLAY /CREATE /TRANSPORT=DECnet /NODE=remote_node 9$ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=remote_node 




BNote that LAT is typically used only for the VXT series X Windows Fterminals, but it can also be used from OpenVMS to OpenVMS systems on Gvarious OpenVMS releases, such as on OpenVMS Alpha V6.1 and later. For ddetails on configuring the TCP/IP transport, see Section 11.14.

?If you are interested in X Windows terminals and have an older FVAXstation system around, please see the EWS package on Freeware V5.0.z

11.3 How can I get the information from SHOW DISPLAY into a symbol?



AUse the undocumented SHOW DISPLAY/SYMBOL, and then reference the Dsymbols DECW$DISPLAY_NODE, DECW$DISPLAY_SCREEN, DECW$DISPLAY_SERVER and/or DECW$DISPLAY_TRANSPORT.

EAn example of calling the underlying (and also undocumented) sys$qio &programming interface for the WSDRIVER(WSAn:) is available at:

 

"
1- http://www.hp.com/go/openvms/freeware/  


FLook in the Freeware V4.0 directory /srh_examples/DECUS_UNDOC_CLINIC/.d

11.4 How do I get a log of a DECterm session?



HIf you are working from a DECwindows DECterm terminal emulator, you can Guse the AutoPrint feature. Choose the "Printer..." menu item Gfrom the "Options" menu, set the printing destination to the Hname of the file you want, and set "Auto Print Mode". You are now free to continue.

GIt should be noted that all of the characters and escape sequences are Gcaptured, but if you display the resulting log file on a DECterm, then 3you will see exactly what was originally displayed.

GYou can also use the "Print Screen" screen capture available Hin the DECwindows session manager menus, if you simply wish to snapshot .a particular portion of the X Windows display.

If you are using the FreewareBVTstar terminal emulator package, you will find a similar logging $mechanism is available in the menus.a

11.5 Why is DECwindows Motif not starting?



GFirst check to see if there is a graphics device, usually a G* device. H(eg: On a DEC 2000 model 300, use the command SHOW DEVICE GQ) If you do not find a graphics device:



)If there is a G* graphics device present:

g

11.6 How do I set the title on a DECterm window?



/If you are creating a new DECterm window, check

 

"
+$ HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES 




?If you want to change the title of an existing window, use the Gfollowing control sequences, where [esc] is the ANSI escape Gcode, value decimal 27, and "text label" is what you want to display:

>To set the DECterm title, send the escape character, then the Echaracters "]21;", then the text label string, and then an 3escape character followed by a backslash character.

FTo set the icon label, send the escape character, then the characters A"]2L;", then the icon label string, and then an escape ,character followed by a backslash character.

HTo set both the DECterm title and icon to the full device name, you can use the following DCL commands:

 

"
$  esc[0,7] = 27 F$  fulldevnam = F$Edit(F$GetDVI("TT","FULLDEVNAM"),"UPCASE,COLLAPSE") 9$  write sys$output esc+ "]21;" + fulldevnam + esc + "\" 9$  write sys$output esc+ "]2L;" + fulldevnam + esc + "\" 




GYou can also change the title and the icon using the Options-Window... menu.

oAlso see Section 12.1 and Section 8.13.w

11.7 How do I customize DECwindows, including the login screen?



DTo customize various DECwindows Motif characteristics including the Fdefaults used by the SET DISPLAY command, the DECwindows login screen Gbackground logo used (the default is the DIGITAL, Compaq, or HP logo), various keymaps (also see Section 11.7.2 and Section 11.7.1), the BFileView defaults, session manager defaults, the DECwindows login >processing, DECwindows log file processing, and various other ,DECwindows attributes, see the example file:

 

"
/$ SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE 




DThis example template file is typically copied over to the filename DSYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM and then modified to meet site-specific requirements.

GAdditionally, various X tools such as xsetroot, bitmap and xrdb---some Gthese can be useful in customizing the appearance of an application or Gof the DECwindows Motif display---are provided in the DECW$UTILS: area.

EWhen using DECwindows V1.2-4 and later on OpenVMS Alpha, the default Edesktop is the Common Desktop Environment (CDE). You can select your Hpreferred desktop (CDE or DECwindows Motif) when logging in, or you can Hchange the default to the DECwindows Motif desktop using the DCL symbol Cdecw$start_new_desktop in the DECwindows private application setup Hcommand procedure. See SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE for ?further details, and how to create DECW$PRIVATE_APPS_SETUP.COM.

GNote that with DECwindows CDE, the root window is no longer visible by -default. The root window is hidden behind theF"backdrop" window of the current CDE workspace. To make the Hroot window visible, use the CDE style manager selection "backdrop Gnone", and use information such as that in the OpenVMS FAQ to set the root window.

FTo add a new backdrop to the DECwindows CDE environment, the backdrop ?must first be in or be converted into X11 pixmap format. (This 5conversion is often possible using tools such as xv.):Then (if necessary) create the default backdrop directory DSYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS]. Place the X11 pixmap file Gcontaining the desired image into the backdrops directory, ensure that Git has a filename extension of .PM. (The xv default filename extension Efor the X11 pixmap file is .XPM, while CDE expects only to see files Gwith .PM.) Now invoke the CDE style manager and select a new backdrop. BYou will find your image will be placed at the end of the list of backdrops available.

HIf you require a message be included on the initial display---where the Gstart session display and the logo appears---you can use either of the following approaches:



AThe login logo is stored as an XPM bitmap image in the text file HSYS$SYSROOT:[SYSCOMMON.CDE$DEFAULTS.SYSTEM.APPCONFIG.ICONS.C]DECDTLOGO.PM,) and it can be changed. Copy the file to J SYS$SYSROOT:[SYSCOMMON.CDE$DEFAULTS.USER.APPCONFIG.ICONS.C]DECDTLOGO.PM, D as DECwindows upgrades can replace the system version of this file.

GOn DECwindows V1.3-1 and later (and possibly on V1.3), both DECwindows ?CDE and DECwindows Motif displays use this logo file. On older Freleases, only the DECwindows CDE displays used this logo file, while Bthe logo used for the Motif login display was hard-coded into the Fpackage and the only available override is the DECW$LOGINLOGO command 9procedure mechanism within the customized, site-specific !DECW$PRIVATE_APPS_SETUP.COM file.

GLook at the contents of the DECDTLOGO.PM file and at other *.XPM files !and tools for additional details.R

11.7.1 How do I customize DECwindows keymapping?



BVarious keymaps can be implemented on OpenVMS and other X Windows @systems, allowing the implementation of a Dvorak-style or other @alternate keymappings. For details, see the available X Windows Cdocumentation (this is the documentation associated with X Windows Ditself, and not the product documentation for the OpenVMS operating Dsystem nor for the DECwindows X Windows implementation) and see the EDECwindows *.DECW$KEYMAP (text-format) files found in the DECwindows DECW$KEYMAP: directory.

YFor other keymapping information, see Section 11.7.2._

11.7.2 Why does the DELETE key delete forward instead of backward?



ASee the SET TERMINAL/BACKSPACE command on OpenVMS V8.2 and later.

EThis behaviour involves the Motif virtual key bindings. When a Motif Bapplication starts, it looks at the vendor string returned in the Edisplay connection information and attempts to match the string to a table of virtual bindings.

GYou can override the default bindings in your decw$xdefaults.dat file. AHere is the entry you would make to get the default VMS bindings.

 

"
*defaultVirtualBindings:\" osfCancel :  [F11] \n\! osfLeft :  [Left] \n\ osfUp  :  [Up] \n\# osfRight :  [Right] \n\! osfDown :  [Down] \n\( osfEndLine :Alt  [Right] \n\) osfBeginLine :Alt  [Left] \n\$ osfPageUp :  [Prior] \n\% osfPageDown :  [Next] \n\* osfDelete :Shift  [Delete] \n\& osfUndo :Alt  [Delete] \n\( osfBackSpace :  [Delete] \n\' osfAddMode :Shift  [F8] \n\! osfHelp :  [Help] \n\ osfMenu :  [F4] \n\# osfMenuBar :  [F10] \n\% osfSelect :  [Select] \n\) osfActivate :  [KP]_Enter \n\) osfCopy :Shift  [DRemove] \n\$ osfCut  :  [DRemove] \n\  osfPaste :  [Insert]




To merge:

 

"
 $ xrdb :== $decw$utils:xrdb.exe ($ xrdb -nocpp -merge decw$xdefaults.dat 




EAlso note that the DECW$UTILS:DECW$DEFINE_UTILS.COM procedure can be -used to establish the xrdb and other symbols.

@Also see the DECxterm directory of Freeware V5.0 for details on 2connecting to OpenVMS from various UNIX platforms.

^For other keymapping information, see Section 11.7.1.i

11.8 Why doesn't XtAppAddInput() work on OpenVMS?



GYes, XtAppAddInput() does work on OpenVMS. The MIT definition of the X BWindows call XtAppAddInput() includes platform-specific arguments.

GOn platforms where C is the typically the primary programming language Ffor the platform, the file descriptor mask is one of the arguments to the XtAppAddInput() call.

DOn OpenVMS, the platform-specific arguments to this call include an Hevent flag and an IOSB, as these are the traditional OpenVMS constructs Hused to synchronize the completion of asynchronous operations. While it Fwould be easier to port non-OpenVMS C code that calls XtAppAddInput() Fover to OpenVMS if the arguments included the C file descriptor, this Ewould make the call unusable from other OpenVMS languages, and would Emake it extremely difficult to use OpenVMS features such as ASTs and sys$qio calls.

FOne restriction on the event flag: the event flag chosen must be from Cevent flag cluster zero. When using the traditional lib$get_ef and lib$free_efHcalls to allocate and deallocate event flags, you must first explicitly Ccall lib$free_ef to free up some event flags in event flag cluster Fzero. Please see the event flag documentation for specific details on Dthese calls and for specific event flags that can be freed in event flag cluster zero.

FHere is some example code that covers calling this routine on OpenVMS:

 

"
#    m->InputID = XtAppAddInput(         m->AppCtx,         m->InputEF,         m->InputIosb,         the_callback, 1 ); "    if ( !((int) m->InputID )) 
        {         XtAppErrorMsg(             m->AppCtx,             "invalidDevice",             "XtAppAddInput",             "XtToolkitError", #            "Can't Access Device",             (String *) NULL, !            (Cardinal *) NULL );         ... 


w

11.9 Why do the keyboard arrow keys move the DECwindows cursor?



ECongratulations, you have just stumbled into "dead rodent" Gmode. This DECwindows environment---where the keyboard arrow keys move Athe mouse cursor and where the [SELECT], [PREV], and [NEXT] keys Gemulate the three mouse buttons---allows rudimentary system operations 'when the mouse is among the casualties.

DTo enter or exit "dead rodent" mode, enter the following: [CTRL/SHIFT/F3]h

11.10 Why does half my DECwindows display blank?



GThis is likely a result of receiving an OPCOM or other console message Hon a system that shares the system console with the DECwindows graphics workstation display.

4You can toggle off the console display window using =[CTRL/F2] and you can enable a serial console per lSection 14.3.6 or Section 14.3.3.3.

FAlso see the console message window application available with recent GDECwindows versions---DECwindows versions V1.2-3 and later will enable Hthis window by default. For details on this console message window, see %the DECW$CONSOLE_SELECTION option in -SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE.

>On older releases, you can disable output using the following:

 

"
+$ SET TERMINAL/PERMANENT/NOBROADCAST OPA0:  $ DEFINE/USER SYS$COMMAND OPA0: $ REPLY/DISABLE 




Also see Section 14.3.3.2, Section 14.17, and Also see Section 8.4,




 r Y \ ^  
PreviousNextContentsIndex