Bobby, For a more expansive review of using the "Record Qualifiers" in "SYSTEM CONFIG", see the post on this listserve at: http://listserv.uark.edu/scripts/wa.exe?A2=ind1002&L=IBMVM&P=R6649&I=-3&X=1C6106111E9F2D0425&Y=Mike.Walter%40hewitt.com (watch out for any URL wrap)
For Bobby and EVERYONE ELSE who does not YET know how to search this listserve's archives: ------------------------------------------------------------------------------------------ You might also want to invest a few minutes learning how to search the listserve's archives at: http://listserv.uark.edu/archives/ibmvm.html There's an incredible amount of information available from people who have already trod the path that you're just beginning to go down. Searching the archives can answer immediate questions immediately (instead of overnight), and can also help to keep you from trodding down that path with a self-inflicted gunshot wound. It is very much worth the short time learning to search the archives - especially when you need help in the middle of the night or on a weekend when fewer souls are answering posts here. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Bauer, Bobby (NIH/CIT) [E]" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 08/12/2010 11:10 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: Disaster Recovery TCPIP Address Issue Would this be done with the SYSTEM_IDENTIFIER statement in the SYSTEM CONFIG and if so, how do I find my current model and cpuid? Looks like the 'q cupid' will give it to me. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -----Original Message----- From: David Boyes [mailto:[email protected]] Sent: Thursday, August 12, 2010 11:34 AM To: [email protected] Subject: Re: Disaster Recovery TCPIP Address Issue >location. While discussing our requirements, the topic of TCPIP addresses >came up. Since the addresses at the offsite location will be different >from our local addresses, we are at a loss as to how to change them. The vendor should be able to give you the CPUIDs of the recovery systems you'll be running on during your test. Add those to SYSTEM NETID and SYSTEM CONFIG with different node names (I use DISASTER). Once that's done, when the system comes up, you can use qualifiers in the TCPIP PROFILE and SYSTEM CONFIG to set up things with the addresses of your disaster recovery system, kinda like this (not precise syntax, so RTFM for it): NORMAL: LINK FOO xxxx DISASTER: LINK FOO yyyy Presto, no need to change anything actually AT recovery site. 8-) -- db The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
