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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Developer for z/OS
Categories Other/Unknown
Created by Guest
Created on Aug 26, 2022

RELATED IDEAS

Local preprocessors in IDz: provide a property for the location of the BuildOutput folder

We are developing sources in IDz in combination with GIT repositories that are cloned in the workspace. When you invoke the preprocessor (for PL/1) in your editor, then the tools automatically created a BuildOutput folder in the top-level our your locally cloned GIT repository and puts a .dek, .lst and .xml file in it. The BuildOutput folder can be considered as temporary work data for the editor. If after editing our sources, we would perform a commit and push, the contents of this work data would also land up in our central Git repository and we don't want that. We can bypass this by putting the BuildOutput folder in a .gitignore file, but it isn't an elegant solution. Please provide a preference so that the location of the BuildOutput folder can be changed to a real temp location (instead of in our locally cloned GIT repository).
Idea priority Medium
  • Guest
    Reply
    |     Oct 18, 2022
    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. At this time we have no plans to address this request within our product. We do however suggest looking into .gitignore as possible solution.

    Again, thank you for your request.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.