Remember when TCPTN was forced upon us? There was a migration (health) check to make sure in the new release we do have telnet separate from TCPIP. And that was way after OMVS was made restartable.
Now, go and do a F OMVS,TERMINATE (but not as part of the regular shutdown). TCPTN does stay up. Well, after OMVS restart it doesn't work anymore *at all*, and when it terminates, it throws some abend202 dumps, too! Wonna know IBMs reaction to *that*? Paraphrased: "It is documented that TCPTN must be taken down before OMVS". Well, documented most probably *after* the first customer reported an abend when doing the OMVS shutdown. Now, why doesn't it terminate on its own? All the other address spaces dependend on OMVS do! (Even those that had been around when OMVS was NOT restartable!) IBM has 'graciously' accepted a 'requirement' for something that was broken from the start. You may want to 'subscribe' (or whatever the term is) to MR0715091455 and give them hell, too! Regards, Barbara Nitz ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
