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 Submitted
Created by Guest
Created on Jun 3, 2026

Support detection of IMS DB usage in Assembler programs when DL/I calls are performed indirectly via wrapper modules and dynamic calls.

Currently, IMS/DB Usage and Logical Usage reports rely on detecting statement occurrences within program source. In environments using Assembler, it is common to encapsulate IMS access through wrapper modules and dynamic calls (e.g., program → DBACCESS → ACCESSDB → DL/I call).

In these cases, the calling program does not contain a direct DL/I statement, and as a result, no IMS usage is reported, even though the program logically accesses the database.

Enhancement request:

  • Support detection of IMS DB usage when calls are performed indirectly via wrapper modules or dynamic loading patterns
  • Optionally trace usage across module boundaries (call chain)
  • Or provide an option to associate usage with upstream programs when IMS access is abstracted
Idea priority Medium