×
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.
Scott Klement wrote:
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.
I did know about that, but reading it again made me think of adding a
chdir command to display the current directory, to see if I could
confirm my suspicion.
C:\WINDOWS\system32 seems to be the default current directory for
iSeries Access for Windows Remote Command. I'm not sure if I was
terribly inattentive before or if something changed, but the path is
printed in the spooled output for every command in the .bat script that
I'm running, whether or not the chdir command is in the script.
When I was first trying to get this work (about a month ago), it seemed
that the CD command didn't change the directory properly for the next
command in the .bat script. Now it is working and the process seems to
be working fine.
Thanks everyone for your help,
Adma
This mailing list archive is Copyright 1997-2025 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.
midrange.com
