In an INET environment where only a single TCP/IP stack can be running, Telnet client connections are automatically associated with the active stack, and you do not need to explicitly associate the Telnet server to the stack.
In a common INET (CINET) environment, Telnet is associated with all stacks that are running. When multiple stacks are supporting a single Telnet server, Netstat displays might not display all Telnet connections. The only connections that are displayed are connections that are supported by the stack from which the command is issued. If another stack is started while Telnet is active, the current LISTEN for the port is cancelled and is reissued automatically to include the new stack. If you explicitly associate Telnet to one TCP/IP stack, all Telnet clients must connect through that stack.
If you want to explicitly associate Telnet with one stack for control purposes or for functionality support, use the TCPIPJOBNAME statement in the TELNETGLOBALS block when you start Telnet. If you use the TCPIPJOBNAME statement, you must continue to use it on all future profile updates to set affinity to the same stack.
The Telnet SNMP subagent requires that you explicitly associate Telnet with a single TCP/IP stack. Telnet SNMP subagent activation requires that you register the stack name with the agent. If you do not specify the TCPIPJOBNAME statement, then Telnet blocks the subagent activation request. The Telnet SNMP subagent can register with only one agent, and each agent can support only one Telnet subagent. If you are going to use the Telnet SNMP subagent, plan for one agent per Telnet subagent. If multiple Telnet SNMP subagents initialize to the same agent, the agent forwards all data requests to the first subagent that connected, and all other initialization attempts are queued. If the first subagent ends, then the next subagent in the queue receives all data requests.