Explanation
XCF tried to initialize a data set
as a primary or alternate function couple data set, but found that
it contains sysplex ownership information inconsistent with the ownership
information in the sysplex couple data set. This may indicate that
the incoming data set is currently in use by another sysplex. However,
it may simply indicate that the incoming data set has been previously
used and is not part of the last known couple data set configuration
for the specified type, as recorded in the sysplex couple data set.
For example:
- The data set may have been in use as the primary couple data set,
been removed by a SETXCF COUPLE,PSWITCH command, and is now being
brought back into use as the alternate via a SETXCF COUPLE,ACOUPLE
command.
- The data set may have been in use as the primary couple data set,
and is still named in COUPLExx as the primary couple data set, but
the current IPL is using different sysplex couple data sets that have
no record of the data set's previous usage.
In the message text:
- dsname
- The name of the couple data set.
- volser
- The DASD volume where the couple data set resides.
- typename
- The type of data contained in the couple data set.
System action
Message IXC247D follows this message; XCF prompts
the operator to see if it is acceptable to use this couple data set
for the specified type.
Operator response
Notify the system programmer.
System programmer response
Determine whether the
incoming data set is in use by another sysplex. If so, direct the
operator to reply 'D' to message IXC247D to deny use of the data set.
Take
steps to prevent inadvertent use of a couple data set by two sysplexes.
Change the COUPLExx member so that it does not reference the same
couple data set for both sysplexes, or ensure that the operator does
not specify the wrong couple data set on the SETXCF command.
Source
Cross System Coupling Facility (SCXCF)
Module
Routing code
Descriptor code