IEA015A   text

Explanation

In the message, text is:

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).

System action

The system waits for a reply to message IEA015A.

Operator response

Notify the system programmer.

System programmer response

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.

If only a few MVS images issued IEA015A, it is likely that ETR links have failed to those machines. Repair the failed links and then reply with "RETRY" on each issuing system. If the problem was corrected, processing resumes. If the problem was not resolved, the message is reissued until the problem is fixed or until you reply "ABORT". A reply of "ABORT" results in a 0A2-114 wait state if the MVS image is a member of a multisystem sysplex. If it is not, processing resumes in local TOD clock mode.
Note:
  1. When all systems in the sysplex issue IEA015A there is no time limit for making the reply. However, after the first response is given to IEA015A, the rest of the systems must be replied to within a minimum of four minutes. When there are more than eight systems in the sysplex the time limit is calculated using (30 seconds * number of systems).
  2. If not all systems in the sysplex are affected, the systems that are still running can take action for "status update missing" (SUM) on systems waiting for a reply to IEA015A. In this case, the four minute rule does not apply.
If ALL ETR synchronized MVS images issue IEA015A, then there has been a failure of one or both Sysplex Timers. If one Sysplex Timer fails, the other may go into dormant state when it can not communicate with the failed 9037. In this case, it is possible to recover the dormant 9037 and then reply "RETRY" as previously described.
Note: When replying to IEA015A using the Hardware Management Console (HMC), you must select the priority message box.

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).

Source

Timer Supervision

Module

IEATSWLH

Parent topic: IEA messages