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.

Add a new idea Subscribe
Status Delivered
Workspace IBM DS8000
Created by Guest
Created on Feb 4, 2016

RELATED IDEAS

Gathering PPRC status information should not rely on SITE A

The PPRC status information gathering should not rely on SITE A.

Idea priority Medium
  • Guest
    Reply
    |     Sep 11, 2017

    The use case is like: Site A PPRC to Site B. There could be some reason that PPRC get suspended. Current design is that PPRC status information can be gotten from Site A from disk subsystem or by GDPS/PPRC K system. However, if there is any communication problem between site A and B, the operator in site B could not get accurate status of PPRC from only site B disk subsystem.

    If ZDL implementation, the long leg PPRC target for DB2 log is deployed in Site B. It is extremely important because all data replication rely on this PPRC link. Then monitoring the status of this long leg PPRC become critical for ZDL solution.

  • Guest
    Reply
    |     Feb 6, 2016

    Creating a new RFE based on Community RFE #83550 in product IBM DS8000.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.