Conference bulova::decw_jan-89_to_nov-90

3617.0. "DECW$DISPLAY not correctly defined for Tektronix XN10?" by GIDDAY::STRAUSS (talking through my binoculars) Thu Nov 08 1990 23:52

    Can anyone help me troubleshoot this problem?
    A customer is trying to start Decwindows on a Tektronix XN10
    x-terminal.  He fires it up using these commands...
    	$ define/nolog decw$dwt_decnet_server 151
    	$ spawn/nowait/input=nl: mcr decw$dwt_decnet
    	$ set display/create/transport=decnet/node=epx001/server=151
    	$ define/nolog sys$error xw.err
    	$ mcr decw$startlogin
    	$ deassign sys$error
    and the first error message he gets is...
    	Display name DECW$DISPLAY is not correctly defined.

    After that, he gets a Session Manager window but isn't able to
    startup FileView or DECterm.
    Decw$sm.log file contains a four messages like this...

    	[Assigned DECnet server number 10 on node EPVAXA]
    	[Remote display is server number 151 on node EPX001 using DECNET
    	transport]
    	X error event received from server:  BadAccess - attempt to access
    	private resource
    	  Failed request major op code 109 (X_ChangeHosts)
    	  Failed request minor op code 0 (if applicable)
    	  ResourceID 0x8006b in failed request (if applicable)
    	  Serial number of failed request 33
    	  Current serial number in output stream 37
    	Session Error: %NONAME-E-NOMSG, Message number 02DB822A

    ...which I suspect are a consequence of the DECW$DISPLAY message.

    I thought decw$display was defined by $ set display, although
    SYS$COMMON:[SYSMGR]DECW$STARTAPPS.COM contains this line...
    	$ define/nolog decw$display 'decw$startup_dev'

    and decw$startup_dev gets its value from...
    	$ decw$startup_dev = F$trnlnm("decw$startup_device")

    I haven't been able to find where DECW$STARTUP_DEVICE is defined in any
    .COM files in sys$startup, sys$manager etc.

    On the other hand, should he be explicitely defining decw$display, and
    if so how?

    The DECnet side of things seems to be ok.

    Thanks in advance for any ideas, pointers etc.

    	leon
    	csc . sydney . australia

    
       	> $ define/nolog decw$dwt_decnet_server 151
    	> $ spawn/nowait/input=nl: mcr decw$dwt_decnet
    	> $ set display/create/transport=decnet/node=epx001/server=151

        I don't think the customer understands the use of decw$dwt_decnet.exe.
        The purpose of this image is to allow terminals using LAT
        transport to be a display server for a node that is not on the
        same LAN as the DECwindows terminal.  Since the Tektronix terminal
        is using DECnet transport, It makes no sense to use the
        decw$dwt_decnet program.  Leave off the /server=151 from the set
        display command and see if this helps.

    						MJC  

Thanks for .1 - unfortunately it didn't fix the problem.
The customer (finally) reported back to me.  He said that removing /server=151
from
$ set display/create/transport=decnet/node=epx001/server=151
didn't make any difference.

He still gets the session manager up and can move windows around etc.
He just can't get any applications to run in them.

The symptoms and decw$sm.log entries are the same as described in .0

Any other ideas?
Thanks in advance

	leon

I got the customer to try running decw$examples:ico, which worked fine.
When he tried decburger, he got some error messages about problems loading
fonts.

It turns out that he loads his fonts on to the Tek from a Sun.
So the problem all along was between the Sun and the Tek and not a Decwindows
problem at all.  He's chasing that up with his Sun support people.

Thanks for the help anyway.

	leon