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 » urgent - how to keep channel always alive -MQ VSE/ESA

Post new topic  Reply to topic
 urgent - how to keep channel always alive -MQ VSE/ESA « View previous topic :: View next topic » 
Author Message
tanbsj
PostPosted: Wed Jun 23, 2004 5:47 pm    Post subject: urgent - how to keep channel always alive -MQ VSE/ESA Reply with quote

Novice

Joined: 08 Jun 2003
Posts: 16

We have setup a sending channel that are connected to another
MQ under tandem.

The sending channel will shutdown after all messages are send out and
the queue is empty. See below the system.log
MQI005005I PRG:MQPSEND TRN:MQ02 TRM:.... TSK:23022 06/18/2004 17:48:53
CHANNEL QUEUE EMPTY

MQI005008I PRG:MQPSEND TRN:MQ02 TRM:.... TSK:23022 06/18/2004 17:48:53
CHANNEL SHUTDOWN

MQI005006I PRG:MQPSEND TRN:MQ02 TRM:.... TSK:23022 06/18/2004 17:48:53
CHANNEL QUEUE CLOSED

MQI005007I PRG:MQPSEND TRN:MQ02 TRM:.... TSK:23022 06/18/2004 17:48:53
CHANNEL DISCONNECTED

However, when there is message put to the queue, the channel will
automatic started. Is this the normal way MQ in VSE/ESA behave?

But is there a way that We can keep the channel alway in started status
even when the queue is empty.
Please advise.

Thank you in advance.
Back to top
View user's profile Send private message Send e-mail
kevinf2349
PostPosted: Thu Jun 24, 2004 5:00 am    Post subject: Reply with quote

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

A disconnect interval of 0 will keep a channel alive.....but it sounds like you have a triggered channel so I really don't see what the problem is. Unless of course you can't take the extra delay while triggering starts the channel.

There have been a few threads discussing the in and outs of triggered channels v.s channels being 'kept alive'....do a search on DISCINT. My own view is that triggered channels are easier to keep operational and are more secure, but a little slower on initial startup. Of course you could always issue a start command ahead of the application starting up.
Back to top
View user's profile Send private message
PGoodhart
PostPosted: Thu Jun 24, 2004 9:47 am    Post subject: Reply with quote

Master

Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA

I think you are missing the point. If your MQ channels and transmit queues are properly set up the channels will go between running and inactive and back to running without your intervention. The channels don't need to be running to be ready for a message. The thing that I have seen is if you fail to specify the initation queue (INITQ) on the transmission queues, then the channels won't restart automatically. You can use the SYSTEM.CHANNEL.INITQ that should already exist.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin
Back to top
View user's profile Send private message
any2xml
PostPosted: Tue Jul 06, 2004 5:23 pm    Post subject: Send channel dropping out - Linux on mainframe Reply with quote

Apprentice

Joined: 18 May 2004
Posts: 42

I have the same problem. I am not able to work out how the initiation queue affects the send channel. However I do have a SYSTEM.CHANNEL.INITQ

Should the channel reference it?

The definition is:
Code:

AMQ8409: Display Queue details.
   DESCR(WebSphere MQ Channel Initiation Queue)
   PROCESS( )                              BOQNAME( )
   INITQ( )                                TRIGDATA( )
   CLUSTER( )                              CLUSNL( )
   QUEUE(SYSTEM.CHANNEL.INITQ)             CRDATE(2004-04-29)
   CRTIME(07.58.18)                        ALTDATE(2004-06-17)
   ALTTIME(22.08.03)                       GET(ENABLED)
   PUT(ENABLED)                            DEFPRTY(0)
   DEFPSIST(NO)                            MAXDEPTH(1000)
   MAXMSGL(2000)                           BOTHRESH(0)
   NOSHARE                                 DEFSOPT(EXCL)
   HARDENBO                                MSGDLVSQ(PRIORITY)
   RETINTVL(999999999)                     USAGE(NORMAL)
   NOTRIGGER                               TRIGTYPE(NONE)
   TRIGDPTH(1)                             TRIGMPRI(0)
   QDEPTHHI(80)                            QDEPTHLO(20)
   QDPMAXEV(ENABLED)                       QDPHIEV(DISABLED)
   QDPLOEV(DISABLED)                       QSVCINT(999999999)
   QSVCIEV(NONE)                           DISTL(NO)
   DEFTYPE(PREDEFINED)                     TYPE(QLOCAL)
   SCOPE(QMGR)                             DEFBIND(OPEN)
   IPPROCS(1)                              OPPROCS(0)
   CURDEPTH(0)


The channel looks like this:
Code:
   
CHANNEL(BAXT.USCS_MQB1)                 CHLTYPE(SDR)
   TRPTYPE(TCP)                            DESCR( )
   XMITQ(BAXT.USCS.XMITQ)                  MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(6000)
   SHORTRTY(10)                            SHORTTMR(60)
   LONGRTY(999999999)                      LONGTMR(1200)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        CONVERT(NO)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(167.144.89.135(1414))           HBINT(300)
   BATCHINT(0)                             NPMSPEED(FAST)
   SSLCIPH( )                              BATCHHB(0)
   LOCLADDR( )                             KAINT(AUTO)
   MCAUSER( )                              ALTDATE(2004-06-09)
   ALTTIME(11.21.34)                       SSLPEER()
   MSGEXIT( )
   SENDEXIT( )
   RCVEXIT( )
   MSGDATA( )
   SENDDATA( )
   RCVDATA( )



Notice that the DISCINT is set to 6000. The ALTER command would not let me change it!
_________________
A Perl Hacker
http://www.goreliance.com
http://www.any2xml.com
Back to top
View user's profile Send private message
any2xml
PostPosted: Sat Jul 10, 2004 9:56 pm    Post subject: ALTER worked .. but strange Reply with quote

Apprentice

Joined: 18 May 2004
Posts: 42

I had to say

ALTER CHANNEL (X) CHLTYPE(SDR) DISCINT(0)

Should MQSC not know that the channel X is already defined as type SDR? Why would I need to specify it?
_________________
A Perl Hacker
http://www.goreliance.com
http://www.any2xml.com
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Jul 11, 2004 5:00 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

CHLTYPE is simply a required parameter to ALTER CHANNEL.

Likely, this is because you are allowed to have more than one channel with the same name - as long as they are different channel types!

For instance, one might want to have a receiver channel named after the queue manager AND a cluster receiver named after the queue manager on a cluster gateway queue manager.

I wouldn't do it that way myself, but it's allowable.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Jul 11, 2004 6:09 am    Post subject: Reply with quote

Grand High Poobah

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

any2xml

You can reset your channel to a discint of 6000 but
you will need at the same time to issue:

Code:
alter ql(BAXT.USCS.XMITQ) initq(system.channel.initq) +
trigger trigtype(first) trigdepth(1)


The assumption is you are on WMQ 5.3 version....

Setting the channel initq on the transmition queue and setting the queue to triggered will allow the channel to automatically restart when traffic resumes on the queue.

at the same time you should have defined an alias for your transmit queue:
Code:
def qalias(uscs)
with as a base queue your transmission queue(BAXT.USCS.XMITQ). This should allow the qmgr (baxt ?) to find a default communication channel to USCS.

Enjoy
F.J.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » urgent - how to keep channel always alive -MQ VSE/ESA
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.