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 Submitted
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Jan 7, 2025

z/OSMF store result into log file

We had the situation that an ISV software trys to call an z/OSMF REST API (dataset service). The ISV product only returned HTTP 500. In the z/OSMF logs, also only the HTTP 500 was visible. The error that was seen within z/OS was:


ICH408 for $LIBPATH/ceasapit.dll CL(DIRSRCH ) ($LIBPATH wasn't resolved). After some research and trying it from the SwaggerUI, we got a more concrete error message and have seen that the reason was the to small TSO segment region of the user that invoked the ISV service.


I know, that it should be logged by the client that issues that request. But as z/OSMF currently only logs HTTP 500, this is completly useless. Instead, z/OSMF should also log the HTTP response for the error in case of for example an HTTP 500


Idea priority Low