MQSeries.net :: View topic - MO71

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » MO71 - Queue history

MO71 - Queue history

« View previous topic :: View next topic »

Author

Message

hench

Posted: Thu Oct 17, 2013 3:05 am Post subject: MO71 - Queue history

Newbie

Joined: 09 Aug 2004
Posts: 9

Hi,

Suppose we have an empty queue right now.
Is it possible with MO71 to find out when (date,time) the last put/get was made on that queue ?

Regards. Hench

hughson

Posted: Thu Oct 17, 2013 4:32 am Post subject:

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

If you have turned on queue monitoring (MONQ attribute) then it is possible to see the last put and last get times and dates.

Retrospectively turning on queue monitoring will not help though. It had to be on when the last put or get was done.

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

wmbwmq

Posted: Fri Oct 18, 2013 6:19 am Post subject:

Acolyte

Joined: 18 Jul 2011
Posts: 66

Morag,
I think Put/get date etc are part of PCF and are always available irrespective of MONQ is on or off(at least in distributed environments)
It is weird though. May be that fetching of PCF takes an extra cycle and MONQ controls whether to fetch that or not?

fjb_saper

Posted: Fri Oct 18, 2013 6:24 am Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

wmbwmq wrote:

Your pcf may not return any information if MONQ is set to OFF.

_________________
MQ & Broker admin

wmbwmq

Posted: Fri Oct 18, 2013 6:28 am Post subject:

Acolyte

Joined: 18 Jul 2011
Posts: 66

Saper,
Sorry not true. You can test this on some queue yourself and see

bruce2359

Posted: Fri Oct 18, 2013 6:31 am Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

wmbwmq wrote:

Saper,
Sorry not true. You can test this on some queue yourself and see

I believe that fjb_saper is saying that a PCF command cannot return accurate/current/correct/reliable data if MONQ is not enabled.
_________________
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.

wmbwmq

Posted: Fri Oct 18, 2013 6:38 am Post subject:

Acolyte

Joined: 18 Jul 2011
Posts: 66

mqm@ >echo "def ql(SAPER_ROCKS)" | runmqsc TSTQMGR
1 : def ql(SAPER_ROCKS)
AMQ8006: WebSphere MQ queue created.
mqm@ >echo "dis qs(SAPER_ROCKS)" | runmqsc TSTQMGR
1 : dis qs(SAPER_ROCKS)
MEDIALOG( ) MONQ(OFF)
mqm@ >/opt/mqm/samp/bin/amqsput SAPER_ROCKS TSTQMGR
Sample AMQSPUT0 start
target queue is SAPER_ROCKS
hi
Sample AMQSPUT0 end
mqm@ >echo "dis qs(SAPER_ROCKS)" | runmqsc TSTQMGR
1 : dis qs(SAPER_ROCKS)
AMQ8450: Display queue status details.
QUEUE(SAPER_ROCKS) TYPE(QUEUE)
CURDEPTH(1) IPPROCS(0)
LGETDATE( ) LGETTIME( )
LPUTDATE( ) LPUTTIME( )
MEDIALOG( ) MONQ(OFF)
MSGAGE( ) OPPROCS(0)
QTIME( , ) UNCOM(NO)
mqm@ >echo "alter ql(SAPER_ROCKS) monq(high)" | runmqsc TSTQMGR
AMQ8008: WebSphere MQ queue changed.
mqm@ >echo "dis qs(SAPER_ROCKS)" | runmqsc TSTQMGR
AMQ8450: Display queue status details.
QUEUE(SAPER_ROCKS) TYPE(QUEUE)
CURDEPTH(1) IPPROCS(0)
LGETDATE( ) LGETTIME( )
LPUTDATE(2013-10-1

LPUTTIME(10.33.41)
MEDIALOG( ) MONQ(HIGH)
MSGAGE(19) OPPROCS(0)
QTIME( , ) UNCOM(NO)

bruce2359

Posted: Fri Oct 18, 2013 6:43 am Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

MONQ is enabled in this example.

wmbwmq wrote:

LPUTTIME(10.33.41)
MEDIALOG( ) MONQ(HIGH)
MSGAGE(19) OPPROCS(0)
QTIME( , ) UNCOM(NO)

_________________
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.

wmbwmq

Posted: Fri Oct 18, 2013 6:45 am Post subject:

Acolyte

Joined: 18 Jul 2011
Posts: 66

Bruce,
you will see that it was not enabled before putting the message if you read my post again...

hughson

Posted: Fri Oct 18, 2013 8:08 am Post subject:

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

If MONQ(OFF) you get no data returned in those fields thus:-

Code:

QUEUE(Q2) TYPE(QUEUE) CURDEPTH(2) IPPROCS(0)
LGETDATE( ) LGETTIME( ) LPUTDATE( ) LPUTTIME( )
MEDIALOG( ) MONQ(OFF) MSGAGE( ) OPPROCS(0)
QTIME(,) UNCOM(NO)

If MONQ(HIGH) then you will as already demonstrated by others.

If you cycle your queue manager then even if you have MONQ(HIGH) you can't see the information until something new happens on the queue.
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

wmbwmq

Posted: Fri Oct 18, 2013 8:16 am Post subject:

Acolyte

Joined: 18 Jul 2011
Posts: 66

I was referring your quote

Quote:

Retrospectively turning on queue monitoring will not help though. It had to be on when the last put or get was done.

So, I can just turn it on anytime later and get the status. Which also makes me wonder why we have MONQ parameter in the first place.

bruce2359

Posted: Fri Oct 18, 2013 8:18 am Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

hughson wrote:

If MONQ(OFF) you get no data returned in those fields thus:-

Code:

QUEUE(Q2) TYPE(QUEUE) CURDEPTH(2) IPPROCS(0)
LGETDATE( ) LGETTIME( ) LPUTDATE( ) LPUTTIME( )
MEDIALOG( ) MONQ(OFF) MSGAGE( ) OPPROCS(0)
QTIME(,) UNCOM(NO)

These fields are not returned because they would be stale for whatever time period followed setting MONQ(OFF). It is up to the sysadmin to reset queue stats, if necessary/required.
_________________
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.

hughson

Posted: Fri Oct 18, 2013 9:24 am Post subject:

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

wmbwmq wrote:

I was referring your quote

Quote:

Retrospectively turning on queue monitoring will not help though. It had to be on when the last put or get was done.

So, I can just turn it on anytime later and get the status. Which also makes me wonder why we have MONQ parameter in the first place.

The MONQ parameter protects a number of different attributes, not just these two. The parameters it protects take time stamps to gather their information. The gathering of time stamps can be expensive on some platforms (less so on others). As it happens PutDate/Time is generated anyway to fill in the MQMD fields, but you wouldn't want all the others to be collected if your platform was one where this cost was high.
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » MO71 - Queue history

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP