APAR status
Closed as program error.
Error description
When invoking the MQConnector to put an output message in the MQOutput node the wrapper code builds up a set of properties to pass to the connector to control where and with what properties it writes the output message, e.g. for where to put the message under syncpoint or not. When using a destination list the correct properties are not being setup and passed into the connector for all destinations defined in the destination list. This might be particularly visible if trying to put messages outside of syncpoint by setting the the transaction property of the input node to 'No' and the equivalent setting on the MQOutput node to 'Automatic'. Some of the messages in the destination list will be put under syncpoint as the contextual information of transaction 'no' is not passed into the connector leaving it to default to 'yes'.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus V10 who use the MQOutput node with DestinationLists. Platforms affected: MultiPlatform, z/OS **************************************************************** PROBLEM DESCRIPTION: When invoking the MQConnector to put an output message in the MQOutput node the wrapper code builds up a set of properties to pass to the connector to control where and with what properties it writes the output message, e.g. for where to put the message under syncpoint or not. When using a destination list the correct properties are not being setup and passed into the connector for all destinations defined in the destination list. This might be particularly visible if trying to put messages outside of syncpoint by setting the the transaction property of the input node to 'No' and the equivalent setting on the MQOutput node to 'Automatic'. Some of the messages in the destination list will be put under syncpoint as the contextual information of transaction 'no' is not passed into the connector leaving it to default to 'yes'. 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 correctly sets up the properties to pass to the MQOutput connector. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.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 number
IT18147
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
2016-11-29
Closed date
2017-03-16
Last modified date
2017-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
5724J0540
Applicable component levels
RA00 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":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020