Very likely this is the result of not enough memory in *BASE. The assumption here is that all of the host servers are still running in QUSRWRK and/or QSYSWRK and no work management has been done to tune the memory pools, and push all activity out of *BASE except base system jobs.

You might want to check WRKSYSSTS to see if *BASE and *MACHINE pools are faulting and paging quite a bit. Note that even if they are, normal character based application usually continue to run within reason. Any remote SQL access regardless of the type is likely to be slow as well.

If the jobs have been moved out of QUSRWRK/QSYSWRK (a good thing!) then the memory pool they are running in is most likely in stress as well.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 7/17/2012 11:40 PM, Jason wrote:
Hi,

Is anyone else experiencing performance issues with iSeries Navigator 7.1 and
very slow performance to display database tables? Sometimes the tables won’t
finish
loading unless I constantly use the scroll bar and can take up to 20 mins to
display.
I’m running V7R1 with latest PTF’s installed and latest SP (SI45664) of
navigator and have tried all the performance tips from IBM but still no luck.
Any ideas on what could be the issue or where I should investigate further?

Jason

--

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.