Extending Control (from Fraktal SAS Programming): Unterschied zwischen den Versionen

Aus phenixxenia.org
Zur Navigation springen Zur Suche springen
(Die Seite wurde neu angelegt: „Now, with proper declaration, it is safe to run your MACRO as a component in a validated system. However, it is still difficult to follow its results and disco…“)
 
K
Zeile 1: Zeile 1:
 +
[[Kategorie:zazy]]
 +
{{SeitenNavigation1
 +
|links=xx_left.png
 +
|zurück=Parameter Scope (from Fraktal SAS Programming)
 +
|rechts=xx_right.png
 +
|vorwärts=Apply Logic (from Fraktal SAS Programming)
 +
|hoch=Duck_zazy_com.png
 +
|übersicht=Macro (from Fraktal SAS Programming)
 +
}}
 +
 
Now, with proper declaration, it is safe to run your MACRO as a component in a validated system. However, it is still difficult to follow its results and discover failure risks or un-wanted misbehavior.  
 
Now, with proper declaration, it is safe to run your MACRO as a component in a validated system. However, it is still difficult to follow its results and discover failure risks or un-wanted misbehavior.  
  
Zeile 10: Zeile 20:
  
 
We will implement these requirements now step by step and thereby touch relevant parts of the '''so-called ''SAS Macro Facility'''''.
 
We will implement these requirements now step by step and thereby touch relevant parts of the '''so-called ''SAS Macro Facility'''''.
 +
 +
{{SeitenNavigation1
 +
|links=xx_left.png
 +
|zurück=Parameter Scope (from Fraktal SAS Programming)
 +
|rechts=xx_right.png
 +
|vorwärts=Apply Logic (from Fraktal SAS Programming)
 +
|hoch=Duck_zazy_com.png
 +
|übersicht=Macro (from Fraktal SAS Programming)
 +
}}

Version vom 30. Januar 2014, 10:12 Uhr

Zurück

Übersicht

Vorwärts

Now, with proper declaration, it is safe to run your MACRO as a component in a validated system. However, it is still difficult to follow its results and discover failure risks or un-wanted misbehavior.

You might therefore find it useful to add functionality such as:

  1. apply logic to check for parameters’ appropriate values
  2. navigate through the ecosystem by reading and processing metadata
  3. document workflow by writing comments to the LOG
  4. inform responsibles about invocation by sending an email
  5. write a text file that contains the plain code the MACRO generated


We will implement these requirements now step by step and thereby touch relevant parts of the so-called SAS Macro Facility.

Zurück

Übersicht

Vorwärts