Bruce, Got around all of this by backing up the IODF from the test lpar and restoring it to the production lpar. This was just needed to do a software OS config for the Prod Lpar and worked as it should. Thanks.
Bruce Black <[EMAIL PROTECTED]> wrote: > > The problem is that on both lpars the master catalogs are the same names and > the datasets on the test lpar are in the master catalog. Its probably a bad practice to use duplicate master catalog names. make each one unique so they can be accessed by the opposite system. To solve your problem, I suggest backing up the clusters on the test LPAR, deleting them, and restoring them to new names which would put them in a shared catalog. -- Bruce Black Senior Software Developer Innovation Data Processing ---------------------------------------------------------------------- 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 --------------------------------- Do you Yahoo!? Next-gen email? Have it all with the all-new Yahoo! Mail Beta. ---------------------------------------------------------------------- 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
