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

Thanks for the tip.  Using CFGTCP option 1 [WRKTCPSTS OPTION(*IFC)], I found
the line description.  
The "Display TCP/IP Interface Status" shows the MTU = 1492 and the Line Type
= *ELAN

The "Display Line Description" shows both the Line Speed and the Current
Line Speed as 10M (10 million bits per second).  The maximum frame size is
1496.

Is tracert available on the 400?

I did a ping to the remote 400 I was having complaints about and a summary
of the results shows:
   Round-trip (in milliseconds) min/avg/max = 46/67/95             
   Connection verification statistics: 20 of 20 successful (100 %).
I used all of the default values on the ping command (except for the
NbrPkt(20) ).
Does this indicate anything significant?

- Dan Bale

> -----Original Message-----
> From: Rob Berendt [SMTP:rob@dekko.com]
> Sent: Wednesday, May 03, 2000 12:24 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: Correlating *SAVF "records" to FTP job I/O count
> 
> Combination of:
> CFGTCP & WRKLIND
> would be a start.  
> Under NT you can use the command tracert, which stands for trace route.
> For example, from the MS DOS command prompt:
> 
> 
> C:\qtemp>tracert gdisys
> 
> Tracing route to gdisys.dekko-1 [198.1.1.201]
> over a maximum of 30 hops:
> 
>   1   <10 ms   <10 ms   <10 ms  10.10.4.1
>   2   <10 ms   <10 ms    10 ms  198.1.1.201
> 
> Trace complete.
> 
> Second sample:
> C:\qtemp>tracert nra.org
> 
> Tracing route to nra.org [206.97.103.71]
> over a maximum of 30 hops:
> 
>   1   <10 ms    10 ms   <10 ms  10.10.4.1
>   2   <10 ms    10 ms   <10 ms  208.16.99.1
>   3    40 ms   <10 ms   <10 ms  sl-gw5-chi-5-2.sprintlink.net
> [144.228.59.117]
>   4    50 ms    60 ms    60 ms  sl-bb3-chi-2-0.sprintlink.net
> [144.228.50.15]
>   5    71 ms    80 ms   100 ms  core4-serial6-0-0.WillowSprings.cw.net
> [206.157
> 77.93]
>   6    60 ms    61 ms    70 ms  corerouter2.WillowSprings.cw.net
> [204.70.9.146]
> 
>   7    50 ms    60 ms    70 ms  corerouter1.WestOrange.cw.net
> [204.70.9.138]
>   8   120 ms   100 ms   100 ms  core9.WestOrange.cw.net [204.70.9.53]
>   9   100 ms    40 ms    60 ms  core2-hssi-2.NewYork.cw.net [204.70.1.97]
>  10   200 ms    80 ms    60 ms  border6-fddi-0.NewYork.cw.net
> [204.70.219.66]
>  11   130 ms   200 ms   241 ms  mainstream-eis.NewYork.cw.net
> [204.70.221.86]
>  12   110 ms   150 ms   130 ms  www.nra.org [206.97.103.71]
> 
> Trace complete.
> 
> 
> 
> 
> 
> DBale@lear.com on 05/03/2000 10:37:08 AM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To:   MIDRANGE-L@midrange.com@Internet
> cc:    
> Fax to:       
> Subject:      RE: Correlating *SAVF "records" to FTP job I/O count
> 
> Wow, what a difference!  I am unaware of the comm hardware involved here.
> I
> can tell you that they have a network of 30+ AS/400s.  FWIW, any of these
> AS/400s can FTP to any other AS/400 in the network (I don't know if that
> gives a clue as to the setup they're using).
> 
> How can I tell what comm config is being used for FTP?
> 
> TIA,
> Dan Bale
> 
> > -----Original Message-----
> > From:       Patrick Townsend [SMTP:townsend@patownsend.com]
> > Sent:       Wednesday, May 03, 2000 2:10 AM
> > To: MIDRANGE-L@midrange.com
> > Subject:    Re: Correlating *SAVF "records" to FTP job I/O count
> > 
> > Dan,
> > 
> > I just transferred a large save file from the AS/400 to PC:
> > 
> >     81792480 bytes transferred in 328.231 seconds. Transfer rate 249.191
> > KB/sec.
> > 
> > I then transferred the same save file to another AS/400 on the same
> > network (10, not 100):
> > 
> >     81792480 bytes transferred in 127.947 seconds. Transfer rate 639.267
> > KB/sec.
> > 
> > I think you should be seeing better throughput! Have you talked to the
> > network folks to see what they have to say?
> > 
> > Patrick
> > 
> > 
> > "Bale, Dan" wrote:
> > > 
> > > 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
+---