You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Adding FIX on bottom level of large sparse dimension causes DATACOPY and CLEARDATA commands to long?

Accepted answer


I am working with a fairly large application with a sparse dimension containing over 50,000 bottom level members. I am trying to improve performance of our business rules, especially various data copies and clears. We have a specific business rule where, if we do not FIX on the large sparse dimension (project) at all, it runs significantly faster than if I use either @RELATIVE,0 (this one never finishes) or @LEVMBRS,0 (this one takes 5 minutes). Any idea why this would be the case? I would think that reducing the members required for the DATACOPY by FIXing on the bottom of

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!