| Author |
Message
|
| chris boehnke |
 Posted: Sat Dec 11, 2010 12:15 pm Post subject: Omegamon-Msg Delete/ forward - 2035(NOT_AUTHORIZED) error |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi,
We are running 6.2 version of TEPS and TEMS on WIndows machines, and the agent 6.1 installed on the Solaris machine where the QMgr is running.
We have installed/ configured and started the agent with "user1" which is part of mqm group.
There is another user "TEPUser" who is using the TEPS client on his desktop and trying to look at the messages. TEPSUser is also part of mqm group on Solaris machine where the QMgr is running. TEPSUser is able to browse the message content and header but not able to DELETE/ FORWARD the msgs from a queue from TEPS client and getting 2035(NOT_AUTHORIZED) error.
Below is what I see in the agent logs:
| Code: |
IBM Tivoli OMEGAMON XE for Messaging.
(c)Copyright IBM Corp., 2000,2006. All rights reserved.
12/09/10 15:54:16 KMQMI125I System xxxxx, QMgr MQ1, initialization completed.
12/09/10 15:54:16 KMQMI187I Agent Successfully Connected to the server (HUB1)
12/09/10 15:54:17 KMQMI197I QMgr command server is available.
12/09/10 16:00:09 KMQMI102E Error accessing queue SYSTEM.DEAD.LETTER.QUEUE Operation=MQOPEN CC=0X2 RS=0X7F3
12/09/10 16:00:40 KMQMI102E Error accessing queue SYSTEM.DEAD.LETTER.QUEUE Operation=MQOPEN CC=0X2 RS=0X7F3
12/09/10 16:06:42 KMQMI102E Error accessing queue SYSTEM.DEAD.LETTER.QUEUE Operation=MQOPEN CC=0X2 RS=0X7F3
12/09/10 16:10:12 KMQMI161E Component kmq_qmmsg_del_agent is missing required table index values
12/09/10 16:12:20 KMQMI102E Error accessing queue SYSTEM.ADMIN.COMMAND.QUEUE Operation=MQPUT CC=0X2 RS=0X7F3
12/09/10 16:12:20 KMQMI188I MQ command invoked for QMgr=MQ1
12/09/10 16:12:20 KMQMI189I Command text: CLEAR QLOCAL('SYSTEM.DEAD.LETTER.QUEUE')
12/09/10 16:12:20 KMQMI190I WebSphere MQ command completed for QMgr=MQ1
12/09/10 16:12:20 KMQMI192I MQ command completion status: CCCRC=3, CompCode=2, Reason=2035 |
We turned on the MQ trace and I see the below information in the traces:
| Code: |
|..0 |
15:24:25.664852 28011.1 Hobj : Output Parm
15:24:25.664858 28011.1 Compcode : Output Parm
15:24:25.664864 28011.1 Reason : Output Parm
15:24:25.664871 28011.1 --{ ziiMQOPEN
15:24:25.664877 28011.1 ---{ ziiCreateIPCCMessage
15:24:25.664884 28011.1 ----{ zcpCreateMessage
15:24:25.664899 28011.1 Terminus(0) RequestedSize(376)
15:24:25.664908 28011.1 ----} zcpCreateMessage rc=OK
15:24:25.664915 28011.1 ---} ziiCreateIPCCMessage rc=OK
15:24:25.664922 28011.1 ---{ ziiSendReceiveAgent
15:24:25.664929 28011.1 ----{ zcpSendOnPipe
15:24:25.664936 28011.1 -----{ xcsResetEventSem
15:24:25.664942 28011.1 -----} xcsResetEventSem rc=OK
15:24:25.664948 28011.1 -----{ xcsPostEventSem
15:24:25.664958 28011.1 xcsPostEventSem 1::0::0-487736
15:24:25.664990 28011.1 -----} xcsPostEventSem rc=OK
15:24:25.664998 28011.1 ----} zcpSendOnPipe rc=OK
15:24:25.665005 28011.1 ----{ zcpReceiveOnPipe
15:24:25.665012 28011.1 -----{ xcsWaitEventSem
15:24:25.665021 28011.1 xcsWaitEventSem 1::0::0-487568
15:24:25.666952 28011.1 -----} xcsWaitEventSem rc=OK
15:24:25.666968 28011.1 MessageReceived (368 bytes)
15:24:25.666981 28011.1 0x0000: 5a524f50 000007df 00000000 00000002 |ZROP............|
15:24:25.666981 28011.1 0x0010: 000007f3 00000014 4f442020 00000001 |........OD ....|
15:24:25.666981 28011.1 0x0020: 00000001 54455354 20202020 20202020 |....TEST |
15:24:25.666981 28011.1 0x0030: 20202020 20202020 20202020 20202020 | |
15:24:25.666981 28011.1 0x0040: 20202020 20202020 20202020 20202020 | |
15:24:25.666981 28011.1 0x0050: 20202020 00000000 00000000 00000000 | ............|
15:24:25.666981 28011.1 0x0060: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x0070: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x0080: 00000000 414d512e 2a000000 00000000 |....AMQ.*.......|
15:24:25.666981 28011.1 0x0090: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x00a0: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x00b0: 00000000 5448414e 56582020 20202020 |...TEPUSER |
15:24:25.666981 28011.1 0x00c0: 00000000 fd4fb83c 00000000 4d442020 |.... O.<....MD |
15:24:25.666981 28011.1 0x00d0: 002daf3c 00000000 00000000 00000000 |.-.<............|
15:24:25.666981 28011.1 0x00e0: ffffff80 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x00f0: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x0100: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x0110: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x0120: 00000000 00000000 00000000 00000000 |................|
15:24:25.666981 28011.1 0x0130: 4b4d512e 4952412e 4147454e 542e5155 |KMQ.IRA.AGENT.QU|
15:24:25.666981 28011.1 0x0140: 4555452e 34434645 35423745 32303030 |EUE.4CFE5B7E2000|
15:24:25.666981 28011.1 0x0150: 43463032 20202020 20202020 00000000 |CF02 ....|
15:24:25.666981 28011.1 0x0160: 00000000 00000000 00000000 00000000 |................|
15:24:25.666989 28011.1 ----} zcpReceiveOnPipe rc=OK
15:24:25.666996 28011.1 ---}! ziiSendReceiveAgent rc=MQRC_NOT_AUTHORIZED 15:24:25.667002 28011.1 ---{ zcpDeleteMessage
15:24:25.667010 28011.1 ---} zcpDeleteMessage rc=OK
15:24:25.667015 28011.1 --} ziiMQOPEN rc=OK
15:24:25.667022 28011.1 __________
15:24:25.667029 28011.1 MQOPEN <<
15:24:25.667034 28011.1 Hconn : Input Parm |
Can you guys throw some light on this.
Thanks. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat Dec 11, 2010 12:28 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Whichever userid is attempting to clear the SDLQ is not authorized to use the CLEAR command.
Look at the WMQ error logs to see exactly which userid is attempting to access the dead-letter-queue. Ensure that the id is in the mqm group.
_________________
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 |
|
|
| chris boehnke |
| Posted: Sat Dec 11, 2010 12:41 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| bruce2359 wrote: |
Whichever userid is attempting to clear the SDLQ is not authorized to use the CLEAR command.
Look at the WMQ error logs to see exactly which userid is attempting to access the dead-letter-queue. Ensure that the id is in the mqm group. |
Thanks Bruce.
The "TEPUser" from TEPS client is trying to CLEAR the queue from his desktop. In the MQ traces, I see the user as "TEPUSER". I see the user is converting to UPPERCASE. Not sure how to pass the original ID to MQ manager to CLEAR the queue from TEPS client.
Thanks. |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sat Dec 11, 2010 1:41 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Here is one more MQ trace output when trying to delete the msg from TEPS console from a queue.
| Code: |
15:24:25.666021 22368.24 ---------------{ zfuUnlockHashTable
15:24:25.666027 22368.24 ----------------{ xcsReleaseMutexSem
15:24:25.666071 22368.24 ----------------} xcsReleaseMutexSem rc=OK
15:24:25.666078 22368.24 ---------------} zfuUnlockHashTable rc=OK
15:24:25.666086 22368.24 ---------------{ zutCvtMQName2Str
15:24:25.666092 22368.24 ---------------} zutCvtMQName2Str rc=OK
15:24:25.666099 22368.24 ---------------{ xcsGetpwnam
15:24:25.666113 22368.24 name(TEPUSER) pwd(ffffffff7873bfc8) buffer(ffffffff7873c034) bufsize(3363) result(ffffffff7873cd70)
15:24:25.666358 22368.24 ---------------}! xcsGetpwnam rc=Unknown(FFFFFFFF)
15:24:25.666378 22368.24 UnknownPrincipal(TEPUSER)
15:24:25.666385 22368.24 --------------}! zfu_as_searchprincipallist rc=lrcE_UNKNOWN_ENTITY
15:24:25.666397 22368.24 Principal(TEPUSER ) EntityType(1)
15:24:25.666397 22368.24 ObjectName(TEST ) ObjectType(1)
15:24:25.666397 22368.24 PrimaryOnly(0) AccessTemplate(6) Authorization(0)
15:24:25.666404 22368.24 -------------}! zfu_as_calculateauthority rc=lrcE_UNKNOWN_ENTITY
15:24:25.666411 22368.24 -------------{ xcsIsEnvironment
15:24:25.666424 22368.24 xcsIsEnvironment[MQSAUTHERRORS] = FALSE
15:24:25.666430 22368.24 -------------} xcsIsEnvironment rc=OK
15:24:25.666436 22368.24 ------------}! zfu_as_checkobjectauthority rc=MQRC_UNKNOWN_ENTITY
15:24:25.666443 22368.24 ------------{ zfp_ss_getnext_component
15:24:25.666449 22368.24 ------------}! zfp_ss_getnext_component rc=zrcF_NOT_FOUND
15:24:25.666456 22368.24 ------------{ zfp_ss_unlock_service
15:24:25.666461 22368.24 ------------} zfp_ss_unlock_service rc=OK
15:24:25.666467 22368.24 -----------}! gpiCheckObjectAuthority rc=lrcE_NOT_AUTHORIZED
15:24:25.666474 22368.24 -----------{ apiEnquireObject
15:24:25.666484 22368.24 Object(TEST ) ObjectType(1) LockMode(0)
15:24:25.666492 22368.24 ------------{ aouLockObjectCatalogue
15:24:25.666499 22368.24 -------------{ xcsRequestMutexSem
15:24:25.666505 22368.24 -------------} xcsRequestMutexSem rc=OK
15:24:25.666512 22368.24 ------------} aouLockObjectCatalogue rc=OK
15:24:25.666519 22368.24 ------------{ aocEnquireObject
15:24:25.666525 22368.24 -------------{ aouLocateEntry
15:24:25.666531 22368.24 --------------{ aotLocateEntryByName
15:24:25.666538 22368.24 ---------------{ aouHash
15:24:25.666544 22368.24 ---------------} aouHash rc=OK
15:24:25.666555 22368.24 --------------} aotLocateEntryByName rc=OK
15:24:25.666561 22368.24 -------------} aouLocateEntry rc=OK
15:24:25.666568 22368.24 -------------{ aouUnlockObjectCatalogue
15:24:25.666574 22368.24 --------------{ xcsReleaseMutexSem
15:24:25.666580 22368.24 --------------} xcsReleaseMutexSem rc=OK
15:24:25.666586 22368.24 -------------} aouUnlockObjectCatalogue rc=OK
15:24:25.666591 22368.24 -------------{ xcsRequestMutexSem
15:24:25.666597 22368.24 -------------} xcsRequestMutexSem rc=OK
15:24:25.666605 22368.24 -------------{ xcsReleaseMutexSem
15:24:25.666611 22368.24 -------------} xcsReleaseMutexSem rc=OK
15:24:25.666617 22368.24 ------------} aocEnquireObject rc=OK
15:24:25.666624 22368.24 -----------} apiEnquireObject rc=OK
15:24:25.666629 22368.24 ----------}! kqiAuthorityChecks rc=lrcE_NOT_AUTHORIZED
15:24:25.666636 22368.24 ---------}! kqiResolveHereQName rc=lrcE_NOT_AUTHORIZED
15:24:25.666643 22368.24 ---------{ kqiDeleteQPath
15:24:25.666649 22368.24 ---------} kqiDeleteQPath rc=OK
15:24:25.666655 22368.24 --------}! kqiSetupQPath rc=lrcE_NOT_AUTHORIZED
15:24:25.666663 22368.24 --------{ xcsQueryMTimeFn
15:24:25.666669 22368.24 --------} xcsQueryMTimeFn rc=OK
15:24:25.666677 22368.24 -------}! kqiOpenQueue rc=lrcE_NOT_AUTHORIZED
15:24:25.666683 22368.24 -------{ kqiFreeObjectHandle
15:24:25.666689 22368.24 --------{ xcsRequestMutexSem
15:24:25.666694 22368.24 --------} xcsRequestMutexSem rc=OK
15:24:25.666703 22368.24 --------{ xcsReleaseMutexSem
15:24:25.666708 22368.24 --------} xcsReleaseMutexSem rc=OK
15:24:25.666715 22368.24 --------{ xcsFreeQuickCell
15:24:25.666724 22368.24 hqc(2::5::5-4448224)
15:24:25.666732 22368.24 ---------{ xllSpinLockRequest
15:24:25.666739 22368.24 ---------} xllSpinLockRequest rc=OK
15:24:25.666746 22368.24 ---------{ xllSpinLockRelease
15:24:25.666751 22368.24 ---------} xllSpinLockRelease rc=OK
15:24:25.666757 22368.24 --------} xcsFreeQuickCell rc=OK
15:24:25.666762 22368.24 -------} kqiFreeObjectHandle rc=OK
15:24:25.666770 22368.24 -------{ kqiErrorEvent
15:24:25.666777 22368.24 -------}! kqiErrorEvent rc=krcI_EVENT_OFF
15:24:25.666783 22368.24 ------}! kqiOpenIt rc=lrcE_NOT_AUTHORIZED
15:24:25.666805 22368.24 Returning an error to the AI Layer: CompCode 2 Reason 7f3 MQRC_NOT_AUTHORIZED
15:24:25.666812 22368.24 -----} kpiMQOPEN rc=OK
15:24:25.666819 22368.24 -----{ zsqDeleteObj
15:24:25.666827 22368.24 ------{ xcsFreeMem
15:24:25.666835 22368.24 component:32 pointer:100186568
15:24:25.666846 22368.24 ------} xcsFreeMem rc=OK
15:24:25.666852 22368.24 -----} zsqDeleteObj rc=OK
15:24:25.666857 22368.24 ----}! zsqMQOPEN rc=MQRC_NOT_AUTHORIZED
15:24:25.666863 22368.24 ---}! zlaMQOPEN rc=MQRC_NOT_AUTHORIZED
15:24:25.666872 22368.24 ---{ zcpDeleteMessage
15:24:25.666880 22368.24 ---} zcpDeleteMessage rc=OK
15:24:25.666887 22368.24 ---{ zcpSendOnPipe
15:24:25.666895 22368.24 ----{ xcsResetEventSem
15:24:25.666901 22368.24 ----} xcsResetEventSem rc=OK
15:24:25.666907 22368.24 ----{ xcsPostEventSem
15:24:25.666916 22368.24 xcsPostEventSem 1::0::0-487568
15:24:25.666939 22368.24 ----} xcsPostEventSem rc=OK
15:24:25.666947 22368.24 ---} zcpSendOnPipe rc=OK
15:24:25.666954 22368.24 --} zlaProcessMQIRequest rc=OK
15:24:25.666960 22368.24 -} zlaProcessMessage rc=OK
15:24:25.666968 22368.24 -{ zcpReceiveOnPipe
15:24:25.666976 22368.24 --{ xcsWaitEventSem
15:24:25.666985 22368.24 xcsWaitEventSem 1::0::0-487736 |
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Dec 11, 2010 2:47 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I must have missed where you posted the platform(s) where you are running the TEPS client and the managed qmgr.
_________________
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 |
|
|
| chris boehnke |
| Posted: Sat Dec 11, 2010 2:57 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| bruce2359 wrote: |
| I must have missed where you posted the platform(s) where you are running the TEPS client and the managed qmgr. |
Below are the platforms
TEPS & TEMS - Windows 2003
TEPS client - Windows Desktop (Windows XP)
Qmgr/ Omegamon agent - Solaris 10.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Dec 11, 2010 3:22 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
So, the qmgr to be managed is on Solaris? And the Windows box is where the TEPS client attempting to manage the qmgr exists?
So, the 2035 is on the Solaris box, yes?
And the trace is from Solaris?
15:24:25.666397 22368.24 Principal(TEPUSER ) EntityType(1)
15:24:25.666397 22368.24 ObjectName(TEST
From the trace snippet, it seems TEPUSER has insufficient authority to TEST - the qmgr name?
_________________
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 |
|
|
| fjb_saper |
| Posted: Sat Dec 11, 2010 5:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you running the latest version of WMQ on Solaris? I seem to remember that there was a problem early on (possibly base version) where the user name was not translated properly case wise. I suggest you use an only lower case user name on TEPS as well as on Solaris. If this still does not work open a PMR. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sat Dec 11, 2010 7:14 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| bruce2359 wrote: |
So, the qmgr to be managed is on Solaris? And the Windows box is where the TEPS client attempting to manage the qmgr exists?
So, the 2035 is on the Solaris box, yes?
And the trace is from Solaris?
15:24:25.666397 22368.24 Principal(TEPUSER ) EntityType(1)
15:24:25.666397 22368.24 ObjectName(TEST
From the trace snippet, it seems TEPUSER has insufficient authority to TEST - the qmgr name? |
We see 2035 on MQ agent logs on solaris box and also see NOT_AUTHORIZED on the TEPS console when try to CLEAR the msg from any of the queue.
On Solaris box, we have the user TEPUser which is part of mqm group. When we log into the TEPS client with the TEPUser and try to CLEAR the msg from a queue, we see 2035 error on TEPS console and also see the MQ agent logs on solaris box. Tried to turn on MQ trace to see whether can be found out from traces. When we look at the MQ traces, we see the user as TEPUSER(uppercase) instead of TEPUser accessing the CLEAR QL(TEST) command. As UNIX is case senstitive, TEPUSER is not recognised by OS and getting 2035 error.
Not sure how to use TEPS client to DELETE the msgs from queues(TEST env) by passing the right user to the MQ manager.
Thanks. |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sat Dec 11, 2010 7:18 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| fjb_saper wrote: |
| Are you running the latest version of WMQ on Solaris? I seem to remember that there was a problem early on (possibly base version) where the user name was not translated properly case wise. I suggest you use an only lower case user name on TEPS as well as on Solaris. If this still does not work open a PMR. |
We are running MQ version 6.0.2.3 on solaris box. The TEPUser from TEPS client is able to browse the msgs but not the DELETE and FORWARD msgs and getting 2035.
Any input is appreciated.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Dec 11, 2010 10:56 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| We see 2035 on MQ agent logs on solaris box and also see NOT_AUTHORIZED on the TEPS console when try to CLEAR the msg from any of the queue. |
I asked where the 2035 occurred, not where you saw the error. I'm guessing that TEPS is using a client channel to connect to the qmgr, so the Solaris qmgr is where the 2035 actually happened. Then the TEPS client echoed the 2035.
I also asked you to look in the qmgr error logs on both client and server. Did you do so? I couldn't tell from the reply you posted if you, in fact, looked at the qmgr error logs.
| Quote: |
| ...client is able to browse the msgs but not the DELETE and FORWARD msgs and getting 2035. |
If the TEPS client (Windows) can browse and get messages, but not CLEAR them, I'm going to speculate (guess) that the userid attempting the CLEAR QL() PURGE command doesn't have mqm OR sufficient authority on the qmgr where the local queue exists.
Use the dspmqaut and/or dmpmqaut command to display the authorizations for the userid. And, once again, look at the mq error logs.
_________________
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 |
|
|
| fjb_saper |
| Posted: Sun Dec 12, 2010 2:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| chris boehnke wrote: |
| fjb_saper wrote: |
| Are you running the latest version of WMQ on Solaris? I seem to remember that there was a problem early on (possibly base version) where the user name was not translated properly case wise. I suggest you use an only lower case user name on TEPS as well as on Solaris. If this still does not work open a PMR. |
We are running MQ version 6.0.2.3 on solaris box. The TEPUser from TEPS client is able to browse the msgs but not the DELETE and FORWARD msgs and getting 2035.
Any input is appreciated.
Thanks. |
Does the TEPUser actually have Get authority on the queue? You'll need this for deleting and forwarding messages...
As I said before 6.0.2.3 is a fairly old version and I can't remember if it had the case troubles with the user name. Upgrade!
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sun Dec 12, 2010 5:42 am Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| fjb_saper wrote: |
| chris boehnke wrote: |
| fjb_saper wrote: |
| Are you running the latest version of WMQ on Solaris? I seem to remember that there was a problem early on (possibly base version) where the user name was not translated properly case wise. I suggest you use an only lower case user name on TEPS as well as on Solaris. If this still does not work open a PMR. |
We are running MQ version 6.0.2.3 on solaris box. The TEPUser from TEPS client is able to browse the msgs but not the DELETE and FORWARD msgs and getting 2035.
Any input is appreciated.
Thanks. |
Does the TEPUser actually have Get authority on the queue? You'll need this for deleting and forwarding messages...
As I said before 6.0.2.3 is a fairly old version and I can't remember if it had the case troubles with the user name. Upgrade! |
Yes, the "TEPUser" is part of mqm group on the solaris machine where the Qmgr/ agent is running. The "TEPUSER"(uppercase) doesn't have perms. When I turn on MQ traces and look at the traces, I see the user as TEPUSER(uppercase). When the TEPUser is trying to DELETE/ FORWARD, I see the user passed to the MQ manager is TEPUSER(in upper case). How to pass the original user id from TEPS client to the QMgr from TEPS console (TEPUser)?.
We are under the process of upgrading to version 7 but right now the monitoring agent should function properly in DELETE/ FORWARD functions. I can open a PMR but I just want to make sure we are not missing anything with our setup.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 12, 2010 8:14 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Moved to General Discussion.
_________________
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 |
|
|
| fjb_saper |
| Posted: Sun Dec 12, 2010 2:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
Yes, the "TEPUser" is part of mqm group on the solaris machine where the Qmgr/ agent is running. The "TEPUSER"(uppercase) doesn't have perms. When I turn on MQ traces and look at the traces, I see the user as TEPUSER(uppercase). When the TEPUser is trying to DELETE/ FORWARD, I see the user passed to the MQ manager is TEPUSER(in upper case). How to pass the original user id from TEPS client to the QMgr from TEPS console (TEPUser)?.
We are under the process of upgrading to version 7 but right now the monitoring agent should function properly in DELETE/ FORWARD functions. I can open a PMR but I just want to make sure we are not missing anything with our setup. |
I remember there were some case problems for the userid in the early versions of 6.0 especially from windows to Unix. Upgrade to the latest of 6.0.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
