Conference noted::motif

What happens if you

	$ set display/create/transport=local
	$ mcr decw$examples:ico

				-- Bob

    re: .1
    
    Thanks for the reply, Bob.
    
    Sorry I've got to wait for the customer to come back from the Easter
    holiday before I can dial in. Here what happened:
    
    $ set displ/cre/transport=local
    $ mc decw$terminal
    This is the Motif Version of the DECterm controller
    X Toolkit Error: Can't Open display
    %DWT-F-NOMSG, Message number 03AB8204
    %TRACE-F-TRACEBACK, symbolic stack dump follows
     Image Name   Module Name     Routine Name    Line Number  rel PC     
    abs PC
     DECW$XTLIBSH                                           0 0003E2D8   
    002FE2D8
     DECW$XTLIBSH                                           0 0003DECC   
    002FDECC
     DECW$XTLIBSH                                           0 0003E108   
    002FE108
     DECW$XTLIBSH                                           0 0003C8B4   
    002FC8B4
     DECW$XTLIBSH                                           0 00048FCC   
    00308FCC
     DECW$TERMINA                                           0 0002136C   
    0003136C
     DECW$TERMINA                                           0 00022730   
    00032730
                                                            0 85641A50   
    85641A50
    $  run Decw$Examples:Ico
    Cannot open display
    : non-translatable vms error code: 0x144, vms message:
    %system-f-ivdevnam, invalid device name
    
    
    Regards,
    John, CSC/Sydney

Oops, I see that you already posted the ICO output in .0.

Is the DECwindows server process starting at all?  In .0 you said that
there was a "void" DECW$SERVER_0_ERROR.LOG file.  Does this mean that the
file is empty or that it has no error messages but does contain normal
messages?

Please use @sys$update:decw$versions and post the output here, and make
sure there are no decw$*.exe files in sys$specific:[sysexe] or
sys$specific:[syslib].

				-- Bob

Thanks Bob

� Is the DECwindows server process starting at all?

I have to say YES because I remember I had done "@sys$manager:decw$startup
restart" almost every time when I dialled into the customer system.


� In .0 you said that there was a "void" DECW$SERVER_0_ERROR.LOG file.  Does
  this mean that the file is empty or that it has no error messages but does
  contain normal messages?

No I meant it was a "void of" DECW$SERVER_0_ERROR.LOG. There was a
DECW$SERVER_0_ERROR.LOG created at all for the DECterm creation that was done
(either from the failing ICO or CREATE/TERM or DECW$TERMINAL).

I know if there's some messages in the log file it may provide more details
about the problem. Unfortunately, there wasn't a
SYS$manager:DECW$SERVER_0_ERROR.LOG; NOT A SYS$MANAGER:NETSERVER.LOG and not a
SYS$LOGIN:DECW$SM.LOG.

I had once done a "DEFINE DECW$DECTERM)_OUTPUT DECTERM.LOG" but i was still
unable to get hold of any log files.


� Please use @sys$update:decw$versions and post the output here,

This is something I haven't done so far. However, the customer has been out of
reach today. If I can not be able to get hold of the customer today (it's Friday
afternoon in Australia here) I have to get back to you next week.


� make sure there are no decw$*.exe files in sys$specific:[sysexe] or
  sys$specific:[syslib].

I'd checked this one. There wasn't any DECW executables in sys$specific

John

I don't see how the server could be running if there is no
decw$server_0_error.log file.  Please confirm that the DECW$SERVER_0
process is running at the time that you try to start DECterm.

				-- Bob

    OK Bob. I will arrange to dial in the customer system again to make
    sure that DECW$SERVER_0 process is there when starting DECTERM
    
    Will post the result here later
    
    Thanks,
    John

Hi Bob,

Here's the display from:

$ @sys$update:decw$versions
DECwindows ident is                     DW V1.2-3960215
DECwindows server ident is              DW V6.1-940402
DECwindows transport ident is           DW V6.1-940402
DECwindows xlib ident is                DW V1.2-3960215
DECwindows OSF/Motif Toolkit ident is   DW V1.2-3960215
DECwindows apps ident is                DW V1.2-3960215
DECwindows programming ident is         DW V1.2-3960215


And from SHOW SYSTEM, you can see DECW$SERVER_0 has been running:

$ SH SYS
OpenVMS V6.1  on node BRD014   9-APR-1997 09:33:09.34  Uptime  15 21:06:50
  Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages
00000101 SWAPPER         HIB     16        0   0 00:00:07.37         0      0
...........
00000174 DECW$SERVER_0   HIB      8     1260   0 00:00:05.38      1793     89
0000017B DECW$SESSION    LEF      6      439   0 00:01:47.59      2421     29


Then, trying to create DECTERM:

$ set displ/cre/transport=local
$ mc decw$terminal
This is the Motif Version of the DECterm controller
 fatal error: DECterm connection to server lost
DECterm exiting.
%NONAME-W-NOMSG, Message number 00000000
$  run Decw$Examples:Ico
XIO:  unable to open connection _WSA21:
      after 0 requests (0 known processed) with 0 events remaining.
Cannot open display
: non-translatable vms error code: 0x2DBA002, vms message:
%decw-e-cnxabort, connection aborted


This time I found error messages in SYS$SYSROOT:[SYSMGR]DECW$SERVER_0_ERROR.LOG
(maybe I didn't read thru this log file thoroughly last time :-(  SORRY ):

$ ty/p SYS$SYSROOT:[SYSMGR]DECW$SERVER_0_ERROR.LOG;145
24-MAR-1997 12:49:20.6 Hello, this is the X server
This is the DECwindows X11 display server for OpenVMS AXP V6.1-940402
.............
 9-APR-1997 09:37:17.6 Invalid access from transport: LOCAL
                                                node: 0
                                                user: FIELD
 9-APR-1997 09:37:34.4 Invalid access from transport: LOCAL
                                                node: 0
                                                user: FIELD

and FIELD was the Username I was working from.

Can these help?

Thanks,
John

Did the user log into DECwindows as FIELD?  If not you'll need to add
LOCAL 0 FIELD to the access list in the Session Manager's Security Options
dialog box.

				-- Bob

Bob,

In fact I logged into DECwindows as FIELD.

The Security Options in Session Manager was one of the first few items in the
troubleshooting list and it has been "played" around with all kinds of wildcard
settings.

John

I can't explain what's happening.  I suggest logging it as an IPMT.

				-- Bob