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 Future consideration
Workspace IBM i
Categories BRMS
Created by Guest
Created on Sep 9, 2025

Lack of BRMS auditing

BRMS does not log changes made to backup control groups, policies, and other configurable options into a specific table or journal. Having BRMS log changes to backup control groups, policies, and other configurable options into a dedicated table or journal is essential for maintaining strong audit capabilities. Without this logging, it becomes difficult to track who made modifications, when they occurred, and what was changed—leaving gaps in accountability and compliance reporting. From a security perspective, unlogged changes create opportunities for misconfigurations or malicious alterations to go unnoticed, which could compromise backup integrity and recovery processes. Implementing detailed change logging aligns with industry best practices and regulatory requirements, ensuring organizations can demonstrate proper governance, detect anomalies quickly, and safeguard critical data assets.

Idea priority High
  • Guest
    Nov 10, 2025
    The BRMS team will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. The BRMS team will use votes and comments from others in the community to help prioritize this request.