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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
this is part of the 5.3 release
I thought about examples like this:
dcl 1 struc
,2 part1
,%include COPYB1
,2 part2
,%include COPYB2
;
struc.value = 42; //Ex1
struc.part1.value = 42; //Ex2
If you have to maintain such nested include structures you know in Ex2 exactly where you have to search but in Ex1 you have to search in every include to find that field.
Sure, a global NOLAXQUAL(FULL) my not always be the best idea but if you may can use it with a FORCE-statement it would be much more useful.
This is easy to implement in the compiler, but it might indeed be quite unpopular with developers
From the poster:
> This enhance will force the developer to always use just full qualified structure name.
This will make your developers hate you like the plague. Have you ever programmed in Pascal, where, unless you use the very dangerous "with" statement, you have such abominations as "MyStruct.ThisPart.LowerLevel.Field.DatapointX.DatapointY.Centre" Forcing the same onto your developers will significantly lower their productivity, and is likely to increase the number of typos significantly.