| Author |
Message
|
| kordi |
 Posted: Wed Apr 29, 2015 2:08 am Post subject: MCAUSER on SDR channel |
 |
|
Centurion
Joined: 28 May 2012
Posts: 146
Location: PL
|
Hi guys,
Is there any reason for this attribute on sender channels? I guess for version 7.0.1 and earlier it is no use to set MCAUSER on sender. Yesterday I was testing connection between 2 q managers and setting MCAUSER on sender didn't give any effect while on receiver the effect was as I expected.
Cheers |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Apr 29, 2015 4:04 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
MCAUSER on a channel definitions ascribes a username to the channel instance. It is that username on a SDR channel which will be used to determine if it can MQOPEN its transmit queue.
What name did you use? Did you restart the channel after changing MCAUSER? Is the name in the MQ admin group? What o/s?
_________________
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 |
|
|
| mqjeff |
| Posted: Wed Apr 29, 2015 4:20 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
| MCAUSER on a channel definitions ascribes a username to the channel instance. |
I would say "MCAUSER on a channel definition, or in a CHLAUTH rule forces a userid on that connection" |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Apr 29, 2015 4:26 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mqjeff wrote: |
| bruce2359 wrote: |
| MCAUSER on a channel definitions ascribes a username to the channel instance. |
I would say "MCAUSER on a channel definition, or in a CHLAUTH rule forces a userid on that connection" |
A channel security exit could set MCAUSER as well.
_________________
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 |
|
|
| mqjeff |
| Posted: Wed Apr 29, 2015 4:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
| mqjeff wrote: |
| bruce2359 wrote: |
| MCAUSER on a channel definitions ascribes a username to the channel instance. |
I would say "MCAUSER on a channel definition, or in a CHLAUTH rule forces a userid on that connection" |
A channel security exit could set MCAUSER as well. |
Yes. If one wanted to run those risks.
And those could still be overrirden by a CHLAUTH rule. |
|
| Back to top |
|
|
| kordi |
| Posted: Wed Apr 29, 2015 5:29 am Post subject: |
|
|
Centurion
Joined: 28 May 2012
Posts: 146
Location: PL
|
This is what I read from IBM publib:
http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.csqzaj.doc/sc11040_.htm
MCAUSER(string)
Message channel agent user identifier.
If it is nonblank, it is the user identifier that is to be used by the message channel agent for authorization to access WebSphere MQ resources, including (if PUTAUT is DEF) authorization to put the message to the destination queue for receiver or requester channels.
.....
This parameter is not valid for channels with a channel type (CHLTYPE) of SDR, SVR, CLNTCONN, or CLUSSDR. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 29, 2015 5:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yes, I'm sure that's what the documentation says.
It's correct.
It doesn't invalidate anything that has been said. |
|
| Back to top |
|
|
| kordi |
| Posted: Wed Apr 29, 2015 12:00 pm Post subject: |
|
|
Centurion
Joined: 28 May 2012
Posts: 146
Location: PL
|
Yes, what you said is true, however not reffering to sender channel I guess.
For the sender channel this attribute doesn't have any influence on connection. Or does it?
As I said, I changed MCAUSER and see no difference in delivering messages. MCAUSER is not even present when you display channel status of sender. |
|
| Back to top |
|
|
|
|
