In a message dated 6/26/2008 12:14:42 P.M. Central Daylight Time, [EMAIL PROTECTED] writes:
Personally, I'd also look at ways to avoid JNUM > 90% and to increase the total number of jobs that can be in the system at any given time. Can you tell us your settings that control JNUM? Can you increase those values, without exceeding maximums (or third- party software limitations on job numbers, ranges, format of JOBID, etc)? That's where I'd start looking at to solve this issue. >> Well guess a good place to start would be offloading the SMTP services to another machine or using UDP(Lionel's got a good write up in his XMITIP gem at _www.lbdsoftware.com_ (http://www.lbdsoftware.com) ). For DB/2 have to watch threads like a hawk. When they spill over to the common pool big time bottlenecks(hangs) while it thrashes it out with everything else. Then there's just bad SQL. What's his name(Platinum) quotes 70% for performance problems. **************Gas prices getting you down? Search AOL Autos for fuel-efficient used cars. (http://autos.aol.com/used?ncid=aolaut00050000000007) ---------------------------------------------------------------------- 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
