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


  • Subject: RE: Correlating *SAVF "records" to FTP job I/O count
  • From: "Goodbar, Loyd (AFS-Water Valley)" <LGoodbar@xxxxxxxxxxxxxx>
  • Date: Mon, 1 May 2000 15:12:00 -0400

Could you use the MTU value from your TCP/IP setup? The MTU (maximum
transmission unit) is the maximum number of bytes in each IP packet. On
LANs, I think the value is usually 1500. I don't know what each "I/O" on an
FTP transfer is, either. I guess it is NOT the number of save file records
(you can see with the DSPSAVF command). If you use the MTU, realize it can
be a partial IP packet. (IE, save file size >> packets * MTU)

HTH,
Loyd

-----Original Message-----
From: Bale, Dan [mailto:DBale@lear.com]
Sent: Monday, May 01, 2000 12:58 PM
To: 'MIDRANGE-L@midrange.com'
Subject: Correlating *SAVF "records" to FTP job I/O count


Is there a known, constant, record-blocking factor used when transmitting a
save file from one AS/400 to another via FTP?

I am using FTP to transmit save files from plant boxes to the division box.
One I have running right now is 56MB.  The system operator is wondering how
much longer the FTP will run.  When I look at the job running FTP, it shows
the save file being transmitted as an open file (WRKJOB option 14) and shows
the I/O count at 12,417.  If I could correlate the save file's number of
records to the I/O count, I would be able to estimate the time remaining to
complete the transmission.  

RTFM?  Please point the way.

- Dan Bale


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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