Mq Error 2173
with a mandatory word, e.g. keyword2 keyword1 +keyword2 Questions excluding a word, e.g. keyword2 keyword1 -keyword2 Questions with a specific tag and keyword(s) +[tag1] keyword1 Questions with two or more specific tags and keyword(s) +[tag1] +[tag2] keyword1 To search for all posts by a user or all posts with a specific tag, start typing and choose from the suggestion list. Tags Spaces API Connect Appsecdev BPM Blockchain Bluemix CICS Cloud Analytics Cloud marketplace Content Services (ECM) Continuous Testing Courses DB2 LUW DataPower Decision Optimization DevOps Services Digital Experience Hadoop IBM Design IIDR ITOA InformationServer Integration Bus Internet of Things LinuxONE MDM Mainframe Messaging Node.js ODM Open Predictive Analytics PureData for Analytics Push Run Book Automation Storage Streamsdev Swift UrbanCode WASdev WSRR Watson dW Answers Help dW Premium developerWorks Team Watson Health More Users Badges Ask a question Why is our MQ application PUT failing with MQRC 2173? Question by Gregory(Greg)Bowman ( 5082) | Mar 02, 2015 at 07:21 AM mqmessaging2173mqrc_pmo_error Our WebSphere MQ application issues a MQPUT but fails with MQRC= 2173 (087D): MQRC_PMO_ERROR. This error indicates that the PUT options used are invalid even though they look correct. What could be the cause ? SteveWebb People who like this Close 1 Comment 10 |3000 characters needed characters left characters exceeded Viewable by all users Viewable by moderators Viewable by moderators and the original poster Viewable by all users 1 reply · Add your answer Sort: Accepted answer Answer by MarkWomack (4004) | Mar 02, 2015 at 07:26 AM We've seen overlays (caused by message descriptors (MD) extensions) that can write over the message options (PMO) structure. Here's sample application code of how the MQMD version might be set : MOVE MQMD-VERSION-2 TO MQMD-VERSION OF MESSAGE-DESCRIPTOR You should check to see if the version of the copybook agrees with this. If not, change the application to include the copybooks for the MQMD version to be used. Comment SteveWebb People who like this Close 1 Share 10 |3000 characters needed characters left characters exceeded Viewable by all users Viewable by moderators Viewable by moderators and the original poster Viewable by all users Your answer Text editing toolbar Hint: You can notify a user about this post by typing @username. Attachments: Up to 4 attachments (including images) can be used with a maximum of 1.0 MB each and 4.2 MB total. Follow this question 23 people are following this qu
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » Mainframe, CICS, TXSeries » MQ 2173 Error Code MQ 2173 Error Code « View previous topic :: View next topic » Author Message Mainframe Dude Posted: Fri Oct 20, 2006 10:01 am Post subject: MQ 2173 Error mq error Code NewbieJoined: 20 Oct 2006Posts: 6 While changing a Cobol batch program from using an MQPUT1 to using an MQPUT (with MQOPEN before and MQCLOSE after processing is complete), I'm receiving a 2173 reason code, completion code 2, whenever I attempt the MQPUT. I changed the parameter listing accordingly. Connect is from MQCONN and Object is from the MQOPEN. mq error 2173 Any ideas? The MQPUT1 works great but is not as efficient when writing multiple records to the queue. Thanks MOVE MQMI-NONE TO MQMD-MSGID OF PUT-MESSAGE-DESCRIPTOR. MOVE MQPER-PERSISTENT TO MQMD-PERSISTENCE OF PUT-MESSAGE-DESCRIPTOR. MOVE MQFMT-STRING TO MQMD-FORMAT OF PUT-MESSAGE-DESCRIPTOR. ADD MQPMO-NO-SYNCPOINT MQPMO-FAIL-IF-QUIESCING GIVING MQPMO-OPTIONS. MOVE LENGTH OF WMSULOGE-RECORD TO WS-BUFFER-LENGTH. CALL 'MQPUT' USING WS-HANDLE-CONNECT, WS-HANDLE-OBJECT, PUT-MESSAGE-DESCRIPTOR, MQM-PMOPTIONS, WS-BUFFER-LENGTH, WMSULOGE-RECORD, WS-COMP-CODE, WS-REASON END-CALL Back to top kevinf2349 Posted: Fri Oct 20, 2006 10:17 am Post subject: Grand MasterJoined: 28 Feb 2003Posts: 1311Location: USA Quote: PUT-MESSAGE-DESCRIPTOR, MQM-PMOPTIONS, Shouldn't that be Code: PUT-MESSAGE-DESCRIPTOR, MQPMO-OPTIONS, Back to top Mainframe Dude Posted: Fri Oct 20, 2006 11:28 am Post subject: Thanks, But Same Error NewbieJoined: 20 Oct 2006Posts: 6 I tried your suggestion, but I received the same error. When setting up queues do you know if different security can be defined for MQPUT1 versus MQPUT. My guys say no, but there has to be something environmental that's causing this error. CALL 'MQCONN' USING WS-QMGR, WS-HANDLE-CONNECT, WS-COMP-CODE, WS-REASON END-CALL CALL 'MQOPEN' USING WS-HANDLE-CONNECT, PUT-OBJECT-DESCRIPTOR, MQM-PMOPTIONS, WS-HANDLE-OBJECT, WS-COMP-CODE, WS-REASON END-CALL CALL 'M