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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Nov 21, 2017

ENDJOB OPTION(*IMMED) considered harmful

ENDJOB OPTION(*IMMED) has outlived it's usefulness. Modern code contains more subtle locking then in days past & often has exit handlers to perform cleanup. This is true of both client & IBM code (I'm looking at you, SQE). End *IMMED ends up causing too many zombie processes & dangling resource locks.

Use Case:

Go ahead and keep OPTION(*IMMED), but convert it behind the scenes to OPTION(*CNTRLD) DELAY(10) , or whatever delay you deem appropriate.

Idea priority Medium
  • Guest
    Feb 16, 2018

    We do not plan to make this change. ENDJOB *IMMED does not prevent cancel handlers/iexits from running. Using ENDJOBABN can cause cancel handlers to be ended abruptly or not called, and for this reason we do not allow it to be used unless ENDJOB has first been issued against the job, and cancel handlers have been given enough time to reasonably complete.

  • Guest
    Jan 29, 2018

    Yes, I understand you can not assert authority on a command parameter. Rob has suggested the use of an exit point to accomplish this. I second that suggestion.

  • Guest
    Jan 29, 2018

    All powerful tools can be harmful when used inappropriately. However, sometimes these powerful tools are necessary. If you have folks that are not skilled enough to use them safely, remove their authority to those tools. But please do not try to protect me from your novice operators.

  • Guest
    Jan 19, 2018

    A workaround until the arrival of Nirvana is to use a command exit point to change all *IMMED's to *CNTRLD and add a delay time. Search for QIBM_QCA_CHG_COMMAND. I've used this to:
    - Change SNDDST to SNDEMAIL.
    - Automatically generate a PDF of the joblog and email it to me whenever SIGNOFF is used and the user is QSECOFR

  • Guest
    Jan 2, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Core OS
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Availability, Recovery
    Operating system - IBM i
    Source - None