| Author |
Message
|
| nvs76 |
 Posted: Wed Sep 28, 2005 11:02 am Post subject: |
 |
|
Novice
Joined: 28 Sep 2005
Posts: 11
|
Hopsala:
I don't have MQ Explorer installed or I don't know where to find that. That's what I'm looking for to ease the maintainance. The MQ is running on AIX box.
NVS |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Sep 28, 2005 11:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Use amqsbcg to dump messages to stdout.
Should be /var/mqm/samp/bin/amqsbcg.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Sep 28, 2005 11:05 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
If memory serves, user commands tend to be located under /var/mqm/bin not /usr/bin, mqver should also be there, if not search for it under /var/mqm or wherever it is you installed mq; odd it's not in your path...
|
(perhaps this is a little off the current thread but...) amqsbcg is a sample program, so its in /opt/mqm/samp/bin
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 28, 2005 11:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| wschutz wrote: |
| (perhaps this is a little off the current thread but...) amqsbcg is a sample program, so its in /opt/mqm/samp/bin |
not on AIX. /var/mqm/samp/bin, on all my servers.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nvs76 |
| Posted: Wed Sep 28, 2005 11:24 am Post subject: |
|
|
Novice
Joined: 28 Sep 2005
Posts: 11
|
| jefflowrey wrote: |
| wschutz wrote: |
| (perhaps this is a little off the current thread but...) amqsbcg is a sample program, so its in /opt/mqm/samp/bin |
not on AIX. /var/mqm/samp/bin, on all my servers. |
I should just run the amqsbcg program and it should clear out entire DLQ? I found it in /usr/lpp/mqm/samp/bin/ folder
How do we make the copy of it? We definately don't want to transfer the messages from DLQ to original queues.
Thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 28, 2005 11:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It won't clear the DLQ.
It will write out a representation of all the messages to standard out.
And, yeah, I guess I got it wrong. It is /usr/mqm/samp/bin on my servers...
So, do something like /usr/lpp/mqm/samp/bin/amqsbcg ... > deadletter.txt
And then clear the DLQ manually, using runmqsc.
You won't be able to reply these messages from this file. You'll just be able to figure out what's wrong with them. If you *do* need to replay these messages, then you should maybe configure the dead letter handler to move them to a different queue for now.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nvs76 |
| Posted: Wed Sep 28, 2005 11:38 am Post subject: |
|
|
Novice
Joined: 28 Sep 2005
Posts: 11
|
| jefflowrey wrote: |
| And then clear the DLQ manually, using runmqsc. |
Sorry to say but can you please tell me how to clear the DLQ from runmqsc manually?
I'm not a pro like you... Can you give me the command to clear the DLQ? |
|
| Back to top |
|
|
| sandiksk |
| Posted: Wed Sep 28, 2005 12:13 pm Post subject: |
|
|
Centurion
Joined: 08 Jun 2005
Posts: 133
|
try
clear ql(SYSTEM.DEAD.LETTER.QUEUE) |
|
| Back to top |
|
|
| hopsala |
| Posted: Wed Sep 28, 2005 2:10 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
(yep, apparently memory did not serve concerning the sample locations...  )
Look, let me put an important emphesis here: the dlq is not your original problem, you should definitely take care of it, but only after you solve the real issue - the fact that msgs are even *trying* to get to the dlq.
What you need to do, since I don't think you'll be able to read the binaries of the dead letter header, is find an MQ Explorer near you and use it to open the dlq to see the error code; You could even install an MQ server trial version on your pc to do this.
To be perfectly honest, it seems you are not sufficiently proficient with MQ for us to help you, there are limits to remote support; you should contact your MQ Admin, or start reading the manuals... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Sep 28, 2005 7:51 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Jeff,
| Quote: |
| And then clear the DLQ manually, using runmqsc. |
I'd have expected that you know you'll get an object in use.
Nvs76,
For the DLQ operations use the dlq manager: runmqdlq
Check up on the syntax in the admin manual
Enjoy  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 29, 2005 3:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| I'd have expected that you know you'll get an object in use. |
Not necessarily.
It depends on how long ago the last message went on there. DLQ is not kept open in the same way that an XMITQ is.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nvs76 |
| Posted: Thu Sep 29, 2005 7:32 am Post subject: |
|
|
Novice
Joined: 28 Sep 2005
Posts: 11
|
I did get "MQSeries Object in use" when tried to clear the DLQ using clear ql() command.
What I did was stopped the channel initiator and trigger monitor and kept only MQ up and cleared the queue(DLQ) immediately.
Hopsala:
You are absolutely correct that I'm not at all proficient in MQ. If I was, I would never have this problem at all. Unfortunately we don't have any MQ Admins since last two years. |
|
| Back to top |
|
|
| hopsala |
| Posted: Thu Sep 29, 2005 9:39 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| nvs76 wrote: |
| Hopsala: You are absolutely correct that I'm not at all proficient in MQ. If I was, I would never have this problem at all. Unfortunately we don't have any MQ Admins since last two years. |
I see; I can only extent my condolences.
What this means, is that you (or whoever is responsible for WMQs well-being) must become an MQ admin; the *only* way to do this is read the literature. You must read the Intercommunication manual and Programming Guide in full, and browse other books such as the Clusters and Security manuals.
I'm afraid that without some basic mq knowledge (such as dead letter queues, channels etc) it will be almost impossible for us to help you.
Back to matters at hand, I repeat what I said the last post - the dlq is not the prob, you must find out why msgs are trying to get to the dlq. I just hope that by clearing it you didn't lose any buisness data... |
|
| Back to top |
|
|
| nvs76 |
| Posted: Thu Sep 29, 2005 10:04 am Post subject: |
|
|
Novice
Joined: 28 Sep 2005
Posts: 11
|
I would love to learn and become MQ Admin. But that's not the only thing I do here. Basically I'm a developer but I do Oracle DBA stuff (though I'm not DBA), SQL server development, Oracle & SQL Server Datawarehousing, programming and maintaining other systems as well as Unix/AIX administration (again I'm not Unix Admin). Altogether I handle almost 11 systems and try to keep everything up and smooth.
Before I cleared up DLQ I made sure that we are not loosing anything.
My main problem again here is one of our queue REC.REC.CTR.UPDATE is not getting the messages from Mainframe in time. We are receiving eventually but after couple hours or a day or two which is not good.
I have one of the guy helping me who is MQ Admin from one consulting company who is helping us for goodwill. But this guy is only gathering the information since last three days and haven't come up with any solutions yet.
That's the reason I'm trying other resources like you all MQ GURUS.
Thanks,
NVS |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 29, 2005 10:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Now that the DLQ is clear, you can watch it for the next message that appears. Then you can look at the reason code, and get a better idea why.
You can also watch the channel status on both sides to see what's going on, and look for channel error messages in the mq error logs.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
