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 Future consideration
Workspace z/OS
Categories SDSF
Created by Guest
Created on Jan 26, 2018

Additional SDSF reason codes to the client

I was trying to access the SDSF APF panel while the system was under
heavy IO stress. Retrieving the data for the panel failed with:

ISF452E SDSFAUX communications failed, return code 0x00000004, reason
code 0x0036080F, function "query APF". Internal error

Looking up this RC/RSN, I see that it is a WARNING because of a TIMEOUT.

xxxx080F
Timeout
A request did not complete with the timeout interval.
Some requests may be delayed if they require I/O to complete or if the
system is busy. You can increase the timeout interval with the SET
TIMEOUT command.

Instead of an "internal error," I would have suspected to see something
related to a timeout printed. "Internal error" indicated more of a failure than a timeout.

Could more reason codes for the client be added to put out more immediately useful short messages?

Thanks!

Idea priority Low
  • Guest
    Reply
    |
    Feb 26, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - SDSF
    Operating system - IBM z/OS
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for System z
    Component - Usability
    Operating system - IBM z/OS
    Source - None