| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mq listener in iseries |
« View previous topic :: View next topic » |
| Author |
Message
|
| mnollora |
 Posted: Fri Jul 02, 2004 11:51 am Post subject: mq listener in iseries |
 |
|
Newbie
Joined: 02 Jul 2004
Posts: 3
|
Hi,
Please help me  ... I'm new in mqseries and didn't get a formal training. I am having a problem starting a receiver channel. I don't see any error in the joblog. I was informed by the other party that my listener is down. I already started the listener and the job RUNMQLSR is in TIMW status. I was also informed that they can TCP Ping me.....Where do I look for the problem?
Frustrated One,
Ma |
|
| Back to top |
|
 |
| kman |
| Posted: Mon Jul 05, 2004 7:55 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
On iSeries?
Try WRKMQMCMD or something.. that would give you the list of command to use.
After you start the Receiver channel from the menu panel.. or whatever they call it on iSeries (I am not iSeries person.. maybe Charlie can help on this one  ) you need to refresh to see.
However, if they can ping you, that means connection are all working. They can start sending message. And they need to start their SENDER channel. |
|
| Back to top |
|
|
| kman |
| Posted: Tue Jul 06, 2004 4:19 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
If they can PING you that means connection was successful. They can send the probe into your channel, and your channel has responded. So that means all config setting is working fine.
If your partner's channel is in BINDING mode, that is not a problem yet. Look at the Intercommunication document for the various states of active and inactive channel status.
They are still seeing BINDING mode maybe because the machine is too slow. After a few refresh, that would go off. Normally, on development (if this is it), the machines are so slow.. due to some reasons.
If the status does not change to RUNNING after a few moments.. then take a look at the AMQERR01.LOG. That should shed some thing on this on. Normally it's a communication problem. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
