IBM Support

PI92087: DFHPIDSQ WAITS ONE SECONDS FOR BTS CLEANUP, AND IT CAN BE TOO LONG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • BTS is used in soap over MQ webservices.
    DFHPIDSQ, in the routine bts_cleanup, is performing a
    delay EXEC CICS DELAY FOR SECONDS(1);
    It can cause problems because if the transaction is using DB2,
    it can lock DB2 rows for too long.
    .
    When a transaction runs the BTS state is updated asynchronously
    and a one second delay is there to allow time for the update to
    complete.
    Without it the acquire_process call in BTS_cleanup might fail.
    .
    

Local fix

  • A possible work around is add an explicit CICS SYNCPOINT at the
    conclusion of the Web Service program, but this would be a
    customer code change.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: There is a one second delay for each    *
    *                      transaction run using inbound web       *
    *                      services over WebSphere MQ when message *
    *                      persistence is turned on.               *
    ****************************************************************
    When web services over WebSphere MQ with message persistence
    are used for an inbound request, on completion of the pipeline
    in DFHPIDSQ there is a one second wait in routine BTS_CLEANUP.
    Given the same scenario without message persistence and the one
    second wait is removed.
    

Problem conclusion

  • In DFHPIDSQ the BTS_CLEANUP routine has been altered to first
    check whether the BTS process is still current, in which case
    the rest of that routine is bypassed without any wait.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI92087

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-05

  • Closed date

    2018-04-09

  • Last modified date

    2018-05-01

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

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

    UI55085 UI55086 UI55087

Modules/Macros

  • DFHPIDSQ
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI55087

       UP18/04/11 P F804

  • R100 PSY UI55085

       UP18/04/10 P F804

  • R900 PSY UI55086

       UP18/04/11 P F804

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

Document Information

Modified date:
01 May 2018