PI41660: UNEXPECTED COMMITS FOR THREADS DURING ABEND PROCESSING MAY CAUSE DATA LOSS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When an abend occurs during processing of a two-phase commit
  transaction, a message may get lost due to the default behaviour
  of the LE processing: If a message was read from an MQ queue and
  is supposed to be inserted in a database table within the same
  transaction, the MQ GET operation is committed, while the SQL
  INSERT operation is rolled back, if an abend occurs in the SQL
  processing thread.
  
  LE Support has documented this behaviour and added an
  environment variable as part of LE APAR PM44718 and extended
  under PI22096 to control the RRS COMMIT/ROLLBACK of abending and
  non-abending TCBs.
  
  WebSphere Message Broker will enable this new environment
  variable for all brokers to ensure the correct transactional
  behaviour with APAR PI17010.
  
  WebSphere BI for FN needs to extend this behaviour to those
  components which do not run under broker control, specifically
  to the FIN Processing FSMs.
  

Local fix

• Temp fix is required
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: UNEXPECTED COMMITS FOR THREADS DURING   *
  *                      ABEND PROCESSING MAY CAUSE DATA LOSS    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Formerly, when an abend occurred during processing of a
  two-phase commit transaction, a message could get lost due to
  the default behavior of the LE processing:
  If a message was read from an MQ queue and is supposed to be
  inserted in a database table within the same transaction, the
  MQ GET operation was committed, while the SQL INSERT operation
  was rolled back, if an abend occurred in the SQL processing
  thread.
  LE Support has documented this behavior and added an environment
  variable _EDC_PTHREAD_BACKOUT as part of LE APAR PM44718 and
  extended under PI22096 to control the RRS COMMIT/ROLLBACK of
  abending and non-abending TCBs.
  

Problem conclusion

• Now, WebSphere BI for FN extends this new behavior to the
  FIN processing FSMs, and no messages can get lost anymore.
  With APAR PI17010 WebSphere Message Broker will enable this
  new environment variable to ensure the correct transactional
  behavior.
  

Temporary fix

Comments

APAR Information

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

  PI41528

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

  UI29307

Modules/Macros

• DNF00175 DNF00178 DNF00185 DNF00197 DNF00238
  

Fix information

• Fixed component name

  SN FIN, SN IA,

• Fixed component ID

  5655FIN01

Applicable component levels

• R11E PSY UI29307

     UP15/07/17 P F507

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.