PH55323: TRANSACTION DATA NOT RECOVERED FOR RRS RESOURCES IN LIBERTY ON Z/OS AFTER ABEND

APAR status

• Closed as program error.

Error description

• Transactions that include RRS enabled resources may not recover
  after an abend.
  
  Examples of RRS enabled resources include:
  - DB2 type 2 connection
  - MQ using BINDINGS mode
  - CTG in local mode
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of  WebSphere Liberty feature     *
  *                  zosTransaction-1.0                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: RRS Resources involved in JTA           *
  *                      transactions may not recover after      *
  *                      application server failure.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The zosTransaction-1.0 feature allows RRS enabled resources to
  be enlisted with transactions in Liberty.  When this feature
  is used, the application server must identity itself to RRS
  using a unique Resource Manager Name that the application
  server persists in the workarea.  The application server must
  use the same name across multiple restarts in order to perform
  transaction recovery against RRS resources.
  The workarea is automatically deleted whenever the application
  server performs a clean start.  A clean start occurs when
  either the application server is restarted after terminating
  unexpectedly, service is applied or --clean is specified as a
  startup option.
  After the clean start, the application server would register a
  new Resource Manager Name with RRS under which new
  transactional work would be performed.  The RRS Resource
  Manager List (ATRFPRML) panels would still display the original
  Resource Manager Name in state 'Reset'.  If any transactions
  performed under the original Resource Manager Name required
  recovery then those transactions would remain unrecovered and
  would required manual intervention to complete them
  administratively.
  

Problem conclusion

• The location of the data persisting the Liberty application
  server's RRS Resource Manager Name was changed so that a clean
  start of the application server did not result in the data
  being deleted.
  
  The fix for this APAR is targeted for inclusion in fix pack
  23.0.0.6. For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

• Set the permissions on the application server's
  workarea/rrs/tx directory to 555 (rx, rx, rx) in order to
  preserve the Resource Manager Name in the rmData.log after a
  Liberty server abends, or if the Liberty server is started
  with the --clean option.
  

Comments

APAR Information

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

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

Fix information

• Fixed component name

  LIBERTY PROF -

• Fixed component ID

  5655W6514

Applicable component levels