Re: expect - sometimes it runs sometimes it doesn't....

So you are seeing this too where it does absolutely nothing, no error but no connection?

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 9/8/2016 8:10 AM, Kevin Bucknum wrote:

It happens often enough that in our little send program we use we
account for it. We are redirecting output to a file, and we parse that
file afterwards. If it's completely empty, we delay 30 seconds and try
again. We let that happen 5 times before we completely fail and report
it upstream.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Wednesday, September 07, 2016 9:56 PM
To: Midrange Systems Technical Discussion
Subject: Re: expect - sometimes it runs sometimes it doesn't....

We'll likely convert it to a CL. Currently we're submitting the QSH
'sftp.sh > sftp.log' command directly. It has worked and it has failed.

It has ALSO failed while in QSH. I run it thus:
================================
/sftp.sh
$
================================
Absolutely nothing between the command and the $.

Perhaps the next time though, it WORKS and you get:
================================
/sftp.sh
spawn sftp GrandRapids@mft.********.com
GrandRapids@mft.********.com's password:
WARNING: USE OF THIS SYSTEM IS RESTRICTED TO AUTHORIZED USERS This
computer is the private property of the Company and may be...
<snip>
Connected to mft.********.com...
sftp> ls -l
-rw-rw-rw- 1 user group 324 Sep 7 19:11 Agent_xx.OLD
-rw-rw-rw- 1 user group 0 Sep 7 19:11 Office_xx.OLD
<snip>
sftp> mput *.txt
Uploading agent.txt to /agent.txt
agent.txt 100% 265 0.3KB/s 00:00
Uploading office.txt to /office.txt
office.txt 100% 0 0.0KB/s 00:00
sftp> $
===============================================

So it's a pretty dramatic difference. Either works or NOTHING!

And that's the frustrating part. How do you see what's happening when it
does NOTHING?

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 9/7/2016 7:39 PM, Scott Klement wrote:

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??

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.