| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| QRep Websphere MQ error |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Fri Mar 20, 2009 2:41 am Post subject: Re: QRep Websphere MQ error |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WMBDEV1 wrote: |
| terminology...... i was using remoteq and target q interchangeably.... tut tut |
You still wouldn't get a put error for any queue (of any type) being full unless it was local to the putting application. I use local here in the WMQ sense where "local" is the queue manager to which the application is connected and "remote" is any other.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Mar 20, 2009 2:44 am Post subject: Re: QRep Websphere MQ error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Vitor wrote: |
| WMBDEV1 wrote: |
| terminology...... i was using remoteq and target q interchangeably.... tut tut |
You still wouldn't get a put error for any queue (of any type) being full unless it was local to the putting application. I use local here in the WMQ sense where "local" is the queue manager to which the application is connected and "remote" is any other. |
Alright, if we're being precise, you wouldn't get a put error in the putting application if the target queue on the remote machine was full. You'd get it in the DLH added to the message as it was DLQ'd by the remote queue manager.
Unless there was no DLQ on the remote queue manager, etc, etc, etc 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Fri Mar 20, 2009 3:44 am Post subject: Re: QRep Websphere MQ error |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Vitor wrote: |
| Vitor wrote: |
| WMBDEV1 wrote: |
| terminology...... i was using remoteq and target q interchangeably.... tut tut |
You still wouldn't get a put error for any queue (of any type) being full unless it was local to the putting application. I use local here in the WMQ sense where "local" is the queue manager to which the application is connected and "remote" is any other. |
Alright, if we're being precise, you wouldn't get a put error in the putting application if the target queue on the remote machine was full. You'd get it in the DLH added to the message as it was DLQ'd by the remote queue manager.
Unless there was no DLQ on the remote queue manager, etc, etc, etc |
this could just run and run.... I was just trying to ensure the target q wasnt full which was then causing his channels to stop, the xmit q to fill and the 2053 RC then being returned!!!! Maybe I didnt explain myself very well.... I am new to this "helping others out remotely" stuff  |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
