I'm not currently in a position to look this up in a manual, but in general parallel sysplex configurations do not require system outages to modify, nor are such outages commonly advised. While the procedure you outline may work, I'd explore doing your migration dynamically with no outages at all.
-- Migrate to new SHRCDS nondisruptively vis OS commands -- IPL a new sysplex member nondisruptively The biggest strength of doing these things dynamically is that if something is wrong, you get an error message, and life goes on. When you implement changes at IPL, problems may well cause IPL to fail. . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: "Buckton, T. (Theo)" <[email protected]> To: [email protected] Date: 04/14/2011 04:36 AM Subject: SMSVSAM Sharing control data set - delete and activate Sent by: IBM Mainframe Discussion List <[email protected]> Please advise: We need to activate new sharing control data sets for SMSVSAM. Our plan is: - terminate the SMSVSAM address space - delete the active and space shcds (v sms,smsvsam(shscds),delete - IPL the machine (reason: new lpar is added to the sysplex) -activate the new shcds on current and new lpar. - display the SMSVSAM address space. Please confirm if these steps are correct and in the correct sequence. Regards Theo ---------------------------------------------------------------------- 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
