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 IBM Z System Automation
Created by Guest
Created on Sep 29, 2022

RELATED IDEAS

INGGROUP should have a parm to prevent entire group outages

The inggroup now accepts RECYCLE to perform a psuedo rolling recycle of the group. You can specify CHUNK to indicate how many members of that group should be processed in parallel. The one thing it does not do is ensure that the previous resource that was stopped becomes available prior to stopping the next resource.


We have a SYSPLEX SERVER group with 3 members, all active at the same time across the plex to provide a service.


We can handle 1 or 2 of the members down as the third member will take on the plex transaction.

If we perform maintenance on the application and then issue a INGGROUP RECYCLE,CHUNK=1 the first member is stopped.


During the start the member encounters and error and goes into a Broken status. Automation then proceeds to the next member which also encounters an error and goes broken.

Before the operator is able to intervene the group recycle has disabled the entire application across the plex.


The rolling recycle in its current implementation is dangerous for us to implement due to this issue.


It would be nice to have a parm that indicates the PREVIOUS member stopped must be available prior to proceeding to the next member.


There is a PREPARE MOVE function but that only indicates that a member will not be stopped until a resource is available.



Idea priority High

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.