do you have bad performance for all kind of transactions of PowerLink? Or maybe some particular views or transactions are slow?
My experience is that database access can make the fastest machines very slow. The advantage of PowerLink is the flexibility to change views, cards, sorts and subsets. Sometimes this turns into a disadvantage if the generated SQL takes too much time. For this Infor has build the Debug-Options in PowerLink. This is a easy way to find and fix bottlenecks in the database access.
If there is only a problem in particular situations and you are able to reproduce this scenario it would be a good idea to run the PowerLink-Client in Debug-Mode to trace the DatabaseConnection.
If you cannot reproduce the problem the Index Advisor (see IBM i Navigator) would be the best way to find problems. Take a look at the recommended indexes for your AMFLIBx and AMCESSQL. Some of our customers had a bad performance with new machines and new client hardware. Building the cards took a few seconds each time. We found that there were temporary indexes build to access data each time the opened a particular view or card. We could analyze these activities and created own indexes (SQL: CREATE INDEX…) and then the system was very fast.
If you need some more information about DebugMode and/or IndexAdvisor please let me know.
And: what is your PCM-level? Infor provided some PTFs to get better performance. See inforXtreme KnowledgeBase. Maybe this will help you.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.