|
George, your SNA-IDs of the two systems are NEX.NEX and NEX2.NEX2 while you set the nex controllers up for a conversation between the machines NEX.APPN and NEX2.APPN. Do a CHGNETA on both machines for the local network ID parameter and change it to "APPN" on both machines, so that they both reside in the "APPN"-network, then it should work. HTH, regards from Germany, Philipp Rusch George Kinney schrieb: > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > -- > [ Picked text/plain from multipart/alternative ] > Hopefully someone out there can halp me with this. We have two systems in > house (NEX v3r7) > and (NEX2 v4r5) and we are quite happy with them talking TCP/IP. However, > our parent company's > support staff don't understand FTP, TELNET, etc. So they've requested that > we enable APPN, and > related services between them. (Which puts me in a bind since I know about > as much about APPC > , APPN, SNA and the like as they do about TCP/IP :)) > > Going by the examples in the Communication Configuration manual, I went > through the steps to > set up APPC over TCP/IP, but I can't start a passthrough session. It always > ends with an > error: " APPC failure. Failure code is X'0009000000000000'." This is > immediately preceded by the > error: " BIND sense code X'10030000' received for mode BLANK device NEX." > > On the remote system, I get: > > Message . . . . : MPTN connection request rejected. > > Cause . . . . . : The system rejected an incoming Multiprotocol Transport > > Networking (MPTN) connection request. The local LU name is APPN.NEX2. The > > remote LU name is NEX.NEX. The reason code is 0001. The reason codes and > > their meanings follow: > > 0001 -- The network identifier does not match the system network > identifier. > > I've added the necessary entries to the *APPNRMT config list, and done the > ADDCMNE step as > advised in the error message above. Both boxes are on the same in-house LAN, > in the same sub-net, > etc. So there is no equipment between them other than a switch. Both are set > to Autocreate > devices, etc. > > As you can see, *ANYNW is enabled, and we I have no TCP/IP connection > problems of any type. > Have I configured something obviously wrong? Or do I need to take some > additional steps? > At any rate, I'm pretty much stumped at this point. > > Any help would be appreciated. > > Following are the configurations for both systems: > > System 1 - NEX2: > Display Network Attributes > System: NEX2 > Current system name . . . . . . . . . . . . . . : NEX2 > Pending system name . . . . . . . . . . . . . : > Local network ID . . . . . . . . . . . . . . . . : NEX2 > Local control point name . . . . . . . . . . . . : NEX2 > Default local location . . . . . . . . . . . . . : NEX2 > Default mode . . . . . . . . . . . . . . . . . . : BLANK > APPN node type . . . . . . . . . . . . . . . . . : *ENDNODE > Data compression . . . . . . . . . . . . . . . . : *NONE > Intermediate data compression . . . . . . . . . : *NONE > Maximum number of intermediate sessions . . . . : 200 > Route addition resistance . . . . . . . . . . . : 128 > Server network ID/control point name . . . . . . : *LCLNETID *ANY > > Display Controller Description > > Controller description . . . . . . : NEX2APPC > Option . . . . . . . . . . . . . . : *BASIC > Category of controller . . . . . . : *APPC > > Link type . . . . . . . . . . . . : *ANYNW > Online at IPL . . . . . . . . . . : *YES > Remote network identifier . . . . : APPN > Remote control point . . . . . . . : NEX2IP > Autocreate device . . . . . . . . : *ALL > System job . . . . . . . . . . . . : QCMNARB02 > Message queue . . . . . . . . . . : *SYSVAL > Current message queue . . . . . . : QSYSOPR > Library . . . . . . . . . . . . : QSYS > Text . . . . . . . . . . . . . . . : *BLANK > > Display Device Description > > Device description . . . . . . . . : NEX > Option . . . . . . . . . . . . . . : *BASIC > Category of device . . . . . . . . : *APPC > > Automatically created . . . . . . : NO > Remote location . . . . . . . . . : NEX > Online at IPL . . . . . . . . . . : *YES > Local location . . . . . . . . . . : *NETATR > Remote network identifier . . . . : APPN > Attached controller . . . . . . . : NEX2APPC > Message queue . . . . . . . . . . : *CTLD > Current message queue . . . . . . : QSYSOPR > Library . . . . . . . . . . . . : QSYS > Local location address . . . . . . : 00 > APPN-capable . . . . . . . . . . . : *YES > > Display Configuration List > > Configuration list . . . . . . . . : QAPPNRMT > Configuration list type . . . . . : *APPNRMT > Text . . . . . . . . . . . . . . . : Remote APPN list > > -------------------APPN Remote Locations-------------------- > Remote Remote Control > Remote Network Local Control Point Secure > Location ID Location Point Net ID Loc > NEX APPN NEX2 NEX2IP APPN *NO > > System 2 - NEX: > Display Network Attributes > System: NEX > Current system name . . . . . . . . . . . . . . : NEX > Pending system name . . . . . . . . . . . . . : > Local network ID . . . . . . . . . . . . . . . . : NEX > Local control point name . . . . . . . . . . . . : NEX > Default local location . . . . . . . . . . . . . : NEX > Default mode . . . . . . . . . . . . . . . . . . : BLANK > APPN node type . . . . . . . . . . . . . . . . . : *ENDNODE > Data compression . . . . . . . . . . . . . . . . : *NONE > Intermediate data compression . . . . . . . . . : *NONE > Maximum number of intermediate sessions . . . . : 200 > Route addition resistance . . . . . . . . . . . : 128 > Server network ID/control point name . . . . . . : NEX NEX > > Display Controller Description > > Controller description . . . . . . : CTLD NEXAPPC > Option . . . . . . . . . . . . . . : OPTION *BASIC > Category of controller . . . . . . : *APPC > > Link type . . . . . . . . . . . . : LINKTYPE *ANYNW > Online at IPL . . . . . . . . . . : ONLINE *YES > Remote network identifier . . . . : RMTNETID APPN > Remote control point . . . . . . . : RMTCPNAME NEXIP > Text . . . . . . . . . . . . . . . : TEXT *BLANK > > Display Device Description > > Device description . . . . . . . . : DEVD NEX2 > Option . . . . . . . . . . . . . . : OPTION *BASIC > Category of device . . . . . . . . : *APPC > > Automatically created . . . . . . : YES > Remote location . . . . . . . . . : RMTLOCNAME NEX2 > Online at IPL . . . . . . . . . . : ONLINE *NO > Local location . . . . . . . . . . : LCLLOCNAME NEX > Remote network identifier . . . . : RMTNETID APPN > Attached controller . . . . . . . : CTL NEXAPPC > Message queue . . . . . . . . . . : MSGQ QSYSOPR > Library . . . . . . . . . . . . : *LIBL > Local location address . . . . . . : LOCADR 00 > APPN-capable . . . . . . . . . . . : APPN *YES > Single session . . . . . . . . . . : SNGSSN > Single session capable . . . . . : *NO > > Display Configuration List > > Configuration list . . . . . . . . : QAPPNRMT > Configuration list type . . . . . : *APPNRMT > Text . . . . . . . . . . . . . . . : > > -------------------APPN Remote Locations-------------------- > Remote Remote Control > Remote Network Local Control Point Secure > Location ID Location Point Net ID Loc > *ANY APPN NEX NTSERVER APPN *NO > NEX2 APPN NEX NEXIP APPN *NO > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.