Communication exit library problem determination

Some options are available to help diagnose problems with a communication exit library.

The communication exit library is not provided as part of Db2®. Rather, it is a library that you install. It might be automatically installed and configured by a tool or application that you are using, or it might be written by you.

The name of the library that is specified in the database manager configuration parameter comm_exit_list gives some indication as to the source of the library.

If you experience any issue with the library, the documentation for the tool or application must be consulted. The tool or application documentation outlines what problem determination steps must be taken.

An interface to write to the db2diag log files is available to communication exit libraries. The db2diag log files can be checked whether there are concerns if the library is functioning properly.

If there are concerns about the performance of the communication exit library, monitoring wait times can be used to investigate how long the library is taking. For more information about these monitor tools, see the related reference.