APAR status
Closed as program error.
Error description
The NonStop system have 2 CPU system and all MQ primary processes started on CPU1. The putting application put messages into the queue and MQRC_BACKED_OUT was returned when the backup CPU (CPU0) was went down. The putting application reconnected to the queue manager and put messages. Then getting application got messages from the queue. After RC 2033 MQRC_NO_MSG_AVAILABLE was returned, the queue status still showed CURDEPTH(1).
Local fix
Problem summary
In case of a "MQRC_BACKED_OUT" (2003) failure situation when putting non persistent messages without syncpoint and outside of transactions, the failing put will still be counted towards the queue depth statistics for this queue.
Problem conclusion
The product has been changed to handle such situations and decrement the queue depth statistics accordingly.
Temporary fix
Comments
APAR Information
APAR number
IT29055
Reported component name
WEBS MQ NSS ITA
Reported component ID
5724A3902
Reported release
531
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-05-07
Closed date
2019-06-17
Last modified date
2019-06-17
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
WEBS MQ NSS ITA
Fixed component ID
5724A3902
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.3.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023