Mq Error Code 2018
Contents |
Your application issues an MQOPEN which fails with an HCONN error MQRC 2018 MQRC_HCONN_ERROR. MQCONN is successful. Symptom MQRC_HCONN_ERROR MQRC HCONN ERROR MQRC2018 RC2018 Cause The HCONN address is a 31-bit address, however, the application is passing a 24-bit HCONN. Resolving the problem Correct the application to pass the HCONN back to WebSphere MQ as supplied. Historical Number 25902 499 000 Product Alias/Synonym WebSphere MQ WMQ Document information More support for: WebSphere MQ Application / API Software version: 7.1 Operating system(s): z/OS Reference #: 1677508 Modified date: 22 July 2014 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
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » Mainframe, CICS, TXSeries » 2018 Error in MQPUT 2018 Error in MQPUT « View previous topic :: View next topic » Author Message suresh_shahukaru Posted: Sat Apr 22, 2006 10:41 pm Post subject: 2018 Error in MQPUT NoviceJoined: 22 Apr 2006Posts: 17 I have a PL/1 code which does the following: 1. Gives a call to MQCONN and gets the HCONN (conn. handle) 2. Gives a call to MQOPEN to open the queue. 3. Reads IMS http://www-01.ibm.com/support/docview.wss?uid=swg21677508 DB, formats the data into a message 4. Puts the formatted message onto the Queue. performs steps 3 and 4 until all the IMS DB records are done. Problem: First MQPUT is successful, from the second MQPUT, its gives the error 2018 saying invalid connection handle but code wise everything looks fine. Given the print of HCONN and the binary value is proper and it didnt got lost. I tried doing only one put and then MQCLOSE, at http://www.mqseries.net/phpBB2/viewtopic.php?t=28995&sid=68d82311d0c0d774b49914ee5d726a18 that time also, the MQPUT was successful and MQCLOSE failed with the same reason code 2018. Please help me... Back to top wschutz Posted: Sun Apr 23, 2006 4:15 am Post subject: Jedi KnightJoined: 02 Jun 2005Posts: 3316Location: IBM (retired) Is this new code or has this been working and now doesn't? You are aware that after taking a syncpoint, the IMS adapter invalidates the connection and object handles, except in a batch-oriented BMP. http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzal.doc/imsapps.htm_________________-wayne Back to top suresh_shahukaru Posted: Sun Apr 23, 2006 4:49 am Post subject: NoviceJoined: 22 Apr 2006Posts: 17 It is a new program and we are using MQ for the first time. Such a scenario is there for MQGET as well where there are multiple MQGETs after a MQCONN and MQOPEN and it is working fine. For MQPUT, we are just giving the OPTIONS as SET_ALL_CONTEXT Please suggest what shall I do? Do I need to code using MQPUT1? Back to top suresh_shahukaru Posted: Sun Apr 23, 2006 5:24 am Post subject: NoviceJoined: 22 Apr 2006Posts: 17 Multiple MQGETs in the same unit of work is working fine because we didnt have any IMS commit using IOPCB in that program But in the multiple MQPUT program, we have got IMS commit for every MQPUT where the IMS thinks that the unit of work is done and closes all the open handles. Now, if I still want toGoogleВойтиСкрытые полÑПоиÑк групп или Ñообщений