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 updateson 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
Add lsb.params setting to limit the number of times a job can be redispatched upon either a pre-exec failure of job initilization failure
We currently have jobs that will bounce from host to host either based upon a pre-exec failure, or a job initialization failure. This can impact > 500 hosts and cause an increase in MBD memory use.
It would be nice to have a setting such as: MAX_JOB_LAUNCH_FAILURE=20 That would limit the job to 20 start tries before going PSUSP with a suspended reason that the job either could not be launched or the pre-exec failed more than X times.
I know that one of the failure modes is for a user whose user account has been removed causes that same behavior. What's odd is that I know that in Windows, if the users password can not be validated more than X times, the job will go PSUSP, but I'm uncertain if that setting is exposed to the user or not. It seems almost the same thing, but not quite exactly.
Do not place IBM confidential, company confidential, or personal information into any field.