A REFRESH of the ASRs is not instantaneous. So this is a function that you should know more about.
CA Allocate does have some overhead. My standard "line" I used when I did training was:
For any beneficial "work" to be done, there is some price to pay.
One measure of one type of overhead is how long it takes to refresh your ASRs. To see how long this takes, look for this message in the SYSPRT DD of the VAM task:
START OF COMPILE OF VDSPROG ASR
WAS ON 11JAN12 AT 10:39.34
Then locate this message:
SUCCESSFUL COMPILE OF VDSPROG ASR
WAS ON 11JAN12 AT 10:39.45
Note that it took 11 seconds to assemble this set of ASRs that was 12,700 lines. That was 11 seconds that VAM was not handling allocations because of the REFRESH process.
This is a situation you need to be aware of so you do a REFRESH only when very necessary or preferably at times of low activity.
The worst example I recall was one sites ASRs that were more than 40,000 lines. The length of time for a REFRESH was intolerable - over 40 seconds - so they had to take on the task to re-write the ASRs.
So, the bottom-line suggestion is to keep your ASRs as short as feasible and perform a REFRESH at times of as low activity as possible.
If any questions, please contact CA Allocate Support. We can not revise your ASRs for you, but we can help with specific questions.
Release: ESBALQ99000-12.5-CA-Allocate-DASD Space and Placement-with Quota Manager-Extende