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 DFSMS DSS
Created by Guest
Created on Sep 12, 2023

Zap a cloned zFS file with the correct audit-file id (auditfid) when it is created

Various auditing routines use the zFS supposedly-unique "file id" as opposed to the filesystem names, and have an issue when one or more datasets in the same shared-filesystem plex are using the same file id.  DFDSS is IBM's poster-child for manipulating zFS data--to copy a zFS for a new lpar or to dump a zFS to transmit to a new sysplex.  Yet for some reason, the copy and restore functions of DFDSS pop out datasets with the "parent's" file id.  To correct this, we would need to mount the copied file read-write and run a zFS admin "force" command to update the file id so it reflected the current volume and track location of the clones, and we'd need to remember to do that even with vendor-delivered code.  Why couldn't DFDSS do that internally as the dataset is created? Perhaps (if you can't distinguish between a zFS and just a linear-vsam) with some zFS-specific parm? 

This would simplify maintenance and make it more likely that audit programs don't detect "discrepancies" in our environments (especially if it was an automatic function).

See https://www.ibm.com/docs/en/zos/2.4.0?topic=commands-zfsadm-setauditfid for more information.  If IBM wants this to be a unique file-id, I kind of think at least IBM products should be able to enforce that.

Idea priority Medium