Extending Control (from Fraktal SAS Programming): Unterschied zwischen den Versionen
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 |
||
| (9 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
| 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=Fully Qualified Coding (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. | ||
You might therefore find it useful to add functionality such as: | You might therefore find it useful to add functionality such as: | ||
| − | + | * [[Apply Logic (from Fraktal SAS Programming)|'''Apply Logic:''' Check, branch and loop for specified parameters’ values]] | |
| − | + | * [[Process Metadata (from Fraktal SAS Programming)|'''Process Metadata:''' Navigate through the ecosystem by reading and processing metadata]] | |
| − | + | * [[Workflow Documentation (from Fraktal SAS Programming)|'''Workflow Documentation:''' Document workflow by writing comments to the LOG and '''generated code''' to a program file]] | |
| − | + | * [[Realtime Information (from Fraktal SAS Programming)|'''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'''''. | 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=Fully Qualified Coding (from Fraktal SAS Programming) | ||
| + | |hoch=Duck_zazy_com.png | ||
| + | |übersicht=Macro (from Fraktal SAS Programming) | ||
| + | }} | ||
Aktuelle Version vom 10. November 2022, 13:03 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.
|
|
|
|
