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 Manager 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.
You enter 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 you use the following
keywords in the spdsserv.parm file, they associate a user with the
performance-level parameter settings:
MED
Parameters defined
in this section are applied to medium performance class users.
HIGH
Parameters defined
in this section are applied to high-performance class users.
LOCKING
Parameters defined
in this section are applied to LOCKING=YES users.
Consider the following
example:
User Bob belongs to
the low-performance class. User Tom belongs to the medium performance
class. User Mary belongs to the high-performance class. If you wanted
to assign different server values to low, medium, and high users,
you would define 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";
In the spdsserv.parm
file, all low users receive the initial LOW (default) values for SORTSIZE=,
BINBUFSIZE=, MAXWHTHREADS=, and WORKPATH=. Medium users inherit the
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. High users inherit the LOW values, with the following exceptions:
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 who are set to HIGH do not inherit any parameter
settings from MEDIUM users. Therefore, you must specify MAXWHTHREADS=6
for users who are 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 use the following code
to override the parameter values for all users of the locking proxy.
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 this 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.