|
This would appear to be a bug in the sftp client. I would report it to IBM.
jmmckee wrote:
This agency seems to generate new problems on a regular basis. Just when I thought I had sFTP of data to them automated, I get a new issue.
Yesterday and this morning, their sFTP site was not cooperating. The session returned status code 3 in both cases.
The CL controlling things was plain jane CLP. I changed the type to CLLE and recompiled - in order to utilize MONMSG on a missing parameter.
The job log created has a spool file from the sFTP session with this message in it:
Couldn't get handle: Failure
That message was listed after a PUT command. No other different message are listed. And, that message did not trigger a non-zero return code, thus the CLLE went about doing the tasks as if the PUT had been successful. Logging in with FileZilla confirmed that the PUT did indeed fail.
Any suggestions?
John McKee
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.