Explanation
During sysplex initialization, cross-system
coupling facility (XCF) determined that the system is trying to use
a sysplex couple data set that was last used after the current time
on this system. It may be the case that the TOD clock on this system
is either incorrect, or a system with an unsynchronized clock value
has updated the sysplex data set.
In the message text:
- dsname
- The name of the sysplex couple data set that is being initialized.
- volser
- The direct access storage device (DASD) volume on which the sysplex
couple data set resides.
- mm/dd/yyyy hh:mm:ss
- The date and time the sysplex couple data set was last updated
or the date and time of the current system. The date is in months
(1-12), days (1-31), and years. The time is in hours (00-23), minutes
(00-59), and seconds (00-59).
- xx
- The suffix identifying the COUPLE parmlib member.
System action
The system restarts XCF and issues message IXC207A
to request a new COUPLExx specification.
Operator response
Notify the system programmer.
System programmer response
Make sure that all systems
are using the identical time. The problem could be the result of
at least one of the systems in the sysplex having a different time
base than the others. See the consequences of different times being
encountered within the sysplex in z/OS MVS Setting Up a Sysplex.
Some recovery actions have more serious implications than others.
The list which follows attempts to order the actions in increasing
levels of impact.
Have the operator do one of the following:
- Verify the correct sysplex couple data set is in
use. If the wrong sysplex couple data set was specified for this system,
use a different COUPLExx parmlib member which specifies the correct
sysplex couple data set.
- When the time difference is small, and the system clock (or external
time reference, ETR) was changed to reflect a change in local time,
wait until the time difference has elapsed and respecify the same
COUPLExx parmlib member.
- When the current sysplex couple data set was used
in an environment with a system time (or external time reference,
ETR) in the future, the sysplex couple data set(s) is no longer usable
and must be reformatted before it can be used. This allows its time
base, and that of all the systems in the sysplex to be synchronized.
- To continue without a sysplex couple data set, specify COUPLE=**
to IPL in XCF-local mode.
Module
Routing code
Descriptor code