PROVIDERVERSION normal mode with restrictions

Normal mode with restrictions uses the JMS 2.0 API, but not the new IBM MQ Version 8.0 or later features such as shared subscriptions, delayed delivery, or asynchronous send.

The following flowchart shows the checks that the JMS client makes to determine whether a normal mode with restrictions connection can be created .

If the queue manager specified in the connection factory settings has a command level of 700 or greater, and the TRANSPORT property of the connection factory is set to BINDINGS, a normal mode connection is created without checking any further properties.

If the queue manager specified in the connection factory settings has a command level of 700 or greater, and the TRANSPORT property is set to CLIENT, the SHARECNV property on the server connection channel is also checked. This check is needed because IBM MQ messaging provider normal mode with restrictions uses the sharing conversations feature. Therefore, for a normal mode with restrictions connection attempt to be successful, the SHARECNV property, which controls the number of conversations that can be shared, must have a value of 1 or greater.

If all the checks shown in the flowchart are successful, a normal mode with restrictions connection to the queue manager is created and we can then use the JMS 2.0 API, but not the asynchronous send, delayed delivery, or shared subscription features.

• The queue manager specified in the connection factory settings has a command level that is earlier than 700. In this case, the createConnection method fails with exception JMSFCC5008.
• The SHARECNV property on the server connection channel is set to 0. If this property does not have a value of 1 or greater, the createConnection method fails with an exception JMSCC5007.

Parent topic: IBM MQ messaging provider modes of operation

Related information

• Dependencies between properties of IBM MQ classes for JMS objects
• DEFINE CHANNEL (SHARECNV property)
• TRANSPORT