IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Add a new idea Subscribe
Status Future consideration
Workspace IBM MAS - Manage (Base)
Categories System Admin Config/Security
Created by Guest
Created on Jan 8, 2025

RELATED IDEAS

Add ability to define list of jobs that a specific Async crontask is not allowed to run

Problem

==

Currently the async crontasks allow you to specify a list of jobs that they can run.

If no jobs are specified for a particular crontask then that crontask can pick any job to run. It is unclear if jobs specified for one crontask can be processed by another cron where thre job was included in its job list.

There is a risk that the wrong cron could process the job and delay other jobs.

Request

==

Implement crontask donotrun type functionality so the "incorrect" crontask does not handle the work if another cron includes the name of the job.

 

this would be used by administrators to reduce the risk of a system experiencing delays executing scripts because the wrong cron processed the request.

 

Idea priority High
Needed By Month
  • Post comment
  • Guest
    Jan 9, 2025

    For clarity, this is regarding the AsyncImmediateJobCron and AsyncScheduledJobCron cron tasks. These cron task instances take `condition` and `jobnames` parameters, and this Idea is about adding a `donotrun` parameter which would take a list of job names that should NOT be run by this cron task instance.

    In addition, please provide clear documentation on these cron tasks. Particularly, such documentation should explain whether a job name appearing in the `jobnames` for one instance will or will not prevent another instance from processing it.

    Reply

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.