MULTIPLE VIPA DEFINITIONS NOT WORKING ON RELEASE 6.4.0

 
 APAR Identifier ...... PI79288      Last Changed ........ 17/04/06
 MULTIPLE VIPA DEFINITIONS NOT WORKING ON RELEASE 6.4.0
 
 Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
 Severity ................... 3      Date Closed ......... 17/04/04
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 640      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 640   : UI46169 available 17/04/06 (1000 )
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 As of release 6.4.0, a TCP/IP configuration that has multiple
 VIPA device definitions will only allow the first VIPA interface
 to come online.  Subsequent VIPA devices fail with:
   DTCPAR123I Line xxx: Overlapping device address ranges for
 devices <dev1> and <dev2> specified
 
 LOCAL FIX:
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: All users of z/VM TCP/IP                     *
 ****************************************************************
 * PROBLEM DESCRIPTION:                                         *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 Configuring devices with device addresses very close together
 does not appropriately detect when the address ranges needed for
 those devices overlap.  This can manifest itself in two ways:
   - Device ranges which do overlap do not cause an error when
     they should.  For example, two OSAs can be configured
     devices with the same device address in the PROFILE TCPIP.
     The parser will deem this valid and the devices will
     attempt to initialize (at which point, one of them will
     receive an error).
   - Devices that require no virtual device addresses may
     incorrectly be reported as being overlapping.  This
     is most likely encountered with multiple VIPA devices
     being defined, at which point the following error will
     occur:
       DTCPAR123I Line xxx: Overlapping device address ranges
                  for devices <dev1> and <dev2> specified.
 
 PROBLEM CONCLUSION:
 Code has been updated to correctly determine the number of
 device addresses required for the interfaces being configured in
 the stack.
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:
 TCPARSE
 
 SRLS:
 NONE
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: