Re: Problems with MCAUSER on OS/390
Specifying MCAUSER on the receiver channel only controls what userid is checked for security to put to the requested queue. It doesn't cause this userid to be placed in the message descriptor of the message being put. - Bruce Giordano Prudential Insurance Pete Moir <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Sent by: MQSeries List Subject: Problems with MCAUSER on OS/390 <[EMAIL PROTECTED]> Thursday September 26, 2002 11:44 AM Please respond to MQSeries List Hello, I have a frustrating problem I hope soemone can explain to me. I have a client on Win2K (V5.2) I'm running under userid 'pmoir' I am connected to a server on NT (V5.2) I use amqsputc to put a message onto a remote queue on the server which is then sent to a local queue on OS/390 (V5.2). The message turns up on the queue on OS/390 with userid of 'pmoir' as you'd expect. Now I amend the receiver channel on OS/390 to have MCAUSER of something else and set PUTAUT to 'ONLYMCA' but still when I send a message it turns up on the queue on OS/390 with the userid of 'pmoir'. I've stopped/started the channel, even refereshed the queue manager but still no change. the manual states for ONLYMCA option ; "The default user ID is used. Any user ID received from the network is not used." surely the only place the userid of 'pmoir' could've come from is "the network" I've also tried PUTAUT of DEFAULT. How do I force the message to pick up the userid from the MCAUSER of the receiver channel on OS/390 ? This is easy to do on the NT server simply setting the MCA user on the SVRCONN channel but I don't want to do it there. I have no MQ security exits on OS/390 which could be overiding MCA. Pete. _ Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority. _ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Problems with MCAUSER on OS/390
Pete,
When you say 'turns up on the queue with user id "pmoir"' do you mean that
the check against that resource is done against "pmoir" or that the user id
in the MQMD is "pmoir"?
If you mean the latter, changing PUTAUT will not change that. PUTAUT
specifies which user id (or user ids) are checked against the profiles for
that resource. If you set warning on, on your RACF profiles for this
resource you will be able to see which user ids are checked against the
profile - assuming you have the switches set on to do the checking in the
first place.
What is it you are trying to achieve here? Is it resource profile checking,
or changing the user ID within the MQMD of the message?
Cheers
Morag
Morag Hughson
WebSphere MQ for z/OS Development
Internet: [EMAIL PROTECTED]
Pete Moir
cc:
Sent by: MQSeries Subject: Problems with MCAUSER on
OS/390
List
26/09/2002 16:44
Please respond to
MQSeries List
Hello,
I have a frustrating problem I hope soemone can explain to me.
I have a client on Win2K (V5.2) I'm running under userid 'pmoir'
I am connected to a server on NT (V5.2)
I use amqsputc to put a message onto a remote queue on the server which is
then sent to a local queue on OS/390 (V5.2).
The message turns up on the queue on OS/390 with userid of 'pmoir' as you'd
expect.
Now I amend the receiver channel on OS/390 to have MCAUSER of something
else
and set PUTAUT to 'ONLYMCA' but still when I send a message it turns up on
the queue on OS/390 with the userid of 'pmoir'.
I've stopped/started the channel, even refereshed the queue manager but
still no change.
the manual states for ONLYMCA option ;
"The default user ID is used. Any user ID received from the network is not
used."
surely the only place the userid of 'pmoir' could've come from is "the
network"
I've also tried PUTAUT of DEFAULT.
How do I force the message to pick up the userid from the MCAUSER of the
receiver channel on OS/390 ?
This is easy to do on the NT server simply setting the MCA user on the
SVRCONN channel but I don't want to do it there.
I have no MQ security exits on OS/390 which could be overiding MCA.
Pete.
_
Notice to recipient:
The information in this internet e-mail and any attachments is confidential
and may be privileged. It is intended solely for the addressee. If you are
not the intended addressee please notify the sender immediately by
telephone. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful..
When addressed to external clients any opinions or advice contained in this
internet e-mail are subject to the terms and conditions expressed in any
applicable governing terms of business or client engagement letter issued
by
the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America,
N.A., London Branch, Banc of America Securities Limited and Banc of America
Futures Incorporated are regulated by the Financial Services Authority.
_
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Problems with MCAUSER on OS/390
Pete I believe your problem has to do with the setting of RESLEVEL authority for the Chinit. You can read about this in more detail in the System Setup Guide. I believe you need to have the RESLEVEL profile set to READ or UPDATE for the Chinit address space and set ONLYMCA as the PUTAUT. Then it goes through the proper steps to resolve what the manual calls MCA user id which I believe includes MCAUSER. Also, if you change the authority of RESLEVEL, you have to recycle the address space in order to have it take. The refresh commands do not work on RESLEVEL. I will be interested in how you make out. Thanks Frank -Original Message- From: Pete Moir [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 11:44 AM To: [EMAIL PROTECTED] Subject: Problems with MCAUSER on OS/390 Hello, I have a frustrating problem I hope soemone can explain to me. I have a client on Win2K (V5.2) I'm running under userid 'pmoir' I am connected to a server on NT (V5.2) I use amqsputc to put a message onto a remote queue on the server which is then sent to a local queue on OS/390 (V5.2). The message turns up on the queue on OS/390 with userid of 'pmoir' as you'd expect. Now I amend the receiver channel on OS/390 to have MCAUSER of something else and set PUTAUT to 'ONLYMCA' but still when I send a message it turns up on the queue on OS/390 with the userid of 'pmoir'. I've stopped/started the channel, even refereshed the queue manager but still no change. the manual states for ONLYMCA option ; "The default user ID is used. Any user ID received from the network is not used." surely the only place the userid of 'pmoir' could've come from is "the network" I've also tried PUTAUT of DEFAULT. How do I force the message to pick up the userid from the MCAUSER of the receiver channel on OS/390 ? This is easy to do on the NT server simply setting the MCA user on the SVRCONN channel but I don't want to do it there. I have no MQ security exits on OS/390 which could be overiding MCA. Pete. _ Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority. _ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Problems with MCAUSER on OS/390
Hello, I have a frustrating problem I hope soemone can explain to me. I have a client on Win2K (V5.2) I'm running under userid 'pmoir' I am connected to a server on NT (V5.2) I use amqsputc to put a message onto a remote queue on the server which is then sent to a local queue on OS/390 (V5.2). The message turns up on the queue on OS/390 with userid of 'pmoir' as you'd expect. Now I amend the receiver channel on OS/390 to have MCAUSER of something else and set PUTAUT to 'ONLYMCA' but still when I send a message it turns up on the queue on OS/390 with the userid of 'pmoir'. I've stopped/started the channel, even refereshed the queue manager but still no change. the manual states for ONLYMCA option ; "The default user ID is used. Any user ID received from the network is not used." surely the only place the userid of 'pmoir' could've come from is "the network" I've also tried PUTAUT of DEFAULT. How do I force the message to pick up the userid from the MCAUSER of the receiver channel on OS/390 ? This is easy to do on the NT server simply setting the MCA user on the SVRCONN channel but I don't want to do it there. I have no MQ security exits on OS/390 which could be overiding MCA. Pete. _ Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority. _ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
