JnextPlan is slow
You find that JnextPlan is unacceptably slow.
Cause and solution:
There are three possible causes for this problem:
- Tracing too much
- One possible cause is the tracing facility. It could be that it is providing too much trace information. Reduce the number of processes that the tracing facility is monitoring. See Quick reference: how to modify log and trace levels for full details.
- Application server tracing too much
-
Another possible cause is that the application server tracing is set to high. See Log and trace files for the application server for more details about the trace and how to reset it.
- Database needs reorganizing
-
Another possible cause is that the database needs reorganizing. See "Reorganizing the database" in IBM® Workload Scheduler: Administration Guide for a description of how and why you reorganize the database, logically and physically.