APAR status
Closed as program error.
Error description
Failed Timeout Control messages backed out to a DLQ will have their timeout control data removed. They do still contain the MBTIME01 MQMD Format field set but without the timeout control data, they are no longer valid timeout control messages. If these are subsequently sent directly to the SYSTEM.BROKER.TIMEOUT.QUEUE, the TimeoutNotification node will attempt to process the now invalid timeout control messages and this could result in abends with a trace back stack as follows: ImbWstring::assignInternal(const unsigned short*,unsigned in ImbTimeoutConstants::readControlData(unsigned char**) ImbTimeoutNotificationNode::TimeoutElement::TimeoutElement(I ImbTimeoutNotificationNode::processNewMessages(ImbTimeoutNot ImbTimeoutNotificationNode::processTimeouts(ImbOsThread*) ImbTimeoutNotificationNode::Parameters::run(ImbOsThread*)
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Message Broker and IBM Integration Bus who use the TimeoutNotification Node. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM SUMMARY: Failed Timeout Control messages backed out to a DLQ will have their timeout control header removed. Without the timeout control data, they are no longer valid timeout control messages. If these are subsequently sent directly to the SYSTEM.BROKER.TIMEOUT.QUEUE, the TimeoutNotification node will attempt to process the now invalid timeout control messages and this could result in abends. 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 timeout control message header is no longer removed during back out message processing. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.5 v9.0 9.0.0.3 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
PI13778
Reported component name
WEB MB Z/OS
Reported component ID
5697P4400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-14
Closed date
2014-04-30
Last modified date
2014-04-30
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 MB Z/OS
Fixed component ID
5697P4400
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
30 April 2014