ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral IBM MQ SupportMQMON dynamic queues message persistence

Post new topicReply to topic
MQMON dynamic queues message persistence View previous topic :: View next topic
Author Message
eniomarques
PostPosted: Mon Oct 24, 2016 10:06 am Post subject: MQMON dynamic queues message persistence Reply with quote

Novice

Joined: 25 May 2015
Posts: 21
Location: Brazil

Hello everyone!

Is there any way to set the MQMON messages to expiry? We have a monitoring tool that is constantly alerting due a queue depth in the dead letter queue, and it's always caused by a persistent message intended to the MQMON dynamic queues that are already gone.

Thanks!

Back to top
View user's profile Send private message
PaulClarke
PostPosted: Mon Oct 24, 2016 10:16 am Post subject: Reply with quote

Guardian

Joined: 17 Nov 2005
Posts: 925
Location: New Zealand

By 'MQMON' do you mean MO71 or some other product ?
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
eniomarques
PostPosted: Mon Oct 24, 2016 10:19 am Post subject: Reply with quote

Novice

Joined: 25 May 2015
Posts: 21
Location: Brazil

PaulClarke wrote:
By 'MQMON' do you mean MO71 or some other product ?


yes MO71, yours
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Mon Oct 24, 2016 12:18 pm Post subject: Reply with quote

Guardian

Joined: 17 Nov 2005
Posts: 925
Location: New Zealand

Hi,

Well, it is probably better to deal with these sorts of things via support@mqgem.com but since you raise it here I'll answer it here.

It you look in the manual you can see that for each location you can specify the monitor interval. This is....

[OK Monitor Interval ['(' OK Expire ')' ] [ ',' Bad Monitor Interval ['(' Bad Expire ')' ] ] ]

This means that you can specify a interval and expiry time differently for when the the Queue Manager is responding and when it is not.

You don't say what version of MO71 you are using but this has been the case for many releases.

I hope this helps,

Regards,

Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Mon Oct 24, 2016 12:19 pm Post subject: Reply with quote

Grand Poobah

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

I am sure Paul's product does not usually use persistent messages, unless you ask it to.
Could you please check that message? Is it a response to a PCF command?
What is your OS and MQ version?


_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
eniomarques
PostPosted: Mon Oct 24, 2016 12:59 pm Post subject: Reply with quote

Novice

Joined: 25 May 2015
Posts: 21
Location: Brazil

PaulClarke wrote:
Hi,

Well, it is probably better to deal with these sorts of things via support@mqgem.com but since you raise it here I'll answer it here.

It you look in the manual you can see that for each location you can specify the monitor interval. This is....

[OK Monitor Interval ['(' OK Expire ')' ] [ ',' Bad Monitor Interval ['(' Bad Expire ')' ] ] ]

This means that you can specify a interval and expiry time differently for when the the Queue Manager is responding and when it is not.

You don't say what version of MO71 you are using but this has been the case for many releases.

I hope this helps,

Regards,

Paul.


Thanks Paul, I'll make sure the monitoring is turned off and watch the DLQ.



fjb_saper wrote:
I am sure Paul's product does not usually use persistent messages, unless you ask it to.
Could you please check that message? Is it a response to a PCF command?
What is your OS and MQ version?



I double checked and they are really not persistent, just have no expiration time. The DLH is missing the reason probably due a missing fix pack (this specific QM is at v7.5.0.1)

This is the message:
Code:
[  364 bytes] Message Descriptor (MQMD)
StrucId      :'MD  '
Version      :2
Report       :00000000
Message Type :2 (Reply msg)
Expiry       :-1
Feedback     :0 (None)
MQEncoding   :0x'222'
CCSID        :437
Format       :'MQDEAD  '
Priority     :0
Persistence  :0 (Not Persistent)
Message Id   :02000100AC6E4E051A210E58000000000000000000000000
              '.....nN..!.X............'
Correl. Id   :02000100AC6E4E051A210E58000000000000000000000000
              '.....nN..!.X............'
Backout Cnt. :0
ReplyToQ     :'                                                '
ReplyToQMgr  :'QMNAME                                       '
UserId       :'mqm         '
AccountingTkn:1601051500000084DA6CC43D37B6CC52B643FBE803000000000000000000000B
ApplIdentity :'                                '
PutApplType  :7 (Queue Manager)
PutApplName  :'amqpcsea                    '
Put Date     :'20161024'
Put Time     :'14563668'
ApplOriginDat:'    '
Group Id     :000000000000000000000000000000000000000000000000
Msg Seq No.  :1
Offset       :0
MsgFlags     :00000000
Original Len.:-1
444C4820 01000000 05080000 4D514D4F 4E2E6132 69363738 612E3538 30323431 42423244 43424138 33322020 20202020 20202020 20202020  DLH ........MQMON.a2i678a.580241BB2DCBA832             
20202020 454B534E 30364150 44202020 20202020 20202020 20202020 20202020 20202020 20202020 20202020 20202020 20202020 22020000      QMNAME                                       "...
B5010000 4D514144 4D494E20 06000000 616D7170 63736561 00000000 00000000 00000000 00000000 00000000 32303136 31303234 31343536  ....MQADMIN ....amqpcsea....................201610241456
33363638 02000000 24000000 01000000 0D000000 1C280000 01000000 00000000 00000000 05000000 04000000 44000000 E0070000 B5010000  3668....$............(......................D...........
30000000 454B532E 50524541 5554484F 52495A45 5041594D 454E5420 20202020 20202020 20202020 20202020 20202020 20202020 03000000  0...EDITEDQNAME                         ....
10000000 14000000 07000000 04000000 44000000 ED070000 B5010000 30000000 53505243 4C315044 20202020 20202020 20202020 20202020  ................D...........0...CLUSNAME               
20202020 20202020 20202020 20202020 20202020 20202020 03000000 10000000 3B000000 02000000 04000000 54000000 DD070000 B5010000                          ........;...........T...........
40000000 54323831 36333620 20202020 20202020 20202020 20202020 20202020 20202020 20202020 20202020 20202020 20202020 20202020  @...T281636                                             
20202020 20202020 20202020                                                                                                                 
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Mon Oct 24, 2016 2:46 pm Post subject: Reply with quote

Guardian

Joined: 17 Nov 2005
Posts: 925
Location: New Zealand

Hi,

This doesn't appear to be a monitor message but is just an INQUIRE QUEUE response. The DLH reason code is there, it is 2053 (Queue full.) You are clearly using a model queue for your replies. What is the maximum depth of the model queue ? And, how many queues etc do you have defined ?

As for persistent it appears to be AS Q DEF. What is the default persistent of your reply queue ?

Cheers,

Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
eniomarques
PostPosted: Mon Oct 24, 2016 3:12 pm Post subject: Reply with quote

Novice

Joined: 25 May 2015
Posts: 21
Location: Brazil

PaulClarke wrote:
Hi,

This doesn't appear to be a monitor message but is just an INQUIRE QUEUE response. The DLH reason code is there, it is 2053 (Queue full.) You are clearly using a model queue for your replies. What is the maximum depth of the model queue ? And, how many queues etc do you have defined ?

As for persistent it appears to be AS Q DEF. What is the default persistent of your reply queue ?

Cheers,

Paul.


That makes sense...

We usually set the default model queue as the reply queue for all of our QMs, but looks like itś happening just to a couple of new added QMs.

This QM have almost 700 local queues (shared in the cluster as well), but part of a big cluster, with 14 identical QMs and others..

This is the actual Q definition:

QUEUE(SYSTEM.DEFAULT.MODEL.QUEUE) TYPE(QMODEL)
ACCTQ(QMGR) ALTDATE(2016-07-15)
ALTTIME(16.44.02) BOQNAME( )
BOTHRESH(0) CLCHNAME( )
CRDATE(2016-07-15) CRTIME(15.48.13)
CUSTOM( ) DEFPRTY(0)
DEFPSIST(NO) DEFPRESP(SYNC)
DEFREADA(NO) DEFSOPT(EXCL)
DEFTYPE(TEMPDYN) DESCR( )
DISTL(NO) GET(ENABLED)
HARDENBO INITQ( )
MAXDEPTH(10000) MAXMSGL(4194304)
MONQ(QMGR) MSGDLVSQ(PRIORITY)
NOTRIGGER NPMCLASS(NORMAL)
PROCESS( ) PUT(ENABLED)
PROPCTL(COMPAT) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(999999999)
RETINTVL(999999999) NOSHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(FIRST) USAGE(NORMAL)


Also, where did you see the 2053? Couldn't find any '805' hexa value.
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Mon Oct 24, 2016 4:06 pm Post subject: Reply with quote

Guardian

Joined: 17 Nov 2005
Posts: 925
Location: New Zealand

Actually I just copied and pasted you message into our new MQEDIT product and it gives me this...
Code:
StrucId      :'DLH '
Version      :1
Reason       :2053 (Queue full.)
Dest. Queue  :'MQMON.a2i678a.580241BB2DCBA832                  '
Dest. QMgr   :'EKSN06APD                                       '
MQEncoding   :0x'222' (Reversed)
CCSID        :486
Format       :'MQADMIN '
PutApplType  :6 (UNIX)
PutApplName  :'amqpcsea....................'
Put Date     :'20161024'
Put Time     :'14563668'

The reason code is actually the 3rd set of 4 bytes. Which is '05080000' which, when byte swapped, is '00000805'

Cheers,

Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
bruce2359
PostPosted: Mon Oct 24, 2016 8:40 pm Post subject: Reply with quote

Poobah

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

PaulClarke wrote:
Actually I just copied and pasted you message into our new MQEDIT product and it gives me this...
Code:
StrucId      :'DLH '
Version      :1
Reason       :2053 (Queue full.)
Dest. Queue  :'MQMON.a2i678a.580241BB2DCBA832                  '
Dest. QMgr   :'EKSN06APD                                       '
MQEncoding   :0x'222' (Reversed)
CCSID        :486
Format       :'MQADMIN '
PutApplType  :6 (UNIX)
PutApplName  :'amqpcsea....................'
Put Date     :'20161024'
Put Time     :'14563668'

The reason code is actually the 3rd set of 4 bytes. Which is '05080000' which, when byte swapped, is '00000805'

Cheers,

Paul.

The DLH structure is documented here http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.dev.doc/q096110_.htm
_________________
There are two types of people in this world:
1) Those that can extrapolate from incomplete data
Back to top
View user's profile Send private message
rekarm01
PostPosted: Tue Oct 25, 2016 3:34 am Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1345

PaulClarke wrote:
Actually I just copied and pasted you message into our new MQEDIT product and it gives me this...
Code:
...
CCSID        :486
...

X'B5010000' = 486?
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Oct 25, 2016 3:49 am Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 5999

rekarm01 wrote:
PaulClarke wrote:
Actually I just copied and pasted you message into our new MQEDIT product and it gives me this...
Code:
...
CCSID        :486
...

X'B5010000' = 486?

The bit you need to be looking at is:
Quote:
444C4820 01000000 05080000 4D514D4F 4E2E6132 69363738 612E3538 30323431 42423244 43424138 33322020 20202020 20202020 20202020 DLH ........MQMON.a2i678a.580241BB2DCBA832

_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.

Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Oct 25, 2016 4:50 am Post subject: Reply with quote

Grand Poobah

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

rekarm01 wrote:
PaulClarke wrote:
Actually I just copied and pasted you message into our new MQEDIT product and it gives me this...
Code:
...
CCSID        :486
...

X'B5010000' = 486?

486 would be 1e6 and is possibly the closest match to the actual value of 437.
437 or 1b5 looks to me more like a ccsid encoding... Did somebody make an assumption and forget to lookup the meaning of the MQ Encoding field?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
PaulClarke
PostPosted: Tue Oct 25, 2016 7:04 am Post subject: Reply with quote

Guardian

Joined: 17 Nov 2005
Posts: 925
Location: New Zealand

Oops, you are quite right. Think I must have got my copy and paste slightly askew. If I try it again I get....
Code:
[  461 bytes] Dead Letter Queue Header (MQDLH)
StrucId      :'DLH '
Version      :1
Reason       :2053 (Queue full.)
Dest. Queue  :'MQMON.a2i678a.580241BB2DCBA832                  '
Dest. QMgr   :'EKSN06APD                                       '
MQEncoding   :0x'222' (Reversed)
CCSID        :437 (IBM PC)
Format       :'MQADMIN '
PutApplType  :6 (UNIX)
PutApplName  :'amqpcsea....................'
Put Date     :'20161024'
Put Time     :'14563668'


Cheers,

Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportMQMON dynamic queues message persistence
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


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.