PN85558: TCPIP AND ITS SERVERS USING MVPMAIN END NORMALLY (COND CODE = 0) WHEN AN ABEND OCCURS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When TCPIP or any of its servers that use MVPMAIN, encounters
  an abend, message " IEF142I name name STEP WAS EXECUTED -
  COND CODE 0000 ", is issued.
  This prevents operators or automation from detecting that a
  problem has occurred.  When a S0C4 happens, customer expects
  the STC to end with a S0C4 abend.
    According to the above message, the cond code is picked up
  from the value in return code in reg 15.  Reg 15 does contain
  x'000C4000' upon exiting MVPMAIN.  However, as described in
  MVS/ESA JCL REFERENCE MANUAL under the EXEC statement (Sub -
  parameter definitions), the code must be a value between
  0 and 4095 (x'0'- x'FFF').  Anything greater than d'4095'
  results in invalid Return Code testing or invalid return code
  in messages.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of TCP/IP for MVS; Platform        *
  *                 (MVPMAIN).                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Job step return code is '0000' when an  *
  *                      abend occurs.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A subtask of MVPMAIN abended with an 0C4. MVPMAIN exited to MVS
  with a return code (RC) of 802816 (X'000C4000'). Because a valid
  RC is zero thru 4095, some components saw an rc of zero. This
  customers job monitor saw a RC of 0000 and assumed there was no
  problem.
  
  If a subtask (TCPIP/CLIENT/SERVER) abends, MVPATT's ECB gets
  posted with the abend code in positions 8 thru 18 of the ECB.
  MVPATT passes the ECB value to MVPMAIN, who passes it to MVS.
  
  Additional Keywords: ABEND0C4 ABENDS0C4 S0C4
  

Problem conclusion

• MVPATT (EZACA00G) has been changed to recognize this situation
  and set the return code to decimal 200.
  
  Page 1258, Appendix A. "TCP/IP Codes", of the TCP/IP for MVS
  Version 3 Release 1 Messages and Codes (SC31-7132-00) manual
  should be have the following completion code added:
  
     -------------------------------------------------------------
     200
  
     Explanation: A subtask of MVPMAIN abended.
  
     System Action: The system ends the task.
  
     User or Operator Response: Tell the system programmer about
     the error.
  
     System Programmer Response: Check the job log to identify the
     failing task. Use the dump from the abend to determine the
     cause of the failure in the subtask (please refer to the
     MVS/ESA SP V5 Diagnosis: Procedures manual for more
     information about debuging abends).
  
     Source Data Set: MVPMAIN
  
     Procedure Name: Mainline code
     -------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

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

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

  UN93691 PN88976

Modules/Macros

• EZACA00G
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R310 PSY UN93691

     UP96/08/19 P F608

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.