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.
We do disable storage rules in our daily business when we have maintanance windows for dsmserv updates to prevent long running processes operating on physical tape drives. we also do this when we have maint action with physical tape environments. we also disable stgrules when we do maintenance within the external library manager - TSLM. If not disabled proberly before such actions you always have to manually manage orphan tape mounts or isp processes.
but that is not the point. we recommend to disable all stgrules in dsmserv maint to do it like it is already implemented with admin schedules. or the old "nomigrecl". there are two key points. first is after a isp upgrade we start the dsmserv with maint - in this scenario you do not want to start stgrules like audit, protect or tiering. you want a isp that is only starting, but not operating with processes/stgpools/stgrules/admin-sches. second is when you have restored a isp server via dsmserv restore db......after you have done the restore, the best way is to start dsmserv in maint to prevent client sessions to start. you only want to audit your stgpools, repair your containers, audit your tapes - you do not want to have additional stgrules running during stgpool recover.
in such situations you do not want to disable stgrules as "special point" - you want it disabled automatically.
How often do we disable storage rules? We need more information around why this is necessary. Please expand in the comments below.