Use a slash to change a password. data T1(pw=R); A=1; run; proc datasets nolist ; modify T1(write=R/W alter=R/A read=R/RR); run; quit; proc print data=T1(read=RR); run;   ... View more

have you tried clearing the librefs? A different Lib name besides DATA? ... View more

A third way is to use an ATTRIB statement to remove the labels from all the variables at procedure time.   proc compare base=have1 compare=have2; attrib _all_ label=' '; run; ... View more

Hello,   I have been using the intck function and it works very well. x day of the year=intck('day',PRV_Dt_Annee_Deb,date) + 1 ;       ... View more

There is not a function that will do that directly you will have to take your rules and code each one, for example: data test; do i=0 to 100; y=i*0.05; x=i+0.01; output; end; run; data test; set test end=last; x_obs=7.01; y_obs=0.35; if last then reflabel='.3'; run; data demo; format date weekdatx. sat_start_of_week sat_end_of_week begining_month_date ending_month_date date9.; do date='01jan2016'd to '31mar2016'd; sat_start_of_week=intnx('week.7',date,0,'b'); sat_end_of_week=intnx('week.7',date,0,'e'); begining_month_date=intnx('month',date,0,'b'); ending_month_date=intnx('month',date,0,'e'); wdb=weekday(begining_month_date); wde=weekday(ending_month_date); if wdb =6 then begin_month=begining_month_date+1; if wdb =2 then begin_month=begining_month_date-2; if wde eq 1 then ending_month=ending_month_date-2; if wde eq 2 then ending_month=ending_month_date-3; output; end; drop begining_month_date ending_month_date; run; proc print; format begin_month ending_month date.; run; ... View more

From you table, if the first day of the month is a Sunday, you substract one day to shift to Saturday. if the first day of the month is a Monday, you substract two days, if it is a Tuesday you substact three days and a Wenesday four day. If we substact x days from the start date we do the same for the end date.   If the fist day of the month is a Thursday, you add two days, and a Friday on days.  Then we add two or one days at the end. Is that correct ? ... View more

Hello,   First thank you very much for you SAS code to get the week start date on a Saturday. I have kept the same logic for the end of the week.   But for the begining of the year, and the end of the year I think values could be different.   /* Therefore, if the fist January 2025 is Weneday then the begining of the year will be Saturday 28, 2024 */ data demo; format date weekdatx. sat_start_of_week sat_end_of_week sat_start_of_year sat_end_of_year date9.; do date='28dec2013'd to '10jan2015'd; sat_start_of_week=intnx('week.7',date,0,'b'); sat_end_of_week=intnx('week.7',date,0,'e'); sat_start_of_year=intnx('year', sat_start_of_week, 0, 'b'); sat_end_of_year=intnx('year', sat_start_of_week, 0, 'e'); output; end; run; proc print data=demo; run; I am pretty confortable with the estimate for the begining and the end of the week.  It starts on Saturday and end on a Friday. But if for the week we have a lead of few day should we expect the same for the year ?  So should the year 2014 start on 28dec2013 and end on 02jan2015 ? So if I want to apply that logic, how do we estimate those two dates? ... View more

Hello @alepage,   If you need this modified WEEKDAY function multiple times in your programs, you may want to create your own function ("MYWEEKDAY"): proc fcmp outlib=work.funcs.test; function myweekday(date); return(mod(weekday(date),7)+1); endsub; run;   Usage example: options cmplib=work.funcs; data _null_; set original_data; wd=myweekday(date); put wd date weekdate.-l; run; Result: 1 Saturday, December 28, 2013 2 Sunday, December 29, 2013 3 Monday, December 30, 2013 4 Tuesday, December 31, 2013 5 Wednesday, January 1, 2014 6 Thursday, January 2, 2014 7 Friday, January 3, 2014 ... View more

Really nice explanation and sample code, @FreelanceReinh!  ... View more

Intervals you can use in INTNX, from the documentation https://documentation.sas.com/doc/en/pgmmvacdc/9.4/leforinforref/n0pxq4af0hx60nn1i1x3xn41mc3c.htm#n0zn1re74n6pfvn170g9us41coho   For custom intervals, scroll down in the documentation to "Multi-Unit Intervals"   Regarding weeks that go from Saturday to Friday, you can scroll down to "Shifted Intervals" ... View more

So did you check whether that command worked or not?  I sounds like it did work since you did not read in any error messages when you ran it. (I doubt it would work unless for some reason you used compress to create a compressed version of a file and named it with .zip as the extension even though it was not a ZIP archive.)   Try reading in the first line from the file it wrote. data _null_; input """&work./&fname..&VAR_MOIS.&year..&fextension""" obs=1; input; list; run; Or trying running the ls command to see if it wrote the file. data _null_; input "ls -l ""&work./&fname..&VAR_MOIS.&year..&fextension""" pipe ; input; list; run; And if you want to do what your message says remove the > from the OS command and use a data step that actually reads the file.  For example if that was a compressed CSV file you might use something like: filename oscmd pipe "uncompress -c &path./&fname..&VAR_MOIS.&year..zip 2>&1"; data want; infile oscmd firstobs=2 dsd truncover; input var1 var2 :$30 ; run;   ... View more

So that looks more like a listing now.  The values are in fixed positions on the line, so adjust your INPUT statement to match to locations.  Not sure where they are?  Use the LIST statement. 266 data mydata; 267 input; 268 list; 269 cards; RULE: ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0 270 NB 271 Obs RSP RISK LINE CIE TRANSACTIONS PRIME 272 273 1 1843858 85379040 274 275 2 3 1843858 85379040 276 277 3 AUTO 1843858 85379040 278 279 4 AUTO 3 1843858 85379040 280 281 5 COMM 322475 14702635 282 283 6 PERS 1521383 70676405 284 285 7 COMM 3 322475 14702635 286 287 8 PERS 3 1521383 70676405 288 So you just need an input statement that using column ranges. data mydata; infile "/.../test/wu.valide.auto.prm.lst" FIRSTOBS=6; input obs 1-5 rsp $ 10-15 ... run; But watch out if the listing is more than one page long as PROC PRINT will normally re-align the widths of the columns when the lengths of the values on the page is different.     ... View more

I've experienced in the past issues with the use of call execute() within a SAS macro. You could use dosubl() instead. I personally prefer to generate and %include code the way @Tom already demonstrated because it leads to SAS log that's easier to read and debug. ... View more