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 Index » Mainframe, CICS, TXSeries » Msgs on default Xmit queue in zOS

Post new topic  Reply to topic
 Msgs on default Xmit queue in zOS « View previous topic :: View next topic » 
Author Message
knock2mq
PostPosted: Sat Jan 16, 2010 3:27 am    Post subject: Msgs on default Xmit queue in zOS Reply with quote

Novice

Joined: 09 Jan 2010
Posts: 17

Hi,
Xmit queue in my zOS queue manager(MyQMgr) is having messages with below properties:

Reply-to-queue = SYSTEM.CSQOREXX.C546FC62812C1785
Reply-to-Queue manager = MyQMgr
Data header= XQH...SYSTEM.COMMAND.INPUT

Q 1. Why they are piling up in default xmit queue ?
Q 2. What should I do to avoid this ?
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat Jan 16, 2010 1:27 pm    Post subject: Re: Msgs on default Xmit queue in zOS Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

knock2mq wrote:
Q 1. Why they are piling up in default xmit queue ?


Find out who's attempting to connect to an inaccessable queue manager from the ISPF panel via the queue manager in question.

knock2mq wrote:
Q 2. What should I do to avoid this ?


Make the queue manager accessable, or stop them.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat Jan 16, 2010 1:28 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Moved to more relevant section
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Jan 16, 2010 5:49 pm    Post subject: Reply with quote

Poobah

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

Quote:
Q 1. Why they are piling up in default xmit queue ?

I'd guess that there is no sender channel using the default xmit queue; and one of your QRenote definitions doesn't resolve to any other xmit queue, and thus the messages end up in in the default xmit queue.

Some choices: 1) if no channel ever uses the default xmit queue, delete the default xmit queue name from the qmgr object attribute. 2) If you're not sure if a channel uses the default xmit queue, put disable it. This will cause the offending application(s) to get a ReasonCode.

I'd pick 1).
_________________
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
View user's profile Send private message
Mr Butcher
PostPosted: Mon Jan 18, 2010 4:52 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

Bruce,

yes, this may be the case during "normal" processing which involves default xmitq.

but, as vitor already pointed out, that SYSTEM.CSQOREXX stuff comes from the ISPF panels. most likely somebody typed in a non existing target queuemanager, or the route from the connect queuemanager to the target queuemanager is not known.

as you pointed out ti looks like there is no sender channel for default xmitq, so i would remove the default xmitq fromt he qmgr object if it is not used. otherwise, also applications can send messages to unknown destinations, no rc will be given to application, it all ends um in the no-channel-default xmitq.
_________________
Regards, Butcher
Back to top
View user's profile Send private message
knock2mq
PostPosted: Mon Jan 18, 2010 6:03 am    Post subject: Reply with quote

Novice

Joined: 09 Jan 2010
Posts: 17

yes, Thank you Mr Vitor and Mr Buther, actually it was a typo error in the traget queue manager field. so message went to default xmit queue.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jan 18, 2010 7:12 am    Post subject: Reply with quote

Poobah

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

Quote:
it was a typo error in the traget queue manager field. so message went to default xmit queue.

XMITQ name is resolved at MQOPEN of QRemote definition in this order:
1. explicit xmitq() in QR definition
2. rqmname() is QR definition
3. default xmit queue (in qmgr object)
4. error- mqopen fails
_________________
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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » Msgs on default Xmit queue in zOS
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.