Within SAS Data Integration Studio, how is the internal code of a SAS Code transformation assigned to its options?

Question

Options

• ASAS macro variables
• Bcolumns of SAS datasets
• CSAS formats
• DSAS macro calls

• A
  91% (32)
• B
  3% (1)
• C
  6% (2)

Explanation

SAS Data Integration Studio passes option values into a transformation's internal code through SAS macro variables - when you configure options in the transformation's properties dialog, DI Studio maps each option to a macro variable that the underlying SAS code references at runtime (e.g., &input_table, &output_table). This design cleanly separates the reusable code template from the runtime configuration.

Why the distractors are wrong:

• B (columns of SAS datasets): Dataset columns hold data values, not code configuration parameters - they have no mechanism for controlling how a transformation executes.
• C (SAS formats): Formats define how values are displayed or stored; they play no role in passing configuration into transformation logic.
• D (SAS macro calls): While macro calls invoke macros, they are not the mechanism by which DI Studio assigns option values to the internal code - that assignment happens through macro variable resolution (&varname), not the call itself.

Memory tip: Think of DI Studio options as a form that gets "filled in" - each field on that form becomes a &macro_variable that plugs directly into the code template, like mail-merge for SAS programs.

No community discussion yet for this question.