Re: [foxboro] ICC to CP disconnect

Thanks to everyone who responded.  I am always amazed by the level of
expertise of this group and the willingness to share/help where
possible.  I have spent the day today going through the ideas and
looking in the places to where I was pointed.  In summary:

1) The problem (which consisted of two missing subdirectories and a CP
in an undefined state following the use of the delete/undelete command)
occurred on the development system and not on our production system.
2) We perform an automatic save_all every day and maintain the most
current five copies - no we are not saving uploads and shrinks.
3) I have (again) looked back on our printer and cannot identify that
the CP (which is a CP60) was initialized (apparently there are messages
for load_all but not for initialize).  Nor were there any alarms on the
system monitor.
4) I know of no instances where a compound was named with the same value
as the CP letterbug.  If they existed previously, they are gone now.
5) When I looked in /opt/fox/ciocfg/CPLBUG, I found CPLBUG.wf and
CPLBUG.O files.  No COMP.O files.
6) After generating a CSA save of the CP in question, no compounds or
blocks of any type were listed.
7) Because of the oddity of this situation, I used FoxSelect to view a
sequence block running on the "apparently" initialized CP.  I found that
step and subroutine numbers were changing, indicating that the block was
indeed running, but when I attempted to view the code, that overlay was
"smurf'd."

Given all of the unusual conditions, I opted to reinitialize the CP and
then use the save_all from Sunday evening to reload the CP.  This
reinstalled one of the missing subdirectories.  w.r.t. the second
missing subdirectory, I have current backup copies of all sequence logic
(including #include files) so I was able to reinstate that with little
difficulty or pain.

Where does that leave me?  Very reluctant to use the D/U function.  I
guess that as long as I perform a save_all prior to ever using D/U, I
could protect myself from too much pain.

Thanks again,

Matt Gunter
ATK Launch Systems
 
 
_______________________________________________________________________
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: