PH29984: DOCUMENT THE SCOPECHECKING PARAMETER ON THE COMIBMPARSERMANAGER

APAR status

• Closed as documentation error.

Error description

• It is possible to disable parser scope checking using the
  following command:
  
  mqsichangeproperties -e -o
  ComIbmParserManager -n scopeChecking -v false
  
  This property is
  not documented in the KnowledgeCenter.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus version 10 and App Connect
  enterprise version 11.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <span style="background-color:rgb(255, 255, 255)">It is possible
  to disable parser scope checking using the </span><span
  style="background-color:rgb(255, 255, 255)">following command:
                                              </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255,
  255)">mqsichangeproperties -e -o </span><span
  style="background-color:rgb(255, 255, 255)">ComIbmParserManager
  -n scopeChecking -v false                  </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">This property
  is </span><span style="background-color:rgb(255, 255, 255)">not
  documented in the KnowledgeCenter.      </span>
  

Problem conclusion

• The following text will be added to Knowledge Center topic
  bn23637 which describes the properties available on the
  ComIbmParserManager object.
  
  -n scopeChecking -v value
  This property specifies whether additional scope checking is
  performed on parsers that are re-used in the flow. This scope
  checking ensures that parsers are only re-used when it is safe
  to do so because it is possible using the Java API to re-use
  parsers across message groups. Reusing a parser while it is in
  use by another message group can lead to the process
  DataFlowEngine abending. For message flows which frequently
  re-use parsers this can cause a higher memory requirement.
  Disabling the scope checking can reduce this memory requirement
  by making parser eligible for re-use earlier in the flow
  invocation, however the user will no longer be protected against
  cross message group usage of parsers.
  The value set for this property must be either true or false and
  the default value is true.
  

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

Applicable component levels