Use IBM MQ classes for JMS in IMS

Standards-based messaging support within an IMS environment is provided through the use of IBM MQ classes for JMS.

Check the system requirements for the IMS system that your enterprise uses. See General planning information for IMS Version 13 for further information

This set of topics describes how to set up the IBM MQ classes for JMS in an IMS environment, and the API restrictions that apply when using the classic (JMS 1.1) and simplified (JMS 2.0) interfaces. See JMS API restrictions for a list of the API-specific information. Note: Similar restrictions apply to the legacy (JMS 1.0.2) domain-specific interfaces, but they are not specifically described here.


Supported IMS dependent regions

The following dependent region types are supported:

  • MPR
  • BMP
  • IFP
  • JMP 31 and 64 bit Java virtual machines (JVMs)
  • JBP 31 and 64 bit JVMs

Unless specifically mentioned in the following topics, IBM MQ classes for JMS behaves the same in all region types.


Supported Java Virtual Machines

IBM MQ classes for JMS requires Java Platform, Standard Edition 7 (Java SE 7) or later.


Other restrictions

The following restrictions apply when using IBM MQ classes for JMS in an IMS environment:

  • Client mode connections are not supported.
  • Connections are only supported to IBM MQ Version 8.0 queue managers using the IBM MQ messaging provider Normal, or Version 8 mode.

    The PROVIDERVERSION attribute on the connection factory must be either unspecified, or a value greater than, or equal to, seven.

  • Use of any of the XA connection factories, for example com.ibm.mq.jms.MQXAConnectionFactory, is not supported.

  • Set up the IMS adapter for use with IBM MQ classes for JMS
    IBM MQ classes for JMS make use of the same IBM MQ-IMS adapter as used by other programming languages. This adapter uses the IMS External Subsystem Attach Facility (ESAF).
  • Transactional behavior
    Messages sent and received by the IBM MQ classes for JMS in an IMS environment are always associated with the IMS unit of work (UOW) that is active on the current task.
  • Implications of IMS syncpoints
    The IBM MQ classes for JMS build upon the existing IBM MQ adapter support which makes use of ESAF. This means that the documented behavior applies, including all open handles being closed by the IMS adapter when a syncpoint occurs.
  • Considerations when using the IMS adapter
    We need to be aware of the following restrictions. We can have only one connection handle for each queue manager. There are implications in the interaction with IBM MQ when using both JMS and native code. There are limitations to connection authentication and authorization.
  • JMS API restrictions
    From a JMS specification perspective, the IBM MQ classes for JMS treat IMS as a Java EE compliant application server, that always has a JTA transaction in progress.

Parent topic: Use IBM MQ classes for JMS


Related information