I thought the point of the CATTR is to allow to put pieces of code such as the
external module CSRC4BLD in the same class
> On Nov 22, 2020, at 10:35 PM, Keven Hall wrote:
>
> Any VCon or ACon moved along to CSA with the SRB code will refer to
> locations in your private area and probably
Any VCon or ACon moved along to CSA with the SRB code will refer to locations
in your private area and probably would not resolve satisfactorily in the
addres space the SRB is scheduled for execution
Keven
> On Nov 22, 2020, at 21:05, Joseph Reichman wrote:
>
> It would seem to me that if
It would seem to me that if CATTR segregates the code I should be able to dine
how put the external reference for CSR4BLD in that class
Thanks
> On Nov 22, 2020, at 10:01 PM, Keven Hall wrote:
>
> If your SRB code needs to be in common storage, maybe an better solution
> might be to put
If your SRB code needs to be in common storage, maybe an better solution might
be to put it in a separate module and issue a global or a directed LOAD
(according to your requirements for module persistence) to put it there. That
will also obviate any need to adjust AdCons during relocation
Hi
I have SRB code in my Assembly which I segregated with a CLASS via CATTR
In that SRB routine I am calling CSRC4BLD statically i.e with a VCON
Since I am going to move this code to CSA I would like the =V(CSRC4BLD) to
be in the same class where I defined my SRB so when I MVCL the
