| Author |
Message
|
| ignasi |
 Posted: Mon Jan 08, 2007 1:23 am Post subject: Connecting Windows QM V6 to HP-UX QM V5.3 |
 |
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
Hi all:
I'm trying to connect a Websphere MQ Queue Manager version 6.0.2.0 running on windows to a queue manager V5.3 CSD13 running on HP-UX but a channel connection problem ever grows up.
ERROR LOG CONNECTING FROM MQEXPLORER:
----- amqrccca.c : 777 --------------------------------------------------------
08/01/2007 09:32:23 - Process(3340.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9002: El canal 'ESBRKD01V6.ESISUD00' se está iniciando.
EXPLICACIÓN:
El canal 'ESBRKD01V6.ESISUD00' se está iniciando.
ACCIÓN:
Ninguno.
-------------------------------------------------------------------------------
08/01/2007 09:32:26 - Process(3340.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9209: Conexión al sistema principal '' cerrada.
EXPLICACIÓN:
Se ha producido un error al recibir datos de '' a través de 'TCP/IP'. La
conexión con el sistema principal remoto ha finalizado inesperadamente.
ACCIÓN:
Póngase en contacto con el administrador del sistema.
----- amqccita.c : 3094 -------------------------------------------------------
08/01/2007 09:32:26 - Process(3340.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9999: El programa de canal ha terminado anormalmente.
EXPLICACIÓN:
El programa de canal 'ESBRKD01V6.ESISUD00' ha terminado anormalmente.
ACCIÓN:
Consulte los errores precedentes para el programa de canal
'ESBRKD01V6.ESISUD00' en los archivos de errores para determinar la causa del
fallo.
----- amqrccca.c : 777 --------------------------------------------------------
ERROR FROM COMMAND LINE
C:\Documents and Settings\INSXM01>runmqchl -m ESBRKD01 -c ESBRKD01V6.ESISUD00 5724-H72 (C) Copyright IBM Corp. 1994, 2004. TODOS LOS DERECHOS RESERVADOS.
08/01/2007 09:21:55 El canal 'ESBRKD01V6.ESISUD00' se está iniciando.
08/01/2007 09:21:57 AMQ9209: Conexión al sistema principal '☻' cerrada.
08/01/2007 09:21:57 AMQ9999: El programa de canal ha terminado anormalmente.
That's in spanish and more/less says that channel is trying to connect and then "AMQ9209: Conection to system 0x00 closed." after "channel program closed".
Can someone help me solving this, I was a week trying it but i can't do. Why can't give me the correct system name?
Thanks in advance to all. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jan 08, 2007 1:39 am Post subject: Re: Connecting Windows QM V6 to HP-UX QM V5.3 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| contact admin wrote: |
Why can't give me the correct system name?
|
Why can't what give you what name? 
AMQ9209 is typically associated with a network error, which you'd know if you search this forum or Googled. As a first move make sure a connection is available between the 2 machines on the port number you're using. As a second move ensure the listener is running on the target machine.
IF that fails, search as I suggest above for a laundry list of typical problems. There's nothing inherantly odd about what you're trying to do in terms of platform and/or software level.
Happy Searching! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Mon Jan 08, 2007 1:47 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
Use telnet or ping, and verify the network is trouble free or not
i suggest you to use telnet.
Search this forum, you will get the answer
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 08, 2007 1:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gaya3 wrote: |
| verify the network is trouble free or not |
I thought I said that....
| Gaya3 wrote: |
| Search this forum, you will get the answer |
I quite positively said that! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ignasi |
| Posted: Mon Jan 08, 2007 1:59 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
If I make a telnet from HP-UX to windows or from windows to HP-UX on the port of the listeners the connection can be solved.
The channel from HP-UX to windows is connected and running.
The other from windows to HP-UX fails.
I've got a zOS too and a pair of channels one from zOS to windows that works perfectly and one from windows to zOS that doesn't work, same as HP-UX.
Channel on windows:
C:\>runmqsc ESBRKD01
5724-H72 (C) Copyright IBM Corp. 1994, 2004. TODOS LOS DERECHOS RESERVADOS
Se está iniciando MQSC para el gestor de colas ESBRKD01.
DISPLAY CHANNEL(ESBRKD01V6.ESISUD00)
1 : DISPLAY CHANNEL(ESBRKD01V6.ESISUD00)
AMQ8414: Detalles de Display Channel.
CHANNEL(ESBRKD01V6.ESISUD00) CHLTYPE(SDR)
ALTDATE(2007-01-0 ALTTIME(09.27.54)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(WIND_PC(1410))
CONVERT(NO) DESCR( )
DISCINT(6000) HBINT(300)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(PROCESS) MCAUSER( )
MODENAME( ) MONCHL(QMGR)
MSGDATA( ) MSGEXIT( )
NPMSPEED(FAST) PASSWORD( )
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCIPH( )
SSLPEER( ) STATCHL(QMGR)
TPNAME( ) TRPTYPE(TCP)
USERID( ) XMITQ(ESISUD00)
Channel on HP-UX:
/var/mqm/qmgrs/ESISUD00#runmqsc ESISUD00
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager ESISUD00.
DISPLAY CHANNEL(ESBRKD01V6.ESISUD00)
1 : DISPLAY CHANNEL(ESBRKD01V6.ESISUD00)
AMQ8414: Display Channel details.
CHANNEL(ESBRKD01V6.ESISUD00) CHLTYPE(RCVR)
TRPTYPE(TCP) DESCR( )
BATCHSZ(50) SCYEXIT( )
SEQWRAP(999999999) MAXMSGL(4194304)
PUTAUT(DEF) SCYDATA( )
MREXIT( ) MRDATA( )
MRRTY(10) MRTMR(1000)
HBINT(300) NPMSPEED(FAST)
SSLCIPH( ) SSLCAUTH(REQUIRED)
KAINT(AUTO) MCAUSER( )
ALTDATE(2007-01-0 ALTTIME(10.56.32)
SSLPEER()
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( ) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 08, 2007 2:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So inbound channels TO windows work, but outbound channels FROM windows don't work.
But telnet does work.
Probably a firewall issue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ignasi |
| Posted: Mon Jan 08, 2007 4:37 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
This was the event log output:
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 9209
Date: 08/01/2007
Time: 13:24:59
User: N/A
Computer: MQTESTMQ
Description:
Connection to host '' closed.
An error occurred receiving data from '' over TCP/IP. The connection to the remote host has unexpectedly terminated.
Tell the systems administrator. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 08, 2007 4:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I stand by network problems as the likely cause, and I'd have gone with jefflowrey as the firewall being the most likely suspect.
Shut down any firewalls on the Windows machine (especially that stupid thing that comes with XP!) and anything else on the link between Windows & HP-UX, then start the channel. If it comes up, this proves it's the firewall and you can then work through getting the channel to work with the protection in place.
Another thing you could try is using absolute IP addresses in the channels (nnn.nnn.nnn.nnn) in case the DNS isn't doing what you think it is.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ignasi |
| Posted: Mon Jan 08, 2007 5:08 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
Nothing with firewalls: All the windows 2k3 are disabled and HP-UX too.
There are a curious think:
From windows I can resolve the HP-UX machine name but from HP-UX I can't resolve the windows one. Thinking on this, the windows tx cannel connection has the HP-UX name to call gethostbyname() ok and the HP-UX tx channel connecion has the ip address of the windows one to posible bypass the call to gethostbyname() that the DNS will fail.
It seems that, when HP-UX receives a connection from windows one, wants to resolve his name and cannot do it. Then on the fail error the remote host name was a 0x00 character.
Aaaaaargh! Nothing on HP-UX errors, @SYSTEM/errors/, QMGR/errors/, mq errors.
I walk on te dark. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 08, 2007 5:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you can't resolve the hostname using DNS, then you can either use the direct IP address, or you can put an entry for the hostname into /etc/hosts.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ignasi |
| Posted: Mon Jan 08, 2007 5:18 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
| With IP address it was just retrying. But on zOS the problem was solved! Only 1 left. |
|
| Back to top |
|
|
| ignasi |
| Posted: Mon Jan 08, 2007 5:25 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
On the HP-UX system I've created SYSTEM.MQEXPLORER.REPLY.MODEL to browse the QManager from V6 explorer on the windows and a 2195(AMQ4048) error goes up; but I can explore this queue manager from a V5.3 explorer on a windows machine.
... I'm going to turn crazy. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 08, 2007 5:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| contact admin wrote: |
On the HP-UX system I've created SYSTEM.MQEXPLORER.REPLY.MODEL to browse the QManager from V6 explorer on the windows and a 2195(AMQ4048) error goes up; but I can explore this queue manager from a V5.3 explorer on a windows machine.
... I'm going to turn crazy. |
If there's a 2195 there should be a (helpful/informative) entry in the queue manager log file. Google / search this forum for the probe id.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ignasi |
| Posted: Mon Jan 08, 2007 6:04 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
Nothing generated, only event log
Event Type: Information
Event Source: WebSphere MQ
Event Category: None
Event ID: 9002
Date: 08/01/2007
Time: 14:57:15
User: N/A
Computer: MQTESTMQ
Description:
Channel 'ESBRKD01V6.ESISUD00' is starting.
Channel 'ESBRKD01V6.ESISUD00' is starting.
None.
---------------------------------------------------------------------------
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 9209
Date: 08/01/2007
Time: 14:57:18
User: N/A
Computer: DMQIV6A1
Description:
Connection to host '' closed.
An error occurred receiving data from '' over TCP/IP. The connection to the remote host has unexpectedly terminated.
Tell the systems administrator.
---------------------------------------------------------------------------
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 9999
Date: 08/01/2007
Time: 14:57:18
User: N/A
Computer: DMQIV6A1
Description:
Channel program ended abnormally.
Channel program 'ESBRKD01V6.ESISUD00' ended abnormally.
Look at previous error messages for channel program 'ESBRKD01V6.ESISUD00' in the error files to determine the cause of the failure.
AMQERR01.LOG
08/01/2007 14:57:15 - Process(5580.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9002: El canal 'ESBRKD01V6.ESISUD00' se está iniciando.
EXPLICACIÓN:
El canal 'ESBRKD01V6.ESISUD00' se está iniciando.
ACCIÓN:
Ninguno.
-------------------------------------------------------------------------------
08/01/2007 14:57:18 - Process(5580.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9209: Conexión al sistema principal '' cerrada.
EXPLICACIÓN:
Se ha producido un error al recibir datos de '' a través de 'TCP/IP'. La
conexión con el sistema principal remoto ha finalizado inesperadamente.
ACCIÓN:
Póngase en contacto con el administrador del sistema.
----- amqccita.c : 3094 -------------------------------------------------------
08/01/2007 14:57:18 - Process(5580.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9999: El programa de canal ha terminado anormalmente.
EXPLICACIÓN:
El programa de canal 'ESBRKD01V6.ESISUD00' ha terminado anormalmente.
ACCIÓN:
Consulte los errores precedentes para el programa de canal
'ESBRKD01V6.ESISUD00' en los archivos de errores para determinar la causa del
fallo.
----- amqrccca.c : 777 --------------------------------------------------------
Same but in spanish and no FDC generated. |
|
| Back to top |
|
|
| ignasi |
| Posted: Thu Jan 11, 2007 2:49 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2007
Posts: 8
Location: Barcelona
|
Ok, problem solved!!
The problem was with inet.sec, mqseries starts with inetd and the security applied denies access from my V6 machine but I can't access to its configuration.
SAP people, who administers machine, sends the configuration, we change it and TXATXAN!! it works.
Thanks to all for your help. |
|
| Back to top |
|
|
|
|
