channel compression, Channel event control, message retry default, heartbeat for clients, IPv6" /> Channels

 

Channels

 

Compression of channel data

Compression of channel data reduces the amount of network traffic and can therefore improve the performance of channels. Channel data compression is enabled through the use of channel send and receive exits. New versions of the MQCD and MQCXP have been added, and new attributes have been added to the DEFINE CHANNEL and ALTER CHANNEL commands, to support channel compression.

For information about changes to MQCD and MQCXP, see WebSphere MQ Intercommunication.

For information about the DEFINE CHANNEL and ALTER CHANNEL commands, see WebSphere MQ Script (MQSC) Command Reference.

 

Channel event control

It is now possible to enable or disable channel event messages, IMS Bridge event messages and SSL event (these are the messages that are put to the SYSTEM.ADMIN.CHANNEL.EVENT queue). Previously the only way to do this was to delete the queue itself.

It is also now possible to collect only those event messages that are of interest (that is, event messages related to channel errors rather than those related to the normal starting and stopping of channels).

To support this feature, changes have been implemented to the commands ALTER QMGR and DISPLAY QMGR.

 

Message retry on channels

Message retry is now available using the MRRTY, MRTMR, MREXIT and MRDATA channel attributes.

Migrated channels from previous releases have the default value MRRTY(0) so there is no message retry, and new channels have the default value MRRTY(10).

Note that we can change the message retry default settings by altering the SYSTEM.DEF* channels.

 

Heartbeat for clients

When an MQI channel is waiting, particularly for a GET with WAIT, it is useful to be able to poll the channel to verify that the two MCAs are still active.

In this context, heartbeat interval is now supported for client-connection channels.

To support this feature, changes have been implemented for the ALTER CHANNEL and DEFINE CHANNEL MQSC commands.

 

Support for IPv6

IPv6 (Internet Protocol V6) is designed by the IETF to replace the current version Internet Protocol, V4 (IPv4). IPv6 fixes a number of problems in IPv4, such as the limited number of available addresses, as well as adding improvements in areas such as routing and automatic configuration of networks . IPv6 is expected to gradually replace IPv4, with the two protocols co-existing for a number of years during a transition period. WebSphere MQ for z/OS offers support for intercommunication using IPv6, and continues to support the use of the IPv4 protocol.

To support IPv6, a new attribute, IPADDR has been added to the ALTER QMGR and DISPLAY QMGR commands. For details of these commands, see WebSphere MQ Script (MQSC) Command Reference.

For information about using IPv6, see the WebSphere MQ Internet Protocol V6 (IPv6) Migration publication.