AMPX036I Assertion Failure Checking Error Starting OSD Device

 
 APAR Identifier ...... PQ75472      Last Changed ........ 04/01/20
 AMPX036I ASSERTION FAILURE CHECKING ERROR STARTING OSD DEVICE
 
 Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
 Severity ................... 3      Date Closed ......... 04/01/20
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 3A0      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 430   : PTF not available yet
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 OSD devices intermittently fail to initialize to a READY state.
 The z/VM TCPIP server console shows the following Pascal
 assertion error when this condition is detected:
 
 AMPX036I ASSERTION FAILURE CHECKING ERROR
       TRACE BACK OF CALLED ROUTINES
  ROUTINE                          STMT AT ADDRESS IN MODULE
  STARTOSDWRITE                       3    00C5F640   TCTOOSD_TOO
  SENDIPREQUEST                      37    00C62226   TCTOOSD_TOO
  INITSETIP                           2    00C6206C   TCTOOSD_TOO
  PROCESSREADINT                     95    00C60806   TCTOOSD_TOO
  TOOSD                              77    00C64EBC   TCTOOSD_TOO
  SCHEDULER                         128    00BD97DC   TCSCHED_SCH
  <MAIN-PROGRAM>                     22    00B43284   TCPIP
  VSPASCAL                                 00CCCFC2
 
 LOCAL FIX:
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: All TCP/IP users of OSA-Express OSD devices  *
 ****************************************************************
 * PROBLEM DESCRIPTION:                                         *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 The OSD device driver expects that interrupts for READ and WRITE
 control responses will come back in the same order that the
 requests were sent out.  If this is not the case, an assertion
 failure can occur or a response is lost.
 
 PROBLEM CONCLUSION:
 The OSD device driver was updated to support responses for
 READ and WRITE control requests coming in any order.  Requests
 will be queued with a sequence number and responses will be
 matched up to the sequence number when the response arrives.
 In addition, the StartLAN and Query IP Assist requests were
 changed to use the OSD scheduler (rather than being "stand
 alone" requests issued during initialization).
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:   ALLMACRO MSTCP    TCBASTY  TCIPUP   TCMPCOCO
 TCPEQUAT TCPIP    TCPOCO   TCPRINT  TCTOOSD
 
 SRLS:      NONE
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: