Other tools to check synchronization of all the pertinent data files can be obtained
and aren't mentioned here. When installed, check_db_sync and ck_multi_cps in the
directory check_sync located in /opt/fox/bin/tools will give you a warm and fuzzy
feeling when it successfully reports databases are synchronized. These tools are a
part of the (now partially defunct) 'bootless upgrade' feature. I run these once a
week and have discovered problems long before they cause real trouble.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 7:29 PM
To: Foxboro DCS Mail List
Subject: Synchronization (was RE: HLBL REF.)
Corey,
It is critical that the CSA database, the station volume workfile and the
checkpoint file stay synchronized. Because parameters are constantly
changing on the CP, it is normal that the setable parameters in the CP will
not match the other files, although the non-settable parameters must match.
There are several things that can cause a problem between CP, CSA, station
workfile and checkpoint file. Some of these include:
1) Power failure or system reboot during ICC session
2) Improper exit from ICC
3) Tape restore
4) setpars
5) CSA tools
6) ICC use with severe station overloading
Other causes probably exist. Corruption of CSA, work file or checkpoint
file is possible too. Of the list above, #1 is the one I have seen most
often. Typically, an ICC session is left open and is still open when the
computer or xterminal it is running on is rebooted (before checkpoint).
Tape restore of an AP or AW is a tricky one. If changes have been made in
ICC since the tape you are restoring from was made, and if no current
SaveAlls exist, you will probably need to restore from tape, reboot the CP
(to checkpoint file from tape) and re-create the changes in ICC made after
the tape.
A couple of items that may not be obvious:
1) Upload only updates settable parameters from CP to workfile. Assumption
probably is that non-settable parameters shouldn't need to be updated from
CP.
2) A SaveAll is not made from the CP but from the workfile. If setpars is
used to change a non-settable parameter on the CP, a SaveAll won't reflect
that change even after an upload.
Tools are available for troubleshooting mismatches:
Select views parameters in CP.
iccprt views parameters in workfile.
dbvu views parameters in checkpoint file (-t option, needs checkpoint file,
map file and image file).
CSA_save exports an ascii copy of the CSA database.
Regards,
Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
------------------------------------
Tel: +64 (9) 573 7690
Fax: +64 (9) 573 7691
Corey R Clingo
<[EMAIL PROTECTED]> To: Foxboro DCS Mail List
<[EMAIL PROTECTED]>
Sent by: cc:
<[EMAIL PROTECTED] Subject: RE: HLBL REF.
oject.org>
07/10/01 11:17 AM
Please respond to "Foxboro
DCS Mail List"
OK, you've gone and confused me now (don't get the big head; it's not that
hard
to do ;-).
I am kind of new to I/A, and this whole checkpoint/workfile/CP's memory
thing
has me asking a lot of questions, to say the least. I had thought that the
checkpoint at least was a direct copy of the CP's memory, but from what you
say
below this is not the case. (Emotional state on discovering this
deleted...)
So....is there anything else supplied by Foxvensys that can make changes to
the
CP's memory that cannot be duplicated on-disk?
Corey Clingo
Sr. Engineer
BASF Corporation
Ken,
As others have stated, extreme caution should be taken when using setpars.
Anytime setpars is used for bulk changes it should be followed by an upload
and then a checkpoint (if you want the changes to be there in the event of
a reboot), because setpars makes active changes in the CP only, not in the
workfile or checkpoint file.
setpars -- makes active change in CP
upload -- updates settable parameters in CP to station workfile
checkpoint -- builds new checkpoint file based on station workfile
One of the big dangers in using setpars is that it can change non-settable
parameters. These changes can not be updated in the station workfile with
an upload, resulting in a mismatch between checkpoint file, station
workfile, and CP. Wildcards can be used in the filter specifications in
setpars which can lead to unforseen changes due to unexpected matches.
Making a small mistake when updating a setpars script can cause extensive
damage to control logic.
If you are making changes to settable parameters in an operating plant and
need to do them from a UNIX script, consider using omset or omsetimp.
Kevin FitzGerrel
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
