https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487050#M31526 <P>See Maxim 1.</P> <P>proc datasets supports run blocks (a run does not terminate it), and stays active until a new procedure or data step starts, or a quit statement is issued.</P> Wed, 15 Aug 2018 15:50:55 GMT Kurt_Bremser 2018-08-15T15:50:55Z https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487044#M31523 <P>I'm working on a log analysis program (based on the LOGPARSE macro) for my team.&nbsp; We use EG, which helpfully inserts some macro code at the beginning and end of tasks which can be used to identify process flow and task labels.&nbsp; However, I'm running into a weird problem, specifically when PROC DATASETS is used as the last code submitted in a program node.&nbsp;</P> <P><BR />If PROC DATASETS is the last code submitted, the timing results come back&nbsp;<EM>after</EM> the macro code injected at the end of the program.&nbsp; This does not happen if, say, a data step or a proc sort is the last code submitted. This is tripping me up when parsing the log as the i'm using the&nbsp;%LET _CLIENTTASKLABEL part of the log to determine the associated task node, but it's being reset to blank before I can get the timing info.</P> <P>&nbsp;</P> <P>I've attached sample code and log files so you can see what I'm talking about.&nbsp; The ones labeled Program_1 work as expected (with a data step as the last submitted code), and the ones labeled Program_2 do not work as expected (with a PROC DATASETS as the last submitted code).</P> <P>&nbsp;</P> <P>I'd greatly appreciate if anyone has any insight as to why the log behaves in this way, or suggestions for how to get the timing info to show up before the macro variables get reset.</P> Wed, 15 Aug 2018 15:44:30 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487044#M31523 sdennett 2018-08-15T15:44:30Z https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487048#M31525 <P>Here are the log files, which did get uploaded for some reason.</P> Wed, 15 Aug 2018 15:45:32 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487048#M31525 sdennett 2018-08-15T15:45:32Z https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487050#M31526 <P>See Maxim 1.</P> <P>proc datasets supports run blocks (a run does not terminate it), and stays active until a new procedure or data step starts, or a quit statement is issued.</P> Wed, 15 Aug 2018 15:50:55 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487050#M31526 Kurt_Bremser 2018-08-15T15:50:55Z https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487068#M31529 <P>Aha!&nbsp; Thank you, using a quit statement instead of run solved it!</P> Wed, 15 Aug 2018 16:55:08 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/PROC-DATASETS-weird-log-behavior-in-EG/m-p/487068#M31529 sdennett 2018-08-15T16:55:08Z