SAS Chapter 12: Storing Macro Programs

Reviewed by Editorial Team

The ProProfs editorial team is comprised of experienced subject matter experts. They've collectively created over 10,000 quizzes and lessons, serving over 100 million users. Our team includes in-house content moderators and subject matter experts, as well as a global network of rigorously trained contributors. All adhere to our comprehensive editorial guidelines, ensuring the delivery of high-quality content.

Learn about Our Editorial Process

| By Moxleyv

Moxleyv

Community Contributor

Quizzes Created: 38 | Total Attempts: 21,992

| Attempts: 330 | Questions: 10

Quiz Flashcard

Share on Facebook Share on Twitter Share on Whatsapp Share on Pinterest Share on Email Copy to Clipboard Embed on your website

Question 1 / 10

0 %

0/100

Score 0/100

1. Why would you want to store your macros in external files?

You could easily share your macros with others.

You could edit your macros with any text editor.

Your macros would be available for use in later SAS sessions.

All of the above

If you store your macro definitions in external files, you can easily share these files with others. Also, you can edit a macro definition that is stored in an external file with any text editor, and you can reuse the macro in other SAS sessions.

Explanation

Submit

About This Quiz

This SAS Chapter 12 quiz focuses on storing macro programs. It tests knowledge on %INCLUDE statements, storing macros in SAS catalogs, using the Stored Compiled Macro Facility, and... see morecreating permanently stored compiled macros. Essential for learners aiming to master SAS macro programming. see less

2. If you use the Stored Compiled Macro Facility,

The macro processor does not compile a macro every time it is used.

The only compiled macros that the Stored Compiled Macro Facility can access are those that are stored in the Sasmacr... The only compiled macros that the Stored Compiled Macro Facility can access are those that are stored in the Sasmacr catalog.

You need to specify the MSTORED and SASMSTORE system options.

All of the above

The Stored Compiled Macro Facility enables you to store compiled macros permanently so that you can reuse them in later SAS sessions without compiling them again. Compiled macros must be stored in a catalog named Sasmacr, and both the MSTORED system option and the SASMSTORE system option must be specified.

Explanation

Submit

3. The %INCLUDE statement

Can be used to insert the contents of an external file into a program.

Will cause a macro definition that is stored in an external file to be compiled when the contents of that... Will cause a macro definition that is stored in an external file to be compiled when the contents of that file are inserted into a program and submitted.

Can be specified with the SOURCE2 option in order to write the contents of the external file that is inserted... Can be specified with the SOURCE2 option in order to write the contents of the external file that is inserted into a program to the SAS log.

All of the above

The %INCLUDE statement can be used to insert the contents of an external file into a SAS program. If a macro definition is stored in an external file, the %INCLUDE statement causes the macro definition to be compiled when it is inserted into the SAS program. The contents of the macro definition will be written to the SAS log only if the SOURCE2 option is specified.

Explanation

Submit

4. When you submit the following code, what happens?

%macro prtlast;
   proc print data=&syslast (obs=5);
      title "Listing of &syslast data set";
   run;
%mend;

A session-compiled macro named Prtlast is stored in Work.Sasmacr.

A macro named Prtlast is stored in the autocall library.A macro named Prtlast is stored in the autocall library.

The Prtlast macro is stored as a stored compiled macro.

The Prtlast macro is stored as a SOURCE entry in a permanent SAS catalog.

When you submit a macro definition, SAS creates a session-compiled macro and stores it in the temporary SAS catalog Work.Sasmacr. This macro will be deleted at the end of the SAS session.

Explanation

When you submit a macro definition, SAS creates a session-compiled macro and stores it in the temporary SAS catalog Work.Sasmacr. This macro will be deleted at the end of the SAS session.

Submit

5. What will the following PROC CATALOG step do?

proc catalog cat=mylib.sasmacr;
   contents;
quit;

Copy the contents of the Sasmacr catalog to a temporary data set.

List the contents of the Sasmacr catalog as output.

Copy the contents of the output window to the Sasmacr catalog.

None of the above

The PROC CATALOG step enables you to view a list of the contents of a SAS catalog. This might be especially useful if you store your macro definitions as SOURCE entries in permanent SAS catalogs. You might also use the PROC CATALOG step to see a list of the session-compiled macros that are stored in Work.Sasmacr.

Explanation

Submit

6. If you store a macro definition in a SAS catalog SOURCE entry

The macro definition can be submitted for compilation by using the FILENAME and %INCLUDE statements.

You can use the PROC CATALOG statement to compile the macro.

The SOURCE entry will be deleted at the end of the session.

You do not need to compile the macro before you invoke it in a program.

When a macro definition is stored as a catalog SOURCE entry, you must compile it before you can call it from a SAS program. You compile a macro that is stored as a catalog SOURCE entry by using the CATALOG access method. This creates a session-compiled macro that will be deleted at the end of the SAS session. The PROC CATALOG statement enables you to view a list of the contents of a SAS catalog.

Explanation

Submit

7. Which of the following correctly creates a permanently stored compiled macro?

Libname macrolib 'c:\mylib';options sasmstore;%macro prtlast; / store proc print data=&syslast (obs=5); title "Listing... Libname macrolib 'c:\mylib';options sasmstore;%macro prtlast; / store proc print data=&syslast (obs=5); title "Listing of &syslast data set"; run;%mend;

Libname macrolib 'c:\mylib';options mstored sasmstore=macrolib;%macro prtlast / store; proc print data=&syslast (obs=5); title... Libname macrolib 'c:\mylib';options mstored sasmstore=macrolib;%macro prtlast / store; proc print data=&syslast (obs=5); title "Listing of &syslast data set"; run;%mend;

Libname macrolib 'c:\mylib';options mstored sasmstore=macrolib;%macro prtlast; proc print data=&syslast (obs=5); title "Listing of... Libname macrolib 'c:\mylib';options mstored sasmstore=macrolib;%macro prtlast; proc print data=&syslast (obs=5); title "Listing of &syslast data set"; run;%mend;

Libname macrolib 'c:\mylib';%macro prtlast / store; proc print data=&syslast (obs=5); title "Listing of... Libname macrolib 'c:\mylib';%macro prtlast / store; proc print data=&syslast (obs=5); title "Listing of &syslast data set"; run;%mend;

In order to create a permanently stored compiled macro, you must specify the MSTORED system option. The SASMSTORE system option must be specified to point to the library in which you want your macros to be stored. You must also use the STORE option in the %MACRO statement.

Explanation

Submit

8. Which of the following is not true about stored compiled macros?

Because these stored macros are compiled, you should save and maintain the source for the macro definitions in a different... Because these stored macros are compiled, you should save and maintain the source for the macro definitions in a different location.

The Stored Compiled Macro Facility compiles and saves compiled macros in a permanent catalog, in a library that you specify.

You do not need to specify any system options in order to use the Stored Compiled Macro Facility.

You cannot move a stored compiled macro to another operating system.

In order to use the Stored Compiled Macro Facility, you need to specify the MSTORED and SASMSTORE system options. The Stored Compiled Macro Facility saves the compiled macro in a permanent SAS catalog, but it does not save the macro definition. You cannot move a compiled macro across operating systems. Since you cannot re-create the macro definition from a compiled macro, it is a good idea to save your source program permanently as well.

Explanation

Submit

9. Which of the following programs correctly sets the appropriate system options and calls the macro Prtlast? Assume that Prtlast is stored in an autocall library as a text file and that it has not been compiled during the current SAS session.

Libname mylib 'c:\mylib';filename macsrc 'mylib.macsrc';options mautosource sasautos=(macsrc, sasautos);%prtlast

Libname mylib 'c:\mylib';filename macsrc catalog 'mylib.macsrc';%prtlast

Filename mylib 'c:\mylib';options mautosource sasautos=(sasautos,mylib);%prtlast

Libname mylib 'c:\mylib';options mautosource sasautos=mylib;%prtlast

To call a macro that is stored in an autocall library, you must specify both the MAUTOSOURCE system options and the SASAUTOS system option. The SASAUTOS system option can be set to include multiple pathnames or filerefs. Once these two system options are set, you can call the macro by preceding the macro name with a percent sign.

Explanation

Submit

10. Which of the following is not true?

The autocall macro facility stores compiled SAS macros in a collection of external files called an autocall library.

Autocall libraries can be concatenated together.

One disadvantage of the autocall facility is that the first time you call an autocall macro in a SAS session,... One disadvantage of the autocall facility is that the first time you call an autocall macro in a SAS session, the macro processor must use system resources to compile it.

The autocall facility can be used in conjunction with the Stored Compiled Macro Facility.

The autocall macro facility stores macro definitions — not compiled macros — permanently. The first time an autocall macro is called during a SAS session, the macro is compiled and a session-compiled macro is created in Work.Sasmacr.You can have multiple autocall libraries that are concatenated, and you can use the autocall facility in conjunction with the Stored Compiled Macro Facility.

Explanation

Submit

View My Results

Quiz Review Timeline (Updated): Mar 15, 2023 +

Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.