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

Status Future consideration
Workspace GDPS
Created by Guest
Created on Oct 12, 2021

Improvements to the GROUP keyword used in the SYSPLEX verb

We would like the ability to have enhanced selection criteria for the GROUP statement in the SYSPLEX verb.

As an example during Site Switch, we shutdown the whole of a SITE with the exception of certain systems, it would be useful to have a statement capability thus;

SYSPLEX STOP GROUP=SITE1 EXCEPT=system_name(s)

We would like this capability extended to all verbs where the GROUP keyword is useable.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 28, 2022

    n/a for the time being

  • Guest
    Reply
    |
    Jan 27, 2022

    Priority for SF.

  • Guest
    Reply
    |
    Jan 27, 2022

    We do not use the group keyword - Barclays

  • Guest
    Reply
    |
    Jan 27, 2022

    We do not currently use the GROUP keyword, but this would be low priority.

  • Guest
    Reply
    |
    Jan 27, 2022

    We don't have a scenario that would use this particular capability

  • Guest
    Reply
    |
    Jan 13, 2022

    We do not currently use the GROUP statement due to the reasons listed in the description, so this would be useful in our environment.

  • Guest
    Reply
    |
    Jan 7, 2022

    Potentially useful but very low priority for LBG.

  • Guest
    Reply
    |
    Jan 4, 2022

    WFC believes this would be useful but of low priority to us specifically.

  • Guest
    Reply
    |
    Jan 3, 2022

    This RFE does not apply to Worldpay/FIS.

  • Guest
    Reply
    |
    Dec 30, 2021

    We currently have similar requirements on our test environments for validation.

    In order to provision minimal loss of data such as logs we shutdown all systems in the plex except one. on the last one we perform other activities and then reset it.

    This means we have several statements to manage the Group function instead of just having 2 statements 1 for the majority of the plex and then one more to reset the last system.

    This could be useful in reducing procedures and script management.

  • Guest
    Reply
    |
    Dec 23, 2021

    Maybe consider an additional column in Standard Actions to enable each system in SITEn to be sub-grouped (e.g. "A", "B" , stc), and then use -

    SYSPLEX STOP GROUP=SITE1 EXCEPT_SUBGROUP=groupname(s) or INCLUDE_SUBGROUP=groupname(s)

    Regards,
    Kevan