MPROUTE Routing Table Not Updated When OSD Link is Started

 
 APAR Identifier ...... PQ53969      Last Changed ........ 01/11/15
 MPROUTE ROUTING TABLE NOT UPDATED WHEN OSD LINK IS STARTED
 
 Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
 Severity ................... 3      Date Closed ......... 01/11/15
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 410      Fixed Release ............ 999
 Component Name TCP/IP V2 FOR V      Special Notice
 Current Target Date ..              Flags
 SCP ...................
 Platform ............
 
 Status Detail: APARCLOSURE - APAR is being closed.
 
 PE PTF List:
 
 PTF List:
 Release 3A0   : PTF not available yet
 Release 410   : PTF not available yet
 Release 420   : PTF not available yet
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 The VM TCP/IP host is first initialized, after which the OSD
 device is started via an OBEYFILE. In this sequence of event,
 MPRoute is not notified of its status change, therefore no
 network connectivity is possible.
 Recycling the VM MPRoute server machine after the device is
 started circumvents the problem.
 
 LOCAL FIX:
 MT02925
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: All users of MPRoute that are using OSD      *
 *                 devices.                                     *
 ****************************************************************
 * PROBLEM DESCRIPTION: Status changes are not being reflected  *
 *                      to MPRoute for OSD devices that are     *
 *                      started after the MPRoute server is     *
 *                      initialized.                            *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 When a device changes status, a call to procedure
 LinkStateChange in routine TCMIB must be made.  It is within
 this routine that the determination is made to send
 information to the MPRoute server about the status change.
 TCTOOSD did not make a call to the LinkStateChange routine
 when the device status changed to InitComplete, therefore no
 information was sent to the MPRoute server about the device.
 
 PROBLEM CONCLUSION:
 TCTOOSD has been modified to call OsdLinkStateChange (which in
 turn calls LinkStateChange in TCMIB) when the device changes
 status to InitComplete.  There were also a couple of places in
 TCTOOSD where the call to OsdLinkStateChange was made after the
 device status had been changed.  When this is done, the
 information about the previous status is lost and
 LinkStateChange can no longer detect a change in status.  These
 calls have been moved in front of the code that actually
 changes the device status.
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:   TCPIP    TCTOOSD
 
 SRLS:      NONE
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: