Known limitations
Learn about limitations of IBM® MQ Advanced Message Security.
- The following IBM MQ options are not supported:
- Publish/subscribe.
- Channel data conversion.
- Distribution lists.
- Application message segmentation
- The use of non-threaded applications using API exit on HP-UX platforms.
- IBM MQ classes for .NET in a managed mode (client or bindings connections).
- Message Service client for .NET (XMS) applications.
- Message Service client for C/C++ (XMS supportPac IA94) applications.
- IBM MQ queues processed by the IMS bridge.
Note: IBM MQ AMS is supported on CICS® Bridge queues. You should use the same user ID to MQPUT (encrypt) and MQGET (decrypt) on CICS Bridge queues.
- All Java applications are dependant on IBM Java Runtime. IBM MQ AMS does not support any JRE provided by other vendors.
- Users should avoid putting two or more certificates with the same Distinguished Names in a single keystore file because the IBM MQ AMS interceptor's functioning with such certificates is undefined.
- IBM MQ AMS is not supported in JMS if the WMQ_PROVIDER_VERSION property is set to 6.