• Subject: RE: SNA over IP communication
  • From: "Sims, Ken" <KSIMS@xxxxxxxxxxxxxxxx>
  • Date: Thu, 4 Jan 2001 14:53:53 -0500

Hi Chris -

>TCP/IP is almost never a problem , the real pain starts when 
>the SNA ( encapsulated ) needs to be migrated.

I assume that you are talking about using AnyNet support for SNA over

>My big question is : where is the relation defined between the 
>SNA definitions and the IP-address ?
>Depending on the source , I get following answers :
>1) That relation must be manually entered in the router.
>2) That should be done on the AS/400.
>3) Nothing, it's automatically taken care of.
>4) No clue ( most popular one :-( )
>The first answer was given to me by Software Support from IBM.
>Having a lot of faith in that person, 
>I assumed that his answer was the correct one.

You have faith in an answer from IBM????  <G>

The correct answer is #2.  The router needs to be able to route TCP/IP to
the IP address in question, but that's all.  (Routing SNA directly rather
than using AnyNet *does* require router configuration.)

Besides the normal SNADS configuration, there are two extra pieces for

1. a host table entry for IP address which has a host name of the format:
where [hostname] is the name you want to call this IP address by (you'll
probably also want to have a host name entry for this IP address using just
[hostname]), and
where [networkname] is the remote network name.  This is probably the same
as your local network name, which you can see with DSPNETA.

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.

Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.

| 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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.