Using a client channel definition table with .NET

You can use a client channel definition table (CCDT) with the IBM® MQ classes for .NET. You specify the location of the CCDT in different ways, depending on whether you are using a managed or unmanaged connection.

Non-XA or XA unmanaged client connection type

With an unmanaged connection type, you can specify the location of the CCDT in two ways:
  • Using the environment variables MQCHLLIB to specify the directory where the table is located, and MQCHLTAB to specify the file name of the table.
  • Using the client configuration file. In the CHANNELS stanza, use the attributes ChannelDefinitionDirectory to specify the directory where the table is located, and ChannelDefinitionFile to specify the file name.
If the location is specified both in the client configuration file and by using environment variables, the environment variables take priority. You can use this feature to specify a standard location in the client configuration file and override it using environment variables when necessary.

Managed client connection type

With a managed connection type, you can specify the location of the CCDT in three ways:
  • Using the .NET application configuration file. In the CHANNELS section, use the keys ChannelDefinitionDirectory to specify the directory where the table is located, and ChannelDefinitionFile to specify the file name.
  • Using the environment variables MQCHLLIB to specify the directory where the table is located, and MQCHLTAB to specify the file name of the table.
  • Using the client configuration file. In the CHANNELS stanza, use the attributes ChannelDefinitionDirectory to specify the directory where the table is located, and ChannelDefinitionFile to specify the file name.

If the location is specified in more than one of these ways, the environment variables take priority over the client configuration file, and the .NET Application Configuration File takes priority over both other methods. You can use this feature to specify a standard location in the client configuration file and override it using environment variables or the application configuration file when necessary.

From IBM MQ 9.3.0, the .NET client behaves in the same way as the C and Java clients and returns the MQRC_Q_MGR_NAME_ERROR when using a CCDT with queue manager grouping.