Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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
Workspace IBM i
Created by Guest
Created on Feb 7, 2012

Manual builder needed for i Projects

Currently i Projects offers three builder options, a CL based builder, a user-supplied command based builder and the *NONE builder. When no builder is needed for the and the *NONE builder is selected the options to push changed members to the IBM i are no longer available in the context menu.

It would seem that a selection for a "Manual" builder is needed for the case in which the build of the elements in the i Project will be done manually by the developer. The Manual builder would contribute only the context menu actions for the files and provide no action when a clean or build of the actual i Project is done.


Use Case:

This enhancement would be used when the building of objects in the i Project is only every done manually or by some already-defined action on the IBM i independent of the i Project.


Idea priority Low
  • Guest
    Reply
    |
    Sep 28, 2021

    We have evaluated this request and determined that it cannot be implemented at this time.

  • Guest
    Reply
    |
    Jun 19, 2020

    We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.

  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for Power Systems

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Developer for Power Systems

  • Guest
    Reply
    |
    Oct 18, 2012

    A manual build is needed especailly when a custom compile command is needed. I have developed a process for CL programs where an include statement is used similar to the way an RPGLE include is done. A custom compile command will recognize thes in the CLLE code and create a source member with the merged source then call the compiler.

    Also when using modules and service programs a custom manual build must also be created because the order of the module and object creation is critical to creating the bound programs.

    The Manual build should include some way of associating a custom compile command with each source or object. A binding directory object could be the holder of the build of a service program or a bound program. Some of the third party source management solutions may recoginze these relationships, but most do not.

    Since there may be many modules, service programs, display files, tables, and the bound program, a repeatable build process is needed. The build process should also be exportable so that it can be imported into a new workspace when needed.

  • Guest
    Reply
    |
    Oct 1, 2012

    I believe this will be needed when the build is done in the Rational Team Concert. Other products that provide source control would also make use of a manual build process... Make that a build not in the Rational product.

  • Guest
    Reply
    |
    Apr 27, 2012

    This RFE will be under consideration for a future release. Status has been updated to Uncommitted Candidate.

  • Guest
    Reply
    |
    Mar 29, 2012

    This RFE is consistent with our strategy and product roadmap and IBM is continuing to evaluate.