IXC250I

Explanation
XCF could not make a data set available as an alternate
couple data. In the message text: dsname
The name of the data set.
typename
The type of data contained in the data set.
reason
One of the following:ANOTHER ALTERNATE COUPLE DATA SET REQUEST IS CURRENTLY BEING PROCESSED
The system is already trying to make a couple data set available
as the alternate couple data set.
THE NEW ALTERNATE DATA SET COULD NOT BE OPENED
The system was unable to open data set dsname.
The data set cannot be used.
THE NEW ALTERNATE DATA SET IS CURRENTLY IN USE AS THE PRIMARY
DATA SET
Data set dsname is already in use as the primary
couple data set.  It cannot be used as the alternate couple data set.
THE NEW ALTERNATE DATA SET IS CURRENTLY IN USE AS THE ALTERNATE
DATA SET
Data set dsname is already in use as the alternate
couple data set.  The request is ignored.
COULD NOT WRITE SYSTEM STATUS RECORD(S) OR LOCK BLOCK(S)
The system was unable to initialize dsname by
writing the system status record(s) or lock block(s) to it. The data
set cannot be used.
COULD NOT CLEAR THE RECOVERY LOCK BLOCKS ON THE NEW ALTERNATE
DATA SET
The system was unable to initialize dsname by
clearing the recovery lock blocks.  The data set cannot be used.
COULD NOT CLEAR THE SYSPLEX LOCK BLOCKS ON THE NEW ALTERNATE DATA
SET
The system was unable to initialize dsname by
clearing the sysplex lock blocks. The data set cannot be used.
COULD NOT CLEAR THE LOCK BLOCKS ON THE NEW ALTERNATE DATA SET
The system was unable to initialize dsname by
clearing the sysplex lock blocks. The data set cannot be used.
COULD NOT WRITE A SEQUENCE NUMBER TO THE NEW ALTERNATE DATA SET
The system was unable to initialize dsname by
writing a sequence number to it.  The data set cannot be used.
THE NEW ALTERNATE DATA SET COULD NOT BE SYNCHRONIZED WITH THE
PRIMARY DATA SET
The system was unable to initialize dsname by
synchronizing it with the primary data set.  The data set cannot be
used.
REQUIRED RECORDS COULD NOT BE READ FROM THE NEW ALTERNATE DATA
SET
The system was unable to read required records from data set dsname.
 The data set cannot be used.
CONSISTENCY CHECKING FAILED FOR THE NEW ALTERNATE DATA SET
Data set dsname failed consistency checking.
The data set cannot be used.
THE FORMAT TOD IN THE NEW ALTERNATE DATA SET IS INCORRECT
The format time-of-day (TOD) stamp in alternate couple data set dsname does
not match the format TOD stamp for the primary couple data set. The
data set cannot be used.
THE SYSTEM IS IN XCF-LOCAL MODE
The system is in XCF-local mode, and cannot use couple data sets.
 The request is rejected.
THE CAUSE OF THE FAILURE IS UNKNOWN
XCF could not determine why the couple data set request failed.
PERMANENT ERROR PROCESSING IS CURRENTLY ACTIVE FOR THIS DATA TYPE
XCF is currently processing a permanent error for this data type.
COULD NOT GAIN OWNERSHIP OF THE DATA
The system was unable to gain ownership of the data for type typename within dsname.
The data set cannot be used.
COULD NOT CLEAR UPLEVEL RECORDS ON THE NEW ALTERNATE DATA SET
The system was unable to clear uplevel records on the new alternate
couple data set for type typename within dsname.
The data set cannot be used.
ORIGINATING SYSTEM DID NOT COMPLETE INITIALIZATION
The system on which the ACOUPLE request originated did not complete
the necessary initialization of the new alternate couple data set.
This indicates a maintenance mismatch. The issuing system requires
an initialization protocol in which the originating system is not
capable of participating.
UNABLE TO SERIALIZE ACOUPLE PROCESS
The issuing system was unable to access the primary sysplex couple
data set to serialize the ACOUPLE request, probably due to an I/O
timeout.
OWNERSHIP INDICATORS INCONSISTENT
The data ownership indicator in the new alternate couple data
set as read by a participating system does not match the information
provided by the system initiating the ACOUPLE request. This indicates
that the two systems are not using the same data set, probably because
the volume serial specified or implied by the ACOUPLE command refers
to different devices on the two systems.
PRIMARY DATA SET EXPERIENCING I/O DELAYS
It is currently unsafe to remove the existing alternate couple
data set because the primary couple data set is experiencing I/O delays.
If the alternate were removed, it could result in the loss of both
couple data sets for the named type if the primary does not return
to normal operation in a timely manner.

System action
XCF may already have removed from use the old
alternate couple data set for the specified type of data, so the sysplex
may be running without an alternate couple data set.

Operator response
 If the message text contains ORIGINATING
SYSTEM DID NOT COMPLETE INITIALIZATION, reissue the SETXCF COUPLE,ACOUPLE
command from any system that issued this message.
If the message
text contains UNABLE TO SERIALIZE ACOUPLE PROCESS or
PRIMARY COUPLE DATA SET EXPERIENCING I/O DELAYS, check for indications
of I/O delays affecting the primary sysplex couple data set. Reissue
the ACOUPLE command after correcting any problems.
Otherwise,
notify the system programmer.

System programmer response
Make a different alternate data set
available, or delete and reformat data set dsname to
make it available.
If the problem persists, search problem reporting
data bases for a fix for the problem.  If no fix exists, contact the IBM® Support Center.

Source
Cross System Coupling Facility (SCXCF)

Module
IXCL1AA

Routing code
1,2

Descriptor code
4