We ran for some years before it bit us in the ass. And I couldn't really find any load related cause at that time. It seemed a random strike out of the blue.
So, I wouldn't count on reproducing the error in any controlled fashion :( -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Chase, John Sent: Friday, June 06, 2008 9:15 AM To: [email protected] Subject: Re: TCPIP Segmentation Offload > -----Original Message----- > From: IBM Mainframe Discussion List On Behalf Of Brian Peterson > > This morning, I checked the Exception Letters for our z9 and > z10 processors. > Both Exception Letters are dated May 28, 2008, and both still > say that Segmentation Offload needs to be disabled. > > I am not saying that IBM hasn't fixed the problem - I hope > they have. But, the Exception Letters still say the problem > is NOT fixed. Interesting.... They're dated three days LATER than the date we installed the latest ucode (that was supposed to fix the problem). We enabled SEGMENTATIONOFFLOAD on the sandbox (z/OS 1.9) yesterday, but there's very little TCPIP load on the sandbox (still doing IVP of 1.9, and post-installation "cleanup"). Maybe we can cobble up something that should "stress" it to the breaking point (maybe FTP-ing some SMF offload datasets or sysdumps?). Meanwhile, we'll leave it disabled on the other LPARs until we hear something more reassuring (or determine that we can't "break" it on the sandbox). -jc- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
