Hi, I think it would be fair to make your suggestion as a SAS ballot idea. I haven't used the automatic variable &SYSPROCNAME , but it contains the name of the current proc being processed by the "SAS Language Processor". (I guess the SAS Language Processor is a logical name for whatever controls word scanning/tokenization and sending tokens off to the appropriate compiler.) With it you can do: proc print data=sashelp.class;
title "Current procedure is: &sysprocname";
run;
title;
proc means data=sashelp.class;
title "Current procedure is: &sysprocname";
run;
title;
Personally, I don't like that style of TITLE statements (I like them before the PROC). But since &SYSPROCNAME was implemented (I think in a fairly recent version), seems fair to ask for &SysCurrentDSN (&SYSDSN already exists, but it is like &SYSLAST). Without that, I would suggest either wrapping your PROC calls in a macro, so that the macro could generate the title for you, or creating a %MakeFootnote(data=) macro, where you pass it a dataset name and it makes footenote like "Run on dataset &data by &user on %now()". But those would be more programming solutions, not sure how they would feel to an EG task user. On the other hand, for the general purpose (linking a report back to its source), if you keep the EG project, then there are automatic macro variables that could be used in the footnote to provide the name of the EG project file that generated the report. For many purposes, having the names of the project file / code is more useful than having the name of the data set.
... View more
