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 Needs more information
Workspace z/OS
Categories BCP_IOS
Created by Guest
Created on Jul 18, 2024

Add Support For Read Only 3390 DASD When Running In LPAR

Maintenance of base and middleware on z/OS systems in my shop is performed on a master system. When new z/OS systems are created, these master volumes are copied to the new system. The cloned system LPARs quickly get out of sync with the master system. If we had the ability to make DASD read-only in LPAR, then we could simply overlay the cloned volumes with fresh copies without fear of overwriting something unique in that cloned system.

We have great success in this pattern using read-only MDISKs in z/VM.

Idea priority Low
  • Guest
    Reply
    |
    Nov 6, 2024
    HCD allows for devices to be defined as READ-ONLY including Synchronous Peer-to-Peer Remote Copy (PPRC) secondary devices. Please refer to the z/OS HCD Planning documentation, chapter 2, topic ?Defining whether an I/O device is read-only? for more information.
    https://www.ibm.com/docs/en/zos/3.1.0?topic=features-defining-whether-io-device-is-read-only
    If this does not support your requirement, please elaborate on the functionality that is missing.
    1 reply
  • Guest
    Reply
    |
    Aug 6, 2024

    Currently z/os does support read only devices if they are set up as a secondary in a pprc pair. The only issue is that we can't set the read only bit in the IODF without it being part of a PPRC pair. This causes issues in catalog writing serialization commands to a read only device. This should be an easy fix.