A fix is available
APAR status
Closed as program error.
Error description
The intent of the AUTORESTTIME=IMMEDIATE parameter is to sync the CICS internal clock with the MVS clock as soon as a USER task is attached. On a *very* quiet system, this may not occur. Or, a system may have conversational tasks 'running' but are suspended. When these are re-dispatched, they will not drive DFHAPIN which would check the clocks will drive a resync should one be necessary.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All. * **************************************************************** * PROBLEM DESCRIPTION: AUTORESETTIME=IMMEDIATE may not always * * synchronise CSATODP with the z/OS * * clock. * **************************************************************** * RECOMMENDATION: * **************************************************************** Sit option AUTORESETTIME=IMMEDIATE will synchronize the CICS time-of-day ( CSATODP ) with the system time-of-day ( the MVS clock ) if, at the next task attach, the CICS time-of-day differs from the system time-of-day. CICS will issue message DFHIC0801 when the times are synchronized. . However, this mechanism relies on task attach logic to drive the resync code. If the system is an extremely quiet one with no new work entering the system then it is possible the CICS and system time-of-day fields can remain misaligned. . In the reported problem, an MVS time change was performed for daylight savings and an extremely quiet CICS system had a vendor product in a SUSPEND. No new work entered the system but when the vendor product came out of its suspend, ( note that no ATTACH logic is driven ) it expected to find the CICS and system time-of-day clocks aligned. They weren't, this resulted in the vendor product taking its error code path. Keywords: ICV
Problem conclusion
DFHZDSP ( system task TCP ) runs regularly - even in a quiet CICS system. It will now also detect a mismatch between the CICS and MVS time-of-day clocks and if it detects they are out of sync, will attach a system task to perform an IC reset.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI39631
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-22
Closed date
2015-10-01
Last modified date
2017-03-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI31666 UI31667 PI78307
Modules/Macros
DFHZDSP
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
16 March 2017