|
Larry,
I would not recommend using a redirect like > because that only
redirects "standard output" (stdout) which is where normal output
messages are written -- it does not log "standard error" (stderr)
which is where error messages are written.
Assuming you are running this from a CL program, I would use the
QIBM_QSH_CMD_OUTPUT variable to specify a file that output is written to.
Unfortunately a description like "does absolutely nothing" doesn't
give us much to go by.
-SK
On 9/7/2016 2:58 PM, DrFranken wrote:
I am utilizing expect on several different servers. On one of them we
need to sftp two small files up to a service periodically through the
day. When I run the shell script in QSH it will run perfectly. Then I
run it again and it does absolutely nothing. It may be many minutes
before it will run again. Signing off and back on doesn't
consistently fix it either. When submitted to batch it's the same, it
may run and may not.
I am redirecting standard output to a log file (> 'output.log') and
when it runs correctly everything is in it. When it does not run the
file is correctly time stamped but is empty (0 bytes). Even when it's
not logging it may fail, in that case if it's interactive QSH simply
returns to the '$' prompt.
IBM i 7.1 with reasonably current PTFs and the latest version of
expect from ScottKlement.com.
Thoughts??
As an Amazon Associate we earn from qualifying purchases.
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.