Integration
This is an IBM Automation portal for Integration 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 updates on 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
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.
This sounds great from a developer point of view, but for the customer the product should support the features of the OS it is running on.
> The proposition suggested in this idea does not work on all OSes and also requires manipulating crontab config files, which is not optimal.
Also:
>requires manipulating crontab config files, which is not optimal.
This doesn't make any sense, the product is already manipulating the main crontab file, the same information can go into a specific file in /etc/cron.d - at that point updates and removal are trivial since you don't have to deal with other lines in the file
I just voted for this. Would like to see this as well. The standard of using cron.d has been around for ages and ages. Using cron.d is the right way to automatically deploy cronjobs like this.
We do not consider changing the way of scheduling tasks by ILMT Disconnected Scanner in close future, but we will keep this requirement in the backlog to monitor interest/votes and design an acceptable approach. The proposition suggested in this idea does not work on all OSes and also requires manipulating crontab config files, which is not optimal. The dev team will be seeking potential other options to address this requirement.
Hi Team, Kindly provide ETA for requested change.