A few recommendations:
#2) save you original Global as you do otherwise. [Just to be Save]
#1) In Studio Copy class has a checkbox to copy Storage Definition (=Globals) . Set it.
In the new class add ClassParameter MANAGEDEXTENT=0 ;
/// to ignore this class. If set to 1 then the Extent Manager will register globals used by
/// the class and detect collisions. Unmanaged extents (MANAGEDEXTENT = 0) are not checked.
/// Currently, only classes using default storage (%Library.CacheStorage) can be managed.
Parameter MANAGEDEXTENT As INTEGER [ Constraint = "0,1", Flags = ENUM ] = 1;
So the old and the new class use the same Globals.
Now go on with #3 to #6
If you miss something in refactoring the damage should be limited as you just change names not the Storage in Globals.
Assuming the change of ClassName is all you do.
- Log in to post comments



This query plan tells you what is really happening.

