Allan The reason you were able easily to convert your NJE to be IP-based is that NJE now offers a direct socket interface to the IP network.[1] One can say that NJE has been IP-enabled.
The same is not true in the case of TSO which requires to use a VTAM API interface to the SNA network. The closest equivalent to TSO with an IP-enabled application is the z/OS UNIX Telnet server (otelnetd). I don't expect that necessarily meets all the requirements of your system programmers - but perhaps it does some. Reflecting on your post - as one does taking a shower <g> - there came to mind the famous Irish "local" who, when asked how to get somewhere replied something like "Well now, if I was wanting to go there, I wouldn't be starting from here, so I wouldn't." In more prosaic language, the question is "What do you *really* want to do?" I have a vision of your system programmers sitting at their desks with a PC in front of them. The PC will have a TN3270 (possibly -E) emulator which can start multiple connections to a number of TN3270 servers and a connection with each server can be selected from the "Start" "tab" - or equivalent - and can be resumed after "minimising" from an identifying "tab" in the "task bar" - or equivalent. So with your IP network extending from each of your LPARs to the PCs on your system programmer's desk, why not just enable the Communications Server TN3270 server in as basic a way as you like on each of your LPARs.[2] And you can do all of this with z/OS V1R4 as well as z/OS V1R7. Just a thought. Incidentally if the IP path from your system programmer's desk to any one LPAR happens to pass between LPARs it may well find itself using your HiperSockets connection so you will have achieved your objective. I guess this means you will have "started from here". The trouble is I worked out the above only after I had speculated on what might be the minimal implementation of APPN - in order to support Enterprise Extender as Pat indicated - which would meet the requirement of supporting just your TSO applications on your LPARs. If my idea of connecting to each individual LPAR's z/OS image through a local TN3270 server doesn't meet your requirements, please post again. Another qualification is that I am taking into account your later post indicating that all other SNA traffic involving your "glass house", if there ever had been any, has been somehow migrated already. That is, there is no SNA CICS, SNA IMS and so on. Note that it's always best to keep discussions "online" since it feeds the archives with information which may turn out to be useful. [1] Washington Systems Center Technical Bulletin Network Job Entry Formats and Protocols for System/370 Program Products GG22-9373 June 1986 used to be the book which defined NJE protocols. With the introduction of IP support, this book has been revived, with additions, as Network Job Entry Formats and Protocols SA22-7539 which you will find on the online bookshelves together with the JES2 manuals from V1R7. [2] Often the requirement for customers wanting to dispense with SNA is to be able to limit SNA to the "glass house" with IP tentacles reaching out into the world at large. What I have suggested here is that the SNA network which TSO insists on using will be limited to logic within each LPAR, never even seeing the artificial light of the "glass house" - although, come to think of it, that applies also to HiperSockets paths. Chris Mason ----- Original Message ----- From: "Staller, Allan" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Thursday, 01 February, 2007 9:33 PM Subject: Vtam migration > We have multiple LPARs in a single CEC and have just migrated our > NJE/SNA connections routed over a 2216 switch > to NJE/TCPIP over HIPERSOCKETS (works like a champ). > > We would next like to migrate our TSO VTAM cross LPAR routing over > hipersockets also. > > Can anybody post a sample of working SNA defintitions to perform the > same routing for TSO/VTAM. > > I have RTFM'ed many FM's and I am getting very confused. > > Fell free too contact me offline if necessary. > > Thanks in advance... > > Al ---------------------------------------------------------------------- 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
