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 Feb 15, 2024

AD - Representing DL1 call graph/DB's in different annotation.

If common DL-1 service module “pgm-x’ having CBLTDLI is called by ‘pgm-1’ , ‘pgm-2’, ‘pgm-3’ for several business reasons, finally at the end AD generates 3 different call arrows towards different databases for same physical call in the service module “pgm-x”. Logically this representation seems right as per existing algorithm. However from developer aspect it looks bit weird, as a result their analysis inference might go wrong.

Therefore for the benefit of end users, there is a possibility to add call graph arrows in different colour to alert users to cross verify all the nested program flows and procedure division clause, it would be hint for them to back tracing everything from down above.

In brief:

1) If DL1 service module is called by standalone one driver then the existing call graph arrows in yellow can stay as is (no change)

2) When common DL1 service module is called by several drivers from different levels of call chains, then we expect AD to represent same call graph arrows in different colour code (1st call arrow in red, 2nd call arrow in pink .. and so on).

Existing PMR case TS013584339/discussion threads can be referred.

Idea priority Medium
  • Admin
    Ken Edwards
    Reply
    |
    Mar 18, 2024

    Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. Your request is currently in line with our product strategy and we have planned it for a future release of the product. Thank you for your suggestion and continued support.