PI61889: UPGRADING TO Z/OS 2.02 RESULTS IN DUPLICATE EG ON RELOAD

APAR status

• Closed as program error.

Error description

• After upgrading to z/OS v2.02, issuing the mqsireload command
  for an Execution Group (EG) or cancelling the EG address space
  will result in a duplicate EG address space after the EG has
  restarted.
  
  The broker Joblog will contain the following error:
  
  BIP9241E: An internal error occurred with a DataFlowEngine
  address space, returncode 157, reasoncode 0.
  

Local fix

• To avoid the duplicate EG scenario,
  
  1. issue mqsistopmessageflow (BIPSPMF) with the -e EGname
  option.
  
  wait for the EG to stop.
  
  2. issue mqsistartmessageflow (BIPSTMF) with the -e EGname
  option.
  
  
  If you have reloaded / canceled the EG and are already in the
  duplicate EG scenario ...
  
  1. issue mqsistopmessageflow (BIPSPMF) with the -e EGname
  option. (This will stop the non-duplicate EG address space)
  
  cancel (/C) the duplicate EG address space.
  
  2. issue mqsistartmessageflow (BIPSTMF) with the -e EGname
  option.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker v7.0, v8.0 and IBM
  Integration Bus v9.0, v10.0 who upgrade to z/OS v2.02.
  
  
  Platforms affected:
  z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Problems may be encountered after upgrading to z/OS v2.02.
  
  An at attempt to reload an integration server/execution group
  (EG) using the mqisreload command, or an automatic restart of a
  failed EG, may result in a duplicate EG address space once the
  EG has restarted.
  
  If the EG address space ends very early on in the start up
  process, the following messages may be logged, indicating there
  was a problem with starting or stopping the EG address space:
  
  BIP9241E:An internal error occurred with a DataFlowEngine
  address space,
  returncode 157, reasoncode 4. An internal error occurred
  processing a
  semaphore whilst starting or stopping a DataFlowEngine address
  space.
  
  BIP2057E: Integration server 'MQ20BRK' could not be started:
  integration
  node name 'EG1'; UUID 'ab12c345-de67-89f0-12a3-456bc7de89f0';
  label
  'EG1'. The integration node was unable to start an integration
  server process. Ensure that the executable is available and that
  the
  integration node's service userid has permission to run the
  executable.
  
  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 has been modified to resolve the problems
  encountered after upgrading to z/OS v2.02.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.7
  v8.0       8.0.0.8
  v9.0       9.0.0.7
  
  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

  5655V6000

Applicable component levels

• R700 PSY

     UP