Shoot, not logging that, and cannot reproduce on my dev systems, so to find out will have to re-build, ship to customer, wait for test ...
Will start that in motion, but meanwhile, what would you be looking for? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Kirk Wolf Sent: Friday, September 7, 2018 6:39 AM To: [email protected] Subject: Re: Unexpected UDP sendto() errors on z/OS V2R3 What __errno2() are you getting? (reason code) On Thu, Sep 6, 2018 at 3:03 PM Charles Mills <[email protected]> wrote: > I've got code that has been running unmodified "forever." It does a UDP > sendto(). Those of you familiar with UDP know that the good news with UDP > is > that you never get errors; the bad news is that you never get errors. > > > > Suddenly, at two customers we are seeing EIO or 122 from sendto(). EIO has > one of those generic "an I/O error occurred" descriptions. The common > thread > is they are both V2R3. > > > > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ce > ea900/cs00228.htm > <https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ceea900/cs00228.htm> > > > > Is anyone else seeing anything like this? Anyone have any insights? > > > > Thanks, > > > > Charles > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
