RE: System slow

Sometimes a client will not perform a commit often enough and take up huge amounts of CPU with pending database changes.

Use DSPJOB with OPTION(*OPNF) to list the tables used by your QZDASOINIT and QRWTSRVR jobs. Any that have a large number of recurring open files are suspects to investigate.

HTH

Gary

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Tuesday, May 28, 2013 10:05 AM
To: midrange-l@xxxxxxxxxxxx
Subject: System slow


Hi Folks, for about 10 mins today our i went into slowdown mode with CPU in the high 90% (which is fairly frequently from time to time) and our MQ jobs went into MTXW and some applications were stalled or hung, our legasuite app for one. No interactive sessions were knocked off or ended and no errors for controllers were shown on qsysopr during this 10 min period. Qsysopr shows only a few jobs running during the 10 min period and those jobs are rountinely run during the day.

As the network folks wonder what's wrong with the i and my boss too...I say the issue may be the network and I'm not totally sure about that but this type of issue has happened b4 where the i is slow then all of a sudden we're back to normal.

Is there anything that I can do to prove that the issue was not on the i?

Is there anything in the performance reports that could help me figure out what happened?

What's the strategy that you folks would employ in this situation?

Thanks, Frank
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.