Re: [foxboro] Cross Referencing Parameters

But Duc, the beauty of the unsecured set is also what makes it tough 
(nearly impossible) to cross reference.  It could be set from a display, or 
many displays, a piece of sequence logic or many pieces of sequence logic, 
a program using FoxAPI, or AIMapi, a shell script using omset, and there 
are probably other places as well.

It's easy enough to check sequence code for a particular C:B.P with several 
tools that are available IF the C:B.P is constructed prior to run 
time.  (See Sascha's comments along this line)
It is also relatively easy to de-construct displays and search for an exact 
C:B.P, but there could be substitution lists using text files, or partial 
naming constructs in the display file.  In each case additional (difficult) 
checking is needed.

To the best of my knowledge there is no way to completely search for script 
files and/or executables that set OM variables.

SO, should Foxboro provide a tool that manages to find 90% of the cases 
where an unsecured write occurs, but cannot guarantee that it isn't used 
somewhere else? I don't know, but I do know that it would take a really 
huge effort to handle all of the cases could come up.

Regards,
David




"Quote me as saying I was misquoted."
Groucho Marx

 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: