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 May 6, 2015

Controlling overflow behaviour in z/OS Enterprise COBOL

Current COBOL behaviour when any kind of overflow occurs on a MOVE, COMPUTE, ADD, MULTIPLY statement, unless ON SIZE ERROR was specified, not including MOVE which doesn't accomodate ON SIZE ERROR directive - is to ignore and not handle the condition.

Similar to SSRANGE option, we as the software engineering team in our bank tasked with providing organization wide solutions, would be happy to have a compiler option to influence overflow processing.
Currently the capturing of these conditions is complicated - requiring either to code ON SIZE ERROR in numerous places (and MOVE's are not supported) or turning on the program mask and running with LE option TRAP(OFF).

Idea priority High
  • Guest
    Reply
    |
    Dec 8, 2020

    Contacted submitter directly, but did not get a response. As a result, we will be rejecting for now. If the submitter is still interested, feel free to open a new RFE.

  • Guest
    Reply
    |
    Feb 9, 2017

    OK, thnak you, when is it going to be available????

  • Guest
    Reply
    |
    Jan 13, 2016

    We would consider a development-only compiler option to help find sources of bad data. It would tell the compiler to generate ON SIZE ERROR and ABEND for size error conditions. Accepting the RFE based on these grounds only.

  • Guest
    Reply
    |
    Jan 12, 2016

    PRODUBAN Santander Bank is really interested in such an option, to be used only in a developement environment.

  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - COBOL Compilers

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - COBOL Compilers

  • Guest
    Reply
    |
    Aug 7, 2015

    Hi,

    We could consider a development-only compiler option to help find sources of bad data. It would tell the compiler to generate ON SIZE ERROR and ABEND for size error conditions.
    Using this in production would significantly reduce the runtime performance.

    Would this be something you're interested in?

  • Guest
    Reply
    |
    Jun 3, 2015

    Thanks for the reply. We are further evaluating this request.

  • Guest
    Reply
    |
    May 24, 2015

    Hello,
    In answer to the question "will we use the option only in dev / test environments", I'd say initially yes, but in time we'd incorporate it into production. We currently use SSRANGE also in production. I assume we'd slowly introduce such an option to expose existing overflows without disturbing systems' stability too much. As the bugs would be weeded out we could consider using it in production as well.

  • Guest
    Reply
    |
    May 21, 2015

    Hi, is this request only for your testing/development environment? or would you need this in your production environment as well?