This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
I am creating a scheduled job to perform regular REORGs of the Db2 Catalog.
I am generating a list of catalog objects and feeding it to LISTDEF and then using ITEMERROR,SKIP
I am using extremely gentle DRAIN settings...DRAIN_WAIT of 2 or 3 seconds. When this job runs, I want it to ATTEMPT to drain the catalog objects as it REORGs them, but if it CANNOT get the DRAIN, I want it to just move on. We would be running the job frequently enough that we would just "get it next time".
ITEMERROR,SKIP does this...but it sets the final RC of the REORG step to an "8".
I don't want the job to set an "8" just because some SPUFI user forgot to COMMIT and sign off after querying the catalog, and have Batch Scheduling calling asking "what's wrong with the job??".
So what I'd like to see...is a command or option for REORG where you can tell it, "IF a SHRLEVEL CHANGE REORG fails solely because it couldn't get a DRAIN, set the RC for that step to '4' instead of '8'".
This would occur ONLY if the job failure is SPECIFICALLY due to inability to complete a DRAIN. All other errors would still set an "8" for the final RC.
This would allow scheduled REORG jobs to REORG whatever they CAN get a DRAIN on, and if they CAN'T get a DRAIN, just skip that object, and those routine jobs could return RC4 instead of RC8, to avoid alerting Scheduling to a problem that isn't really a problem.
Needed By | Not sure -- Just thought it was cool |
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.