The most obvious solution (for me) is to store the data in a SPDE (or SPDS if thats an option at the libname, and do a SET BY (which will result in a implicit sort on the BY variables). I'm not sure if this can be done with other techniques, but why...? Regards, Linus ... View more

I believe that SP:s only can exist in Foundation, well I had never come across any other implementation. As a general rule of thumb: unless specified, all EBIS objects must reside in Foundation (9.1.3). Regards, Linus ... View more

To do this within DI Studio you will probably create a job with a input table using parameter. Then call this job using Loop and Loop end transformations. As input to the Loop you can have a look-up table the table-names you want to validate, which map to the parameter name you specified in the validation job. Regards, Linus ... View more

In the current release there is limited support for nesting jobs. By using Loop and Loop end transformations you can conditionally call/loop one other DI Studio job. I believe there will some more functionality in this area with 9.2 version. But you can whatever you like by using the Cynthia mention, but then It won't be a DI Studio process. Regards, Linus ... View more

Sorry, I don't what I was thinking of. I meant to suggest countc, but as Scott says counw is a bit neater (just make sure to remove the +1 part from my example). /Linus ... View more

See the online doc for FILENAME FTP statement (if you want to do it within SAS). Otherwise you can create a shell script with your ftp commands, which you can call from a SAS session using the X statement. Regards, Linus ... View more

This is handled by some classic data step programming. Could be done i thousands of ways, here's one. This example involves some help variables, retain, if-then-else and scans. If you are going to do more of this kind est you should consider taking a SAS programming class. data report; infile '~/reportdat.dat'; input; length station origin $10 originCount 8 originNext $1; retain station originCount originNext; firstVar = scan(_infile_,1,' '); if firstVar eq 'STATION:' then do; station = scan(_infile_,2,' '); originCount = 0; originNext = 'N'; end; else if firstVar eq '(data' then originNext = 'Y'; else if firstVar eq 'TTL' or originNext = 'Y' and originCount lt 5 and firstVar not =: '-' then do; origin = firstVar; sales2008 = input(scan(_infile_,2,' '),best.); sales2007 = input(scan(_infile_,3,' '),best.); if firstVar eq 'TTL' then originNext = 'N'; else originCount+1; output; end; drop firstVar originCount originNext; run; Regards, Linus ... View more

To do a comparison with floating point numbers, you have to use %sysevalf function: %if %sysevalf(&a < &b) %then %put "True"; %else %put "False"; Regards, Linus ... View more

If you want to do something dynamic without individual coding for each variable, I think you first have to determine how many variables there are in the file, and us this information either to specify a array or to create a macro %DO loop when reading the file. Array example: data dat; infile '~/data.dat'; input; call symput('ANTVAR',left(put(indexc(_infile_,'|') + 1,3.))); stop; run; data dat; infile '~/data.dat' dlm='|'; array dynvar(*) dynvar1 - dynvar&ANTVAR.; input dynvar(*); run; Regards, Linus ... View more

You can also do a subsetting if in the first datastep (on the new "ranuni"-variable). Then there is no need to sort and read the data a third time. Regards, Linus ... View more

You can store the formatted value in a seperate column, something like this: data genderstage; set gender (in=g) stage (in=s); if g then gendFmt = put(gender,$gendFmt.) else gendFmt = put(gender,$stageFmt.); run; Regards, Linus ... View more

As Olivier pointed out, you can use dictionary.macros/sashelp.vmacro. Try this out: %let a=Linus; proc sql noprint; select name into: userMac separated by ' ' from dictionary.macros where scope = 'GLOBAL'; quit; %symdel &userMac UserMac; proc sql; select * from dictionary.macros; quit; Beware that this code alse deletes macro variables such as SQLMSG etc. Regards, Linus ... View more

Hi, here is some sample (untested!) code you can start with. Have a look in doc for PROC COMPARE and SYSINFO for details. About the rechecking, I suggest that you use a scheduling tool for that, such as cron in UNIX. Regards, Linus %macro checkdata; data _null_; dsid = open('libname.table'); updated_dt = attrn(dsid, 'MODTE'); if "&SYSDATE9"D eq datepart(updated_dt) the call symput('UPDATED','Y'); else call symput('UPDATED','N'); run; %if &UPDATED eq Y %then %do; proc compare data=lib.today compare=lib.yesterday; ...; run; %if &SYSINFO ne 0 %then %do; %include "program.sas"; %end; %end; %mend checkdata; %checkdata; ... View more

This seems specific syntax for an other DBMS . You are right, it won't work in proc sql. Some options can be set in the proc sql statment, and using the RESET stament inside proc sql. If you can describe what you want to accomplish it would be easier to help you with more specific answers. Regards, Linus ... View more

If you have year and week stored seperately in numeric columns, the syntax might look like this: data step: length yw $12; yw=catx(' ',put(year,4.),"week",put(week,2.)); SQL: select catx(' ',put(year,4.),"week",put(week,2.)) as yw length =12 ... Regards, Linus ... View more