PM42682: PACKET TRACE FORMATTER DOES NOT SHOW THE CORRECT FINAL STATE.

APAR status

• Closed as fixed if next.

Error description

• Packet trace formatter is not showing the correct final state
  for some connections:
  
  Host:                                 Local,          Remote
  
   Client or Server:                   SERVER,          CLIENT
   Port:                                33745,           10132
  
  Connection:
   First timestamp:                 2011/06/23 07:51:48.760389
   Last timestamp:                  2011/06/23 07:51:48.846524
   Duration:                                   00:00:00.086135
   Average Round-Trip-Time:                              0.001 sec
   Final Round-Trip-Time:                                0.011 sec
   Final state:                     FIN_WAIT_2 (PASSIVE CLOSE)
   Out-of-order timestamps:                                  0
  
  TcpHdr   IO F        Seq        Ack RcvWnd  Data Delta Time
  TimeStamp  RcdNr State
        S   I   2697578064          0   5808     0   0.000000
  07:51:48.760389 164048    SYN_RCVD
     A  S   O   1619256623 2697578065  32768     0   0.000073
  07:51:48.760462 164049    SYN_RCVD
     A      I u 2697578065 1619256624   5808     0   0.000472
  07:51:48.760934 164050 ESTABLISHED
     AP     I . 2697578065 1619256624   5808   175   0.000474
  07:51:48.761408 164051 ESTABLISHED
     AP     O + 1619256624 2697578240  32593   158   0.000388
  07:51:48.761796 164052 ESTABLISHED
     A      I a 2697578240 1619256782   6880     0   0.000483
  07:51:48.762279 164053 ESTABLISHED
     AP     I . 2697578240 1619256782   6880   267   0.000008
  07:51:48.762287 164054 ESTABLISHED
     AP     O + 1619256782 2697578507  32501   197   0.003268
  07:51:48.765555 164055 ESTABLISHED
     AP     I + 2697578507 1619256979   7952   470   0.001485
  07:51:48.767040 164056 ESTABLISHED
     AP     O + 1619256979 2697578977  32298   958   0.071004
  07:51:48.838044 164057 ESTABLISHED
     AP     I + 2697578977 1619257937   9868    10   0.006251
  07:51:48.844295 164066 ESTABLISHED
     AP     O + 1619257937 2697578987  32758    54   0.000202
  07:51:48.844497 164067 ESTABLISHED
     AP     I + 2697578987 1619257991   9868    10   0.001028
  07:51:48.845525 164068 ESTABLISHED
     AP     O + 1619257991 2697578997  32758    54   0.000049
  07:51:48.845574 164069 ESTABLISHED
     A   F  I a 2697578997 1619258045   9868     0   0.000456
  07:51:48.846030 164070 ESTABLISHED
     AP  F  O a 1619258045 2697578998  32758     0   0.000154
  07:51:48.846184 164071  FIN_WAIT_1
     A      I a 2697578998 1619258046   9868     0   0.000340
  07:51:48.846524 164072  FIN_WAIT_2
  
     Based on the flow here, the final state should be LAST_ACK
     (PASSIVE CLOSE) instead of FIN_WAIT_2 (PASSIVE CLOSE).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 10, 11, 12 and *
  *                 13 IP: Packet Trace                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Packet trace formatter does not show    *
  *                      the correct closing and final states.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem may be described as follows:
    1. User collected the packet trace data for the TCP
       connection.
    2. User issued CTRACE command to format the packet traces.
    3. EZBPTTCP received control to determine the TCP session
       states from the trace data. It determined the incorrect
       TCP session closing states.
  
  +-------------------------------------------------------------+
  + 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

Temporary fix

Comments

• 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.
  
  The solution for this APAR is included in
  CS for zOS Version 2 Release 1.
  

APAR Information

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

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

Modules/Macros

• EZBPTTCP
  

Fix information

Applicable component levels

• R1D0 PSY

     UP