| Author |
Message
|
| BBM |
 Posted: Thu Jul 27, 2006 9:10 am Post subject: Alias and Local |
 |
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Hi,
Does anyone know a way of checking whether messages are being put onto a Local queue directly or via an Alias?
We are using an API exit to intercepts PUTs that come via aliases and some external parties are putting directly onto our Local queue - hence our API exit misses them.
Many thanks
BBM |
|
| Back to top |
|
 |
| rtsujimoto |
| Posted: Thu Jul 27, 2006 9:25 am Post subject: |
|
|
Centurion
Joined: 16 Jun 2004
Posts: 119
Location: Lake Success, NY
|
| IIRC, you define a rule barring them from writing to the qlocal, but they would still be able to put to the qalias. They may not like it, but you'll quickly find out who is doing puts directly to the qlocal. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jul 27, 2006 10:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Drop the qlocal. Create a new qlocal with a new name. Create a new qalias with the old qlocal name.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| BBM |
| Posted: Fri Jul 28, 2006 12:33 am Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Hi,
Unfortunately this is a production queue manager with over 600 queues that handle high volume high value messages. We are not able to delete local queues as other applications have reference to them although it is a pretty efficient way to find out who is using the aliases!
I have access to the logs and the Cressida Request tool - does anyone know whether MQ records if the put was to a local or alias queue in the logs?
Thanks
BBM |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Jul 28, 2006 1:26 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
what plattform are we talking about?
on z/OS one option could be to set different RACF security for alias and queue.
alias - allow access
queue - permitt access, but set level to warning.
so you get a warning for every direct access to the queue, but you do not harm or block anyone and you dont have to change names.
if you are not on z/OS, maybe this can be adopted in some way on the different plattforms (but afaik there is no warming level there)?!?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| BBM |
| Posted: Fri Jul 28, 2006 1:37 am Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Butcher thanks...
We are using MQ5.3.11 on Windows 2000 server - apologies for once again not mentioning this!
BBM |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Jul 28, 2006 3:10 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| We are using an API exit to intercepts PUTs that come via aliases and some external parties are putting directly onto our Local queue - hence our API exit misses them. |
What exactly do that mean? Doesn't your API exit also get called when messages are put to the local queue directly?
_________________
-wayne |
|
| Back to top |
|
|
| cwolfhagen |
| Posted: Fri Aug 11, 2006 2:48 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2004
Posts: 8
Location: Nødebo, Denmark
|
MQ logs the put to the base queue of the alias queue, which seen from a recovery standpoint is logical.
Unfortunately that means that ReQuest cannot distinguis between messages put directly to the local queue and message put to the alias queue.
Similarily ReQuest can only display the messages put to remote queues by looking for the associated transmit queues.
Christian Wolfhagen
Senior Consultant
Cressida Technology Ltd. |
|
| Back to top |
|
|
|
|
