According to the digest of IBM-MAIN I receive - in lieu of having a groaning inbox - this post should appear. However there is nothing in the Archives. Could anyone explain this anomaly?[1]
<quote> How to connect jes2 and jes3 on different lpars --------------------------------------------- Arju Hi, We have jes3 on one lpar and jes2 on another. We would like to use tcp/ sna to set up nje between two. Any definiton examples are most appreciated. We have no ncp, only appn. Thanks - Tues, Feb 17 2009 6:39 am </quote> However, let me try to disentangle the query itself. It mentions SNA - and APPN (and even NCP) - so I thought I should have a try at clarification if little else. Arju I could tackle the topic in a somewhat joking manner and suggest that the relatively recent IP support for NJE as described in "Network Job Entry Formats and Protocols", SA22-7539-02,[a] and according to "z/OS JES2 Introduction", SA22-7535-06,[b] and "z/OS JES3 Introduction", SA22-7551-06,[c] implemented by both JES2 and JES3 which does employ TCP as the transport protocol were supported using AnyNet Sockets over SNA thereby enabling the "TCP/SNA" stipulation! [a] http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HAS2A620 [b] http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HAS2A860 [c] http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IAT2A760 Unfortunately, this is not a very practical suggestion since the superb AnyNet Sockets over SNA function was dropped in z/OS V1R8 - more's the shame and pity! If I assume that your "TCP/SNA" stipulation was actually a rather distorted was of saying "SNA over TCP/IP" which in turn was a rather distorted way of saying "SNA over UDP/IP" or "HPR over UDP/IP" we arrive eventually at "Enterprise Extender" which is a current and popular way of dealing with the need to have SNA applications communicate over an IP network. Against this and even favouring my original impractical suggestion is that you insist you have APPN - and no NCP although NCP absent or present is not at all relevant to what I'm guessing you may be wanting to do. But, since it appears that what is really wanted, with all the penumbral information removed, is to set up NJE communication between JES2 and JES3 and assuming the very likely presence of IP connectivity possibly to probably in the form of an intranet, I could go back to my original design and simply remove the impractical insertion of AnyNet Sockets over SNA. In other words, I could propose JES3 to JES2 NJE over an IP network. Note that IP support was included in JES2 NJE with z/OS V1R7 and JES3 NJE with z/OS V1R8.[2] Chapter 12 of the redbook covers NJE with IP but is detailed only in the case of JES2. I'm afraid you may have only the Initialization and Tuning Guide and Reference manuals to help you in the case of JES3. If you really want to use SNA NJE and perhaps use an Enterprise extender logical link over the IP network, post again and perhaps someone will be able to assist. It's handy that your VTAMs are enabled for APPN. Chris Mason [1] I checked on what the Google digest had to say about Arju and followed up on two recent posts. One definitely got into the archives and furthermore stimulated some discussion. This was "How to sort ip address with dfsort ?". Another, "read and write devices for fctc connections", supposedly posted on Jan 16th also did not appear in the archive. Also, using the Google facilities, I see this post did not attract any replies. Since despite the title it concerns the coding of TRLEs I hope to get to that one after this. Interestingly enough there are two queries from last year, one of which went unanswered and one did receive an answer! [2] The z/OS Version 1 Release 7 Implementation redbook claims V1R7 but the manuals only mention IP support in the V1R8 editions. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
