IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 z/OS
Categories Communications Server
Created by Guest
Created on Jun 14, 2024

RELATED IDEAS

Allow option for V TCPIP,,SYSPLEX,QUIESCE to persist across IPLs

We use the V TCPIP,,SYSPLEX,QUIESCE,TARGET command as part of a high availability strategy to isolate a problem LPAR and remove it from distribution. This works well, but the status is reset when TCPIP is restarted. We would like the ability to allow this status to persist across a restart/IPL such that if an IPL is needed to clear the incident, we would want to verify that the problem has been corrected on this LPAR before resuming distribution.


This can currently be achieved, but the methods are very cumbersome, such as tinkering with the target XCF addresses on the distributing stacks or preventing the stack from joining the group automatically, but these methods have risks and many complications. It would be much easier if the target LPAR were in a quiesced state at startup.

Idea priority High
  • Guest
    Reply
    |     Aug 15, 2024

    I see that something like this has been implemented with z/OS 3.1 - the ability to pause distribution when the LPAR comes up. This, however, for our purposes would be exponentially more useful at the receiving end rather than the distributing end. If you recycle/IPL a problem LPAR during business hours, you would want that LPAR to come up quiesced and not receive work regardless of where the distributor is. Putting this control point at the distributor is perhaps easier to implement, but makes it all or nothing. If you have 6 systems you are distributing to, instead of taking 1 out, you take 5 out by pausing distribution.

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.