Updating the Database Manager Configuration File

This file contains important settings for application development.

For routines (stored procedures and UDFs), the keyword KEEPFENCED has the default value YES. This keeps the routine process alive. If you are developing a routine, you may want to test loading the same shared library a number of times. This default setting may interfere with reloading the library. It is best to change the value of this keyword to NO while developing routines, and then change it back to YES when you are ready to load the final version of your shared library.

For threadsafe routines, the process used to run the routine remains on the instance after completion (only the thread within the process that is used to invoke the routine terminates). For this reason, when developing a new routine you should define the routine as not threadsafe. Then, if appropriate, enable the routine to run in a threadsafe mode when it is put into production.

Note:
KEEPFENCED was known as KEEPDARI in previous versions of DB2.

For Java application development, you need to update the JDK_PATH keyword with the path where the Java Development Kit (JDK) is installed.

Note:
JDK_PATH was known as JDK11_PATH in previous versions of DB2.