IBM Z Software


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 Future consideration
Workspace GDPS
Created by Guest
Created on Oct 6, 2023

RELATED IDEAS

GDPS should recover from secondary dynamic pathing problem

After problems on the secondary Metro Mirror devices due to maintenance on channel paths, following messages occurred:

IOS210I PATH RECOVERY INITIATED FOR PATH xx on CU yyyy REAS PATHING ERROR and

IOSHS0010I DYNAMIC PATHING IS NOT INITIALIZED FOR PPRC SECONDARY DEVICE 1xxxx

The hyperswap status remained NOK on 3 LPARs that had access to those channels even after running Monitor 2. It was necessary to run HYPERSW OFF/HYPERSWON .

It would be nice to have Hyperswap status re-enabled after such disruptive events occur because if a hyperswap occurred in that timeframe, those LPARs would have been reset.

Idea priority Medium
  • Guest
    Reply
    |     Jan 31, 2024

    Yes, GDPS should handle situations like this autonomically.

  • Guest
    Reply
    |     Jan 29, 2024

    FIS/Worldpay agrees.

  • Guest
    Reply
    |     Jan 18, 2024

    We never experienced this issue, but looks like a deficiency to be fixed.

  • Guest
    Reply
    |     Jan 17, 2024

    The idea is a good one. GDPS being able to self correct without operator intervention is always good, provided all is OK in the environment and HYPERSW OFF/ON can be issued .

  • Guest
    Reply
    |     Jan 17, 2024

    I agree with the other comments. If GDPS could issue the HYPERSW OFF/ON, then it should.

  • Guest
    Reply
    |     Jan 16, 2024

    We specify in IECIOSxx -

    RECOVERY PATH_SCOPE=CU,DEV=DASD,LIMITED_RECTIME=10

    Would a solution affect the recovery here?

    Otherwise, the Idea seems a very good one.

  • Guest
    Reply
    |     Jan 16, 2024

    HYPERSW OFF/ON is not good for the SLA. GDPS must monitor relevant messages, and once received, immed fix the status.

  • Guest
    Reply
    |     Jan 15, 2024

    When GDPS can handle it itself, than it should do. Therefore I vote for this Idea.

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.