Last updated on OCTOBER 29, 2014
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0]
Information in this document applies to any platform.
***Checked for relevance on 29-OCt-2014***
We are using cm_cache in some of our code. In details, we are creating a flist to capturing some CM specific information
and store this information in a global cm_cache. Whenever needed, we 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_XXXX_cm_context_flist_ptr, (void *)&key, cm_flistp, &err);
We don't have enough information regarding how cm_cache_update_entry manage memory. The question here is that after we call cm_cache_update_entry(),
do we 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?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms