PN80284: ABEND S0C4 IN MODULE MVPDG7D OFFSET +920

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During normal operation TCPIP MVS ABENDs
  with code S0C4.  Abend PSW is in module
  MVPDG7D at offset +920
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TCP/IP 3.1 TELNET users who code         *
  *                 LUSESSIONPEND in their TCPIP profile.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: During normal operation, TCPIP ABENDs   *
  *                      with code S0C4.  AbEND PSW is in        *
  *                      module MVPDG7D at offset +920.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The ABEND0C4 occurs because a terminate has come in from the
  client at almost the same time as the initiate is being
  redriven due to LUSESSIONPEND.
  
  The ABEND0C4 could occur at other places in
  MVPDG7D because it is timing related.  The problem is that the
  terminate and (re)-initiate for the session are not
  synchronized.  MVPDG7C processing the terminate (Fterm) runs
  on one TCB and MVPDG7D processing the (re)initiate due to
  LUSESSIONPEND (FInit) runs on a separate TCB.  This process
  needs to be synchronized.
  

Problem conclusion

• EZACA01D (MVPDG7C) and EZACA01E (MVPDG7D) will synchronize the
  terminate by delaying it, if LUSESSIONPEND on for the connection
  MVPDG7C (Fterm) will delay the terminate by queuing an FTERM
  DELAY to MVP (VTRQ with 'FF'X Terminate_RC).  When the FTERM
  DELAY is processed in EZACA03S (MVPVTWK), it will queue the
  terminate to VTAM at that point, which will ensure that the
  initiate is processed prior to the terminate.
  
  In addition, EZACA01E (MVPDG7D) in Finit will not reload
  the MSG10 table, if it is already loaded, since we
  are processing an initiate due to LUSESSIONPEND.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

• REPINNED RP96/05/14To indicate Hiper status nmb.
  
  ×**** PE96/08/16 FIX IN ERROR. SEE APAR PN87428  FOR DESCRIPTION
  

APAR Information

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

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

  UN89622

Modules/Macros

• EZACA01D EZACA01E EZACA03S
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R310 PSY UN89622

     UP96/05/09 P F605 Ž

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.