Enabling communication exit libraries outside of 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.

Before you begin

You must have SYSADM authority to run the steps in this task.


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. Stop the database manager. To stop the database manager, run the db2stop command.
  2. Copy the communication exit library file to the correct directory.
    For more information about the location of communication exit libraries, see the related concepts. The file can be a symbolic link to another location if wanted.
  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. Start the database manager. To start the database manager, run the db2start command.

Results

The library is loaded and initialized.