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 Submitted
Workspace IBM i
Created by Guest
Created on Aug 27, 2024

Add Inherit Rules to IFS journalling

Today when you set up journalling for the IFS the STRJRN command allows you to filter the objects that are to be journalled, however this is a one off request and the inherit rules are not able to be set to allow future filtering of the objects journalled.

When you start journalling against a library you can set the inherit rules, so you can filter what new objects are journalled when they are created in the library, this would be a very good option at the directory level.

Some application have issues when objects reside on the system which should not be there when a start of the application is requested? This means certain IFS objects if replicated via a HA tool can cause the application to fail.

Filtering of the objects on the target before being applied is an option, but it adds significant overhead in terms of LAN, CPU, Disk and memory managing the filters. Every single journal entry has to be mapped against the filter even if it is to be applied or not.

Many applications generate a lot of temporary IFS files which are not required, being able to filter and not journal will save a lot of overhead, things like .log files are common and can grow to a significant size, asking the developers not to place these in a directory with other files that are required to be journalled and replicated is a non starter.

Idea priority Urgent