Re: REXEC (RUNRMTCMD) between IBM i systems

[Luis Rodriguez <luisro58@xxxxxxxxx>]

Joe,

The command gets executed on the target machine but (at least in my V5R3
system), the output gets directed to the source machine. Check your source
system spool...

HTH,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Tue, Jan 18, 2011 at 8:33 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>wrote:

> I've noted with interest the discussions here about REXEC, and I did
> some experimenting.  I was able to execute a RUNRMTCMD on one IBM i
> pointing to another using *IP, but it never seems to execute on the
> target machine.  I tried something simple: WRKACTJOB, both OUTPUT(*) and
> OUTPUT(*PRINT).  If I don't have the REXEC server running, the command
> fails on the source machine (as I would expect), but when I start the
> REXEC server the commands completes on the source machine but I never
> see anything on the target machine that I can find. No spooled files, no
> job logs, no entries in QHST.  I look at the various QTRXC jobs on the
> target machine and I don't see anything that even makes it look like
> they are receiving or processing a request.
>
> Am I just trying something that won't work?  It seemed like a simple way
> to execute a command on another machine.
>
> Joe
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.