API call fails synchronously with diagnostic reason code

If the API call does not complete successfully, the return code, ERRNO value (in decimal and interpreted), and possibly a diagnostic reason code are shown. The first two bytes of the diagnostic reason code are a qualifier (IBM® internal use only). The last two bytes of the diagnostic reason codes are the UNIX ERRNOJR values described in z/OS Communications Server: IP and SNA Codes.

====================================================================000085C1   
 MVS026    SOCKAPI   60050004  19:36:01.934828   ACCEPT Exit                   
HASID....01F6     PASID....01F6     SASID..01F6     JOBNAME..EZASOKUE          
TCB......006E6A68 TIE......00006DF0 PLIST..00006E04 DUCB.....0000000D KEY..8  
ADSNAME..EZASOKUE SUBTASK..EZASOKUE                 TOKEN....7F6F3798 09902FB0 
LOCAL  PORT..11007     IPADDR ..9.67.113.58                              
REMOTE PORT..0         IPADDR ..0.0.0.0                                  
 REQAREA..:  00000000x                                          Addr..00006D80 
 SOCKET...:  0                                                  Addr..00006BA8 
 NAME.....:  (NO DATA)                                          Addr..00006BAC 
 DIAG. RSN:  76620291x                                                         
 ERRNO....:  5 (EIO)                                            Addr..00006EA8 
 RETCODE..:  -1                                                 Addr..00006EAC