| Author |
Message
|
| harshatej1 |
 Posted: Wed Apr 22, 2015 12:26 pm Post subject: MQ Client |
 |
|
Acolyte
Joined: 20 Nov 2013
Posts: 61
|
Hi,
I am receiving below error in MQ Client(error logs). Remote server is Mainframe.
AMQ9202: Remote host 'mainserver (IP) (PORT)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'mainserver
(IP) (PORT)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
There is no network issue. Application side tell that they are receiving "2059 Initialization error". Remote queue manager is up and running fine. port is open.
Please suggest me a solution for this. |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Wed Apr 22, 2015 12:40 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Just out of interest what is the full message? There should be an ACTION part of the message which tells you the TCP/IP return code.
Cheers,
Paul
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| harshatej1 |
| Posted: Wed Apr 22, 2015 12:47 pm Post subject: |
|
|
Acolyte
Joined: 20 Nov 2013
Posts: 61
|
ACTION:
Try the connection again later. If the failure persists, record the error values and contact your systems administrator. The return code from TCP/IP is 10060 (X'274C'). The reason for the failure may be that this host cannot reach the destination host. It may also be possible that the listening program at host 'Server' was not running. If this is the case, perform the relevant operations to start the TCP/IP listening program, and try again. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 22, 2015 1:07 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| harshatej1 wrote: |
| ...The return code from TCP/IP is 10060 (X'274C')... |
Looks like a Windows TCP/IP error code to me, and if so is a connection time out. Is there a firewall between the client and server? Anything in the CHIN log of the z/OS queue manager? And are you absolutely certain that the CLNTCONN/SVRCONN definitions match?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 23, 2015 5:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| exerk wrote: |
| harshatej1 wrote: |
| ...The return code from TCP/IP is 10060 (X'274C')... |
Looks like a Windows TCP/IP error code to me, and if so is a connection time out. Is there a firewall between the client and server? Anything in the CHIN log of the z/OS queue manager? And are you absolutely certain that the CLNTCONN/SVRCONN definitions match? |
And the channel auth will let you through? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 23, 2015 6:09 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| exerk wrote: |
| harshatej1 wrote: |
| ...The return code from TCP/IP is 10060 (X'274C')... |
Looks like a Windows TCP/IP error code to me, and if so is a connection time out. Is there a firewall between the client and server? Anything in the CHIN log of the z/OS queue manager? And are you absolutely certain that the CLNTCONN/SVRCONN definitions match? |
And the channel auth will let you through? |
Hence my question in regard to the CHIN log - as the OP has not stated at which version the z/OS queue manager is running I wasn't going to assume the version in use is one that has CHLAUTH facility...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 23, 2015 6:14 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Not sure you see anything in the CHIN log if the rejection happens at the listener level...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 23, 2015 6:21 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| Not sure you see anything in the CHIN log if the rejection happens at the listener level... |
Would a V7.0 z/OS queue manager block at listener level?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 23, 2015 7:22 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| exerk wrote: |
| fjb_saper wrote: |
| Not sure you see anything in the CHIN log if the rejection happens at the listener level... |
Would a V7.0 z/OS queue manager block at listener level? |
7.1 and above would...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 23, 2015 7:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| exerk wrote: |
| fjb_saper wrote: |
| Not sure you see anything in the CHIN log if the rejection happens at the listener level... |
Would a V7.0 z/OS queue manager block at listener level? |
7.1 and above would... |
I was hoping the OP would come back with an answer as to just which level they're at, but so far silence. I'd also be very surprised to find that even if at V7.1 or V8.0, that a specific CHLAUTH rule would be used to block a connection from what should be a known source.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 23, 2015 7:35 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| exerk wrote: |
| I'd also be very surprised to find that even if at V7.1 or V8.0, that a specific CHLAUTH rule would be used to block a connection from what should be a known source. |
Missing a channel auth rule and hitting a backstop rule...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
