Extending Control (from Fraktal SAS Programming): Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
K |
K |
||
| Zeile 24: | Zeile 24: | ||
|zurück=Parameter Scope (from Fraktal SAS Programming) | |zurück=Parameter Scope (from Fraktal SAS Programming) | ||
|rechts=xx_right.png | |rechts=xx_right.png | ||
| − | |vorwärts= | + | |vorwärts=Straightforward Coding (from Fraktal SAS Programming) |
|hoch=Duck_zazy_com.png | |hoch=Duck_zazy_com.png | ||
|übersicht=Macro (from Fraktal SAS Programming) | |übersicht=Macro (from Fraktal SAS Programming) | ||
}} | }} | ||
Version vom 13. Mai 2014, 20:45 Uhr
|
|
|
|
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:
- Apply Logic: Check, branch and loop for specified parameters’ values
- Process Metadata: Navigate through the ecosystem by reading and processing metadata
- Workflow Documentation: Document workflow by writing comments to the LOG and generated code to a program file
- Realtime Information: Inform responsibles about invocation by sending an email
We will implement these requirements now step by step and thereby touch relevant parts of the so-called SAS Macro Facility.
|
|
|
|
