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 Sep 14, 2023

Enhance program call graph to not show unused Db2 calls referenced by commented PERFORM statement.

Currently in AD v6.0.1 program call graph shows unused SQL call statements of select/insert/update/delete from sections or para even if the calling PERFORM statement was commented out. Ideally those SQL calls are considered as dead codes as it will not execute in real-time but AD statically analyze those sources and considered them as valid SQL calls resulted as wrongly represented in the graph. Two ways of handling this issue.

1. From appl. aspect user should delete unwanted dead codes from the assets so AD won't show wrong presentation of SQL references in the program calls. This part we do agree.

2. Another option is, to improve the current feature of call graph to not consider dead SQL calls when the calling procedure is commented or not called.

Example:

Pgm1:

---

---

PROCEDURE DIVISION.

--

**** PERFORM XX1 (Commented out)

--

--

XX1 SECTION.

INSERT DB2X.TBL1 INTO VALUES (X,X,X,)

UPDATE DB2X.TBL2 SET COLX = 'XX' WHERE CONDITION..XX

XX1-EXIT.

   EXIT.

 

Result from Application Discovery call graph:

1. Both Table TBL1 and TBL2 are considered as valid SQL references, that is wrong.

Note:

In the above particular scenario standalone dead code analysis report 'unused routines within program' correctly captured XX1 section as unused but it doesn't work in conjunction with program call graph altogether. We see there is a scope for improvement so registered idea after checking with our IBM representative SPOC.

 

 

 

Idea priority Medium