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 Sep 10, 2014

HCD design change - control unit type 2107

Requesting design change to HCD - identify an invalid/unsupported 2107 control unit definition.

CNTLUNIT CUNUMBR=E006,PATH=((CSS(0),89,C2,6A,15)), *
UNITADD=((00,256)),LINK=((CSS(0),41,41,C1,C1)),CUADD=4F,*
UNIT=2107
IODEVICE ADDRESS=(E0F0,016),UNITADD=00,CUNUMBR=(E006), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(E1F0,016),UNITADD=10,CUNUMBR=(E006), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(E2F0,016),UNITADD=20,CUNUMBR=(E006), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(E3F0,016),UNITADD=30,CUNUMBR=(E006), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(E4F0,016),UNITADD=40,CUNUMBR=(E006), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(E5F0,016),UNITADD=50,CUNUMBR=(E006), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(EEFC,002),CUNUMBR=(E006),STADET=Y,SCHSET=1, *
UNIT=3390A
CNTLUNIT CUNUMBR=E007,PATH=((CSS(0),F6,47,29,6D)), *
UNITADD=((00,256)),LINK=((CSS(0),03,03,83,83)),CUADD=4F,*
UNIT=2107
IODEVICE ADDRESS=(ECF0,016),UNITADD=C0,CUNUMBR=(E007), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(EDF0,016),UNITADD=D0,CUNUMBR=(E007), *
STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(EEFE,002),CUNUMBR=(E007),STADET=Y,SCHSET=1, *
UNIT=3390A
.
Control Unit defined passes HCD. Prior to an IPL EEFE and EEFF were "unbound". After systems were IPL'd, received command reject errors on devices EEFE and EEFF. Both devices were suppose to be unavailable.

IODFs will be attached.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 20, 2022
    This item is a valid requirement but unlikely to be given high enough priority to be placed into the product plan
  • Guest
    Reply
    |
    Jun 3, 2020

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

  • Guest
    Reply
    |
    Sep 16, 2014

    We understand the requirement and had some discussions with our L2 team in POK with the following outcome:

    We agree that this is a valid requirent for HCD.
    To avoid the customer situation a possible rule and requirement would be:

    - If a user defines different control units with the same CUADD and SERNO,
    - and the control units have different paths to the same CEC
    - and there are alias defined to one of the control units

    then HCD shows an error message (mainly this will be for scenarios like connect control unit to processor, change cuadd of control unit, connect devices to cu, change serial number of CU)

    It would be the responsibility of the customer to work with a serial number (we should recommend this anyhow).
    And the check would probably make sense for all control unit types with alias.

  • Guest
    Reply
    |
    Sep 11, 2014

    Creating a new RFE based on Community RFE #58969 in product z/OS.