Why is SAS considered self-documenting?
- 1 Answers
- 2569 Views
- Quintiles, I also Faced
- E-Mail Answers
Answer / ravi gupta
I think this is because in SAS by default we get detailed log.. listing out each and every step with ERROR/WARNINGs or NOTES, this is quite helpful in debugging.
On top of it you also have debugging options like - MACROGEN SYMBOLGEN MLOGIC MPRINT MFILE, which allows you to dig deeper and get even more detailed logs.
Looking at SAS log only you can make out what exactly the code is doing... you get the whole story documented itself - how many observations where read from input dataset and how many variables the new dataset have and if a variable was left uninitialised or truncated and lot more.
Its so well documented that you can retrieve your SAS code from its log using a simple regular expression.
However, I struggled to get SAS like logs in R & Python.
| Is This Answer Correct ? | 1 Yes | 1 No |
i am importing large data from oracle to work library. in log there is a error message worklibrary space is not enough. then how to import the data safely to sas environment.
Explain the use of proc gplot? : sas-grid-administration
what has been your most common programming mistake? : Sas programming
Do you prefer Proc Report or Proc Tabulate? Why?
how do you validate sas program?
what are scrubing procedures in SAS?
In the flow of DATA step processing, what is the first action in a typical DATA Step?
i have a dataset with var1,var2,var3; i want to upload the titles for the variables . How can we?
What's the difference between VAR A1 - A4 and VAR A1 - A4?
I have 50 variables in one data set, In reports i want to generate every 10 variables in one page how we will write code in proc report.
How would you compile all macros from a folder in a study, within the autoexec program?
Describe the function and untility of the most difficult SAS macro that you have written.
Teradata 
