The Adabas & Natural by Software AG Ideas Portal is hosted by Aha! Labs Inc.. Therefore, personally identifiable information are processed by Aha! Labs Inc., a company based in the United States of America. By using this Ideas Portal you agree to the
Terms of Service of Aha! Labs Inc.. For further information about Aha’s handling of your personally identifiable information, please go to:
https://www.aha.io/legal/security/gdpr.
You can use the same functions to pause and restart code coverage as you can use for the Profiler as described in https://documentation.softwareag.com/natural/nat921unx/webhelp/natux-webhelp/utis/profiler_batch_mode.htm#Profiler_batch_start_pause.
I think that Code Coverage is currently started at the beginning of the process, so the whole executed code is analyzed for future reference, although can be filtered. it may create large data files and use CPU cycles the whole time the process is active, which may be long if it is a Batch or an RPC. The ability to dynamically start and stop the activation of the Code Coverage, similar to what is available for Natural Profiler , can be useful - jence limiting the file sizes and resource usage. I would vote for an API , similar to USR8210 (I think) , to activate/deactivate the Code Coverage activity .