Question Regarding Cm_cache_update_entry()
(Doc ID 1531289.1)
Last updated on APRIL 03, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.4.0]
Information in this document applies to any platform.
One is using cm_cache in some custom code. In detail, one is creating a flist to capturing some CM specific information and store this information in a global cm_cache. Whenever needed, one can run some opcode to pull out that CM specific information for debugging purpose.
The logic is like below :
- Gather cm specific information and use to create cm_flistp;
- set key = current cm pid;
- cm_cache_update_entry (config_CUSTOM_cm_context_flist_ptr, (void *)&key, cm_flistp, &err);
But there is no enough information regarding how cm_cache_update_entry manages memory. The question here is, after calling cm_cache_update_entry(), is there a need to destroy cm_flistp ? In other words, does cm_cache_update_entry() make a copy of input cm_flistp or use the existing cm_flistp memory?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document