>A hypothetical question. What are the major implications of changing >the sysplex name? What are the gotcha's?
>- a fairly large parallel sysplex with > 15 participating lpars >- 60+ terabytes of DASD, mostly SMS managed >- SMSPLEX same scope as SYSPLEX >- Sysplex restart needed(all systems down at once) >- Re-allocation of various system datasets with sysplex name as a >qualifier >- New CF policies The biggest gotcha (in my opinion) is that you have to define all new couple data sets - the sysplex name is in all of them, not just in the CFRM CDS. You will do a real cold start on freshly formatted datasets. Come to think of that - I am not sure how to handle the LOGR CDS if you cannot cold start the log stream. (We did not have that problem.) In addition, you don't get a 'test' in the sense that you can do things before all systems are taken down. Changing &sysplex (and possibly the related symbols derived from &sysplex) everywhere in the data set names is hard work. In our case, it wasn't just 'system data sets'. Some of those need the historical data that were in them, written right until the system was taken down. Regards, Barbara Nitz ---------------------------------------------------------------------- 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
