RE: Correlating *SAVF "records" to FTP job I/O count -- MIDRANGE-L

That bugger took 3 hours and 40 minutes to transmit.  It was 59.7MB.  From
the log file:

    61202064 bytes transferred in 12555.306 seconds. Transfer rate 4.875
KB/sec.

The save file had 115,913 records.  115,913 * 528 = 61,202,064.  The DSPOBJD
size was 59,785,216 (????).

Using 1480 bytes per frame, would you calculate the number of puts as:
   1)  61,202,064 / 1480 = 41,352.7         *or*
   2)  1480 / 528 = 2 whole records per frame; 115,913 / 2 = 57,957
Based on the "guesstimate" that the number of puts was around 17,000 about
two hours into the job, I'm not sure either of these calculations work.

I think I'm going to set up a test whereby I submit a batch job to do an FTP
and another batch job to do a DSPJOB OPTION(*OPNF) in a loop that runs every
15 seconds and run some stats on the collected data to see if there's a
pattern I can use.

Other suggestions are greatly appreciated!

- Dan Bale

> -----Original Message-----
> From: Patrick Townsend [SMTP:townsend@patownsend.com]
> Sent: Monday, May 01, 2000 8:24 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Correlating *SAVF "records" to FTP job I/O count
> 
> 
> Yes, 1496 bytes. Subtracting TCP/IP frame headers you are probably
> transferring 1480 bytes per frame. How long does it take to transfer a
> 58 meg save file? Just takes a few minutes here between AS/400 and
> Windows NT PC.
> 
> Patrick
> 
> "Bale, Dan" wrote:
> > 
> > What if I see that the Maximum Frame Size of the line description is
> 1496?
> > What does 1496 mean?  1496 bytes?  I don't have the authority to run a
> comm
> > trace here.  Not sure anyone else here would want to go through the
> bother.
> > 
> > TIA,
> > - Dan Bale
> > 
> > > -----Original Message-----
> > > From: Patrick Townsend [SMTP:townsend@patownsend.com]
> > > Sent: Monday, May 01, 2000 3:15 PM
> > > To:   MIDRANGE-L@midrange.com
> > > Subject:      Re: Correlating *SAVF "records" to FTP job I/O count
> > >
> > > Dan,
> > >
> > > I believe the transfer record size of an FTP transfer will be
> controlled
> > > by the Maximum Frame Size of the line description. Save file record
> > > lengths are 528, but I believe FTP should send multiple records with
> > > each transfer. You can see what the AS/400 is doing by putting a
> > > communications trace on the line (STRCMNTRC). End the trace with
> > > ENDCMNTRC and then print it with PRTCMNTRC. There is a header for each
> > > TCP/IP frame, but you will get an idea of the size this way.
> > >
> > > Patrick
> > > --
> > > IBM AS/400 communications, FTP automation, and network security
> > > software and consulting services.
> > >
> > > http://www.patownsend.com
> > >
> > > "Bale, Dan" wrote:
> > > >
> > > > 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
> 
> -- 
> IBM AS/400 communications, FTP automation, and network security
> software and consulting services.
> 
> http://www.patownsend.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
+---