× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Fri, 2008-09-12 at 11:25 -0500, Scott Klement wrote:
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.

In the past, I made a PC application write a "completed successfully"
message to stdout, and I created a 400 command to assert that a spool
file contained a particular string. With a little glue, I had a "run
successful particular remote command" command <grin />. For general
use, you would want the caller to specify just the command to run on the
remote system.

I can see value in generalizing this, but I also see difficulties. It
is by no means clear that the value outweighs the difficulties.
Thoughts, anyone?

Cheers,
Terry.


Good luck


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.