Some database manager configuration parameters have been changed

Details

New database manager configuration parameters

Due to new features and functionality, Version 10.1 contains a number of new configuration parameters.

Table 1. Summary of new Version 10.1 database manager configuration parameters

Parameter name	Description	Details
comm_exit_list	Communication buffer exit library list	This parameter specifies the list of communication buffer exit libraries that DB2® will use. A communication buffer exit library is a dynamically loaded library that vendor applications can use to gain access to and examine DB2 communication buffers used to communicate with client applications.
wlm_dispatcher	Workload manager dispatcher	This parameter enables (YES) or disables (NO) the DB2 workload manager (WLM) dispatcher. By default, an enabled WLM dispatcher controls only CPU limits.
wlm_disp_concur	Workload manager dispatcher thread concurrency	This parameter specifies how the DB2 workload manager (WLM) dispatcher sets the thread concurrency level. You can also manually set the thread concurrency level to a fixed value.
wlm_disp_cpu_shares	Workload manager dispatcher CPU shares	This parameter enables (YES) or disables (NO) the control of CPU shares by the DB2 workload manager (WLM) dispatcher. By default, an enabled WLM dispatcher controls only CPU limits.
wlm_disp_min_util	Workload manager dispatcher minimum CPU utilization	This parameter specifies the minimum amount of CPU utilization that is necessary for a service class to be included in the DB2 WLM-managed sharing of CPU resources.

Changed database manager configuration parameters

The following table lists the database manager configuration parameters with changes to their default values.

Table 2. Summary of configuration parameters with changed default values

Parameter name	Description	Details about default value change
alt_diagpath	Alternate diagnostic data directory path configuration parameter	Previous releases Null Version 10.1 DB2 pureScale® environments (Linux and UNIX) INSTHOME/sqllib/db2adump/ $m
cf_diagpath	Diagnostic data directory path configuration parameter for the CF	Previous releases of DB2 pureScale environments Null Version 10.1 DB2 pureScale environments INSTHOME/sqllib/db2dump/ $m
diagpath	Diagnostic data directory path configuration parameter	The default value of diagnostic data directory path configuration parameter is changed Previous releases Null Version 10.1 Server Edition (Linux and UNIX) INSTHOME/sqllib/db2dump/ Version 10.1 partitioned database environments (Linux and UNIX) INSTHOME/sqllib/db2dump/ $m Version 10.1 DB2 pureScale environments (Linux and UNIX) INSTHOME/sqllib/db2dump/ $m This new default value means that all database partitions, CFs, and members have their own diagnostic log directory. Version 10.1 (Windows) On partitioned database environments: Instance subdirectory of the directory specified by the DB2INSTPROF registry variable\ $m Outside of partitioned database environments: Instance subdirectory of the directory specified by the DB2INSTPROF registry variable\ You can use the new value $m, which resolves to DIAG_number, to specify a unique diagnostic log path for all database partitions, CFs, or members.

The following database manager configuration parameters have changed behaviors or have new ranges in Version 10.1.

Table 3. Summary of database manager configuration parameters with changed behaviors, new ranges, or new values

Parameter name	Description	Version 10.1 change
diagpath	Diagnostic data directory path configuration parameter	You can use the new value $m, which resolves to DIAG_number, to specify a unique diagnostic log path for all database partitions, CFs, or members. The value $n is deprecated and might be removed in a future release. Use the $m value instead.
numdb	Maximum number of concurrently active databases including host and System i® databases configuration parameter	The maximum number of concurrently active databases in a DB2 pureScale environment is now 200.

Resolution

Take advantage of enhanced functionality or new features by adopting new functionality through the use of new database manager configuration parameters or new values for existing database manager configuration parameters.

For new database manager configuration parameters or changes to existing database manager configuration parameters that result in DB2 server behavior changes, adjust your existing applications or scrips.