Reason:
Over 254 updateable DVWs are currently nested and pending update in the current application. CA Ideal must store initial values and updated values for updateable DVWs that makes simultaneous nested updates extremely expensive.
Action:
Consider restructuring your program to perform FOR constructs one after the other, rather than nesting FOR constructs more deeply in one another. Remember that data from a CA Ideal DVW are accessible to CA Ideal for non-update operations after the ENDFOR, so there is no real need to maintain an active nesting for input-only data.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|