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 20, 2012

Update Behavior of TSM Node Fields

The update behavior of several Node fields seems to be strange.
e.g. The Field LASTACC_TIME is defined as the "The last date and time
that the client node accessed the server".
When a node with nodename NodeA tries to logon to a tsm server the
server updates the following fields of the registered node NodeA
(LASTACC_TIME, TCP_ADDRESS, TCP_NAME..... and maybe more). It updates these fields
regardless of whether the logon was successful or not.
The export of a node to another server reset the field to the date/time
when the export was started.

So the field LASTACC_TIME is therefore more describing The last date
and time someone tried to
logon with the same nodename

Instead of updating the fields with values which don`t belong to the
registered node it would be more useful to have a log entry that tells
us that someone from ip-address xxxxxx tried to logon with nodename
NodeA.

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
    |
    Feb 5, 2013

    Update will be in TSM 7.1