The rule “nobreakby” gives a warning if it encounters a “BREAK BY” without a corresponding FIRST() FIRST-OF() LAST() or LAST-OF() function. This can be solved by removing the word “BREAK”.
The Risk:
A BREAK BY causes extra sorting before processing the selected record set. If you are writing a report that needs control breaks, this can save a bit of effort. If you do not need the break points, you are adding unnecessary overhead to your program – BY without the BREAK will give you the sort order you need.
How to solve this:
Either add a FIRST/FIRST-OF/LAST/LAST-OF() function or remove the BREAK keyword.
How to suppress these warnings:
You can put the directive {&_proparse_prolint-nowarn(nobreakby)} directly before the statement that contains the BREAK BY keyword. See also: suppress warnings.