IT18711: MIXED SUBFLOW STYLES CAN CAUSE ESQL SHARED VAR DUPLICATION

APAR status

• Closed as program error.

Error description

• If a message flow is deployed which contains a mixture of
  subflows that are implementated as .msgflow files and subflows
  that are implemented as .subflow files the shared variables may
  be duplicated if the following conditions are also true:
  
  There exists at least one subflow of each type which contains
  it's own ESQL code in broker schemas
  
  The ESQL in both of these flows references common ESQL in a
  different schema
  
  This commonly referenced ESQL contains SHARED variables.
  
  In these circumstances the SHARED variable is duplicated and
  each subflow will use its own copy of the SHARED variable.
  
  This may lead to unexpected results when executing the parent
  messageflow.
  
  Note that under the infocenter topic for deployment rules and
  guidelines we explicitly state that a mixture of inlined
  resources and deployable resources may not behave as expected:
  
  http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm
  .etools.mft.doc/af35100_.htm
  
  This configuration is therefore NOT reccomended but is supported
  in order to ensure that newer IIB versions execute flows
  migrated from older versions correctly.
  
  It is expected that this APAR would only be encountered when
  migrating from WebSphere Message Broker version 7 or earlier.
  

Local fix

• Convert the inlined (.messageflow) style subflows to deployable
  (.subflow) style subflows using the "Convert to Message Flow"
  action in the Toolkit and rebuild the bar file ensuring that the
  "Compile and inline resources" option is not selected. The bar
  file can then be redeployed and the problem will be resolved.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Intewgration Bus Version 10 or App Connect
  Enterprise version 11 using SHARED variables with inlined ESQL.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <span style="background-color:rgb(255, 255, 255)">If a message
  flow is deployed which contains a mixture of </span><span
  style="background-color:rgb(255, 255, 255)">subflows that are
  implementation as .msgflow files and subflows </span><span
  style="background-color:rgb(255, 255, 255)">that are implemented
  as .subflow files the shared variables may </span><span
  style="background-color:rgb(255, 255, 255)">be duplicated if the
  following conditions are also true:       </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">There exists
  at least one subflow of each type which contains  </span><span
  style="background-color:rgb(255, 255, 255)">it's own ESQL code
  in broker schemas                           </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">The ESQL in
  both of these flows references common ESQL in a  </span><span
  style="background-color:rgb(255, 255, 255)">different schema
                                                </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">This commonly
  referenced ESQL contains SHARED variables.       </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">In these
  circumstances the SHARED variable is duplicated and </span><span
  style="background-color:rgb(255, 255, 255)">each subflow will
  use its own copy of the SHARED variable.     </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">This may lead
  to unexpected results when executing the parent </span><span
  style="background-color:rgb(255, 255, 255)">messageflow.
                                                    </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">Note that
  under the infocenter topic for deployment rules and
  </span><span style="background-color:rgb(255, 255,
  255)">guidelines we explicitly state that a mixture of inlined
  </span><span style="background-color:rgb(255, 255,
  255)">resources and deployable resources may not behave as
  expected: </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm
  <span style="background-color:rgb(255, 255,
  255)">.etools.mft.doc/af35100_.htm
       </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">This
  configuration is therefore NOT recommended and only limited
  support is offered </span><span style="background-color:rgb(255,
  255, 255)">in order to ensure that newer IIB versions execute
  flows </span><span style="background-color:rgb(255, 255,
  255)">migrated from older versions.     </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">It is expected
  that this APAR would only be encountered when </span><span
  style="background-color:rgb(255, 255, 255)">migrating from
  WebSphere Message Broker version 7 or earlier.  </span>
  
  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 such that a BIP6071 message is
  issued if a mixture of non-inline and inlined ESQL is detected
  and there are SHARED variables in both the inlined and
  non-inlined sections.
  
  In these circumstances duplication of SHARED variables is
  expected.
  
  If you have reviewed and tested your flows and can confirm that
  they behave correctly then the warning can be disabled by
  setting the following environment variable to any non-null value
  before starting the Integration Node / Server:
  
  <span style="background-color:rgb(221, 255,
  221);font-size:10.6667px;font-family:monospace">MQSI_ESQL_DISABL
  E_SHARED_VAR_WARNING</span>
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.20
  v11.0      11.0.0.8
  
  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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels