Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

Se See the video to get information on hos how to use Engrafo SAS Analyzer

...

When using Scaproc-files, the extension of the file indicates if Engrafo should treat WORK-libraries as ordinary data-referenes 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

...

Settings and options for Engrafo SAS Analyzer

Headers in the Data Catalog

...

"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

...

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:

image-20240305-102623.pngImage Added

  1. 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.

    1. Linux: //ffss/SASHelp

    2. Windows \\mslib\SAShelp

  2. LibnamesFromParsing. This table holds al the physical mappings to libnames from analyzed SAS scaproc logs and can be utilized for 3)

  3. LibnamesTuUse. This Table holds any mapping you like between the physical references and the logic names you chose. e.g

    1. WORKStandard;W:\SASWORK\TD15948_DKSPAS111
      (This replaces W:\SASWORK\TD15948_DKSPAS111 with WORKStandard in the Data catalog)