AMPX036I Error Message Loop


 
 APAR Identifier ...... PQ61892      Last Changed ........ 02/07/11
 AMPX036I ERROR MESSAGE LOOP
 
 Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
 Severity ................... 3      Date Closed ......... 02/07/08
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 430      Fixed Release ............ 999
 Component Name TCP/IP V2 FOR V      Special Notice
 Current Target Date ..              Flags
 SCP ...................
 Platform ............
 
 Status Detail: SHIPMENT - Packaged solution is available for
                           shipment.
 
 PE PTF List:
 
 PTF List:
 Release 430   : UQ67888 available 02/07/11 (1000 )
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 Intermittant Assertions errors:
 AMPX036I ASSERTION FAILURE CHECKING ERROR
       TRACE BACK OF CALLED ROUTINES
 ROUTINE                          STMT AT ADDRESS IN MODULE
 TREEDELETENODE                     56    00E2AC08   TCTREEP
 DOMPRIOCTL                        178    00CE72FC   TCIPDOW_IPDO
 DOIOCTL                            55    00E1C9D6   SOCKREQUEST
 PROCESSPENDMSG                    196    00E1E1E0   SOCKREQUEST
 SOCKREQUEST                        18    00E1F0A2   SOCKREQUEST
 Schedule                                 00D543BE
 <MAIN-PROGRAM>                     14    00CBC1B0   TCPIP
 VSPASCAL                                 00E533E2
 
 LOCAL FIX:
 Additional Symptoms:
 PITS MT03201
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: All z/VM TCP/IP users.                       *
 ****************************************************************
 * PROBLEM DESCRIPTION: AMPX036I ASSERTION FAILURE CHECKING     *
 *                      ERROR in TreeDeleteNode in TCTREEP.     *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 Routine TreeInsertMatch (in TCTREEP) had two problems. Host
 route subnetmasks were not handled properly, and the node
 field TreeNodeUpwardFromRight was not initialized.  When a new
 node is acquired, sometimes TreeNodeUpwardFromRight was already
 set to TRUE when we expected it to be FALSE.  If that condition
 occurs, our routing tree is incorrect, and assertion errors
 occur.
 
 PROBLEM CONCLUSION:
 The field TreeNodeUpwardFromRight is now initialized in
 TreeInsertMatch.  In addition, the routine was changed to
 correctly handle host routes subnetmasks.
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:   TCPIP    TCTREEP
 
 SRLS:      NONE
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: