There are some ChangeMan ZMF functions in ChangeMan ZMF's ISPF dialog that are typically NOT allowed to be used by just any developer, e.g. because they may impact the integrity of ChangeMan ZMF managed projects. Some examples are:
- Revert a package back to development when the approval process has not been started (= not even 1 approval has been given), because in that case revert is allowed by anybody with application update access (and the CMNxREVR / CMNREVRT entity is not checked!).
- Setting certain user options to some special value (e.g. some Y/N flag to skip some validation in the staging job).
- A scratch request is commonly considered as a dangerous ChangeMan ZMF feature, because of the known ChangeMan ZMF issues related to using scratch request, e.g.: ChangeMan ZMF audit does not include any validations related to scratch requests.
- A selective unfreeze (followed by edit-in-stage and re-freeze) of components in a successfully audited and frozen package, which may introduce inconsistencies for which no built-in controls exist in ChangeMan ZMF to prevent them.
- ...
Just a complete disable of a function like 'unfreeze' (or utility request 'rename') might be an option in certain cases, which is typically done by just remove it from the ISPF panels. But how can you implement something to restrict access to such functions (without removing them entirely)?
READ MORE