PI72566: ABEND0C4 AT BBGZSCFM+377E OCCURS DURING CLIENT BIND

APAR status

• Closed as program error.

Error description

• The abend0C4 occurs during client bind.  The client is
  attempting to determine if tracing is enabled by looking in
  a
  process level name token for trace information.  It appears
  there was also a Liberty server in this address space, that
  did
  not stop cleanly, and it has left a process level name token
  with tracing information in it.  That name token data
  references a static C variable which has since been released
  when module libzNativeServices.so was unloaded. The client
  should not be looking at the server's name token to
  determine
  the trace level.  This sort of tracing is not available in
  the
  client.  This APAR will correct this.
  
  CICS joblog contains this message:
  DFHAP0707  An abend (code 0C4/AKEA) has occurred in
  task related user exit program BBOATRUE.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty for z/OS                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: An ABEND0C4/ABENDS0C4 or CICS ABEND     *
  *                      AKEA occurs in program BBOATRUE when an *
  *                      embedded Liberty server is configured   *
  *                      in CICS.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a Liberty server and a WebSphere Optimized Local Adapters
  (WOLA) client are sharing the same address space, the client can
  incorrectly use the server's trace settings, which are stored in
  process level data.  If that Liberty server is recycled, some of
  that process level data becomes invalid, and the trace settings
  can no longer be found.  This leads to an ABEND0C4/ABENDS0C4
  when the client attempts to determine the trace level.
  

Problem conclusion

• Code was added to prevent the client from reading the server's
  trace settings when the server and the client are running in the
  same address space.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 17.0.0.1.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

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

• RCD0 PSY

     UP