Select the best answer
for each question. After completing the quiz, check your answers using
the answer key in the appendix.
-
-
can be used to insert
the contents of an external file into a program.
-
can 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 into a program to the SAS log.
-
-
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 is
deleted at the end of the session.
-
you do not need to compile
the macro before you invoke it in a program.
-
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
-
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 catalog.
-
you need to specify
the MSTORED and SASMSTORE= system options.
-
-
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 of &syslast data set";
run;
%mend;
-
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 &syslast data set";
run;
%mend;
-
libname macrolib 'c:mylib';
%macro prtlast / store;
proc print data=&syslast (obs=5);
title "Listing of &syslast data set";
run;
%mend;
-
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.
-
The
Prtlast
macro
is stored as a stored compiled macro.
-
The
Prtlast
macro
is stored as a SOURCE entry in a permanent SAS catalog.
-
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.
-
-
What does 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.
-
-
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 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.
-
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, the macro processor must use system resources
to compile it.
-
The autocall facility
can be used in conjunction with the Stored Compiled Macro Facility.