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 Delivered
Workspace COBOL Compilers
Created by Guest
Created on Nov 5, 2013

should be possible to reference all structure items

It should be possible to reference ? ?both items feld in a structure like<br /><br />01 struktur-01.<br /> 05 feld pic x(...).<br /> <br /> 05 struktur-05.<br /> ? ? ?06 feld pic x(..).<br /><br />Compiler message: field is ambigious if you try to reference 05 feld.<br />We need the same behavior of the compiler like in PL/1.

Idea priority High
  • 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
    |
    Feb 11, 2015

    This RFE has been delivered in Enterprise COBOL, V5.2

  • Guest
    Reply
    |
    Aug 12, 2014

    This item has been put into plan for a future compiler release.

  • Guest
    Reply
    |
    Dec 2, 2013

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy.

    We will update the RFE once this item is put into plan.

    Thanks for your input.

  • Guest
    Reply
    |
    Nov 14, 2013

    >> I suggest an option on level 01 of the structure. Not a compiler option. @Sebastian: Is that your idea also? <<
    That is absolutely fine with me!

  • Guest
    Reply
    |
    Nov 14, 2013

    >> Our suggestion would be to change the behaviour of the compiler by an additional option. <<
    I suggest an option on level 01 of the structure. Not a compiler option. @Sebastian: Is that your idea also?

  • Guest
    Reply
    |
    Nov 7, 2013

    Allowing data structures containing fields with same names would be very important for us. This will enable us to reduce unnecessary complexity in other parts of the software development process significantly.
    Actually we generate big data structures based on a complex business model. Unfortunately we often get data structures which contain the same field names in different sub structures. In order to go round the compiler restriction we have to invent artificial names for these fields. This effects the rest of our generating facility in a bad way causing us a lot of extra effort. Maintaining and extending the generating facility is much harder and is error-prone.

    This should work (like PL/I allows it):
    01 group-01.
    05 my-field pic ...
    05 group-05.
    06 my-field pic ...

    This is how we try to handle the shortcoming:
    01 group-01.
    05 my-field-1 pic ...
    05 group-05.
    06 my-field pic ...

    The additional ‘-1' has to be kept in mind for all generated sources using this structure as well. Additionally we are running into complications when communicating with subsystems that are not running in the mainframe context.

    Our suggestion would be to change the behaviour of the compiler by an additional option.