Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Not under consideration
Created by Guest
Created on May 8, 2020

DASD unit with no mounted file should be not bve seen as ready in OS

ZD&T allows to define DASD Units that have no associated file in the host filesystem behind.
This is necessary since the device map does not allow for dynamic changes. All devices (UCBs) must be defined Right from the beginning otherwise they cannot be used. Such devices can be used to change the content of a DASD during normal operation of the OS.

Handling such an "incomplete" device is error prone as the running OS considers it as READY.
Only during I/O it is encountered that it has no backing PC file behind.

zD&T should behave in this case more close to real iron and do not pretend that such a device is ready.

Idea priority Medium
  • Guest
    Reply
    |
    Nov 23, 2020

    The requested information was not provided and the RFE is being closed. Feel free to resubmit the RFE with the information that was requested.

  • Guest
    Reply
    |
    Jun 15, 2020

    z/OS devices that are defined to the zPDT device map file that do not have a Linux file associated and mounted to them, do in fact remain offline to z/OS when the system is started. It would not be possible for an I/O to occur to any of these devices.

    If there is a condition in which a device is online to z/OS, and there is no file associated to it then it could be possible that someone has used a zPDT awsmount command with the -u option to un-mount the current Linux file from the device without first varying the device offline to z/OS.

    Clarification is required on the scenario where online devices on z/OS and no Linux backing file is seen?