RE: CPU usage for QZDASOINIT

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>Ok, so if the RSP column is all 0.X
>it isn't that big of a deal?

It depends <grin>

Basically, my performance evaluations run along the lines of "If my CSR has
consistent sub second response time when she's on the phone with a customer,
then performance is good."  In my corner of the world, the iSeries' main job
is to supply 5250 interface programs to the end-user.  If customer service
is slow, then  we will take measures to see that it gets faster.

That means that batch processes like batch reports and so on can take as
much CPU% as they want as long as the interactive users don't notice.  The
RISC boxes seem to do this better than the CISC boxes did (just a gut
feeling; no hard facts.)

In your particular instance, you have a batch process (a conversion), so in
my view, it doesn't matter the CPU% used by this process as long as your
interactive doesn't suffer.

That answers the original question (I think) "Should it be running this hard
for a simple select/where statement?"

The new question "I was just curious if this time of response was normal for
the type of situation." is a bit different.  Here, Walden's advice is good:
Create an index that supports your query.  You can find out what indexes to
create by STRDBG UPDPROD(*YES), STRSQL, paste in the query, exit STRSQL,
ENDDBG and look at the job log.

I can't lay my hands on the manual that helps with SQL performance, but
that's a good bet.
  --buck