| Author |
Message
|
| murdeep |
 Posted: Wed Mar 08, 2006 11:49 am Post subject: MQTCPSDRPORT |
 |
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Hi, I've recently migrated to WMQ V6. I have the environment variable set as follows MQTCPSDRPORT=2750,2780. When I attempt to ping the channel I get an error indicating that the channel cannot bind to the port. In my AMQERR01.LOG is the following:
| Code: |
3/7/2006 15:48:30 - Process(2120.1) User(murdeep) Program(runmqchl.exe)
AMQ9248: The program could not bind to a TCP/IP socket.
EXPLANATION:
The attempt to bind to socket '(2750,2800)' failed with return code 10047. The
failing TCP/IP call was 'bind'. The most likely cause of this problem is
incorrect configuration of the TCP/IP local address or incorrect start and end
port parameters.
ACTION:
Contact the system administrator. If the problem persists contact your IBM
support center.
|
Does V6 no longer support MQTCPSDRPORT and I must now use the LOCLADDR attribute on the sender channel? |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Mar 08, 2006 1:05 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
it works fine in my V6 FP1 linux system.... 
_________________
-wayne |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Mar 08, 2006 5:15 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Update; I did a quick test on windows (win2k) and it fails with either locladdr or the environment variable set.. (again v6 fp1).... 
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Mar 08, 2006 5:54 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| wschutz wrote: |
| Update; I did a quick test on windows (win2k) and it fails with either locladdr or the environment variable set.. (again v6 fp1).... |
Wayne, are there any error messages on the console or in the error logs for your failing case? |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Mar 08, 2006 6:07 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
mvic .... at the command line:
| Quote: |
F:\tmp>runmqchl -m TEST -c TEST.TEST
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
3/8/2006 20:10:59 Channel 'TEST.TEST' is starting.
3/8/2006 20:10:59 AMQ9248: The program could not bind to a TCP/IP socket.
3/8/2006 20:10:59 AMQ9999: Channel program ended abnormally.
|
in amqerr01:
| Quote: |
----- amqrccca.c : 777 --------------------------------------------------------
3/8/2006 20:52:39 - Process(1112.1) User(wschutz) Program(runmqchl.exe)
AMQ9002: Channel 'TEST.TEST' is starting.
EXPLANATION:
Channel 'TEST.TEST' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
3/8/2006 20:52:39 - Process(1112.1) User(wschutz) Program(runmqchl.exe)
AMQ9248: The program could not bind to a TCP/IP socket.
EXPLANATION:
The attempt to bind to socket '192.168.140.1(5000,5100)' failed with return
code 10049. The failing TCP/IP call was 'bind'. The most likely cause of this
problem is incorrect configuration of the TCP/IP local address or incorrect
start and end port parameters.
ACTION:
Contact the system administrator. If the problem persists contact your IBM
support center.
----- amqccita.c : 1253 -------------------------------------------------------
3/8/2006 20:52:39 - Process(1112.1) User(wschutz) Program(runmqchl.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TEST.TEST' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TEST.TEST' in the error
files to determine the cause of the failure.
----- amqrccca.c : 777 --------------------------------------------------------
|
I e-mailed the trace file ....
_________________
-wayne |
|
| Back to top |
|
|
| murdeep |
| Posted: Wed Mar 08, 2006 7:42 pm Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
My system is W2K V6 (FP1 not applied). I disabled the env variable MQTCPSDRPORT and specified LOCLADDR and it did work. I did a netstat -a and saw the outbound channel was using port 2750.
Notice that when mine failed it was a RC10047 and Wayne's was RC10049 with the explanations as:
10047 WSAEAFNOSUPPORT The specified address family is not supported.
10049 WSAEADDRNOTAVAIL The specified address is not available from the local machine.
Any ideas? |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Mar 09, 2006 2:26 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Good catch  ...I put in the NIC address on my locladdr statement and must have mistyped it ... okay... so, now I can use: LOCLADDR('(x,y')) and that works, but MQTCPSDRPORT doesn't (and I get a 10047)....
mvic, I've sent a new trace ....
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Mar 09, 2006 4:11 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| murdeep wrote: |
| Any ideas? |
Sorry, although Wayne and I have looked at this, and compared notes, we have not found the solution. Please do raise a call with Support, as this is a pretty clear problem description, and easy to demonstrate beyond any doubt what is going on - it will help if you collect trace
| Code: |
strmqtrc -t all -t detail
# recreate problem
endmqtrc
|
and "netstat /a" output (to prove what ports are/are not in use) and send it in once the PMR is open. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Mar 09, 2006 5:05 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Support are likely to reply that MQTCPSDRPORT is an undocumented and unsupported parameter, so if it no longer works at v6 that is hard luck.
Why not use LOCLADDR instead? That IS supported and documented.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Mar 09, 2006 5:26 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
|
| Back to top |
|
|
| murdeep |
| Posted: Thu Mar 09, 2006 9:24 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Nigelg, I agree that if LOCLADDR works then I'll use it...I just want to make know if the env var is no longer supported. BTW, I also tested where the registry has TCP entries StrPort and EndPort (qm.ini equivalent) and that didn't work.
So it looks like LOCLADDR is the only way that works. This is bad since if you have lots of channels then you'll need to change them all when migrating from V5.x to V6. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Mar 09, 2006 9:52 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
murdeep, I agree with mvic, you should open a PMR... a trace of the mca reveals that the MQTCPSDRPORT variable is being read and binds are being issued with specific port #'s trying to setup the socket, but they are failing....
_________________
-wayne |
|
| Back to top |
|
|
| murdeep |
| Posted: Thu Mar 16, 2006 10:09 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| Problem is known to IBM. Fix is available. |
|
| Back to top |
|
|
|
|
