[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

491.0. "Running a program on another node" by EST::JARGENTATI () Tue Mar 28 1989 16:09

              Hello everyone,

              I have a VAXstation with DECwindows installed on
              it.   There is another, more powerful, machine on
              my cluster that also has DECwindows installed on
              it.  I'd like to run DECwrite on this machine FROM
              my VAXstation.  This is possible, isn't it?  What
              does my system manager have to do to make this
              work?

              Thank you in advance for your input.

              Sincerely,
              John Argentati
              ESTG Design Services
T.RTitleUserPersonal
Name		DateLines
491.1DecWindows User's GuideAKO484::SHEPRONOW what'd I do?Tue Mar 28 1989 17:1923
    1) You will need an account on the other system.
    
    2)	From the customize menu in the session manager, use the security
    option and enter the name of the node and username on the other system,
    much in the way a proxy account is setup.  For Example, if you have an
    account, JONES, on the other node in the network, OTHER::, then allow
    the user OTHER::JONES access from the security function.  (Note: If the
    other system is a cluster, using a cluster alias name, you will need an
    entry for each node in that cluster)
    
    3) Set host to the other node and login into your account.
    
    4) Use the command: $SET DISPLAY/CREATE/NODE=your_wrkstatn
    
    4) Run DECWrite.
    
    5) Observe it displaying and taking input from your Workstation and
    running on the remote system.
    
    
    This is documented in chapter 8 of the VMS Decwindows User's Guide.
491.2DECwrite name policeEPIK::BUEHLERSo much noise. So little signal.Tue Mar 28 1989 23:238
>    4) Run DECWrite.
    
    Thanks very much for helping this DECwrite user out, but we do ask that
    the exact name be used - specifically, DECwrite (no capital 'w').  I
    know this is an annoying nit, but product names are of only one form.
    
John
491.3rathole...AIRPRT::GRIERmjg's holistic computing agencyThu Mar 30 1989 18:105
   Oh, ghod, I feel another ALL-IN-1 coming on...


						-mjg
491.4Variation on the theme36021::LAGROTTAWed May 17 1989 13:1411
I have a slightly different scenario to play out.  Instead of logging into the
client VAX, I submit a remote batch job to the client VAX from my workstation.
In the remote .COM file, I presently hardcode the server node name.  My 
experience with DCL is pretty limited.  How would I be able to obtain the node
name of the server from the batch procedure?  It's probably as simple as using
 one of the lexical functions.  Doing it this way allows me to set up a user's
environment in such a way that they are not aware where the application runs,
just that it's available from a Fileview menu.
Thanks,
Margi LaGrotta