Home

 

Channel-exit calls and data structures

 

This topic provides reference information about the special WebSphere MQ calls and data structures that we can use when you write channel exit programs.

This is product-sensitive programming interface information. You can write WebSphere MQ user exits in the following programming languages:

Platform	Programming languages
WebSphere MQ for z/OS	Assembler and C (which must conform to the C system programming environment for system exits, described in the OS/390 C/C++ Programming Guide.)
WebSphere MQ for iSeries	C, COBOL, and RPG II
All other WebSphere MQ platforms	C

You cannot write WebSphere MQ user exits in TAL or Visual Basic. However, a declaration for the MQCD structure is provided in Visual Basic for use on the MQCONNX call from an MQ client program.

In a number of cases, parameters are arrays or character strings whose size is not fixed. For these, a lowercase "n" is used to represent a numeric constant. When the declaration for that parameter is coded, the "n" must be replaced by the numeric value required. For further information about the conventions used in these descriptions, see the Application Programming Reference book.

The calls are:

• MQ_CHANNEL_EXIT – Channel exit

• MQ_CHANNEL_AUTO_DEF_EXIT – Channel auto-definition exit

• MQXWAIT – Wait in exit

The data structures are:

• MQCD – Channel definition

• MQCXP – Channel exit parameter

• MQXWD – Exit wait descriptor

• Data definition files
  

• MQ_CHANNEL_EXIT – Channel exit
  

• MQ_CHANNEL_AUTO_DEF_EXIT – Channel auto-definition exit
  

• MQXWAIT – Wait in exit
  The MQXWAIT call waits for an event to occur. It can be used only from a channel exit on z/OS.

• MQCD – Channel definition
  

• MQCXP – Channel exit parameter
  

• MQXWD – Exit wait descriptor
  

 

Parent topic:

Further intercommunication considerations

ic17730_

 

Home