Mq Error Reason Code 2053
Contents |
2053 Technote (troubleshooting) Problem(Abstract) MQ Connector fails to write messages to queue or publish to topic. Symptom Job log contains error message mq completion code 2 reason 2053 similar to this: WebSphere_MQ_Connector,0: MQPUT call executed with completion code 2 (MQCC_FAILED),
Reason '2053' ('mqrc_q_full')
reason code 2053 (MQRC_Q_FULL) WebSphere_MQ_Connector,0: [IIS-CONN-WSMQ-000017] Put message failed with reason code: 2053 (MQRC_Q_FULL) (CC_WSMQMessageConsumer::processOneTopLevelDataItem(), file CC_WSMQMessageConsumer.cpp, line mqrc_q_full 2053 643) Cause There are typically two reasons for this error: 1) maximum queue depth (MAXDEPTH) has been reached. 2) maximum number of un-commited messages (MAXUMSGS) for the queue manager has
Mq Error Reason Code 2033
been exceeded Diagnosing the problem One must look into the MQ queue manager and specific queue properties to determine what is the reason for the MQ 2053 error. If the current depth (CURDEPTH) is close to maximum queue depth (MAXDEPTH) then removing messages from the queue or increasing the maximum queue depth can resolve the issue. If the queue depth is mqw102 | 2053 not the issue then the issue can be caused by a large transaction of messages being written to the queue with single commit at the end of the transaction. In MQ Connector there is Transaction - record size setting that controls how many messages are written in a single transaction (default value is 0 = all messages are committed at the end). If there is large number of messages participating in a single transaction, the queue manager's maximum number of uncommitted messages can be reach (the limit is queue manager specific so all active transactions count towards this limit). If the MAXUMSGS is the issue, one can set lower record count for the transaction in MQ Connector to force MQ Connector to commit fewer messages per transaction. Document information More support for: InfoSphere DataStage Software version: 8.0, 8.1, 8.5, 8.7 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1580423 Modified date: 25 September 2012 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
write messages) : DataStage MQ Connector fails with 2053 Error(Fail to write messages) : DataStage January 19, 2014 Kuntamukkala RaviBoot Camp, DataStage, Known Errors, Parallel Jobs, Server Jobs, Stages Are you using a real-time stages to push few XML's to downstream systems such as MQ connector? Recently I have faced a typical error wherein DataStage job fails with 2053 error most of the times(until the queue is cleared) Job log contains error message similar to this: [box style='error'] MQ_Connect_ETL,0: MQPUT call executed with completion code 2 (MQCC_FAILED), reason code 2053 (MQRC_Q_FULL) MQ_Connect_ETL,0: [IIS-CONN-WSMQ-000017] Put message failed with reason http://www-01.ibm.com/support/docview.wss?uid=swg21580423 code: 2053 (MQRC_Q_FULL) (CC_WSMQMessageConsumer::processOneTopLevelDataItem(), file CC_WSMQMessageConsumer.cpp, line 643) [/box] Problem would be due to There are typically two reasons for this error: 1) maximum queue depth (MAXDEPTH) has been reached. 2) maximum number of un-commited messages (MAXUMSGS) for the queue manager has been exceeded In order to resolve this error 1. Ask your consumer to clear the Messages in Target Queue If #1 doesn't work or If the http://www.technixgeek.com/mq-connector-fails-with-2053-errorfail-to-write-messages-datastage/ queue depth is not the issue then the issue can be caused by a large transaction of messages being written to the queue with single commit at the end of the transaction. In MQ Connector there is Transaction - record size setting that controls how many messages are written in a single transaction. If there is large number of messages participating in a single transaction, the queue manager's maximum number of uncommitted messages can be reach (the limit is queue manager specific so all active transactions count towards this limit). Thanks Share this:Click to share on Twitter (Opens in new window)Click to share on Facebook (Opens in new window)Click to share on Google+ (Opens in new window)Like this:Like Loading... Related DataStage, ETL, Known Errors, Parallel Jobs, Server Jobs, Stages, Workarounds Author: Kuntamukkala RaviETL Consultant by Profession, Webmaster by Passion Post navigation DataStage job aborts with CLI0106E [Connection is closed] error | [Updated] DataStage job with MQ Connector aborts with error code 2058 (Failed to connect to Queue Manager) Leave a Reply Cancel reply Your email address will not be published. Required fields are marked * Name * Email * Website Comment Notify me of follow-up comments by email. Notify me of new pos
Blog IBM Websphere MQ Reason code list / mq reason codes https://www.imwuc.org/blog/ibm-websphere-mq-reason-code-list-/-mq-reason-codes-/-websphere-mq-error-codes-/-mq-error-messages / websphere mq error codes / https://www.mail-archive.com/mqseries@akh-wien.ac.at/msg07620.html mq error messages Karthick Karthikeyan MQRC_* (Reason Codes) MQRC_NONE 0 X'00000000' MQRC_APPL_FIRST 900 X'00000384' MQRC_APPL_LAST 999 X'000003E7' MQRC_ALIAS_BASE_Q_TYPE_ERROR 2001 X'000007D1' MQRC_ALREADY_CONNECTED 2002 X'000007D2' MQRC_BACKED_OUT 2003 X'000007D3' MQRC_BUFFER_ERROR code 2 2004 X'000007D4' MQRC_BUFFER_LENGTH_ERROR 2005 X'000007D5' MQRC_CHAR_ATTR_LENGTH_ERROR 2006 X'000007D6' MQRC_CHAR_ATTRS_ERROR 2007 X'000007D7' MQRC_CHAR_ATTRS_TOO_SHORT 2008 X'000007D8' MQRC_CONNECTION_BROKEN 2009 X'000007D9' MQRC_DATA_LENGTH_ERROR 2010 X'000007DA' MQRC_DYNAMIC_Q_NAME_ERROR 2011 X'000007DB' MQRC_ENVIRONMENT_ERROR 2012 X'000007DC' MQRC_EXPIRY_ERROR 2013 X'000007DD' MQRC_FEEDBACK_ERROR 2014 X'000007DE' MQRC_GET_INHIBITED 2016 X'000007E0' mq error reason MQRC_HANDLE_NOT_AVAILABLE 2017 X'000007E1' MQRC_HCONN_ERROR 2018 X'000007E2' MQRC_HOBJ_ERROR 2019 X'000007E3' MQRC_INHIBIT_VALUE_ERROR 2020 X'000007E4' MQRC_INT_ATTR_COUNT_ERROR 2021 X'000007E5' MQRC_INT_ATTR_COUNT_TOO_SMALL 2022 X'000007E6' MQRC_INT_ATTRS_ARRAY_ERROR 2023 X'000007E7' MQRC_SYNCPOINT_LIMIT_REACHED 2024 X'000007E8' MQRC_MAX_CONNS_LIMIT_REACHED 2025 X'000007E9' MQRC_MD_ERROR 2026 X'000007EA' MQRC_MISSING_REPLY_TO_Q 2027 X'000007EB' MQRC_MSG_TYPE_ERROR 2029 X'000007ED' MQRC_MSG_TOO_BIG_FOR_Q 2030 X'000007EE' MQRC_MSG_TOO_BIG_FOR_Q_MGR 2031 X'000007EF' MQRC_NO_MSG_AVAILABLE 2033 X'000007F1' MQRC_NO_MSG_UNDER_CURSOR 2034 X'000007F2' MQRC_NOT_AUTHORIZED 2035 X'000007F3' MQRC_NOT_OPEN_FOR_BROWSE 2036 X'000007F4' MQRC_NOT_OPEN_FOR_INPUT 2037 X'000007F5' MQRC_NOT_OPEN_FOR_INQUIRE 2038 X'000007F6' MQRC_NOT_OPEN_FOR_OUTPUT 2039 X'000007F7' MQRC_NOT_OPEN_FOR_SET 2040 X'000007F8' MQRC_OBJECT_CHANGED 2041 X'000007F9' MQRC_OBJECT_IN_USE 2042 X'000007FA' MQRC_OBJECT_TYPE_ERROR 2043 X'000007FB' MQRC_OD_ERROR 2044 X'000007FC' MQRC_OPTION_NOT_VALID_FOR_TYPE 2045 X'000007FD' MQRC_OPTIONS_ERROR 2046 X'000007FE' MQRC_PERSISTENCE_ERROR 2047 X'000007FF' MQRC_PERSISTENT_NOT_ALLOWED 2048 X'00000800' MQRC_PRIORITY_EXCEEDS_MAXIMUM 2049 X'00000801' MQRC_PRIORITY_ERROR 2050 X'00000802' MQRC_PUT_INHIBITED 2051 X'00000803' MQRC_Q_DELETED 2052 X'0000080
change in size based on usage or when a queue manager is restarted or if previously active queues have been idle for some time. What you mean to say is "you want to monitor the size of the file system where the queues for the queue manager in question reside. I believe under V5.1 and below, queue sizes could grow to 320MBs, V5.2 this changed to 2GBs and V5.3 its now 2TBs (for UNIX systems). For V5.1 systems, in the TuningParameters section of the mq.ini file, if you specify the keyword 'DefaultQFileSize' and set it to 1GB (DefaultQFileSize=1000000000), then bounce the queue manager, any NEW queues created will now grow up to this size. If a "Queue Full" condition is encountered, check messages that go to your DLQ for a reason code of 2053 (MQRC_Q_FULL or Hexadecimal number 0805 - how the RC is stored in the DLQ header). Now tailor your DLQ Rules Table appropriately for the action you want your DLQ utility (e.g., runmqdlq) to take when this type of error condition is encountered. REASON(MQRC_Q_FULL) ACTION(FWD) FEWQ(OverFlowQueue) runmqdlq < MyRulesTable.txt A 2053 reason code is normally associated with "maximum number of messages reached". I have never seen a condition where the queue size was at capacity. If somebody has seen this condition and it was registered within the AMQERR01.LOG file, please respond back as to what the AMQxxxx number issue. I'm sure I would not be the only one interested in this error. We do manage messages UP TO 85MBs in size, so if the application reading this queue becomes hung, it won't take but a few hundred messages before this condition becomes reality. Also check your SYSTEM.ADMIN.PERFM.EVENT queue, because when queue full conditions are encountered, an event message will be put to this queue by the queue manager that detected this condition. If you have enabled PERFORMANCE EVENTS and are monitoring this queue, then you should be able to catch this condition when it occurs, and alert your staff. Stephan C. Moen -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Christopher D. Fryett Sent: Thursday, April 03, 2003 10:05 AM To: [EMAIL