<SNIP> TCP/IP DNS names are yet another name choice you get to make. Sysplex distributor, especially when coupled with Cisco local director, is supposed to allow you to specify the "cluster" IP name and get routed to
the image with the best chance of fulfilling your request in the shortest amount of time. Even if you use DNS names that direct you to a specific system (like in the olden days), things can get really interesting when you use VIPA. <SNIP> Yes, I already deal with this problem. We have people who start an application and then a second copy using different ports who just can't understand why the second copy sits and does nothing when the first copy ends. And so my point about the TCP/IP was, EVEN if you had unique names for the stacks (and only run one stack per z/OS), that with all the JES images using the name of MVSA, you could connect to MVSA while your application was running on MVSA'. Then your next attempt might go to MVSA''. So, while VIPA would solve that (because the address belongs to the application in question), other things would get more and more confusing. Which I think was your original point (which I was agreeing with while trying to demonstrate just how loony this would/could get if you continued down this road far enough). Regards, Steve Thompson -- Opinions by this poster may or may not be those of poster's employer. -- ---------------------------------------------------------------------- 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
