I trust this has been resolved. As of z/OS 3.1, a "modern" sysplex couple data set is required. That means one where the input to the format utility (IXCL1DSU) specifies ITEM NAME(SSTATDET) NUMBER(1). You should of course format at least two such CDS so you can have both a primary and alternate. Preferably more so that you can have spares ready to be brought into service if either of those should become inaccessible or unusable.
So ... you would run the format utility to create such a sysplex CDS and then get it to become the primary CDS in your sysplex. The cleanest would be to issue a SETXCF COUPLE command from some system in the sysplex to ACOUPLE the new CDS as the alternate sysplex CDS, then issue SETXCF COUPLE to PSWITCH it so it becomes the primary CDS. Then ACOUPLE the newly formatted alternate. You would then be able to IPL a z/OS 3.1 system into the sysplex. Don't forget to update your COUPLExx parmlib members to reflect the new CDS. You could also update the COUPLExx parmlib member to point at the newly formatted sysplex CDS and reIPL the sysplex. None of the above impacts the CDS used by WLM. Mark Brooks z/OS Sysplex Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
