Re: Here is a simple question.

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

>Every night I have 100+ SAVF that need to be sent to another AS/400.
>We use *ANYNET/SNADS over IP.  The process takes about 4 hours.
>I noticed that SNADS queues up and sends 1 file at a time.
>Is there a way to change this so that the target user-system is the same but
>that SNADS sends 2-3 at a time?
>
>We looked at FTP but the list varies from night to night and new ones are
>added and old ones removed constantly.

Two things to consider:

(a) You -can- automate FTP transmissions.  A little CLP and you can tune
the file list as you go.

(b) SNADS is like the post office:  "Neither rain nor snow nor sleet nor
fog nor gloom of night will stay this courier from the [not so] swift
completion of its appointed rounds."  This is because SNADS has all the
error recovery code in the world.  If you give it to SNADS, it will get
there.  Sometime.

Since a SAVF is, to RPG, just a 528-byte file (verify that number, folks),
which can be read by RPG, you can write your own communication programs to
send the data from a save file on one system to a save file on another
system.  Just read-and-send on one end, and receive-and-write on the other.

The only problem is that your own programs have to handle their own error
corrections.  Fortunately, if your comm link is anywhere near good, your
file will get there.  But you're on your own if it doesn't.

The good thing is that you can fire up as many sets of send/receive
programs as you have bandwidth.

--Paul E Musselman
PaulMmn@ix.netcom.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
+---