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 » General IBM MQ Support » Are there any conditions where a qmgr will STOP a SENDER

Post new topic  Reply to topic
 Are there any conditions where a qmgr will STOP a SENDER « View previous topic :: View next topic » 
Author Message
javagate
PostPosted: Fri Mar 31, 2006 3:58 am    Post subject: Are there any conditions where a qmgr will STOP a SENDER Reply with quote

Disciple

Joined: 15 Nov 2004
Posts: 159

Are there any conditions where a qmgr will STOP a SENDER on its own? I am trying to find out why some channels keep getting stopped.
The qmgr is on z/os.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab.
Back to top
View user's profile Send private message
wschutz
PostPosted: Fri Mar 31, 2006 4:09 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

One that comes to mind is the case where a message can't be delivered and there is no DLQ. Is there anything in the CHIN log?
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
javagate
PostPosted: Fri Mar 31, 2006 4:13 am    Post subject: Reply with quote

Disciple

Joined: 15 Nov 2004
Posts: 159

I checked the CHIN and nothing jumped out at me. The ADMIN.CHANNEL.EVENT log is empty since we have a monitor. I seam to remember that a Sender can get stopped under certain conditions.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 31, 2006 4:27 am    Post subject: Reply with quote

Grand High Poobah

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

javagate wrote:
I checked the CHIN and nothing jumped out at me. The ADMIN.CHANNEL.EVENT log is empty since we have a monitor. I seam to remember that a Sender can get stopped under certain conditions.

Well on a seqnum mismatch but you should see something in the logs.
Same if the msg size is bigger than the channel's max msgsize. (Yes I've seen it happen: chnl size set lower than default with the xmitq at default...)

How about target queue full and no DLQ ?

Least and not last after a hard disconnect (network) it is sometimes necessary to stop and restart the channel at both ends between the MF and distributed systems. This is just one more reason to have triggered channels as the occurrence of having to do a hard stop/restart is much much lower on triggered channels than the ones always open.


_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
javagate
PostPosted: Fri Mar 31, 2006 5:52 am    Post subject: Reply with quote

Disciple

Joined: 15 Nov 2004
Posts: 159

according to IBM

For a channel to change to a Stopped state there must be one of the
following;
- STOP command,
- non-retryable error
- retry limit reached

now I know.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 31, 2006 3:29 pm    Post subject: Reply with quote

Grand High Poobah

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

Sorry I understood stopped as not working...
not necessarily in stopped status...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
csmith28
PostPosted: Fri Mar 31, 2006 5:26 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

Well if DISCINT is set to anything other than (0) yes. The MQManager will in a manner of speaking issue a "stop chl(CHANNEL) status(inactive)" if no message arrives on the TRIGGER'ed XMITQ within the defined DISCINT interval.

The status of the Channel will not be STOPPED it will be inactive so if you issue a "dis chs(CHANNEL), it will echo "Status not found" or something similar.

If DISCINT is set to (0) then the MQManager will keep the Channel up as long as there are no problems.

If there are problems the SDR Channel will AMQ9999 End abnormally and the MQManager will continue to try to re-start the SDR Channel as defined by the value of SHORTTMR and then LONGTMR. During this time the SDR Channel will be in a RETRY status.

If the MQManager can not re-establish the connection using those thresholds it will issue a stop chl placing the SDR Channel in a status of STOPPED.

This is how I believe it works. If I am wrong anyone who knows better should feel free to correct me.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
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 » General IBM MQ Support » Are there any conditions where a qmgr will STOP a SENDER
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.