Posted: Mon Sep 17, 2007 9:18 pm Post subject: Reason code 2019: MQRC_HOBJ_ERROR in MQCLOSE
Newbie
Joined: 17 Sep 2007 Posts: 1
hi,
The following is the flow in my application:
-1->Input in front-end Webpage using .net-MQ
-2->This input is put onto the remote queue(one on mainframes) that triggers a CICS transaction say JA25.
-3->The MQ-CICS-COBOL program ran successfully with MQCONN-->MQOPEN-->MQGET-->MQCLOSE-->MQDISC-->businesslogic that reads some data from dbase-->MQCONN-->MQOPEN(remote queue at front end-windows)-->MQPUT(onto frontend)-->CLOSE-->DISC.
-4->END CICS TRANSACTION JA25
-5->The mqGet at frontend read the data and populated on the webpage successfully.
-6->Now the data is modified and again put on remote queue that triggers the same CICS transaction JA25.
-7->Now in CICS-MQ pgm after MQCONN-->MQOPEN-->MQGET--> the MQCLOSE ended with reason code 2019. MQRC_OBJ_ERROR.
Now my question is why, even for a new transaction I'm unable to move further after MQCLOSE? The above error doesn't allow other MQI calls to execute. I have used separate object handles while opening the queues(one for local and other for remote).
Note: the CICS application JA25 has been ended at the other end for the first turnaround(webpage->MQ->CICS pgm->MQ->webpage) but at frontend the webpage is still running connected to the WMQ.Does this affect the MQ-CICS bridge?
Joined: 31 Mar 2006 Posts: 386 Location: Ohio, USA
Did you perhaps overwrite your queue handle in working storage while running? You may want to make sure any dynamic data (like stuff that comes from a DB table) is placed after the queue handle in working storage. _________________ Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum