Dirk & Others, I strongly recommend a review of B0400DF (HLBL User Guide) when writing standard exception handling subroutines. More specifically the "Useful Hints on SBX Programming" section. The document even provides sample code on how to correctly implement the SBX code and offers many hints as to do's and don'ts. It is also advisable to limit the number of SBXs (eg: TO_SYS_ERR, TO_USR_ERR, TO_MANUAL, TO_INACTIVE, TO_PAUSED). If the sequence is executing code in one of these SBXs, and another exception is caused, eg: block placed to manual by user, your CP can REBOOT with a memory violation. I have seen this at a site, and have replicated it on a testbed. One of the documents advises not to use statements with multiple C:B.P references. Instead you could have two variables (or just one) and do something like this: var1 := C:B.P1; var2 := C:B.P2; IF (var1 < var2) THEN ......... Hope this helps, Maks Wilde -- Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. _______________________________________________________________________ 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