dynamic update of a policy without stopping CDP started tasks.

Thank you for this submission! This Idea was functionally delivered in our 4Q 2022 release. Please see the "What's new in 5.1" section of our product documentation for more details.

Extract from the case # TS006492971 :

Initially, the CDP product was purchased in my company to capture the RACF SMFs and send them under Splunk : The purpose was to monitor security violations.

But we would like to use it more intensively and we are configuring it to capture other types of SMF records. That's why we need to do stop/start as we deploy.

Also, we decided to send only the interesting fields by defining DEFINE UPDATE. But sometimes we need to change these definitions, by adding a new field that we think is interesting for a new need. This also obliges us to do stops/start.

Currently, we do between two to five stops per month. But, even when the deployment is complete, I think we will still need to update the configuration for new needs. Or when we will install new PTFs.

The loss of SMF 80 capture during shutdown / restart is a real problem because we can miss security violations.

Maybe when this product was purchased, we were not well advised because it does not allow to work in the expected high availability.

I am not sure that the workaround consisting of the use of two sets of CDP procs can be used in my company (duplicated data and not easy management).

I hope you now have a better understanding of why we change the configuration of CDP so frequently.

Please let me know if I can move the dynamic config to the top of the top of the list of new fonctions. :-D

Sebastien COUVENHES - La Banque Postale (FRANCE)