Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Categories System Management
Created by Guest
Created on Jun 7, 2013

Allow a Global Transaction to be spread across multiple IMS Connect and IMS Control region on different LPAR.

Currently a distributed two-phase commit global transaction that involves IMS Connect has the restriction that IMS Connect and IMS have to be on the same LPAR. To clarify this restriction, IMS Connect and the IMS that receives the input msg must be on the same LPAR, this is true even in a SQ environment where IMS Connect and the receiving IMS FE have to be in the same LPAR (the transaction can then run on a BE IMS in a different LPAR, but the receiving IMS FE must be on the same IMS Connect LPAR).
The customer would like to have this restriction removed in order to improve availability and facilitate transaction distribution.
This RFE origins from old FITS MR0115101127 .

Idea priority High
  • Guest
    Reply
    |
    Nov 11, 2015

    Available as of IMS v14

  • Guest
    Reply
    |
    Jun 17, 2013

    Change Visibility to Public as requested by Customer.

  • Guest
    Reply
    |
    Jun 11, 2013

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Information management
    Product family - IMS
    Product - IMS System Services
    Component - System Management

    For recording keeping, the previous attributes were:
    Brand - Information management
    Product family - IMS
    Product - IMS Transaction Manager
    Component - General TM

  • Guest
    Reply
    |
    Jun 8, 2013

    Changed Visibility to Public per customer's request.

  • Guest
    Reply
    |
    Jun 7, 2013

    Please change the Visibility of this RFE to Public as requested by Customer.