| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Websphere MQSeries 5.3 MQPUT1 2085 |
« View previous topic :: View next topic » |
| Author |
Message
|
| loudcfla |
 Posted: Tue Dec 10, 2002 7:02 am Post subject: Websphere MQSeries 5.3 MQPUT1 2085 |
 |
|
Acolyte
Joined: 05 May 2002
Posts: 58
|
Hello All, we have a web enabled CICS application using Sun Solaris and IBM mainframe OS/390 2.10 and MQ 5.3. The application will run all day and then all of a sudden we start to get 2085's put unsuccessful, which can't possibly be because we've been putting to this queue all day. I checked and the queue is not full, the channels are running and there are no errors in the logs that I can find but we have a 2085. We restart MQ and CICS and all is well. Can anybody tell me what could cause this to happen? We certainly would appreciate your help!
Regards, Lou |
|
| Back to top |
|
 |
| MichaelR |
| Posted: Wed Dec 11, 2002 6:32 am Post subject: MQPUT1 and 2085 |
|
|
Apprentice
Joined: 20 May 2002
Posts: 37
Location: Tampa
|
Return code 2085 indicates "unknown object name". Is the queue you are "putting" to a dynamic queue? If so it may have been automatically deleted because the application which "created" it has ended. Temporary dynamic queues are automatically purged when there are no more "active" object handles.
Because MQPUT1 performs an MQOPEN, MQPUT & MQCLOSE "undercover" your application sobject handle is "transient" (i.e. not fixed). This would provide a small window of opportunity for MQ to purge the queue.
 |
|
| Back to top |
|
|
| loudcfla |
| Posted: Wed Dec 11, 2002 6:41 am Post subject: MQPUT1 2085 |
|
|
Acolyte
Joined: 05 May 2002
Posts: 58
|
| No it is not a dynamic queue, it is defined within the MQ qmgr. We noticed that when we bounce MQ we still have the problem, but when we bounce CICS the problem is resolved. As I mentioned we wil put successfully to this queue and then all of a sudden we get 2085's on the queue. |
|
| Back to top |
|
|
| MichaelR |
| Posted: Thu Dec 12, 2002 6:10 am Post subject: Error code 2085 |
|
|
Apprentice
Joined: 20 May 2002
Posts: 37
Location: Tampa
|
Did see a similar problem a few months ago where a oreviously existing application, in a VAX VMS environment, was using MQ 2.1 to PUT messages to a QMgr. This application was working without issue until the VMS platform was upgraded to MQ 5.1. All of a sudden the applicatioin started experiencing transient 2085 messages.
After several days of working with IBM Hursley, we were told that the problem was a result of the applications thread design. For example, the parent process was spawning a child thread, passing to the child thread the object handle of the opened queue. Unfortunately the relative address of the object handle was NOT thread-safe across process boundries. This wasn't a problem in MQ VMS 2.1 but was changed in MQ VMS 5.1. Hence the developer had to redesign the application.
Not sure if this helps resolve your problem.
Good luck!
MichaelR
 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
