I should have amplified. For XCF, there is no such thing as an 'invalid' couple type. If the TYPE= specified is not in use in the sysplex, he does not assume a typo. He assumes that the type named is not (yet?) in use. For the types that are actually in use, issue D XCF,CPL. All in-use couple data sets are displayed along with the type associated with each. Your SETXCF commands must name (or default to) one of those types
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Skip Robinson <jo.skip.robin...@sce.com> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 02/11/2014 07:14 AM Subject: Re: XCFAS holding OMVS and XCF CDSes Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> The problem is that you're using the wrong TYPE keywords. They should be TYPE=SYSPLEX and TYPE=BPXMCDS . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Gary Weinhold <weinh...@dkl.com> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 02/11/2014 07:09 AM Subject: Re: XCFAS holding OMVS and XCF CDSes Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Thanks for the responses, Skip and Lizette, I probably wasn't clear that I did issue SETXCF CPL,ACOUPLE=SYS2.DKLOMVS.CDS03,TYPE=OMVS and received "IXC388I SETXCF COUPLE,ACOUPLE REQUIRES TYPE OMVS TO BE ACTIVE ON THIS SYSTEM" and similarly for TYPE=XCF. I suspect it's something to do with the Basicness of the sysplex (no coupling facility), so I guess updating the COUPLExx PARMLIB members and reIPLing is the only way to go. Gary Weinhold Data Kinetics, Ltd. From: Skip Robinson<jo.skip.robin...@sce.com> (snipped) In any case, as long as TYPE= is correct for the couple data set(s) you're manipulating, you should have no problem. From: Lizette Koehler<stars...@mindspring.com> (snipped) I think the same process you used for the CFRM and LOGR can be used for the others. each one is a TYPE in the environment. I would check the manual, but I think you can create new files and switch them like the CFRM. Or you create new files, update parmlib and IPL. -----Original Message----- > From: Gary Weinhold<weinh...@dkl.com> (snipped) > > I am trying to clean up a volume with several alternate couple datasets > on it. For CFRM and LOGR, I just used IXCL1DSU to allocate alternates > and SETXCF CPL,ACOUPLEd to them and that freed up the datasets so I > could delete them. But the XCF and OMVS CDSes are a problem. I can't > delete them because they're in use by XCFAS (shared enq). SETXCF won't > do anything because "IXC388I SETXCF COUPLE,ACOUPLE requires type OMVS to > active on this system" and the same message for XCF. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
