Re: [foxboro] Setting Application Objects from IND blocks

Johnson, Alex (Foxboro) wrote:

> 2) The BPCSTM parameter will limit the number of statements per BPC.

Well, a coworker and I had an argument about this a while ago, so we did 
some tests. Just for the record: It seemed to me that the BPCSTM 
parameter - despite its name - rather limits statements per period. If I 
remember correctly it was on a CP with a BPC of 0.1 sec. But it could 
well be that we misinterpreted our results.

> 4) External references like yours (:A:O.A := 2) will suspend the block's
> execution.

Not only the execution of the block containing the reference, it seems. 
In a project I recently did there was a typo in an external reference. 
This causes the IND block to pause until searching for the reference had 
timed out. After that, it gave an error but since it was forced to AUTO 
and ACTIVE it directly tried again. So far, so good. The, um, 
"interesting" side effect was: This typo not only caused the IND block 
containing it to pause until timeout, but rather _ALL_ IND blocks 
running in that CP stopped resolving external references until the time 
out of the misspelled one was over. This decreased performance of our 
sequence blocks dramatically and it took us a while until we figured it 
out. We even exchanged the CP before. :|

-- 
Gruß,

Sascha Wildner
erpicon Software Development GmbH
Neusser Str. 724-726
50737 Köln
Germany

Phone: +49 221 9746069
Fax:   +49 221 9746099
eMail: swildner@xxxxxxxxxx

 
 
_______________________________________________________________________
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: