IC SunsetThe developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this community and its apps will no longer be available. More details available on our FAQ.
Topic
  • 14 replies
  • Latest Post - ‏2019-02-04T11:36:36Z by 6X6D_ossama_rashad
SystemAdmin
SystemAdmin
8523 Posts

Pinned topic MQ 5.3 sender channel becomes inactive and has to be manually started

‏2004-07-07T05:10:03Z |
I am using MQ 5.3 .My sender channel becomes inactive once there no messages for the time specified , the disconnect time interval that i have specified is 6000 seconds . After this time interval expires , the channel becomes inactive ,then after that the channels have to be started manually .But then the channels should be active automatically once there are messages , but this doesn't happen .Please advice
Updated on 2004-07-16T07:49:30Z at 2004-07-16T07:49:30Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-08T12:56:16Z  
    Check that xmitq related to this channel has been defined with triggering ... regards ... Ruud
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T04:14:33Z  
    Check that xmitq related to this channel has been defined with triggering ... regards ... Ruud
    The triggering for the transmit queue is enabled and the triggering type is First .
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T06:51:46Z  
    The triggering for the transmit queue is enabled and the triggering type is First .
    okidoki - so if there are msgs in the xmitq, and the chl isn't starting, check the mq error logs. Also check the target system ensuring the rcvr chl is ok and the listener is started.
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T07:15:41Z  
    okidoki - so if there are msgs in the xmitq, and the chl isn't starting, check the mq error logs. Also check the target system ensuring the rcvr chl is ok and the listener is started.
    > okidoki - so if there are msgs in the xmitq, and the
    > chl isn't starting, check the mq error logs. Also
    well the target system listener is started.
    As per the mqerror logs it states that the channel is stopped after the disconnect time interval expired
    .Presently the disconnect time interval for the Channel is set to 6000 seconds
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T07:16:57Z  
    okidoki - so if there are msgs in the xmitq, and the chl isn't starting, check the mq error logs. Also check the target system ensuring the rcvr chl is ok and the listener is started.

    well the target system listener is started.
    As per the mqerror logs it states that the channel is stopped after the disconnect time interval expired
    .Presently the disconnect time interval for the Channel is set to 6000 seconds
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T08:01:58Z  

    well the target system listener is started.
    As per the mqerror logs it states that the channel is stopped after the disconnect time interval expired
    .Presently the disconnect time interval for the Channel is set to 6000 seconds
    ok, the only thing left (I can think of) is that the triggering hasn't been set up quite correctly.
    Can you pls paste the xmitq def here?
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T08:41:50Z  
    ok, the only thing left (I can think of) is that the triggering hasn't been set up quite correctly.
    Can you pls paste the xmitq def here?
    DEFINE QLOCAL('Transmit_1) +
    DESCR('Transmit_Queue_to_GCX') +
    SHARE +
    TRIGMPRI(0) +
    TRIGDPTH(1) +
    TRIGTYPE(FIRST) +
    TRIGDATA(' ') +
    BOQNAME(' ') +
    PROCESS('Process_1') +
    DEFPRTY(0) +
    MAXMSGL(4194304) +
    BOTHRESH(0) +
    MAXDEPTH(5000) +
    TRIGGER +
    DEFSOPT(SHARED) +
    NOHARDENBO +
    MSGDLVSQ(PRIORITY) +
    PUT(ENABLED) +
    GET(ENABLED) +
    DEFPSIST(YES) +
    USAGE(XMITQ) +
    SCOPE(QMGR) +
    RETINTVL(999999999) +
    QDEPTHLO(20) +
    QDEPTHHI(80) +
    QSVCINT(999999999) +
    QSVCIEV(NONE) +
    QDPMAXEV(ENABLED) +
    INITQ('CHANNEL.INITQ') +
    QDPHIEV(ENABLED) +
    QDPLOEV(DISABLED) +
    CLUSTER(' ') +
    CLUSNL(' ') +
    DEFBIND(OPEN) +
    STGCLASS(' ') +
    REPLACE
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T09:13:10Z  
    DEFINE QLOCAL('Transmit_1) +
    DESCR('Transmit_Queue_to_GCX') +
    SHARE +
    TRIGMPRI(0) +
    TRIGDPTH(1) +
    TRIGTYPE(FIRST) +
    TRIGDATA(' ') +
    BOQNAME(' ') +
    PROCESS('Process_1') +
    DEFPRTY(0) +
    MAXMSGL(4194304) +
    BOTHRESH(0) +
    MAXDEPTH(5000) +
    TRIGGER +
    DEFSOPT(SHARED) +
    NOHARDENBO +
    MSGDLVSQ(PRIORITY) +
    PUT(ENABLED) +
    GET(ENABLED) +
    DEFPSIST(YES) +
    USAGE(XMITQ) +
    SCOPE(QMGR) +
    RETINTVL(999999999) +
    QDEPTHLO(20) +
    QDEPTHHI(80) +
    QSVCINT(999999999) +
    QSVCIEV(NONE) +
    QDPMAXEV(ENABLED) +
    INITQ('CHANNEL.INITQ') +
    QDPHIEV(ENABLED) +
    QDPLOEV(DISABLED) +
    CLUSTER(' ') +
    CLUSNL(' ') +
    DEFBIND(OPEN) +
    STGCLASS(' ') +
    REPLACE
    I see. You're using what I would call the 'old-fashioned' method of using a 'process'. Funnily enough, we resolved a problem at our site where they were using a process and the process had been incorrectly defined. I would recommend you remove that process and use the 'trigger data' field which should be set to the name of the channel to be started. Here's an example:

    QUEUE(YOUR.XMIT.QUEUE)
    TYPE(QLOCAL)
    INITQ(SYSTEM.CHANNEL.INITQ)
    USAGE(XMITQ)
    TRIGTYPE(FIRST)
    TRIGDATA(YOUR.CHANNEL.NAME.HERE)
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-09T10:05:55Z  
    I see. You're using what I would call the 'old-fashioned' method of using a 'process'. Funnily enough, we resolved a problem at our site where they were using a process and the process had been incorrectly defined. I would recommend you remove that process and use the 'trigger data' field which should be set to the name of the channel to be started. Here's an example:

    QUEUE(YOUR.XMIT.QUEUE)
    TYPE(QLOCAL)
    INITQ(SYSTEM.CHANNEL.INITQ)
    USAGE(XMITQ)
    TRIGTYPE(FIRST)
    TRIGDATA(YOUR.CHANNEL.NAME.HERE)
    Thanks buddy i would implement this change on my system and observe the changes
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-13T04:06:39Z  
    I see. You're using what I would call the 'old-fashioned' method of using a 'process'. Funnily enough, we resolved a problem at our site where they were using a process and the process had been incorrectly defined. I would recommend you remove that process and use the 'trigger data' field which should be set to the name of the channel to be started. Here's an example:

    QUEUE(YOUR.XMIT.QUEUE)
    TYPE(QLOCAL)
    INITQ(SYSTEM.CHANNEL.INITQ)
    USAGE(XMITQ)
    TRIGTYPE(FIRST)
    TRIGDATA(YOUR.CHANNEL.NAME.HERE)
    below i have stated the definition of my transmit queue after incorporating the change as mentioned by u .But even after doning this still my sender channel has to be manually started , even though there are messages in my transmit queue .

    DEFINE QLOCAL('Transmit_1') +
    DESCR('Transmit_Queue') +
    SHARE +
    TRIGMPRI(0) +
    TRIGDPTH(1) +
    TRIGTYPE(FIRST) +
    TRIGDATA('Senderchannel_1') +
    BOQNAME(' ') +
    PROCESS('Process1') +
    DEFPRTY(0) +
    MAXMSGL(4194304) +
    BOTHRESH(0) +
    MAXDEPTH(5000) +
    TRIGGER +
    DEFSOPT(SHARED) +
    NOHARDENBO +
    MSGDLVSQ(PRIORITY) +
    PUT(ENABLED) +
    GET(ENABLED) +
    DEFPSIST(YES) +
    USAGE(XMITQ) +
    SCOPE(QMGR) +
    RETINTVL(999999999) +
    QDEPTHLO(20) +
    QDEPTHHI(80) +
    QSVCINT(999999999) +
    QSVCIEV(NONE) +
    QDPMAXEV(ENABLED) +
    INITQ('CHANNEL.INITQ') +
    QDPHIEV(ENABLED) +
    QDPLOEV(DISABLED) +
    CLUSTER(' ') +
    CLUSNL(' ') +
    DEFBIND(OPEN) +
    STGCLASS(' ') +
    REPLACE

  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-13T12:41:39Z  
    I see. You're using what I would call the 'old-fashioned' method of using a 'process'. Funnily enough, we resolved a problem at our site where they were using a process and the process had been incorrectly defined. I would recommend you remove that process and use the 'trigger data' field which should be set to the name of the channel to be started. Here's an example:

    QUEUE(YOUR.XMIT.QUEUE)
    TYPE(QLOCAL)
    INITQ(SYSTEM.CHANNEL.INITQ)
    USAGE(XMITQ)
    TRIGTYPE(FIRST)
    TRIGDATA(YOUR.CHANNEL.NAME.HERE)
    below i have stated the definition of my transmit queue after incorporating the change as mentioned by u .But even after doning this still my sender channel has to be manually started , even though there are messages in my transmit queue .

    DEFINE QLOCAL('Transmit_1') +
    DESCR('Transmit_Queue') +
    SHARE +
    TRIGMPRI(0) +
    TRIGDPTH(1) +
    TRIGTYPE(FIRST) +
    TRIGDATA('Senderchannel_1') +
    BOQNAME(' ') +
    PROCESS('Process1') +
    DEFPRTY(0) +
    MAXMSGL(4194304) +
    BOTHRESH(0) +
    MAXDEPTH(5000) +
    TRIGGER +
    DEFSOPT(SHARED) +
    NOHARDENBO +
    MSGDLVSQ(PRIORITY) +
    PUT(ENABLED) +
    GET(ENABLED) +
    DEFPSIST(YES) +
    USAGE(XMITQ) +
    SCOPE(QMGR) +
    RETINTVL(999999999) +
    QDEPTHLO(20) +
    QDEPTHHI(80) +
    QSVCINT(999999999) +
    QSVCIEV(NONE) +
    QDPMAXEV(ENABLED) +
    INITQ('CHANNEL.INITQ') +
    QDPHIEV(ENABLED) +
    QDPLOEV(DISABLED) +
    CLUSTER(' ') +
    CLUSNL(' ') +
    DEFBIND(OPEN) +
    STGCLASS(' ') +
    REPLACE
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-14T08:26:29Z  
    below i have stated the definition of my transmit queue after incorporating the change as mentioned by u .But even after doning this still my sender channel has to be manually started , even though there are messages in my transmit queue .

    DEFINE QLOCAL('Transmit_1') +
    DESCR('Transmit_Queue') +
    SHARE +
    TRIGMPRI(0) +
    TRIGDPTH(1) +
    TRIGTYPE(FIRST) +
    TRIGDATA('Senderchannel_1') +
    BOQNAME(' ') +
    PROCESS('Process1') +
    DEFPRTY(0) +
    MAXMSGL(4194304) +
    BOTHRESH(0) +
    MAXDEPTH(5000) +
    TRIGGER +
    DEFSOPT(SHARED) +
    NOHARDENBO +
    MSGDLVSQ(PRIORITY) +
    PUT(ENABLED) +
    GET(ENABLED) +
    DEFPSIST(YES) +
    USAGE(XMITQ) +
    SCOPE(QMGR) +
    RETINTVL(999999999) +
    QDEPTHLO(20) +
    QDEPTHHI(80) +
    QSVCINT(999999999) +
    QSVCIEV(NONE) +
    QDPMAXEV(ENABLED) +
    INITQ('CHANNEL.INITQ') +
    QDPHIEV(ENABLED) +
    QDPLOEV(DISABLED) +
    CLUSTER(' ') +
    CLUSNL(' ') +
    DEFBIND(OPEN) +
    STGCLASS(' ') +
    REPLACE
    You're still using a 'process'!

    See 'PROCESS('Process1') +' - remove that and try again.
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2004-07-16T07:49:30Z  
    Hi sir,
    i am also using IBM MQ5.3, but i don't know how to configure server file and how to create administrator objects...i want to using JMS with IBM MQ...can u send u'e server JMSADmin.config file and using any sample client file sir..plz help me sir..alreadi i am taken lot of time to solve this problem sir...
    my mail id : manbu_selvam@yahoo.co.in
    thanku,
    regards,
    anbuselvam
  • 6X6D_ossama_rashad
    6X6D_ossama_rashad
    2 Posts

    Re: MQ 5.3 sender channel becomes inactive and has to be manually started

    ‏2019-02-04T11:36:36Z  

    Hi ALl,

     

    I have the same issue "ender channel becomes inactive and has to be manually started " and hereunder my XMITQ definition

     

    DEFINE QLOCAL('TQ_T24_IN') +
       DESCR('Transmit queue to T24 sender channel') +
       INITQ('SYSTEM.CHANNEL.INITQ') +
       MAXDEPTH(50000) +
       TRIGGER +
       TRIGDATA('T24_TO_GTWY') +
       USAGE(XMITQ) +
       REPLACE