Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 z/OS
Categories Change Tracker
Created by Guest
Created on Jan 29, 2024

Add more specific archiving policies or workflows

By creating archiving concepts for configuration items, a viable archiving policy is mandatory. Today you have to choose between retention days (x)or a specified number of copies to keep.

This forces the user to choose between two different types of configuration.

If you choose to keep the last 30 days, datasets which have very infrequent changes will archive probably all previous versions of a configuration member.

If you choose to keep the last 3 copies, datasets which get very frequent (i.e. 10 times a day) changes will archive probably very “young” versions of a configuration member.

What’s missing is a combination of both methods.

i.e. “Archive members which are older than 30 days but keep at lease 3 copies”.

The Number of days and copies is configurable. This would fit both use-cases.

There might be more rules to decide weather a backup is to be archived or to be kept as working copy. Also, the archiving process must be automatic and while change tracker is running. There must be no need to stop change tracker for running the archiving process.


Idea priority High