Mq Error 65536
messages with header reason 65536 No replies Display:ConversationsBy Date 1-1 of 1 Previous Next s_jay 270003F666 1 Post Pinned topic DLQ messages with header reason 65536 2011-05-08T05:50:23Z | Tags: Answered question This question has been answered. Unanswered question This question has not been answered yet. Hi All, An execution group crashes in production(results in abend file) and restarts at a particular time eventhough no data is placed in database at that time . Due to this messages are found in DLQ with header reason 65536. In that execution group,there are two flows. First flow: Timer node(starts every 5 min)->compute->MQOutput(queue name is Input queue of second flow) Second flow: MQInput->compute (database opertion is performed)->MQOutput When i checked the log,the failure location is input node of the second flow.I checked the abend file and found the below info: abend Stack dump for current thread ( 5912) (0xd69e5e88+0x000007a0) ttcdrv [/pa/apps/oracle/product/9.2.0/lib32/libclntsh.a(shr.o)] (0xd68e447c+0x00000050) nioqwa [/pa/apps/oracle/product/9.2.0/lib32/libclntsh.a(shr.o)] (0xd65cad5c+0x00000640) upirtrc [/pa/apps/oracle/product/9.2.0/lib32/libclntsh.a(shr.o)] (0xd671b528+0x0000006c) kpurcsc [/pa/apps/oracle/product/9.2.0/lib32/libclntsh.a(shr.o)] (0xd6736098+0x0000053c) kpuexecv8 [/pa/apps/oracle/product/9.2.0/lib32/libclntsh.a(shr.o)] (0xd67371bc+0x00000ff8) kpuexec [/pa/apps/oracle/product/9.2.0/lib32/libclntsh.a(shr.o)] (0xd67638b8+0x0000001c) OCIStmtExecute [/pa/apps/oracle/product/9.2.0/lib32/libclntsh.a(shr.o)] (0xd397d714+0x00000000)
in WebSphere MQ for z/VSE MustGather; MustGathers; Must Gather; Collect Troubleshooting Data; MustGatherDocument; Collecting; Trouble; Shooting dlh deaqd letter header reason code bigendian littleendian endian big little dead letter queue reason mqrc dead letter queue reason mqrc dead letter queue reason mqrc dead letter queue reason mqrc dead letter queue reason mqrc dead ; MustGatherDocument Technote (troubleshooting) Problem(Abstract) You are experiencing a Dead Letter Queue (DLQ) problem in WebSphere MQ for z/VSE. You would like to know what documentation you must collect (MustGather) so that the WebSphere MQ Support team can diagnose your problem. If you gather this documentation before contacting https://www.ibm.com/developerworks/community/forums/thread.jspa?threadID=370205 support it will expedite the troubleshooting process, and save you time. Resolving the problem Gather this MustGather data before contacting IBM Support: Collecting general data for all problems Collecting troubleshooting data for this problem Troubleshooting hints and tips Exchanging data with IBM Support Go back to: WebSphere MQ (MustGather) Read First Collecting general data for all problems A complete description of the problem, including the following: WebSphere MQ version, release, and http://www.ibm.com/support/docview.wss?uid=swg21264853 maintenance level Operating system version, release, and maintenance level Related products version, and release levels if applicableBack to top Collecting troubleshooting data for this problem Required (MustGather) data: System log. Browse of messages on the dead letter queue. Back to top Troubleshooting hints and tips Search the WebSphere MQ support site for known problems using symptoms like the message number and error codes. Gather the documentation and work with the WebSphere MQ support team to resolve your problem. Process to determine why a message is on the DLQ (dead letter queue): Review System log. You can view the contents of the DLQ using the Master Terminal transaction (MQMT) option 4 (Browse Queue Records). Once in Browse Queue Records panel press PF10=DLH to display the DLH (dead letter header) Sample DLH Or you can: Browse the message on the dead letter queue. Locate the dead letter header. The dead letter header starts with the characters '"DLH". Example: 444C 4820 0000 0001 0000 0825 4D59 2E51 'DLH ........MY.Q' Find the dead letter Reason (the reason the message arrived on the DLQ) in the third word in the dead letter header. In this example the dead letter Reason is: x'0000 0825'. Convert hex x'0000 0825' to decimal 2085. Use the dead letter
2030, 2033, 2035, 2080, 2085, 2092, 2110, 2189 2030 2033 2035 2080 2085 http://www.ibm.com/support/docview.wss?uid=swg21167821 2085 2092 2110 2189 2053 PremiumSupportTips Technote (troubleshooting) Problem(Abstract) WebSphere MQ program fails to process an MQ API call. MQ notifies the program of the failure, by returning a completion code (MQCC), and a reason code (MQRC). These completion codes, and reason codes are documented in the WebSphere MQ Messages manual. Resolving the problem mq error Completion codes The following is a list of the completion codes (MQCC) returned by WebSphere MQ. 0 Successful completion (MQCC_OK) 1 Warning (partial completion) (MQCC_WARNING) 2 Call failed (MQCC_FAILED) Reason codes For a list of reason codes, see Reason codes. You can also use the MQRC utility program to display description of a mq error 65536 reason code. Example: Details regarding the most common reason codes. This information is intended to document the most common causes for following reason codes. MQRC 2030 0x000007ee MQRC_MSG_TOO_BIG_FOR_Q MQRC 2033 0x000007f1 MQRC_NO_MSG_AVAILABLE MQRC 2035 0x000007f3 MQRC_NOT_AUTHORIZED MQRC 2080 0x00000820 MQRC_TRUNCATED_MSG_FAILED MQRC 2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME MQRC 2092 0x0000082c MQRC_XMIT_Q_USAGE_ERROR MQRC 2110 0x0000083e MQRC_FORMAT_ERROR MQRC 2189 0x0000088d MQRC_CLUSTER_RESOLUTION_ERROR Additional information For a list of reason codes, see Reason codes. For a list of feedback codes, see Feedback codes. Related information WebSphere MQ Recommended Fixes A Japanese translation is available Product Alias/Synonym WMQ MQ Document information More support for: WebSphere MQ Application / API Software version: 2.1.2, 3.0, 5.3.1, 6.0, 7.0, 7.0.1, 7.1, 7.5 Operating system(s): AIX, HP NonStop, HP-UX, IBM i, Linux, OpenVMS, Solaris, Windows, z/OS, z/VSE Reference #: 1167821 Modified date: 14 March 2006 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