Enabling communication exit libraries in Db2 pureScale environments

The steps that are outlined in this task are typically run by third party supplied installation scripts. The steps are outlined to help you enable a communication exit library that you develop.

About this task

By using a communication exit library that contains a version number in the file name, and a symbolic link to this file for a library without the version number, it is possible to deploy the library on a member by member basis. In this scenario, it is not necessary to stop the whole instance, only individual members.


Restrictions

The communication exit library files must follow strict file permission guidelines. For more information about these guidelines, see the related concepts.

Procedure

To enable a communication exit library:

  1. Copy the communication exit library that contains the version number in file name to the correct directory.
    For more about the location of communication exit libraries, see the related concepts.
  2. Create a symbolic link from the library without a version to the library that contains the version in the file name.
  3. Update the database manager configuration parameter comm_exit_list with the name of the library.
    To update the configuration parameter, use the UPDATE DBM CFG command.
  4. Stop each member individually.
    To stop each member, run the db2stop command on each member
  5. Restart the stopped members.
    To start the stopped members, run the db2start command.

Results

The library is loaded and initialized.