Example 2 illustrates the usage additional variables.

Explanation:

The variables are stored in the registry. Originally I planned to have 
  PROFILE   remains active, until deleted
  GLOBAL    remains active, until PC is terminated
  SCRIPT    remains active, until root script is terminated, that means all subsequently
	    called scripts have access to this pool.
  LOCAL	    just active within the currently active scipt.

The last two SCRIPT and LOCAL, I failed because I could not find a "transaction number"
which stays during the execution of a script. The concept of transactions seems to be
different from what I know from main frame (MVS) environment.

Even GLOBAL requires a DROPGLBL.EXE inserted in the autostart folder.
  

The script tries to load variables from the global pool, which is not available the 
first time. After displaying a query you can create and store them.
The next time you have access to the data and can refresh them and so on. 	  
 
Action:

1. Run the "MACRO.EXE" (ADD-in Tools)

2. Start "PRECOMPILE" to get a translated version.

3. Run EXAMPLE2.DSC (PF9)
4. PRESS OK, for creating the variables
5. Run EXAMPLE2.DSC (PF9) again
  



 