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.

Add a new idea Subscribe
Status Not under consideration
Workspace IMS System Services
Categories General System
Created by Guest
Created on Jun 11, 2013

RELATED IDEAS

Force affinity to same LPAR IMS FE for IMS Connect distributed 2PC Global transactions (until implementation of RFE 35707)

Currently a distributed Synclevel 2 global transaction that involves IMS Connect has the restriction that IMS Connect and IMS (and RRS too) have to be on the same LPAR.
This is documented in Paragraph "Global (XA) transaction with TCP/IP" of IMS Communication and Connection Guide: "IMS Connect, RRS, and IMS must all be on the same z/OS image".
If this rule is not followed the Transaction, when trying to be processed on a IMS FE not being on the same LPAR, will get an error (message ICO0002E OTMA SENSE CODE 47 x'2F').
We already submitted DCR MR0115101127 in 2010, now RFE 35707) for this Customer to ask for this limitation to be removed; until this RFE would be possibly implemented, and the limitation that IMS Connect and receiving IMS FE have to be on the same LPAR so removed, to avoid Synclevel 2 Transactions coming IMS Connect to possibly go in error if attempted to be processed on a "non-local" different LPAR IMS FE, or not to have Customer required to implement any user controlled mechanism to force the Transactions to be processed by the "local" same-LPAR IMS FE, Customer would like to have IMS supply a facility to force this to happen.
If the "local" same-LPAR IMS FE would be unavailable the input Transaction should be kept on the Queue.
IMS Connect and/or IMS should so set a kind of "affinity" to the IMS FE being on the same LPAR of IMS Connect for the Synclevel 2 Transactions coming from IMS Connect OTMA interface.
It seems as if setting the "Persistent Socket" flag on WAS would allow such an "affinity" to be created already if XA Global Transaction originates from WAS; however Customer wants to have the affinity created also for Transactions coming from different applications.
In the past we already submitted also a RCF to ask for the current restriction that for Input Protected Synclevel 2 Transactions IMS Connect, RRS, and IMS must all be on the same z/OS image, to be added as a possible cause for OTMA NAK SENSE CODE x'002F' / Decimal 47. RCF internal tracking number was 110865.
Depending on which one of our requests would be implemented the other ones could then be considered useless and necessary to be rejected or restored.

Idea priority High
  • Guest
    Reply
    |     Feb 10, 2016

    Dear Mr Bescape,

    Thank you for submitting this IMS enhancement request.

    After a comprehensive review, we regret to inform you that we have determined that at this time this request will not be a candidate for inclusion in an upcoming release because it is not consistent with the product direction.  Hence, we have rejected this request.

    We appreciate your input to the IMS development team.

    Sincerely,
    Tom Morrison

  • Guest
    Reply
    |     Feb 10, 2016

    RFE 35707, which enhances IMS and IMS Connect to support 2PC Global transactions when IMS and IMS Connect reside on different z/OS images, has been delivered in IMS 14. Part of the solution delivered in IMS 14 provides better routing information to the IMS Connect user message exists, including whether 2PC is supported for specific data stores. This information can be used by the customer to enforce their own affinity if required. Therefore, this RFE 35876, which requests that IMS Connect enforce affinity, is no longer required.

    In an email on Feb 10, 2016, Gianmario Bescape confirmed that the customer no longer requires this enhancement:

    Hello Tom,
    ok from Customer in Rejecting DCR MR021612157 / RFE 35876 .

    Therefore, the requirement will be rejected.

  • Guest
    Reply
    |     Jun 17, 2013

    Change Visibility to Public per customer request.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.