Some of you asked for updates. Update: the problem has reappeared after a while in the "version 1.3" code.
I got a packet trace and it seems to me to show everything exactly as I would expect. I have told the customer that it may be our problem but someone on the network side or in IBM is going to have to look at the packet trace and tell me what we're doing wrong. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Wednesday, March 20, 2013 2:27 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Lost datagrams on z/OS 1.12? And the answer is ... that I am not a very happy camper here. I sent "version 1.3" off to the customer. The only changes are diagnostic, not "functional." And guess what -- the problem has gone away. So either - the customer is confused and/or was also making firewall or router changes at the same time. I don't think that is the case. - moving variables around has obscured the problem. That's the one that worries me. Very little variable movement so hopefully not. - perhaps compiler/library maintenance? Thank you Lloyd I am looking into that. Not much time between versions. "Version 1.2" was compiled on Feb. 25 and "Version 1.3" yesterday. Otherwise I just don't know. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Wednesday, March 20, 2013 8:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Lost datagrams on z/OS 1.12? Thanks all. Filling in some gaps and answering some questions. I've added additional trace code within the product to make certain that the socket, sockaddr, and record length are as expected. (I already know that the sendto() is getting issued with the correct record.) I changed the error check from if ( returnvalue < length ) to if (returnvalue != length ) to help avoid any possibility of signed/unsigned or similar issues. Running a test at the customer today with a packet trace also. Environment is z/OS started task. Source language is IBM XL C++. Record length varies but is typically a few hundred bytes and never exceeds 1024 bytes. Ditto for the old version that works, so maximum datagram and MTU size issues seem unlikely. Don't know any of the customer's TCP/IP configuration but the message traffic should be 99.9% the same for both versions -- they are in theory both sending the same "stuff." ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
