IBM Support

JR42028: TRANSACTION ROLLBACK STATE IS NOT PROPERLY PROPAGATED BACK TO BFM/HTM API CALL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Transaction rollback state is not properly propagated back to
    BFM/HTM API call
    .
    When the BFM/HTM APIs perform a transactional call (e.g.
    bfm.complete()), in certain scenarios the APIs are not aware of
    a set rollback flag and therefore do not indicate/raise the
    problem in the client application.
    

Local fix

Problem summary

  • Problem fixed
    

Problem conclusion

  • Fix will be included in V7511
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR42028

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-23

  • Closed date

    2012-03-12

  • Last modified date

    2012-03-12

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

    IV16023

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

Fix information

  • Fixed component name

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R751 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1"}]

Document Information

Modified date:
07 October 2021