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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Is a defect
Created by Guest
Created on Nov 10, 2023

IBM CSM API Should Show all DS8 Session/LSS/SSID In Hexadecimal to Correctly Reflect The Values on the Hardware

We recently encountered a discrepancy in our API reporting from CSM where the Session ID was not matching what is in the GUI (and on the actual DS8 hardware), and it turned out that from the CSM/web/sessions URI, all of the session/LSS/SSID values are incorrectly in decimal, and from the CSM/web/sessions/SESSION_NAME URI, those some ones are in decimal but it does add a couple other entries which are correctly in hex.

This is misleading to the user, as unless they already are familiar with what are the specific session ID's for each session, or notice that some of the session information returned from CSM is impossible since it is higher than 'FF', they may never realize that CSM is not providing what they think it is.

Here are some examples below for the information for the same session, from the two URIs and what needs to be corrected.

## Output from CSM/web/session ##

"sessionNumber": 127 This should be "0x7f"

"masterLss": 127 This should be "0x7f"

"masterSsid": 65407 This should be "ff7f"

## Output from CSM/web/sessions/SESSION_NAME ##

"sequences"/"progress"/"masterLSS": "DS8000:2107.HXXY1:LSS:7F" This is correct

"sequences"/"progress"/"sessionID": "0x7f" This is correct

"sessionprogress"/"gmStatus"/"masterLss": 127, This should be "0x7f"

"sessionprogress"/"gmStatus"/"sessionNumber": 127 This should be "0x7f"

"sessionprogress"/"gmStatus"/"masterSsid": 65407 This should be "ff7f"

Idea priority Medium
  • Guest
    Nov 14, 2023
    Should add. Will need to make this change as a new variable for each of those entries, to avoid breaking any callers that take the decimal number today already and convert it to hex.

    New values will be masterSsidHex, masterLssHex, sessionNumberHex. The older decimal values will still display.
  • Guest
    Nov 14, 2023
    Would consider this a defect. Will fix this in the CSM 6.3.9 release.