On Wed, 4 Jan 2006 12:20:09 -0500 Alan Altmark said: >On Wednesday, 01/04/2006 at 12:02 EST, "Wakser, David" ><[EMAIL PROTECTED]> wrote: > >> I need to know: is there anything special needed to be done if I >> want to set up a second TCP/IP stack in VM (using its own OSA address)? >I >> want to use a 2nd stack, during testing of some new types of >connections, so >> that I do not need to disturb the CURRENT stack in case anything needs >to be >> reconfigured. >> >> By the way, this is in VM 2.3 > >1. Clone the application server you need, too (e.g. FTPSERV2) >2. Modify the PROFILE TCPIP, changing the OBEY, PORT, and AUTOLOG >statements to point to the second set of application servers. >3. Ensure the second set of application servers are using a copy of TCPIP >DATA that contains "TCPIP TCPIP2" (for example) so that they use the >second stack. You may also wish to change the HOSTNAME.
Or you can use labeled values so that a single TCPIP DATA file is used for all stacks, and a SET CPUID changes the default stack. (or directory entry). We run many (>>2) TCPIP stacks all off of one TCPIP DATA file. If you do go the multiple TCPIP DATA files, before you get a thrashing, I would reccomend using the :exit to copy it to the A-disk rather than simply placing it on the A-disk, or modifying the PROFILE EXEC to do the work. (You could also have the exit zap the file name in the module to TCPIP TCPIP2, but that is left as an exercise for the reader) > >If the OSA connection (LCS mode only, no OSD!) is "live", then you'll also >need to change IP addresses. > >Alan Altmark >z/VM Development >IBM Endicott
