You must set PDQPRIORITY, MAXPDQPRIORITY, DSSMAXSCANS and DSSMAXQUERIES(I
forget the exact VAR names) in $ONCONFIG. The PDQPRIORITY in the $ONCONFIG
will set a default if you do not want to put SET PDQPRIORITY in your code. If
there are multiple users I would keep MAXPDQPRIORITY very low( >= 10) and
PDQPRIORITY lower. This number represents a percentage of the resources.
(eg. if ten active sessions with PDQPRIORITY = 10 are running any other
sessions will have to wait there turn. Which may or may not be a long wait.)
You will also be able to monitor multiple threads with onstat -u, there will
be multiple entries with the same session ID.
Matt Bentley
mbentley@xmission.com
www.xmission.com/~advantag "Look for homes on the WWW"
In article <316BB89A.167E@eos.ap.org>,
"Rajesh N. Malhotra" <malhotra@eos.ap.org> wrote:
>Informix Gurus,
>
> I have fragmented a few tables in our schema, and have updated
>statistics on those tables. I set the PSORT_NPROCS variable in the
>onconfig to the largest level of fragmentation (10).
>
> Now when I run queries on the fragmented tables, and monitor them
using
>
> onstat -g ses <ses#>>
>the #RSAM THREADS is always 1. Inspite of fragmentation, I cannot use
>the multi threaded architecture of the Online engine.
>
> We are running Online 7.11.UC1 on an IBM RS6000 running AIX 4.1.4. Any
>help on this matter appreciated.
>
>Thanx,
>
>Raj.