| Author |
Message
|
| jim.p |
 Posted: Mon Aug 01, 2011 8:12 pm Post subject: WMQ - Windows to Z |
 |
|
Newbie
Joined: 01 Aug 2011
Posts: 3
|
Hi All,
Please bear with me i'm a newbie at this. We are trying to connect from a Qmgr on Windows to Qmgr on the mainframe. At the mainframe end they are expecting to see MQMD.UserIdentifier as a certain user, however when we put a message on the Windows side Sender channel, the user coming through on the mainframe side is the user that runs our Siebel app which is invoking the sender channel.
The errror we get is:
Security error occurred - xxxxxxx not authorised to use transaction nnnnnn
Is there any way to change the user on the sender channel to be the required user at the mainframe end?
thanks in advance
Jim |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Mon Aug 01, 2011 10:45 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
" they are expecting to see MQMD.UserIdentifier as a certain user"
and? do you set what they expect on the putting end? obviously the expected user differs from the userid you use to run the siebel application...
_________________
Regards, Butcher |
|
| Back to top |
|
|
| jim.p |
| Posted: Mon Aug 01, 2011 10:56 pm Post subject: |
|
|
Newbie
Joined: 01 Aug 2011
Posts: 3
|
We have tried to set the same user id, but siebel is limited to supplying the user account in the body, but we can't supply it in the header, which is apparently where MQ at the other end is picking it up from.
We've tried putting it in environment variables of different forms and tried setting the MCAUSER on the sender channel, but the user that always comes out at the other end is the Siebel service user id.
thanks |
|
| Back to top |
|
|
| skoobee |
| Posted: Mon Aug 01, 2011 11:09 pm Post subject: |
|
|
Acolyte
Joined: 26 Nov 2010
Posts: 52
|
APR, MQMD, Fields, UserIdentifier:
[quote]This field is normally an output field generated by the queue manager but for an MQPUT or MQPUT1 call you can make this field an input/output field and specify the UserIdentification field instead of letting the queue manager generate this information. Specify either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT in the PutMsgOpts parameter and specify a user ID in the UserIdentifier field if you do not want the queue manager to generate the UserIdentifier field for an MQPUT or MQPUT1 call.
For the MQPUT and MQPUT1 calls, this is an input/output field if MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT is specified in the PutMsgOpts parameter. Any information following a null character within the field is discarded. The queue manager converts the null character and any following characters to blanks. If MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT is not specified, this field is ignored on input and is an output-only field.
[/quote] |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Aug 02, 2011 5:09 am Post subject: Re: WMQ - Windows to Z |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| jim.p wrote: |
| We are trying to connect from a Qmgr on Windows to Qmgr on the mainframe. At the mainframe end they are expecting to see MQMD.UserIdentifier as a certain useruser that runs our Siebel app which is invoking the sender channel... |
Tell us about the Windows application.
Programming language?
Paste here the portion of the source-code that copies/moves the userid into the message header.
_________________
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 |
|
|
| jim.p |
| Posted: Wed Aug 03, 2011 3:21 pm Post subject: |
|
|
Newbie
Joined: 01 Aug 2011
Posts: 3
|
Hi, Thanks for the advice. Turns out it is a Siebel limitation. the MQMD headers that siebel exposes does not include the Useridentifier for outbound messages and so we cannot change the user account. The other side have decided to allow an exception for our user account.
Cheers
J |
|
| Back to top |
|
|
|
|
