| Author |
Message
|
| stornq01 |
 Posted: Fri Mar 23, 2007 8:22 am Post subject: can't get sender channel to connect SUN to MVS |
 |
|
Newbie
Joined: 22 Mar 2007
Posts: 7
|
I've recently taken an existing queue manager on and AIX box and created the same queue mananger on a SUN box. I've changed the connection name on the MVS sender channels to point to the new sun queue manager. The going from the MVS system to the SUN box the connection seems to work. But I am unable to get the connection to work going from the new SUN channels to the MVS channels. Do I need to have the MVS channels reset? Is it possible that the sequence could be out of sync? The error messages don't seem to indicate this. Here is the error message:
----- amqrccca.c : 777 --------------------------------------------------------
03/23/07 09:15:13 - Process(24237.1) User(mqm) Program(runmqchl_nd)
AMQ9002: Channel 'QWT1.BCBSAZTJ.SOAMTV' is starting.
EXPLANATION:
Channel 'QWT1.BCBSAZTJ.SOAMTV' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
03/23/07 09:15:13 - Process(24237.1) User(mqm) Program(runmqchl_nd)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'QWT1.BCBSAZTJ.SOAMTV'.
Some operations are only valid for certain channel types. For example, you can
only ping a channel from the end sending the message.
ACTION:
Check whether the channel name is specified correctly. If it is check that the
channel has been defined correctly.
----- amqrccca.c : 375 --------------------------------------------------------
03/23/07 09:15:13 - Process(24237.1) User(mqm) Program(runmqchl_nd)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'QWT1.BCBSAZTJ.SOAMTV' ended abnormally.
ACTION:
Look at previous error messages for channel program 'QWT1.BCBSAZTJ.SOAMTV' in
the error files to determine the cause of the failure.
"AMQERR01.LOG" 210 lines, 9422 characters
Obviously I'm a little new to this. Any suggestions?
Thanks |
|
| Back to top |
|
 |
| Couple-IT |
| Posted: Fri Mar 23, 2007 8:32 am Post subject: |
|
|
Novice
Joined: 06 Apr 2006
Posts: 11
|
What Channel Type is Channel 'QWT1.BCBSAZTJ.SOAMTV' ???
Please post the output from your Display Channel... |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Sat Mar 24, 2007 4:25 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Channel reset is not neccessary (yet, unless you get a "sequence error" message in the log).
Did you PING a receiver, requester or server connection channel?
_________________
Regards
Hubert |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Mar 24, 2007 11:55 am Post subject: |
|
|
Guest
|
Channel types must be a valid pair: sender-receiver, server-requester, etc.. Take a look at the MQ V6 Intercommunications manual.
To validate channels:
1. use the tcpip ping (from both channel ends): ifconfig -a (or something like it on SunOS), ipconfig on Windows. If you can successfully tcpip ping, continue.
2. from the Sender end of a non-started MQ channel, issue the MQ ping command (from within runmqsc). If this succeeds, your channel definitions are compatible. if successful, continue.
3. from the Sender end of the channel, issue the START CHL command from runmqsc (or runmqchl control command).
As stated elsewhere in this post, refer to the errors folder(s) in the MQ path to identify the detected error. I usually start at the top (in the IBM WebSphere MQ folder, then next try the errors folder with your qmgr name in folder Qmgrs. Look for errors logged at both ends of the channel.
Provide some details here:
-channel definitions
-exact commands you issued
-errors logged |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 25, 2007 5:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
And to verify tcp with a firewall try
telnet <receiver host> <mqlsr port on receiver>
ctrl + ]
quit/bye
It should tell you whether a tcp/ip connection to the receiving qmgr is even possible or if it gets blocked by the firewall. Don't worry about the FDC being cut, this is just because you accessed the port with a non MQ protocol.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Mon Mar 26, 2007 3:10 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| bruce2359 wrote: |
... To validate channels:
1. use the tcpip ping (from both channel ends): ifconfig -a (or something like it on SunOS), ipconfig on Windows. If you can successfully tcpip ping, continue...
|
An working IP ping is not required, to open MQ channels. It is possible (and often configured in firewalls) that IP ping (ICMP packets) are filtered by the firewall. So you may not be able, to use IP ping on a working MQ channel connection.
Instead, use telnet on the MQ port as fjb_saper described.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Mar 27, 2007 6:25 am Post subject: |
|
|
Guest
|
"Instead, use telnet..." Good point, unless telnet has been disabled, too.
I was suggesting that sender and receiver must be able to 'see' each other somehow across the network for a chanel to work. Ping or telnet, or any other method of validation will be fine. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Mar 27, 2007 6:47 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| emiranda |
| Posted: Tue Mar 27, 2007 7:10 am Post subject: |
|
|
Disciple
Joined: 21 Nov 2002
Posts: 196
Location: Dublin, Ireland
|
| Michael Dag wrote: |
looks like stornq01 hasn't returned  |
Yeah... but we keep posting, because we like it!! 
Also, stornq01, if you still there and have a problem yet, send us the "DIS CHL" output for both ends of 'QWT1.BCBSAZTJ.SOAMTV' channel (sender/receiver, server/requester) otherwise we will run out of ideas to try to help you. 
_________________
Warm Regards,
EM |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Mar 27, 2007 10:34 pm Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| bruce2359 wrote: |
"Instead, use telnet..." Good point, unless telnet has been disabled, too.
I was suggesting that sender and receiver must be able to 'see' each other somehow across the network for a chanel to work. Ping or telnet, or any other method of validation will be fine. |
I meant: Use telnet with the port of the MQ listener. This is an ultimative test, to check, if the port is opened .
| Code: |
| telnet <lsnr_IP> <lsnr_port> |
The trick is, that the command above trys to connect to the listener and gets a connection  . After a while, the listener realizes, that the responder is not a WMQ channel and closes the connection.
Invalid port (Unix output)  :
| Code: |
# telnet localhost 1415
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused |
Valid port (Unix output)  :
| Code: |
# telnet localhost 1414
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
|
You will get some error message in the file /var/mqm/qmgrs/<your_qmgr>/errors/AMQERR01.LOG (and this may be monitored on productive systems and so may lead to an alert  !):
| Code: |
-------------------------------------------------------------------------------
03/28/07 08:16:56
AMQ9207: The data received from host 'localhost (127.0.0.1)' is not valid.
EXPLANATION:
Incorrect data format received from host 'localhost (127.0.0.1)' over TCP/IP.
It may be that an unknown host is attempting to send data. An FFST file has
been generated containing the invalid data received.
ACTION:
Tell the systems administrator.
----- amqccita.c : 2848 -------------------------------------------------------
03/28/07 08:16:56
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0.
|
If this telnet test does not get a connection, then the specified <lsnr_IP> <lsnr_port> combination cannot be addressed, neither by telnet nor by WMQ listeners  .
_________________
Regards
Hubert |
|
| Back to top |
|
|
| stornq01 |
| Posted: Fri Mar 30, 2007 2:42 pm Post subject: |
|
|
Newbie
Joined: 22 Mar 2007
Posts: 7
|
| Thank you all for your help. I the telnet test did the trick. It was actually a firewall issue. The connection is working fine now. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat Mar 31, 2007 2:10 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| stornq01 wrote: |
| the telnet test did the trick. |
it usually does
| stornq01 wrote: |
| It was actually a firewall issue. |
it usually is
| stornq01 wrote: |
| The connection is working fine now. |
great 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Sat Mar 31, 2007 5:32 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| Michael Dag wrote: |
| stornq01 wrote: |
| the telnet test did the trick. |
it usually does
| stornq01 wrote: |
| It was actually a firewall issue. |
it usually is
| stornq01 wrote: |
| The connection is working fine now. |
great |
... absolutely right - but don't tell the networkers  .
_________________
Regards
Hubert |
|
| Back to top |
|
|
| sjunejo |
| Posted: Thu Sep 18, 2008 7:44 am Post subject: URGENT PLZ.... |
|
|
Novice
Joined: 12 Sep 2008
Posts: 16
|
I have got similar problem.... error is as below...
On Server
hml-bladep6a1-~/mq: runmqchl -c QMGR1.TO.QMGR2
18/09/08 16:38:11 Channel 'QMGR1.TO.QMGR2' is starting.
18/09/08 16:38:11 AMQ9502: Type of channel not suitable for action requested.
18/09/08 16:38:11 AMQ9999: Channel program ended abnormally.
On Client
hml-bladep6a1-~/mq: runmqchl -c QMGR2.TO.QMGR1 -m QMGR2
18/09/08 16:39:26 Channel 'QMGR2.TO.QMGR1' is starting.
18/09/08 16:39:26 AMQ9519: Channel 'QMGR2.TO.QMGR1' not found.
18/09/08 16:39:26 AMQ9999: Channel program ended abnormally.
Remember I am using same machine this all locally no remote thing is here it should be easy. I am suing my IP address in channel def NOT 127.0.0.1....I have tested with telnet trick and its perfectly working.... I dont know what seems to be the problem here... My listners are running on two sessions of my machine. I have opened another two sessions and trying these commands....
PLZ help  |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Sep 18, 2008 7:49 am Post subject: Re: URGENT PLZ.... |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| sjunejo wrote: |
I have got similar problem.... error is as below...
On Server
hml-bladep6a1-~/mq: runmqchl -c QMGR1.TO.QMGR2
18/09/08 16:38:11 Channel 'QMGR1.TO.QMGR2' is starting.
18/09/08 16:38:11 AMQ9502: Type of channel not suitable for action requested.
18/09/08 16:38:11 AMQ9999: Channel program ended abnormally.
On Client
hml-bladep6a1-~/mq: runmqchl -c QMGR2.TO.QMGR1 -m QMGR2
18/09/08 16:39:26 Channel 'QMGR2.TO.QMGR1' is starting.
18/09/08 16:39:26 AMQ9519: Channel 'QMGR2.TO.QMGR1' not found.
18/09/08 16:39:26 AMQ9999: Channel program ended abnormally.
Remember I am using same machine this all locally no remote thing is here it should be easy. I am suing my IP address in channel def NOT 127.0.0.1....I have tested with telnet trick and its perfectly working.... I dont know what seems to be the problem here... My listners are running on two sessions of my machine. I have opened another two sessions and trying these commands....
PLZ help |
What are the channel types? Can you paste the definitions here?
Also, what do you mean by "On Server" and "On Client"?
And lastly, this is an obvious issue: "Channel 'QMGR2.TO.QMGR1' not found." |
|
| Back to top |
|
|
|
|
