Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Jan 6, 2022

delete all output registered in buildmaps

SVB is a governemental orginizations, that serves all 17 mil. Dutch citizens. Many billion euro's are concerned. We have to maintain strict security rules. One is that we need to keep a close connection between sources and executables. ELM has to be able to garantuee that the sources in the repo reflect the loadlibrarycontents. So when we delete a cobol source, the buildproces needs to delete all output from this source, including the loadmodule. Deletion should occur always and if no succes, it has to be detected easily. But for this info we have to take a very close look at the build-log. I'd expect a warning at least when the delete is unscuccesfull. Maybe use the 'delete Buildable File List' and flag the unsuccesful deletes. Then a postbuild script could be invoked to read this file and try to delete the unscuccesfull deletes again.
Idea priority Medium
Needed By Week
  • Guest
    Reply
    |
    Jan 17, 2022

    The most desirable is that the build does what is it suppose to do, delete all output registred in the buildmap. The second best is that the build indicates that a delete couldn't be done, so it gives a yellow (of better a red) flag when the delete fails. This will be an extra attention to check whether the post-build script succeeded in deleting where the build didn't

2 MERGED

When removing a member from a component, it should be removed from the build space on z/os

Merged
We have a problem updating the build space on Zos. If we delete a copybook from the stream, it is deleted in the buildmap but not in the build space(build resource prefix) on the Zos. So if a program still uses it, when compiling we find the copyb...
almost 2 years ago in IBM Engineering - Workflow Management / Enterprise Extensions 3 Future consideration