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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.
No, the functions of Mapping-Level 4.1 for arrays does not cover the function we need.
Currently and this does not change with Mapping-Level 4.1 all fields in a copybook especially outside OCCURS structures will be generated with nillable="false", which means that this field is mandatory.
But in copybooks normally not all fields are mandatory. Therefore we asked for a function to control the generation of the nillable attribute.
Apar PI67641 introduces mapping level 4.1 and it that we are introducing the concept of truncating empty arrays. That provides what this RFE is asking for, but only in the special case where entire array structures are partially omitted. It's almost a variant of OCCURS DEPENDING ON, just without the DEPENDING ON part. Does that help ?