Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Delivered
Workspace IBM i
Categories Core OS
Created by Guest
Created on Jul 26, 2017

Enable Programmatic End of Batch Restricted State where an end to Batch restricted State has not been reached.

Introduce an API component that will allow for a Batch Restricted State to be terminated from within a BRS job/program without recourse to PWRDWNSYS or Option 14 of the DST Environment.


Use Case:

Where a Batch Restricted State is requested (during SAVE 21 for example) if the BRS needs to be terminated, especially if a Restricted State has not been effected in an appropriate time frame, the only recourse is to use PWRDWNSYS or Option 14 from DST. Both cases require operator intervention. Where a BRS is enacted on a Hosting LPAR, then PWRDWNSYS will not only re-cycle the Host LPAR, but cause all Client LPARS to fail, and in a very dangerous way. These methods negate any real automation for these system tasks and are not very safe or good practice. We are attempting to implement as much automation as possible, and attempt to reduce the amount of time taken for system management functions providing greater end user access, especially in relation to web applications. The current BRS cancellation methods do not achieve that goal.
Given that it would appear from the DST Option 14 method, that there are already routines in the OS that can force a BRS state to end, then it would seem appropriate to allow that process to be able to be accessed from within a BRS job/program.


Idea priority High
  • Guest
    Reply
    |
    Oct 9, 2017

    We added a new parameter to the ENDSBS command for use by BRMS to allow jobs to be ended abnormally to get into restricted state.

    Abnormal end delay time (ABNENDDLY) - Help

    Specifies the amount of time (in minutes) that is allowed for the
    immediate subsystem end operation to complete. If this amount of time
    is exceeded and the end operation is not complete, any jobs still being
    processed in the subsystem are ended abnormally. If a job is ended
    abnormally, the next system end is marked as abnormal. The delay time
    may be extended if there are jobs with SIGTERM handlers active that have
    not ended.

    *NOLIMIT
    The amount of time in which to complete an immediate end is not
    limited.

    10-999
    Specify the number of minutes in which the immediate end operation
    is allowed to complete.

    The new parameter is available in 7.3 and 7.2.