[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

461.0. "SET DISPLAY Problem" by DELNI::J_QUIGLEY () Wed Mar 22 1989 15:30

    I'm trying to display the Bookreader on a remote node and am getting
    the following error message:
    
    XTOOLKIT ERROR:CAN'T OPEN DISPLAY
    %DWT-F-DWTABORT, xtoolkit fatal error
    
    The procedure I followed to do this was to:
    
    Customize security to allow the remote node to display applications
    on my node.
    
    Log in to the remote node.
    
    Enter the following command:
      $SET DISPLAY/CREATE/NODE=my_node
    
    Run the application:
      $DECW$BOOKREADER
    
    Am I doing something wrong?

T.RTitleUserPersonal
Name
DateLines
461.1Is node defined?OIWS20::BRYSONWed Mar 22 1989 20:0713
Is the my_node defined on the remote machine?

Does your machine have the network object X$X0 defined?

               $ mcr ncp show known objects

Try running DECW$EXAMPLES:ICO (if you have installed the PROG portion of 
DECwindows. Xlib programs may give you more information about the connection
problem.

David

461.2DECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Thu Mar 23 1989 00:3518
    Note that X$X0 should only exist on the server machine, not the client.
    
    Make sure that you have both node and username in the security customize.
    If the client is ultrix and the server VMS, the username is the ultrix
    	user id, not the alphanumeric name.
    As said before, make sure the client's node name is known to the server.
    	Try set host client from the server.
    Make sure the client's node name is the actual system name and not a
    	cluster alias.
    Just to double check, try SHOW DISPLAY on the client, and make sure
    	the node is right and the transport is DECNET.
    
    (Actually, since you talked about SET DISPLAY, I know the client is VMS,
    so ignore the appropriate suggestion above).
    
    Burns
    

461.3How to set x$x0AIAG::SURESHFri Mar 24 1989 09:429
    I also have the same problems as 461.0. I checked whether my machine
   has the network object x$x0 defined. I found out that it wasn't. Now I am
    a novice to VMS/DECNET and I do not know how to set this network object
    x$x0. So can anyone shed light on this ? 

  
  Thanks in advance

461.4ATSE::DAVIDSONFri Mar 24 1989 14:0514
    re: all
    
    I came across this problem and found out the you better have all the
    possible nodes you can be doing the SET DISPLAY/CREATE/NODE=X setup in
    your workstations local NCP database.  Because the decnet connection
    will come across with only the node number because there is no
    associated node name in NCP's database and then nothing in your
    Security settings NODE::XXX match because you didn't enter something
    like 4937::DAVIDSON for access.
    
    
    Sean
    

461.5Problem solved!DELNI::J_QUIGLEYMon Mar 27 1989 14:332
    Thanks for the help.  It was indeed an NCP database problem.

461.6My problem (I think)ASANA::CHERSONTrout fishing in AndoverTue Jun 20 1989 09:547
As a followup to the previous set display problem, I'd like to know the "no 
such device available" message that I get is based on a missing logical or is
an NCP screwup?

Thanks,
David

461.7XUI::VANNOYJake VanNoyTue Jun 20 1989 11:347
>As a followup to the previous set display problem, I'd like to know the "no 
>such device available" message that I get is based on a missing logical or is
>an NCP screwup?

Most likely means you haven't run DECW$STARTUP on the system in question.


461.8yep!ASANA::CHERSONTrout fishing in AndoverTue Jun 20 1989 14:444
re: .7

Absolutely right!