> From:	SMTP%"groth@pupgg.princeton.edu" 23-JUN-1993 10:42:12.29 To:	EVERHART CC:	 Subj:	Poor Man's X Terminal    X-Newsgroups: comp.os.vms @ From: GROTH@pupgg.princeton.edu (Edward J. Groth   609-258-4361) Subject: Poor Man's X Terminal2 Message-Id: <1993Jun22.174403.22442@Princeton.EDU> Originator: news@nimaster / Sender: news@Princeton.EDU (USENET News System) ' Nntp-Posting-Host: pupggg.princeton.edu # Reply-To: groth@pupgg.princeton.edu 6 Organization: Physics Department, Princeton University# Date: Tue, 22 Jun 1993 17:44:03 GMT 
 Lines: 188 To: Info-VAX@kl.sri.com  X-Gateway-Source-Info: USENET   < There has been some recent discussion in this group on using! VAXstation 2000's as X terminals.   A I've been thinking of doing the same thing and the discussion led > me to believe I would have a hard time getting (and getting to work) the VXT2000 software.   @ There has also been some discussion about allowing access to the? X server when the access hasn't been set by the session manager ? and its security options.  This has proved very helpful in what  follows.  = I'm going to describe how I set up what I call a poor man's X @ terminal.  This is a VAXstation 2000 running vms and decwindows,8 but only the server.  The login box and all other client> functions are running on some other more powerful CPU which is> running DECwindows (but not necessarily a decwindows server, I	 believe.)   > The configurations I've tried this out on are a VS2000 4 planeA system with 10Mbytes, a VS2000 4 plane system with 6Mbytes, and a > VS2000 1 plane system with 6Mbytes as servers and a VAXstationA 4000/90 running the clients.  All are running VMS 5.5-2 and Motif ? 1.1.  They are part of a homogeneous cluster but need not be, I  believe.  A In what follows, I will refer to the server as node XSERV and the  client as node XCLI.  E The steps to get this to work are: (1) Set up an account for a decnet = object; (2) Create the object login procedure; (3) Create the B object; (4) Allow access to the server from the client; (5) Modify9 DECW$PRIVATE_APPS_SETUP.COM; (6) Create a procedure to be   run in place of DECW$STARTLOGIN.  ) 1. Set up an account for a decnet object:   6 Use authorize and create an account with the following specifications:   
 User: PMXTERM & /Owner   ="Poor Man's Xterminal Start" /Account =PMXTERM N /UIC     =[mmm,ggg] (pick a non-system UIC which doesn't conflict with others) /Device  =SYS$COMMON /Direct  =[PMXTERM]   /LGICMD  =PMXTERM_STARTLOGIN.COM@ /Flags   =(Restricted,Diswelcome,Dismail,Disreport,Disreconnect)0 /Password=you pick one but remember it for below /NOPWDEX /NOBATCH /NOLOCAL	 /NODIALUP 	 /NOREMOTE & /Defpriv=(CMKRNL,SYSNAM,TMPMBX,NETMBX)  L All the other UAF parameters can probably be left to defaults (at least they could on my system!).   ' 2. Create the object's login procedure:   5 $ CREATE/DIRECTORY/OWNER=PMXTERM SYS$COMMON:[PMXTERM]   @ and put the following file in it (named PMXTERM_STARTLOGIN.COM):  < $! This procedure is used as a poor man's x terminal startup $!  2 $! We just create a display on the remote node and- $! then run the decwindows startlogin program  $!  ! $! Edward J. Groth  June 19, 1993  $!   $!   $!   $  purge/keep=2 netserver.log K $  set display/create/perm/transport=decnet/node='f$trnlnm("sys$rem_node")' ! $  run sys$system:decw$startlogin O $  open/write pmxtermlink sys$net !this is to let the other end know we're done  $  write pmxtermlink "Done"  $  wait 00:00:05 $  close pmxtermlink	 $  logout     3. Create the Decnet object.  B On the client node, run ncp and define a decnet object as follows:  1 NCP>define object pmxterm number 0 user pmxterm - + password <what you gave to authorize above> 1 NCP>define object pmxterm alias incoming disabled 1 NCP>define object pmxterm alias outgoing disabled I NCP>define object pmxterm file sys$common:[pmxterm]pmxterm_startlogin.com  NCP>set object pmxterm all  . 4. Allow access to the server from the client:  5 Create a file named DECW$SERVER_ACCESS_TRUSTED.DAT in ? SYS$SPECIFIC:[SYSMGR] for node XSERV (and all other nodes which B you intend to be poor man's x terminals).  The file should contain the line  
 DECNET XCLI *    (transport node user) 7 (be sure to substitute your correct node name for XCLI)   1 5. Modify SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM   0 Add the following to decw$private_apps_setup.com   $!  H $! For nodes which are to be "poor man's x terminals", redefine the main $! application. 8 $  pmxtermnodes="XSERV" !Be sure to substitute for XSERV  $  nodename=f$getsyi("NODENAME")A $  if f$locate(nodename,pmxtermnodes) .lt. f$length(pmxtermnodes)  $  then 8 $    decw$mainapp == "@sys$common:[pmxterm]pmxtermstart" $  endif  E If you have more than one node you want to be an X terminal, then use + $  pmxtermnodes="XSERV1/XSERV2/XSERV3" etc.   $ 6. Create the new mainapp procedure.  7 In SYS$COMMON:[PMXTERM], place the following file named  pmxtermstart.com  9 $! This procedure is to be pointed at by decw$mainapps in  $! decw$private_apps_setup.com. 9 $! It is used to fire up a login process on a remote node  $! rather than the local node. $!   $! Edward J. Groth   June, 1993  $!  = $  open pmxtermlink XCLI::"task=pmxterm"	!Substitute for XCLI : $  read pmxtermlink junk	!Wait for the other end to finish $  close pmxtermlink $  exit     C If you've completed all the steps above, then on the server node do   # $ @sys$manager:decw$startup restart   B And you should wind up with node XSERV running only the decwindows: server and node XCLI running the decwindows login process.  > In my case, this makes a painfully slow VS2000s pretty spiffy.  ? Of course, your VS2000 is still running VMS and requires a page @ file somewhere, etc., so it's not quite as nice as having a real5 X terminal - that's why it's a poor man's X terminal!   B Discussion on the net mentioned DECW$SERVER_ACCESS_ALLOWED.DAT and5 DECW$SERVER_ACCESS_TRUSTED.DAT.  I could not find any ; documentation on these files. Both of these seem to specify ; <transport node user> for access to the server.  I did some @ experiments and concluded the following: the access specified by9 ...ALLOWED.DAT is "permanent" and the access specified by < ...TRUSTED.DAT is overwritten by the access specified in the< security options menu of the session manager.  Note that the= access must be specified with a * for the user so that when a ; random USER logs in and the client node tries to connect on @ behalf of USER, access is granted.  Thus, while the login box is? showing, anyone on node XCLI can connect to the server.  If the @ access is specified by ...ALLOWED.DAT, this continues to be true9 even after someone has logged in (BAD).  If the access is ? specified by ...TRUSTED.DAT, then once a user has logged in and ? the session manager is running, access is denied to other users 7 (GOOD).  At least it worked this way in my experiments!     ? If someone has already posted a solution like this, I'm sorry -  I didn't see it.  E If anyone has any suggestions for improvements, I would be interested  in hearing them.  	 					- Ed     H /----------------------------------------------------------------------\H | Edward J. Groth            | Phone: 609-258-4361                     |H | Physics Dept., Jadwin Hall | Fax:   609-258-6853 <- Changed 1-Feb-93 |H | Princeton University       | SPAN/HEPNET:  PUPGG::GROTH=44117::GROTH |H | Princeton, NJ 08544        | Internet:     groth@pupgg.princeton.edu |H \----------------------------------------------------------------------/  