Im still not sure what actual performance problem your seeing, beyond
'performance problems'.
As others have mentioned, I think the best thing to do here is to use the
database monitors to see what queries are being run, and determine if any
logicals/indexes need to be created to help, and also tune the max reuse
parameter on the database server jobs.
Also while the app is running, have a look in QUSRWRK and which jobs are
using CPU. It might well be that particular functions in the app are doing
silly things and need slight changes
Beyond that all you can do is go back to the vendor
As an Amazon Associate we earn from qualifying purchases.
This thread ...
- RE: SQL stored procedures and activation groups via JDBC, (continued)