ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ API Support » Return Code when attempting PUT on a full queue

Post new topic  Reply to topic Goto page Previous  1, 2
 Return Code when attempting PUT on a full queue « View previous topic :: View next topic » 
Author Message
themqstudent
PostPosted: Tue Sep 27, 2011 4:05 am    Post subject: Reply with quote

Novice

Joined: 26 May 2011
Posts: 22

Well my Jedi Master, please forgive my ignorance. As my ID (themqstudent) sublimely implies, I am an MQ neophyte. That said, however, the facts are the facts and the only thing I changed was that field, DEFPSIST, from NO to YES. Nothing else, including the program, was changed. Of course I lack the knowledge to explain it. One day I will, though. In the mean time, I humbly come to places like this forum looking for a good soul, such as you, to help me out if time allows them.

Thank you and my the force be with you!
Back to top
View user's profile Send private message
zpat
PostPosted: Tue Sep 27, 2011 4:34 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

The default option on a MQPUT is "Persistence as queue default", which would explain this.

Make sure you get the MQMD.Format = 'MQSTR' (or symbolic MQFMT_STRING). Make the CCSID is set matching the data.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue Sep 27, 2011 4:52 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9405
Location: US: west coast, almost. Otherwise, enroute.

zpat wrote:
The default option on a MQPUT is "Persistence as queue default", which would explain this.

Make sure you get the MQMD.Format = 'MQSTR' (or symbolic MQFMT_STRING). Make the CCSID is set matching the data.


WMQ has near zero defaults. Message persistence is determined by persistence field in the MQMD structure. The initial value of persistence is persistence as defined at the queue. It is not a default.
That is, persistence doesn't revert to the initial value follwoing an MQPUT. That would be a default, wouldn't it?

As with the application component of a message, it is the responsibility of the app to specify persistence - one of three values: the message is persistent, the message is non-persistent, the message is to take on the persistence value as set at the queue.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Sep 27, 2011 5:00 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

themqstudent wrote:
I guess for non persistent queues messages MQ does not return a bad return code, if the queue is full or the message is too long.


It should. This is basic WMQ functionality and any message (regardless of persistence) that can't be put to a queue hosted by the queue manager the application is connected to should result in a reason code.

If you're sure there's no app issue you should raise a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
zpat
PostPosted: Tue Sep 27, 2011 6:23 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

bruce2359 wrote:
zpat wrote:
The default option on a MQPUT is "Persistence as queue default", which would explain this.

Make sure you get the MQMD.Format = 'MQSTR' (or symbolic MQFMT_STRING). Make the CCSID is set matching the data.


WMQ has near zero defaults. Message persistence is determined by persistence field in the MQMD structure. The initial value of persistence is persistence as defined at the queue. It is not a default.
That is, persistence doesn't revert to the initial value follwoing an MQPUT. That would be a default, wouldn't it?

As with the application component of a message, it is the responsibility of the app to specify persistence - one of three values: the message is persistent, the message is non-persistent, the message is to take on the persistence value as set at the queue.


OK, initial value if you want to be pedantic about it. One of the more sensible initial values.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue Sep 27, 2011 6:37 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9405
Location: US: west coast, almost. Otherwise, enroute.

zpat wrote:

OK, initial value if you want to be pedantic about it. One of the more sensible initial values.

Pedantic, precise, you say potato...

... no more a default than the SYSTEM.DEFAULT.LOCAL.QUEUE is a default.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » IBM MQ API Support » Return Code when attempting PUT on a full queue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.