Expose collocation groups in TSM reporting

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

Thank you for providing more information. This is consistent with our current product direction and is being targeted for a release. This is not a statement of commitment as intent and plans are subject to change. We will provide an update to the request should plans change or the enhancement is delivered. Thank you for your commitment to TSM and for your support in moving the product forward.

More detail provided by requester via private email:

The node / collocation group relationships only need to be exposed in the TSM reporting (TCR) environment. So for example, we have occupancy reported for each node in TCR but we don't have the node groups or which nodes are in those groups. So as a result you can't produce a report that summarizes the node occupancy by node group. Node group would be used to group by what ever business function the customer determines as important, such as LOB, contract, location, customer, etc.

The fundemental problem with reporting is that all the statistics and relationship information available in TSM are not being transferred to TCR. This means customers who have specific queries can't use TCR. They don't want to have to write command line queries and custom scripts that run against each TSM server to capture information, that's old school. They want to do those queries off line in TCR and send the results to whatever people, in whatever format, and whenever they need to. Customers get really frustrated when they can't recreate a custom report in TCR and give up - despite all the great information already available in TCR...

For example, recently one customer noted that the information from the q filespace command is not captured in TCR. So they can't report on the last back up date of a filespace. This is important because a filespace in unix can get unmounted and the backup schedule is successful but the backup is incomplete. I asked them to open an RFE.

Another example, customer noted that the Registration Date/Time was not captured in the with the node information in TCR. They would have produced reports based on that date to verify that the backup processes were working properly for the nodes added in a certain time period.

Thank you submitting this request. We do apologize for the delay in our response. Unfortunately, based on the information provided, there is not enough detail for our assessment teams to understand what problem the customer is trying to solve with the proposed solution. It would be helpful to provide in any enhancement request, the nature of the problem and the business justification or impact related to the problem. In some cases, the proposed enhancement request may not be the best solution or the solution our teams devise may be off the mark given an open interpretation that could be inferred from the current articulation of the request. Please provide as much detail as possible so we can assess this request more informatively. Thank you for your input and desire to continue to move our product forward.