Thanks all for the info. We're a simple 2 LPAR Monoplex (3rd Linux soon) and
I didn't explain myself well on one point - a problem I suffer from :)...
I too believe in keeping it simple. It was a mistake/poor choice in creating
my initial IODF with a SYS1 HLQ. The SYS0 HLQ we previously used was in a
common shared Ucat and it worked well for us. The only problem I have is in
getting the PROD LPAR back to a common SYS0.IODFx without an IPL (and maybe a
POR). From message CBDA836I it seems only the IODF suffix can be changed so I
can't ACTIVATE SYS0.IODFx.
CBDA836I IODF data set name SYS0.IODF05 is not comparable to source
IODF data set name SYS1.IODF05. Activation is rejected.
Explanation:
The IODF currently in access by HCD must be comparable to the IODF
which was used for IPL and which is the source IODF in the
activation process. Comparable means that both IODF names must be
equal except the xx suffix of the 'nnnnnnnn.IODFxx' production IODF
naming scheme.
System Action:
None. HCD processing is ready to continue.
User Response:
Use another IODF in HCD whose name is comparable to the IODF used
for IPL.
If I IPL Test and ACTIVATE a SYS0 from the Test LPAR I think the token will
get messed up for Prod and I would only be able to make software changes
afterwards on Prod until an IPL.
Is there anything that I'm missing or am I just stuck until I can IPL Prod?
Thanks again,
Robert
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
