With Engrafo you can automatically document your SAS jobs, giving you
a complete data catalog on data used in the programs
data lineage between programs and datasets
program statistics on runtime, usage of procedures and much more
detailed Flowcharts of SAS program flows
information on external input and output
…and much more
See the video to get information on how to use Engrafo SAS Analyzer
https://youtu.be/-zFKX6SBZpcDocumenting Work-libraries
Sometimes you do not want to document data stored in WROK-libraries.
When using Scaproc-files, the extension of the file indicates if Engrafo should treat WORK-libraries as ordinary data-references or not, e.g.
Chapter10.scp: Includes WORK-libraries in creating data catalog, data lineage and other documentation
Chapter10.scpwork: Does NOT include WORK-references in the automated documentation
Appsettings for SAS Analyzer
Headers in the Data Catalog
If you are only using the SAS Aanalyzer module, you might want to rename the headers in the data catalog.
That can be done in Appsettings.json. An example on this, could be:
"Labels": {
"Database": "SAS Database",
"Schema": "SAS Data Catalog",
"Table": "SAS Datasets",
“Column": "Variable",
},
Specific settings for the SAS Analyzer module
In appsettings.json there are the following settings
"SASAnalyzerSettings": {
"FileExcludes": {
"FileInput": ".sas, .pdf, .png, .jpg",
"FileOutput": ".sas, .pdf, .png, .jpg, .source, .index"
},
"Index": {
"Index": "true"
},
"Model": {
"Physical": "false"
}
References to external files
Your might want to exclude external file-references in the flowcharts and documentation. This can be done by excluding specific files by extension, e.g.
FileExcludes : {
"FileInput": ".sas, .pdf, .png, .jpg ",
"FileOutput": ".sas,, .pdf, .png, .jpg ",
},
Include Index-creation in flow chart
You can exclude index-references in the generated SAS Flowcharts. This can be done by setting the parameter “Index” to true or false
Index : {
"Index": "true",
},
Use physical model
In SAS programs Libnames are defined by a logic name pointing to a physical path, e.g.
libname LibnameToData “p:\SASdata”
"Model": {
"Physical": "false"
}
If you want to use physical references instead of logic, set Physical to true.
If you are using the physical model you also have the option to replace physical references with a logic name that you chose. The can be done in the mapping table in:
LibnamesMappings holds any wanted replacements. This can be useful if you have different environments having physical references pointing to the same directory but with different syntax, e.g.
Linux: //ffss/SASHelp
Windows \\mslib\SAShelp
LibnamesFromParsing
This table holds al the physical mappings to libnames from analyzed SAS scaproc logs
LibnamesTuUse