Hello Everybody,   I was trying to verify a hash method for comparing dataset-observations (via keys), thereby revealing a somewhat odd inconsistency:   data cars ; set sashelp.cars; run; data cars2 (keep = Make Model compare_digest); length compare_digest $ 32; set sashelp.cars; compare_digest = put(md5(catq(' ', Type, Origin, DriveTrain, Invoice)), $hex32.); run; /* source/compare lookup: hash lookup method */ data work.changed_obs work.new_obs work.same_obs; length source_digest $ 32; drop source_digest compare_digest ; if 0 then set work.cars2; if _N_ eq 1 then do; declare hash hct(dataset: 'work.cars2', hashexp: 20); hct.defineKey("Make", "Model"); hct.defineData("Make", "Model", "compare_digest"); hct.defineDone(); end; set work.CARS (keep = Make Model Type Origin DriveTrain Invoice) end = eof ; /* create digest */ source_digest = put(md5(catq(' ', Type, Origin, DriveTrain, Invoice)), $hex32.); /* source/compare match */ if hct.find() eq 0 then do; /* source/compare match: no change detected */ if source_digest eq compare_digest then output work.same_obs; /* source/compare match: change detected */ else if source_digest ne compare_digest then output work.changed_obs; end; /* source table: new records */ else if hct.find() ne 0 then output work.new_obs; run; data cars_for_comp cars_for_comp2; set sashelp.cars; run; proc sort data=work.cars_for_comp out=cars_for_comp_s; by make Model;run; proc sort data=work.cars_for_comp2 out=cars_for_comp2_s; by make Model;run; proc compare noprint base=work.cars_for_comp_s compare=work.cars_for_comp2_s out=diffs outnoeq ; by make Model ; run; The 1 million $ question is: why do I get 3 observations with the hash method that are regarded different between the two "car files" whereas when using the COMPARE PROCEDURE I do get the correct result, namely, THERE ARE NO DIFFERENCES!   Cheers, FK1 ... View more

Hello,   Quite a while ago, I encountered an issue that has been bothering me ever since. Namely, when I run a PROC CONTENTS on a DB2-Table that has been assigned in a library certain (meta) field information is missing: Number of observations Last modified date, Create date .... Here is a screenshot  (the blackend out parts are due to confidentiality requirements)...   Has anybody an idea, why the metadata/dictionary tables are not filled, so that consequently the PROC CONTENTS procedure cannot retrieve any information?   Thx, FK1 ... View more

  Hi Folks,   I read in the SAS Online Documentation regarding the "weekday-function" the following: "The WEEKDAY function produces an integer that represents the day of the week, where 1=Sunday, 2=Monday, ..., 7=Saturday." When I run the following code, I get WRONG weekdays as soon as I put a weekday-Format on the calculated weekday.   Data input; format date date9. ; input date ; datalines; 21400 21401 21402 21403 21404 ; run; data weekdays_wrong; set input; weekday = weekday(date); weekday2 = weekday(date); weekday3 = weekday(date); format weekday2 weekday9. weekday3 weekdate9.; run;   Correctly, the 4th of August 2018 was a SATURDAY (which corresponds to the integer "7", so the weekday-function works!) . But SAS assigns a Friday (integer = "6") as soon as I want to put a format - no matter if I use "weekday9." or "weekdate9." for example -  on the calculated weekday!     What am I missing? Does it have to do something with the Nation Language Support?  I would like to get the weekdays in German language (I think, I have to use the "NLDATEWN" format)? Would that mean, that I have to set the option options LOCALE=DE_DE; By default, we have set options LOCALE=US_EN. I vaguely remember that Americans vs. Germans start counting the week by a 1 day difference.....   Any help would gladly be appreciated. Thanks, FK1   ... View more

Hi Folks,   I am trying to write a Macro, which writes (depending on the macro parameters) the source code of a compiled macro (from a macro catalog) into the log or a *sas file, respectively.   However, I always get an error message, when compiling the macro, which says:   "ERROR: Macro keyword END appears as text."   The problem ist obviously, that my %IF .... %THEN %DO .....  %END     %ELSE %DO..... %END; case differentiation cannot be used with the %COPY Statement as it is already a macro by itself.   So my question is: how can I somehow get a workaround or mask the above mentioned macro key words?     Here is my code:   %MACRO get_macro_sourcecode(_makroname= , _librefMacKatalog= , _outPfad=) /store source DES="Makro, um den Sourcecode eines kompilierten Makros ins Log ODER in eine ' *.sas ' Datei auszugeben."; /*Fall 1: Codeausgabe in *sas-Datei und libref UNGLEICH der libref in Systemoption "sasmstore" */ %IF %sysevalf(%superq(_outPfad)= ,boolean) eq 0 AND %sysevalf(%superq(_librefMacKatalog)= ,boolean) eq 0 %THEN %DO; %COPY %UPCASE(&_makroname.) /SOURCE LIBRARY=&_librefMacKatalog. out="&_outPfad.&_makroname..sas" %END; /*Fall 2: Codeausgabe in *sas-Datei und libref GLEICH der libref in Systemoption "sasmstore" */ %IF %sysevalf(%superq(_outPfad)= ,boolean) eq 0 AND %sysevalf(%superq(_librefMacKatalog)= ,boolean) eq 1 %THEN %DO; %COPY %UPCASE(&_makroname.) /SOURCE out="&_outPfad.&_makroname..sas" %END; /*Fall 3: Keine Ausgabe in ".sas" - Datei, sondern Ausgabe ins Log und libref UNGLEICH der libref in Systemoption "sasmstore" */ %IF %sysevalf(%superq(_outPfad)= ,boolean) eq 1 AND %sysevalf(%superq(_librefMacKatalog)= ,boolean) eq 0 %THEN %DO; %COPY %UPCASE(&_makroname.) /SOURCE LIBRARY=&_librefMacKatalog. ; %END; /*Fall 4: Keine Ausgabe in ".sas" - Datei, sondern Ausgabe ins Log und libref GLEICH der libref in Systemoption "sasmstore" */ %IF %sysevalf(%superq(_outPfad)= ,boolean) eq 1 AND %sysevalf(%superq(_librefMacKatalog)= ,boolean) eq 1 %THEN %DO; %COPY %UPCASE(&_makroname.) /SOURCE LIBRARY=&_librefMacKatalog. ; %END; %MEND;   ... View more

Hi Everyone,   I wrote a Macro called "GET_PRODCUT_DATA". This Macro - among other parameters - needs  an input filename. This filename, in turn, did I write into a macro variable, which I called file1. As I have more than one file, I created macro variables with the corresponding filename in the manner of file1 file2 ... ... ... Now, I want to repetitivelyy call the Macro "GET_PRODCUT_DATA" within another Macro called "LOOP_CSV), so that I can loop through the different filenames which are stored in the macro var. However, when I run it (for example from 1 to 2, i.e. file1 and file2 filenames) it runs without Errors, but only the filename corresponding to &file1 is being used.   Why does it not loop throug &file2, &file3, etc.?     %MACRO LOOP_CSV; %DO i = 1 %TO 2 /*&anz_files.*/; %GET_PRODUCT_DATA( p_sInOutProductFileCSV=&&file&i ,p_sInCSVDELIMITER = { ); %end; %MEND; %LOOP_CSV;   ... View more