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 Delivered
Created by Guest
Created on Jan 13, 2012

Update the behavior of space allocation when using DEVCLASS type FILE , when more than 1 directory is specified

The file based device class allows user to specify more than 1 directory as destination to store TSM volumes. When you specify more than 1 directory, spread over multiple file system, you can have error message reported (ANR8785E) saying that we're running out of space in one of the available direcories in the device class. The point is that there is available space on others directories/file systems so this error messages is reported "by mistake", and TSM is aware about that because is trying to write data on others of the directories specified in the device class. I 'd like that TSM spread the volumes over the directories first, then test if he is able to store data on a directory/file system, and if not, he tries on another one, and if all the directories/file systems are out of space, so he can raised an alert (ANR8785E) .

Idea priority Medium
  • 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 24, 2012

    TSM does check available space prior to allocating it in a file devclass.  The use of space triggers can allow for earlier notifications of space shortage because volumes are pre-allocated when space usage thresholds are reached. Space Triggers are documented under the DEFINE SPACETRIGGER command.


    The problem here may be that the multiple directories may be within the same file system  - we document to customers in the DEFINE DEVCLASS ( for FILE ) command the following:


    Tip: If you specify multiple directories for a device class, ensure that the directories are associated with separate file systems. Space trigger functions and storage pool space calculations take into account the space remaining in each directory. If you specify multiple directories for a device class and the directories reside in the same file system, the server will calculate space by adding values representing the space remaining in each directory. These space calculations will be inaccurate. Rather than choosing a storage pool with sufficient space for an operation, the server might choose the wrong storage pool and run out of space prematurely. For space triggers, an inaccurate calculation might result in a failure to expand the space available in a storage pool. Failure to expand space in a storage pool is one of the conditions that can cause a trigger to become disabled. If a trigger is disabled because the space in a storage pool could not be expanded, you can re-enable the trigger by issuing the following command: update spacetrigger stg. No further changes are required to the space trigger. 


    Both commands are documented from http://publib.boulder.ibm.com/infocenter/tsminfo/v6r3/index.jsp
    by following:
    IBM Tivoli Storage Manager servers
     Server commands, options, and utilities
      Administrative commands
        DEFINE commands
          DEFINE DEVCLASS
             File
          Or       DEFINE SPACETRIGGER