Fraktal SAS Programming

Welcome to the Introduction to "Fraktal SAS Programming".

The pages provided here are intended to serve as guidelines for Beginners in SAS Based Reporting from Database Tables.

Why "Fraktal"? Try this movie on measurement of coast lines by using Fractals (German audio)

We are using the term "Fraktal" with a "k" here to emphasize, that the programming concept introduced is derived from Fractal Geometry in Mathematics but not identical to it.

1. Preface: Learn about appropriate positioning of the "SAS System" from "SAS Institute".
2. Coding: Read important considerations on front-end program structure and back-end runtime behaviour.
   1. Implicit Coding
   2. Explicit Coding
3. Macro: Find out how every single aspect from your workflow definition can easily be reflected and implemented.
   1. Straightforward Coding
   2. Generalized Approach
   3. Advanced Coding
   4. Symbol Tables
   5. Parameter Scope
   6. Extending Control
      1. Apply Logic
      2. Process Metadata
         1. What is Metadata?
         2. Process Metadata: List
         3. Process Metadata: Numbered
         4. Process Metadata: Direct
      3. Workflow Documentation
         1. Stored Workflow Documentation
      4. Realtime Information
   7. Fully Qualified Coding
4. DBMS: Talk to Database Management Systems from within your SAS program to build a seamlessly integrated workflow.
   1. Libname Engine
   2. Hybrid Queries
   3. Passthru SQL
5. Programming: Communicate your algorithm to SAS code processors by applying them to data and code as well.
   1. Processing Records
   2. Generating Code
6. Data Structures: Discover the the key to flexibility and efficiency in SAS programming!
   1. Tables and Views
   2. Meta Data Tables
   3. SAS Formats

Fraktal SAS Programming is considered to be "fractal" because the program archtitecture is suggested to use minimized i.e. smallest scale modules to comprise the implementation from. Unlike fractal curves segments, e.g. used in coast line measurement, the module size meets a lower limit introduced by syntactic properties. Nevertheless, the module size possible will range between a few lines and very few screen pages. Overall size of a module will very rarely reach 100 lines of code. This includes declares, communication and documentation as well as logic like loops and branches.

To make these guidelines compatible with the subject they present, the structure is likewise modularized to a maximum: It is comprised from half-page text slides, making tiny lessons that are easily taken one by one.