| Author |
Message
|
| sotoka |
 Posted: Sat Mar 04, 2006 9:38 am Post subject: MQRC_CHANNEL_STOPPED_BY_USER not returning some parameters |
 |
|
Novice
Joined: 05 Feb 2006
Posts: 12
|
Hello,
"WebSphere Event Monitoring" (5.3 edition) says that
the event data of MQRC_CHANNEL_STOPPED_BY_USER will always
contain four parameters: QMgrName, ReasonQualifier, ChannelName
and ErrorIdentifier. It should also contain XmitQName if
the channel is a sender, server, cluster-sender, or cluster-receiver.
However, when using MQ Exporer to stop the channel,
or when issuing PCF commands, I'm observing a different situation.
ParameterCount is always equal to 3, and the only parameters returned
are QMgrName, ReasonQualifier and ChannelName.
Below is the message contents.
07 00 00 00 24 00 00 00 ....$...
01 00 00 00 2E 00 00 00 ........
01 00 00 00 01 00 00 00 ........
00 00 00 00 E7 08 00 00 ....ç...
03 00 00 00 04 00 00 00 ........
1C 00 00 00 DF 07 00 00 ....ß...
00 00 00 00 05 00 00 00 ........
45 54 41 2E 31 00 00 00 ETA.1...
04 00 00 00 18 00 00 00 ........
AD 0D 00 00 00 00 00 00 Â.......
03 00 00 00 54 4F 32 00 ....TO2.
03 00 00 00 10 00 00 00 ........
FC 03 00 00 0A 00 00 00 ü.......
ErrorIdentifier is not returned. Fifth byte in a last line
is a ReasonQualifier (MQRQ_CHANNEL_STOPPED_DISABLED = 0x0a), right? Not
an ErrorIdentifier?
XmitQName is also not returned although the channel is a server.
dis chl(TO2) chltype xmitq
3 : dis chl(TO2) chltype xmitq
AMQ8414: Display Channel details.
CHANNEL(TO2) CHLTYPE(SVR)
XMITQ(XQ.TO2)
Also - my PCF commands specify full channel name (that is, TO2), without
any "*" characters; in other words, I don't specify a generic name. In that
case, a ConnectionName parameter should be returned according to the docs,
but it isn't returned.
What could be the reason of that behaviour?
thanks,
So |
|
| Back to top |
|
 |
| wschutz |
| Posted: Sat Mar 04, 2006 11:48 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
are you at a reasonibly current csdl level?
_________________
-wayne |
|
| Back to top |
|
|
| sotoka |
| Posted: Sat Mar 04, 2006 12:36 pm Post subject: |
|
|
Novice
Joined: 05 Feb 2006
Posts: 12
|
> are you at a reasonibly current csdl level?
Sorry for not providing this earlier.
D:\WebSphere MQ\bin>mqver.exe
Name: WebSphere MQ
Version: 530.12 CSD12
CMVC level: p530-12-L051208
BuildType: IKAP - (Production) |
|
| Back to top |
|
|
| wschutz |
| Posted: Sat Mar 04, 2006 2:56 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
using evmon (ms0k), I get this for a v53 fp9 and v6 fp1 qmgr on linux for a sender chl:
Reason Code : MQRC_CHANNEL_STOPPED
Event type : CHANNEL EVENT
Event Put Date : 2006/03/04
Event Put Time : 22:35:34
MQCA_Q_MGR_NAME : WSCHUTZ
MQCACH_CHANNEL_NAME : WSCHUTZ.TEST
MQCACH_XMIT_Q_NAME : TEST
MQCACH_CONNECTION_NAME : localhost(1430)
MQIACF_REASON_QUALIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_ERROR_IDENTIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_DATA_INT_1 : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_ERROR_DATA_INT_2 : MQRQ_CHL_STOPPED_DISABLED
MQCACF_AUX_ERROR_DATA_STR_1 : WSCHUTZ.TEST
MQCACF_AUX_ERROR_DATA_STR_2 :
MQCACF_AUX_ERROR_DATA_STR_3 :
for a svr channel, I get:
Reason Code : MQRC_CHANNEL_STOPPED
Event type : CHANNEL EVENT
Event Put Date : 2006/03/04
Event Put Time : 23:00:46
MQCA_Q_MGR_NAME : WSCHUTZ
MQCACH_CHANNEL_NAME : WSCHUTZ.TEST.SVR
MQCACH_XMIT_Q_NAME : TEST
MQCACH_CONNECTION_NAME : 127.0.0.1
MQIACF_REASON_QUALIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_ERROR_IDENTIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_DATA_INT_1 : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_ERROR_DATA_INT_2 : MQRQ_CHL_STOPPED_DISABLED
MQCACF_AUX_ERROR_DATA_STR_1 : WSCHUTZ.TEST.SVR
MQCACF_AUX_ERROR_DATA_STR_2 :
MQCACF_AUX_ERROR_DATA_STR_3 :
-----------------------------------------------------------
Reason Code :
Event type : CHANNEL EVENT
Event Put Date : 2006/03/04
Event Put Time : 23:00:46
MQCA_Q_MGR_NAME : WSCHUTZ
MQCACH_CHANNEL_NAME : WSCHUTZ.TEST.SVR
MQIACF_REASON_QUALIFIER : MQRQ_CHL_STOPPED_DISABLED
so this is a little different than what you're getting as I'm always getting a conname and xmit .... use evmon and compare results .... one more thing... in both cases, the "stop" command was issued from the end of the channel where the xmitq was ....
_________________
-wayne |
|
| Back to top |
|
|
| sotoka |
| Posted: Sat Mar 04, 2006 3:42 pm Post subject: |
|
|
Novice
Joined: 05 Feb 2006
Posts: 12
|
> I get this for a v53 fp9 and v6 fp1 qmgr on linux for a sender chl:
I don't have access to a UNIX box right now so can't tell if that makes
a difference.
[snip]
> so this is a little different than what you're getting as I'm always getting a > conname and xmit .... use evmon and compare results ....
Thanks for your help, wschutz!
However, it seems that evmon from MS0K does not support MQRC_CHANNEL_STOPPED_BY_USER event but only MQRC_CHANNEL_STOPPED.
If I modify evmon a little bit by adding
case MQRC_CHANNEL_STOPPED_BY_USER:
strcpy(rval, "MQRC_CHANNEL_STOPPED_BY_USER");
break;
somewhere into the dispReason function, I'm getting this
-----------------------------------------------------------
Reason Code : MQRC_CHANNEL_STOPPED_BY_USER
Event type : CHANNEL EVENT
Event Put Date : 2006/03/04
Event Put Time : 23:26:02
MQCA_Q_MGR_NAME : ETA.1
MQCACH_CHANNEL_NAME : TO2
MQIACF_REASON_QUALIFIER : MQRQ_CHL_STOPPED_DISABLED
-----------------------------------------------------------
Reason Code : MQRC_CHANNEL_STOPPED
Event type : CHANNEL EVENT
Event Put Date : 2006/03/04
Event Put Time : 23:26:02
MQCA_Q_MGR_NAME : ETA.1
MQCACH_CHANNEL_NAME : TO2
MQCACH_XMIT_Q_NAME : XQ.TO2
MQCACH_CONNECTION_NAME : 127.0.0.1(1415)
MQIACF_REASON_QUALIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_ERROR_IDENTIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_DATA_INT_1 : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_ERROR_DATA_INT_2 : MQRQ_CHL_STOPPED_DISABLED
MQCACF_AUX_ERROR_DATA_STR_1 : TO2
MQCACF_AUX_ERROR_DATA_STR_2 : ♦
MQCACF_AUX_ERROR_DATA_STR_3 : UALIFIER : MQRQ_CH☺☻'
-----------------------------------------------------------
I noticed that there are two messages being put onto the SYSTEM.ADMIN.CHANNEL.EVENT queue after I manually stop the channel (using MQ Explorer or via PCF). First one, put on by AMQPCSEA.EXE, is MQRC_CHANNEL_STOPPED_BY_USER. The second one, on put by runmqchl.exe is MQRC_CHANNEL_STOPPED. There are no problems with the latter (i.e. all parameters are present).
Well, that makes a subtopic now  Why two events?
> one more thing... in both cases, the "stop" command was issued from
> the end of the channel where the xmitq was ....
Same here. |
|
| Back to top |
|
|
| sotoka |
| Posted: Sat Mar 04, 2006 3:48 pm Post subject: |
|
|
Novice
Joined: 05 Feb 2006
Posts: 12
|
> Well, that makes a subtopic now icon_smile.gif Why two events?
Hm, I guess I know why. MQRC_CHANNEL_STOPPED_BY_USER is created when user issues a STOP CHANNEL command and MQRC_CHANNEL_STOPPED is produced when channel actually stops. Right? |
|
| Back to top |
|
|
| wschutz |
| Posted: Sat Mar 04, 2006 3:52 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| sotoka wrote: |
> Well, that makes a subtopic now icon_smile.gif Why two events?
Hm, I guess I know why. MQRC_CHANNEL_STOPPED_BY_USER is created when user issues a STOP CHANNEL command and MQRC_CHANNEL_STOPPED is produced when channel actually stops. Right? |
makes sense to me ....
_________________
-wayne |
|
| Back to top |
|
|
| sotoka |
| Posted: Sun Mar 05, 2006 2:01 am Post subject: |
|
|
Novice
Joined: 05 Feb 2006
Posts: 12
|
wschutz, would you be so kind and recompile evmon with this case statement
in the dispReason function?
| Code: |
case MQRC_CHANNEL_STOPPED_BY_USER:
strcpy(rval, "MQRC_CHANNEL_STOPPED_BY_USER");
break;
|
I think I'll contact our IBM representatives if you tell me that evmon also on your boxes returns only 3 parameters.
Thanks! |
|
| Back to top |
|
|
| wschutz |
| Posted: Sun Mar 05, 2006 5:14 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Code: |
-----------------------------------------------------------
Reason Code : MQRC_CHANNEL_STOPPED_BY_USER
Event type : CHANNEL EVENT
Event Put Date : 2006/03/05
Event Put Time : 12:52:13
MQCA_Q_MGR_NAME : WSCHUTZ
MQCACH_CHANNEL_NAME : WSCHUTZ.TEST.SVR
MQIACF_REASON_QUALIFIER : MQRQ_CHL_STOPPED_DISABLED
-----------------------------------------------------------
Reason Code : MQRC_CHANNEL_STOPPED
Event type : CHANNEL EVENT
Event Put Date : 2006/03/05
Event Put Time : 12:52:14
MQCA_Q_MGR_NAME : WSCHUTZ
MQCACH_CHANNEL_NAME : WSCHUTZ.TEST.SVR
MQCACH_XMIT_Q_NAME : TEST
MQCACH_CONNECTION_NAME : 127.0.0.1
MQIACF_REASON_QUALIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_ERROR_IDENTIFIER : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_DATA_INT_1 : MQRQ_CHL_STOPPED_DISABLED
MQIACF_AUX_ERROR_DATA_INT_2 : MQRQ_CHL_STOPPED_DISABLED
MQCACF_AUX_ERROR_DATA_STR_1 : WSCHUTZ.TEST.SVR
MQCACF_AUX_ERROR_DATA_STR_2 :
MQCACF_AUX_ERROR_DATA_STR_3 :
|
however, this makes sense to me... I wouldn't expect that conname.xmitq would be in the MQRC_CHANNEL_STOPPED_BY_USER (as that comes the from the command and xmitq/conname are unresolved at that time), I would expect to find it in the MQRC_CHANNEL_STOPPED (which comes from the channel itself shutting down).
Does this cause a problem? You "are" getting the info, just in a different message than you expected....
_________________
-wayne |
|
| Back to top |
|
|
| sotoka |
| Posted: Sun Mar 05, 2006 5:28 am Post subject: |
|
|
Novice
Joined: 05 Feb 2006
Posts: 12
|
| Quote: |
however, this makes sense to me... I wouldn't expect that conname.xmitq would be in the MQRC_CHANNEL_STOPPED_BY_USER (as that comes the from the command and xmitq/conname are unresolved at that time), I would expect to find it in the MQRC_CHANNEL_STOPPED (which comes from the channel itself shutting down).
|
Thanks for that info! This clarifies much.
| Quote: |
Does this cause a problem? You "are" getting the info, just in a different message than you expected....
|
Not really, it's not a big problem at all. I've just noticed that actual behaviour differs from what the docs say and spent a couple of hours reviewing my code  to be sure I wasn't doing anything silly. OK, I'll just
assume that the documentation is not 100% correct regarding this event... |
|
| Back to top |
|
|
| wschutz |
| Posted: Sun Mar 05, 2006 5:54 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
i think the doc's wrong...I've submited a feedback to the info people.....
_________________
-wayne |
|
| Back to top |
|
|
| sotoka |
| Posted: Sun Mar 05, 2006 6:46 am Post subject: |
|
|
Novice
Joined: 05 Feb 2006
Posts: 12
|
| wschutz wrote: |
| i think the doc's wrong...I've submited a feedback to the info people..... |
Guess I should create a signature for this forum and put the "Thanks wschutz!" in there |
|
| Back to top |
|
|
| wschutz |
| Posted: Sun Mar 05, 2006 7:02 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
actually, i was wrong here:
| Quote: |
| using evmon (ms0k), I get this for a v53 fp9 and v6 fp1 qmgr on linux for a sender chl: |
ms0k is out of date... Sam's mo01 version of "evmon" is the way to go....
_________________
-wayne |
|
| Back to top |
|
|
|
|
