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.
Thank you for this RFE.
The need being expressed here can be summarised as being able to easily map native structure fields to those in a JSON schema that was designed separately from the copybook structure. This is known as "meet in the middle" mapping and we have an existing RFE (88702) that we have accepted for this:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=88702
Though in this case it is only the fieldnames changing, the broader use case is to map fields from any copybook to any pre-designed JSON schema regardless of structure. By being able to use the pre-designed JSON schema as a starting point, renames happen implicitly, thus avoiding the issue described in this RFE of having to type out the new field names to match the design.
As such this RFE is being closed as a duplicate of RFE (88702) linked above.