Channel-exit programs are called at defined places in the processing carried out by MCA programs.
Some of these user-exit programs work in complementary pairs. For example, if a user-exit program is called by the sending MCA to encrypt the messages for transmission, the complementary process must be functioning at the receiving end to reverse the process.
The different types of channel-exit program are described below. Table 37 shows the types of channel exit that are available for each channel type.
Channel Type | Message exit | Message- retry exit | Receive exit | Security exit | Send exit | Auto- definition exit |
---|---|---|---|---|---|---|
Sender channel | Yes | Yes | Yes | Yes | ||
Server channel | Yes | Yes | Yes | Yes | ||
Cluster- sender channel | Yes | Yes | Yes | Yes | Yes | |
Receiver channel | Yes | Yes | Yes | Yes | Yes | Yes |
Requester channel | Yes | Yes | Yes | Yes | Yes | |
Cluster- receiver channel | Yes | Yes | Yes | Yes | Yes | Yes |
Client- connection channel | Yes | Yes | Yes | |||
Server- connection channel | Yes | Yes | Yes | Yes | ||
Notes:
|
If you are going to run channel exits on a client, you cannot use the MQSERVER environment variable. Instead, create and reference a client channel definition table as described in the WebSphere MQ Clients book.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
wace |