Where variables are stored
The main issues to remember about variables are as follows:
- Name your local variables; otherwise, PATROL will do it for you, and you will not be able to use them in your script later.
- Use configuration variables only when necessary (resource usage).
- Beware of cumulative global variables (memory usage).
Browsing the Namespace
This section provides an example script for browsing a namespace.
Namespace and Attributes
The PATROL namespace is a hierarchical structure of objects. The hierarchy is made up of the following objects, with each their own attributes.
- Root object '/'
- Application class level
- Application instance level
- Parameter level
Each of these objects have a set of attributes. Some of them are shown on the slide below. Besides the builtin attributes, the namespace also contains configuration variables and user defined global variables. The local variables are local to a PSL process and not accessible in the namespace. The following figure shows the attributes in the PATROL namespace.
Attributes in the PATROL namespace
Context of a PSL Process
When a PSL process is started, it gets launched in a certain context. The following figure shows the context for PSL processes.
Context of a PSL process