| Author |
Message
|
| vennela |
 Posted: Mon Sep 16, 2002 9:13 am Post subject: |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If you feel there is a firewall between the Windows machine and the host then try to telnet to the host from the NT machine.
Use a telnet client and say
telnet eoo3.esb.eur.deuba.com 1414
if it returns back saying connection failed then this port on the host will not communicate with your NT machine. Make sure you use the port 1414 instead of the default 23 telnet port. |
|
| Back to top |
|
 |
| jc_squire |
| Posted: Mon Sep 16, 2002 1:10 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2002
Posts: 105
Location: New Zealand
|
Shobha,
The channel initiator is responsible for starting a channel which is in a retry state i.e. it searches the channel table at intervals for any channel with a status of retrying and if it is scheduled to retry at that interval, the channel initiator starts it, hence, no channel initiator no retrying even though it shows it is in this state. If it was retrying you would see this in your error logs.
You could possible have more than one problem here but as a first step get your your channel initiator running.
Regards
_________________
J C Squire
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| mgrabinski |
| Posted: Mon Sep 16, 2002 9:41 pm Post subject: |
|
|
Master
Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland
|
You said that some messages had ended in the DLQ on the mainframe. Could you post their DLQH header or the reason field at least?
In one of this year's MQUpdate (I believe it was March or April) there is an utility that reads DLQ on a mainframe and prints a report showing all fields of DLQH in understandable format
_________________
Marcin Grabinski <>< |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Mon Sep 16, 2002 11:37 pm Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Hi..
I meant dead letter queue on the NT not on the mainframe...
When I try to ping with the port it says bad IP address...but without the port number it returns a reply..
thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Tue Sep 17, 2002 3:20 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
When you say PING, it that a MQ-ping or a TCP/IP ping ?
What does your OS/390 guis tell you?
Are there any trace of "SHOBHA.RECEIVE" in the EOO3CHIN tasks DD=JESMSGLG ?
If your Firewall folks have closed port 1414, you would't see any trace in the EOO3CHINs JESMSGLG.
You could try to contact the mqserver via TELNET like this:
| Quote: |
| TELNET eoo3.esb.eur.deuba.com:1414 |
Yes I know it will fail, but if the firewall is ok, there will be a trace like this in EOO3CHIN log:
| Quote: |
+CSQX207E Qxxxx CSQXRESP Invalid data received, connection
xxx.xxx.xxx.xxx,TRPTYPE=TCP
+CSQX228E Qxxxx CSQXRESP Listener unable to start channel,
TRPTYPE=TCP INDISP=QMGR |
and on your WIN/NT somthin like this:'
| Quote: |
C:\>telnet eoo3.esb.eur.deuba.com:1414
Connecting To eoo3.esb.eur.deuba.com:1414...Could not open a connection to host: Connect failed |
Lets take it from here
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Tue Sep 17, 2002 3:59 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Hello...
I can not see any trace of my receiver channel...also none of the recevier channels on the e003 show up on the chin log.yup it says connection failed...But how is that when I try to ping the channel it says 'the channel was pinged successfully. Mqseries sent data to remote Queue Manager and received the data returned(AMQ4006).' OFcourse when I try to ping from the command prompt with the port number also it returns the message host not found or undefined host. But without the port number it pings successfully.
I have asked the same question to our MQ expert but he is yet to get back..as this is not related to any project..
Ultimately looks like I can not proceed further...as there is no way of asking them to remove that firewall if at all that exists just for my experimenting...
thanks...
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Tue Sep 17, 2002 6:15 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
When you use the ping from the command line it's TCP/IP ping, and it communicates with a ping service on the host. This have nothing to do with MQSeries at all.
Have you tried the TELNET as I mentioned just above, TELNET can make a note in MQSeries log, so you can see there are a hole in the firewall.....
You can do it from both sides (if you have a listener started ofcause.. ;o))
Let's get forward and find the rice corn.
Just my $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Tue Sep 17, 2002 7:00 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Yes..as I wrote in the last mail...it says Connection Failed when I try to do with telnet...How do u do it from the host side?....Because I tried giving TELNET e003.esb.eur.deuba.com:1414 at the command prompt which opened the TELNET Dialong Screen.There a connect to the Host system says Connection Failed...
Thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Tue Sep 17, 2002 7:50 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Just as I expected, the take a look in the host system in EOO3CHIN log and see if there are a report of the connection attempt.
From the host you can try TSO TELNET pconnname port, and yes it fails too, but you will be able to see an error in the event viewer (on NT)....
Saying somthing like :
| Quote: |
Error on receive from host conname(Ipaddr).
An error occurred receiving data from conname(Ipaddr) over TCP/IP. This may be due to a communications failure.
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these values and tell the systems administrator. |
This would tell you that there are a TCP/IP hole thru....
Hope it help.
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| dgolding |
| Posted: Tue Sep 17, 2002 9:59 pm Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
What do you get when you ping channel?
Have you done an AMQSBCG of the DLQ and decoded the error?
What does the AMERR01.LOG say? |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Wed Sep 18, 2002 2:04 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Yes I did try from the host as u had mentioned but it returns not the message 'connection failed' but " Foreign host did not respond within OPEN timeout (8560) ". And th Event viewer on NT doesn't say anything about this attempt.There is no report n the CHIN log either.
and Golding, The messages are on the dead letter queue on the NT side...browsing the message does not show any error message.Could it be that remote administration of the que manager on NT may not have been permitted?....
thanks..
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| dgolding |
| Posted: Wed Sep 18, 2002 2:10 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| The DLQ does not contain error messages, it contains an error code. Bytes 9-12 will have the error code, which is reverse order (bytes 1 and 2 should be 3 & 4 respectively, and vice versa). |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Mon Oct 07, 2002 3:33 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
I think you should take a chat with your network folks, and ask is port 1414 is open for comminication.
Another thin to check (haven't we covered that before ??) if the TCPIP listener is running?
just another $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
|
|
