A fix is available
APAR status
Closed as program error.
Error description
When a server loses STP synchronization z/OS systems running in a multi-system sysplex issue IEA394A and spin waiting for a reply. However, some systems will switch to local timing and continue running. These systems are: 1. GDPS controlling system. New function via APARs OA28323 and OA26085 allows the GDPS controlling system to continue running in local timing mode for up to 80 minutes 2. Monoplex systems - systems with PLEXCFG specified as XCFLOCAL or MONOPLEX in IEASYSxx The systems listed above can also switch to local timing even if the server does not lose STP synchronization but an STP sync check occurs where the offset is greater than the TIMEDELTA specified in CLOCKxx. When one of the systems listed above switches to local timing (either due to the server losing STP synchronization or TIMEDELTA being exceeded during STP sync check processing), D ETR wrongly displays STP synchronization. In the reported problem, a MONOPLEX system switched to local timing as TIMEDELTA was exceeded for an STP sync check. The syslog showed: After the server lost STP synchronization 16:29:17.59 D ETR 16:29:17.59 IEA386I 16.29.17 TIMING STATUS 925 SYNCHRONIZATION MODE = STP THIS SERVER IS A STRATUM 2 CTN ID = CGBNET THE STRATUM 1 NODE ID = 002818.M10.IBM.84.xxxxxx THIS IS THE BACKUP TIME SERVER NUMBER OF USABLE TIMING LINKS = 12 THIS SERVER HAS ONLY A SINGLE SOURCE OF TIMING SIGNALS THIS STP NETWORK HAS NO SERVER TO ACT AS ARBITER 16:32:16.37 IEA389I THIS STP NETWORK HAS NO SERVER TO ACT AS BACKUP 16:32:18.44 IXC438I COORDINATED TIMING INFORMATION HAS BEEN UPDATED FOR SYSTEM: SYSA PREVIOUS CTNID: STPCTN CURRENT TIMING: LOCAL 16:35:32.78 D ETR 16:35:32.78 IEA282I 16.35.32 TIMING STATUS 933 SYNCHRONIZATION MODE = LOCAL THE ETR FACILITY IS NOT INSTALLED. After the server regained STP synchronization 16:36:57.36 *IEA265I UNABLE TO SYNC TOD CLOCKS TO STP. CPC CONTINUES IN LOCAL MODE. 16:37:15.48 D ETR 16:37:15.49 IEA386I 16.37.15 TIMING STATUS 939 SYNCHRONIZATION MODE = STP <*** should be LOCAL THIS SERVER IS A STRATUM 2 CTN ID = STPCTN THE STRATUM 1 NODE ID = 002818.M10.IBM.84.xxxxxx THIS IS THE BACKUP TIME SERVER NUMBER OF USABLE TIMING LINKS = 12 THIS SERVER HAS ONLY A SINGLE SOURCE OF TIMING SIGNALS THIS STP NETWORK HAS NO SERVER TO ACT AS ARBITER For a GDPS controlling system that switches to local timing after the server loses STP synchronization, the syslog would show: 09:43:08.06 *IEA381I THE STP FACILITY IS NOT USABLE. SYSTEM CONTINUES IN LOCAL TIMING MODE. 09:43:10.15 IXC438I COORDINATED TIMING INFORMATION HAS BEEN UPDATED FOR SYSTEM: AAIS PREVIOUS CTNID: ISCTEST CURRENT TIMING: LOCAL 09:43:10.15 *IXC410E SYSTEM AAIS LOST SYNCHRONIZATION WITH THE TIMING NETWORK. LOCAL TIMING MODE WILL BE ALLOWED FOR 80 MINUTES. 09:44:11.28 D ETR 09:44:11.28 IEA386I 09.44.11 TIMING STATUS 778 SYNCHRONIZATION MODE = STP <*** should be LOCAL THIS SERVER IS A STRATUM 0 CTN ID = NUMBER OF USABLE TIMING LINKS = 0 THIS SERVER HAS ONLY A SINGLE SOURCE OF TIMING In addition, for the systems listed above that switch to local timing when STP synchronization is lost, after a switch back to STP synchronization, message IEA380I THIS SYSTEM IS NOW OPERATING IN STP TIMING MODE. is not issued.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users at z/OS HBB7770 and above running * * in STP timing mode. * **************************************************************** * PROBLEM DESCRIPTION: This apar addresses 2 problems: * * 1. DISPLAY ETR command response * * incorrectly shows STP timing mode * * when the timing mode switched from * * STP to Local timing mode. * * 2. When in Local timing mode and then * * STP synchronization is restored, * * so that the system has switched * * back to STP timing mode, message * * IEA380I is not issued to inform * * the user that the system is in * * STP timing mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** Both issues occur in the Timing Alert External SLIH, IEATEEIH, during a timing status change event. 1. The field to indicate STP timing mode is incorrectly set during an unsynchronized timing state change. A timing mode change can not be set during an unsynchronized timing state change. 2. The field used to check to issue MSGIEA380I is improperly set causing the check to always fail. Additional keywords: STP/K
Problem conclusion
Both problems can be solved by one solution. In IEATEEIH, fix the check for a synchronized timing state change to correctly set the STP timing mode indicator and the issuance of MSGIEA380I.
Temporary fix
Comments
APAR Information
APAR number
OA41776
Reported component name
TIMER SUPERVISO
Reported component ID
5752SC1CV
Reported release
780
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-22
Closed date
2013-04-23
Last modified date
2013-10-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA68905 UA68906 UA68907
Modules/Macros
IEATEEIH
Fix information
Fixed component name
TIMER SUPERVISO
Fixed component ID
5752SC1CV
Applicable component levels
R770 PSY UA68905
UP13/05/08 P F305
R780 PSY UA68906
UP13/05/08 P F305
R790 PSY UA68907
UP13/05/08 P F305
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
07 October 2013