Page History
...
- Begin with a "*" (asterisk).
- At least 4 characters in length.
- Not contain imbedded embedded blanks.
- Not be *ALL, *ALL_REAL, *ALL_VIRT, *DEFAULT, *EXCLUDING, *HIVAL, *INCLUDING, *LOVAL, *NAVAIL, or *NULL as these values are reserved by LANSA.
- Not begin with *MTXT because this prefix is reserved for multilingual variables.
...
Mandatory. Default value is STATIC. Specifies how LANSA is to derive the system variable within a file I/O module or user-written function that references it. Allowable values are:
STATIC | The system variable is a static value, therefore its value can be derived once (during program initialisationinitialization) by LANSA. Examples of static system variables would include the current job name, the current user name, and most probably the current date (providing that applications do not normally span midnight while executing). |
DYNAMIC | The system variable is a dynamic value, therefore its value must be derived each and every time it is referenced. Examples of dynamic system variables would include the current time, the current output queue name and library, and all user-defined system variables that "allocate" values such as the next invoice number, the next batch number, etc. Note that every time a dynamic system variable is referenced the associated evaluation program is called to "refresh" the system variable. Excessive use of dynamic system variables with complex evaluation programs may degrade LANSA performance. |
...
Note also that the program should be able to be located in the user's library list at the time the system variable is evaluated. For more information refer to System Variable Evaluation Programs in the Visual LANSA Developer Guide.
...