PI13204: WMB FOR Z/OS V8.0 : GLOBAL CACHE CATALOGS SLOW TO START WITH NON-EXISTENT HOSTNAME

APAR status

• Closed as program error.

Error description

• When using the global cache, configured with multiple catalog
  servers on multiple machines, each catalog server knows the
  hostname (or IP address) of the other catalog servers.
  
  A problem occurs when some (at least 2) of the catalog servers
  are on hosts/IP addresses that exist, but the others are on
  hosts that do not exist. In this case, the broker that is on
  the existent host can be started, but the cache components may
  take more than 10 minutes to start.
  
  This can occur, for instance, in a two broker cache, where each
  broker is configured to host two catalogs, and the machine
  hosting one of the brokers is unavailable. Or if virtual IP
  addresses are being used on z/OS, which exist only for the
  lifetime of a broker task.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker V8.0 and IBM Integration
  Bus V9.0 who use the global cache with multiple catalog servers.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  When using the global cache, configured with multiple catalog
  servers on multiple machines, each catalog server knows the
  hostname (or IP address) of the other catalog servers.
  
  A problem occurs when some (at least 2) of the catalog servers
  are on hosts/IP addresses that exist, but the others are on
  hosts that do not exist. In this case, the broker that is on the
  existent host can be started, but the cache components may take
  more than 10 minutes to start.
  
  This can occur, for instance, in a two broker cache, where each
  broker is configured to host two catalogs, and the machine
  hosting one of the brokers is unavailable. Or if virtual IP
  addresses are being used on z/OS, which exist only for the
  lifetime of a broker task.
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0. For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The product now contains a version of WebSphere eXtreme Scale
  where this problem is fixed.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.5
  v9.0       9.0.0.2
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available, information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  WEB MB Z/OS

• Fixed component ID

  5697P4400

Applicable component levels

• R800 PSY

     UP