Static vs. Dynamic storage (was Activation groups for beginners)

 > I guess I'm not clear on how static storage is "shared".

It is not shared at all.  "static" is what you probably think of as "normal"
variable storage in an RPG program.  The notion of designating storage as
static came about because in subprocedures the default is dynamic.  By this
we mean that the storage is allocated when the subprocedure is entered, and
deallocated when the subprocedure returns.  If you want to have storage in a
subprocedure behave like "normal" storage, then you have to designate the
variable(s) as STATIC.

For sharing of storage between modules the variables have to be designated
as Export(ed) by the owning program/service program and Import(ed) by all
those that wish to share that storage.

Jon Paris
Partner400