When you want to specify your own SAS options in SAS/EG they only take effect after SAS/EG generates the following lines:   ;*';*";*/;quit;run; 2 OPTIONS PAGENO=MIN; 3 %LET _CLIENTTASKLABEL='Program'; 4 %LET _CLIENTPROCESSFLOWNAME='Process Flow'; 5 %LET _CLIENTPROJECTPATH='\\Prodnasfs2\homefs2$\PL77986\My Documents\My SAS Files\lineage.egp'; 6 %LET _CLIENTPROJECTPATHHOST='L6003956'; 7 %LET _CLIENTPROJECTNAME='lineage.egp'; 8 %LET _SASPROGRAMFILE=''; 9 %LET _SASPROGRAMFILEHOST=''; 10 11 ODS _ALL_ CLOSE; 12 OPTIONS DEV=PNG; 13 GOPTIONS XPIXELS=0 YPIXELS=0; 14 FILENAME EGSR TEMP; 15 ODS tagsets.sasreport13(ID=EGSR) FILE=EGSR 16 STYLE=HtmlBlue 17 STYLESHEET=(URL="file:///C:/Program%20Files/SASHome/SASEnterpriseGuide/7.1/Styles/HtmlBlue.css") 18 NOGTITLE 19 NOGFOOTNOTE 20 GPATH=&sasworklocation SYMBOLGEN: Macro variable SASWORKLOCATION resolves to "/saswork1/SAS_workC4F900005DF1_prodsascom5l/SAS_work42CA00005DF1_prodsascom5l/" 21 ENCODING=UTF8 22 options(rolap="on") 23 ; NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR 24 25 GOPTIONS ACCESSIBLE; 26 options mprint sgen ls=255;   Is it possible to cause the user specified options to execute BEFORE the SAS/EG generated program statements? ... View more

It seems that the latest version of base SAS has changed the way source program statements  are numbered on the SAS log.   Here's a sample of how SAS displayed numbers on the SASLOG file: 12 ODS tagsets.sasreport13(ID=EGSR) FILE=EGSR STYLE=HtmlBlue 12 ! STYLESHEET=(URL="file:///F:/Program%20Files/SASHome/x86/SASEnterpriseGuide/5.1/Styles/HtmlBlue.css") NOGTITLE NOGFOOTNOTE 12 ! GPATH=&sasworklocation ENCODING=UTF8 options(rolap="on");   Now, it looks like this:   15 ODS tagsets.sasreport13(ID=EGSR) FILE=EGSR 16 STYLE=HtmlBlue 17 STYLESHEET=(URL="file:///C:/Program%20Files/SASHome/SASEnterpriseGuide/7.1/Styles/HtmlBlue.css") 18 NOGTITLE 19 NOGFOOTNOTE 20 GPATH=&sasworklocation 21 ENCODING=UTF8 22 options(rolap="on") 23 ;   So, it seems that long program source statements have different line numbers instead of a single line number (with an ! indicating it's a single statement.  The problem with this behavioral change is that it is causing a program we use to fail.  Is there a way to specify in an OPTIONS statement to restore the old behavior?  Also, can user-specified OPTIONS statements take effect BEFORE the SAS/EG or SAS Web Studio options? ... View more