Re: APPC over TCP/IP Problems...

Paul,

Agreed - Netid can act as an extra item of security.  If I recall
correctly (I deleted the email) the problem in the original question
appeared to be that each of his two systems had different Netid's (I
believe he had each one set the same as the system name - NEX and NEX2 I
think).  Admittedly, you can work around that in WRKCFGL, but that might
be making things a bit too difficult when he's trying to set it up for the
first time.

...Neil





PaulMmn <PaulMmn@ix.netcom.com>
Sent by: midrange-l-admin@midrange.com
2002/06/14 01:33
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Subject:        Re: APPC over TCP/IP Problems...


I beg to differ about NETID!  The NetID is (IMHO) a name that should
be unique for each installation or company.  I'm of the opinion that
this assists in security; makes it harder for people to guess.

Everyone uses APPN as their network ID because IBM uses it in their
examples; it took me a long time to realize that this is a
-variable;- you're allowed to select your own!  It doesn't even have
to be the same at both ends of the connection (although it does make
things a lot simpler).


The remote config list should (theoretically) not be required!  Many
times when I've talked to IBM on the help line, they expressed the
opinion that APPN should automatically configure itself, and the CFGL
shouldn't be necessary.

However, I've also added remote and local configuration lists to our
systems, mainly because APPN isn't perfect, and sometimes gets
confused.  The configuration lists sort of give APPN a leg up and get
things started.


--Paul E Musselman
PaulMmn@ix.netcom.nospam.com





Scott Said (in part):

>Second, if possible get the "Local network ID" to match on both systems.
I
>prefer using APPN, but you should be able to use NEX also if there is an
>overwhelming reason to do so (i.e. someone who previously set up your
>network SNA services(perhaps on a mainframe) with a different NetID.)
>
>You need to create a remote config list (QAPPNRMT) as follows:
>           Remote              Remote    Control
>Remote    Network   Local     Control   Point
>Location  ID        Location  Point     Net ID
>-------------------------------------------------
>Sysname1  APPN      Sysname2  TCPIP     APPN
_______________________________________________