| Author |
Message
|
| anan |
 Posted: Tue Mar 11, 2014 8:40 am Post subject: distinguish system Q from rest of the Q's not using its name |
 |
|
Novice
Joined: 24 Sep 2013
Posts: 11
|
Please suggest a way to distinguish system queues from rest of the queue with out using its name.. like
dis ql(system*)..
Any other options please... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Mar 11, 2014 9:26 am Post subject: Re: distinguish system Q from rest of the Q's not using its |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anan wrote: |
| Please suggest a way to distinguish system queues from rest of the queue with out using its name |
The only thing which makes a system queue a system queue is it's name; they're just queue objects like any others.
So
is the only real way - why don't you want to use it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Mar 11, 2014 9:51 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| And do not use any object that starts with the name SYSTEM.**, especially and SVRCONN channels. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 11, 2014 9:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| JosephGramig wrote: |
| And do not use any object that starts with the name SYSTEM.**, especially and SVRCONN channels. |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Mar 11, 2014 2:25 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
There are lots of other SYSTEM objects besides queues. You would have to do many display commands to see them all.
I hope you are aware of automatic case conversion on object names in MQSC commands. The safest method is display queue('SYSTEM.*')
_________________
Glenn |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Mar 12, 2014 2:23 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
'**' is not detectable.
| Code: |
display qlocal(SYSTEM.**)
1 : display qlocal(SYSTEM.**)
AMQ8424: Error detected in a name keyword. |
'*' works though.
| Code: |
display qlocal(SYSTEM.*)
2 : display qlocal(SYSTEM.*)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.ACCOUNTING.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.ACTIVITY.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.CHANNEL.EVENT) TYPE(QLOCAL)
:
|
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Mar 12, 2014 5:16 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
The "SYSTEM.**" is an setmqaut thing which is quite different from "SYSTEM.*" and is also valid. I encourage the readers to look that up in the manual and fully understand the difference before attempting the implementation of a security schema. IMHO I don't see any pragmatic value to the single '*' functionality in the OAM and have never see any institution correctly and usefully implement it.
It is interesting that the MQSC command are different and only accept one '*' and nothing after it, but it is a matter of resources to code such features that governs how the product works... |
|
| Back to top |
|
|
| anan |
| Posted: Tue Mar 25, 2014 9:29 am Post subject: |
|
|
Novice
Joined: 24 Sep 2013
Posts: 11
|
| Blocked system queues using a script to monitor all other Q's. ThankQ all for your tips. |
|
| Back to top |
|
|
|
|
