On Mon, 28 Nov 2005 14:59:00 +0200, Gil Peleg <[EMAIL PROTECTED]> wrote:
>Maybe they should introduce the same kind of processing done by APAR
OA07640
>in case of an operator initiated SETXCF COUPLE,PSWITCH ??
Gil,
APAR OA07640 does not change the processing for removal of a couple
data set for operator-initiated PSWITCH or for any other reason. All it
does is periodically probe to determine the accessibility of couple data
sets, so an infrequently-accessed CDS that has become inaccessible can be
removed from service and replaced with a usable CDS in a timely manner,
preventing the other CDS from becoming a single point of failure.
It was implemented this way precisely because it is not possible to
do what you suggest. When a system determines that a couple data set has
become inaccessible, it initiates removal of the CDS. The protocol does
not permit another system to reject the removal of that CDS, nor is there
any way to make it do so without unacceptable migration and compatibility
issues. As Barbara Nitz pointed out, data integrity concerns require that
all systems in the sysplex use the same CDS configuration. If one system
determines that some CDS is unusable, all other systems must also stop
using that CDS, whether or not they still have access to it. The matter
is not subject to a vote.
Bill Neiman
z/OS Development
----------------------------------------------------------------------
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
