I tested your code. It seems to capture the transitions just fine in the test data that @Patrick wrote. Is it because your data contains something that is not shown in the picture? (For instance, if the second 0 contains leading blanks). ... View more

Something like this may do the trick: data want; set have; length ID $8; _N_=findw(str,'ID',': .'); if _N_ then ID=compress(substr(str,_N_,14),,'DK'); run; The parameters for the COMPRESS function simply deletes anything that is not digits, and because ID has a length of 8, only the first 8 digits are included. You may have to modify the parameters for the FINDW function to find all occurrences of "ID" (the parameters shown are the ones needed for the example data provided by @Patrick ). The third parameter (14) to SUBSTR is just a guess, we do not want to scan the whole rest of the string in case somebody entered an ID with only 7 digits in it (in which case the "14" should more or less guarantee that we do not get the first digit of the ZIP code or the date added to the ID). ... View more

You can use the SASMSTORE option to place the compiled macro in the SASMACR catalog in a different library, e.g.: options mstored sasmstore=MYLIB; - the compiled macro should then be in the catalog MYLIB.SASMACR. ... View more

Assuming that the ID variable in the main table is numeric, and the ones in the subsidiary tables are character, you could try something like this for the subsidiary tables: data subsidiary1_anon(drop=id local_id) anonymization_id; set subsidiary1(rename=(id=local_id)); id=input(scan(local_id,1,'_'),best32.); id_type=scan(local_id,2,'_'); /* I suppose we want to keep this */ modify anonymization_id key=id/unique nobs=n_id; if _iorc_ then do; /* assuming that the ID was not found */ n_id+1; anon_id=n_id; output anonymization_id; _error_=0; end; output patient1_anon; run; ... View more

Just did something like that. The solution I used went more or less like this: proc sql; create table anonymization_id (id num,anon_id num); create unique index id on anonymization_id(id); quit; data patient1_anon(drop=id) anonymization_id; set patient1; modify anonymization_id key=id/unique nobs=n_id; if _iorc_ then do; /* assuming that the ID was not found */ n_id+1; anon_id=n_id; output anonymization_id; _error_=0; end; output patient1_anon; run; To anonymize the next patient table, just use a similar datastep (but keeping the same anonymization_id table), and you will have one table with all the anonymizations used, and anonymized versions of the patient data tables (just remember to write/copy them to a permanent library, not WORK).   If you need to anonymize the text variable NAME as well, you could just insert something like name=cats('Dummy',anon_id); before the second output statement, the patients' name will then be anonymized as well.   By using the same anonymization table for all the tables containing Patients' IDs, you will get the same translation from real to anonymized ID in all the tables. ... View more

As @Kurt_Bremser remarked, the value of &SYSERR is the latest value of the error code. Much better to use SYSCC, which contains the maximum error code encountered so far, and which can be reset by the program: RSUBMIT wait=no log=mylog1 cmacvar=auths new; %let SYSCC=0; /* So far, so good */ %include "/sasdata/cro_rte/user_libs/crm_prod/aasbon/systask/rsubmit/test/tes1.sas"; %SYSRPUT auths1=&SYSCC.; ENDRSUBMIT; ... View more

How can I effectively utilize macro variables to handle date values in SAS Studio? I normally use the DATE9. format for date macro variables. Either plain text, or as date constant. %let date1=31DEC2022; /* plain text */ %let date2='31DEC2022'd; /* Date constant */ The way to use these macro variables is simple: data test; retain date1 "&date1"d; /* convert to date constant */ date2=&date2; /* already formatted as date constant */ datetime="&date1:00:00"dt; /* a datetime, not possible with the second format */ datetime2=dhms(&date2,0,0,0); /* but you can do it like this */ /* more statements */ run; Note the double quotes, as macro expressions within single quotes are not resolved.   They can also be created using functions with %SYSFUNC, e.g. %let date1=%sysfunc(today(),date9.); %let date2="%sysfunc(today(),date9.)"d; I much prefer to have my date macro variables in a readable format, rather than integers, as they are easier to understand and read, for instance in MPRINT output.   ... View more

No, you do not need to migrate the required tables. I think the solution is to use an interface to MySQL that does not go through ODBC, as that seems to be the one creating the problems. So, if you have access for MySQL, you may want to try that instead of the ODBC interface, as suggested here. ... View more

I tried looking it up, and the problem seems to come (sporadically) with the ODBC connection to MySQL (not just in SAS, the problem seems to have nothing to do with SAS). If possible, you should switch to the SAS Interface to MySQL, instead of going through ODBC. ... View more

It may depend on your character set settings, but I had some problems with your example The obvious solution seems to be the good old TRANSLATE function, but that does not work, as 'Ã' seems to register as more than one character in my current SAS session: 70 data _null_; 71 set aaa; 72 newname=translate(orgname,'A','Ã'); 73 put _all_; 74 run; ORGNAME=PAZ RODRíGUEZ S L newname=PAZ RODRA ­GUEZ S L _ERROR_=0 _N_=1 The TRANWRD function works, on the other hand: 70 data _null_; 71 set aaa; 72 newname=tranwrd(orgname,'Ã','A'); 73 put _all_; 74 run; ORGNAME=PAZ RODRíGUEZ S L newname=PAZ RODRA­GUEZ S L _ERROR_=0 _N_=1 - only problem with that is that you may have to use several calls to get rid of different "strange" characters.   KTRANSLATE works better, as it can translate double-byte to single-byte characters (or the other way round): 70 data _null_; 71 ORGNAME='PAZ RODRíGUEZ S Lã'; 72 newname=ktranslate(orgname,'Aa','Ãã'); 73 put _all_; 74 run; ORGNAME=PAZ RODRíGUEZ S Lã newname=PAZ RODRA­GUEZ S La _ERROR_=0 _N_=1   ... View more

You are probably better off submitting your question in the "SAS Studio" section of SAS Communities, but here are my two cents:   It looks like your user written step is not part of the flow. Should it not be in order to get executed? You may want to show the log file that PROC PRINTTO writes to, and the SQL server table that the user written code writes to, in the diagram. That way, it will be much clearer what the code does, and a lot easier to switch the output, e.g. if you are moving from TEST to PROD. It's been a while since I have done any SAS Studio work, and I do not remember how to reference files and tables in user-written code (ask over at the SAS Studio section, I am sure it's not complicated). ... View more

You also write that you have a MAIN table, containing all IDs, and that you want all the IDs to be accounted for (although this is not shown in your wanted output). If your MAIN table looks like this (sorted by ID, only one record for each ID): data main; do id=1 to 7; output; end; run; you can get the table you want like this: %let min_age=0; %let max_age=10; data want; array interv [&min_age:&max_age] 8 _temporary_; call missing(of interv[*]); do until(last.id); merge have(in=have) main(keep=id); by id; if have then interv[age]+1; end; count_int=0; do age=&min_age to &max_age; intervention=interv[age]>0; count_int+interv[age]; output; end; run; Note: HAVE should also be sorted by ID (but not necessarily by AGE), and all AGEs should be between &min_age and &max_age, no missing values. This can of course also be ensured by using the dataset option "where=(age between &min_age and &max_age)" on HAVE in the code above - you may have some interventions outside the range of years that you want to study.   ... View more

You can try something like this for the last wanted result you show: data want; do _N_=nobs to nobs-2 by -1, 4 to nobs-3, 3 to 1 by -1; set have point=_N_ nobs=nobs; output; end; stop; run; Your original result with the same style of coding: data want; do _N_=nobs, 2 to nobs-1, 1; set have point=_N_ nobs=nobs; output; end; stop; run; ... View more