Troubleshooting
Problem
Telnet, as a separate address space, is unable to listen on a port after issuing the following message: EZZ6011I TELNET BPX1BND FAILED, RC = 0000006F RSN = 744C7246 or EZZ6011I TELNET BPX1BND FAILED, RC = 0000045B RSN = 12BA00C4
Cause
Telnet is configured to run as a separate address space. When Telnet tries to listen on a port specified by the Telnet configuration, the following messages are issued:
EZZ6011I TELNET BPX1BND FAILED, RC = 0000006F RSN = 744C7246
- EZZ6011I TELNET BPX1BND FAILED, RC = 0000045B RSN = 12BA00C4
- EZZ6035I TELNET DEBUG COMPONENT PORT 392
CONN: 00000000 LU: TELNET MOD: EZBTTINI
RCODE: 102B-00 Socket initialization failed. No retry.
PARM1: 00000000 PARM2: 00000000 PARM3: 00000000
EZZ6010I TELNET SERVER ENDED FOR PORT 23
The EZZ6011I message with function BPX1BND indicates Telnet was unable to bind to the port.
The RC of 6F is EACCES, meaning permission is denied to the port. The RSN of 744C7246 indicates JRPORTACCESSAUTH. This means the user does not have authority to access this port.
The RC of 45B is EADDRINUSE, meaning the address is already in use. The RSN of 12BA00C4 indicates JRRESRPORTSPECIFIED. This means that during a socket bind request, a reserved port was incorrectly specified.
Resolving The Problem
For RC of 6F:
Check the TCPIP profile to ensure that the port specified in message EZZ6010I is reserved for the Telnet server. If migrating from the internal Telnet server, you must change the job name from INTCLIEN or the TCPIP stack name to the job name Telnet is now running under. If the port is being protected by a SAF resource, the Telnet address space must be permitted to that resource. Review the IP Configuration Reference for more information on the PORT statement. If multiple TCPIP stacks are active, Telnet will try to bind on port 23 on all stacks. Code the TCPIPJOBNAME statement within TELNETGLOBALS to cause Telnet to bind only to the specified TCPIP stack.
For RC of 45B:
For RSN 12BA00C4, the port Telnet is trying to bind to is in the INADDRANYPORT range configured in the BPXPRMxx member. Telnet will either need to bind to a different port or the INADDRANYPORT range will need to be changed in BPXPRMxx. The TelnetParms and BeginVtam section must be modified to change the port number Telnet binds to. See the UNIX System Services Planning manual for more information on INADDRANYPORT.
[{"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"All","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"1.6;1.7;1.8;1.9;1.10;1.11;1.12;1.13;2.1;2.2;2.3","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21235564