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
Created by Guest
Created on Nov 20, 2024

DSFS: Automatic CCSID conversation for selected datasets/members

We'd love a enhancement in DSFS that it could do automatic conversation of datasets/members when they are used with DSFS.


For example:

dataset.name(member) -> Terminal emulator 1141 for Germany

/dsfs/txt/dataset.name/member --> automatically converted to 1047 as the default encoding for USS is 1047.


We've a concrete use case:

Currently, we keep all of our Python Scripts within datasets. Currently, if we run them, we use EDCICONV to copy them to a filesystem and converting them from 1141 to 1047 to be able to execute them. Afterwards we remove them from the filesystem to don't have old copies there.


With an automatic conversation in any way that overhead could be saved and it wouldn't be that error prone of duplicate/old Python programs.


Idea priority High
  • Guest
    Reply
    |
    Dec 3, 2024
    This item will be considered and appropriately prioritized with other future candidates for a future release.