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 Future consideration
Created by Guest
Created on Jul 13, 2023

Handle LTO9+ initialization process with parallellisation

I would like a dedicated command added to the SP server admin client for initialization of LTO9+ volumes. I have seen TL43-I-23, but doing it in SP makes it work for all libraries, not just TS.

When we first took the LTO9 library in use, I scripted the initialization process to use all drives in parallel through the library's own API. However, now that it is in production, I can not just grab a bunch of drives and media without TSM knowing about it - that would predictably lead to problems.

I have since used LABEL LIBV to good effect, however:

 * label libv is strictly serial, and initialization of a volume can take up to 2 hours as per spec. 

 * label libv blocks any checkin, checkout and move drm commands - so a typical maintenance script is going to hang until the label process is done.

I would suggest either a new command or a change to label libv with the following features:

 * specify the number of drives to use in parallel

* allow optional mountpoint retention

* allow for using more or less drives as they are available (unlike label libv which ends if it can't get a drive)

* prevent interfering with move drm commands, as those are not going to be touching yet-to-be-initialized volumes anyway

Idea priority Medium
  • Admin
    Juan Carlos Jimenez Fuentes
    Reply
    |
    Jul 14, 2023

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.