Hi Barbara,
Well, I congratulate you on finding a product feature! You've caused a
fair amount of puzzled looks and scratching of heads but what you describe
is exactly what happens.
The UNCOM attribute is documented as returning only two values YES (1) and
NO (0). However, as you have discovered the Distributed product actually
returns the number of uncommitted messages. Now, MO71 has a strategy that
if a returned number matches one of the pre-defined values then is
displayed that value otherwise it will just display the numbers. Which is
why you'll see MO71 report NO, YES, 2,3,4,5.........
The MQ Explorer displays any unexpected value as [Unknown]. So you'll see
the sequence as NO, YES, [Unknown]......
Now, it appears as though MQSC will treat any non-zero value as YES and
won't report the number.
The z/OS always just returns YES and NO.
So, what you've found is am inconsistency between both the books and the
product and an inconsistency between the Distributed and z/OS products. A
pretty good find! The question is what do we do about it ?. The simplest
thing for us to do is to change the command server in the Dist. product to
only return 0 and 1; which means this potentially useful feature is lost.
Alternatively we change the documentation (and possibly MQ Explorer) to
allow for values greater that 1. It's just possible that in the future
the z/OS product could be changed to also report the actual number but I'm
told that this is a non-trivial change and may never happen. We believe
that changing the documentation and keeping the inconsistency is the
lesser of two evils. We will raise a documentation defect.
So, it seems that if you want to monitor the number of uncommitted
messages you will not be able to do it via MQSC. You can do so via MO71
and setting auto-refresh and adding an appropriate filter to the window to
page you (or whatever) when the value reaches a certain limit.
Alternatively you could write a fairly simple PCF application it
repeatedly query the value.
Thanks for bringing this to our attention. Our apologies for any confusion
caused,
Cheers,
Paul
Paul G Clarke
WebSphere Messaging Clients
Hursley Park
Robert Broderick <[EMAIL PROTECTED]>
Sent by: MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>
01/08/2007 16:26
Please respond to
MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>
To
MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
cc
Subject
Re: Finding number of uncommitted msg using runmqsc?
1 + 1 + 1+ 1 + ......... = 237 ??????????????
Date: Tue, 31 Jul 2007 21:38:48 +0100
From: [EMAIL PROTECTED]
Subject: Re: Finding number of uncommitted msg using runmqsc?
To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
Hi Barbara,
I can't think why UNCOM would have a value of 237. Like MQSC I would
expect it to be either YES or NO. What version of MQ server and MO71 are
you using ? Any chance you could send me a screenshot of your dialog just
to ensure we're talking about the same thing.
Cheers,
P.
Paul G Clarke
WebSphere Messaging Clients
Hursley Park
"Hale, Barbara S" <[EMAIL PROTECTED]>
Sent by: MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT> 31/07/2007
19:32
Please respond to
MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>
To
MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
cc
Subject
Re: Finding number of uncommitted msg using runmqsc?
Using runmqsc, the UNCOM field is just "YES", not the actual number of
uncommitted messages...
1 : dis qstatus(XXX.YYY.QL) UNCOM
AMQ8450: Display queue status details.
QUEUE(XXX.YYY.QL)
TYPE(QUEUE) CURDEPTH(0)
UNCOM(YES)
I hover over the column in MO71 and it says Uncommitted Messages(UNCOM),
but it has an actual number of messages in it (237) rather than "YES" so
I'm still unsure how MO71 gets the information.
Barbara
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf
Of Robert Broderick
Sent: Tuesday, July 31, 2007 10:02 AM
To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: Finding number of uncommitted msg using runmqsc?
I would think to display the number you woud minus the numner of actual
messages returned from a browse till 2033 from the queue depth. That is
not exact because you have to worry about expired, and messages locked
and............but...................................................
bobbee
> Date: Tue, 31 Jul 2007 17:30:01 +0100
> From: [EMAIL PROTECTED]
> Subject: Re: Finding number of uncommitted msg using runmqsc?
> To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
>
> If MO71 can tell you something, so can runmqsc. If you hover your mouse
> pointer over the column title on the list which shows you the number of
> uncommitted messages it will tell you the MQSC attribute name inside the
> brackets.
>
> I can't think what attribute tells you this fact - maybe I'm having an
off
> day.
>
> Cheers
> Morag
>
> Morag Hughson
> WebSphere MQ for z/OS Development
> Internet: [EMAIL PROTECTED]
>
>
>
>
> "Hale, Barbara S" <[EMAIL PROTECTED]>
> Sent by: MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>
> 31/07/2007 15:48
> Please respond to
> MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>
>
>
> To
> MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
> cc
>
> Subject
> Finding number of uncommitted msg using runmqsc?
>
>
>
>
>
>
> I wanted to write a small shell script to find the number of uncommitted
> msgs on a queue. Using DISPLAY QSTATUS in runmqsc I can see that I have
> uncommitted messages, UNCOM(YES). And, using the wonderous M071, I can
> see that I have 71 uncommitted messages so I know that the number of
> uncommitted messages information is available.
> Is there a command in runmqsc that will give me the actual number of
> uncommitted messages rather than just "YES" or "NO"? I want to be able
to
> track the number of uncommitted messages over time.
> Thanks for your help,
> Barbara
> ------------
> Barbara Hale
> Con-way Enterprise Services/Distributed Systems Administrator
> 2055 NW Savier Street
> Portland, OR 97209
>
>
> List Archive - Manage Your List Settings - Unsubscribe
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
>
>
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
>
> To unsubscribe, write to [EMAIL PROTECTED] and,
> in the message body (not the subject), write: SIGNOFF MQSERIES
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Don't get caught with egg on your face. Play Chicktionary!
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Missed the show? Watch videos of the Live Earth Concert on MSN. See them
now!
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
To unsubscribe, write to [EMAIL PROTECTED] and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
