Not knowing exactly what you are trying to achieve why not something like: proc sql;                              /* Create a dataset which has you loop values (so this &n_multi) */      create table LOOP as      select     distinct                    NAME      from       ...; quit; data _null_;                         /* Using the dataset you created above, generate a bit of code for each observation in that dataset                                                   with the code and the loop variable */      set loop;      call execute('data foo;                               model="'||strip(name)||'";                           run;'); run; ... View more

Thanks data _null_; I see what you mean now.  I don't really use macros so not really come across that.  Must try reading documentation sometime. ... View more

Sorry, I have to ask data_null_; how does the %nstr change the operation of call execute.  To my understanding call executes generates code which always executes after the containing step has finished irrespective of code used which is why it works particularly well as loop generation with a datastep.  E.g. data _null_;      set sashelp.cars;      call execute('aaaa'); run; When this gets sent to the compiler at each observation the text aaa would be put out to the compiler.  When the run; is encountered to end the datastep, the compiler then starts executing aaa then the next aaa etc. for however many were generated. ... View more

Yes, macros or call execute, e.g. data _null_;      set sasahelp.columns (where=(libname="YOURLIB" and memname="YOURDATASET"));      if name="YOURCOLUMN" then call execute('%do_somecodemacro();'); run; You would need to be more specific for a specific example. ... View more

Hi, I am not sure on the point of your macro.  You are going to hit problems as you are generating a macro variable with a datastep loop.  So the macro pre-processor gets your code, it does a search and replace on the &x. and finds nothing delclared for X so it throws an error, it never gets to the stage where the datastep is actually run to create X. In your example X always referencing the last mdy, this is because the loop goes over each time and only the last iteration sets the date. So first question, what is it your trying to achieve?  Is it to find all dates within that range and use them to select data, if so then store to dataset and use this in your code, e.g.: data dates;      attrib mydate format=date9.;     do loop=mdy(3,1,2015) to mdy(3,31,2015);           mydate=loop;           output;     end; run; /*later on */ proc sql;      create table DATA_TO_WORK_ON as          select     *      from       DATA_I_HAVE      where     DATE in (select MYDATE from WORK.DATES); quit; ... View more

Well, that depends on what you specs/team tell you.  If it is just sort by date (and what if there are multiple on the same date?), then sort the dataset, retain lstvisit and lstunsch, if unscheduled then visit=lstvisit + lstunsch.  It could however be far more complicated than that with applied logic defining visit windows, or other known patterns. Code for the above: data want;      set have;      by subjid;      retain lstvisit lstunsch;      if first.subjid then do;           lstvisit=visit;           lstunsch=0;      end;      else if type="UNSCHEDULED" then do;               lstunsch=lstunsch+0.1;          /* note I would recommend using 0.01 as there may be more than 10 */           visit=lstvisit + lstunsch;      end;      else lstvisit=visit; run; ... View more

Actually, you can do most things with SAS, have a secured autoexec.sas for instance which sets up permissions, creates things based on username etc.  You could for instance put in autoexec the statements: If user="aaa" then do;      libname aaa_data "...\..." access=read;      libname aaa_workspace "...\...";      proc datasets ... copy datasets from core to aaa_data; end; etc. However you would also need IT to protect things on a storage level as obviously knowing the network path to core would allow access. ... View more

Could you mean some kind of access control to a large dataset.  I know what OC does is create a view with a subclause for access: So Table ACCESS: User     Priv     Area aaaa     write     Dom1 aaaa     write     Dom2 bbb       read     Dom1 Proc sql;      create view TEST as      select     *      from        DATA_TABLE      where     AREA in (select THIS.AREA from ACCESS THIS where THIS.USER="&USER."); quit; ... View more

Try: http://support.sas.com/documentation/cdl/en/etsug/60372/HTML/default/viewer.htm#etsug_intervals_sect006.htm Look at the months entry, so something along the lines of to=month2.3? ... View more

Hi, Check: What is your escape char set to, e.g. ods escapechar='^'; In your proc report statement do you have split= set, e.g. proc report data=mydata split='~'; In your initial PDF, it looks like you have a special language set loaded, something in your intialisation? ... View more