6.5 Simplifying Programs with Macro Variables (%LET)

6.5 Simplifying Programs with Macro Variables (%LET)

Quick Answer: The content guide requires you to "use macro variables to simplify program maintenance" through three expanded objectives: create macro variables with the %LET statement, use macro variables within SAS programs, and use the macro variable name dot delimiter (.). Base-level macro work is text substitution and nothing more — no %MACRO definitions are required for A00-231.

A macro variable holds text. Before SAS compiles a DATA or PROC step, the macro processor scans the source, finds every &name reference, and replaces it with the stored text. The DATA step never knows a macro variable existed; it sees only the substituted result.

---

1. Creating Macro Variables with %LET

%LET macro-variable-name = value;

%let reportYear = 2026;
%let region     = West;
%let inLib      = sasuser;

Four rules govern what actually gets stored:

1. Everything is text. %let reportYear = 2026; stores the four characters 2026, not the number two thousand twenty-six. SAS treats the substituted text as a number only when the surrounding SAS code puts it in a numeric context.
2. Leading and trailing blanks are stripped. %let region = West ; stores West.
3. Quotation marks are stored literally. %let region = 'West'; stores 'West' including the quotes, which then appear in the substituted code — a classic source of doubled quotation marks.
4. The name follows SAS naming rules — 1 to 32 characters, beginning with a letter or underscore.

/* One edit changes the whole program */
%let region = West;

data work.filtered;
   set sashelp.shoes;
   where Region = "&region";     /* becomes: where Region = "West" */
run;

proc means data=work.filtered mean sum;
   var Sales;
   title "Sales Summary for &region";
run;

Change the %LET to Africa and every downstream reference follows. That is precisely the "simplify program maintenance" the objective is describing.

---

2. Referencing Macro Variables: the Quotation Mark Rule

The macro processor scans double-quoted strings but skips single-quoted strings entirely.

Exam Trap: this is the most-tested macro fact at Base level. Whenever a macro reference must resolve inside a quoted string — a TITLE, a FOOTNOTE, a WHERE clause, a file path — the string must use double quotation marks.

---

3. The Name Delimiter: The Period

A macro variable reference ends at the first character that cannot be part of a SAS name. That works for &region/sales, but it fails when text must butt directly against the value:

%let prefix = sales;

/* WRONG: SAS looks for a macro variable named PREFIX2026 */
data &prefix2026;    /* WARNING: Apparent symbolic reference PREFIX2026 not resolved */
run;

/* RIGHT: the period terminates the name and is then consumed */
data &prefix.2026;   /* resolves to: data sales2026;  */
run;

The delimiting period is removed during resolution. When the generated text needs a period of its own, code two periods:

%let lib = sasuser;
%let ds  = clients;

proc print data=&lib..&ds;   /* resolves to: proc print data=sasuser.clients */
run;

The first period ends &lib; the second survives as the two-level-name separator. Writing &lib.&ds produces the single token sasuserclients and an error.

%let yr  = 2026;
%let ext = csv;

/* One delimiter period plus one literal period in a file name */
filename out "C:\reports\summary_&yr..&ext";   /* summary_2026.csv */

---

4. Automatic Macro Variables

SAS maintains a set of read-only macro variables that resolve without any %LET:

footnote1 "Produced by &SYSUSERID on &SYSDAY, &SYSDATE9";

Note that &SYSDATE and &SYSTIME capture the moment the session started, not the moment the statement runs, so a long batch job stamps every page with the same value.

---

5. Debugging Macro Resolution

Because substitution happens before compilation, a macro bug surfaces as a puzzling DATA step error rather than a macro error. Three tools make the substitution visible.

options symbolgen;      /* log every macro variable resolution */

%let region = West;
%put NOTE: region resolves to &region;      /* writes directly to the log */
%put _USER_;                                /* lists all user-defined macro variables */

SYMBOLGEN writes a line such as SYMBOLGEN: Macro variable REGION resolves to West for every reference, which immediately exposes the two most common failures: a value carrying unexpected quotation marks, and a reference that never resolved at all.

Exam Tip: WARNING: Apparent symbolic reference X not resolved means no macro variable named X exists — usually a typo or a missing name delimiter. The step still runs, substituting the literal text &X, which is why the eventual error message often points somewhere entirely unrelated.