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.

Add a new idea Subscribe
Status Delivered
Workspace IBM Developer for z/OS
Categories Enterprise Service Tools
Created by Guest
Created on Jul 21, 2009

RELATED IDEAS

Suppress object of ODO from interface and calculate value at runtime

In a web services bottom up generation scenario, we use the OCCURS DEPENDING ON clause in our COBOL Copybooks to have variable length arrays and RDz correctly translates to the schema equivalent of minOccurs and maxOccurs. The use of the ODO clause requires a counter (object of the ODO clause) field and typically, that field is then exposed in the interface itself. This is ok for Response interface definition because we can manually exclude the counter field from appearing in the interface definition. The same cannot be done for the counter field in an input interface definition. If we EXCLUDE the counter field from the input interface, then the XML conversion fails because the converter does not populate the counter field with the number of occurrences of the array item from the XML request.

The enhancement request is whenever the counter field for an ODO is excluded from the INPUT interface, the xml converter should populate the value from the actual XML input.

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 - Developer for System z

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Developer for System z

  • Guest
    Reply
    |     Oct 19, 2011

    Delivered in recent RDz release

  • Guest
    Reply
    |     Jul 19, 2011

    This RFE is being considered for delivery in an upcoming RDz release. Thanks.

  • Guest
    Reply
    |     Sep 26, 2009

    this request is in line with IBM strategy.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.