Re: Another RUNRMTCMD question

Hi Adam,

I can execute commands Windows like 'move' and 'copy', but the Windows app's import program always completes without errors but also without actually doing anything. I believe the Windows app uses a relative path to access the import file, and that somehow the REXEC environment causes problems with the current directory.

RUNRMTCMD should output a spooled file that shows what happened during the session.

You might consider using the rexec tool from QShell, or the rexec() API, instead of the RUNRMTCMD command.

Personally, I like the rexec tool from QShell, since it reports any output information to stdout. You can easily run that from a CL program and override STDOUT to a PF in QTEMP, then read that PF to see if there are any error messages.

But... anyway... my point is this: The fact that RUNRMTCMD didn't report an error does NOT mean that the command ran successfully. It only means that the command was successfully sent to the Windows PC. Keep in mind that MS-DOS doesn't have *ESCAPE messages or anything like that. If a program fails, it prints an error on the screen, but it doesn't throw any sort of exception that the command interface could pick up on. So it's very difficult to for the iSeries Incoming Remote Command service to detect whether your command succeeded or failed. Instead, it just relays any messages to you, and leaves it up to you to determine whether they're just informational messages or whether they're errors.

Good luck