Re: Capturing expect session

Quoting Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>:

John McKee wrote:

My most recent LONG telephone call gave me more information. Not sure how
useful. I enabled both options to get as much info as possible. The script
clearly recognizes the password: request - and sends it. But, their system
says password is invalid.

I'm missing something. Didn't you say, earlier, that it was failing
when waiting for the sftp> prompt after the 2nd transfer? If that's
the case, doesn't that mean tht the password had already worked?

I removed the second file, thinking that it might be contributing to the issue. So, after the only put, I wait for sftp> and send quit.

With the second put removed, there are now four expects. Each has a separate
return code: 2, 3, 4, 5. Yet first invocation returns 00006 and second returns
00010 - which makes no sense to me. I was told that their end shows me not
sending the password. Since receiver is Windows, last night I experimented
with changing all \n to \r\n. Made no difference. Still got 00006 and 00010
for return codes. Only thing I can think is that I am converting the return
code incorrectly. But, since the same expect script is used a second time, it
seems that the second session is somehow picking up on the first session. The
original code had the return code output from %BIN being used in an IF. I
attempted to use that in a CHGVAR - purpose was to give a text message for the
error message. The thought was that it was "better" to extract the return code
once instead of having multiple %BIN calls. But, in light of 00006 an 00010, I
am going back to using %BIN directly in the IF instead of attempting to assign
to a variable. I should know if that makes any difference shortly after I get
to work.

John McKee