W3SV1003 REQUEST FAILED FOR PORT=2635, REGISTER(BIND_FAILED), ERROR=EADDRINUSE, VERRIN=48
Article ID: 43194
Updated On:
Products
Issue/Introduction
Seeing this message in the Netmaster log:
W3SV1003 REQUEST FAILED FOR PORT=2635, REGISTER(BIND_FAILED), ERROR=EADDRINUSE, VERRIN=48
Environment
Netmaster for TCP/IP or Netmaster File Transfer, all supported releases
Cause
The named Webcenter PORT – in this case 2635 – is already in use elsewhere.
Resolution
Netmaster has multiple locations where listener ports are defined for various purposes. The W3SV1003 message indicates that the port defined in /PARMS $NM WEBCENTER is also defined elsewhere either within Netmaster or on the system. More specifically, it is already in use as a listener port on the local TCP/IP stack.
Each portname must be unique on the system.
To determine where the duplication originates:
1. In your Netmaster region, check the following parameter groups in /PARMS and ensure the port numbers are unique:
/PARMS $NM SOCKETS
/PARMS $NM WEBCENTER
/PARMS $NM REPORTCENTER (if in use)
2. Alternately, from your Netmaster region go to Command Entry (CMD).
Issue the command SH SOCKETS.
You should see separate TCP ports for the TCP/IP Sockets, Webcenter and ReportCenter (if in use).
You can review and update the individual /PARMS members as needed in case of duplication.
3. If you do not see any duplication within the region, go to the /IPDIAG.NS screen and select CONN SERVER.
This will display all TCP/IP listeners on the local stack. You can then do a ‘find’ on the port being reported as duplicate in the W3SV1003 message.
Make corrections as needed.
Additional Information
Screenshots for the parameter groups noted above.
In this case all are defined properly with differing port numbers:
/PARMS $NM SOCKETS
NM01-------------------- Customizer : Parameter Group --------------Page 1 of 2
Command ===> Function=Browse
+- SOCKETS - TCP/IP Sockets Interface ----------------------------------------+
| |
| TCP/IP Software Type ......... USS (USS, IBM, IBMV6 or TCPACCES) |
| |
| Inbound Connections Port ..... 2635 (NONE, 257 to 65535) |
| |
| Retry Interval ............... 00.10 (Blank or time as hh.mm) |
| |
+-----------------------------------------------------------------------------+
/PARMS $NM WEBCENTER
NM01-------------------- Customizer : Parameter Group --------------Page 1 of 2
Command ===> Function=Browse
+- WEBCENTER - WebCenter Web Interface ---------------------------------------+
| |
| Web Interface Port .............. 8635 (NONE, 1 to 65535) |
| Access URL ...................... http://##.##.##.###:8625 |
| Access URL Host Override ........ |
| User Timeout .................... 02.00 (hh.mm) |
| Enable SYSVIEW Interface? ..... YES (YES or NO) |
| Enable Public IP Pages .......... YES (YES or NO) |
| |
| Performance Charts |
/PARMS $NM REPORTCENTER
NM01-------------------- Customizer : Parameter Group --------------Page 1 of 6
Command ===> Function=Browse
+- REPORTCENTER - ReportCenter Control Region --------------------------------+
| |
| ReportCenter Java Task Started Task Name NMJAVA |
| |
| ReportCenter Java Task Setup: |
| IP Host Name or Address ....... ##.##.##.### |
| Port Number ................... 7635 |
| Daily Housekeeping Start ...... 01.30 |
| Enable SYSVIEW Interface? ..... YES (YES or NO) |
| Enable Public IP Pages .......... YES (YES or NO) |
| |
| Performance Charts |
The SH SOCKETS command from Step 2 will look something like this. Note that port 2635 (from $NM SOCKETS) appears multiple times.
This specific example doesn’t show ReportCenter.
sh sockets
N3AF05 TCP/IP INTERFACE IS ACTIVE NAME=USS PRIMARY=YES IPVERS=4
N3AF03 SOCKET TYPE OWNER CLIENTID LPORT PPORT PEER-IP-ADDRESS
N3AF40 SERVER-NAME
N3AF41 ------ ---- -------- -------- ----- ----- ----------------------------------------
N3AF04 004605 RAW PINGTR 00000013 - - -
N3AF04 030002 RAW PINGTR 00000006 - - -
N3AF04 004604 RAW PINGTR 00000012 - 0 ##.##.##.###
N3AF04 000499 TCPL 000492 00000007 8635 - -
N3AF04 000500 TCPI 000492 - - - -
N3AF04 000475 RAW 000456 00000005 - 0 ##.##.##.###
N3AF04 000320 TCPL 000318 - 2635 - -
N3AF42 CHORUSPERF
N3AF04 000304 TCPL IPAM - 2635 - -
N3AF42 .IPAM
N3AF04 000301 UDP DNR 00000004 25358 - -
N3AF04 000299 TCPL SOLVE 00000002 2635 - -
N3AF04 000302 TCPI SOLVE - - - -
N3AF18 UNIX TYPE OWNER CLIENTID LOCAL-PATH PEER-PATH
N3AF43 SOCKET SERVER-NAME
N3AF44 ------ ---- -------- -------- ------------------------- -------------------------
N3AF19 000499 TCPL 000492 00000007 - -
N3AF19 000320 TCPL 000318 - - -
N3AF46 CHORUSPERF
N3AF19 000304 TCPL IPAM - - -
N3AF46 .IPAM
N3AF19 000300 TCPL SOLVE 00000003 /usr/netm -
N3AF19 000303 TCPI SOLVE - - -
N11907 *END*
** END OF DELIVERED MESSAGES **
The CONN SERVER display from Step 3 will look something like this.
NETSTAT CO SERVER STACK=TCPIP
MVS TCP/IP NETSTAT CS V2R2 TCPIP Name: TCPIP 10:32:30
User Id Conn State
------- ---- -----
DB2DIST 00000193 Listen
Local Socket: ::..5120
Foreign Socket: ::..0
FTPD 00000033 Listen
Local Socket: ::..21
Foreign Socket: ::..0
NM01 0012CAD5 Listen
Local Socket: ::..2635
Foreign Socket: ::..0
NM01 0012CABB Listen
Local Socket: ::..8635
Foreign Socket: ::..0
Feedback
