APAR status
Closed as program error.
Error description
Opening a dynamic queue during MQOPEN or during inquiry of queue fails with the following FDCs. 2015/11/02 22:00:15.038450+8 amqzlaa0 7323 9 AD004020 adhOpen arcE_OBJECT_MISSING 2015/11/02 22:00:15.064711+8 amqzlaa0 7323 9 AQ168001 aqpReadData arcE_OBJECT_MISSING 2015/11/02 22:00:15.080877+8 amqzlaa0 7323 9 AQ143008 aqqAccessQHeader arcE_OBJECT_DAMAGED MQM Function Stack Examples: AD004020: zlaMainThread zlaProcessMessage zlaProcessMQIRequest zlaMQOPEN zsqMQOPEN kpiMQOPEN kqiOpenIt kqiOpenQueue kqiSetupQPath kqiResolveHereQName kqiFastnetLockQueue apiEnquireObject aocEnquireObject aqmAccessQueue aqqAccessQueue aqqAccessQHeader aqpReadData aqpOpen adhOpen xcsFFST AQ143008: zlaMainThread zlaProcessMessage zlaProcessMQIRequest zlaMQOPEN zsqMQOPEN kpiMQOPEN kqiOpenIt kqiOpenQueue kqiSetupQPath kqiResolveHereQName kqiFastnetLockQueue apiEnquireObject aocEnquireObject aqmAccessQueue aqqAccessQueue aqqAccessQHeader xcsFFST AQ168001: zlaMainThread zlaProcessMessage zlaProcessMQIRequest zlaMQOPEN zsqMQOPEN kpiMQOPEN kqiOpenIt kqiOpenQueue kqiSetupQPath kqiResolveHereQName kqiFastnetLockQueue apiEnquireObject aocEnquireObject aqmAccessQueue aqqAccessQueue aqqAccessQHeader aqpReadData xcsFFST AD004020: zlaMainThread zlaProcessMessage zlaProcessSPIRequest zlaSPIInquireQueueStatus zsqSPIInquireQueueStatus kqiInquireQueueStatus apiEnquireObject aocEnquireObject aqmAccessQueue aqqAccessQueue aqqAccessQHeader aqpReadData aqpOpen adhOpen xcsFFST AQ168001: zlaMainThread zlaProcessMessage zlaProcessSPIRequest zlaSPIInquireQueueStatus zsqSPIInquireQueueStatus kqiInquireQueueStatus apiEnquireObject aocEnquireObject aqmAccessQueue aqqAccessQueue aqqAccessQHeader aqpReadData xcsFFST 			 			 AQ143008: zlaMainThread zlaProcessMessage zlaProcessSPIRequest zlaSPIInquireQueueStatus zsqSPIInquireQueueStatus kqiInquireQueueStatus apiEnquireObject aocEnquireObject aqmAccessQueue aqqAccessQueue aqqAccessQHeader xcsFFST
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users using dynamic queues may be affected by this problem. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: This problem occurred due to a logic error which caused the queue manager to fail to correctly handle the error condition when attempting to open a dynamic queue which was not available.
Problem conclusion
MQ has been modified to correctly return and handle lrcE_UNKNOWN_OBJECT_NAME error when the dynamic queue is not available. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.6 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT13221
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-01-18
Closed date
2016-03-23
Last modified date
2016-03-23
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
WMQ BASE MULTIP
Fixed component ID
5724H7251
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2016