In JAL, I would like to setup some global values and global functions:

For example, a global receipient list so that if I have to add another person,
I need only modify 1 value instead of 90.

Also, there is a great deal of commonality in the jobs that are run. Is there a way
write a subroutine or function so that I can simply pass the different parameters
and reuse code.

For example, I always want to check whether a file received is of zero length or not.
This is done numerous different ways in different jobs. I would rather have one
'zeroByteLength' function that I can call in each script to do the check.

Thanks

Global functions can be defined in Tools/Script Library
Global variables can be defined in any script as
Dim GLOBAL.myvariable, datatype, [initial value]
or
Dim( GLOBAL.myvariable, datatype, [initial value] )

It is a good idea to create a job which will run on the scheduler startup and initialize global variables with some useful values.
For more info please see "Global variables" topic " in the on-line help.

: In JAL, I would like to setup some global values and global functions: For
: example, a global receipient list so that if I have to add another person,
: I need only modify 1 value instead of 90.

: Also, there is a great deal of commonality in the jobs that are run. Is there
: a way
: write a subroutine or function so that I can simply pass the different
: parameters
: and reuse code.

: For example, I always want to check whether a file received is of zero length
: or not.
: This is done numerous different ways in different jobs. I would rather have
: one
: 'zeroByteLength' function that I can call in each script to do the check.

: Thanks

In a previous topic, you talk about version 4 running all script type jobs as detached. How are you planning to take care of globals?

: Global functions can be defined in Tools/Script Library
: Global variables can be defined in any script as
: Dim GLOBAL.myvariable, datatype, [initial value]
: or
: Dim( GLOBAL.myvariable, datatype, [initial value] )

: It is a good idea to create a job which will run on the scheduler startup and
: initialize global variables with some useful values.
: For more info please see "Global variables" topic " in the
: on-line help.

Global variables will be saved in a cache file on the disk. Every time a reference to global variable is made its value will be read/written from/to the cache file. I assume there could be some performance hit if many global variables are created. On the other hand it should be 100% backward compatible with all previous versions.

: In a previous topic, you talk about version 4 running all script type jobs as
: detached. How are you planning to take care of globals?