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 Sep 13, 2017

COBOL 6.2 - option to allow Parmeter/Argument size mismatch

Client is requesting an option to allow a compile of a currently illegal mismatch of a parameter/argument in COBOL 6.2.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 25, 2017

    The compiler compiles one program at a time and is not aware of any mismatch.
    The compiler cannot guarantee the layout memory outside the bounds of a single program's working-storage section is exactly the way it was in V4.
    Things are considerably different in V5/V6.

    You will have to fix this issue or use PARMCHECK with a large-enough buffer to mitigate the problem. Hence, this RFE is being rejected.