PROVIDERVERSION migration mode

For migration mode, the IBM® MQ classes for JMS use the features and algorithms similar to those that are supplied with IBM WebSphere® MQ 6.0, such as queued publish/subscribe, selection implemented on the client side, non-multiplex channels, and polling used to implement listeners.

The figure is described in the surrounding text. — Figure 1. PROVIDERVERSION migration mode

If you want to connect to WebSphere Message Broker 6.0 or WebSphere Message Broker 6.1 using IBM MQ Enterprise Transport version 6.0, you must use migration mode.

You can connect to an IBM MQ 8.0 queue manager using migration mode, but none of the new features of an IBM MQ classes for JMS queue manager are used, for example, read ahead or streaming. If you have an IBM MQ 8.0 or later client connecting to an IBM MQ 8.0 or later queue manager on a distributed platform, [z/OS] or an IBM MQ for z/OS® 8.0 or later queue manager, then the message selection is done by the queue manager rather than on the client system.

If IBM MQ messaging provider migration mode is specified and the IBM MQ classes for JMS attempt to use any of the JMS 2.0 API, the API method call fails with the exception JMSCC5007.