Greetings, currently, no RDi has not claimed support for Windows 10.
Just a matter of timing rather then issues of lack of wanting it to work
there. RDi 9.5 and the Win10 release just did not line up. Currently,
none of the Rational based IDE (RAD for example) have claimed support yet.
Some time early next year we will complete our testing and be able to
claim support. Stay tuned.
Tim
Tim Rowe, timmr@xxxxxxxxxx
Business Architect Application Development & Systems Management for IBM i
IBM i Development Lab, Rochester, MN
(507) 253-6191 (Tie) 553-6191
http://www-03.ibm.com/systems/power/software/i/are/index.html
----- Original message -----
From: midrange-l-request@xxxxxxxxxxxx
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Cc:
Subject: MIDRANGE-L Digest, Vol 14, Issue 1656
Date: Tue, Nov 24, 2015 4:29 PM
Send MIDRANGE-L mailing list submissions to
midrange-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
[1]
http://lists.midrange.com/mailman/listinfo/midrange-l
or, via email, send a message with subject or body 'help' to
midrange-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
midrange-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MIDRANGE-L digest..."
*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.
Today's Topics:
1. RE: Will RDi run on Win 10 ? (Justin Taylor)
2. Re: New S814...which port for Lan Console? (rob@xxxxxxxxx)
3. RE: Will RDi run on Win 10 ? (Cyndi Bradberry)
4. Looking for link for all Power8 / EXP24S disk options
(Steinmetz, Paul)
5. IBM i Access Client Solutions: SQL Scripts & Visual Explain?
(Mike Jones)
6. New System - TODO's (Charles Wilt)
7. Re: IBM i Access Client Solutions: SQL Scripts & Visual
Explain? (Vernon Hamberg)
8. RE: New System - TODO's (Steinmetz, Paul)
9. RE: New System - TODO's (Jerry Adams)
10. Re: SFTP client Expect 5.43 via PASE, maximum times allowed
depending on remote OS. (Jerry Draper)
----------------------------------------------------------------------
message: 1
date: Tue, 24 Nov 2015 14:37:35 -0600
from: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
subject: RE: Will RDi run on Win 10 ?
IMO, iACS + iNav. A match made in heaven.
-----Original Message-----
From: DrFranken [[2]mailto:midrange@xxxxxxxxxxxx]
Sent: Tuesday, November 24, 2015 1:54 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Will RDi run on Win 10 ?
+1 on that without reservation.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 11/24/2015 2:24 PM, rob@xxxxxxxxx wrote:
> I would seriously look at scrapping the old IBM i Access for Windows
> and stick with the Access Client Solutions.
>
>
> Rob Berendt
>
------------------------------
message: 2
date: Tue, 24 Nov 2015 15:38:16 -0500
from: rob@xxxxxxxxx
subject: Re: New S814...which port for Lan Console?
I know the people who feel it's perfectly fine for your employees to get
into data like proprietary drawings, customer data, payroll data, etc
but
think it's curtains for the free world if they can connect to your FSP
may
argue with me but I tend to put our FSP's on our LAN. Thus our
redundant
HMC's can connect to either machine in either city. Think of it this
way,
if that PC you have as your console dies wouldn't you like to be able to
connect another? And what happens if it happens to die while you are at
COMMON?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
[3]
http://www.dekko.com
From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 11/24/2015 03:13 PM
Subject: Re: New S814...which port for Lan Console?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
lol...ok I'll use the top port...
Now is that's the
A) top port (T1) all by itself on the left hand side as you are looking
at
the back?
B) the top port on the 2 port stack on the left hand side..
C) the top port on the 4 port card on the right...
If A), that's where I had the cable, but I've got a A9002000 src being
displayed..
What did I do wrong? Do I need a cross pinned ethernet cable? It's not
mentioned, but seems strange to run a straight through cable direct.
Charles
On Tue, Nov 24, 2015 at 2:53 PM, DrFranken <midrange@xxxxxxxxxxxx>
wrote:
> T1. Top port. Always top port OR you could use the top port, either
way.
> :-)
>
> - Larry "DrFranken" Bolhuis
>
> www.Frankeni.com
> www.iDevCloud.com - Personal Development IBM i timeshare service.
> www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
>
>
> On 11/24/2015 2:36 PM, Charles Wilt wrote:
>
> All,
>>
>> Which port do I connect to the PC for the initial console setup?
>>
>> ACS docs say T1, Hardware infocenter mentions T4, T5
>>
>> Thanks!
>>
>> Charles
>>
>> --
> 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: [4]
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 [5]
http://archive.midrange.com/midrange-l.
>
>
--
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: [6]
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 [7]
http://archive.midrange.com/midrange-l.
------------------------------
message: 3
date: Tue, 24 Nov 2015 21:25:00 +0000
from: Cyndi Bradberry <CyndiB@xxxxxxxx>
subject: RE: Will RDi run on Win 10 ?
Thank you one and all for the nod. I will be putting in an order for a
windows 10 laptop.
Cyndi B.
Idaho
------------------------------
message: 4
date: Tue, 24 Nov 2015 21:30:30 +0000
from: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
subject: Looking for link for all Power8 / EXP24S disk options
Looking for link for all Power8 / EXP24S disk options
The August 2014 Technical Review does NOT include the latest announced
DASD.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<[8]mailto:psteinmetz@xxxxxxxxxx>
[9]
http://www.pencor.com/
------------------------------
message: 5
date: Tue, 24 Nov 2015 13:30:33 -0800
from: Mike Jones <mike.jones.sysdev@xxxxxxxxx>
subject: IBM i Access Client Solutions: SQL Scripts & Visual Explain?
Does IBM i Access Client Solutions have the ability to Run SQL scripts
and
Visual Explain, like Navigator does?
------------------------------
message: 6
date: Tue, 24 Nov 2015 16:33:02 -0500
from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: New System - TODO's
All,
Does IBM document a list of TODO's for a new system?
Wayback when, on our first box running v3r6...I recall some initial
setup
instructions for a new system. One step for instance was picking a new
system name.
I'd expect setting the system CCSID to be part of this list of TODO's.
Probably reviewing other system values for that matter.
It's been not quite 20 years since I had a brand new system, rather than
migrating from an existing system to new hardware.
Thanks!
Charles
------------------------------
message: 7
date: Tue, 24 Nov 2015 15:49:32 -0600
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: IBM i Access Client Solutions: SQL Scripts & Visual
Explain?
Hi Mike
Not yet - but Run SQL Scripts is supposed to come out in a December
release. Visual Explain is not there yet.
Vern
On 11/24/2015 3:30 PM, Mike Jones wrote:
> Does IBM i Access Client Solutions have the ability to Run SQL scripts
and
> Visual Explain, like Navigator does?
------------------------------
message: 8
date: Tue, 24 Nov 2015 21:56:53 +0000
from: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
subject: RE: New System - TODO's
Charles,
It's out there, used it a couple of years ago when setting up a hosted
test LPAR.
I'll send it once I find it.
Paul
-----Original Message-----
From: MIDRANGE-L [[10]mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Charles Wilt
Sent: Tuesday, November 24, 2015 4:33 PM
To: Midrange Systems Technical Discussion
Subject: New System - TODO's
All,
Does IBM document a list of TODO's for a new system?
Wayback when, on our first box running v3r6...I recall some initial
setup instructions for a new system. One step for instance was picking
a new system name.
I'd expect setting the system CCSID to be part of this list of TODO's.
Probably reviewing other system values for that matter.
It's been not quite 20 years since I had a brand new system, rather than
migrating from an existing system to new hardware.
Thanks!
Charles
--
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: [11]
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
[12]
http://archive.midrange.com/midrange-l.
------------------------------
message: 9
date: Tue, 24 Nov 2015 15:58:12 -0600
from: "Jerry Adams" <midrange@xxxxxxxx>
subject: RE: New System - TODO's
You mean there wasn't a Setup 1-2-3 manual with the box? My last setup
was
for a V5R4 system but it included a checklist. I called Barsa about an
anomaly and the first thing he said was, "Jerry, did you read the
manual?"
Anyway, are they shipping these things like PCs these days?
Jerry C. Adams
Depression is merely anger without enthusiasm. -Steven Wright
IBM i Programmer/Analyst
--
NMM&D
615-832-2730
-----Original Message-----
From: MIDRANGE-L [[13]mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of
Charles Wilt
Sent: Tuesday, November 24, 2015 3:33 PM
To: Midrange Systems Technical Discussion
Subject: New System - TODO's
All,
Does IBM document a list of TODO's for a new system?
Wayback when, on our first box running v3r6...I recall some initial
setup
instructions for a new system. One step for instance was picking a new
system name.
I'd expect setting the system CCSID to be part of this list of TODO's.
Probably reviewing other system values for that matter.
It's been not quite 20 years since I had a brand new system, rather than
migrating from an existing system to new hardware.
Thanks!
Charles
--
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: [14]
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
[15]
http://archive.midrange.com/midrange-l.
------------------------------
message: 10
date: Tue, 24 Nov 2015 14:28:43 -0800
from: Jerry Draper <midrangel@xxxxxxxxxxxxx>
subject: Re: SFTP client Expect 5.43 via PASE, maximum times allowed
depending on remote OS.
For most xfers we set the timeout to 20.
In the case of the very large PRICAT file we up the timeout to 480 and
then reset it back to 20 for the next in a series of gets.
We rename the file on the server to an archive folder after the xfer.
480 was determined after some trial and error.
The overall .sh script includes a byte count check of the file size on
the server vs the file size received on the IFS. Any discrepancy causes
a text message alert to the on call staff member.
Jerry
while {[gets $files file] != -1} {
if { $file != "ARCHIVE" && $file != "ls -1" && $file != "sftp> "
} {
set timeout 480
send "get $file\n"
expect {
default {exit 2}
"not found" {exit 3}
"sftp>"
}
set timeout 20
send "rename $env(RPATH1)PRICAT/$file
$env(RPATH1)PRICAT/ARCHIVE/$file\n"
expect {
default {exit 2}
"not found" {exit 3}
"sftp>"
}
send "!cp $env(LPATH1)$file $env(LPATH2)$file\n"
expect {
default {exit 2}
"not found" {exit 3}
"sftp>"
}
} else {
expect {
"sftp>"
}
}
}
close $files
On 11/24/2015 10:26 AM, Steinmetz, Paul wrote:
> Jerry,
>
> Could you please supply a sample of the code of how you modified the
Expect timeout.
>
> Paul
>
> -----Original Message-----
> From: MIDRANGE-L [[16]mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of Jerry Draper
> Sent: Monday, November 23, 2015 6:23 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: SFTP client Expect 5.43 via PASE, maximum times allowed
depending on remote OS.
>
> We programmed an sFTP system using Expect because our sFTP partner
will not allow key exchange.
>
> We had to modify the Expect timeout on large files as Scott suggests
below.
>
> This could be done dynamically by checking the file size before
initiating the Expect sFTP
>
> Jerry
>
> On 11/23/2015 3:13 PM, Scott Klement wrote:
>> Paul,
>>
>> 1) Expect is not "one of my products". It's a public domain program
>> available from NIST.
>>
>> There are a lot of tools available for IBM i that fall into "my
>> products", HTTPAPI, FTPAPI, TN5250, HSSFR4, XLPARSER4, JDBCR4, etc.
>>
>> 2) I do not have any other versions of it, I haven't needed them.
>> Feel free to get the latest sources and build your own version for
>> PASE if you are so inclined.
>>
>> 3) I do not consider any of the behavior you mentioned to be a bug in
>> Expect. Your script for Expect can be modified to check the timeout
in
>> a loop, thus allowing it to take much longer. Or to turn off the
>> timeout completely, etc as you like.
>>
>> Also, it's more useful to know the version of Expect vs. the
operating
>> system being used. As Expect is not part of the operating system,
the
>> version of the OS really shouldn't come into play, here.
>>
>> -SK
>>
>>
>> On 11/23/2015 10:45 AM, Steinmetz, Paul wrote:
>>> Scott,
>>>
>>> I want to clarify that this is an Expect 5.43 issue (one of your
>>> products), which is not supported by IBM.
>>> Second, majority of the SFTP and SSH documentation does not apply
>>> when Expect is used.
>>> Third, based on my testing and attempting to change config files,
>>> the ssh_config and sshd_config files are not used.
>>> ClinetAliveCountMax ; ClinetAliveInterval ; TCPKeepAlive had no
impact.
>>>
>>> The reason this product was installed years ago, we needed an SFTP
>>> solution for when the remote site could/would NOT support the use of
>>> keys, only user and password.
>>> Originally, only one remote vendor.
>>> Now we are using for seven vendors.
>>>
>>> Could you confirm my findings?
>>> Do you have a newer version of Expect?
>>> Is there a fix or workaround for this issue?
>>>
>>> I've been testing sending the same file(s) via Expect 5.43 to 3
>>> different servers using V7R1 as the client.
>>>
>>> 1) Remote Vendor OS unknown
>>> 2) Remote Local Production i5 V7R1
>>> 3) Remote Local Linux CENTOS 6.7
>>>
>>> CALL PGM(QP2SHELL) PARM('/QOpenSys/usr/bin/sh' +
>>> '-c' +
>>> '/home/SFTPXFER/PAULS/paulsP05.expect > +
>>> /home/SFTPXFER/PAULS/paulsP05.output')
>>>
>>> It appears Expect 5.43 has a default "set timeout" of 20 seconds
when
>>> no "set timeout" is coded.
>>> Files taking longer than 20 seconds will not complete.
>>> By adding a "set timeout NNN" to the script, longer/larger files can
>>> be sent.
>>> However, the "set timeout NNN" has different maximums depending on
>>> the remote OS.
>>> When the "set timeout NNN" is above the maximum, file never starts
>>> sending, connection is closed.
>>> Sending to the Remote Vendor OS unknown, "set timeout 290" works,
>>> higher values fail.
>>> Sending to the Remote Local V7R1 i5, "set timeout 120" works, higher
>>> values fail.
>>> Sending to the Remote Local Linux CENTOS 6.7, "set timeout 119"
>>> works, higher values fail.
>>>
>>> Below are my testing results, showing the maximums allowed, sending
>>> from a V7R1 OS client to:
>>>
>>>
>>> Remote Vendor OS unknown Rem Production i5 V7R1
Rem
>>> Local Linux CENTOS 6.7
>>> 7mb 20 sec 12 sec 12 sec
>>> 10mb 23 sec 12 sec 12 sec
>>> 15mb 23 sec 12 sec 12 sec
>>> 20mb 49 sec with ST 30 12 sec 12
sec
>>> 25mb 49 sec with ST 30 12 sec 13 sec
>>> 50mb 1m 49 sec with ST 60 15 sec 15 sec
>>> 75mb 1m 52 sec with ST 60 17 sec 17 sec
>>> 100mb 2m 49 sec with ST 90 21 sec 19
sec
>>> 125mb 2m 54 sec with ST 90 44 sec with ST 30 41
>>> sec with ST 30
>>> 150mb 3m 46 sec with ST 120 44 sec with ST 30
45
>>> sec with ST 30
>>> 200mb 4m 50 sec with ST 150 50 sec with ST 30
>>> 58 sec with ST 30
>>> 300mb 7m 42 sec with ST 240 60 sec with ST 30
58
>>> sec with ST 30
>>> 400mb 8m 38 sec with ST 290 1m 49 sec with ST 60
>>> 1m 44 sec with ST 60
>>> 500mb 8m 40 sec with ST 290 1m 49 sec with ST 60
>>> 1m 46 sec with ST 60
>>> 600mb 10m with ST 290 88% 1m 57 sec with ST 60
1m
>>> 47 sec with ST 60
>>> 700mb 2m 35 sec with ST 90 2m 33 sec
>>> with ST 90
>>> 800mb 2m 57 sec with ST 90 2m 48 sec
>>> with ST 90
>>> 900mb 3m 31 sec with ST 120 3m 14 sec
>>> with ST 110
>>> 1gb 3m 39 sec with ST 120 3m 24 sec
with
>>> ST 110
>>> 1.1gb 3m 51 sec with ST 120 3m 24 sec
>>> with ST 110
>>> 1.2gb 3m 55 sec with ST 120 3m 38 sec
>>> with ST 110
>>> 1.3gb 4m 00 sec with ST120 98% 4m 00 sec
>>> with ST 119 88%
>>>
>>> Paul
>>>
>>>
>>> -----Original Message-----
>>> From: MIDRANGE-L [[17]mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf
>>> Of Scott Klement
>>> Sent: Wednesday, November 18, 2015 3:00 PM
>>> To: Midrange Systems Technical Discussion
>>> Subject: Re: SFTP client via PASE, large files possibly timing out
>>>
>>> Paul,
>>>
>>> The 'set timeout' in Expect makes perfect sense. That didn't occur
to
>>> me before seeing your recent messages, but it makes a lot of sense.
>>>
>>> Expect is not part of SSH (like SFTP is). It is a generic program
>>> that pretends to be a user at a terminal, and automates what the
user
>>> might do... so it keys in values, and sits and waits for responses
to
>>> be sent to the "screen" (the virtual screen it's reading under the
>>> covers, not your actual display) and based on what it sees on the
>>> screen, it does something in response, etc. It can be used to
>>> automate any user interaction with a PASE command-line environment.
>>>
>>> So if you've written your script to timeout during a put/get
command,
>>> it makes perfect sense that it's killing the file transfer when the
>>> timeout occurs. It doesn't know what the command is doing under the
>>> covers, it only knows what's displayed to the screen.
>>>
>>> So, my question to you... why code expect to do a timeout during
the
>>> actual put/get command? are you having trouble with it 'freezing'
>>> during file transfers and never completing?
>>>
>>> Sorry this response was a bit slow... I was out of the office for a
>>> few days.
>>>
>>> -SK
>>>
>>>
>>>
>>>
>>> On 11/14/2015 11:43 AM, Steinmetz, Paul wrote:
>>>> Scott,
>>>>
>>>> Those were settings recommended to check by IBM support.
>>>> By increasing "Set Timeout" from 30 to 90 included in the .expect
>>>> input script, I was successful in resolving this issue.
>>>> I tested using higher values, successful up to 296.
>>>> 297 and higher fails.
>>>> Why is this?
>>>> I'd like to confirm for future for large files or when times are
longer.
>>>>
>>>> Paul
>>>>
>>>> -----Original Message-----
>>>> From: MIDRANGE-L [[18]mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf
>>>> Of Scott Klement
>>>> Sent: Friday, November 13, 2015 12:49 AM
>>>> To: Midrange Systems Technical Discussion
>>>> Subject: Re: SFTP client via PASE, large files possibly timing out
>>>>
>>>> Paul,
>>>>
>>>> Unless I'm misunderstanding your symptoms, you're looking at the
>>>> wrong settings, here...
>>>>
>>>> My understanding is that your file transfer is looking good,
>>>> transferring data successfully until all of the sudden,
>>>> mysteriously, the transfer is cut off after 45 seconds.
>>>>
>>>> But, you are checking things related to "inactivity". Inactivity
>>>> means that NOTHING is sent for the timeout period. Inactivity
would
>>>> never cut you off in the middle of a file transfer that's
progressing!
>>>>
>>>> I know the timeout settings are set higher, but let's use 45
seconds
>>>> as an example to explain what 'inactivity' timeouts mean... if you
>>>> had an inactivity timeout of 45 seconds that was affecting you,
this
>>>> is what would happen: (1) You'd start the transfer. (2) At some
>>>> point (maybe right away, or maybe several minutes later) the
>>>> transfer would "freeze"
>>>> where no new data was transfering for some reason like a network
>>>> glitch or something. (3) 45 seconds after freezing up -- which is
>>>> to say, 45 seconds without a single byte being transferred -- the
>>>> timeout would
>>>> kick in and disconnect you. If the transfer never froze up, the
>>>> timeout would never occur (even if the file took hours to send)
>>>>
>>>> That's what an inactivity timeout is... it means things are
stalled.
>>>> Nothing at all is transferred in the timeout period, not even a
>>>> single byte. As long as at least one byte is sent in that 45
>>>> seconds, it would not occur.
>>>>
>>>> However, that's not how I understand your symptom. I understood
>>>> that it was cutting you off while the transfer was successfully
going..
>>>> So unless i'm misunderstnading, what you're experiencing cannot be
>>>> an inactivity timeout. It's a timeout that occurs even on an
active
>>>> session... right?
>>>>
>>>> The 4 settings you mentioned, however...
>>>>
>>>> 1- an INACTIVITY timeout on your router.
>>>>
>>>> 2- Keepalive... this is completely unrelated.
>>>>
>>>> 3- FTP server settings -- completely unrelated, you are not using
FTP.
>>>> Even if you were, it's not the server.
>>>>
>>>> 4- SSH is the right tool to check for settings on... but again,
this
>>>> is an INACTIVITY timeout.
>>>>
>>>> Unfortunately, I have no clue what would cause the issue you're
seeing.
>>>> I've never seen this happen before. But, unless the session
_is_
>>>> stalling for 45 seconds, this isn't an "inactivity" timeout. It's
a
>>>> "you only have 45 seconds total to use this connection before I cut
>>>> you off" timeout, which is very different.
>>>>
>>>> It's like saying to your teenaged daughter "you can only be on the
>>>> phone for 10 minutes per day". (Time limit) That's very different
>>>> from "as long as you say at least one word every 10 minutes you can
>>>> stay on the phone, but if you don't say anything for 10 minutes
i'll
>>>> cut you off"
>>>> (inactivity timeout)
>>>>
>>>>
>>>>
>>>>
>>>> On 11/12/2015 2:03 PM, Steinmetz, Paul wrote:
>>>>> I discovered a new piece to this puzzle.
>>>>> For this one specific remote server:
>>>>> All files are successful that complete in 45 seconds or less.
>>>>> All files taking longer than 45 seconds fail.
>>>>>
>>>>> Somewhere, there must be a 45 second timer/timeout setting.
>>>>> These have been checked and confirmed.
>>>>>
>>>>> 1- It could be at the firewall/router's idle timeout level. - 5
>>>>> minutes.
>>>>> 2- Verify the TCP keepalive on the iSeries (CHGTCPA). - TCP keep
>>>>> alive . . . . . . . . . 5
>>>>> 3- General FTP Server Inactivity Timeout Value see the following
>>>>> doc: The default inactivity timeout value is 300 seconds. The
>>>>> default transfer timeout value is 420 seconds. Inactivity timeout
.
>>>>> . . . . . . 300
>>>>> -
http://www.ibm.com/support/docview.wss?uid=nas8N1011178
>>>>> 4- Timeout in SSH: Disconnecting Inactive SSH Sessions on the IBM
>>>>> I The TMOUT and TIMEOUT PASE environment variables have a value of
>>>>> 600 seconds. If there is no activity within an SSH session for 10
minutes
>>>>> -
http://www.ibm.com/support/docview.wss?uid=nas8N1013311
>>>>>
>>>>> Paul
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: MIDRANGE-L [[19]mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf
>>>>> Of Scott Klement
>>>>> Sent: Tuesday, November 03, 2015 4:39 PM
>>>>> To: Midrange Systems Technical Discussion
>>>>> Subject: Re: SFTP client via PASE, large files possibly timing out
>>>>>
>>>>> FWIW.. I have used sftp to send extremely large files, such as
>>>>> whole server backups, without any problems at all. I did not have
>>>>> to set up anything in particular, it just worked.
>>>>>
>>>>> When you are having trouble with your larger files (imho, 110mb
>>>>> isn't really very big) does it always stop at the exact same byte
>>>>> position?
>>>>> Or does it vary?
>>>>>
>>>>> If it varies, I'd suggest this is probably a network issue rather
>>>>> than a software issue. A flaky cable/switch/router/etc is causing
>>>>> the data to get screwed up somewhere, causing the transfer to
abort.
>>>>>
>>>>> IF it's always the same, then I would look for some sort of size
>>>>> limit being set up somewhere, most likely on the server-side.
>>>>>
>>>>> Also, you could also try using scp rather than sftp and see if
that
>>>>> matters at all. Just as a lark...
>>>>>
>>>>>
>>>>> On 11/3/2015 8:34 AM, Steinmetz, Paul wrote:
>>>>>> I changed the SFTP process to send a 3mb zip file instead of the
>>>>>> 110mb uncompressed file.
>>>>>> SFTP now working with a zipped 3mb file.
>>>>>> Large file issue for SFTP still exists, possibly 30 to 40mb
limit.
>>>>>> Still looking to resolve this issue.
>>>>>>
>>>>
>>>> --
>>>> 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: [20]
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
>>>> [21]
http://archive.midrange.com/midrange-l.
>>>>
>>> --
>>> 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: [22]
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
>>> [23]
http://archive.midrange.com/midrange-l.
>>>
>
> --
> --
> Jerry Draper, Trilobyte Software Systems, since 1976 IBMi, Network,
and Connectivity Specialists, LAN/WAN/VPN Representing WinTronix,
Synapse, HiT, and others .....
> (415) 457-3431; www.trilosoft.com
>
> --
> 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: [24]
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
[25]
http://archive.midrange.com/midrange-l.
>
--
--
Jerry Draper, Trilobyte Software Systems, since 1976
IBMi, Network, and Connectivity Specialists, LAN/WAN/VPN
Representing WinTronix, Synapse, HiT, and others .....
(415) 457-3431; www.trilosoft.com
------------------------------
Subject: Digest Footer
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [26]
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 [27]
http://archive.midrange.com/midrange-l.
------------------------------
End of MIDRANGE-L Digest, Vol 14, Issue 1656
********************************************
References
Visible links
1.
http://lists.midrange.com/mailman/listinfo/midrange-l
2. mailto:midrange@xxxxxxxxxxxx
3.
http://www.dekko.com/
4.
http://lists.midrange.com/mailman/listinfo/midrange-l
5.
http://archive.midrange.com/midrange-l
6.
http://lists.midrange.com/mailman/listinfo/midrange-l
7.
http://archive.midrange.com/midrange-l
8. mailto:psteinmetz@xxxxxxxxxx
9.
http://www.pencor.com/
10. mailto:midrange-l-bounces@xxxxxxxxxxxx
11.
http://lists.midrange.com/mailman/listinfo/midrange-l
12.
http://archive.midrange.com/midrange-l
13. mailto:midrange-l-bounces@xxxxxxxxxxxx
14.
http://lists.midrange.com/mailman/listinfo/midrange-l
15.
http://archive.midrange.com/midrange-l
16. mailto:midrange-l-bounces@xxxxxxxxxxxx
17. mailto:midrange-l-bounces@xxxxxxxxxxxx
18. mailto:midrange-l-bounces@xxxxxxxxxxxx
19. mailto:midrange-l-bounces@xxxxxxxxxxxx
20.
http://lists.midrange.com/mailman/listinfo/midrange-l
21.
http://archive.midrange.com/midrange-l
22.
http://lists.midrange.com/mailman/listinfo/midrange-l
23.
http://archive.midrange.com/midrange-l
24.
http://lists.midrange.com/mailman/listinfo/midrange-l
25.
http://archive.midrange.com/midrange-l
26.
http://lists.midrange.com/mailman/listinfo/midrange-l
27.
http://archive.midrange.com/midrange-l
midrange.com
