On 10/01/2012 04:32 PM, David Andrews wrote:
On Mon, 2012-10-01 at 16:48 -0400, Chambers, David W. wrote:
Since you're IPLing the Test LPAR you could temporarily relabel the
BEBS... volumes to the original BEBC... volume serials and respond
with the appropriate reply to the DUPLICATE VOLUME message at IPL
time. And the production volumes would also be offline to your Test
LPAR. Just make sure you've got the right (test) volumes online on the
Test LPAR.
I thought of that, but wasn't altogether clear on what x-system magic
JES2 was doing. Two LPARs on a GRS ring, with their primary JES talking
to the same volsers, but different unit addresses. Wonder if that would
make a mess?
If I were trying this, I would for sure use a stand-alone test LPAR
system that was completely independent from production with production
DASD offline to the test LPAR, test LPAR DASD off-line to prod LPAR, and
no shared GRS ring, coupling facility, or other unneeded communication
with the production environment. When you are deliberately creating
multiple drives with same volser and making a test JES2 that may
essentially "think" it is a production JES2, you want to be
double-double sure that test system cannot touch prod drives or other
prod resources by accident and there are no cross system enqueues or
other unintended cross-system communication to confuse things.
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
