Yes, it sort of does. But this is not a feature of MQ as such. Naming convention is something that is designed and followed by the end-users. But in case you are following a format as above, then yes, it does signify a hierarchy. But a logical one.
Here's something for you from the...
Take a look at the following manuals and that should give you a fair idea of what MQ is.
http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/redp0021.html?Open
http://www-306.ibm.com/software/integration/mqfamily/library/manualsa/manuals/platspecific.html
Cheers
KK
Well, glad that you are satisfied, at last.
But as for the cluster problem, i would say that there may be something with the domain that you are using. Just a thought.
Good luck!!!
Cheers
KK
If you get a 2195, then most likely there MUST be an associated FD/FFST file created under the errors directory.
Post the relevant ffst here, that would throw more light. 2195 "as is" NEVER tells you what went wrong.
Cheers
KK
I wanted to use MQSeries in a program to send messages from one pc to another. But I think if it is not possible through the MQEXPLORER I don't need to program it.
"
---As far as i know you cannot send messages and just browse if there are any, on your queues.
"After reading some documentation...
Are you using MQEXPLORER to just connect to the remote system. Thats it. If so, how is clustering invovled. If you just click on show queue manager and add a remote qm, you should be able to see it. I am still unclear as to where this clustering coming into picture.
Also it looks like you...
No, your english is fine. :)
Now, what i dont understand is what do you mean by "When I tried to connect with the default cluster ".
Did you use an application to connect to a cluster. Becauser the above line does not have any significance other than an app being used.
Also on windows2000...
There is only one QM on each machine (two machines are involved). "
"how else should I install it on two different machines"
---So doesnt this already mean that you have installed on 2 diff machines.
As far as evaluation version is concerned. I havent used it. But i dont think there should...
But I can't connect to the cluster, I got an AMQ4036 error code, what means that I've got not sufficient rights... "
---This itself means you are trying to connect to a qm.
"I think I don't use any api/command calls... "
---And this is an MQ api call, mqconn. It may not be any of your apps...
Could you explain your setup. How many qms are involved in the cluster. Where are they. I mean, are all the queue managers on the same system or different ones.
The machine/system where you are getting this authorization problem, are you able to start and use any other queue managers other...
Your userid should also be in the "mqm" group.
Check in the mqerrlg's to see what userid it is complaining about. Are the queue managers defined locally. And did you use the same userid to install and connect to the default cluster.
Cheers
KK
...not really apply to this current context. In any case, even if you had 100's of messages within one UOW, i dont think there would be and should be *any* overhead to MQ processing other api calls, viz, puts/gets etc. Because message persistance or UOW has nothing to do with MQ processing...
Well, FFSTs are a way to report errors to the end user and they cant be turned off. They would come out whenever MQ encounters a problem. So, what you should do is try and find out why you are getting them at the first place.
And by the way, 5.2.1 which you plan to upgrade to is also old...
...of a few KB, then there sure seems to be some problem.
I would suspect if MQ is the culprit, it is trying to write FFST's. Check in the root install\error directory to see if any *FDC files got created. If MQ is busy cutting FFSTs, then it sure wouldnt process api calls as quickly...
Could be possible that you are using all of the memory, if the messages are Non persistent, or you could be using all of the hard disk space if they are persistent.
Whats the size of the messages and what type they are, persistent or non-persistent.
Cheers
KK
You have to increase it. But you have to remember the following from the manuals.
"it also applies to server-connection and client-connection channels. On these channels, heartbeats flow when a server MCA has issued an MQGET command with the WAIT option on behalf of a client application.
"...
Try increasing HBINT value of the svrconn channel. But that would help only if your client is already connected. If they have issues connecting itself, then MQ is not involved in any way. MQ comes into picture after it recieves a connect request and starts the svrconn channel.
Cheers
KK
If you are talking about connections via channels going into inactive state, then yes, you can use HBINT and DISCINT. Check the manuals for their usage and use the one appropriate to your needs.
Cheers
KK
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.