Re: SFTP using expect.

Yep, that's what it always looks like.....
I did not suggest the firewall to be causative, but contributory. Then
again each time I've thought that and got on the firewall guys anyway the
problem mysteriously disappears......

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Wed, Feb 15, 2023 at 10:10 AM Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

But really after rereading Gerald's original message, probably expect is
just timing out waiting for the next string. Check your timeout values..

On Wed, Feb 15, 2023 at 9:07 AM Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Consider also checking your firewall settings. Many firewalls will

suspect

nefarious transfers when many small files or one very large one goes
across. It happens so often with the newer firewalls it's getting to be

a

knee jerk reaction.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Wed, Feb 15, 2023 at 9:57 AM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx>
wrote:

we are switching from FTPs to SFTP.
sometimes we have a large number of files to receive.
and the files have very long file names.

we use "MGET *.edi" to perform the receive.

it _appears_ that after about 10 or 12 files, the process dies. The
expect log appears that it just "filled up". if we have less than

that

number
of files, the process works just fine.

does EXPECT have some limit in the size of data it will process?

--

*JACK WOEHR, IBM Champion 2021-2023
<https://www.credly.com/users/jack-woehr/badges>*

*SENIOR IBM i ENGINEER*

303.847.8442
jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx
stay connected
<https://www.linkedin.com/company/absolute-performance-inc./>

<https://www.absolute-performance.com/>
www.absolute-performance.com

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain

confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further

distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and

delete/destroy all copies of this communication immediately.
--
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://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.