Stefano,
I think your intention is not only to protect Environments but to
enable/disable omsets.
Take a look at the following extract of an Env-Configuration:
dmcmd chng_env
dmcmd protect value 2
dmcmd disable omsets
== $DMNAME DMName1 enable omsets
== $DMNAME DMName1 unprotect value 2
==
Title: RE: Protecting Environments
Hi,
You could add the following lines
to all of your environmental scripts,
Customize the dmname and access class list entries as
required. This will work for dm's, but you will
have to consider the alarm managers as well.
dmcmd protect all
== $DMNAME
