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 Not under consideration
Created by Guest
Created on Sep 20, 2021

EWM 6.0.6.1 Delete sources from RTC doesn't always delete all files from zOS datasets

This happens in a complete 6.0.6.1 environment. So server, client and BTK all have v 6.0.6.1. When I delete a source from RTC, the build-process should delete all files known in the build-map from this source. For a cobol-source, we have the source in COBB, the listing in LSTCOB and the loadmodule in MODB. But when a dataset is locked in anyway, no deletion is possible. In our OA environment I get three members in datasets when building the source: ONE.cbl, SYSTEM.OA.M.COBB(ONE, SYSTEM.OA.M.LSTCOB(ONE) and SYSTEM.OA.M.MODB(ONE). The dataset SYSTEM.OA.M.MODB is not in any CICS at the moment. When I do move this source to R, the file gets built into SYSTEM.R.* datasets. The SYSTEM.R.M.MODB is in a CICS that is running. Just building is no problem, the loadmodule is refreshed. When I do delete ONE in OA, SYSTEM.OA.M.LSTCOB(ONE), SYSTEM.OA.M.COBB(ONE) and SYSTEM.OA.M.MODB(ONE) are deleted. When I move the workitem with this delete to R and I do a build, SYSTEM.R.M.COBB(ONE) and SYSTEM.R.M.LSTCOB(ONE) are deleted, but SYSTEM.R.M.MODB(ONE) can't be deleted. Build gives no errors, but when looking at the build.log, you can see that the load module couldn't be deleted. Promoting to the next level S, SYSTEM.S.M.MODB(ONE) is deleted as this dataset is not in a CICS. Is there another programmatic way to resolve this?
Idea priority Medium
Needed By Quarter
  • Guest
    Reply
    |
    Oct 11, 2021

    This requirement has been assessed. It is not likely that this will be implemented in the next 12-24 months and so it is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.