RE: SNA over IP communication

["Alexei Pytel" <pytel@xxxxxxxxxx>]

> 2. entries in the QAPPNRMT configuration list where the Remote Location
is
> the same as [hostname], and the Remote Control Point is TCPIP.  The
Remote
> Network ID, Local Location, and Control Point Net ID can be usually be
left
> as *NETATR, which will cause the information from DSPNETA to be filled
in.
> If the remote network name is different from the local network name,
enter
> the actual remote name.  In either case the Remote Network ID should be
the
> same as [networkname] when you are done.

Not exactly. When you create APPC controller type *ANYNW, you create a kind
of "funnel", leading down to SNA-over-IP support.
For this controller you specify control point - as <network ID>/<CP name>
pair.
They could be anything at all - not necessarily TCPIP.

When you configure QAPPNRMT, for every remote location, which is supposed
to be reached via SNA-over-IP, you add an entry and specify control point
from *ANYNW controller.

When APPC session is established for a given remote location, system will
look in QAPPNRMT, then find appropriate APPC controller using control point
information. If this happens to be *ANYNW controller, then SNA-over-IP is
used to find IP address, establish connection etc. etc.

You may have as many *ANYNW controllers as you want (with different CP
names) - or funnel all SNA-over-IP sessions via single *ANYNW controller.


Alexei



+---
| 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
+---