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
Created by Guest
Created on Jun 19, 2018

bcpii error enhancment on group cap value

I was trying to change a group cap and was on an LPAR that was not in the group. Instead of getting a bad data return code or something meaningful I got:

REXXHostRc = 0 rc = 101
DiagArea.Diag_Index = 0
DiagArea.Diag_Key = 146
DiagArea.Diag_Actual = 0
DiagArea.Diag_Expected = 0
DiagArea.Diag_CommErr = 21
DiagArea.Diag_Text =

which is a Communication Error and typically means that the SE may be busy.

This misleading error caused us to waste a lot of time. We eventually realized that there was no group on that LPAR, so the cap could not be changed. But the error did not reflect that.

Support told me that they were looking at the codes and it does not look like the hardware has a
specific code for an Image not being defined to a group so it is defaulting to the SE Busy code. They said the error does not even relate to the issue at hand and suggested opening a RFE against the API for more specific Return
Codes for Service Element Errors.

Thanks

Idea priority Medium
  • Guest
    Reply
    |
    Aug 9, 2021

    Originally SNMP/BCPiiV1 exposed group capping via the Image (Logical Partition) object. This is the path the customer was using when trying to change a group capping attribute. In addition, starting with z14, the SNMP/BCPiiV1 interface also exposes these attributes via the LPAR group object. The latter implementation is more correct since these attributes are really part of the group and not part of the Image. This is also consistent with the new BCPiiV2 interface. The customer should use this path for the automation to avoid getting this cryptic failure since it is more correct and how things will be done in the long run with BCPiiV2.

  • Guest
    Reply
    |
    Nov 13, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Z and LinuxONE Systems Hardware
    Product - Z and LinuxONE Systems Hardware
    Component - HMC/Support Element (SE)
    Operating system - IBM z/OS
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - BCP_BCPii
    Operating system - IBM z/OS
    Source - None

  • Guest
    Reply
    |
    Oct 30, 2020

    .Are you still interested in this RFE? Please let us know either way. We would like to understand your response to our question. Thank you.