PH03970: S0C7 ABEND IN IAYLSTNR MAINFRAME LISTENER - ENDEVOR SHOP

APAR status

• Closed as fixed if next.

Error description

• IBM Application Discovery Connect for Mainframe v5.0.3.*
  v5.0.4.*
  When a non-AD client (unauthorized or accidental) makes a
  connection to the AD listener on z/OS, the client can
  potentially send a stream of bytes that form an invalid request
  and cause the listening task to abend on S0C7.
  The task recovers and the listener continues to function, but
  the abends can be disruptive and waste system resources.
  
  This fix will screen out such instances and prevent the S0C7
  abend.
  

Local fix

• N/A
  

Problem summary

• When an AD Build Client first connects, the AD connector expects
  the first 3 bytes in the data stream to be a valid numeric
  value representing the number of segments that make up the
  incoming request.  In this case, a non-AD client was connecting
  to the AD agent, and sending a stream of bytes that was not a
  valid AD message.  The segment count check failed since the
  first 3 bytes were not valid numeric, and the CVB instruction
  failed on S0C7.  The fix was to add a check on the first 3 bytes
  to filter out any invalid requests before attempting to perform
  the CVB instruction.
  

Problem conclusion

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:

Fix information

Applicable component levels