PH10224: EVEN THOUGH AUTORESETTIME=IMMEDIATE IS SET,SOME CICS REGIONS ARE NOT AUTOMATICALLY ADJUSTING THE CICS LOCAL TIME

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The z/OS local time offset was changed from -5 hours to -4 hours
  right about 2AM/3AM. This makes the local time jump from
  02:00:xx straight to 03:00:xx .... exactly 1 hour forward. You
  have AUTORESETTIME=IMMEDIATE specified, yet the time in the CICS
  region is not getting adjusted.
  
  Below in the message log you can see the DFHAC2001 message
  issued at 03.05.32 has a timestamp from CICS in that message
  that says 02.05.32. That is evidence that CICS thinks it is
  02.05.32 while z/OS thinks it is 03.05.32.
  .
  00.00.00 DFHIC0801 applid CICS time altered from 24.00.000
           to 00.00.001 - date 03/10/19 - relative day 126
  03.05.32 DFHAC2001 03/10/2019 02:05:32 applid Transaction'P' is
           not recognized. Check that the transaction name
           is correct.
  03.11.59 DFHIC0801 applid CICS time altered from 03.11.59 to
           03.11.599 - date 03/10/19 - relative day 126
  Additional Symptom(s) Search Keyword(s): KIXREVSCB
  
  .
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: AUTORESETTIME=IMMEDIATE SIT parameter   *
  *                      not honoured.                           *
  *                                                              *
  ****************************************************************
  In the reported problem, a user changed their z/OS time-of-day
  clock.  AUTORESETTIME=IMMEDIATE was specified as a SIT
  parameter. This should have caused CICS to do a PERFORM
  RESET command to synchronize the CICS time-of-day with the
  z/OS time-of-day at the next task attach. This would have been
  evident by message DFHIC0801 being issued - but it was not
  issued.
  
  The user had a START OF TASK TRUE active which did an EXEC CICS
  ASKTIME.  This command caused CSATODP
  (the CICS time-of-day field) to temporarily contain a value that
  matched the z/OS time-of-day value and existing
  AUTORESETTIME=IMMEDIATE logic in DFHZDSP did not detect a time
  difference.
  A CEMT P RESET was required to synchronize the z/OS and CICS
  time-of-day clocks.
  Keywords: msgDFHIC0801
  

Problem conclusion

• DFHAPIN and DFHZDSP have been amended to prevent the
  aforementioned scenario.
  
  The IBM Knowledge Center will have the following update applied:
  Home>CICS Transaction Server for z/OS 5.4.0 & 5.5.0 > Reference
  > Diagnostics > Data Area > CSA - Common system area generator
  
  will have the following field added:
  
  Offset Hex  Type      Len  Name(Dim) Description
  
              AUTORESETTIME trigger management
  138         CHARACTER 4    CSATODP2  Copy of CSATODP
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI64339 UI64340 PH23587

Modules/Macros

• DFHAPIN  DFHCSAD  DFHDSCSA DFHTAJP  DFHZDSP
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R100 PSY UI64340

     UP19/07/23 P F907

• R200 PSY UI64339

     UP19/07/23 P F907

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.