Conference bulova::decw_jan-89_to_nov-90

791.0. "Inexplicable errors preventing client-server connection" by 43372::BARKER (Jeremy Barker - NAC Europe - REO2-G/J2) Tue May 16 1989 20:46

I have wasted a great deal of time trying to get a client-server connection
to work - with zero success.

I am SET HOST 0 from a DECterm window (like the session it is running
under SYSTEM) to account BARKER.  0::BARKER and nodename::BARKER are both
authorized users in the SYSTEM session.

There should be no global pages problem - there were over 10000 unused global
pages free when I tried the commands shown below.

	$ set display/create/transport=decnet
	$ notes/decwindows
	%XLIB-F-IOERROR, xlib io error
	$ set display/nopermanent
	$ set display/create/trans=local
	$ notes/decwindows
	X Toolkit Error: Can't Open display
	%DWT-F-DWTABORT, xtoolkit fatal error
	$ set display/nopermanent

What I would like to know is how I can *easily* determine the cause of the
failures to set up the connection.  Frankly the error messages are as near
to 100% useless as is acheivable and certainly don't meet my standards for
production software.  Looking in the supplied documentation doesn't help at
all - there's absolutely nothing there to help deduce the cause of the
problems.

If anyone can genuinely help an account on the system can be arranged so that
they can poke about to see how things are set up.

Jeremy Barker
NAC Diagnostic Engineering

    Try the following:
    
    SET DISPLAY/CREATE/NODE=0/TRANS=LOCAL
    
    

I tried explicitly setting the /NODE, which actually made things work.

However, according to the VMS Version 5.1 New Features Manual, which documents
the SET DISPLAY command, it shouldn't be necessary as the /NODE qualifier is
sensibly defaulted.  It states:

	/NODE=workstation

	Defines the node to be associated with this display device.  When
	/CREATE is specified, NODE defaults to SYS$REM_NODE if defined,
	otherwise to SYS$NODE.  This behavior allows the SET DISPLAY/CREATE
	command to be used whether you are logged in to the workstation
	locally, or are logged into a remote system after having entered
	the SET HOST command from the workstation.


I still do not like the paucity and unhelpfulness of the error messages.

jb

    
    An aside:  if you're using SDC DECwindows, that 'set disply/noperm'
    command probably destroyed your process logical name table.  Fixed in
    next release.
    
    Try this again and after the first command, issue a 'show display'
    command and see if the result makes sense.
    
    						m