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 Future consideration
Created by Guest
Created on Nov 10, 2023

Allow different zAPM Distributed Gateways to communicate

Where there are multiple DGs that may be globally dispersed, CICS (SYSPLEX1) connected to DG1 => MQ => CICS (SYSPLEX2) connected to DG2 may result in events being sent to different DGs for a single end to end message flow.

Even though the DG2 may be configured to send data to the same controller(/s) as DG1, it will not have a singularity header to associate it with as it was added by zAPM rather than AppD.

Please allow DGs to be connected/ aware of other DGs (via config), so it could send the events not associated with a singularity header for consideration in End to End flows to other DGs.

This will enable end to end flows to be more complete.

Idea priority Medium
  • Admin
    CHRISTOPHER WALKER
    Reply
    |
    Feb 14, 2024

    Moving to a potential future item. At the moment, this is not under immediate consideration.