APAR status
Closed as program error.
Error description
When sending a message to an MQ Output node a BIP4694E Exception will be thrown indicating that the MQMD is in the wrong position if the MQMD is not first child of the Properties folder. At v9 the MQOutput node only checked that an MQMD is present somewhere in the message. This means that some working scenarios where the children prior to the MQMD do not contribute a bitstream towards the final MQ message now fail when run at IIB v10 where they passed at v9. Aggregation scenarios where an MQMD is inserted as the first child of the CombIgmAggregateReplyBody is one such example.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v10 and IBM App Connect Enterprise v11 who are migrating flows from IBM Integration Bus v9 or earlier where the MQMD header may not necessarily be the first header in the message at an MQOutput node. Platforms affected: MultiPlatform, z/OS **************************************************************** PROBLEM DESCRIPTION: When sending a message to an MQ Output node, a BIP4694E Exception will be thrown indicating that the MQMD is in the wrong position if the MQMD is not the first element after the 'Properties' folder. At v9 the MQOutput node only checked that an MQMD header is a direct child of the Root element and was in any position. This means that some working scenarios where the children prior to the MQMD do not contribute a bitstream towards the final MQ message now fail when run at IIB v10 where they passed at v9. Aggregation scenarios where an MQMD is inserted after the ComImbAggregateReplyBody is one such example.
Problem conclusion
For IIB v10, the v9 behaviour can be re-enabled by setting the environment variable MQSI_RELAX_CHECK_FOR_MQMD_HEADER_POSITION. For ACE v11 and above, the v9 behaviour is the default. The stricter behaviour from IIB v10 can be opted-in via the environment variable MQSI_STRICT_CHECK_FOR_MQMD_HEADER_POSITION. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.15 v11.0 11.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
IT25971
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-08-14
Closed date
2018-10-11
Last modified date
2020-11-19
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
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]
Document Information
Modified date:
20 November 2020