Larry > Thank you all who replied
Thanks gratefully accepted - if Luke and Elardus don't mind me speaking for them. > The CoD didnt say anything about the change so I missed it Well the "CoD" - whatever that is, and you must excuse my not knowing since I lead a sheltered life - seems to have fallen down on the job "big time" assuming it is the purpose of a "CoD" to warn you of all necessary changes. >From the ways it is structured, I would expect that the NFS - that is, in this case, the Communications Server(CS) "New Function Summary" manual - should be your guide for necessary changes when changing releases with CS. I have seen manuals such as the NFS offer a "what to do" when you are moving from VaRb to VcRd sections but I guess this has just become too much work. Thus the V1R9 one http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1F230/ merely says what is new. In the case of the possibility to run the TN3270E server in a separate address space you need to have noticed what is said in the NFS for V1R6 http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1F200/ All of which implies that you need to be sure that you pay attention to whatever set of NFS manuals you may have been skipping over. > I am currently going through all my current parms and parsing them, then I will place them where needed. I'm not sure I would characterise setting up a new address space as simply shuffling parameters - but meaning changes with the individual. Just watch out that you go on bended knees to the RACF group for the necessary changes or you will be - as one amusing systems programmer with whom I have worked has it - "RACFed"! There is also the messy business of how to ensure the new - and possibly not really wanted - TN3270E address space is brought into life along with all the other system components, the CS IP ones included. IMNSHO rather stupidly, it is expected that you have an automation facility available to manage this problem in the case of the new TN3270E server address space for you since you can no longer rely on the handy AUTOLOG function. My personal recommendation if you simply want a quiet life - and do not care that the TN3270E server takes an age to initiate - because in your case it doesn't at all - is to set up a SCHEDxx PPT entry for the new TN3270E program, EZBTNINI, which mimics the IEFSDPPT PPT entry in all respects except that it imposes cancellable in place of noncancellable - for which setting there is no justification whatsoever in this world! http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2e281/69.6 http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2e281/69.7 That way you can use the handy AUTOLOG function for the TN3270E address space just as you do today with all the other server address spaces which indicate their health with a "listening" socket. - Incidentally what you refer to as "TCP" is only one, the most popular certainly, of the transport layer options associated with IP-based packages of software- and, of course, it *is* the one used by the TN3270E server. I have been obliged with mildly gritted teeth to accept that "TCP" in your case refers to the IP component of z/OS Communications Server (CS) which, because of its ancestry having originally been "TCP/IP for MVS" - derived from "TCP/IP for VM", with slightly twisted arm I accept being described as "TCP/IP" but I really tend to prefer CS IP if you want the shortest logical abbreviation. Note that, if you ever want to refer to a function supported by CS IP which has no truck whatsoever with the transport protocol TCP such as, for example, Enterprise Extender or the Network File System (NFS) in the days when I worked with it, your abbreviation ceases to hold any water at all. Chris Mason On Tue, 21 Dec 2010 09:53:39 -0600, Larry Macioce <[email protected]> wrote: >Thank you all who replied >The CoD didnt say anything about the change so I missed it >I am currently going through all my current parms and parsing them, > then I will place them where needed. >Again thank you >Larry ---------------------------------------------------------------------- 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
