Server Performance Levels

You can specify different SPD Server performance-level parameters based on the performance class of the user or based on whether the user is assigned the SPD Server locking proxy specified by the LOCKING=YES LIBNAME option. Every SPD Server user in the SPD Server Password Table database is assigned a performance class attribute. For more information about user performance classes, see The Password Manager Utility psmgr. Each performance class can be associated with server parameters that use the performance class to control how user resources are allocated.

The SPD Server administrator enters users into the Password Manager database as either LOW, MEDIUM, or HIGH performance users. Low users get the LOW (or default) values that are specified in the spdsserv.parm file. Medium users inherit the LOW values plus any values redefined in the MED section of the spdsserv.parm file. High users inherit the LOW values plus any values redefined in the HIGH section of the spdsserv.parm file. LOCKING=YES is a special user class that is activated by a LOCKING=YES LIBNAME assignment for the user. LOCKING=YES users inherit the LOW values plus any values redefined in the LOCKING section of the spdsserv.parm file.

When used in the spdsserv.parm file, the following keywords associate a user with the performance-level parameter settings:

Consider the following example:

User Bob belongs to the low performance class. User Tom belongs to the medium performance level class. User Mary belongs to the high performance class. The system administrator wants to assign different server values to low, medium, and high users. The system administrator defines the following entities in the spdsserv.parm file:

SORTSIZE=256M;
BINBUFSIZE=32K;
MAXWHTHREADS=4;
WORKPATH="/var/tmp";
---MED---
SORTSIZE=512M;
MAXWHTHREADS=6;
---HIGH---
SORTSIZE=1G;
MAXWHTHREADS=6;
WORKPATH="/var/hightmp";

Using the spdsserv.parm file, all low users receive the initial LOW (default) values for SORTSIZE=, BINBUFSIZE=, MAXWHTHREADS=, and WORKPATH=. Any medium users inherit LOW values, with the exceptions of the SORTSIZE= setting, which has a value of 256 MB, and the MAXWHTHREADS= setting, which has a value of 6. Any high users inherit LOW values, with the exceptions of the SORTSIZE= setting, which has a value of 1 GB, the MAXWHTHREADS= setting, which has a value of 6, and the WORKPATH= setting, which has a value of /var/hightmp. All initial values are inherited from the LOW setting. Users set to HIGH do not inherit any parameter settings from MEDIUM users. Therefore, it is necessary to specify the MAXWHTHREADS= setting of 6 for users set to HIGH or MED.

The LOCKING=YES value is a special user case. All users share the same SPD Server locking proxy. For LOCKING=YES, all users inherit the LOW values in the spdsserv.parm file, regardless of performance class. You can override the parameter values for all users of the locking proxy as follows:

SORTSIZE=256M;
BINBUFSIZE=32K;
MAXWHTHREADS=4;
WORKPATH="/var/tmp";
---MED---
SORTSIZE=512M;
MAXWHTHREADS=6;
---HIGH---
SORTSIZE=1G;
MAXWHTHREADS=8;
WORKPATH="/var/hightmp";
---LOCKING---
MAXWHTHREADS=2;

In the example, all LOCKING=YES users inherit the initial default parameter values, with the exception of the initial MAXWHTHREADS=4 setting, which changes to MAXWHTHREADS=2.