Re: [foxboro] "protect name .PARM" DM/FV command
- From: <duc.do@xxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 23 May 2007 09:27:07 -0400
Corey,
You should know by now that there's no silver bullet. And there's no
easy way out. (But then again I'm toughened by having to work with SAP
before. I/A is a piece of cake compare to that monstrous system.)
But funny you should mention running d_edit on the detail displays and
faceplates on every upgrade. That's what I resigned myself to a long
time ago. Now I have a script file (with double stern warnings of "do
you want to do this?" and "do you really want to do this?") to run a
series of dozens of d_edit commands on the various faceplates and detail
displays, mainly to change access class for various picks on those
graphics. Brute force, but effective.
Duc
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Wednesday, May 23, 2007 9:14 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] "protect name .PARM" DM/FV command
True. This mechanism is not foolproof, even if it had worked as I=20
envisioned/desired. But it would eliminate 90-95% of the issues, and=20
prevent all that typing of loopback connections in situations where=20
changes were not desired, but it wouldn't be the end of the world if
they=20
happened. I was just salivating for a moment or two at the prospect of=20
several lines of "protect name .DONTTOUCHTHIS" lines in an environment=20
script to protect a desired list of parameters, rather than a
combination=20
of locking them, having some enforcer application set them back when
they=20
changed (for all those settable/non-connectable ones), or d_edit'ing all
the faceplates and details to control access via protection classes - on
every system upgrade (but then again I'm toying with the idea of making
my=20
own, as I find the system-supplied ones lacking in several areas, so
maybe=20
that last one is not such a big deal).
Corey Clingo
BASF Corporation
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
