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:
Post your ideas
Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
Compiler: Replace object without moving existing object to QRPLOBJ
We have a LPAR which is used as a build server for ILE objects. Therefore the LPAR will only execute compiler commands, save the created objects and send them to another server. The compiled objects will never be used (called) on this LPAR.
When we do a build of our software the generated objects has a size of 30GB. So every build will fill the library QRPLOBJ. To clean up the library QRPLOBJ we have a job that executes CLRLIB QRPLOBJ every 5 minutes. But when CLRLIB is in execution some compiler jobs will go into job status LCKW when it wants to move the existing object to QRPLOBJ. When LCKW reaches the default wait time and QRPLOBJ is still locked the object will be moved to QTEMP (CPI2118).
To avoid this we want a option to control what to do with existing objects.
Move to QRPLOBJ (the current function when using REPLACE(*YES))
Move to QTEMP (new. Our jobs will be executed from PASE via cmake, therefore the QTEMP object will automaticly cleared after the compile of one object is finished)
Delete existing object (new)
We have no option to delete the existing object before executing the compiler command in our build pipeline.
Do not place IBM confidential, company confidential, or personal information into any field.