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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS
Categories z/OS File System (zFS)
Created by Guest
Created on Dec 23, 2025

RELATED IDEAS

omvs should mount zfs in parallel at startup

I have two systems I IPLed system A ....and mounted some ZFS's. I shut this down ( Shutdown abended)
I started my old system - which uses the same ZFS. It mounts each ZFS ... waits for 65 seconds, then mounts the next.. waits 65 seconds. then the next.
It should detect this, and if it is hanging for one ZFS - do the next one... This way we wait for wait for just over 65 seconds not 10 * 65 seconds

Idea priority Medium
  • Guest
    Mar 24, 2026
    The 65 second wait to ensure the original system is no longer writing to the file system is an important file system integrity check and needs to be done for each file system that was not properly unmounted. To skip a mount and move to the next one (while one waited) would be inappropriate if the mount point for the one skipped to is inside the file system whose mount is waiting.
    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.