Re: Correct use of STATIC variables

[Rory Hewitt <roryhewitt@xxxxxxxxx>]

Kurt,

This makes  a lot of sense, especially if the variable is a large text
variable. I have several procedures which pass large strings (65535 bytes)
as parameters, and include local work variables defined the same way. Rather
than change the parameters or make the variables varying (which would
require a bunch of analysis), I did a project to simply identify these
procedures, check that the explicit code already effectively initialized the
variable, and then changed them to be static. Much better performance
resulted.

Rory

On Tue, Jan 26, 2010 at 11:23 AM, Kurt Anderson <
kurt.anderson@xxxxxxxxxxxxxx> wrote:

> I don't' really know what the programs David works on pertain to, but there
> is another purpose of Static.
>
> In my environment, we process millions of records in batch.  A procedure
> could then be called a million times or more within the life of a job.
>  There are times when I will make local variables static so all the stuff
> that happens under the covers for a non-static local variable every time the
> procedure is called won't have to happen.  I only do this when the procedure
> doesn't rely on the procedure to initialize the variable (i.e. the procedure
> will always set the value of the local variable in the calc specs (generally
> condition-based) before it is used).
>
> -Kurt Anderson