PQ78475: EZZ6038I TELNET COMMAND INACT LUNAME COMPLETE - FOLLOWED BY EZZ6039I TELNET COMMAND INACT LUNAME FAILED, RCODE=3002

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• TN3270E client with LUSESSIONPEND and DEFAULTAPPL coded attempts
  to start a session.  OPEN ACB fails and the TELNET SERVER issues
  error message "EZZ6038I TELNET COMMAND INACT luname COMPLETE".
  Because this is a TN3270E Client,  after MSG07 is sent and the
  client responds with a LOGON APPLID(applname), the OPEN ACB is
  again attempted with the same LUNAME as before. This causes
  "EZZ6039I TELNET COMMAND INACT luname FAILED, RCODE=3002" (lu-
  name is already inactive).  MSG07 is sent with OPEN OPEN failure
  RC=x'5A' and the process repeats itself as long as the client
  continues to retry.
  

Local fix

• Initial OPEN ACB failure occured due to improper coding of the
  VTAM LFBUF pool.  This buffer pool needed to be tuned.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Communications Server           *
  *                 z/OS Version 1 Release 5                     *
  *                 IP Telnet facilities.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Client logging onto Appl repeatedly     *
  *                      MSG07 screen after OPEN ACB Failure     *
  *                      makes it seem Telnet is in a loop.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  EZBTVOPN just sets RCODE to RC_OPEN_ACB_FAIL (2013) and MSG07
  is sent back to the client. The Client with a screen scraper
  running, just does a LOGON APPLID( ) again repeatedly with
  MSG07 going back for each. This appears to be never ending
  with LUSESSIONPEND coded.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• Telnet will be changed to disconnect a client that had an LUNAME
  that failed the OPEN ACB request. The CVB already has an OPEN
  fail flag.  Now if the client logs on again, and OPEN
  ACB Fails, If CVB_OpenFail is is already on, the Rcode will
  be set to RC_OPEN_ACB_FAIL_TWICE, Rcode 2044.
  If debug is on EZZ6035I will be issued with this
  return code and the client disconnected EZBTTCLS will recognize
  this new RCODE and disconnect the client. EZBZTDBG has the
  new Rcode defined and EZBTZDB2 for will have the new Rcode
  defined to cause the message to get issued.
  EZAZMTNS will have the new Rcode and
  description added. EZBTZMSG is shipped to pick up this.
  .
  Documentation Changes:
  SC31878604  V1R5   IBM Communications Server: IP Messages: Vol 4
  Under message EZZ6035I Find the Rcode 2043 and add the following
  just after it:
  .
  2044
  .
  A TN3270E connection gets the LUNAME allocated
  as soon as the device type is known.
  If this LUNAME at OPEN ACB is not active in
  VTAM, The OPEN fails. The LUNAME gets varied
  inactive at this time, but the LUNAME is left
  in the CVB for the connection due to the
  client knowing the LUNAME. If the client
  enters a new application, OPEN ACB will fail
  again. When this occurs, the connection will
  be dropped with the 2044 error code. This is to
  prevent a loop with a screen scraper running.
  
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

APAR Information

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

  PQ76650

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

  UQ80440

Modules/Macros

• EZAZMTNS EZBTTCLS EZBTVOPN EZBTZDB2 EZBTZMSG
  EZBZTDBG
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R150 PSY UQ80440

     UP03/10/22 P F310

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.