The key difference between a job shared and a module shared variable really exists across modules

[Swapnil Bankar 3]

In 'TIB_bwce_2.4.2_concepts.pdf',

we have following lines @page 18/35,

The key difference between a job shared and a module shared variable is that when jobs expand across

module boundaries, a job shared variable is visible outside the module it was set in, while the module

shared variable is visible only inside the module in which it was set.

Can you just confirm that that this mentioned difference really exists across modules

Or what is your understanding

My Observations,

1.Across modules means Application Module & Shared Module

2.And does not mean two Application Modules [you will get exception if you try to call any process across application modules]

3.In case mentioned in point 1, my observation is, not only job shared module but module shared variable (both defined in Shared Module) also visible in dependent Application Module.

[sangamesh -watage]

Module means any things shored / application. If we define madule shared variable in any application module AM it is accessible to all processed inside AM . If you AM process call other module process . This module shared variable is not accessible to other processes . It is restricted withing defines module.

Where as job shared variable is spanned across job irrespective of which module process it is calling . If it is part of same job. Job shared variable is accessible