SAS Institute A00-211 Exam Dumps & Practice Test Questions
Question 1:
A SAS dataset named SASUSER.HOUSES contains a variable PRICE that has been assigned the permanent label "Asking Price".
To generate output where the label "Asking Price" is temporarily replaced with "Sale Price" specifically for a PROC PRINT procedure, which SAS program correctly achieves this?
A. proc print data = sasuser.houses; label price = "Sale Price"; run;
B. proc print data = sasuser.houses label; label price "Sale Price"; run;
C. proc print data = sasuser.houses label; label price = "Sale Price"; run;
D. proc print data = sasuser.houses; price = "Sale Price"; run;
Answer: C
Explanation:
In SAS, variable labels are crucial for making output understandable and readable, providing more descriptive names than raw variable names. When a variable has a permanent label stored within the dataset, it is possible to override this label temporarily for the duration of a specific procedure, such as PROC PRINT, without altering the original dataset. The challenge lies in using the correct syntax for both the PROC PRINT statement and the LABEL statement within the procedure.
Let's evaluate each provided SAS program snippet:
A. proc print data = sasuser.houses; label price = "Sale Price"; run; This program correctly uses the LABEL statement syntax (label variable = "New Label";) to specify the desired temporary label for PRICE. However, it is missing a critical option on the PROC PRINT statement itself. For PROC PRINT to display variable labels instead of variable names, the LABEL option must be included in the PROC PRINT statement (e.g., proc print data = sasuser.houses label;).
B. proc print data = sasuser.houses label; label price "Sale Price"; run; This option correctly includes the LABEL option in the PROC PRINT statement, which is a necessary step to enable label printing. However, the syntax for the LABEL statement itself is incorrect. In SAS, when assigning a label within a LABEL statement, an equals sign (=) is required between the variable name and the label text (e.g., label price = "Sale Price";). Omitting the equals sign will result in a syntax error, preventing the program from executing successfully.
C. proc print data = sasuser.houses label; label price = "Sale Price"; run; This is the correct program. It combines both essential elements for temporarily overriding a variable label in PROC PRINT output:
proc print data = sasuser.houses label;: The LABEL option is included in the PROC PRINT statement, instructing SAS to display labels in the output rather than variable names.
label price = "Sale Price";: The LABEL statement within the PROC PRINT step uses the correct syntax (variable = "label_text") to assign "Sale Price" as the temporary label for the PRICE variable. When this program is submitted, PROC PRINT will produce output where the PRICE column header displays "Sale Price".
D. proc print data = sasuser.houses; price = "Sale Price"; run; This program contains a fundamental syntax error. Inside a PROC PRINT step, you cannot use an assignment statement (price = "Sale Price";) to change variable values or assign labels. Assignment statements are typically used within DATA steps to create or modify variables.
Therefore, the only SAS program that correctly implements the temporary label override for PROC PRINT output is option C.
Question 2:
The WORK.PEOPLE dataset contains 5 observations, and the WORK.MONEY dataset contains 7 observations.
How many observations will the resulting WORK.EMPSALARY dataset contain after this program is submitted?
A. 0
B. 5
C. 7
D. 12
Answer: A
Explanation:
This SAS program utilizes a SET statement with the IN= dataset option, a common source of confusion for new SAS users when concatenating or interleaving datasets. The IN= option creates temporary, Boolean (0 or 1) variables that indicate which dataset an observation originated from during the current iteration of the DATA step. Understanding how SET processes multiple datasets and how the IN= variables behave is key to determining the final observation count.
Let's break down the program's execution flow:
data work.empsalary;: This statement initiates a DATA step, indicating that a new dataset named work.empsalary will be created.
set work.people (in = inemp) work.money (in = insal);: This is the core of the data processing. When multiple datasets are listed in a single SET statement without a BY statement, SAS performs a concatenation. This means:
SAS first reads all observations from the first dataset listed (work.people).
After all observations from work.people have been read, SAS then proceeds to read all observations from the second dataset listed (work.money).
The IN=inemp option creates a temporary variable inemp. inemp will be 1 (true) when an observation is being read from work.people, and 0 (false) otherwise.
Similarly, IN=insal creates insal. insal will be 1 (true) when an observation is being read from work.money, and 0 (false) otherwise.
if insal and inemp;: This is a subsetting IF statement. It instructs SAS to write an observation to the work.empsalary dataset only if the logical condition insal AND inemp evaluates to true. For this condition to be true, both insal and inemp must simultaneously be 1.
Now, let's trace the values of inemp and insal as the SET statement processes the data:
When reading from work.people (5 observations):
For each of these 5 observations, inemp will be 1, and insal will be 0.
The condition if insal and inemp; will evaluate to if 0 and 1;, which is FALSE.
Therefore, none of the 5 observations from work.people will be written to work.empsalary.
When reading from work.money (7 observations):
For each of these 7 observations, inemp will be 0, and insal will be 1.
The condition if insal and inemp; will evaluate to if 1 and 0;, which is FALSE.
Therefore, none of the 7 observations from work.money will be written to work.empsalary.
Since inemp and insal are mutually exclusive within a single SET statement performing concatenation (an observation can only come from one dataset at a time), the condition insal AND inemp will never be true. Consequently, no observations will meet the subsetting condition, and the resulting dataset WORK.EMPSALARY will contain 0 observations.
This scenario highlights a common misconception: the IN= option flags the source of the current observation, not whether the observation exists in both datasets, which would require a MERGE statement with a BY variable.
Question 3:
What will be the final length of the variable JOBCODE in the output dataset WORK.ACCOUNTING?
A. 3
B. 5
C. 7
D. 8
Answer: C
Explanation:
Understanding how SAS determines and assigns lengths to character variables within a DATA step is crucial, especially when variables appear in multiple input datasets or when LENGTH statements are used. The general rule is that a variable's length is set upon its first reference in the DATA step and typically cannot be changed later within that same DATA step.
Let's analyze the provided SAS program step-by-step:
data work.accounting;: This line initiates the DATA step, indicating that a new dataset work.accounting will be created.
set work.dept1 work.dept2;: This is the first reference to the JOBCODE variable in the DATA step, as it's present in both work.dept1 and work.dept2. When a SET statement lists multiple datasets that contain the same variable with differing lengths, SAS follows a specific rule: it assigns the longest length found among all contributing datasets for that variable.
JOBCODE in work.dept1 has a length of 5.
JOBCODE in work.dept2 has a length of 7. Comparing these, SAS will determine the length of JOBCODE in the Program Data Vector (PDV) and ultimately in the output dataset work.accounting to be 7. This length is established at the time the SET statement is processed.
jobcode = "FA1";: This is an assignment statement. At this point, the JOBCODE variable has already been defined in the PDV with a length of 7 (from the SET statement). The value "FA1" (which has a length of 3) will be assigned to JOBCODE. Since the variable's defined length (7) is greater than the assigned value's length (3), "FA1" will be stored as "FA1 " (with four trailing blanks) to fill the 7-character space. This assignment statement does not change the already established length of 7. If the assigned value were longer than 7, it would be truncated to 7 characters.
length jobcode $ 8;: This is a LENGTH statement. LENGTH statements are used to explicitly define the length of a variable. However, for a LENGTH statement to take effect for an existing variable, it must appear before the variable's first reference in the DATA step. In this program, the JOBCODE variable was first referenced in the SET statement. Because this LENGTH statement appears after the SET statement, it is ignored by SAS for the JOBCODE variable. It has no effect on the length that was already determined to be 7.
Final Determination:
Based on the rules of SAS variable length determination:
The SET statement establishes JOBCODE's length as 7 (the maximum length from work.dept1 and work.dept2).
The jobcode = "FA1"; assignment does not change the established length.
The length jobcode $ 8; statement is ignored because it appears too late in the DATA step.
Therefore, the length of the variable JOBCODE in the output dataset WORK.ACCOUNTING will be 7.
Question 4:
What will be the result when this program is executed?
A. Data set SASUSER.ONE has 5 observations, SASUSER.TWO has 5 observations, data set WORK.OTHER has 3 observations.
B. Data set SASUSER.ONE has 2 observations, SASUSER.TWO has 2 observations, data set WORK.OTHER has 1 observation.
C. Data set SASUSER.ONE has 2 observations, SASUSER.TWO has 2 observations, data set WORK.OTHER has 5 observations.
D. No data sets are output. The DATA step fails execution due to syntax errors.
Answer: D
Explanation:
To correctly determine the outcome of a SAS program, it's essential to meticulously check for syntax errors before analyzing the logical flow. Even a seemingly minor syntax issue can prevent a program from executing and producing any output.
Let's perform a detailed line-by-line analysis of the provided SAS program:
This is the critical line containing a syntax error.
In SAS, when referencing a dataset that resides in a specific library other than WORK, the full, qualified name must be used, which follows the format libref.dataset-name.
The programmer intended to read from SASDATA.TWO. However, they wrote sasdata two.
SAS interprets sasdata as a library reference and two as a separate token, likely an attempt to name another dataset without a library reference. This construction (libref dataset-name without a period) is invalid syntax when attempting to read from a single, qualified dataset. The period . is mandatory to delineate the library reference from the dataset name when reading a specific dataset from a non-WORK library.
Correct syntax would be set sasdata.two;
if x = 5 then output sasuser.one;
Assuming the SET statement had been correct, this IF-THEN OUTPUT statement would conditionally write observations where X equals 5 to the sasuser.one dataset. Logically, this would result in 2 observations being written to sasuser.one (from the rows where X is 5 in the input SASDATA.TWO dataset).
else output sasdata two;
Again, assuming the SET statement was correct, this ELSE OUTPUT statement would conditionally write observations where X is not equal to 5 to the sasdata.two dataset. There is a logical issue here: if the input dataset is SASDATA.TWO, trying to output to SASDATA TWO (even if the syntax were SASDATA.TWO) implies overwriting the input, which is a common pattern for "update in place" but still requires correct syntax. More importantly, it also contains the same syntax error as the SET statement: sasdata two instead of sasdata.two.
Result of Execution:
Because of the syntax error in the SET statement (set sasdata two; instead of set sasdata.two;), the SAS compiler will detect an error. When a DATA step encounters a critical syntax error, it typically fails compilation, stops execution, and produces error messages in the SAS log. No output datasets are created. The program does not proceed to execute the IF-THEN logic.
Therefore, the correct answer is D. No data sets are output. The DATA step fails execution due to syntax errors.
Question 5:
Which footnote(s) will be displayed in the report generated by the PROC PRINT step?
A. All Products
B. Sales Report for Last Month All Products
C. All Products All Regions All Figures in Thousands of Dollars
D. Sales Report for Last Month All Products All Regions All Figures in Thousands of Dollars
Answer: D
Explanation:
In SAS, the FOOTNOTE statement is used to add descriptive text at the bottom of each page of procedure output. SAS supports up to 10 footnote lines, specified as FOOTNOTE1 through FOOTNOTE10. Understanding how these statements interact, especially when redefined, is key to predicting the final output.
The crucial behavior of FOOTNOTE statements is that they are positional and cumulative until explicitly redefined or cleared. When a specific FOOTNOTE statement (e.g., FOOTNOTE2) is encountered, it replaces any previously defined content for that specific footnote number. Other footnote numbers (e.g., FOOTNOTE1, FOOTNOTE3, FOOTNOTE4) remain unaffected unless they, too, are explicitly redefined or cleared.
Let's trace the execution of the provided SAS program step-by-step:
Initial FOOTNOTE Definitions (Global): The first block of FOOTNOTE statements defines four footnote lines globally, meaning they will apply to all subsequent procedure outputs until redefined or cleared.
footnote1 "Sales Report for Last Month";
footnote2 "Selected Products Only";
footnote3 "All Regions";
footnote4 "All Figures in Thousands of Dollars";
At this point, the active footnotes are:
FOOTNOTE1: "Sales Report for Last Month"
FOOTNOTE2: "Selected Products Only"
FOOTNOTE3: "All Regions"
FOOTNOTE4: "All Figures in Thousands of Dollars"
proc print data = sasuser.shoes;: This statement begins the PROC PRINT step. Any FOOTNOTE statements placed within a PROC step (before the RUN statement) will temporarily override globally defined footnotes for that specific procedure's output.
footnote2 "All Products";: This FOOTNOTE statement appears within the PROC PRINT step. It specifically redefines FOOTNOTE2.
The previous content of FOOTNOTE2 ("Selected Products Only") is now replaced by "All Products" for the duration of this PROC PRINT step.
Crucially, FOOTNOTE1, FOOTNOTE3, and FOOTNOTE4 are not mentioned or redefined in this PROC PRINT block. Therefore, their content remains as defined globally.
run;: This statement executes the PROC PRINT step.
Final Footnotes Displayed:
When PROC PRINT generates its output, it will use the most recently active definition for each footnote line. Combining the global definitions with the in-procedure redefinition, the footnotes displayed will be:
FOOTNOTE1: "Sales Report for Last Month" (from the global definition, as it was not overridden)
FOOTNOTE2: "All Products" (overridden by the definition within PROC PRINT)
FOOTNOTE3: "All Regions" (from the global definition, as it was not overridden)
FOOTNOTE4: "All Figures in Thousands of Dollars" (from the global definition, as it was not overridden)
Question 6:
Which SAS statement, when inserted into the program at <insert statement here>, will correctly result in a character variable named DEPARTMENT with the value "Printing750"?
A. department = dept || number;
B. department = left(dept) || number;
C. department = trim(dept) number;
D. department = trim(dept) || put(number, 3.);
Answer: D
Explanation:
This question tests understanding of character and numeric variable handling, implicit length assignments, and proper concatenation techniques in SAS. The goal is to combine a character string that might contain trailing spaces with a numeric value into a single, seamless character string.
Let's first analyze the data after the INPUT statement:
infile "dept";: Specifies the input file.
input dept $ 1-11 number 13-15;: Reads the raw data.
dept $ 1-11: Reads characters from columns 1 to 11. From the example data ("Printing "), dept will contain "Printing " (8 characters "Printing" followed by 3 spaces to fill 11 characters). The dept variable will have a length of 11.
number 13-15: Reads numeric digits from columns 13 to 15. From the example data ("750"), number will contain the numeric value 750.
We want the DEPARTMENT variable to be a character string "Printing750". This means we need to remove the trailing spaces from dept and convert the number (which is numeric) into its character representation before concatenating them.
Now, let's evaluate each option:
A. department = dept || number;
This statement attempts to concatenate a character variable (dept) with a numeric variable (number) using the || (concatenation) operator.
Result: This will cause a type mismatch error. SAS does not implicitly convert numeric values to character values during string concatenation. You must explicitly convert the numeric value to character.
B. department = left(dept) || number;
The LEFT() function removes leading blanks from a character string. Since dept has trailing blanks, LEFT(dept) would produce "Printing " (still with trailing spaces).
Similar to Option A, this statement still attempts to concatenate a character value (result of LEFT(dept)) with a numeric value (number).
Result: This will also cause a type mismatch error for the same reason as Option A.
C. department = trim(dept) number;
The TRIM() function correctly removes trailing blanks from a character string. So, TRIM(dept) would result in "Printing".
However, the syntax trim(dept) number; is invalid. SAS requires an explicit operator (like || for concatenation or mathematical operators) between expressions. Simply placing them side-by-side like this will result in a syntax error. This is not a valid way to concatenate in SAS.
D. department = trim(dept) || put(number, 3.);
This is the correct statement, combining the necessary functions and operators:
trim(dept): This function effectively removes the trailing spaces from dept, resulting in the character string "Printing".
put(number, 3.): The PUT() function is used to explicitly convert a numeric value (number) into a character string using a specified format (3. for a width of 3 characters). This will convert the numeric value 750 into the character string "750".
||: This is the correct concatenation operator in SAS, joining the two character strings.
Result: ("Printing") || ("750") correctly concatenates to form the character string "Printing750". The DEPARTMENT variable will be created as a character variable with a length sufficient to hold this result (which would be 11 characters).
Therefore, the only statement that correctly performs the necessary conversions and concatenations to achieve the desired result is option D.
Question 7:
What will be the final length and value of the variable ADDRESS in the output dataset?
A. Length is 14; value is "214 London Dri"
B. Length is 14; value is "214 London Way"
C. Length is 16; value is "214 London Drive"
D. Length is 200; value is "214 London Drive"
Answer: A
Explanation:
This question delves into critical SAS concepts concerning character variable length determination, particularly when variables are created implicitly through functions, and the behavior of the TRANWRD function. SAS assigns a length to a new variable based on its first appearance, and this length can lead to truncation if a later assigned value exceeds it.
Let's break down the program step-by-step:
Variable Creation and Length Assignment for address1: In this DATA step, address1 is created. Since no LENGTH statement is provided for address1 before its first assignment, SAS assigns its length based on the length of the value first assigned to it.
set one;: This reads observations from the WORK.ONE dataset created in the previous step. So, for the first (and only) observation, address1 (with length 14, value "214 London Way") is brought into the Program Data Vector (PDV).
address = tranwrd(address1, "Way", "Drive");: This statement creates a new variable named address and assigns it the result of the TRANWRD function.
The TRANWRD function replaces all occurrences of a specified substring within a string. Here, it will replace "Way" with "Drive" in the value of address1.
address1 = "214 London Way"
TRANWRD("214 London Way", "Way", "Drive") will produce the string "214 London Drive".
The string "214 London Drive" has 16 characters.
Length Assignment for address (The Tricky Part): This is where the crucial SAS rule comes into play. When a new character variable is created by an assignment statement involving a function (like TRANWRD, SUBSTR, CATX, etc.) and no explicit LENGTH statement for that new variable has been previously specified, SAS will typically assign the new variable the same length as the first argument to the function.
The first argument to TRANWRD here is address1.
The length of address1 (as determined in the first DATA step) is 14.
Therefore, the new variable address is assigned a length of 14.
Truncation: Since the calculated value from TRANWRD ("214 London Drive", which is 16 characters long) is longer than the assigned length of the address variable (14 characters), SAS will truncate the value. It will take only the first 14 characters of the result..
The variable ADDRESS in the output dataset will have a length of 14 and its value will be "214 London Dri".
This behavior is a common pitfall in SAS programming. To avoid truncation, one should explicitly define the length of address using a LENGTH statement before its first assignment in the DATA step, ensuring it's long enough to hold the longest possible result from the TRANWRD function (e.g., length address $ 16;).
Question 8:
What will be the final value of the variable PROD in the output dataset WORK.SETS?
A. 6
B. 7
C. 8
D. (missing numeric)
Answer: B
Explanation:
This question tests understanding of SAS DO loops, specifically the DO UNTIL construct, and the behavior of a sum statement (variable + expression;) within a DATA step. The interaction of these two elements determines the final value of the PROD variable.
Let's break down the code's execution flow:
data work.sets;: Initiates a DATA step, which processes implicitly in a loop (once per observation, though here no input dataset means one implicit iteration).
do until (prod gt 6);: This defines a DO UNTIL loop. Key characteristics of DO UNTIL loops:
The loop body executes at least once.
The condition (prod gt 6) is checked after each iteration of the loop body.
The loop continues to execute until the condition becomes true.
prod + 1;: This is a sum statement in SAS, which has special properties:
Automatic Initialization: If PROD is not defined or initialized to a value before its first use in a sum statement, SAS automatically initializes it to 0 for the first observation of the DATA step.
Automatic Retention: The value of PROD is automatically retained from one iteration of the DATA step to the next, similar to explicitly using a RETAIN statement. In this specific program, since there's no input dataset, the DATA step only runs for one implicit observation, but the prod + 1; statement within the DO loop still benefits from its internal retention, meaning PROD's value persists across the loop iterations.
Accumulation: On each execution of this statement, 1 is added to the current value of PROD.
The loop continues until PROD becomes 7. At that point, the condition (prod gt 6) becomes true, and the loop terminates. The value of PROD when the loop exits is 7. This is the value that will be written to the output dataset WORK.SETS.
Therefore, the final value of the variable PROD in the output data set is 7.
Question 9:
Which one of the following MERGE statements correctly completes the program to merge the two datasets by the common employee name, given that the BY statement specifies fname?
A. merge work.employee work.salary (fname = name);
B. merge work.employee work.salary (name = fname);
C. merge work.employee work.salary (rename = (fname = name));
D. merge work.employee work.salary (rename = (name = fname));
Answer: D
Explanation:
Merging datasets in SAS is a powerful operation for combining information from different sources based on common variables. When performing a match-merge (using a BY statement), a fundamental requirement is that the key variables used for matching must have the same name in all input datasets. If the key variables have different names but contain the same logical information (like employee names here, stored as fname in one dataset and name in another), a RENAME= dataset option is necessary.
Let's analyze the objective and each option:
Objective: The goal is to merge WORK.EMPLOYEE (which has fname) and WORK.SALARY (which has name) based on the employee's name. The partial program already specifies BY fname;. This means that for the merge to succeed, both input datasets must present a variable named fname to the MERGE statement.
Analysis of Options:
A. merge work.employee work.salary (fname = name);
This syntax is invalid. The format variable = variable directly inside the parentheses of a MERGE statement is not a valid way to rename or link variables for merging. SAS does not understand this as a renaming instruction. It would lead to a syntax error.
B. merge work.employee work.salary (name = fname);
This syntax is also invalid for the same reason as Option A. It does not conform to SAS's RENAME= option syntax.
C. merge work.employee work.salary (rename = (fname = name));
This option uses the correct RENAME= dataset option syntax. However, the renaming logic is incorrect for the stated problem.
(rename = (fname = name)) would instruct SAS to rename the fname variable from WORK.EMPLOYEE to name before the merge.
If fname in WORK.EMPLOYEE were renamed to name, then WORK.EMPLOYEE would no longer have a variable named fname during the merge. The BY fname; statement would then fail because fname would not exist in one of the input datasets (specifically, WORK.EMPLOYEE after the rename). This would result in an error.
D. merge work.employee work.salary (rename = (name = fname));
This is the correct statement.
It uses the RENAME= dataset option, applied to the WORK.SALARY dataset (work.salary (rename = (name = fname))).
(name = fname) instructs SAS to temporarily rename the variable name in the WORK.SALARY dataset to fname just for the duration of this DATA step's merge operation.
After this renaming, both datasets effectively have a variable named fname when they are processed by the MERGE statement.
WORK.EMPLOYEE contributes fname (original).
WORK.SALARY contributes fname (renamed from name).
Now, the BY fname; statement can successfully perform the match-merge because the common key variable fname exists in both datasets with the same name.
Therefore, to correctly complete the merge based on fname as specified in the BY statement, you must rename the name variable in WORK.SALARY to fname using the RENAME= dataset option.
Question 10:
Which SAS program correctly displays a listing of all datasets currently stored within the SASUSER library?
A. proc contents lib = sasuser.all; run;
B. proc contents data = sasuser.all; run;
C. proc contents lib = sasuser._alI_; run;
D. proc contents data = sasuser._all_; run;
Answer: D
Explanation:
The PROC CONTENTS procedure in SAS is a fundamental tool used to describe the contents of a SAS dataset or an entire SAS library. When an administrator needs to see all datasets within a specific library, a particular syntax involving a special SAS keyword is required.
Let's evaluate each option to determine the correct program:
A. proc contents lib = sasuser.all; run;
The LIB= option is used to specify a library whose engine information (e.g., path, type) you want to display, not its datasets. Furthermore, sasuser.all is interpreted as attempting to specify a dataset named ALL within the SASUSER library, not a keyword to list all datasets. This syntax is incorrect for listing all datasets.
B. proc contents data = sasuser.all; run;
The DATA= option is used to specify a particular SAS dataset whose contents you want to describe. If there truly were a dataset literally named ALL within the SASUSER library (sasuser.all), this command would describe only that single dataset. However, the question asks for a listing of all datasets, and all is not the special keyword SAS uses for this purpose. This syntax is incorrect for the stated objective.
C. proc contents lib = sasuser._alI_; run;
This option attempts to use the LIB= statement with a keyword that looks similar to _ALL_. However, notice the subtle but critical typographical error: it uses a capital 'I' (_alI_) instead of a lowercase 'L' (_all_ or _ALL_). SAS is case-insensitive for keywords, but it is sensitive to the actual characters used. _alI_ is not recognized as the special keyword for "all datasets" and would likely result in a syntax error or a "dataset not found" error if SAS tries to interpret it as a dataset name.
D. proc contents data = sasuser._all_; run;
This is the correct program.
DATA= option: This is the appropriate option to use with PROC CONTENTS when you want to specify a dataset or a collection of datasets (like all datasets in a library).
sasuser: This correctly specifies the library whose contents are to be listed.
_ALL_: This is a special, predefined SAS keyword (case-insensitive, so _all_ or _ALL_ both work) that instructs PROC CONTENTS to process all datasets within the specified library. When _ALL_ is used with the DATA= option, PROC CONTENTS generates a report that lists each dataset found in the library, along with its variable information.
Therefore, to obtain a listing of all datasets in the SASUSER library, the correct and standard SAS program is proc contents data = sasuser._all_; run;.
Site Search:
