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
Add binder source prompt to CRTSQLRPGI for lib/file(member)
Allow binder source file other than QSRVSRC for CRTSQLRPGI command when creating a service program object. All other methods for creating service program objects allow the binder source library/file/member to be specified. This allows binder source to be organized along with other application source for different ILE language types. This is NOT the case with ILE SQL service programs created using the CRTSQLRPGI command. It will only locate the binder source when it resides in a QSRVSRC source file within the library list and the member name must match the resulting service program source name for the create command to complete successfully. This is a complete departure from the other ILE languages and a major step backward for what is arguably the most important development language on the system.
Actor: ILE Developer
1. Prompt CRTSQLRPGI. 2. Select OBJTYPE to be *SRVPGM 3. A qualified prompt appears for library/file(member). Note: Could default to *LIBL/QSRVSRC(*OBJ) for backward compatibility in other environments.
Do not place IBM confidential, company confidential, or personal information into any field.