IBM Z Software
Hide about this portal


This portal is to open public enhancement requests against IBM Z Software 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 Not under consideration
Workspace GDPS
Created by Guest
Created on Jan 16, 2017

RELATED IDEAS

LPAR/System Status Tracking within GDPS

See this idea on ideas.ibm.com

GDPS will keep track the statu of the LPAR/System and display in the Standard Actions Panel. When a user perform an action against a LPAR/system, the status will change accordingly (e.g. after using GDPS to activate an LPAR, the status will change to ACT-ED). However, currently the status of the Site 1 and Site 2 LPARs are not kept separately and when we perform an action against the Site 2 LPAR using GDPS (by selecting the ABNORMAL entry in the GDPS Site Table), the status of the LPAR/system in Site 1 will change even we select the "NORMAL" entry in the Site Table after the required action for Site 2 LPAR is done.

GDPS should keep the status of the LPAR/system in Site 1 and Site 2 (NORMAL/ABORNMAL entry in Site Table) separatley and only update the status of the LPAR/system after an action is perform against the LPAR in corresponding site.

Idea priority Medium
  • Guest
    Reply
    |     Apr 27, 2024
    After giving the request a comprehensive review, we have determined that although we agree that the proposed enhancement is desirable, we cannot include it as a candidate in an upcoming release because it cannot be delivered within our planning cycle.
  • Guest
    Reply
    |     Feb 10, 2017

    Medium priority. It is important that the GDPS reflects the real scenario at DR.

  • Guest
    Reply
    |     Feb 9, 2017

    Low – Could be helpful at some situations. We have covered most of such situations with planned/unplanned scripts.

  • Guest
    Reply
    |     Feb 9, 2017

    Medium

  • Guest
    Reply
    |     Feb 6, 2017

    An interesting problem, although we haven't had a case to encounter it. Seems to require a different "keying" mechanism for tracking. Might find a use for it, yet.
    Medium is my vote

  • Guest
    Reply
    |     Feb 3, 2017

    Medium - Consistent tracking is always of importance, so correct and meaningful display are a must, especially at DR time.

  • Guest
    Reply
    |     Feb 3, 2017

    See this as low priority item as there would be risks around this as well as benefits.

  • Guest
    Reply
    |     Feb 1, 2017

    It is interesting.

  • Guest
    Reply
    |     Feb 1, 2017

    This option reduces the time to move systems to their backup LPAR and is helpful in DR test scenarios.

  • Guest
    Reply
    |     Jan 30, 2017

    Medium - Having the capabilities of managing the LPARs independently would be beneficial.

  • Guest
    Reply
    |     Jan 25, 2017

    Low priority.

  • Guest
    Reply
    |     Jan 25, 2017

    We also think it is an advantage to be able to activate the ABNORMAL LPAR's in case of a DR-test before shutting down production systems in their NORMAL LPAR's.

  • Guest
    Reply
    |     Jan 24, 2017

    LOW

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.