Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Under review
Workspace z/OS Explorer
Created by Guest
Created on Mar 22, 2024

zExplorer to support edit of local files containing x'0D in COBOL PICTURE clause

The issue is when they copy from the host (IBM1047) to local (UTF-8) and the program contains the hex value '0D'. It is being translated to '3F'.

IDz COBOL Editor can preserve x'0D in a value clause but only when editing remote datasets. It doesn't work with local files.

DBB and Git doesn't support roundtrip with x'0D either so the only viable solution is to change their source code to use the COBOL X notation.

The workaround is change their source code and replace direct x'0D by VALUE("X'0D'") For example:

01 name1 PIC X(20) VALUE "X'0D'".

instead of having hex 0D directly in the source, like

01 name1 PIC X(20) VALUE "␍"

Idea priority Medium
  • Admin
    Karan Patel
    Reply
    |
    Apr 10, 2024

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.