I just now did several PSWITCH and ACOUPLE commands to clean up from a 
recent mix-up. No problem as long as *each* command includes TYPE= . For 
(I think) historical reasons, omitting TYPE= implies TYPE=SYSPLEX because 
in the Garden of Eden, that was all there was. (See what that snake did?) 
In any case, as long as TYPE= is correct for the couple data set(s) you're 
manipulating, you should have no problem. 

.
.
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
[email protected]



From:   Lizette Koehler <[email protected]>
To:     [email protected], 
Date:   02/10/2014 03:47 PM
Subject:        Re: XCFAS holding OMVS and XCF CDSes
Sent by:        IBM Mainframe Discussion List <[email protected]>



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.



COUPLE INTERVAL(60)                    /* 1 minute */
   OPNOTIFY(60)                        /* 1 minute */
   SYSPLEX(PLEX1)                      /* SYSPLEX NAME*/
   PCOUPLE(SYS1.PCOUPLE,CPLPKP)        /* COUPLE DS */
   ACOUPLE(SYS1.ACOUPLE,CPLPKA)        /* ALTERNATE DS*/
   MAXMSG(750)
   RETRY(10)
DATA TYPE(CFRM)
   PCOUPLE(SYS1.PFUNCT.CTTEST,FDSPKP)
   ACOUPLE(SYS1.AFUNCT.CTTEST,FDSPKA)
DATA TYPE(BPXMCDS)
   PCOUPLE(SYS1.OMVS.CDS01,3390x1)
   ACOUPLE(SYS1.OMVS.CDS02,3390x2)


Lizette


-----Original Message-----
>From: Gary Weinhold <[email protected]>
>Sent: Feb 10, 2014 2:33 PM
>To: [email protected]
>Subject: XCFAS holding OMVS and XCF CDSes
>
>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.
>
>That may be because we come up as a basic sysplex, but don't bring the 
>other lpar up.
>
>Do I have any alternatives?
>
>Gary Weinhold
>Data Kinetics, Ltd.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to