RE: HELP establishing dialup in an application

[Evan Harris <spanner@xxxxxxxxxx>]

Dan

I believe the section you might want in the "More cool things..." redbook
is PPP/Dial-on-Demand; be aware that there may/will be hardware release
dependencies - I'm pretty sure dial on demand required particular comms
cards. You will probably struggle on a release pre V4R3 and even then there
may be some stuff that is not reliable

Using Dial on demand I got my AS/400 to dial different numbers based on
some command parameter stuff as part of a proof of concept FTP automation
project. I agree with Buck that if you are going to automate FTP then you
will probably want to use Scott's API as vanilla FTP is a dog to error
check and recover. There are the commercial offerings also if money is
avilable.

One thing I seem to recall from someone on the list doing something similar
was an issue if the IP address at the other end was not fixed it was a
problem for the PP/SLIP connection defintion but I may be incorrect. Given
what it sounds like you are doing this may be worth investigating through
the archives.

Hope this helps
Regards
Evan Harris

>Dan Bale wrote:
>
> >I am trying to educate myself on what is
> >involved in automatically establishing a
> >dialup connection so that we can FTP several
> >files from the AS/400 to a server once each
> >day - with NO user intervention.
>
>You will be wanting to look at Scott Klement's FTP API.
>http://klement.dstorm.net/oss.html  You will also want to get a copy of the
>modem manual for the modem your system is using.
>
> >Messages with "good" or "bad" results could
> >be sent to a special message queue.  Assuming
> >the configuration is "set", what does my program
> >have to do to vary on (and in what sequence)?
>
>VRYCFG *LIN xxx *on, then *CTL, then *DEV
>
> >Should I be checking to see if some other
> >job is using the same dialup line that
> >my program wants to use?
>
>RTVCFGSRC
>
> >If I have to vary something off to vary my
> >???stuff??? on, then I would want to vary
> >that something back on after I'm done.
>
>If you want to play nice you should put things back the way you found them.
>
> >What are "resources", "line descriptions",
> >"controller descriptions", and "device
> >descriptions" in the dialup communications context?
>
>'Resource' is the physical port on the back of the iSeries.
>'Line' is a logical description of the modem.
>'Controller' is a logical description of the far end.
>'Device' is a logical description of the local end.
>
>These are all very vague and simplified.  You need to understand that the
>iSeries communications support (line, ctl, dev) is intended to handle every
>scenario, and a simple point to point dial up is very easy compared to a
>multi-drop leased line with dial backup.  The main thing to understand is
>that your end must match the far end.
>
>I am not a SLIP or PPP person, but I am pretty certain that this is what
>you'll be using to make the connexion.
>
>   --buck