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 Oct 25, 2018

COBOL 6.2 behaviour: during NUMCHECK, "check" only on ARITHMETIC OPERATION

Customer uses compilation parameter NUMCHECK(ZON(NOALPHNUM), ABD) as suggested by IBM,
but he would like that DISPLAY statement would be escluded by ABEND. Customer would like the "check" only on ARITHMETIC OPERATION not on other instruction.
DISPLAY is the most common way that application programmers use to visualize fields content,
and it is very useful to check the content of some fileds like the PIPPO1 shown in the sample
that we will send to ecurep.

Idea priority Urgent
  • Guest
    Reply
    |
    Nov 23, 2018

    There are a few options here that currently exist. The user can use MSG instead of ABEND, at least while debugging ( as the user can't put in DISPLAY statements without recompiling anyway).
    Or the user can simply not use NUMCHECK.

    Is there a specific reason as to why the user *wouldn't* want to know about invalid data as early as possible? There are three cases in which the DISPLAY would abend. Either:

    - The invalid data is used after the DISPLAY statement, and abending on the DISPLAY statement is a good thing, as that means the user identifies the invalid data as early as possible, so it's easier to trace it back to its source.
    - The invalid data isn't used after the DISPLAY statement (at least, not in the current program; it could be passed to another program without triggering a numcheck if a parent group is passed); the DISPLAY becomes the only way, in that program, to identify the bad data.
    - The item containing invalid data is overwritten without being used after the DISPLAY statement. In this case, the user can still use NUMCHECK(MSG) instead, or make the change to correct the data before the DISPLAY statement instead.

    Due to the above reasons, this RFE is currently being rejected.

  • Guest
    Reply
    |
    Oct 29, 2018

    "Customer would like the "check" only on ARITHMETIC OPERATION not on other instruction" change to
    "Customer would like the "check" only on ARITHMETIC OPERATIONs and conditions, not DISPLAY statements"