Potential migration issues for the IMS TM resource adapter

You might need to modify existing applications that use older connector frameworks, architectures, or APIs when you upgrade to newer versions of the IMS TM resource adapter

Deprecated functions and support

  • The SYNC_RECEIVE_ASYNCOUTPUT interaction verb was deprecated in IMS TM Resource Adapter Version 10, and is replaced by SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT. No migration step is required.

    See the topic on "Asynchronous output programming model" for the differences between the new interaction verbs SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT. These two verbs provide finer control of the interactions when checking for the output on the IMS OTMA asynchronous hold queue.

Removed functions and support

  • The Common Connector Framework (CCF) is not supported. Applications that use CCF must be migrated to the JCA specification.
  • You might encounter warnings if you run applications that use non-managed connections or were generated by using a previous version of JCA 1.0-based IMS TM Resource Adapter with the latest versions of IMS TM Resource Adapter. The TransactionResourceRegistration property available in IMS TM Resource Adapter Version 9 was removed from the custom properties of an IMS TM resource adapter connection factory. This property supported dynamic transaction enlistment for JCA 1.0-based resource adapters. This function was incorporated into the JCA 1.5-based resource adapters, so the TransactionResourceRegistration property is no longer needed.
  • MFS web services applications that were generated by WebSphere® Studio Application Developer Integration Edition are not supported by IMS TM Resource Adapter.