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.
this was delivered as part of 5.2
This could be useful, particularly as an alternate to RULES(NOLAXSTMT)
Nice, here we go again:
This is asking for a rue that should never have been necessary if IBM had not changed the way statements are numbered, going from the old V2.3.0 OS compiler to Enterprise PL/I. As an example, I have a program that counts 4,721 statements when compiled with the former, and 5,586 when compiled with the latter - here is a short sample from both, where you can see that WHEN now gets the same, IMO, illogical treatment:
V.2.3.0 OS PL/I
60 1 2 WHEN (SUBSTR(LISTREC.DATA, 1, 2) = '{Z')
DO;
61 1 3 IF LIST_OWN ^= SYSNULL() THEN
DO;
62 1 4 CALL POST_PROCESS();
63 1 4 LIST_OWN = SYSNULL();
64 1 4 END;
65 1 3 CALL GET_TZ_INFO();
66 1 3 END;
V4.5.0 Enterprise PL/I
2333.0 64 1 2 when (substr(listrec.data, 1, 2) = '{Z')
2334.0 65 1 2 do;
2339.0 66 1 3 if list_own ^= sysnull() then
2340.0 67 1 3 do;
2341.0 68 1 4 call post_process();
2342.0
2343.0 69 1 4 list_own = sysnull();
2344.0 70 1 4 end;
2345.0
2346.0 71 1 3 call get_tz_info();
2347.0 72 1 3 end;
However, both treat statements of the type
var_a, var_b = value;
as a single statement, where one would expect EPLI to count this as two, as it's nothing more than a textual shortcut for
var_a = value;
var_b = value;
Would you like to also flag those? RULES((NO)MULTIASSIGN) ?
I personally would like to see a RULES() option to revert to the old OS statement numberiing scheme.
Test - earier comment (20 minutes formulating it) disappeared on "Submit".