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.
MAXRUNTIME is a poor option because it only works on single commands in the background.
If the admin schedule runs a script, or a WAIT=YES command, then it will not kill.
It's not actually a maximum run time, rather, it looks for the process ID and sets up a kill after. But if the process is never backgrounded, then it will not look until after the process is done, no matter how long it takes.
For REPLICATE NODE, a second schedule can be created with "CANCEL REPLICATION". This does not work for any of the multitude of reasons REPLICATE NODE can hang; however, as long as REPLICATE NODE is behaving properly, the CANCEL REPLICATION will kill the master process and all of the secondary sessions will terminate once they get to a checkpoint.
Having a DURATION flag on REPLICATE NODE might be nice, but it would create additional polling inside the process, where an extra admin schedule would be part of the existing system.
This can be accomplished using the MAXRUNTIME parameter of a scheduled admin command.
When the TSM administrator schedules a REPLICATE NODE command, they can specify the MAXRUNTIME of the schedule. If the process for the REPLICATE NODE is still running and has met the MAXRUNTIME value, then the process gets cancelled.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family