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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
I really like the idea of an IDE. It should do all the keeping track of things for me. It should help me with my builds, it should make debugging easier for me, and RDI does a lot of that very nicely. But one place where it falls short is in helping with ILE builds. I shouldn't have to remember what modules are used to build which service programs. I shouldn't even have to manage binder source, the IDE should be able to do that for me. Maybe I am missing something, but this sort of build support should be a minimum level of support. I was talking to a colleague about ILE, and he told me that he hasn't done ILE because it is too hard. To hard in that there are too many moving parts, and no tools that know how to manage them. If I am missing something, please let me know, but I just don't see it in RDi. I was hoping that an I Project would be the ticket, but not really. It lets you write a binding program, but that is not the tool doing the work.
What would be nice is to be able to define a service program in some sort of meta data. A dialog would let me attach modules to the service program, and then tell which procedures were exported. It would also allow me to attach binding directories, and work with the binding directory entries. It would be smart enough to know whether to create or update the service program based on source dates, and whether or not I have added a new module. And I would simply have to tell RDI to build the service program, and it would do it all correctly. That includes recompiling the sources that have changed, and updating or replacing the service program. Generating the appropriate binder source with a static signature. Disallowing moving or removal of exports if at all possible, or making it painful to do so because that would require a rebind of all dependent programs and service programs. It would be nice though if RDi could handle that though as well, automatically.
In RSE: 1. Right click a library and select new, there should be a few additional objects here: a. ILE Program b. ILE Service Program c. Binding Directory 2. A prompt dialog for the appropriate command is opened, and attribute values are stored in meta-data somewhere, perhaps the IFS. For example: a. for New ILE Program, prompt CRTPGM b. for New Service Program, prompt CRTSRVPGM c. for New Binding Directory, prompt CRTBNDDIR 3. Additional meta-data would need to be stored: a. for New Service Program store variable and procedure exports used to generate Binding Language b. for New Binding Directory store modules and service programs to be referenced in the binding directory 4. When I right click an ILE Program, or Service Program in RSE I should be able to choose Build, and it will either Create or Update the object based on whether it exists or not in the library. That means that the RSE should list the meta-objects as well as the real objects associated with the directory. this could be a filter option. Once the object is built, it should show up as a real object instead of a meta-object. 5. This could be used for other non-source objects such as Data Areas, Data Queues, and User Spaces. 6. I want a way to generate, save, and update the meta-data for an object that already exists. 7. Binding Language should be maintained automatically based on exports specified in the meta-data. 8. The tool should make it easy to enforce best practices such as: do not change the order of exports, or their parameters, Just use a non-generated signature for service programs, or if using generated signatures, the tool should manage them transparently.
Do not place IBM confidential, company confidential, or personal information into any field.