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 May 22, 2017

SE Log to help troubleshoot API timeouts

System: zSeries Support Element
Actor: Computer Operation group needing new feature

The SE provides various logs that help with managing activities.

We are a software development shop that uses both BCPii and Web Services APIs. We have a number of people doing this testing and need to police who is doing what. We are aware that certain tasks are single-threaded on the SE – an example would be any of those associated with "Perform Model Conversion".

We have occurrences where BPCii calls time out and we need tools to troubleshoot why this happened. We examine the available SE logs (in particular - Audit and Log Management) and can find where the call failed but not what caused it to time out. We know that queries (which are not recorded in the SE logs) as well as commands that change settings can “lock” the SE making it busy for 30 seconds or more. This can happen using API calls or the equivalent console commands. Large numbers of queries in a short time span are also a concern.

We need a log to be able to determine who, when, and the command used to lock the SE for command processing and when the SE was released from the lock. This new information could be added in to an existing log or a new log could be introduced.

Idea priority High
  • Guest
    Reply
    |
    Jun 22, 2017

    Thank you for your request. We have investigated it and have the following analysis.
    There are existing logs that show the BCPii and web services requests being performed as well as logs that show the user initiated tasks that are performed. These existing logs already make it possible to know who was doing what, when. While it is true that some actions block other actions, we do not intend to make this low level, internal information available for end users. Automation needs to be able to handle failures of many sorts and it is our expectation that the appropriate retry mechanisms are in place to handle the majority of these types of situations. In the event of persistent issues manual intervention is usually required and we believe the necessary tools are available to allow for the determination of what executing actions are the likely causes of any blockages. In the event that this is not possible, there is always the path of using the "Report a Problem" task to request support from IBM service to help diagnose the issue.