Re: [foxboro] Inconsistency between host and CP
- From: "Gunter, Matt" <Matt.Gunter@xxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 16 Dec 2013 14:17:45 +0000
Thanks Kevin!
I can see that I will be checking periodically now as well.
Regards,
Matt
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Kevin Fitzgerrell
Sent: Friday, December 13, 2013 5:37 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Inconsistency between host and CP
Hi Gunter,
Your issue appears to be very close to the one we used to have when using ICC
remotely, usually via Exceed or just a remote X session, and would hang or lose
the session prior to exiting ICC. The changes would be written to the CP
immediately, but the workfiles not updated, resulting in a mismatch.
The guys I worked with got pretty good at letting me know when this happened so
we could go back and synchronize the block or blocks, and I also checked
monthly for block and parameter level mismatches.
Cheers,
Kevin
On Sat, Dec 14, 2013 at 7:53 AM, Landry, Scott <Scott.Landry@xxxxxxxxxxxx>wrote:
>
>
> Yep, gotta hit the RETURN key. Some people are not aware that
> RETURN = ENTER.
>
>
> Regards,
>
>
> Scott
>
> ________________________________________
> From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Joe Riccardi [joe@xxxxxxxxxxxxx]
> Sent: Friday, December 13, 2013 1:48 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Inconsistency between host and CP
>
> The Enter issue happens all of the time with the younger Windows
> guys/gals working on the older UNIX systems. I see it all of the time,
> they forget to hit enter and wonder why the system is not seeing the change...
>
> I just smirk... :-,)
>
> Sent from my iPhone
>
> On Dec 13, 2013, at 12:08 PM, "Gunter, Matt" <Matt.Gunter@xxxxxxx> wrote:
>
> > That is absolutely correct and we are in that boat. If a value is
> > typed
> in and then done is selected or another parameter is selected using
> the mouse - without hitting ENTER first, that value is NOT assigned.
> In this instance, the value in the workfile was correct, but the value
> in the CP was incorrect.
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
> > [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Boulay, Russ
> > Sent: Friday, December 13, 2013 10:03 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: Re: [foxboro] Inconsistency between host and CP
> >
> > I think there may be a simpler answer.
> > Some versions of ICC, when a value is changed in parameter entry
> > field,
> if enter is not hit, the value would actually stay there as if entered.
> > Although this more commonly happens when a historian name or WP
> > logical
> name is selected from the right hand menu.....i have heard reports of
> my previous sentence occurring.
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
> > [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Gunter, Matt
> > Sent: Friday, December 13, 2013 8:56 AM
> > To: 'foxboro@xxxxxxxxxxxxx'
> > Subject: Re: [foxboro] Inconsistency between host and CP
> >
> > Thanks for the replies! I haven't been able to run db_sync, but am
> still working at it.
> >
> > If I enter \opt\fox\bin\tools\db_sync>ksh, I get "Permission denied".
> >
> > If I enter \opt\fox\bin\tools\db_sync>ksh ck_multi_cps -h >
> > filename,
> I get "Ambiguous output redirect".
> >
> > However, based upon Scott's response, I'm not sure how useful
> > db_sync
> will be.
> >
> > When the mismatch occurred, we were working in the ICC from the host AW.
> As I understand it, at the conclusion of checkout the ICC was opened
> and changes were made to the IOMOPT parameters to set the blocks back
> to operational mode. A checkpoint was performed and the ICC was minimized.
> While in this state, the WSOD occurred.
> >
> > Let me explain further about the WSOD... I thought it was a
> > commonly
> understood acronym, but I was wrong. It appears to be a memory issue
> within FoxView. Sometimes when trying to open a new window, or bring
> up a minimized window, the X-windows application crashes, the screen
> is wiped clean (white) and the box reverts to a terminal. We can't
> restart X-windows and therefore can't restart FoxView. So far the
> only fix we've been able to identify is a reboot (shades of older MS
> Windows). The host appears to still be running, in that the remote
> collector continues to operate, but we haven't tried remotely logging
> into the host and, say, upload a CP's database. Naturally, this only
> occurs on our production host (of course!).
> >
> > I will search through the list server history using "mismatch" as
> recommended and see what I can come up with.
> >
> > I greatly appreciate everyone's willingness to share and pitch in to
> help solve problems. I read through the posts from this group on an
> ongoing basis and the information, sprinkled as it is with humor, is a
> real education and help!
> >
> > Best regards to all!
> >
> > Matt
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
> > [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Landry, Scott
> > Sent: Thursday, December 12, 2013 7:26 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: Re: [foxboro] Inconsistency between host and CP
> >
> >
> >
> >
> > db_sync is useful for finding missing blocks or compounds but
> > not
> for parameter differences
> > in the blocks and compounds between what is in the CP and what
> > is in
> the wf.
> >
> > Like Alex said, an Upload will sync up the settable parameters
> > on
> the blocks and compounds.
> >
> > Uploading blocks and compounds that are in the CP but not in the
> > wf
> will error.
> >
> > Deleting and undeleting a block in the wf that is not in the CP
> > will
> put it in the CP.
> >
> >
> >
> > Regards,
> >
> >
> > Scott
> >
> > ________________________________________
> > From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Dirk Pauwels [dirk.pauwels@xxxxxxxxxx]
> > Sent: Thursday, December 12, 2013 6:36 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: Re: [foxboro] Inconsistency between host and CP
> >
> > Hi Matt,
> >
> > Would db_sync be a solution to check for out of sync dbse?
> > Command:
> >
> > \opt\fox\bin\tools\db_sync>ksh
> > Ck_multi_cps -h > chckdbse_test
> >
> > This is the result of chckdbse_test when I run it at our site:
> >
> > ck_multi_cps - Version 1.4
> > File ./progress_file is updated with results as ck_multi_cps
> > progresses
> ...
> >
> > Checking CP6004
> > check_db_sync - Version 1.7
> > Generating Checkpoint list (/opt/DB_SYNC/CP6004/checkpoint.l) ...
> > There are 1340 names in the database.
> > Generating CSA list (/opt/DB_SYNC/CP6004/csa_db.l) ...
> > Generating Work-Files list (/opt/DB_SYNC/CP6004/work_files.l) ...
> >
> > CP6004 Database names are in proper sync.
> >
> > Checking CP6003
> > check_db_sync - Version 1.7
> > Generating Checkpoint list (/opt/DB_SYNC/CP6003/checkpoint.l) ...
> > There are 1005 names in the database.
> > Generating CSA list (/opt/DB_SYNC/CP6003/csa_db.l) ...
> > Generating Work-Files list (/opt/DB_SYNC/CP6003/work_files.l) ...
> >
> > CP6003 Database names are in proper sync.
> >
> > Checking CP6002
> > check_db_sync - Version 1.7
> > Generating Checkpoint list (/opt/DB_SYNC/CP6002/checkpoint.l) ...
> > There are 975 names in the database.
> > Generating CSA list (/opt/DB_SYNC/CP6002/csa_db.l) ...
> > Generating Work-Files list (/opt/DB_SYNC/CP6002/work_files.l) ...
> >
> > CP6002 Database names are in proper sync.
> >
> > Checking CP6001
> > check_db_sync - Version 1.7
> > Generating Checkpoint list (/opt/DB_SYNC/CP6001/checkpoint.l) ...
> > There are 1403 names in the database.
> > Generating CSA list (/opt/DB_SYNC/CP6001/csa_db.l) ...
> > Generating Work-Files list (/opt/DB_SYNC/CP6001/work_files.l) ...
> >
> > CP6001 Database names are in proper sync.
> >
> > Rgds,
> > Dirk
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
> > [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Gunter, Matt
> > Sent: woensdag 11 december 2013 20:21
> > To: 'foxboro@xxxxxxxxxxxxx'
> > Subject: [foxboro] Inconsistency between host and CP
> >
> > To all,
> > I have to suspect that this topic has previously been discussed ad
> infinitum. So if someone can recommend a topic to search for in the
> archives, I will be happy to do so. I did search for "inconsistency"
> but didn't turn up any useful hits.
> >
> > We recently had an instance where a pair of blocks had their IOMPOPT
> option set to 1 in the ICC but 0 in the CP. It was easily rectified
> when the ICC was opened and a value of 1 re-entered and DONE selected.
> However, we are being asked what could cause such an inconsistency and
> I don't have a reasonable answer to provide. Normally, as soon as
> DONE is selected any modified parameter value is immediately written
> to the field. I therefore can't see how these values could be different.
> >
> > We did have a WSOD occur while involved in manipulating these blocks
> > for
> checkout, some time back, but since the ICC registered had a 1 I have
> to assume the value was accepted and as such should have then been
> written to the CP.
> >
> > Our system:
> > Foxview 9.0.4
> > I/A 7.1.5
> > Work stations and hosts are Solaris red and silver boxes.
> > Configurator is ICC
> >
> > Any help in understanding this will be greatly appreciated.
> >
> > Thanks in advance,
> >
> > Matt Gunter
> > ATK Launch Systems
> >
> >
> >
> >
> > ________________________________
> > Lawter Notice: The information (including any attachments) contained
> > in
> this communication is confidential, private and proprietary, may be
> privileged or otherwise protected by applicable law or legal rule, and
> is intended only for the use of the addressee(s). Unauthorized use,
> disclosure, distribution or copying is strictly prohibited and may be
> unlawful. If you have received this communication in error, please
> notify the sender immediately by reply e-mail, or by calling the
> sender, and then delete it completely 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
> > *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to
> which it is addressed. This e-mail is confidential and may well also
> be legally privileged. If you have received it in error, you are on
> notice of its status. Please notify the sender immediately by reply
> e-mail and then delete this message from your system. Please do not
> copy it or use it for any purposes, or disclose its contents to any
> other person. This email comes from a division of the Invensys Group,
> owned by Invensys plc, which is a company registered in England and
> Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London,
> SW1X 7AW (Registered number 166023).
> For a list of European legal entities within the Invensys Group,
> please select the Legal Entities link at invensys.com.
> >
> >
> > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be
> subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its
> subsidiaries and affiliates).
> >
> >
> >
> >
> > ____________________________________________________________________
> > ___ 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
> >
> >
> >
> > ____________________________________________________________________
> > ___ 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
> >
> >
> >
> > *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to
> which it is addressed. This e-mail is confidential and may well also
> be legally privileged. If you have received it in error, you are on
> notice of its status. Please notify the sender immediately by reply
> e-mail and then delete this message from your system. Please do not
> copy it or use it for any purposes, or disclose its contents to any
> other person. This email comes from a division of the Invensys Group,
> owned by Invensys plc, which is a company registered in England and
> Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London,
> SW1X 7AW (Registered number 166023).
> For a list of European legal entities within the Invensys Group,
> please select the Legal Entities link at invensys.com.
> >
> >
> > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be
> subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its
> subsidiaries and affiliates).
> >
> >
> >
> >
> > ____________________________________________________________________
> > ___ 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
> >
> >
> >
> > ____________________________________________________________________
> > ___ 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
> >
>
>
> ______________________________________________________________________
> _ 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
> *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to
> which it is addressed. This e-mail is confidential and may well also
> be legally privileged. If you have received it in error, you are on
> notice of its status. Please notify the sender immediately by reply
> e-mail and then delete this message from your system. Please do not
> copy it or use it for any purposes, or disclose its contents to any
> other person. This email comes from a division of the Invensys Group,
> owned by Invensys plc, which is a company registered in England and
> Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London,
> SW1X 7AW (Registered number 166023).
> For a list of European legal entities within the Invensys Group,
> please select the Legal Entities link at invensys.com.
>
>
> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be
> subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its
> subsidiaries and affiliates).
>
>
>
>
> ______________________________________________________________________
> _ 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
>
>
_______________________________________________________________________
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
_______________________________________________________________________
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
Other related posts:
