@Kurt_Bremser wrote: For conditions with strings containing blanks, use double quotes: %macro one; data two; title1= '&title1.'; %if "%str(&title2.)"="%str( )" %then %do; title2 ="one"; %let _ttln=2; %end; %else %if "%str(&title4.)"="%str( )" %then %do;title4 ="two"; %let _ttln=3 ; %end; %else %if "%str(&title3.)"="%str( )" %then %do;title3 ="three"; %let _ttln=4 ; %end; %else %do; title2 ="&title2.";title3 ="&title3."; title4 ="&title4.";title5 ="five"; %let _ttln=5; %end; run; %mend; %one;   Using double quotes in this context is not recommended.  I think all that is needed is the proper execution time quoting function.  I like SUPERQ it works as I expect in most situations.   I do agree that the entire macro part is unnecessary in this application. ... View more

Once again, misunderstanding of macro timing. The put statements are part of data step code, and so the macro PREprocessor tries to resolve the macro variables before they are created.   Use %put after the data step boundary (the run statement): %let gmvar_asat = %str((Population)) ; %let gmvar_subtitle = %str(Population| Phases(adjuvant and Adjuvant Phases)); %let title_1=%str(Between-Treatment Comparisons in Adverse Events); %let subtitle=&gmvar_subtitle.|&gmvar_asat.; data _null_; length item $1000; %* Create Macro variables Title1-Title# to hold the title and subtitle rows *; title_number = 0; item = "&title_1." ; title_number=title_number + 1; call symput("title" || compress(put(title_number,8.)), compbl(item) ); temp_subtitle=trim(left("%nrbquote(&subtitle)")); _sindex = 1 ; do while(lengthn(scan(temp_subtitle,_sindex,"|")) > 0); title_number=title_number + 1; item=trim(left(scan(temp_subtitle,_sindex,"|"))); call symput("title" || compress(put(title_number,8.)), trim(left(item)) ); output; _sindex=_sindex+1; end; run; %put title1=&title1.; %put title2=&title2.; %put title3=&title3.; %put title4=&title4.; ... View more

Thank you very much for reply. I will try to explain what i need in my pgm. If not clear sorry. I will try if i can write the logic in data step.    1. In my pgm, I calculate the difference between any two dates if both responses are in 'CR' 'PR'.   eg. if the first response is either 'CR' or 'PR'  and second(NEXT) response also has to be 'CR' and 'PR'.   2. if the first response is either 'CR' or 'PR'  and second(NEXT) response not in 'CR' or 'PR'. then i calculate difference between date of first response date and randamization date(rdate in my pgm).   The Proc sql pgm works fine for this.    But for id=7, where responses are  CR NE NE CR ,  the sql code calculates as below.   1.CR(first) -NE(first)  (date of CR-date of rdate) 2.CR-NE(second one)   (date of CR-date of rdate) 3. CR(first)-CR(second) (date of CR-date of CR)     I need help in  step 3 where it should be calculating    (date of CR(first) -date of rdate) as there are 2 or more NE  between two CR                     ... View more

The value of the macro variable just replaces the reference and the resulting program statement is then evaluated. So you made COL have a value like A$B$C. If you substitute that into your IF and %IF statements you get: if index(A$B$C, "A") eq 0 then do; %if %index(A$B$C, "A") eq 0 %then %do; So the IF statement is not valid since you cannot have a variable name with dollar signs in it.  And your data step only has the variables A,B and C anyway.  If you want to treat that as a character constant then your need to enclose it in quotes.  But note that  you  get false positives if some other name contains A as part of the name.  So you should use the INDEXW() function instead. if indexw("A$B$C", "A","$") eq 0 then do; if indexw("&col", "A","$") eq 0 then do; The macro %IF condition can never be true since your string, A$B$C does not contain the letter A with quotes around it. You could remove the quotes from around A, but then you might get false positives if some other name contains A as part of the name.   If you really want to search for the name A in the list of names you could use something like this instead. %if %index($A$B$C$, $A$) eq 0 %then %do; %if %index($&col$, $A$) eq 0 %then %do;   ... View more

You are attempting to put character values CR PR into a numeric defined array response. As was mentioned arrays must have a declared size or explicit list of variables to set membership. If you don't want "character converted to numeric" messages in the log use input.   data two; set one; array dt{9} ; array response{9} $ ; cw=countw(a); do i=1 to cw ; if scan(a,i) in ('CR' 'PR') then dt(i)=input(scan(date,i),best.); response(i)=scan(a,i); end; run; And if those are actually dates in the dt array then you might consider assigning an actual date format to the dt variables.   ... View more

This is a Q&A board, I do not see a question here.  Seems like you have a reasonable spec there how are you going with it?  Or were you after a contractor to do some work for you?   ... View more

@knveraraju91 you can edit your posts by clicking the little gear button at the top of the post.  I've merged them into one post here. ... View more

@knveraraju91 you can edit your posts by clicking the little gear button at the top of the post.  I've merged them into one post here. ... View more

Firstly Pinnacle 21 is not a SAS product. Secondly you talk about an "adam" and an "sdtm" dataset. Are you really expecting us as SAS users to understand terms that look like they are only relevant to Pinnacle 21? If these terms are relevant to your problem please explain what they mean.   Also you need to provide any SAS code you you have written for your process. If the "adam" dataset you talk about is a SAS dataset then use PROC CONTENTSto confirm the length of the SRCSEQ variable.   In the end I suspect you would be better off posting your problem on a Pinnacle 21 forum. ... View more

A classic example of when to use the UPDATE statement.  Update is intended to apply transactions to a dataset. In particular missing values are treated as meaning no change should be made.   Normally you need a master and transaction dataset, but you can use an empty version of your source data as the "master". data want ; update one(obs=0) one; by id val; run; ... View more

Hi - I would set up some kind of loop to read through your list of data sets. Instead of proc contents, I used the dictionary.tables data set. Then in your macro you can use a %do loop to go through each data set. I've assumed that each of your sequence variables is named like the table, so you can use &in. to achieve the same thing as &seq. If that's not the case, you'd have to get creative to identify the sequence variable as well. /*Create a list of tables in question*/ proc sql noprint; select memname into :table_list separated by ' ' from dictionary.tables where upcase(libname) eq 'WORK' and upcase(memname) in ('TEST'); quit; %let table_count = %sysfunc(countw(&table_list.)); /*Count how many need to be looped across*/ /*Begin process of identifying duplicates*/ %macro duplicates; %do i=1 %to &table_count.; %let in=%scan(&table_list.,&i.,' '); proc sort data=sdtm.&in. out=_null_ dupout=dups__&in. nodupkey; by usubjid &in.seq; run; proc print data=dups__&in. width=min ; title "Dups in sdtm.&in."; var usubjid &in.seq; run; %end; %mend; %duplicates;    ... View more

One possibility is to write your code a temporary file and then execute that: proc contents data= sdtm._all_ noprint out= sdtmall ; run; filename tempsas temp; data _null_; set sdtmall; where upcase(name) ne 'USUBJID'; file tempsas; put 'Proc sort data=sdtm.' memname 'out=_null_ dupout=dups__' memname 'nodupkey;' / ' by usubjid ' name ';' / 'run;' / 'ODS PDF FILE="..pdf";' / 'Title "Dups in sdtm.' memname '";' / 'Proc print data=dups__' memname Width=min; / ' var usubjid ' name ';'/ 'run;'/ 'ODS PDF close;' / ; run; %include tempsas /source2; Before actually submitting the %INCLUDE statement, you may want to have a look at the TEMPSAS file, and perhaps submit the first block of code to see if everything goes well. A lot easier to debug than macros.   Edit note: after submitting the post, I realised that the code (and your original code as well) will generate a lot of statements like proc sort; by usubjid usubjid; run; which is probably not what you want, so I added the WHERE clause to avoid that.   ... View more

Turn on the MPRINT option to see the different SAS code that the two macros generate.   Also make sure to define the macro variables INN1,INN2, etc before calling the second macro so that they will be available after the macro ends.   ... View more

That's just bad programming.   Maybe they meant  if not ( ^first.rsdtc and ^ last.rsdtc ); which is bad programming too as it's really difficult to read.    Or maybe they changed the code and forgot to remove something. Who knows?   In any case the program line you mention is that same as if first.rsdtc and ^ last.rsdtc;   ... View more

Whenever you create a macro (or a macro variable) and use it, the result must be VALID SAS CODE.   So, you can't have a PROC SORT and PROC PRINT inside a data step. That is not valid SAS code.   In your code, you could call the macro %DUPLICATES after the RUN; that ends the data step. That would be LEGAL SAS CODE. Whether it is actually what you want or not, I don't know. ... View more