Skip to Main Content
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
  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.

Status Planned for future release
Created by Guest
Created on Nov 8, 2011

When schedule is missed the database still shuts down

Just to clarify: the issue occurs when the window is missed because the client cannot communicate with the STORServer server (network issue, or STORServer server is down etc.) We consider this to be a flaw because (as you can see in the attached log file) the preschedulecmd executes once the client re-establishes connectivity with the STORServer server and THEN checks the scheduler and says: "Oh, I'm outside the window, I won't back up". But, it brings the database down. This happened during the day (at 11:00 A.M. last week) when all our district users were attached and working and then the preschedulecmd ran (shutting down the database) and all our phones started ringing off the hook. One of our senior techs feels that the "world should be notified of this flaw" which effectively nullifies the value of having the preschedulecmd shut down the database (whether the preschedulecmd is in the client's dsm.sys file or even if it is set up in the STORServer server's command option (effectively handing control over to TSM). But .... no go. Serious flaw that negates the use of the preschedulecmd.

Idea priority High
  • Guest
    Reply
    |
    Jun 12, 2015

    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

  • Guest
    Reply
    |
    Jan 2, 2012

    Thanks for submitting this enhancement request, we plan to address this requirement in a future release of the product. via a PTF

  • Guest
    Reply
    |
    Nov 8, 2011

    Attachment (Description): IBM case 16758 033 000 has been opened.

  • Guest
    Reply
    |
    Nov 8, 2011

    Attachment (Description): The issue occurs when the window is missed because the client cannot communicate with the STORServer server (network issue, or STORServer server is down etc.) We consider this to be a flaw because (as you can see in the attached log file) the preschedulecmd executes once the client re-establishes connectivity with the STORServer server and THEN checks the scheduler and says: "Oh, I'm outside the window, I won't back up". But, it brings the database down. This happened during the day (at 11:00 A.M. last week) when all our district users were attached and working and then the preschedulecmd ran (shutting down the database) and all our phones started ringing off the hook. One of our senior techs feels that the "world should be notified of this flaw" which effectively nullifies the value of having the preschedulecmd shut down the database (whether the preschedulecmd is in the client's dsm.sys file or even if it is set up in the STORServer server's command option (effectively handing control over to TSM).