See attached setdates.sas macro, which generates a large number of SAS global macro variables containing (day,wk,month,qtr,year) dates of differing formats (e.g. monyy7). Values are generated relative to current date i.e. day0=today, day1=yesterday, mon0=this month, mon1=last month, etc.
Example:
%put &mon1_start_date9;
resolves to 01JAN2022 (1st of previous month if current month is Feb2022) and:
%put &mon1_start_date9q;
resolves to '01JAN2022' (the above value in single quotes - useful for pass-thru SQL queries.
Can be overridden using:
%setdates(date=ddmonyy);
This is useful for program testing back and forward in time.
Particularly useful when added to the SAS root macro folder and invoked on any SAS session execution. Allows for standardisation across installations with hundreds of users.
sysdt macro values always refer to system date (not reference date).
---------------------
Having standardised, predictable, meaningful macro variables names is useful in a number of ways:
1) Looping around dates (see %tmp macro below).
2) Also using for e.g. &mon1_yyyy (which is the yyyy year of the previous month) means not having to write logic to cater for year changes when performing a Dec21 run in Jan22.
3) Avoids users creating (and referencing macro variables with personal preference naming convention like 'mydate' which has little meaning.
4) Avoids sometimes convoluted date mathematics to get basic date parameters. When reading someone else's code this has to be first deconstructed to understand meaning.
%macro tmp;
%do i=1 %to 10;
%put &&mon&i._yyyymm;
%end;
%mend;
%tmp;
202201
202112
202111
202110
202109
202108
202107
202106
202105
202104
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9. Sign up by March 14 for just $795.
Data Literacy is for all, even absolute beginners. Jump on board with this free e-learning and boost your career prospects.