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
Created by Guest
Created on Nov 4, 2020

Develop *USER Activation Group

ACTGRP(*NEW) vs ACTGRP(<myname>) is a bit challenging to beginner to intermediate RPG developers. It would be useful to have something like ACTGRP(*USER) that works like a named activation group. Specifically to avoid programmers using the DFTACTGRP(*YES) or ACTGRP(*CALLER) to the *DFTACTGRP. This new "named" activation group would be named *USER and provide consistency across all IBM i installations. This is similar to what we talked about during development of ILE and the ACTGRP named QILE, except it would have more adoption. The *USER activation group would be automatically started when the job is started to avoid that bit of overhead.

Use Case:

I have an app that needs to run in an Activation Group and I don't want the overhead of ACTGRP(*NEW) but also don't want to specify a hard-coded ACTGRP name, such as ACTGRP(QILE). Instead of I would specify ACTGRP(*USER) which would work like any named activation group but already be started when the job is invoked.

Idea priority Medium
  • Guest
    Jan 25, 2021

    One objective that may not have been clear, is to encourage RPG developers to use something other than *DFTACTGRP. Currently many use DFTACTGRP(*NO) and ACTGRP(*CALLER). Which effectively means *DFTACTGRP. Given them something tangible they can easily understand without "learning ILE" could be beneficial to performance and resource scoping. So it would be nice to reconsider the "declined" status.

  • Guest
    Jan 7, 2021

    IBM does not intend to provide a solution to this request at this time, so it is being closed. While the proposed *USER activation group may provide some simplification, there is a work around of using a naming scheme and named activation groups, which will provide similar functionality.

  • Guest
    Nov 9, 2020

    Just to add clarity to the functionality of this request... When a Job is started, it will start 1 or more named activations groups identified as *USER, *USER2, *USER3, etc.
    Should the end-user job issue the RCLACTGRP ACTGRP(*USER) command, then activation group *USER would be ended, and upon the next program that uses it, it would be restarted within the job.
    The request is specifically for a *USER activation group however a system value of QMAXUSRAG would be nice to allow end-users to establish the number of *USER activation groups to start in each job. For example if QMAXUSRAG = 3, then *USER, *USER2, and *USER3 would be started. There would be no *USER1. This system value would be shipped with a value of 1, but also allow a values of 0 (alternatively *NONE is fine too).

  • Guest
    Nov 9, 2020

    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 - Application Development
    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 - Core OS
    Operating system - IBM i
    Source - None