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 » General Discussion » DLQ maxmsglength anomaly on WMQ 6 on Win 2K3 and ZOS 1.6

Post new topic  Reply to topic
 DLQ maxmsglength anomaly on WMQ 6 on Win 2K3 and ZOS 1.6 « View previous topic :: View next topic » 
Author Message
lex_talionis
PostPosted: Mon Jan 22, 2007 12:42 pm    Post subject: DLQ maxmsglength anomaly on WMQ 6 on Win 2K3 and ZOS 1.6 Reply with quote

Novice

Joined: 23 Aug 2006
Posts: 23
Location: Austin, TX

Hey gang,

Search here and read Admin guide but couldn't find anything. We are using WMQ 6 refresh pack 1 on Win2K3 and our Trading Partner on ZOS 1.6 is using WMQ 6 but I don't know their put level or patch level. This week we discovered why we were not getting 6.5mb messages to go across and it was due to the DLQ not being set to at least what the max message length currently being used (6.5mb). Once we changed our DLQ maxmsglength to 20mb we were able to receive the 6.5mb messages okay.

I'm no MQ guru by any stretch, but has this always been like this or is it new for version 6? Is there something else we are missing?

Thanks,
Lex
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Jan 22, 2007 1:13 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It make sense that the MCA would not accept a persistent message if it knew that the DLQ could not hold it - and it had to accept the message before determining if it had to go on the DLQ or not.

Your best bet for determining - on your own - if this is new behavior or old behavior - is to go back and read the v5.3 Intercommunications manual.

I'd guess this is not new behavior.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
csmith28
PostPosted: Mon Jan 22, 2007 1:30 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

It's normal behavior.

For example the default Max message length is 4194304 bytes but if you want the MQManager to handle messages larger than that, say 8388608 you have to modify the MAXMSGL attributes of the MQManager, all the channels & Qlocals that will handle those messages and the SDLQ for it to work properly.

It part of the MCA (Message Channel Agent) Negotiation from MQManager to MQManager to check the MAXMSGL attribute of the SDLQ before accepting a message from a remote MQManager because if for some reason it can't deliver the message to the destination Queue Local it won't have any place to put the message if the MAXMSGL attribute is to small on the SDLQ.

If it is a client application attempting to put the message that is too large the MQManager will not accept the message either, I forget the Return Code off the top of my head but I've seen it happen.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
lex_talionis
PostPosted: Mon Jan 22, 2007 1:59 pm    Post subject: Reply with quote

Novice

Joined: 23 Aug 2006
Posts: 23
Location: Austin, TX

thanks guys...hummm...it does all make sense when you step back and look.

csmith, I think the code is a 2010...I've bookmarked this site for easy reference

http://www-306.ibm.com/software/integration/mqfamily/library/manualsa/amqzao/amqzao0m.htm

Lex
Back to top
View user's profile Send private message
csmith28
PostPosted: Mon Jan 22, 2007 2:02 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

I don't have the link handy but try to download the .pdf versions of the WMQ documentation.

IBM likes to change the links to often to rely on a bookmark for very long.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
lex_talionis
PostPosted: Mon Jan 22, 2007 2:24 pm    Post subject: Reply with quote

Novice

Joined: 23 Aug 2006
Posts: 23
Location: Austin, TX

true on the urls but this one has been good for over 2 years now.

lex
Back to top
View user's profile Send private message
lex_talionis
PostPosted: Fri Feb 02, 2007 6:28 am    Post subject: Reply with quote

Novice

Joined: 23 Aug 2006
Posts: 23
Location: Austin, TX

further testing shows that say for a 10mb message set to persistent from sending app. then the dest. queue as well as the DLQ has to have max message length to accomodate; however, if persistency is off, then the DLQ doesn't have to have appropriate max message length.

Lex
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Feb 02, 2007 6:33 am    Post subject: Reply with quote

Grand High Poobah

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

lex_talionis wrote:
however, if persistency is off, then the DLQ doesn't have to have appropriate max message length.


It is the lot of the non-persistent message to be destroyed if there's no room at the proverbial inn.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » DLQ maxmsglength anomaly on WMQ 6 on Win 2K3 and ZOS 1.6
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.