APAR status
Closed as program error.
Error description
The WMB/ IIB tracing system has logic such that if any message is missing a final insert the node label is added automatically for the missing insert. Under APAR IC92192 the ExceptionList message tree generation was updated to match this logic such that the ExceptionList message tree also contained this final insert. The APAR IC92192 fix did not take into account the BIP2951 and BIP2999 that can be used in an ESQL THROW statement. These messages have 10 inserts that a flow developer can use and it is unlikely that all 10 inserts would be used. As such the node label is also added to these user exceptions when it is not desired.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Message Broker v8.0 and IBM Integration Bus v9.0 and v10.0 throwing a user generated ESQL exception message (BIP2949E-BIP2999E) Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When an exception is thrown in a message flow it can be handled using a catch/failure terminal. In this case an ExceptionList message tree is generated and propagated to the catch/failure terminal such that the ExceptionList can be traversed by error handling logic. Each Exception record in the ExceptionList tree will have all the details of the exception along with its inserts. The IBM Integration Bus tracing system has logic such that if any message is missing a final insert the node label is added automatically for the missing insert. Under APAR IC92192 the ExceptionList message tree generation was updated to match this logic so that the ExceptionList message tree also contained this final insert. The IC92192 fix did not take into account the user generated ESQL exception messages in the range BIP2949E to BIP2999E, that can be used in an ESQL THROW statement. These messages have 10 inserts that a flow developer can use and it is unlikely that all 10 inserts would be used. As such the node label is also added to these user exceptions when it is not desired.
Problem conclusion
The product has been corrected so that user generated ESQL exception (BIP2949E to BIP2999E) messages do not get any extra inserts added to them. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.9 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 number
IT19877
Reported component name
WEB MESSAGE BRO
Reported component ID
5724J0520
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-27
Closed date
2017-05-24
Last modified date
2017-05-24
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 MESSAGE BRO
Fixed component ID
5724J0520
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
24 May 2017