retain AETOXGR_base .; AETOXGR_base = max(AETOXGR_base, AETOXGR); ... View more

If your SAS session "knows" the definition of a macro all you need to run in your session is this snippet: %executeMyProcess( inputDataSet=sashelp.class; ,analysis2=Y ,analysis3=Y ) (you can compare it to the situation where you are using some function in Python which was imported from a packages). So at the beginning of the session you have to tell SAS where the macro definition is stored.   In 99% cases having a macro definition inside the definition of another macro is considered bad programming practice. But in 99.9% cases calling a macro inside another macro is standard way of coding.   The way I would organise my code would be by creating a  SAS Package (here is link: https://github.com/yabwon/SAS_PACKAGES). I would wrap my code from each file inside macros and then add one more "driving" macro (like the one I showed). Then at the beginning of a SAS session you, or other user would load the package, and then could run the snippet.   Bart     ... View more

Ok, thanks for the snippet. Form what I can see in the dump file it wont be easy to import it to SAS in the for it is, MySQL's syntax is too different then one used by SAS. SAS "import wizard" is dedicated for plain text files(CSVs) or Excels not for database dumps.    You wrote you did the dump yourself, have you considered dumping data to files in CSV format, which is "easily" importable into SAS ?   Bart ... View more

You mean something like this: %macro executeMyProcess( inputDataSet= ,analysis1=N ,analysis2=N ,analysis3=N ); %if %syperq(analysis1) = Y %then %do; %regression_is_one_macro1() /* from file regression_is_one_macro1.sas */ %end; %if %syperq(analysis2) = Y %then %do; %another_statitics2() /* from file another_statitics2.sas */ %end; %if %syperq(analysis2) = Y %then %do; %another_statisticN() /* from file another_statisticN.sas*/ %end; /* ... */ %mend executeMyProcess; %executeMyProcess( inputDataSet=sashelp.class; ,analysis2=Y ,analysis3=Y ) Bart ... View more

one more advantage of the "let's make a file" approach, you can have several such files created an just waiting to be used 🙂 ... View more

You are right, I would make it more "visible" too.  It took me a bit to find it a few years ago when I needed this kind of feature. ... View more

the input() function pops up in interactive pythons console as far as I understand that function. In SAS case we don't have that kind "interactive" console right away.   If you have windows DMS SAS session you could use %WINDOW command to generate popping up window which can grab parameters (but it's only for DMS) In Enterprise Guide you could set project prompts popping up at start of the process, but again it's EG specific.   xlsx file has this advantage that you can edit it easily, "double check" values before run, etc.  one more option I would consider is a "trivial" txt file with form: paramerter1:value1 paramerter2:value2 paramerter3:value3 ... ... instead xlsx, txt file is easier to modify on every OS, does not require MS Excel, etc.   Bart  ... View more

But of course! I should spot that myself! 😄 ... View more

Data steps don't allow to "embed" libname definition inside their views. Only SQL allows this.  BTW for datasets I personally consider  set "/direct/path/to/a/data/set/namedXYS.sas7bdat"; bad programming practice.   Bart ... View more

Agree 100%, for production jobs only explicit lists of variables. But here I didn't know variables in datasets. ... View more

"Second, SAS SQL does not have a USING clause." - it does. https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/sqlproc/n0nolnbokay91in1gouzgw3xzl5e.htm   Bart ... View more

btw. how's SQL version? In your session: libname dummy "C:\test" ; data dummy.class ; set sashelp.class; run; libname mySesion "C:\downloads"; PROC SQL; CREATE VIEW mySesion.Central AS SELECT * FROM x.class where sex='M' USING LIBNAME x "C:\test"; ; QUIT; in bran new one: libname newSas "R:\downloads"; proc print data=newSas.central; run; bart ... View more

Which version of sas do you use? On my M8 I have: 1 %let path=R:\; 2 libname dummy "&path" ; NOTE: Libref DUMMY was successfully assigned as follows: Engine: V9 Physical Name: R:\ 3 data test; 4 set dummy.class_v; 5 run; NOTE: View DUMMY.CLASS_V.VIEW used (Total process time): real time 0.01 seconds cpu time 0.00 seconds NOTE: There were 19 observations read from the data set R:\/class. NOTE: There were 10 observations read from the data set DUMMY.CLASS_V. NOTE: The data set WORK.TEST has 10 observations and 5 variables. NOTE: DATA statement used (Total process time): real time 0.04 seconds cpu time 0.00 seconds   bart ... View more

Hi,   SQL is an animal which likes statements in certain order, I would try with: PROC SQL; CREATE VIEW &TABLES_SAVE_PATH_LIBNAME..Central AS SELECT MAT.*, MAIN.* FROM &TABLES_SAVE_PATH_LIBNAME..Other_Table MAT LEFT JOIN &TABLES_SAVE_PATH_LIBNAME..Other_Table2 MAIN ON MAT.AGREEMENT_NUMBER=MAIN.AGREEMENT_NUMBER USING LIBNAME &TABLES_SAVE_PATH_LIBNAME. &TABLES_SAVE_PATH. ; QUIT; BTW. macrovariables are resolved during view generation and stored view will have constant values (for libname and path) Bart ... View more