× 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.

I think the only real way is to query the (error) output of the sftp command ...

Did you consider to forward the sftp (QSH command) errors to an IFS-file? Just add "2> /ifs/path/errors.txt" to the command in PASE.
Or you can forward the QSH output to a file. Use Envvar QIBM_QSH_CMD_OUTPUT (https://www.ibm.com/docs/en/i/7.4?topic=qshell-running-commands-from-cl)
Or you write a PASE shell script that handles your sftp and all the errors... (https://www.ibm.com/docs/en/i/7.4?topic=qshell-pdf-file)



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Alan Shore via MIDRANGE-L
Sent: Samstag, 30. April 2022 18:36
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Alan Shore <ashore@xxxxxxxx>
Subject: Checking for sftp errors

Hi everyone
Before I forget, we are on V7r3
I have created a CLLE program using sftp to transfer files from an external system, into the iSeries This works on our development system This has now been transferred/promoted into our production system, but it is reporting that there are errors Looking at the log - the only thing that I can see is that (at this moment) there are no files to transfer. For the next month or so - that is possible The program creates a script (using mget), and upon execution of that script checks for error in the following way
/* perform sftp */

I realize that using QSH0000 is ALL encompassing, so my question is - does anyone have a "better" way of capturing sftp errors

Alan Shore
Solutions Architect
IT Supply Chain Execution


60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx

'If you're going through hell, keep going.'
Winston Churchill

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://urldefense.com/v3/__https://lists.midrange.com/mailman/listinfo/midrange-l__;!!CqVFughQ-RE!gpAlaMfKjJHxs5_RWUiafJI2Wa4vKF9jCu5EBFRPDu7L0U-_FqeL6Hv2gjjtkDR6FyVKA2-xoIFt7B_JPQsgITOYkZwVSUk$
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://urldefense.com/v3/__https://archive.midrange.com/midrange-l__;!!CqVFughQ-RE!gpAlaMfKjJHxs5_RWUiafJI2Wa4vKF9jCu5EBFRPDu7L0U-_FqeL6Hv2gjjtkDR6FyVKA2-xoIFt7B_JPQsgITOYEYQzYdI$ .

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://urldefense.com/v3/__https://amazon.midrange.com__;!!CqVFughQ-RE!gpAlaMfKjJHxs5_RWUiafJI2Wa4vKF9jCu5EBFRPDu7L0U-_FqeL6Hv2gjjtkDR6FyVKA2-xoIFt7B_JPQsgITOYgJK5PkA$

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 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.