This action might not be possible to undo. Are you sure you want to continue?
1. Have you used macros? For what purpose you have used? Yes I have, I used macros in creating analysis datasets and tables where it is necessary to make a small change through out the program and where it is necessary to use the code again and again. 2. How would you invoke a macro? After I have defined a macro I can invoke it by adding the percent sign prefix to its name like this: % macro name a semicolon is not required when invoking a macro, though adding one generally does no harm. 3. How can you create a macro variable with in data step? with CALL SYMPUT 4. How would you identify a macro variable? with Ampersand (&) sign 5. How would you define the end of a macro? The end of the macro is defined by %Mend Statement 6. For what purposes have you used SAS macros? If we want use a program step for executing to execute the same Proc step on multiple data sets. We can accomplish repetitive tasks quickly and efficiently. A macro program can be reused many times. Parameters passed to the macro program customize the results without having to change the code within the macro program. Macros in SAS make a small change in the program and have SAS echo that change thought that program. 7. What is the difference between %LOCAL and %GLOBAL? % Local is a macro variable defined inside a macro.%Global is a macro variable defined in open code (outside the macro or can use anywhere). 8. How long can a macro variable be? A token? A component of SAS known as the word scanner breaks the program text into fundamental units called tokens. · Tokens are passed on demand to the compiler. · The compiler then requests token until it receives a semicolon. · Then the compiler performs the syntax check on the statement. 9. If you use a SYMPUT in a DATA step, when and where can you use the macro variable? The macro variable created by the CALL SYMPUT routine cannot be used in the same datastep in which it got created. Other than that we can use the macro variable at any time.. 10. What do you code to create a macro? End one? We create a macro with %MACRO statement and end a macro with %MEND statemnt.
Ex: A. %mend plot. in log window. How are parameters passed to a macro? A macro variable defined in parentheses in a %MACRO statement is a macro parameter. 13. Can you execute a macro within a macro? Describe. we call it as nesting of macros. is macro variable. Every macro's beginning is identified the keyword %macro and end with %mend. Use following statement to assign the value of a rather than the variable itself %Let A=xyz. how would SAS know where the current macro ended and the new one began? Yes. %plot(age. which is allowed. Simplest method is %LET. 14. Such macros are called nested macros. not the variable xyz to x. 15. %put x="&A". They can be obtained by using symget and call symput macros. 12. Yes. I can execute macro within a macro. Define it as Global.11. This will assign "xyz" to x. There are different ways of assigning a global variable. How would you code a macro statement to produce information on the SAS log? This statement can be coded anywhere? .sex) 17. What is the difference between %PUT and SYMBOLGEN? %PUT is used to display user defined messages on log window after execution of a program where as % SYMBOLGEN is used to print the value of a macro variable resolved. If you need the value of a variable rather than the variable itself what would you use to load the value to a macro variable? If we need a value of a macro variable then we must define it in such terms so that we can call them everywhere in the program. proc plot. Can you execute macro within another macro? If so. How do you add a number to a macro variable? Using %eval function or %sysevalf function if the number is a floating number. Macro parameters allow you to pass information into a macro. 16. plot &yvar*&xvar. run.xvar= ). Here is a simple example: %macro plot(yvar= .
To assign a value to a single macro variable. though it can be conditionally executed in a macro. The use of %include does not actually set up a library. or run statement. Data steps executes when SAS encounters a step boundary such as a subsequent data. Value can be the name of a variable whose value SAS will use.com/2009/08/call-symput-vs-call-symputx. or a statement fragment) is inserted into the calling program at the location of the call. 19. Where macro-variable-name. Proc SQL . 18. despite its percent sign. is the name of a macro variable. When using the %include building a macro library. is not a macro statement and is always executed in SAS.%EVAL is a widely used yet frequently misunderstood SAS(r) macro language function due to its seemingly simple form. I use CALL SYMPUT with this general form: CALL SYMPUT (“macro-variable-name”.It can be used to setting up a macro library. the included file will usually contain one or more macro definitions. %LET statement. These statements create a macro variable named &status and assign to it a value of either adult or minor depending on the variable age.”adult”). value). and macro parameters. proc. enclosed in quotation marks. . But this is a least approach. I can then use this macro variable in later steps. How we can call macros with in data step? We can call the macro with CALL SYMPUT. and value is the value I want to assign to that macro variable.html CALL SYMPUT is often used in if-then statements such as this: If age>=18 then call symput (“status”. Tell me about % include and % eval? The %include statement.OPTIONS MPRINT MLOGIC MERROR SYMBOLGEN.”minor”). 20. else call symput (“status”. Tell me about call symput? CALL SYMPUT takes a value from a data step and assigns it to a macro variable. or it can be a constant value enclosed quotation marks. macro definition.blogspot. more abt callsymput routine can be read at: http://studysas.Caution: We cannot create a macro variable with CALL SYMPUT and use it in the same data step because SAS does not assign a value to the macro variable until the data step executes. The %include statement points to a file and when it executed the indicated file (be it a full program.
25. its usage and result become elusive and problematic. the macro processor automatically creates certain macro var.. or macro quotation functions. %IF condition in macro is evaluated by %eval. Describe the ways in which you can create macro variables? There are the 5 ways to create macro variables: %Let %Global Call Symput Proc SQl into clause Macro Parameters. you simply name the macro vars names in parenthesis in the %macro statement. 21.parn).par2. parameter-2= . MPRINT: Displays SAS statements generated by macro execution are traced on the SAS Log for debugging purposes. What is the maximum length of the macro variable? 32 characters long. MLOGIC: SAS prints details about the execution of the macros in the log. %MEND macro-name. macro-text%. when its actual argument is a complex macro expression interlaced with special characters. to reduce it to true or false. MERROR: SAS will issue warning if we invoke a macro that SAS didn’t find. Specific options related to macro debugging appear in alphabetical order in the table below: MEMRPT: Specifies that memory usage statistics be displayed on the SAS Log. Tell me more about the parameters in macro? Parameters are macro variables whose value you set when you invoke a macro. 23. 22. %macro_name(par1. Presents Warning Messages when there are misspellings or when an undefined macro is called.. SERROR: SAS will issue warning if we use a macro variable that SAS can’t find. …… parameter-n = ). mixed arithmetic and logical operators. What system options would you use to help debug a macro? The SAS System offers users a number of useful system options to help debug macro issues and problems.. eg: &sysdate &sysday. SYMBOLGEN: SAS prints the value of macro variables in log and also displays text .However. The results associated with using macro options are automatically displayed on the SAS Log. 24. Syntax: %MACRO macro-name (parameter-1= .. To add the parameters to a macro. Automatic variables for macro? Every time we invoke SAS.
few of them are. quit. _numeric_ missf. %mend sortit. format _character_ $missf. proc freq data=&dsn. proc sql noprint. %sortit (ae. select distinct name into:varname1-:varname22 from cont. %put &i &&varname&i. vars=age gender bdate). run. vars=_numeric_). PROC SORT DATA = &DATASETNAME..from expanding macro variables to the SAS Log. %do i =1 %to &sqlobs. / missing. title1 ‘Distribution or Missing / Non-Missing Values’. What are the macros you have used in your programs? Used macros for various puposes. What are SYMGET and SYMPUT? SYMPUT puts the value from a dataset into a macro variable where as SYMGET gets the value from the macro variable to the dataset..pid. 4) Macros written to split the number of observations in a dataset . tables &vars. %varlist(demo). %mend missrep.sarath).001. BY &PID &INVESTIGATOR.inverstigator). %varlist(adverse) 2) Distribution or Missing / Non-Missing Values %macro missrep (dsn. 1) Macros written to determine the list of variables in a dataset: %macro varlist (dsn). proc contents data = &dsn out = cont noprint. run. 3) Written macros for sorting common variables in various datasets %macro sortit (datasetname..demog. %mend. %end. %mend varlist. %missrep(study. 27. 28.
Rather than having the same macro code for in each program where the code is required. 30. data &dsnsplit2.admit4. What is auto call macro and how to create a auto call macro? What is the use of it? How to use it in SAS with macros? SAS Enables the user to call macros that have been stored as SAS programs. set &dsnorig (firstobs = %eval(&obs1 + 1)).2) 29. run. The SASAUTOS option tells SAS where to look for the macros. data &dsnsplit1.admit. Unique advantage of %PUT over PUT is …you can use %PUT outside the data step whereas you can’t with PUT. The MAUTOSOURSE option must be set open and the SASAUTOS option should be assigned. dsnsplit2. %mend split.%macro split (dsnorig. For ex: sasauto=’g:\busmeas\internal\macro\’.admit5. set &dsnorig (obs = &obs1). Although the program may contain other macros and/or open code. obs1). with an autocall macro. Why and How to Use %PUT Statement: %Put statement is similar to the PUT statement in data step.Macro set-up:The fist step is to set-up a program that contains a macro. The auto call macro facility allows users to access the same macro code from multiple SAS programs. it is advised to include only one macro. run. The MAUTOSOURSE option indicates to SAS that the autocall facility is to be activated. %put program Name here as &program. desired to be used in multiple programs. If you want to make sure your macro variable resolves as expected. How to use %PUT: %let program=AE. Set MAUTOSOURSE and SASAUTOS: Before one can use the autocall macro within a SAS program. This permits faster updates and better consistency across all the programs. you can make sure it with %PUT statement. %split(sasuser. . What it does is it writes text and values of macro variable after execution to the SAS System LOG. the code is in one location. dsnsplit1.
%do i=1 %to &nvars.. What can you do with %PUT: Numerous options are available for the %PUT statement... ex: We generally use &&var&i or &&dsn&i these macro variables when we are using a %do loop. %macro doit. You have a dataset and it has 5 variables . &systime . 31) How to know how &&var&i or &&dsn&i resolves? It is very confusing some times to tell rightaway how &&var&i or &&dsn&i get resolved. So if the nvars value is 7.. %mend doit.. %PUT _all_: It prints all macro variables in the log that are available in all environments (global. local.%sysdsn. %PUT _automatic_: It prints all the SAS defined automatic macro variables in the log.. user and automatic). .. %syserr etc) %PUT _global_: It prints macro variables that are created by the user and available in all environments... but here is the simple technique you can use to know. Patid sex age ethnic race wt ht.Above %put statement resolves to … %put Program Name here as AE. (ex: &sysdate. then the loop creates a macro variable list of &var1 &var2 &var3 &var4 &var5 &var6 &var7 which further get resolved to patid sex age ethnic race wt ht You can always use Macro debugging option SYMBOLGEN to see how each macro variable got resolved.. to execute same code n number of times. (couldn’t be able use those macro variables outside the particular data step) %PUT _user_: It prints macro variables that are created by the user in each environment. &&var&i %end... %PUT _local_: It prints macro variables that are created by the user and available only in the local environment.