OA48019: RRS COMMIT AFTER PTHREAD ABNORMAL TERMINATION WMB

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A user running a multi-thread POSIX application using multiple
  RRS Contexts (native & private) across multiple threads
  experiences unexpected commits on any incomplete transactions if
   the process is forced to terminate abnormally.
  The user might reasonably expect all incomplete transactions to
  be rolled back if the process is forced to terminate abnormally.
  If environment variable _EDC_PTHREAD_BACKOUT is set to YES then
  the Language Environment will attempt to perform a rollback on
  each thread during abnormal termination but this will only
  rollback the RRS Context which is the current context and not
  all context's belonging to each thread. If the current context
  is a private context then the native context will not be rolled
  back, but will be committed.
  
  In the context of WebSphere Message Broker (WMB) if a customer
  is running a message flow involving MQ and DB2 work and some of
  the DB2 work is set to be done under a transaction scope of
  'commit' then a user maybe observe that any MQ and DB2 work
  done under the transaction scope of 'automatic' is committed
  instead of being rolled back if an abend occurs whilst
  executing the 'commit' scope work.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users running z/OS HBB7780 and above.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: In support apar for USS apar OA48017    *
  *                      and Context Services apar OA48021.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Need to provide Supervisor support for USS apar OA48017
  and Context Services apar OA48021.
  

Problem conclusion

• Added a field in the TCB to support USS apar OA48017 and
  Context Services apar OA48021.
  

Temporary fix

Comments

APAR Information

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

  PI41400

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

  UA78527 UA78528 UA78529

Modules/Macros

• IKJTCB
  

Fix information

• Fixed component name

  TASK MANAGER

• Fixed component ID

  5752SC1CL

Applicable component levels

• R7A0 PSY UA78527

     UP15/08/19 P F508

• R780 PSY UA78528

     UP15/08/19 P F508

• R790 PSY UA78529

     UP15/08/19 P F508

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.