Home

 

Overview

Availability:

• All versions except MQCNO_VERSION_4: AIX, HP-UX, i5/OS, Solaris, Linux, Windows, plus WebSphere MQ 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.

See the WebSphere MQ Application Programming Guide for details of using shared handles within a global unit of work and the effect that this has on, for example, XA transactions.

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 Vfield set to MQCNO_VERSION_1. To use fields that are not present in the version-1 structure, the application must set the Vfield to the version number of the version required.

Character set and encoding: Data in MQCNO must be in the character set and encoding of the local queue manager; these are given by the CodedCharSetId queue-manager attribute and MQENC_NATIVE, respectively. However, if the application is running as a WebSphere MQ client, the structure must be in the character set and encoding of the client.

 

Home