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 Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Feb 8, 2021

Option to have spaces treated as zeros at Runtime

Our COBOL V6 migration has been painful and slow. Much of this due to 'invalid data'.
The biggest pain for our applications folks are when copy books and linkage areas initialized to spaces at the 01 level. To code around this in V6 is a lot of extra work. It's often not an option to 'fix' the copybook as many are shared between multiple applications and programs.
They would like an option to specify the runtime treat spaces (x'40') or low values as a zero instead of blowing up on NUMCHECK.
Ideally they'd like V6 to work like V4 but that's not going to happen - giving an option for space and/or low value to be treated as zero would speed up development and assist in migration to V6. This has been the biggest challenge.

Idea priority High
  • Guest
    Reply
    |
    May 11, 2021

    Discussions have been going on with the RFE submitter directly and we have decided to implement a different approach (ie not the one outlined in this RFE). As a result, we are rejecting this specific RFE.

  • Guest
    Reply
    |
    Feb 17, 2021

    This is being discussed further internally.

  • Guest
    Reply
    |
    Feb 11, 2021

    I disagree with this proposal.
    That would be starting to allow anything in the treatment of digital areas.
    Note that with the NONUMCHECK option, spaces are considered as zeros (unfortunately).

  • Guest
    Reply
    |
    Feb 9, 2021

    Hi SkiDreamer

    I cannot vote for this issue, as I see this as a clear program error, and not something that should be fixed using options.
    If you want to, it is possible to run 6.3 and have it treat spaces as zeroes.
    Remove the numcheck, numproc and zonedata options, and that should fix it.

    The right fix here should be, to initialise ws-stuff, instead of moving spaces to it.
    That will move zeroes to the number instead of spaces.

    And you are not the only one struggling with these options.
    Our solution was to make it so that only programs that are tested to work with the options, use them in production.
    I'm guessing we have less than 5% of all programs running the best options for 6.3.

    Regards,
    Rune