Re: [foxboro] Best method for remote read-write DM/AM?
- From: "Hicks, David" <david.hicks@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Sat, 26 May 2007 09:37:26 -0400
Corey,
At certain times it is necessary to "protect" or limit access to certain
keys or actions in the AM for any and all users whether remote or local,
either when the workstation is booted or when the remote DM and/or AM is
accessed.
Adding the following line to the bottom of the /usr/fox/wp/data/am_cmds
file facilitates this requirement.
=3D amcmd "protect value xxx"
This will protect the key or action on any and all AM's when it is
started regardless of which environment the DM is launched in. An
environment change is then required to unprotect the key or action. The
same string can then be used in the corresponding .env file to
"unprotect" the key or action with an environment change.
=3D amcmd "unprotect value xxx" =
David Hicks
=
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
Office (713) 329-1735
Fax (713) 329-1913
Cellular (713) 447-4053
=
2450 W. Cardinal Dr.
Beaumont, TX 77705
Office (409) 840-8006
Fax (409) 842-3197
=
david.hicks@xxxxxxxxxxxxxxxx
=
=
=
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Friday, May 25, 2007 9:53 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Best method for remote read-write DM/AM?
On our 6.5.3 system it does no good to set the permissions for the AM in
the environment file, because the am_cmds is what launches the initial =
environment, and that line is commented out, so the AM never runs the =
initial environment. You could rectify this of course, but you are then
editing two files.
I have kind of decided to put default/global/early items in the *_cmds
or =
init.user, and anything that _changes_ when you change environments in
the =
environment files. I initially tried to execute all my custom stuff as =
external dmcmd/amcmd scripts that I called from the *_cmds files, but
that =
doesn't work in am_cmds; it never runs the external script.
Corey Clingo
BASF Corporation
Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.
_______________________________________________________________________
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:
