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 Not under consideration
Workspace GDPS
Created by Guest
Created on Jun 19, 2017

Support of INGREQ Type=NORM/IMMED/FORCE

In System Automation three different Types are supported by INGREQ to stop a system or application (NORM,IMMED,FORCE). GDPS only supports TYPE=NORM by default. We would like to get a parameter where we can specify Type=NORM/IMMED/FORCE each time we shut down a system by Standard action panel and by scripts.

Idea priority Medium
  • Guest
    Reply
    |
    Aug 5, 2022
    After giving the request a comprehensive review, we have determined that we cannot include it as a candidate in an upcoming release because it won't be pursued within our planning cycle.
  • Guest
    Reply
    |
    Nov 16, 2018

    N/A

  • Guest
    Reply
    |
    Nov 7, 2018

    High priority, we use INGREQ Type=NORM & FORCE depending of the system IPL's and have at the moment an own workaround to change the INGREQ Type as needed. We would like to have this functionality in GDPS.

  • Guest
    Reply
    |
    Nov 6, 2018

    N/A

  • Guest
    Reply
    |
    Sep 20, 2018

    Low priority

  • Guest
    Reply
    |
    Sep 20, 2018

    We are interested but not a top priority to actually vote for this.

  • Guest
    Reply
    |
    Sep 4, 2018

    I think this is dangerous. Not keen.

  • Guest
    Reply
    |
    Aug 31, 2018

    Low priority / not in the 2 year requirements threshold described in RFE voting process doc

  • Guest
    Reply
    |
    Aug 27, 2018

    Very high priority.
    We have exactly the same requirement. At the moment we use a "INGSET SET */APG/S02 STOPTYPE=FORCE OUTMODE=LINE" command before we make the STOP command as workaround solution.
    I would like to change the INGREC to IMMED or FORCE dynamically from a command line but also in a planned or takeover script

  • Guest
    Reply
    |
    Dec 15, 2017

    Actually GDPS should permit a means of specifying all of the ingreq parms. There are reasons individuals are using these functions.

    Such as the Override function. This used to be there but was removed and it should not have been. These are user functions and should not be disallowed by IBM.

    The current response is to code an exit to override all these things, but why should the customer have to build an exit to use standard IBM functions.

    All aspects of the INGREQ should be controlled via GDPS PARMS or AAO's