A From:	SMTP%"RELAY-INFO-VAX@CRVAX.SRI.COM" 28-JUL-1993 13:39:21.65  To:	EVERHART CC:	! Subj:	Re: DECwindow-Motif Display    X-Newsgroups: comp.os.vms ) From: jsue@ncsa.uiuc.edu (Jeffrey L. Sue) $ Subject: Re: DECwindow-Motif Display# Date: Tue, 27 Jul 1993 15:44:34 GMT 1 Message-Id: <1993Jul27.154434.1281@ncsa.uiuc.edu> 1 Sender: usenet@ux3.cso.uiuc.edu (Net Noise owner) ) Keywords: DECwindows Motif Server Display $ Originator: jsue@space.ncsa.uiuc.edu& Organization: The Dow Chemical Company	 Lines: 59  To: Info-VAX@kl.sri.com  X-Gateway-Source-Info: USENET   P In article <230vqr$g3e@urmel.informatik.rwth-aachen.de> weikl@ilt.fhg.de writes: >  > On node1 do a  >  > $ set host node2 >  > On node2 then a  > ! > $ set display/create/node=node1  > $ create/terminal/detach > J > I want a means to get the DECW$DISPLAY_NODE on the now created terminal. > $ show display says:/ > %SYSTEM-W-NOSUCHDEV, no such device available 6 > -SHOW-W-OPENIN, error opening DECW$DISPLAY as input. >  > Any suggestions? > 
 > -- Bruno  F Bruno, this sound like the problem I ran into when I upgraded to Motif 1.1 .   C DEC seems to have an on-again-off-again thing with the DECW$TE_xxxx H process, and the WSA device it uses.  In one version, I had this problemA you describe, then Motif 1.0 (or a CSC patch?) fixed it, and then  Motif 1.1 screwed it up again.  E The upshot that I've found is that the DECW$TE_xxxx process no longer F assigns a channel to the WSA device.  Thus, if the process that issuedD the SET DISPLAY/CREATE command logs-out, your interactive process no0 longer has any WSA device for directing x-stuff.  D In my case, I used a DECnet object to do the SET DISPLAY/CREATE, andC the CREATE/TERM/DETACH commands.  This process typically dies after > x minutes (default is 2 minutes, I think, and is controlled byB NETSERVER$TIMEOUT).  I would check my DECW$DISPLAY device promptlyC after login, and it would be there fine, but later when I wanted to > use it it would be gone.  This took quite a bit of thought andB work examining the entire process before I tied it to the deletion of the network process.   G My solution was to add the following line very early in the SYLOGIN.COM 
 procedure:  - $ IF F$GETDVI("DECW$DISPLAY","EXISTS") THEN - = 	OPEN/READ/WRITE/SHARE=WRITE DECW$mumble_DISPLAY DECW$DISPLAY   G Doing this assigns a channel to the WSA device so that when the network > process finally gets deleted, the WSA device won't go with it.  7 This might be the same problem that you are describing.        --   -----  Jeff Sue    F  - All opinions are mine -       (and you can't have any, nya nya nya)  