| Author |
Message
|
| 449adamantov |
 Posted: Tue Jul 19, 2005 11:05 am Post subject: Who set Inhibit Put on queue?? |
 |
|
Newbie
Joined: 19 Jul 2005
Posts: 2
|
These is my problem: a find that a queue has the put inhibit, but i don't change the configuration. Is it possible that for some problem the Mqseries alter the queue definition?
In the log there aren't entry that explain the problem, only message in the dead letter queue.
Many Thanks
Adam |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Jul 19, 2005 1:55 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
MQ will never PUT_INHIBIT a queue by itself. Someone manually did it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 19, 2005 9:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
| MQ will never PUT_INHIBIT a queue by itself. Someone manually did it. |
And usually for a good reason. Talk to your MQ admin and application admin.
Enjoy  |
|
| Back to top |
|
|
| vinodsasidharan |
| Posted: Wed Jul 20, 2005 2:28 am Post subject: ALTTIME ALTDATE |
|
|
Apprentice
Joined: 25 Apr 2003
Posts: 47
Location: Norwich
|
Hi ,
If somebody had altered your definition .Then you can capture the time and date it was done latest.
dis ql(qname)
ALTDATE(2005-04-12).
ALTTIME(11.11.32).
This can be your first step of Investigation if this had happened on your production box . 
_________________
Vinod sasidharan
Ibm Certfied MQ Admin 5.3
Ibm Certfied MQ Admin 6.0
Ibm Certfied WAS Admin 6.0
Ibm Certfied WMB Admin 5.0
Ibm Certfied Db2 Specialist.
Sun certified Java Programmer.
"Ai carte, ai parte ....................." |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jul 20, 2005 3:08 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Careful, alttime / date tells you when *any* attribute was last changed, not just the "put(disable)" attrbiute.
_________________
-wayne |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Jul 20, 2005 3:33 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
If this is important to you, and you don't already have the security and auditing in place you should consider an API exit for the command server - to log userid and parameters. Of course that is no good if anyone can log on to your system as mqm and change things. What if they had deleted that queue, or put inhibited to route the messages somewhere malicious?
Another thing to consider is if you have any external tools or applications that might have automatically put inhibited your queue... e.g. Patrol or an equivalent system management tool. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jul 20, 2005 8:35 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| wschutz wrote: |
| Careful, alttime / date tells you when *any* attribute was last changed, not just the "put(disable)" attrbiute. |
And good ol' MQExplorer will change the Alter time of a queue if you simply look at a queue, not change anything, and Click "OK" instead of "Cancel".
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| malammik |
| Posted: Wed Jul 20, 2005 8:42 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
|
|
