RE: Strange DASD Utilization Issue

 
It will optimize Query and SQL tasks.  Best is to read the help text on the
sysval.  I think you will be OK at v5r2, my problems with it were a long
time ago.  I would start with *IO and just see if you think your runs are
faster.  The higher level options take more overhead and require multiple
processors (SMP).

I should probably say what my problem was.  When QQRYDEGREE was set to
*OPTIMIZE or *MAX (I don't remember which) an SQL job would generate an
excessive number (thousands) of jobs/threads and the run would actually be
much slower to complete.  This was back on an 840 8-way.  I did talk with
Support Line when it was going on and can't remember a solution other than
to drop back to the *IO setting.  Since I have not heard of this since it
has likely be repaired over the years.

--
Doug Hart
 
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chuck Lewis
Sent: Wednesday, March 01, 2006 10:57 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Strange DASD Utilization Issue

Doug,

What does that do/impact ?

Ours is set to *NONE. We are V5R2

Thanks !

Chuck

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Doug Hart
Sent: Monday, February 27, 2006 6:51 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Strange DASD Utilization Issue

 
You did not state what OS version you are on but older versions had problems
with SQL temp indexes.
Check your system value QQRYDEGREE and only use the parm value *IO not
*OPTIMIZE or *MAX.