Macros

Is There Any Debugging Help for SAS Macro Errors?

Debugging errors in SAS macros can be difficult. The SAS Clinical Standards Toolkit defines the global macro variable_cstDebug to enable these SAS system options: mprint, mlogic, symbolgen, and mautolocdisplay.
Use these options to significantly increase the number of lines written to the SAS log. By default, _cstDebug is set to 0, and these options are not enabled.
Common errors might be discussed in various parts of the SAS Clinical Standards Toolkit: User's Guide. SAS also maintains a knowledge base that includes notes regarding installation, problems, and usage for specific products. (See How Do I Report Problems, Ask Questions, or Get More Information about How to Use the SAS Clinical Standards Toolkit?.)
Other users might have reported or addressed problems on the SAS and Clinical Trials Community forum ( http://communities.sas.com/community/sas_and_clinical_trials).
See “Common Errors and Solutions” in Chapter 6, “SASReferences File,” in the SAS Clinical Standards Toolkit: User's Guide.

Where Do the Framework and Standard-Specific Macros Reside?

The SAS Clinical Standards Toolkit framework macros can be found here for SAS 9.3:
  • Microsoft Windows
    !SASROOT\cstframework\sasmacro, where !SASROOT is C:\Program Files\SASHome\SASFoundation\9.3
  • UNIX
    !SASROOT/sasautos, where !SASROOT is /usr/local/SASHome/SASFoundation/9.3/
Macros for specific standards can be found in the global standards library directory/standards/standard/macros directory.