that was the policy when I started at my current gig, I now manage the
policies so I usually cycle from CFMRPOL1 - 2 .etc...
activate the new policy (2), if there' issues I just reactivate policy (1)
Carmen
On 12/9/2022 9:16 AM, Mark Jacobs wrote:
At $currentjob whenever an XCF policy is changed and stored in the couple
dataset their standard practice is to replace the current active policy using
the same name, CFRMPOL as an example, then activate it. IMHO, this is a bad
practice. I always wrote the updated policy with a new name, then activated
that. What are y'all doing in this arena?
Mark Jacobs
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
--
Carmen
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
