As I recall it was either part of Netbase or NFS from Quest that allows you
to work with remote files and programs. It would of course involve
spending money, a good amount of it actually, on a product, but there is an
option.
At 12:28 PM 10/31/2000, Dave Darnell wrote:
>Tom,
>
>question answered (required strictly literal interpretation) but answers to
>your questions in-line:
>
> > -----Original Message-----
> > From: Emerson, Tom # El Monte [mailto:[log in to unmask]]
> > Sent: Tuesday, October 31, 2000 12:16 PM
> > To: [log in to unmask]
> > Subject: Re: run a remote program file locally.
> >
> >
> > Without getting too much into the technical details of what
> > it means to
> > "run" a program on a particular machine, let me ask this:
> >
> > Does your boss want to see the CPU of sytem ALPHA consumed
> > as opposed to
> > the CPU of BRAVO?
>
>Yes.
>
> >
> > Does your boss want the files that are processed by "prog
> > X" to be local
> > to ALPHA as opposed to BRAVO?
> >
>Yes.
>
>
> > I suspect it is the latter -- the former is "impossible"
> > without copying the
> > "executable" in some manner to Alpha (but you knew that... ;)
>
>Yeah I did, but my word wasn't good enough. Plus, there's a lot of 3K lore
>I don't know.
>
>
> > ) Besides,
> > the program on "bravo" may refuse to run on "alpha" if, say,
> > it checks for
> > the HPSUSAN to match some internal value.
>
>Not in this case, it's our commercial software.
>
> >
> > One way to "run" a program on a remote machine yet have it
> > affect files on
> > the local machine is as follows:
> >
> > BRAVO:REMOTE:ALPHA HELLO ME,MYSELF.I
> > BRAVO:FILE IN1=IN1:ALPHA#
> > BRAVO:FILE IN2=IN2:ALPHA#
> > BRAVO:FILE OUT1=OUT1:ALPHA#
> > BRAVO:RUN LOCAL.PROG.NAME
> >
> > Note that you are actually "local" to BRAVO, but all the
> > files affected are
> > located on ALPHA
> >
> > I'm not entirely sure of the syntax, but I also seem to recall a node
> > redirector of "$BACK", which would (should?) make the example
> > look like
> > this:
> >
> > ALPHA:REMOTE:BRAVO
> > BRAVO#HELLO ME,MYSELF.I
> > BRAVO#:FILE IN1=IN1;DEV=$BACK
> > BRAVO#:FILE IN2=IN2;DEV=$BACK
> > BRAVO#:FILE OUT1=OUT1;DEV=$BACK
> > BRAVO#:RUN LOCAL.PROG.NAME
>
>The $back scenario yields the same problem: you cant :run
>program.prog.acct:$back
>
> >
> > Unfortunately, these "solutions" may not work if the program
> > opens the files
> > with the "NO FILE EQUATES" foption (or if the program
> > explicitly issues
> > :FILE commands)
> >
> > > -----Original Message-----
> > > From: Dave Darnell [mailto:[log in to unmask]]
> > > Sent: Tuesday, October 31, 2000 11:06 AM
> > > To: [log in to unmask]
> > > Subject: [HP3000-L] run a remote program file locally.
> > >
> > >
> > > Pardon me, but my boss insists that I post this inquiry.
> > >
> > > Systems Alpha and Bravo are both modern MPE/iX machines with
> > > all the common
> > > components such as Network Services. A program exists on
> > > system Bravo.
> > > Without copying the program to system Alpha, how can we
> > > execute it on system
> > > Alpha?
> > >
> > > Thnx for humoring me.
> > >
> > > -dtd
> > >
> >
Regards,
Shawn Gordon
President
theKompany.com
www.thekompany.com
949-713-3276
|
