On Thu, 6 Aug 2009 00:44:20 -0500, Barbara Nitz <[email protected]> wrote:
>What did NOT come down were the three corresponding telnet address spaces >(TCPTNx they're called here). Two of them made OMVS spit out a BPX >message that shutdown was aborted because TCPTNx was blocking it, but the >things did not react to stop commands anymore, cancel resulted in 'use force >arm', and force arm didn't work, either. A good old FORCE was necessary. The >third TCPTNx stayed up through OMVS shutdown and restart, but was >completely broken afterwards, resulting in an IPL. I suspect that these three TCPTNx started tasks are three separate TN3270 Telnet Servers (deamons). When first introduced, (can't recall which version of Comm Server), the installation guide specified the proper command to shut them down. By design, the standalone TN3270 Telnet Servers were to remain active when the TCPIP address space was terminated, with the expectation that TCPIP will restart shortly. ---------------------------------------------------------------------- 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
