APAR status
Closed as program error.
Error description
When all instances of a clustered queue manager alias are PUT(DISABLED), an FDC is produced. The FDC should not be generated and instead, enable the application to see and handle the error (MQRC_CLUSTER_PUT_INHIBITED) The FDC call stack appears as in the following example -------------{ rfiChooseOne Data: 0x00000006 --------------{ rfxLINK --------------} rfxLINK rc=OK --------------{ rfxLINK --------------} rfxLINK rc=OK Data: 0x00000006 --------------{ rfxLINK --------------} rfxLINK rc=OK --------------{ rfxLINK --------------} rfxLINK rc=OK --------------{ rfiMruAdd --------------} rfiMruAdd rc=OK --------------{ rfiMruAdd --------------} rfiMruAdd rc=OK --------------{ rfiMruChoose --------------} rfiMruChoose rc=OK --------------{ rfiMruClear --------------} rfiMruClear rc=OK -------------} rfiChooseOne rc=MQRC_CLUSTER_PUT_INHIBITED ------------} rfxChooseQMGR rc=MQRC_CLUSTER_PUT_INHIBITED -----------} kqiFastnetChooseQmgr2 rc=MQRC_CLUSTER_PUT_INHIBITED ----------} kqiFastnetChooseQmgr rc=MQRC_CLUSTER_PUT_INHIBITED ---------} kqiFastnetFarNotFound rc=MQRC_CLUSTER_PUT_INHIBITED ---------{ xcsFFST
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of queue manager clusters, with all instances of objects in a PUT(DISABLED) state. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The problem was caused by missing error handling logic to address the specific case where all instances of target queue are put disabled. As a result, default error handling actions were triggered, producing an FDC.
Problem conclusion
The problem is fixed with logic that ensures the specific error code is handled and not left to default error reporting --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.6 v9.0 CD 9.0.1 v9.0 LTS 9.0.0.1 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
IT17211
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-09-25
Closed date
2016-09-30
Last modified date
2017-06-01
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:
01 June 2017