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
Categories HCD
Created by Guest
Created on Jul 20, 2022

New cross reference function

In large configuration with many LCU defined on few boxes there is the possibility to misconfigure HCD and give to one physical LCU different definitions that could leave to problems described by OA63553. At the present time the only way we have to protect ourselves from the error reported by OA63553 is to define all the LCU of a box as being attached to all the ficon ports of the hw box itself even thogh only 8 port can be used to reach the LCU. This is a cumbersome process that imply a lot of extra work for environment maintenance if we have to implement the number of FICON cables in use within the configuration. Having the ability to define wich ficon director ports port belong to the same physical box idipendently by the number of path/port actually defined for an LCU and providing a mechanism of XREF betwen the LCU defined in the whole IODF and the ficon ports (similar to the one which is in place for CHPID and LCU) could help in avoiding the misconfiguring of HCD
Idea priority Medium
  • Guest
    Reply
    |
    Oct 19, 2022
    Closing this issue since we did not receive information on time.
  • Guest
    Reply
    |
    Oct 7, 2022
    Hello Rina,

    we still did not receive your IODF for analysis.
    Please send it to our mailaddress IBMHCD@de.ibm.com

    Thanks in advance !

    Kind regards
    Your HCD Team
  • Guest
    Reply
    |
    Aug 22, 2022
    Hello Rina,

    please send the exported IODF to the email address IBMHCD@de.ibm.com

    Thanks in advance !
  • Guest
    Reply
    |
    Aug 18, 2022

    For the description of the scenario, it is described in my updates to TS008834715 update of April 26. I'm going to attach a copy of the case.

    I have problem in attaching the exported IODF. It is 17MB raw and 3MB zipped. May you tell me were I can upload it?

    The involved LCU are F280 and 8A80 and as you could see from the exported iodf, we have comment in place assigning every 2107 LCU to the hw s/n of the box to which belongs. but without having an implicit cross reference function in HCD we don't get any warning of the situtation: all check are based on human checks on comment lines updated by someone.

    Thanks, Rina

  • Guest
    Reply
    |
    Aug 17, 2022
    Hello Rina,

    we discussed your scenario in the team and we are not sure if we fully understand it, from the HCD perspective.

    You wrote that you established a process by ???defining all the LCU of a box as being attached to all the ficon ports of the hw box itself even though only 8 port can be used to reach the LCU."

    As an alternative you might consider grouping the control units of the same storage server by a common serial number. Given that, you could filter the control units by serial number and search the filtered list for CUADD values used more than once.
    Could this help you to avoid accidentally defining the same control unit more than once?

    We know that you already sent some HCD related documents via case TS008834715.
    To analyse this, we would need more documentation (exported IODF or decks and a scenario description for the control units involved).

    Thanks in advance.

    Kind regards,
    Your HCD team