APAR status
Closed as program error.
Error description
An MRM parser can parse against an MRM model that has embedded/nested messages. Due to partial parsing, it is possible that parsing may stop part way through an embedded/nested message. If such a parser is re-used (usually on the next message through the flow) such that: a) A different nested message is parsed when it is re-used or b) A different wire format (TDS, CWF, XML) is specified when it is re-used - Then the MRM parser will emit a BIP5431 exception (Parser not initialized), or will cause the DataFlowEngine to abend. The more levels of nested message that are used, the more likely this is to occur. If the MRM message tree is fully serialized, then it is likely that the partial parse will complete and the problem will not be seen. Conversely, using FolderBitStream to serialize parts of the tree increases the likelihood that the tree is not fully serialized. Therefore, using FolderBitStream exposes the issue further.
Local fix
MQSI_FREE_MASTER_PARSERS can be used to avoid the issue, as parsers will not be re-used from message to message.
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus V9.0 or V10.0 using MRM embedded or nested messages. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: An MRM parser can parse against an MRM model that has embedded/nested messages. Due to partial parsing, it is possible that parsing may stop part way through an embedded/nested message. If such a parser is re-used (usually on the next message through the flow) such that: a) A different nested message is parsed when it is re-used or b) A different wire format (TDS, CWF, XML) is specified when it is re-used Then the MRM parser will emit a BIP5431 exception (Parser not initialized), or will cause the DataFlowEngine to abend. The more levels of nested message that are used, the more likely this is to occur. If the MRM message tree is fully serialized, then it is likely that the partial parse will complete and the problem will not be seen. Conversely, using FolderBitStream to serialize parts of the tree increases the likelihood that the tree is not fully serialized. Therefore, using FolderBitStream exposes the issue further. 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 ensures that MRM parsers are left in an acceptable state following partial parsing of embedded/nested messages, such that exceptions or abends are not observed when those parsers are later reused. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 9.0.0.6 v10.0 10.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 number
IT10608
Reported component name
INTEGRATION BUS
Reported component ID
5724J0530
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-08-11
Closed date
2015-09-14
Last modified date
2016-03-16
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
5724J0530
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020