At this point, you've had lots of good advice. So, I thought I'd add something different (no, not JUST bad advice). There are four repositories of CP Configuration information: 1) CSA which records: a) for each control station, the compound names in the station b) for each compound, the block names in the compound c) for each block, the block type of the block Additionally, it has a fixed set of files that contain the parameter names of each supported block type. It is this set of files that leads to the requirement that CSA always be on the AW/AP with the highest software version. 2) The CP source code files a) These files are found in /opt/fox/ciocfg/<cplbug> plus /opt/fox/ciocfg/<cmpdName> where <cmpdName> is the name of a compound that holds a sequence or PLB block. b) The most famous of these files is the "workfile" (<cplbug>.wf) found in /optt/fox/ciocfg which contains the values of all block parameters. Less well known are the .O files which contain pointers into either another .O file (<cplbug>.O) or into the workfile (<cmpdName>.O). c) The sequence and PLB block source files found in /opt/fox/ciocfg/<cmpdName> are what you see when you enter the ICC and edit them. The compiled versions are in this directory as well. 3) The checkpoint file a) This file is stored in /usr/fox/sp/files as <cplbug>.UC. b) It contains a copy of the memory of the CP in a binary format. c) It can be read (generally speaking) with dbvu. d) It cannot be used to regenerate the full set of CP source files. 4) The CP's RAM a) There is a copy in each of the CP FT pairs. b) When a CP is replaced, the memory is copied from its mate and synchronized. It is possible for any of these to become out of sync with any of the others. The most common source of such discrepancy is the restoration of either the CSA host or the CP host from an old tape. The official way to synchronize these databases is 'Initialize, Reboot, & Load All'. There are other techniques: CSA - there are a set of tools to manipulate the CSA database. They were originally developed to help merge separate nodes into one system, but can be used to make any desired change to CSA. Look in /opt/fox/csa and /usr/fox/csa. Workfile: Compound/Block mismatches Save All what you have. Document the configuration of the CP using dbvu, refs, paper/pen, etc. Take the save all to a different AW/AP (off-line), load it into a CP image or off-line volume. Correct the errors. Tar off the source directories. Tar them back onto the original system. Fix CSA. Parameter Value mismatches Use Upload from within the ICC Checkpoint - Simply checkpoint the CP using the ICC, SMDH, or cpoint. The next reboot will preserve whatever is in the CP. CP RAM - This write-up assumes that you don't want to initialize/reboot/load. Re: We can not delete them, because they are running OK, but need to back up properly because we feel they will be lost if we reboot the CP. So, in response to "we feel they (the blocks found in the CP, but not ICC - AJ) will be lost if we reboot the CP", you do not need to worry if you checkpoint the CP. Re: Fixing a workfile It can be done without the initialize/reboot/load procedure BUT: 1) It is not the official position 2) It is not for the faint of heart, but really the risk is low since the workfiles are wrong anyway. 3) Is non-trivial 4) Should only be used after much practice to be sure you understand what you are doing and to ensure that you really have all of the necessary changes. Remember the Sequence Block and Ladder Logic code could have changed as well and there is no way to recover Sequence Code changes from a running CP. I hope this helps _______________________________________________________________________ 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