RE: Using modems to connect two iSeries

Pete,

The 7855 can be configured to do async. Therefore you ought to be able to
use it to talk PPP to the internal modem in your newer machine. Sorry I
don't have any specifics to tell you, but the last time I used Ops Navigator
to set up PPP, I recall it was pretty friendly. It may already have a
built-in init string for a 7855, since that is an IBM modem. You may just
need to put the 7855 into async mode using its control panel and then let
the iSeries and Ops Nav configure it from there.

-Marty

------------------------------

date: Thu, 11 Dec 2003 08:35:42 -0700
from: "Pete Helgren" <pete@xxxxxxxxxx>
subject: Using modems to connect two iSeries

I didn't get any responses on my first post and perhaps it had to do with
the funky way I posted it.  Let's try again.:

> For many years we have used the "old" BPCUST library that contained
> routines that allowed two iSeries to talk to each other over SNA (I
> think).  My 270, and now my 800 didn't have a modem that supported the
> SDLC protocol (I believe it is a 2793 internal modem).  But, I still need
> iSeries boxes to talk to each other, one with the older modem (like a
> 7855-10) and one using the new internal modem.  Is there a "common ground"
> that will mimic the BPCUST library functions (so I can start a session and
> then use STRPASTHR or better yet, TELNET).  My objective to deliver a
> library of these functions so that my users will just run a command that
> prompts them for a phone number, and the functions will configure the
> lines, start whatever services are required and then present a menu of
> options such as start Passthru, telnet, FTP, etc, similar to the way the
> BPCUST library took care of things (if you are familiar with the BPCUST
> library which I think was an IBM Business Partner add-on).
> 
I am guessing PPP is the right choice if I am using the internal modem, but
can it talk to a 7855 (or similar) modem.  Anybody have some sample code
that already does this?

> Thanks, 
> 
> Pete Helgren
> Timpanogos Technologies, Inc
>