This is an IBM Automation portal for Cloud Management and AIOps products. 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
We would like to have the option (customer configurable via optman setting or other configuration file) to allow EVERY on schedule to work like EVERY on job in that you would only see the next instance of the schedule in the plan (as well as the previously completed instances). Our business partners have plans to use EVERY 0005 for several schedules that run for 12 hours or so. This generates over a hundred schedule instances per schedule they implement. They don't want to see all the future schedules in the plan. I'm suggesting it behave like EVERY on job or if you have another way to not have all the schedules loaded at plan creation, but more "dynamically" as timing suggests. Happy to have a conversation about this for any questions.
Do not place IBM confidential, company confidential, or personal information into any field.