|
Thank you all for your prompt help, I'm extremely sorry for the delay in response I've been trying many things & talking to many people & didn't want to put anything up until we have an answer, I tried all of your good ideas but alas it wasn't solved. I think the 'Function Sequence Error' was a red herring, it was thrown a little while after the looping started & was a consequence of it & not it's cause. We (including IBM) now believe we have fixed the problem which appears to be network related. We have a 2839 Ethernet card on the iSeries that IBM says is known to have problems if it's configured differently from the switch/hub, they both have to be auto-negotiate or fixed config. After looking into the logs we found many errors with the card which would have upset TCP/IP on the iSeries. When we ended TCP while Websphere was running the SERVER1 job went into a loop which is what could have happened while getting the many TCP errors. The strange thing was that Websphere reported no errors or problems, it just started eating up processor, we re-created it 3 times on 2 different machine by stopping TCP when Websphere was running & SERVER1 looped every time. We have fixed the 2839 configuration to hopefully stop it happening again. We won't know for a week or so but everyone is confident this will stop it happening again.... fingers crossed!! Thanks again.... Andy. -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.