Re: [foxboro] Sys Def questions

Thanks, Russ.  I think that sounds about right.  So, is there a problem with
this?  Should I make a special effort to go back into SysDef and change all
the FBM's to NOTYET and re-commit?  Or can I just leave it the way it is?

Tim Lowell
Control Systems Engineer
Phillips Petroleum Company, Trainer Refinery
Phone:  610-364-8362
Fax:    610-364-8211
tlowell@xxxxxxxx


        -----Original Message-----
        From:   Boulay, Russ [SMTP:Russ.Boulay@xxxxxxxxxxxx]
        Sent:   Thursday, May 30, 2002 1:23 PM
        To:     'foxboro@xxxxxxxxxxxxx'
        Subject:        Re: [foxboro] Sys Def questions

        Also..to be in the state your system is in.....after users update
the SysDef
        with the online built ECB's...they usually marked the FBM's DONE in
SysDef
        since the system already knows about them. This can lead to the next
        commital pass thru..resulting in IIF.cur saying DONE for all FBM's
and still
        not have ciofiles...because the ECB's have never been commital
installed in
        the NOTYET state.

        > -----Original Message-----
        > From: foxboro-bounce@xxxxxxxxxxxxx@CORP  On Behalf Of "Lowell,
Tim:"
        > <tlowell@xxxxxxxx>
        > Sent: Thursday, May 30, 2002 1:02 PM
        > To:   'foxboro@xxxxxxxxxxxxx'
        > Subject:      [foxboro] Sys Def questions
        > 
        > 
        > I have some questions about SysDef and the commit install process
I was
        > hoping someone knew the answer to.   We have 2 nodes, and on the
AW of one
        > node, in the directory /usr/fox/sp/ciofiles, there is a list of
files with
        > names corresponding the letterbugs of the CP's and Intelligent
FBM's.  In
        > each file is a list of the FBM's or Intelligent Transmitter child
ECB's
        > attached to that CP or Intelligent FBM that were included in the
SysDef.
        > 
        > However, on the other node's AW, /usr/fox/sp/ciofiles has all the
same
        > type
        > of files, but the files representing the CP's do not have any FBM
listings
        > in them.  They only have one entry, corresponding the CP itself.
The
        > Intelligent FBM files look the same as the first node, though.
It's only
        > the CP files that have missing information.
        > 
        > What process populates the files in /usr/fox/sp/ciofiles with the
FBM
        > letterbugs?  Did we somehow manage to skip a step during our last
upgrade?
        > What happens if the FBM letterbug listings aren't there?  The most
current
        > SysDef and the IIF.cur file on the second node lists all the FBM's
on the
        > second node, and the FBM's are obviously running OK.
        > 
        > As far as I can figure out, this appears to have happened during
our last
        > upgrade in August 2001.  The files in /usr/fox/sp/ciofiles used to
contain
        > similar amounts of data on both nodes prior to that.  Does anybody
have
        > any
        > knowledge of these files they can share?
        > 
        > Thanks,
        > 
        > Tim
        > 
        > 
        >
_______________________________________________________________________
        > 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
        >  


        -- No attachments (even text) are allowed --
        -- Type: application/ms-tnef


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