Mq Error 2192
xcf shared queue 2192 0x00000890 890 MQRC_PAGESET_FULL 2192 0x00000890 MQRC_STORAGE_MEDIUM_FULL Technote (troubleshooting) Problem(Abstract) Your application receives MQRC 2192 ( 0x00000890 ). This application previously ran without errors. The application puts a message to a remote queue, that resolves to a shared transmission queue. The data includes monetary information that must be processed. The application puts messages in one unit of work. The total message size is only about 50K. The messages get backed out. A GTF trace reports the following: The 5EE trace entries showed CSQIMPU0 got 00C90027 CSQI_STRUCTURE_FULL. Prior to that, CSQEMPU1 received 00C50012 CsqeRsnCodeStructureFull because IXLLSTE returned 00000C17 IxlRsnCodeStrFull, as shown in the IXL1MPU1 trace entry. WebSphere MQ was trying to create a new list entry. 2192 0x00000890 MQRC_PAGESET_FULL 2192 0x00000890 MQRC_STORAGE_MEDIUM_FULL Resolving the problem Look at the shared queue definition to verify the structure name. Issue WebSphere MQ command DISPLAY CFSTATUS for the structure in question. Verify the ENTSMAX and ENTSUSED values are large enough. These values relate to the number of CF list entries. ENTSMAX comes from IXLYAMDSTRL_MLSEC. If the values need to be increased, you can run the command: SETXCF START,ALTER,STRNAME=structure-name,SIZE=newsize In this case the command was run so that the newsize matched MAXSIZE of 40960. This time the job ran fine. This might make you question why ALLOWAUTOALT was not automatically increasing the size of the structure, since WebSphere MQ does supports this option. This function is carried out by XES. Autoalter is not going to be triggered by a spike of usage. It only examines things about every 30 seconds, so if the ramp up is happening quickly and then the messages are deleted, it is probably not going to be detected. The threshold condition would not have lasted long enough for the monitor to detect. The documentation that describes autoalter is in Setting up a Sysplex, sections 4.2.2.4 and 4.2.2.5. It does not state much about when monitoring is done, but only that it is done on a periodic basis. Note: PQ75276/UQ78066 addresses problems which could also have the effect of preventing some messages from invalidly
placement of queues across the pagesets. You have too review which pageset you queue is assigned to and see how big https://www.mail-archive.com/mqseries@akh-wien.ac.at/msg02535.html they are, who else is assigned ti it and how much data they http://blog.robiii.nl/2012/01/websphere-mq-reason-codes.html are placing there. This could be a timing thing where you and another resource hog application are placing messages on a queue in the same pageset AND it is toooo small to handle the load. You might want to switch the queue to another pageset by redefining the queue to mq error another one. Also have a look at the pageset allocation. Maybe the Sys Admin didn't allocate enough space. If its production and they are doing there job right there should be MORE space that needed. But then again you app could be doing something wrong. LOOP comes to mind right now! bobbee >From: shailesh bhaskaran <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> mq error 2192 >To: [EMAIL PROTECTED] >Subject: Batch jo abending with MQRC 2192 >Date: Fri, 23 Aug 2002 10:34:48 -0700 > >Hi! All, > >One of our batch job is abending with reason code 2192 >on OS/390. I have looked at the vienna list server for >the previous threads related to this topic. > >MQRC 2192 is Pageset full when the job tries to open >or tries to put the message into a cluster queue on >Mainframe. > >The same job in our test environment does not give us >any problem but in our production environment it >abends with 2192. Our mainframe MQ support is hell >bent on proving that it is a application problem and >not with MQ because they cannot see any 2192 in their >queue manager log. > >Besides obvious reason of pageset being full, what >else can be the reasons for 2192. > >Any help will be highly appreciated. >Thanks >Shailesh > >__________________________________________________ >Do You Yahoo!? >Yahoo! Finance - Get real-time stock quotes >http://finance.yahoo.com > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeri
InnerException is beyond me. This page can be used to look up "ReasonCodes" (which is all the LinkedException provides in XMS.NET). The links in this page all lead to the specific help-page. CodeCode (hex)ReasonCodeDescription 00000RC0MQRC_NONE 9000384RC900MQRC_APPL_FIRST 99903E7RC999MQRC_APPL_LAST 200107D1RC2001MQRC_ALIAS_BASE_Q_TYPE_ERROR 200207D2RC2002MQRC_ALREADY_CONNECTED 200307D3RC2003MQRC_BACKED_OUT 200407D4RC2004MQRC_BUFFER_ERROR 200507D5RC2005MQRC_BUFFER_LENGTH_ERROR 200607D6RC2006MQRC_CHAR_ATTR_LENGTH_ERROR 200707D7RC2007MQRC_CHAR_ATTRS_ERROR 200807D8RC2008MQRC_CHAR_ATTRS_TOO_SHORT 200907D9RC2009MQRC_CONNECTION_BROKEN 201007DARC2010MQRC_DATA_LENGTH_ERROR 201107DBRC2011MQRC_DYNAMIC_Q_NAME_ERROR 201207DCRC2012MQRC_ENVIRONMENT_ERROR 201307DDRC2013MQRC_EXPIRY_ERROR 201407DERC2014MQRC_FEEDBACK_ERROR 201607E0RC2016MQRC_GET_INHIBITED 201707E1RC2017MQRC_HANDLE_NOT_AVAILABLE 201807E2RC2018MQRC_HCONN_ERROR 201907E3RC2019MQRC_HOBJ_ERROR 202007E4RC2020MQRC_INHIBIT_VALUE_ERROR 202107E5RC2021MQRC_INT_ATTR_COUNT_ERROR 202207E6RC2022MQRC_INT_ATTR_COUNT_TOO_SMALL 202307E7RC2023MQRC_INT_ATTRS_ARRAY_ERROR 202407E8RC2024MQRC_SYNCPOINT_LIMIT_REACHED 202507E9RC2025MQRC_MAX_CONNS_LIMIT_REACHED 202607EARC2026MQRC_MD_ERROR 202707EBRC2027MQRC_MISSING_REPLY_TO_Q 202907EDRC2029MQRC_MSG_TYPE_ERROR 203007EERC2030MQRC_MSG_TOO_BIG_FOR_Q 203107EFRC2031MQRC_MSG_TOO_BIG_FOR_Q_MGR 203307F1RC2033MQRC_NO_MSG_AVAILABLE 203407F2RC2034MQRC_NO_MSG_UNDER_CURSOR 203507F3RC2035MQRC_NOT_AUTHORIZED 203607F4RC2036MQRC_NOT_OPEN_FOR_BROWSE 203707F5RC2037MQRC_NOT_OPEN_FOR_INPUT 203807F6RC2038MQRC_NOT_OPEN_FOR_INQUIRE 203907F7RC2039MQRC_NOT_OPEN_FOR_OUTPUT 204007F8RC2040MQRC_NOT_OPEN_FOR_SET 204107F9RC2041MQRC_OBJECT_CHANGED 204207FARC2042MQRC_OBJECT_IN_USE 204307FBRC2043MQRC_OBJECT_TYPE_ERROR 204407FCRC2044MQRC_OD_ERROR 204507FDRC2045MQRC_OPTION_NOT_VALID_FOR_TYPE 204607FERC2046MQRC_OPTIONS_ERROR 204707FFRC2047MQRC_PERSISTENCE_ERROR 20480800RC2048MQRC_PERSISTENT_NOT_ALLOWED 20490801RC2049MQRC_PRIORITY_EXCEEDS_MAXIMUM 20500802RC2050MQRC_PRIORITY_ERROR 20510803RC2051MQRC_PUT_INHIBITED 20520804RC2052MQRC_Q_DELETED 20530805RC2053MQRC_Q_FULL 20550807RC2055MQRC_Q_NOT_EMPTY 20560808RC2056MQRC_Q_SPACE_NOT_AVAILABLE 20570809RC2057MQRC_Q_TYPE_ERROR 2058080A