From: CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 21-JUN-1991 19:43:51.53 To: ARISIA::EVERHART CC: Subj: Re: creating terminal windows from a decstation to a vaxstation From: RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP@CRDGW2 To: Everhart@Arisia@MRGATE Received: by crdgw1.ge.com (5.57/GE 1.100) id AA28290; Fri, 21 Jun 91 19:32:52 EDT Received: From UCBVAX.BERKELEY.EDU by CRVAX.SRI.COM with TCP; Fri, 21 JUN 91 04:25:53 PDT Received: by ucbvax.Berkeley.EDU (5.63/1.42) id AA28141; Fri, 21 Jun 91 04:11:08 -0700 Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-vax@kl.sri.com (info-vax@kl.sri.com) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 20 Jun 91 08:44:19 GMT From: agate!spool.mu.edu!sdd.hp.com!uakari.primate.wisc.edu!samsung!nstar!inland!allebrandi@ucbvax.Berkeley.EDU (Tom Allebrandi) Organization: Inland Steel Research Labs; East Chicago, IN Subject: Re: creating terminal windows from a decstation to a vaxstation Message-Id: <976.28606ae3@inland.com> References: <9106191520.AA16992@eunice.ssc.wisc.edu> Sender: info-vax-request@kl.sri.com To: info-vax@kl.sri.com In article <9106191520.AA16992@eunice.ssc.wisc.edu>, wiebusch@SSC.WISC.EDU (Beth Wiebusch) writes: > I can create a xterm or dxterm window on my vaxstation from a remote unix > (ultrix) station. What I would like to know is: Has anyone been able > to use decnet or tcpip to create this type of terminal without having to > log into the unix station first? I can do this on the VMS side by doing > a "type nodename::task" where task is a command procedure which starts up > a decterm window. I would like to do this from the unix side. I have tryed > about the same thing "type nodename"username password"::task" but this doesn't > work. Is there any manuals that I could reference that deal with this? The > task on the unix side has the following lines in it: > setenv DISPLAY nodename::0.0 > dxterm -ls & > > Has this been done? Can it be done between two different operating systems? Yes it can be done. Getting the DECnet task right on the Unix side can be a little tricky. My experience with doing this is with Ultrix/RISC. The first thing to note right out of the box is that the task name is presented in uppercase. This means that the shell script that represents the task must have an all uppercase name. The second thing is to remember to set the execute permission on Ultrix side script. The easiest thing to do is to make the task object known via ncp on the Ultrix side. That way you can name the script anything you want. Here is what our object looks like: # ncp ncp>show object DW_LAUNCH char Object Volatile Characteristics as of Thu Jun 20 08:23:53 CDT 1991 Object = DW_LAUNCH Number = 0 File = /usr/local/dw_launch Type = Sequenced Packet Accept = Immediate ncp> Here is what the object script (/usr/local/dw_launch) looks like: #!/bin/sh # dw_launch # # Launch a DEC/Xwindows client application on behalf of another node. # This is to be invoked as a DECnet object. There will be a one line # message on stdin in the form "application|server". # # "application" is the name of the application to launch. # # "server" is the DEC/Xwindows server node where the output display # is to occur. # input=`cat` application=`echo $input | sed -e "s/\(.*\)\|\(.*\)/\1/"` server=`echo $input | sed -e "s/\(.*\)\|\(.*\)/\2/"` case $application in DECTERM) dxterm -display ${server}::0 -ls &;; FILEVIEW) dxue -display ${server}::0 &;; esac From the VMS side, we do: $ open/write fyle unix::"0=DW_LAUNCH" $ write fyle "DECTERM|VMSNOD" $ close fyle ("unix" is the node name for the unix node, "VMSNOD" is the node name for the VMS node where the display window is to be created.) --- Tom Tom Allebrandi | Mail guru - DECUS UUCP Development Team Inland Steel Research Labs | Chairperson - VMSnet Working Group, DECUS VAX SIG East Chicago, IN | Internet: allebrandi@inland.com 219 399 6306 | UUCP: ...!uunet!inland!allebrandi | DECUServe: allebrandi