| Author |
Message
|
| MQMB&WAS |
 Posted: Tue May 12, 2020 11:13 pm Post subject: GET Disabled on QALIAS |
 |
|
Centurion
Joined: 12 Jun 2016
Posts: 130
|
Hello Experts,
Is there a situation where an alias queue's GET is disabled automatically. Trying to find why a queue's GET got disabled. It wasn't altered manually, so how else could it get disabled?
Appreciate your time.
Thanks |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Wed May 13, 2020 1:21 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
If this is a regular problem ? Have you considered switching on configuration events ? That way the next time it happens you can just look back at the events and see when and how it happened.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| hughson |
| Posted: Wed May 13, 2020 1:56 am Post subject: Re: GET Disabled on QALIAS |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| MQMB&WAS wrote: |
| Is there a situation where an alias queue's GET is disabled automatically. |
I cannot think of any situation where an alias queue would be altered automatically.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 13, 2020 3:00 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
You are certain that it is the QAliss definition that is GET(disabled)? And not the QLocal that the QAlias points to?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| MQMB&WAS |
| Posted: Wed May 13, 2020 4:35 am Post subject: |
|
|
Centurion
Joined: 12 Jun 2016
Posts: 130
|
| bruce2359 wrote: |
| You are certain that it is the QAliss definition that is GET(disabled)? And not the QLocal that the QAlias points to? |
Yes, just the alias |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed May 13, 2020 3:49 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
QALIAS objects have an alteration date & time, if that helps. It is likely to be set to get disabled by application logic as part of its message processing design, or by an MQ administrator or someone who has authority to set it.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 13, 2020 5:56 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| PaulClarke wrote: |
If this is a regular problem ? Have you considered switching on configuration events ? That way the next time it happens you can just look back at the events and see when and how it happened.
Cheers,
Paul. |
And, more importantly, which who did it.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| MQMB&WAS |
| Posted: Wed May 13, 2020 8:03 pm Post subject: |
|
|
Centurion
Joined: 12 Jun 2016
Posts: 130
|
| gbaddeley wrote: |
| QALIAS objects have an alteration date & time, if that helps. It is likely to be set to get disabled by application logic as part of its message processing design, or by an MQ administrator or someone who has authority to set it. |
I'm guessing this is what happened since no MQ admin has done it. But, wasn't sure if the app has access to do this. COuld you please explain how can an app alter a queue object? THe app id has only put,get, inq, browse permissions on the queue. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 13, 2020 8:51 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| MQMB&WAS wrote: |
| gbaddeley wrote: |
| QALIAS objects have an alteration date & time, if that helps. It is likely to be set to get disabled by application logic as part of its message processing design, or by an MQ administrator or someone who has authority to set it. |
I'm guessing this is what happened since no MQ admin has done it. But, wasn't sure if the app has access to do this. COuld you please explain how can an app alter a queue object? THe app id has only put,get, inq, browse permissions on the queue. |
Tell us about the app? C? Java? JMS? Cobol?
Set permission would be necessary for an app to MQSET queue attributes, unless the offender is a member of the mqm (or equivalent).
As my learned colleague suggested, alter your qmgr to enable config events. When next the QAlias becomes inhibited, look at the config.event queue to identify the culprit.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| hughson |
| Posted: Wed May 13, 2020 8:52 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| MQMB&WAS wrote: |
| gbaddeley wrote: |
| QALIAS objects have an alteration date & time, if that helps. It is likely to be set to get disabled by application logic as part of its message processing design, or by an MQ administrator or someone who has authority to set it. |
I'm guessing this is what happened since no MQ admin has done it. But, wasn't sure if the app has access to do this. COuld you please explain how can an app alter a queue object? THe app id has only put,get, inq, browse permissions on the queue. |
In order to change the QALIAS object, the application would either required +set permission - so it can use the MQSET API verb, or +alt (as well as +put access to the SYSTEM.ADMIN.COMMAND.QUEUE) - so that it can send the command server a PCF command message. If this is not the case, then an admin did it. Config events (as suggested already) is your friend here. If this is a regular occurrence, suggest you turn those on.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 14, 2020 5:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hughson wrote: |
| In order to change the QALIAS object, the application would either required +set permission - so it can use the MQSET API verb, or +alt (as well as +put access to the SYSTEM.ADMIN.COMMAND.QUEUE) - so that it can send the command server a PCF command message. |
Or by accident or design the application is running with mqm authority; for example a badly secured client channel.
This used to be a big problem and is one of the key reasons for the "backstop" security in later versions (all hail @Hughson!)
This in no way invalidates the excellent advice given above by my worthy associates, which I completely endorse. Config events. Audit the changes, identify the guilty, apply the trout.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
