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 is a duplicate of COBOLVUE-I-236 which has been delivered in Enterprise COBOL for z/OS, V6.4.
Delivered !
Denis mentions this structure is possible in REXX. Indeed it is. As well as in PL/I, and C, and C++, and, Java, and C#, and Delphi, and Python, and Ruby, and Perl, and Ada, and, well, in pretty much every language known to man other than COBOL. :-(
(No, I never give up.)
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 - COBOL Compilers
For recording keeping, the previous attributes were:
Brand - Rational
Product family - Design & development
Product - COBOL Compilers
This kind of structure is possible in Rexx :
do forever
...
if ... then leave
...
end
This kind of loop removes the need for a variable and test and feeding instructions of this variable.
I can't say that I am not disappointed. By virtue of the fact that other COBOL vendors support it its apparent to me that the COBOL standards group made a poor decision to not support something like this.
Thanks for opening this RFE, but PERFORM UNTIL EXIT is currently not in the COBOL Standard. Also, since there already is a way to achieve the functionality (as mentioned in the RFE), this item is currently being declined. Feel free to let us know if you have any further questions/concerns.
Yes, those enhancements to EXIT are supported. But I am asking for "PERFORM UNTIL EXIT", which is not currently supported.
Looks like this is available in COBOL 5.2 as well as EXIT PARAGRAPH and SECTION
Interesting thought, but needs its own RFE. Plus I'm not sure how you could do this with COBOL-like syntax, considering that labels in COBOL have somewhat different behavior. Or are you suggesting the addition of a new type of label for this purpose? Something like the following?
loop-test.
loop-1: PERFORM UNTIL EXIT
loop-2: PERFORM UNTIL EXIT
IF ...
EXIT PERFORM loop-2
END-IF
loop-3: PERFORM UNTIL EXIT
IF ...
EXIT PERFORM loop-1
END-IF
END-PERFORM loop-3
END-PERFORM loop-2
statement-a
END-PERFORM loop-1
statement-b
EXIT PARAGRAPH.
Interesting, certainly, but I would not put it on the top of my wish-list.
Like PL/I, you should be able to supply a label on the loops. Then "EXIT loop_label" could exit several nested loops, not only the current.
loop_1: PERFORM UNTIL...
loop_2: PERFORM UNITL...
leave loop_2 *> goes to statement_a
loop_3: PERFORM UNITL....
leave loop_1 *> goes to statement_b
end loop_3
end loop_2
statement_a
end loop_1
statement_b
In my opinion a nice request. I too use that machanism in other languages.
Added to GSE ADL watchlist