Re: Batch automate connecting to AS400's

Andre Nortje wrote:
> 
> > At 7:11 PM 7/17/97, Andre Nortje wrote:
> > >I would like to write a CL/RPG set of programs that will run in
> > >batch. At 4 different locations (other AS400's) nightly jobs are
> > >run that produce files to upload to a central AS400.
> 
> Paul E Musselman wrote...
> 
> > Do you really -need- to use passthrough to get your data?  Why not
> > set up the remote AS/400s to automatically transmit at 06h30?  They
> > can use send net file and SNADS to have your data arrive
> > automatically.  After the file is transmitted, send a net message to
> > a given queue and let the central '400 receive the net file.
> 
> Many thanks to all that replied.
> 
> Ok, I have some constraints - Only one telephone line at Head office
> with one modem attached. No system operators. So I thought I have to
> fetch the data rather than let the remote systems send the data. I
> use SNDNETF extensively, via QSNADS connection, but not TCP/IP.
> 
> AS400-1 can STRPASTHR to AS400-2, then ENDPASTHR. This already
> works. But can you set up SNADS in such a way so that AS400-2
> STRPASTHR to AS400-1 without an existing connection?

You obviously have the connection (line/controller/device) created on
the remote systems to connect from the central one - just make sure you
have
SWTCNN(*BOTH) on the remote systems line description, and not 
SWTCNN(*ANS).
Also make sure the controller descriptions on the remote systems created
for connection to the central one have the central systems dialling
commands/phone number entered in the CNNNBR parameter on the APPC
controller - and SWTDSC(*YES).
If the remote system runs a SNDNETF command and has something to send,
SNADS will initiate the connection and dial-up the central system (of
course, this is dependent on the distribution queue settings I mentioned
in my previous note).
STRPASTHR is not required at all.

> 
> If branch-1 passthrough to central AS400 at 06h30, and branch-2 then
> passthrough at 06h35, and the connection to branch-1 is still active,
> a message is sometimes send to the system operator message queue that
> request a reply. So I though hold the distribution queues at the
> branches, run the day-end job, and let head office control the
> pasthrough, release the queues, pull the data until complete,
> disconnect, and try the next branch.
> 
> REMEMBER I HAVE 4 BRANCHES TO COLLECT DATA FROM, and I do not have a
> system operator that sit there answering messages.

Don't forget you can use WRKRPYLE and enter default options for any
message.  
There are several that may come up when connection attempts fail.

However, for SNADS you can just make sure the distribution queue retries
sending 999 times 5 minutes apart and if it gets a busy signal it will
keep on trying.

-- 
... Neil Palmer                                      AS/400~~~~~      
... NxTrend Technology -Canada       ____________          ___  ~     
... Markham,  Ontario,  Canada       |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000 x238       |__________|_|______|_|______)   
... url:http://www.NxTrend.com        oo      oo   oo  oo   OOOo=o\   
... mailto:NPalmer@NxTrend.com     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *