Overview for MQCNO

• AIX
• IBM i
• Linux
• Windows

and for IBM MQ MQI clients connected to these systems.

Purpose: The MQCNO structure allows the application to specify options relating to the connection to the local queue manager. The structure is an input/output parameter on the MQCONNX call. For more information about using shared handles, and the MQCONNX call, see Shared (thread independent) connections with MQCONNX.

Version: The header, COPY, and INCLUDE files provided for the supported programming languages contain the most-recent version of MQCNO, but with the initial value of the Version field set to MQCNO_VERSION_1. To use fields that are not present in the version-1 structure, the application must set the Version field to the version number of the version required.

Character set and encoding: Data in MQCNO must be in the character set given by the CodedCharSetId queue manager attribute and encoding of the local queue manager given by MQENC_NATIVE. However, if the application is running as an IBM MQ MQI client, the structure must be in the character set and encoding of the client.