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 » Clustering » Lowering effective wait time on a problematic cluster qm

Post new topic  Reply to topic Goto page Previous  1, 2
 Lowering effective wait time on a problematic cluster qm « View previous topic :: View next topic » 
Author Message
mvic
PostPosted: Thu Jan 20, 2011 4:24 am    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080
mattfarney wrote:
Personal Opinion: I wish there was a way to force certain MQ options (persistence, defbind, etc.) since trusting the generator of the data is problematic.

There is a way.

You can write your own API exits that will force the options you need into the MQOPEN, MQPUT calls etc.

You have to write the exit in C, and test it thoroughly. If you don't have the skills for that in-house, then buying in a solution (as per Vitor's suggestion) might be better for you.
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 » Clustering » Lowering effective wait time on a problematic cluster qm
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.