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 z/OSMF
Created by Guest
Created on Oct 8, 2024

Support X-IBM-Dsname-Encoding header when listing data sets and data set members

Some mainframe developers may use a different encoding when entering the name for a new data set or data set member. However, it seems that z/OSMF converts these names behind the scenes to use the IBM-1047 encoding, so characters in the name are converted to IBM-1047 before the data set name is assigned. While this makes sense, users might try to list the data set or its members with the name they provided, rather than the assigned name of the data set.

Since the X-IBM-Dsname-Encoding header isn't used for both the "list data sets" and "list data set members" endpoints, the data set names are interpreted as-is for the API request.

For example: When a user with the codepage IBM-285 searches for a data set with the £ symbol, the matching data set is not returned since it does not actually contain that character in the "IBM-1047"-encoded name. But, this header is respected for uploading and downloading contents of a data set. For those endpoints, if you specify the same data set name with the X-IBM-Dsname-Encoding header set to 285, it will convert the data set name from IBM-285 to IBM-1047 before performing the operation - thus resulting in a successful request. This same behavior is expected when listing data sets or data set members.

Idea priority Medium