A channel problem
Hi, we are having a channel problem. It probably is something simple we are overlooking since nothing special is being done. The is an HP-UX system running MQSeries v5.1 sending to an OS/390 running WebSphere MQ v5.3. There are no channel exits and the firewalls have been opened. Here is the sender channel definition 20 : display channel (JESTER./QUQ5) all AMQ8414: Display Channel details. CHANNEL(JESTER./QUQ5) CHLTYPE(SDR) TRPTYPE(TCP)DESCR( ) XMITQ(QUQ5) MCANAME( ) MODENAME( ) TPNAME( ) BATCHSZ(50) DISCINT(6000) SHORTRTY(10)SHORTTMR(60) LONGRTY(9) LONGTMR(1200) SCYEXIT( ) SEQWRAP(9) MAXMSGL(4194304)CONVERT(NO) SCYDATA( ) USERID( ) PASSWORD( ) MCATYPE(PROCESS) CONNAME(xxx(1418)) HBINT(300) BATCHINT(0) NPMSPEED(FAST) MCAUSER( ) ALTDATE(2003-08-12) ALTTIME(12.29.19) MSGEXIT( ) SENDEXIT( ) RCVEXIT( ) MSGDATA( ) SENDDATA( ) RCVDATA( ) I attempt to execute a PING CHANNEL and I get the following: 18 : ping channel (JESTER./QUQ5) AMQ9209: Connection to host 'muqz (xxx)' closed. The channel goes into retry and the error in /var/mqm/qmgrs/*DEV36AF/errors/*1.LOG --- 08/12/03 12:41:48 AMQ9002: Channel program started. EXPLANATION: Channel program 'JESTER./QUQ5' started. ACTION: None. --- 08/12/03 12:47:49 AMQ9209: Connection to host 'muqz (xxx)' closed. EXPLANATION: An error occurred receiving data from 'muqz (xxx)' over TCP/IP. The connection to the remote host has unexpectedly terminated. ACTION: Tell the systems administrator. --- 08/12/03 12:47:49 AMQ: Channel program ended abnormally. EXPLANATION: Channel program 'JESTER./QUQ5' ended abnormally. ACTION: Look at previous error messages for channel program 'JESTER./QUQ5' in the error files to determine the cause of the failure. --- I checked all other error logs and there are no additonal errors. I dont have direct access to the OS/390 system and must go through a couple of people to get information. The channel (JESTER./QUQ1) still works, the only difference besides the name if the port is 1414. The dns name is the same for both channels. If anyone has any ideas, please let me know. Jeff Tressler Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: A channel problem
>I checked all other error logs and there are no additonal errors. I dont >have direct access to the OS/390 system and must go through a couple of >people to get information. >The channel (JESTER./QUQ1) still works, the only difference besides the >name if the port is 1414. The dns name is the same for both channels. >If anyone has any ideas, please let me know. >Jeff Tressler Jeff, Error message ... AMQ9209: Connection to host 'muqz (xxx)' closed. means that the 'other side' has closed your connection so you really need to look at the OS/390 end to find out why. On this side of the fence all we know is that someone closed the socket we were using so there's no extra information we can give in the HP error logs. The most common reason for something like this is that you've misconfigured the hostname and port and you've connected to something but it isn't being used by WMQ. I would double check that you really do have a listener started on z/OS listening on 1418. If you do then there should be some form of message in the WMQ console on 390 telling you why the connection was dropped. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
