Skip to Main Content
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.

Status Not under consideration
Workspace z/OS
Created by Guest
Created on Aug 2, 2012

Vipadistribute "WLMSTANDBY"

As the options for VIPADISTRIBUTE DISTMETHOD have evolved over time, we have a new scenario that I'm not sure the current options can handle. In a case where we might have a m LPARs at one site and n LPARs at a second site, with our sysplex spanned between, it may be the case for performance or other reasons that I want my workload distributed amongst all of the servers at site A first (via WLM or whatever) and then site B only if all of the site A LPARs are down. HOTSTANDBY gives a similar method for a weighted backup ordering, but it appears to limit a single stack to be the active target at any one time. Curious a mash-up of WLM and HOTSTANDYBY could be created that lets me define a list of DESTIPs for WLM routing and a second (or third) list of DESTIPs that only come into play when the entire (or maybe a percentage, my choice) of the previous "pool" is not available.

Idea priority Medium
  • Guest
    Reply
    |
    Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS Communications Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Networking
    Product - z/OS Communications Server