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
Set Service Program signature via the CRTSRVPGM command
Today, the signature is set by one of the following methods: 1. From the STRPGMEXP SIGNATURE statement of the QSRVSRC source 2. Automatically generated during service program creation if no QSRVSRC is specified or SIGNATURE is *GEN
When using method 2, every time the service program is recreated, all dependent service programs and programs must be updated to the new signature or a exception is thrown.
This request is to enable setting the Service program signature from the CRTSRVPGM command.
Let say we have a service program that we don't want to maintain a QSRVSRC source because we want to EXPORT *ALL. Each time we re-build the service program, the service program is created with new signature, even though its construct is the same, nothing has changed in term of the exports.
A good example is the OpenSSL service program. While re-building it over and over again to make it compatible to the ILE environment, each time we built it, all other programs and service programs must have been re-updated. This makes it very uncomfortable since the OpenSSL lib still had the exact same exports.
Do not place IBM confidential, company confidential, or personal information into any field.