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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
It would be nice on the CRTSRVPGM command to have an option other than *BLANK for the TEXT parameter.
The default could remain as *BLANK, but the ability to change the command default to one of the following would be great!
Examples:
*MODULE - This will grab the text from the module (if only one is specified). It could also grab the text from the first module listed if multiple are used.
*FIRST - Grab the text from the first module listed.
*LAST - Grab the text from the last module.
*MODULEn or *n - Grab the text from the "nth" module.
*EXPORT or *BND - Match the text from the binder language source member.
CRTSRVPGM SRVPGM(MYLIB/FUNCTIONS) MODULE(*SRVPGM) TEXT(*MODULE)
This would create the service program using the text from the MODULE named FUNCTIONS.
Idea priority | Medium |
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.
.This is available in IBM i release 7.4.
IBM agrees with the request and a solution appears to be desirable and feasible. IBM intends to provide a solution. However, IBM's plans may change and no commitment is made that a solution will be provided.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Application Development
Operating system - IBM i
Source - Other
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Languages - RPG
Operating system - IBM i
Source - Other
I am very much in favor of the options *MODULE (for the first or only bound module text) and *EXPORT (not *BND or *BNDSRC). But I would also like to see *SRVPGM to pick up the TEXT from an existing service program, if any, of the same name in the target library before replacement. These three options cover and refer back to the first three parameter names on the command -- which also makes them more self-documenting (i.e., mnemonic).
I tend toward TEXT(*BNDSRC), because the binder source pertains the the exported functions of the service program, whereas any one module's text might not reflect enough of the function of the entire service program.
There is merit to TEXT(*FIRST) - especially in those situations where there is only one module in the *SRVPGM. Although I personally wouldn't probably use it, TEXT(*MODULE) TEXTMOD(module_name) would make the TEXT() support more complete.
TEXT(*CURRENT) would be quite nice.
I think a logical choice is to allow an option to use the text on the binder source member. I definitely would prefer this option. It's explicit and doesn't afford opportunities to be changed by accident--e.g., a when module is added.
Another good option would be *EXISTING to allow the existing comment to be used.
Prefer the *Module option only.
I would like to add: *MODULE or *MODULENAME, which would then require entering a module name to use as the source of the text.
Maybe another parm like Textopt(*text) that also supports the module name whose text you want, plus supports *FIRST and *BNDSRC.
I would really like to see this BUT ...
Personally I don't like the *First, *Last, *Module, and *Modulen options (particularly that last one). They strike me as accidents waiting to happen. Taking it from the binder source would make a lot of sense and, for those who build all SPs from a single module, perhaps *Only would be an appropriate option to have the text taken from a module. Having *First and it only working when using a single module I just don't like - too prone to causing problems later on.