IBM System Storage Ideas Portal
This portal is to open public enhancement requests against IBM System Storage 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.
Gotcha! Yes that makes sense. thank you for submitting the Idea!
Thanks for your quick answer!
What I'm asking for is the ability to specify a timeframe for the execution of an operation, not for a end of the whole action/command.
Independently of which timer type is established, we want to be able to force o CSM a time limit within which the action/command can be executed and send instead an alert if the timeframe expires while not stopping the scheduled operation calendar, just mark that occurrence as "not-executed" and skip to the next one.
For example, if we want to perform a "Flash" command for a session at 21.00, be able to establish that the command can be issued from 21.00 up to 21.15 but not later.
And this request is valid for either "hourly/daily interval timer" or "timer running at fixed times on selectable weekdays".
I hope I made myself a little more clear, thanks, Rina
thanks for the request. I believe you're asking for a way to set a "run schedule up until this date and time". Something similar to how you can specify an end date/time on a reoccurring calendar entry. Please confirm that this is actually what you're requesting.
As for the comment you added to this Idea. Sounds like you're seeing a behavior that you believe is incorrect. Can you please be sure to open an Issue for this so that this can be reviewed and fixed if determined to be a defect. Issues and Ideas are tracked differently so I want to make sure that if there is an issue here that it gets addressed. Thank you!
This actually appears to be a defect.
There are 2 different timer types you can define in scheduled tasks:
An hourly/daily interval timer (OK)
A timer running at fixed times on selectable weekdays (Problem)
The hourly/daily interval timer behaves correctly. When CSM starts and finds a missed run for this timer, it just posts a Warning for the missed execution and calculates the next run time with the selected interval time in the future. Past interval times are skipped in the calculation.
The other timer calculates the next run time incorrectly. It also puts a warning on the missed task, but the next run time is set to the next selected day. If an active CSM server was down for a couple of days (which could happen if there are server issues), the next run of such schedules could be set to the past and since overdue, repetitive task executions could be performed until next runtime is set to a future day. This needs to be addressed and fixed.
I would assume that normal behavior (missed task run times are skipped and NOT executed apart from their schedule) is the most common use case.