IBM MQ client channel boolean attribute ibm-amqIsClientDefault

Preconnect exit modules generally search the LDAP servers with the value of the ibm-amqQueueManagerName attribute as the search criteria. Such a query would return all entries where the ibm-amqQueueManagerName attribute value matches the name of the queue manager specified on the MQCONN/X call. However when using the client channel definition tables (CCDT), you can either set the queue manager name on a MQCONN/X call as blank or prefix the name with an asterisk (*). If the name of the queue manager is blank, the client connects to the default queue manager. If the name is prefixed with an asterisk (*) to the queue manager, then the client connects any queue manager.

Similarly, the ibm-amqQueueManagerName attribute in an entry can be left undefined. In this case, it is expected that the client using this endpoint information can connect to any queue manager. For example, an entry contains the following lines:

ibm-amqChannelName = "CHANNEL1"
ibm-amqConnectionName = myhost(1414)

In this example, the client attempts to connect to the specified queue manager running on myhost.

However in LDAP Servers, a search is not made on an attribute value that has not been defined. For example, if an entry contains the connection information except ibm-amqQueueManagerName, then the search results would not include this entry. To overcome this problem, you can set ibm-amqIsClientDefault. This is a Boolean attribute and is assumed to have a value of FALSE if not defined.

For entries where the ibm-amqQueueManagerName has not been defined and are expected to be part of the search, set ibm-amqIsClientDefault to TRUE. When a blank or asterisk (*) is specified as the queue manager name in a call to MQCONN/X, the preconnect exit searches the LDAP sever for all entries where ibm-amqIsClientDefault attribute value is set to TRUE.

See also ibm-amqQueueManagerName.