Archives of the TeradataForum

Message Posted: Tue, 24 Apr 2007 @ 22:27:42 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

It is a trick question. I would expect that if you set up priority scheduler yourself, you would probably end up with 10 performance groups ( and 10 PG ids). However, if you are using TASM to set up priority scheduler, my guess would be that you will end up with 13 (or more) performance groups. In either scenario you will probably have more than one PG mapped to the same AG.

I am only guessing what is most likely. You could, of course, do it differently. Here, let me show you....

How I set up PSF:

     C:\Documents and Settings\Administrator>schmon -c
     rem SCHMON commands generated from Running PDE Version: 06.02.00.15

     rem       Priority Scheduler Times & Attributes
     rem Age_Time Active_Time Dispatch_Age
     schmon -t   60   61   0
     rem System Limit
     schmon -l none

     rem       Resource Partitions
     schmon -b  0 Default              25    none
     schmon -b  1 RP1                  75    none

     rem       Allocation Groups
     schmon -a   1 N      5 none
     schmon -a   2 N     10 none
     schmon -a   3 N     20 none
     schmon -a   4 N     40 none
     schmon -a   5 N      5 none
     schmon -a   6 N     10 none
     schmon -a   7 N     20 none
     schmon -a   8 N     40 none

     rem       Performance Groups
     schmon -p  0 L   0  S         0.00   1
     schmon -p  1 M   0  S         0.00   2
     schmon -p  2 H   0  S         0.00   3
     schmon -p  3 R   0  S         0.00   4
     schmon -p  4 L0  0  S         0.00   1
     schmon -p  5 M0  0  S         0.00   2
     schmon -p  6 H0  0  S         0.00   3
     schmon -p  7 L1  1  S         0.00   5
     schmon -p  8 M1  1  S         0.00   6
     schmon -p  9 H1  1  S         0.00   7

     rem       AWT Expedited work type limits (reserve maximum)
     schmon -w    0    80

How TASM set up PSF:

     C:\Documents and Settings\Administrator>schmon -c
     rem SCHMON commands generated from Running PDE Version: 06.02.00.15

     rem       Priority Scheduler Times & Attributes
     rem Age_Time Active_Time Dispatch_Age
     schmon -t   60   61   0
     rem System Limit
     schmon -l none

     rem       Resource Partitions
     schmon -b  0 DEFAULT              20    none
     schmon -b  1 TACTICAL             60    none
     schmon -b  2 STANDARD             20    none

     rem       Allocation Groups
     schmon -a   1 N      5 none
     schmon -a   2 N     10 none
     schmon -a   3 N     20 none
     schmon -a   4 N     40 none
     schmon -a   5 N     40 none
     schmon -a   6 N     20 none
     schmon -a   7 N     10 none
     schmon -a   8 N     20 none

     rem       Performance Groups
     schmon -p  0 L       0  S         0.00   1
     schmon -p  1 M       0  S         0.00   2
     schmon -p  2 H       0  S         0.00   3
     schmon -p  3 R       0  S         0.00   4
     schmon -p  4 PGWL8   2  S         0.00   6
     schmon -p  5 PGWL7   2  S         0.00   6
     schmon -p  6 PGWL5   2  S         0.00   6
     schmon -p  7 PGWL9   2  S         0.00   6
     schmon -p  8 PGWL6   2  S         0.00   6
     schmon -p  9 PGWL4   2  S         0.00   6
     schmon -p 10 PGWL2   2  S         0.00   6
     schmon -p 11 PGWL3   2  S         0.00   6
     schmon -p 12 PGWL10  1  S         0.00   8
     schmon -p 13 PGWL1   2  S         0.00   6

     rem       AWT Expedited work type limits (reserve maximum)
     schmon -w    0    80

By the way, I am glad to see that you are using workgroup names in the account strings. Here's a tip: You probably want to make the workgroup names shorter to keep the fully expanded strings at 30 characters or less.

	<Prev	Next>		<<First	<Prev	Next>	Last>>