QZDASOINIT prestart jobs service JDBC requests. When running, they tend
to "grab" a lot of CPU cycles. I assume IBM designed it this way.
Because of this, my Java applications typically get blamed for causing
poor overall system performance (even for interactive jobs).
Is SQL (Java or RPG) more processor intensive than direct file access
via RPG? If so, does anyone know of any guidelines for "up-sizing" the
iSeries box as legacy RPG applications get converted to Java or RPG with
SQL file I/O?
Also, can the QZDASOINIT jobs cause performance problems for Interactive
jobs? I've always thought that they would NOT effect interactive jobs
because of the "Interactive Card Tax" that supposedly isolates x CPW
just for interactive jobs (Batch jobs can't use it... right??).
Any links or advice would be appreciated.