THIS SYSTEM HAS LOST ALL
CONNECTION TO THE SYSPLEX TIMER.
IF THIS EVENT OCCURRED ON SOME,
BUT NOT ALL SYSPLEX MEMBERS,
THE LIKELY CAUSE IS A LINK FAILURE.
TO FIX, ENSURE THAT EACH AFFECTED
SYSTEM HAS AT LEAST ONE CORRECTLY
CONNECTED AND FUNCTIONAL LINK.
IF THIS EVENT OCCURRED ON ALL
SYSPLEX MEMBERS, THEN THE
LIKELY CAUSE IS A SYSPLEX TIMER
FAILURE. TO FIX, REFER TO THE
MESSAGE IEA015A DESCRIPTION IN
MVS SYSTEM MESSAGES.
AFTER FIXING THE PROBLEM, REPLY
"RETRY" FROM THE SERVICE CONSOLE
(HMC). IF THE PROBLEM WAS NOT
CORRECTED, THIS MESSAGE is
REISSUED AND YOU MAY TRY AGAIN.
REPLY "ABORT" TO EXIT MESSAGE LOOP.
PROBABLE RESULT: 0A2-114 WAITSTATE
The system has lost all connections to its sysplex timer(s).
The system waits for a reply to message IEA015A.
Notify the system programmer.
Determine why the loss of Sysplex Timer connectivity occurred, repair the problem, and then reply to the message on each system where it occurs.
There are two basic scenarios for which this message is issues. You should first determine if a subset of the ETR synchronized MVS™ images have issued IEA015A or whether ALL images have issued it.
For more information about how to recognize this condition and how to recover from it, see IBM® Redbooks® publication S/390® Time Management and IBM 9037 Sysplex Timer, SG24-2070. For detailed information, see the topic about last Sysplex Timer lost and last Sysplex Timer lost - extended outage.
See also z/OS MVS Setting Up a Sysplex for the topic on "Understanding PLEXCFG Configurations with a Sysplex Timer". A Sysplex Timer failure can affect the sysplex in several ways, depending on how the sysplex is configured with the PLEXCFG system parameter. This section provides additional information on PLEXCFG and describes different conditions when this message might be issued (for example, with PLEXCFG=MULTISYSTEM and PLEXCFG=ANY).
Timer Supervision
IEATSWLH