Features outside the core classes of IBM MQ classes for Java

IBM MQ classes for Java contain certain functions that are specifically designed to use API extensions that are not supported by all queue managers. This collection of topics describes how they behave when using a queue manager that does not support them.

• Variations in the MQQueueManager constructor option
  Some of the MQQueueManager constructors include an optional integer argument. Some values of this argument are not accepted on all platforms.
• Restrictions on the MQQueueManager.begin() method
  This method can be used only against an IBM MQ queue manager on UNIX, Linux, or Windows systems in bindings mode. Otherwise, it fails with MQRC_ENVIRONMENT_ERROR.
• Variations in the MQGetMessageOptions fields
  Some queue managers do not support the Version 2 MQGMO structure, so we must set some fields to their default values.
• Restrictions in distribution lists in IBM MQ classes for Java
  Not all queue managers allow you to open an MQDistributionList.
• Variations in MQPutMessageOptions fields
  If a queue manager does not support distribution lists, certain MQPMO fields are treated differently.
• Restrictions in MQMD fields with IBM MQ classes for Java
  Certain MQMD fields concerned with message segmentation should be left at their default value when using a queue manager that does not support segmentation.

Parent topic: IBM MQ classes for Java environment-dependent behavior