About TD

TD · ‎12-08-2016

does not seem a consistent check: there's no problem to input a value from variable with length of $16 when the date2 is initialized first in the first data step.

TD · ‎12-07-2016

I think it's a SAS 9.3 bug. Adding seconds ':00' works the same way as increasing date1 length to $19 - input is performed correctly (as expected). Must be some kind of memory optimisation bug - because changing value of date2 to '2' also lets to input date1 without an error. Just noticed, that if I initialize date2 before date1, the input works as expected. Thanks

TD · ‎12-07-2016

1 data a; 2 /* uncomment for input to work in the next data step*/ 3 /* length date1 $20; */ 4 date1 = '2015-10-26T23:59'; 5 date2 = '2015-10-26'; 6 run; NOTE: The data set WORK.A has 1 observations and 2 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds 7 8 data b; 9 set a; 10 dt = input(date1, e8601dt.); 11 run; NOTE: Invalid argument to function INPUT at line 10 column 10. date1=2015-10-26T23:59 date2=2015-10-26 dt=. _ERROR_=1 _N_=1 NOTE: Mathematical operations could not be performed at the following places. The results of the operations have been set to missing values. Each place is given by: (Number of times) at (Line):(Column). 1 at 10:10 NOTE: There were 1 observations read from the data set WORK.A. NOTE: The data set WORK.B has 1 observations and 3 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds

TD · ‎12-07-2016

Hi I'm experiencing weird SAS behavior: data a; /* uncomment for input to work in the next data step*/ /* length date1 $20; */ date1 = '2015-10-26T23:59'; date2 = '2015-10-26'; run; data b; set a; not_related = trim(left(strip(date2)))||'T23:59'; dt = input(date1, e8601dt.); run; the second datastep produces a note that input has invalid argument. However, if in first datastep I set date1 length to $20, then the second step has no problem to run and input date/time. Tested on SAS 9.3 TS Level 1M2 X64_ES08R2. Anyone else seen this before? Thanks

TD · ‎01-29-2014

Hi Yes, I saw later that the example is actually working inside proc fcmp. I assumed that I could actually define a user function similar to cat(), where number of arguments is not defined. The problem is already solved with macro. I'll share a problem, so maybe someone can share their neat solution to it. Problem: For the undefined number of words, check if any of the words are actually in the string. I.e. to simulate such statement: indexw(source, 'string1') or indexw(source, 'string2') or .. or indexw(source, 'stringX') stringN can be any possible non-missing string, including single/multiple white space. The function I was attempting to write was just to make code look cleaner and easier to maintain when search strings are added or removed. Thanks for all the trouble. Just by writing this I had a thought that regular expressions could also solve this without a macro: prxmatch('/\b(string1|string2|...|stringX)\b/') (Please be aware, regexp not actually checked, just something from my head. Regexp tend to become write-only in long term and it's difficult to maintain) Thanks,

TD · ‎01-28-2014

This is helpful, but not as per SAS documentation. I want to use user defined function in proc sql where statement, so the temp array is not a solution. In addition, I don't want to manually define number of arguments (again, temporary array limitation). But the main problem is required use of datastep array. I want to call a function just with arguments so I could use the function in proc sql. Cheers,

TD · ‎01-28-2014

Hi, I have issue with Base SAS(R) 9.3 Procedures Guide, Second Edition example (fixed to run without syntax error). I'm using sas 9.3. Code: options cmplib=work.funcs; proc fcmp outlib=work.funcs.temp; function summation (b ) varargs; total = 0; do i = 1 to dim(b); total = total + b; end; return(total); endsub; quit; options cmplib=(work.funcs); data _null_; sum=summation(1,2,3,4,5); put sum=; run; Log: 1 options cmplib=work.funcs; 2 3 proc fcmp outlib=work.funcs.temp; WARNING: No CMP or C functions found in library work.funcs. 4 function summation (b ) varargs; 5 total = 0; 6 do i = 1 to dim(b); 7 total = total + b; 8 end; 9 return(total); 10 endsub; 11 quit; NOTE: Function summation saved to work.funcs.temp. NOTE: PROCEDURE FCMP used (Total process time): real time 0.03 seconds user cpu time 0.00 seconds system cpu time 0.03 seconds memory 3787.98k OS Memory 10436.00k Timestamp 01/28/2014 04:59:42 PM 12 13 options cmplib=(work.funcs); 14 15 data _null_; 16 sum=summation(1,2,3,4,5); 16 sum=summation(1,2,3,4,5); --------- 72 ERROR 72-185: The summation function call has too many arguments. 16 sum=summation(1,2,3,4,5); --------- 707 ERROR 707-185: Expecting array for argument 1 of the summation subroutine call. 17 put sum=; 18 run; NOTE: The SAS System stopped processing this step because of errors. NOTE: DATA statement used (Total process time): real time 0.01 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds memory 2104.40k OS Memory 10436.00k Timestamp 01/28/2014 04:59:42 PM Anyone seen this before? Anyone has a working function example with variable number of arguments? Thanks

TD · ‎01-02-2014

I have a macro which is used to do produce a number of Odds ratios for different datasets/subsets etc.. However, some comparisons produce warnings in the SAS log that I want to get rid of properly. The warning I refer is: WARNING: There is possibly a quasi-complete separation of data points. The maximum likelihood estimate may not exist. I can't change the model or anything proc logistic. The requirement is to not perform logistic analysis for such data. Is there a way in SAS I could reliably check data if proc logistic will through this warning or not (without producing errors or warnings in the log?). My theoretical solution is a little bit complicated (produce temp dataset to feed into proc logistic, run another SAS session (child process) with %sysexec that will only do proc logistic and check the log/lst/RC for abnormalities after child process finished running). So, I'd like to hear simpler/better approach to this problem. p.s. NOWARN options is not a solution, because I need to see warnings for other cases and to skip data for logistic regression. Thanks and happy around exp(7.6078780732785....) ! Kind regards, Tomas

TD · ‎05-10-2012

%let i=3; %let j=name; data _null_; n=&i ; set sashelp.class point=n; call symputx('val', &j ); /*bug fix*/ stop; /*end bug fix*/ run; %put &val ;

TD · ‎05-10-2012

Hi My two cents: macro approach: %macro m(ds=, i=, j=); %local dsid rc varnum func; %let dsid = %sysfunc(open(&ds)); %let varnum = %sysfunc(varnum(&dsid, &j)); %let rc = %sysfunc(fetchobs(&dsid, &i)); /*%if %sysfunc(vartype(&dsid, &varnum)) eq N %then %let func = getvarn; %else %let func = getvarc; *//*This is refactored*/ %let func = getvar%sysfunc(vartype(&dsid, &varnum)); %let value = %sysfunc(&func(&dsid, &varnum)); %let rc = %sysfunc(close(&dsid)); %put &value; %mend; %m(ds=sashelp.prdsal2, i=3, j=actual); Data step approach: %let ds = sashelp.prdsal2; %let i = 3; %let j = actual; data _null_; dsid = open("&ds"); varnum = varnum(dsid, "&j"); rc = fetchobs(dsid, &i); if vartype(dsid, varnum) eq "N" then valuen = getvarn(dsid, varnum); else valuec = getvarc(dsid, varnum); rc = close(dsid); put valuen= valuec=; run; KSharp: your code is short but this is shorter I think: %let i=3; %let j=name; proc sql noprint; select &j into : v from sashelp.class(firstobs=&i obs=&i); quit; %put &v; Message was edited: added another approach

TD · ‎04-30-2012

My solution: data sample; input year firm $ industry; cards; 2000 A 21 2000 B 21 2001 A 21 2002 A 21 2002 C 50 2002 D 60 ; RUN; data control; input year control $ industry; cards; 2000 m 21 2000 n 21 2000 o 21 2000 p 21 2001 q 21 2001 r 21 2002 s 21 2002 t 21 2002 u 21 2002 v 50 2002 w 50 2002 x 60 ; RUN; proc sort data=control; by year industry control; run; data control; set control; by year industry control; retain dup; if first.industry then dup = 0; dup = dup + 1; run; proc sort data=sample; by year industry firm; run; data sample; set sample; by year industry firm; retain dup; if first.industry then dup = 0; dup = dup + 1; run; data match; if _n_ eq 1 then do; if 0 then set sample control; declare hash hc(dataset:'control'); hc.defineKey('year', 'industry', 'dup'); hc.defineData('control'); hc.defineDone(); end; set sample; drop rc dup; rc = hc.find(); run;

TD · ‎01-10-2012

proc sql; create table l2 as select distinct max(a.id) as id format=ddmmyy10. from l as a left join (select max(id) as id from l) as b on b.id > a.id; quit;

Online Status	Offline
Date Last Visited	‎12-17-2021 02:03 PM

Re: SAS 9.3 bug?

Re: SAS 9.3 bug?

Re: SAS 9.3 bug?

SAS 9.3 bug?

Re: proc fcmp function with variable arguments does not work

Re: proc fcmp function with variable arguments does not work

proc fcmp function with variable arguments does not work

proc LOGISTIC - detecting quasi-complete separation

Re: Acces data in table by row and col number

Re: Acces data in table by row and col number

Re: Match test firms with control firms based on industry.

Re: Acces data in table by row and col number

Re: SAS 9.3 bug?

Re: SAS 9.3 bug?

Re: SAS 9.3 bug?

SAS 9.3 bug?

Re: proc fcmp function with variable arguments does not work

Re: proc fcmp function with variable arguments does not work

proc fcmp function with variable arguments does not work

proc LOGISTIC - detecting quasi-complete separation

Re: Acces data in table by row and col number

Re: Acces data in table by row and col number

Re: Match test firms with control firms based on industry.

To find the second Highest Date