Using MQCONNX

 

You can use the MQCONNX call to specify a channel definition (MQCD) structure in the MQCNO structure. This allows the calling client application to specify the definition of the client-connection channel at run-time. When you use MQCONNX, the call issued at the server depends on the server level and listener configuration.

When you use MQCONNX from a client, the following options are ignored:

• MQCNO_STANDARD_BINDING
• MQCNO_FASTPATH_BINDING

The MQCD structure you can use depends on the MQCD version number you are using. You can use the MQCD structure, for instance, to pass channel-exit programs to the server. You can use the structure to pass an array of exits to the server. You can use this function to perform more than one operation on the same message, such as encryption and compression, by adding an exit for each operation, rather than modifying an existing exit. If you do not specify an array in the MQCD structure, the single exit fields will be checked.

 

Shared connection handles on MQCONNX

You can share handles between different threads within the same process, using shared connection handles. When you specify a shared connection handle, the connection handle returned from the MQCONNX call can be passed in subsequent MQI calls on any thread in the process.

You can use a shared connection handle on a WebSphere MQ client to connect to a server queue manager that does not support shared connection handles.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.