> We have (by oversight) an active base sysplex with CFRM couple datasets > defined in COUPLExx. As it is a base sysplex there is obviously no active > CFRM policy. Are you sure you don't have an active CFRM policy? The policy that was last active on those CFRM CDSs would have been activated, no matter if the CFs defined to it are there or not.
You could try setxcf stop,policy,type=cfrm (caution - I have never tried it before). > Is there any way to remove the CFRM dataset definitions from the running > sysplex without a sysplex-wide IPL to re-drive COUPLExx once the definitions > have been removed? Not that I know. Even worse, even if you do a sysplex-wide IPL and have the CFRM CDSs physically deleted (so they're not there anymore) and removed from COUPLExx a D XCF will still show them as defined/active/available (*there*) because that information is kept in the sysplex CDS. At least this was the way it worked about 10 years ago when I tried to get rid of the unused CDSs in the D XCF display. I haven't deliberately retested it. Back then, I could only get rid of those displays by doing a sysplex wide true cold start with a freshly formatted sysplex CDSs. At about the same time I lost any awe I may have had at the prospect of a sysplex wide cold start. Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
