Hello:
We have the following situation when trying to activate and IPL 3
lpars from site A into site B.
Both sites are distant about 450 Km and the storage replication is made by
Global Metro Mirror.
The issue we have faced last weekend is related to match the IODF we have
received from the team which is responsible for the box in site B. We have
the SYS1.IODFE0 with all the definitions for the box in site B where they
have more lpars than just our 3 defined there.
In site A where my team is responsible for the SYS1.IODFxx we have
pointed in LOADxx with **.
When trying to IPL the same lpars in site B we are configuring in
LOADyy with IODF = E0.
There was something wrong with this configuration because in the
VOLUME where the SYS1.IODFE0 is located, it didn't match with the
configuration in HSA.
Perhaps someone from the site B have validated new IODF for other
lpars than the 3 we have defined and the IPL didn't came up returning an
error which wait state code is 0F indicating a mismatch in the volume or
with the dataset (it looks like it didn't found the dataset or the
configuration).
Does anyone here could give us tips on how to have the configuration
working for both sites without worrying about changes in terms of IO
configuration not related to our lpars ??
Thanks in advance for any help.
Regards,
Gilson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
