Re: JDE Green Screen and system values QPRCMLTTSK and QQRYDEGREE

World is the green screen edition of JDE.

What you'll find is that the apps themselves are basically single-threaded
and that enabling multiprocessor support won't speed up individual jobs.
That said, when the jobs do database or query work that extra processor
capability will kick in. You can safely crank up the system values; you
won't have any problems.

Where multiple CPUs helps JDE the most is in allowing you to run more jobs
concurrently. Open up QBATCH to run more concurrent jobs. But leave the
Post and FASTR job queues single threaded; Post because you can mess things
up if multiple posting jobs run concurrently and FASTRs because multiple
FASTRs for the same user can cause record locking and slow the jobs down
instead of speeding them up. (You can run FASTRs from different users
concurrently with no problems, but generally people don't manage World
workloads to that granularity.)

The rule of thumb for World is that more CPUs = more concurrent jobs;
faster CPUs = shorter job run times. Both more& faster CPUs help, but
they affect performance in different ways. And "faster" CPUs should be
determined by CPW/CPU, not CPU clock speed.

On Tue, Nov 13, 2012 at 6:18 PM, Jim Oberholtzer<
midrangel@xxxxxxxxxxxxxxxxx> wrote:

> Do any of you folks running JDE green screen version (I forget if it's
> World or OneWorld) know of a reason why QPRCMLTTSK (Processor Multi
> Tasking) or QQRYDEGREE (Query Processing degree) should be set:
>
> QPRCMLTTSK: Off
> QQRYDEGREE: *NONE.
>
> I would have thought turning on multitasking (9406-825 with all four
> processors turned on) and setting query degree to *OPTIMIZE would be
> good things.
>
> The customer has them turned off and before we turn them on and learn
> the hard way that was a bad idea, I thought I would ask your thoughts....
>
> --
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
> --