FWIW - I use an entirely separate second "TCPIP Subsystem", complete with it's own TCPIP server. So I've got TCPIP (my primary TCPIP subsystem with it's stack), TCIPIPA and TCPIPB - all running completely independent of one another, all with their own hardware, IP addressing and service virtual machines (i.e. TCPIPA has ROUTEDA, NAMEDA; TCPIPB has ROUTEDB, NAMEDB, etc. etc.).
Not only can I bounce the target TCPIP virtual machine without it impacting other TCPIP subsystems, but if one fails entirely - I have the others as backup. This is particularly helpful when, for example, you need to bounce your primary TCPIP virtual machine and are at a remote location - just connect using TCPIPA or TCPIPB so that your TN3270 session won't disappear when the primary TCPIP virtual machine is taken down. Not a lot of work IMHO. :) Michael Coffin, President MC Consulting Company, Inc. PMB 123 289 Park Street Stoughton, Massachusetts 02072 Voice: (781) 344-9837 FAX: (781) 344-7683 [EMAIL PROTECTED] www.mccci.com We employ aggressive SPAM filters. If you cannot reply or send email to mccci.com go to www.mccci.com/spamblockremove.php -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern Sent: Wednesday, January 04, 2006 1:08 PM To: [email protected] Subject: Re: TCPIP stacks I use a second stack on both sides of a z890 for TELNET and some specialized services across a HiperSocket. It took about 30 minutes to make the necessary updates to the appropriate DTCPARMS and to create the directory entries. Creating the full suite of application servers to go with a second stack would be much more work and I would not want to do it without a great deal of justification. /Tom Kern /301-903-2211
