With regard to the ability for Enterprise guide to use proc SCAPROC to analyze a program file to a process flow (under the Node menu > "Analyze program" > "Analyze program flow"), please develop a way for the results to be interpreted such that if 1) a section of code produces one named dataset and 2) that code is then immediately followed by one or more proc sorts with output named the same as the code in number 1), then, when building the process flow, EG should create only one node and then include the following: the code from 1) and all sets of code from the PROC SORTs recognized in 2).
Example illustration of resulting process flow which is desired:
The current behavior of Enterprise Guide is to treat the one or more PROC SORTS as multiple nodes. If the code that is being analyzed is full of such SORT procedures, then the resulting process flow will be littered with such structures. I argue that such structures are noise which distracts the user from the more meaningful structures. Secondly, after the creation of the process flow the information about the order in which each node is run is not clear visually due to the loopbacks necessary in the program.
Example illustration of current behavior:
Example code that is being analyzed:
set sashelp.cars (Keep=Make MSRP);
by Make MSRP;
proc sort nodupkey;
I believe there is a good case for adding this exception to the "program analysis for process flow" algorithm because the use of PROC SORT is so common.