IBM Support

PH07233: CICS Task.commit() and Task.rollback() throw InvalidRequestException when executed in a JTA transaction

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Task.commit and Task.rollback are prohibited inside a JTA
    transaction and currently issue an exception.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS Task.commit() or Task.rollback()   *
    *                      in a JTA transaction causes an          *
    *                      InvalidRequestException.                *
    ****************************************************************
    CICS Task.commit() and Task.rollback() is disallowed in a JTA
    transaction and an InvalidRequestException is thrown.
    
    With DB2 Connection.commit() or Connection.rollback(), the DB2
    driver is aware that it's running in CICS and asks CICS to
    coordinate by calling Task.commit()/Task.rollback() also
    resulting in an Exception.
    
    Problems also occur when using a Liberty dataSource with a type2
    connection within JTA, specifically when container managed and
    the user is not in control of the user transaction as in the
    case of JSR 352 batch.  If the user application attempts a DB2
    connection close, the exception is thrown.
    

Problem conclusion

Temporary fix

Comments

  • Task.java has been changed to ignore a Task.commit or
    Task.rollback when within a JTA transaction. As a result the
    restriction that DB2 JDBC type 2 connectivity is not supported
    for batch persistence is removed.
    
    The 'Liberty features' topic in the CICS Transaction Server for
    z/OS 5.4.0 Knowledge Center will be updated to remove the
    following restriction associated with the batch-1.0 feature:
    
    'DB2 JDBC type 2 connectivity is not supported for batch
    persistence.'
    

APAR Information

  • APAR number

    PH07233

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-14

  • Closed date

    2019-02-21

  • Last modified date

    2019-03-01

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

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

    UI61425

Modules/Macros

  • DFJ@H356 DFJ@H415
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R10D PSY UI61425

       UP19/02/26 P F902

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

Document Information

Modified date:
01 March 2019