× 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.



Sorry, I wasn't clear in my original post. The DIR command was only used
as an initial test and it was run (and did create a spoolfile) as
expected. But the directory/folder it listed was c:\Windows\System32.

The program that I'm try to run exists in another folder and requires the
working directory to be that folder. I have created a batch file which
issues as CD to the correct working folder and then calls the program.
This also works successfully but my boss has asked me to eliminate the
batch file if possible.

So what I'm asking is if when the RUNRMTCMD runs if the working directory
can be set so the batch file (which sets the working directory) can be
eliminated.

I hope this is clear and sorry for the earlier confusion.

Rob
On 2013-09-27 2:54 PM, Dan Kimmel wrote:

When you're using RUNRMTCMD, you generally don't want to pipe output to a local file as you have here, Rob. Instead let the dir command write to stdout as usual. The REXEC service will stream the output back to the RUNRMTCMD which will then put the output in a spool file on the IBMi.


-----Original Message-----
From: [1]midrange-l-bounces@xxxxxxxxxxxx [[2]mailto:midrange-l-
[3]bounces@xxxxxxxxxxxx] On Behalf Of [4]rob@xxxxxxxxx
Sent: Friday, September 27, 2013 1:46 PM
To: Midrange Systems Technical Discussion
Subject: Re: Help setting up RUNRMTCMD...

Try figuring it out just like I did.
Go to your Windows command prompt.
Type in help and hit enter.
Lots of commands, right?
Now try: help start
for example
start /d \users dir
will switch to the \users directory and run the command dir
Now I couldn't get
start /d \users dir >dirout.txt
like I expected. It created that file back in the starting directory, and
it only had zero bytes


Rob Berendt
--

References

Visible links
1. mailto:midrange-l-bounces@xxxxxxxxxxxx
2. mailto:midrange-l
3. mailto:bounces@xxxxxxxxxxxx
4. mailto:rob@xxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.