IBM Support

PK48346: TIMESTAMP DIFFERENCE IN WSAS AND CICS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Timestamp difference in WSAS and CICS
    
    An application has the following setup:
    .
       IHS => WSAS  =MQ=> CICS (1) =MRO=> CICS (2)
    .
    An http request comes into IHS and the application on WSAS
    generates a message and puts a timestamp (obtained by date()
    in java.util.Date) into the message.  The message will be
    passed into MQ and then passed to CICS (1).  The message
    will then trigger a transaction in CICS (1) for message
    translation and then use an MRO link to send the message to
    CICS (2).
    .
    Please note that all the components are on the same LPAR. And
    the intermediate CICS will not alter any context of the
    message being sent from WAS.
    .
    It was found that the time obtained in WAS and CICS (2)
    region (both are running on the same z/OS LPAR) do not
    synchronize.  This has caused messages to be dropped in the
    CICS (2) region.  The CICS (2) region will drop the incoming
    messages when either one of the following conditions are met:
      1) timestamp in CICS (2) > time obtained in WAS + 20 seconds
      2) timestamp in WAS  >= timestamp in CICS (2)
    .
    This means that the timestamp obtained in WSAS is before
    (or leads) the timestamp in CICS.
    .
    This APAR is being taken by CICS to further investigate the
    problem.  It looks like the problem may be in the CICS
    ABSTIME calculation within DFHEIDTI.  This problem will be
    investigated to determine the appropriate resolution.
    .
    Additional Keywords:
    WebSphere Application Server
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: The time returned from CICS ASKTIME is  *
    *                      earlier than the time returned from     *
    *                      WSAS.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application compares the time from WSAS (Web Services
    Application Server) with the time from CICS ASKTIME (returned
    in EIBTIME copied from CSATODP), expecting the time from
    CICS ASKTIME not to be earlier.  However, in some instances,
    the time from CICS ASKTIME can be a second earlier than the time
    from WSAS.  The reason for this difference is that CICS ASKTIME
    converts the milliseconds to units of 1/300th seconds and in
    doing so loses accuracy.
    
    Additional keyword: CSAJYDP
    

Problem conclusion

  • DFHEIDTI and DFHEIIC have been changed to obtain accurate
    values of time and date from the TIME macro to be used in
    the calculation of EIBTIME and EIBDATE.  ABSTIME has also
    been updated to stay consistent with the new date and time.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK48346

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-04

  • Closed date

    2007-10-23

  • Last modified date

    2007-11-02

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

    PK34836

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

    UK30528

Modules/Macros

  •    DFHEIDTI DFHEIIC
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R500 PSY UK30528

       UP07/10/26 P F710

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":"3.2","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":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 November 2007