IMS Connect coexistence considerations

The IMS 15 IMS Connect function supports IMS 14 and IMS Version 13, although new functions might not be available when connecting with the older versions.

IMS Connect instances from IMS 14 or IMS Version 13 might also be able to connect to an IMS 15 system, but coexistence APARs might be required.

  • Support for cascading global transactions from the IMS TM resource adapter to an IMS TM system on a different LPAR is supported only after both IMS Connect and the IMS control region are migrated to IMS 14.

    If IMS Connect receives a global transaction from IMS TM resource adapter when IMS Connect and IMS are not on the same LPAR and either IMS Connect, IMS, or both, are not at IMS 14, the transaction is rejected with a NAK message that includes a sense code of X'2F'.

  • IMS Version 12 and IMS Version 13 instances of IMS Connect can connect to OTMA tpipes that support parallel processing of RESUME TPIPE requests after the appropriate coexistence APARs are applied. The APARs are required only for IMS Version 12 and IMS Version 13 instances of IMS Connect that connect to tpipes in which tpipe parallelism is enabled.

    Previous versions of IMS Connect require these compatibility fixes:
    • IMS Connect Version 13 APAR/PTF PM93878/UK98632
    • IMS Connect Version 12 APAR/PTF PM93880/UK98633

  • IMS 15 introduces new and changed IMS type-2 commands for IMS Connect. If a type-2 command is broadcast to an IMSplex in which multiple versions of IMS Connect coexist, instances of IMS Connect from earlier versions reject commands that include keywords that they do not support and ignore commands that they do not recognize.