PI38683: TELNET SERVER LOOPs

APAR status

• Closed as fixed if next.

Error description

• Telnet profile defined a port multiple times. Example
  TELNETPARMS
    CONNTYPE SECURE
    SECUREPORT    nn
    TTLSPORT      nn
  .
  .
  
  
  
  
  .
  The two TelnetParms statements refer to the same port number.
  The Telnet server flags the definition error and attempts to
  recover while issuing message:
  .
  EZZ6035I TN3270 DEBUG CONFIG EXCEPTION
   LINE:       77              MOD: EZBTMPRP
   RCODE: 8068-00 Duplicate statement or parameter. Last one used.
   PARM1:          PARM2: 00000000 PARM3: TTLSPORT
  .
  When a connection request attempts to use the port, the Telnet
  server loops trying to process the request.
  

Local fix

• Remove the offending parameter identifed in the EZZ6035I
  message and then restart the Telnet Server, or recycle
  the secure ports by using commands:
    V TCPIP,telnet_proc,T,STOP,PORT=SECURE
  Remove the offending parameter
    V TCPIP,telnet_proc,O,fully.qualified.profile(name)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications Server for z/OS Version  *
  * 2 Release 1 IP Telnet Services                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Loop in Telnet when both SECUREPORT and TTLSPORT are coded   *
  * for the same port number.                                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * FIN                                                          *
  ****************************************************************
  The problem may be summarized as follows:
  1. Both SECUREPORT and TTLSPORT were coded for PORT xxx.
  2. When the profile was activated, message EZZ6035I is issued
  with RC=8068, indicating a duplicate parameter and that the last
  one would be used.
  3. When a connection was attempted to that port, residual
  information from the SECUREPORT statement conflicted with
  information from the TTLSPORT statement and caused a loop.
  

Problem conclusion

Temporary fix

Comments

• The solution for this APAR is included in CS for zOS Version 2
  Release 3.
  
  This APAR is being closed FIN (Fixed If Next) with concurrence
  from the submitting customer. This means that a fix to this
  APAR is expected to be delivered from IBM in a release (if any)
  to be available within the next 36 months.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R210 PSN

     UP