Thanks... That actually makes sense. :-)
--
Robert P. Nix Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844 Rochester, MN 55905 /( )\
-^^-^^
In theory, theory and practice are the same, but
Robert,
You could use virtual cpuids to create extra nodes, for instance as Rich
said, POLAR2 and GRIZZLY2.
You do that by adding extra lines to the SYSTEM NETID with those extra
cpuids and the new node names.
Then in the directory entry of the TCPIP2 userid, you set the cpuid, based
on the
There are various naming options for the PROFILE TCPIP file to support
various combinations of multiple stacks and systems, but I think I¹ve found
one that isn¹t quite supported...
We run CSE in a two CEC environment. Our z/VM systems are called POLAR and
GRIZZLY. We¹ve had a single vSwitch
On: Thu, Nov 20, 2008 at 01:02:20PM -0600,RPN01 Wrote:
} I set up a second TCPIP virtual machine on POLAR (TCPIP2), and created a
} TCPIP2 TCPIP file for its profile. I was able to bring this up and use it.
} The problem comes if I want to run the TCPIP2 virtual machine on both CECs.
} The two
That doesn't help, though, because the system names remain POLAR and
GRIZZLY, so there isn't a way to get the new TCPIP machines to read the
POLAR2 and GRIZZLY2 profiles, other than naming the virtual machines that
way. What I really wanted to do was to run the same virtual machine (TCPIP2)
on
On Thursday, 11/20/2008 at 03:16 EST, RPN01 [EMAIL PROTECTED] wrote:
That doesn't help, though, because the system names remain POLAR and
GRIZZLY, so there isn't a way to get the new TCPIP machines to read the
POLAR2 and GRIZZLY2 profiles, other than naming the virtual machines
that
way. What
