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 Submitted
Created by Guest
Created on Jun 23, 2025

enable all deviceclasses in "del volhist t=dbb" command

When removing dbbackups via deleting volumehistory there is no possibility of retaining certain older backups in other device classes. The "del volhist t=dbb" doesn't recognise non-server deviceclasses. This would be a welcome addition for enabling a second retention layer in tsm without using external scripts.

Idea priority Medium
  • Guest
    Jun 27, 2025

    We want to establish a daily and monthly maintenance schedule each with a "backup db" command going into different tape device classes. When calling "del volhist t=dbb" from within tsm, all dbbackups get deleted in accordance with the todate/totime parameters. The different device classes aren't considered at all.

    following example is what it should look/work like:

    daily schedule:

    backup db devcl=DBBACK_TAPE_DAY type=full wait=yes
    del volhist type=dbb devcl=DBBACK_TAPE_DAY todate=-7

     

    monthly schedule:

    backup db devcl=DBBACK_TAPE_MONTH type=full wait=yes
    del volhist type=dbb devcl=DBBACK_TAPE_MONTH todate=-365

  • Guest
    Jun 25, 2025

    The usecase is not clear here. Can you please help elaborate what you are trying to achieve using 'delete volhistory' command?

    https://www.ibm.com/docs/en/storage-protect/8.1.27?topic=commands-delete-volhistory-delete-sequential-volume-history-information

  • Guest
    Jun 23, 2025

    Very good idea!
    I would welcome a feature like this.

    Peter