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 Not under consideration
Workspace z/OS
Created by Guest
Created on Apr 30, 2012

LUNS/LUNR enhancement to support LUMAP usage

Add LUNS support to permit reading of LUMAP entries and managing associated LU names, where SLUGROUP can not be used.

Idea priority High
  • Guest
    Reply
    |
    Dec 7, 2020

    This item is not in our plans but is being kept in our backlog.

  • Guest
    Reply
    |
    Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS Communications Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Networking
    Product - z/OS Communications Server

  • Guest
    Reply
    |
    May 17, 2012

    My understanding of your request is that you have many LUMAP statements and would like all LUMAP statement LUs to be managed automatically by the LUNS if the server is in a LUNS setup.
    I don't think we can do that without some type of new parameter or statement. Other customers already using LUNS/LUNR expect LUMAP statements to be local and may not want all mapping statements to be managed by the LUNS. So, we would have to add a parameter to the LUMAP statement (or more likely, create a new SLUMAP statement). You state in the requirement that adding a parameter would be less desirable because that would require you to make changes to a program that generates the statements. So, if a solution requires modification of your program, why not change it to generate SLUGROUP statements? The SLUGROUP statement can be part of the INCLUDE file. Where you now have one line for the LUMAP, there would instead be two lines: the SLUGROUP and then the LUMAP statement (which will be exactly the same if the SLUGROUP name is the lu name). I realize that you would prefer to avoid modifying the current program, but if you have to anyway, would that method work for you?

  • Guest
    Reply
    |
    May 10, 2012

    ...If it helps to understand my implementation and requirement, I could also send you one of my LUMAP files. I tried to show a small sample in the record but perhaps that wasn't of much aid. If you see the one of the LUMAP files used then you may be able to vision the purpose of this LUNS/LUNR enhancement request (or show me where I am overlooking an existing capability - though your ETR support folks could not offer something). Let me know if you wish to recieve the LUMAP file (one of them, anyway).

    Steve

  • Guest
    Reply
    |
    May 9, 2012

    Why not create SLUGROUPs for each of the individual LU names? 
    For example,
    SLUGROUP luname1  luname1  ENDSLUGROUP
    SLUGROUP luname2  luname2  ENDSLUGROUP
    and use the same mapping statements as before. Would that approach work for you?