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
Workspace z/OS Connect
Created by Guest
Created on Jan 24, 2018

Provide meaningful error messages for z/OS Connect and API toolkit problems

Currently z/OS Connect provides for a lot of configuration errors, RACF and Unix System Services problems neither an error message in the JES Job Log nor an error message in the messages.log. Often the only way to get an impression of what may be the cause of a problem is to activate traces and to search for Exceptions in it. In some cases also the trace is not helpful because the Exception message is not meaningful. Is a huge problem for a usage of z/OS Connect in production. Not every problem will appear right on the server start-up and because no error messages will show up traces may need to be activated to find errors. But traces have a negative impact on the performance. Besides this no alarming or automation is possible, if no error message shows up. Please enhance z/OS Connect to provide error messages for any problem. Tracing could not be a solution for determining every problem. An administrator should only need to turn on a trace in exceptional cases. System problems should be printed to JES job log and messages.log. For application problems an option would be helpful to configure where the messages appear (JES job log and messages.log or only messages.log). In addition to this whenever there is a RACF problem it should appear in the SYSLOG as well like it the case with other mainframe software products.

Besides z/OS Connect also the API toolkit does not provide meaningful error messages in every case. This makes the life of an administrator or API designer hard. Please enhance the toolkit as well.

Idea priority High
  • Guest
    Reply
    |
    Nov 7, 2018

    This requirement has been open for more information since May 2018. Unfortunately the statement in the RFE was too generic and did not hold enough detail for us to action. Though we have had some ideas for specific improvements, those ideas have not had enough community support to prove that they are pervasive, so correspondingly this requirement is being rejected. Many improvements have been made to messages as a matter of course over our monthly CD drops. If you have ideas for specific improvements in this area based on the current version of the product then please raise an RFE detailing the use case and specific improvements that could be made.

  • Guest
    Reply
    |
    May 22, 2018

    Thank you so much for your response Johnathan, this gives use something much more specific to work with.

    If any other subscribers to this RFE agree that this is the best area to focus on, please comment to show your support.

    If anyone has alternative ideas then please post them as well as we will have to curate a prioritised list of suggestions based on customer interest.

  • Guest
    Reply
    |
    May 14, 2018

    I can't remember the specific message IDs I've encountered that could've been improved, but I'll start logging them here going forward.

    However, many of the security related issues are difficult to determine due to the lack of ICH408I messages, like when a user is not in globalInvokeGroup or globalAdminGroup and some of the failures for the APPL profile. If those messages are being suppressed intentionally due to concerns of those messages flooding the log, then you could give the customer the ability to set flood control limits in server.xml, such as only show the first X errors or show a max of X errors per ID per time interval (maybe 1 minute while setting up and maybe 24 hours in production).

  • Guest
    Reply
    |
    May 11, 2018

    Thank you for this RFE. We are always looking for ways to improve the usability of our product.Unfortunately, there is not enough detail in this RFE to understand what exactly is being asked for.

    To help us act we would love to have some specific examples of user tasks that could be improved by enhancing the communication of specific error conditions. A comment, from each voter on this RFE would be great, ideally containing a top 3 list with specific examples of how the error is communicated today, and how it could be improved.

    Many thanks!