API call fails synchronously

An asynchronous API call might fail synchronously or asynchronously. In this example, the WRITE call error was detected in the synchronous processing, so general-purpose register 15 has a nonzero value. The ERRNO value is interpreted (in this case, the NBYTE parameter on the WRITE call had a value of zero, which is not acceptable).

Note: The ERRNO value is the TCP/IP Sockets Extended Return Code. See z/OS Communications Server: IP and SNA Codes for information about TCP/IP Sockets Extended Return Codes.

====================================================================00007B93   
 MVS026    SOCKAPI   60050057  19:27:13.817195   WRITE Exit                    
HASID....0027     PASID....0027     SASID..0027     JOBNAME..EZASOKOS          
TCB......006E6A68 TIE......00006DF8 PLIST..00006E0C DUCB.....00000009 KEY..8  
ADSNAME..EZASOKOS SUBTASK..00000000 00000000        TOKEN....7F6F3798 09902FB0 
LOCAL  PORT..11007      IPADDR.. 9.67.113.58                              
REMOTE PORT..1031       IPADDR.. 9.67.113.58                              
 REQAREA..:  00006D90x                                          Addr..00006D90 
 SOCKET...:  1                                                  Addr..00006BDC 
 R15......:  NON-ZERO (CALL WAS NOT ACCEPTED)                                  
 ERRNO....:  10184 (EIBMWRITELENZERO)                           Addr..00006EB0 
 RETCODE..:  -1                                                 Addr..00006EB4