Re: RUN process /ON=node
- From: Ryan Moore <rmoore@xxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Oct 2006 16:14:56 GMT
The biggest problem I can see here is that there won't be an X-Windows display defined on the process that gets created on the other node. Somehow a Xwindows display device must get created and the DECW$DISPLAY logical must be set in that process. Merely running an executable isn't going to do that.
If you want to start an Xwindows program on another node and display it on your node, I would do it with a command procedure.
$! STARTMOZ.COM
$ set display/create/node=xxxx/trans=yyyy
$ run APPL_ALPHA:[MOSAIC40]MOSAIC.EXE
Then:
run/proc=mosaic/on=bike/input=startmoz.com sys$system:loginout
or something like that. I don't know if the /input qualifier works when starting a process on a remote node.
On Wed, 18 Oct 2006, JF Mezei wrote:
HELP RUN PROCESS /ON=node indicates that one can actually start a.
process running on a different node.
So, I decided to try this at home.
From my VAX at 7.3, (node VELO) I issued:
$RUN/proc=MOSAIC/ON=BIKE APPL_ALPHA:[MOSAIC40]MOSAIC.EXE
I get a created process ID that has the BIKE digits at the start.
But nothing seems to happen. BIKE is an ALPHA, but has a common SYSUAF
with VELO.
- Follow-Ups:
- Re: RUN process /ON=node
- From: JF Mezei
- Re: RUN process /ON=node
- References:
- RUN process /ON=node
- From: JF Mezei
- RUN process /ON=node
- Prev by Date: RE: How former HP support staff needs to form a new US support center!
- Next by Date: Re: Alpha serial numbers
- Previous by thread: Re: RUN process /ON=node
- Next by thread: Re: RUN process /ON=node
- Index(es):