Just a note of a problem we have encountered with IP/21/CIMIO/FoxAPI that
may or may not apply here. There is a bug in how IP/21 handles get records.
We thought initially if we turned the record processing off when we added
points and turned it back on it would rebuild the sets properly. This is
not the case. It begins rebuilding (close and reopen) the set in API as
soon as a change is made and <CR>. This causes a problem when multiple
points are being changed or added. CIMIO is trying to open and close the
same set multiple times at the same time. What happens is one of the CIMIO
processes dies and dumps a huge core file which really drags down the
system. This really gave us fits for a while because IP/21 just would not
communicate. We had to get an Aspen tech out to resolve this issue. He did
state this is not happening on all installations for some reason. It is
just random. What we are now doing on Aspen's recommendation in the interim
(a fix is supposedly in work) is to stop CIMIO make all changes and restart
it. This works but is annoying.
Chad Airhart
Instrument, Electrical & Control Systems Engineer
Equistar Chemicals, LP.
Victoria, TX
Wk. (361) 572-2568
Pgr. (361) 270-2214 alpha messaging at [EMAIL PROTECTED]
Fx. (361) 572-2541
> -----Original Message-----
> From: John Miller [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, December 11, 2000 1:48 PM
> To: 'Foxboro DCS Mail List'
> Subject: RE: Problem in Foxapi/CIMIO
>
> I don't remember the specifics, but I've done roughly the same thing.
> However, based upon my observations, it seems that it takes about fifteen
> minutes before all of the CIMIO GET tables are functioning properly.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 11, 2000 8:34 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Problem in Foxapi/CIMIO
>
>
>
>
>
> We are using a 5 minute delay in the CIMIO startup script
> (/etc/fox/go_CIMIOFOXIA). The script is kicked off by placing
> it in /etc/fox/user_apps.dat. We collect about 4000 tags per
> AW, and are using QF990084. Our workstations are all 250MHz
> AW51Es (Ultra30).
>
> Foxapi is started with a sleep 40 in /usr/fox/bin/go_FOXAPI. I
> don't believe we altered that script.
>
> Jim Murphy
>
> O-----------------------------------------------------------------O
> | James D. Murphy Phone: 317-276-6859 |
> | Sr. Process Control Engineer FAX: 317-277-9270 |
> | Eli Lilly and Company Pager: 317-256-5500 |
> | Lilly Corporate Center Email: [EMAIL PROTECTED] |
> | Mail Drop Code: 3418 |
> | Indianapolis, Indiana 46285 |
> O-----------------------------------------------------------------O
> |------------------------+------------------------+-----------------------
> -|
> | | John Miller |
> |
> | | <JMILLER@huntrefining| To:
> |
> | | .com> | 'Foxboro DCS Mail
> |
> | | Sent by: | List'
> |
> | | [EMAIL PROTECTED]|
> <[EMAIL PROTECTED]|
> | | andraProject.org | sandraProject.org>
> |
> | | | cc:
> |
> | | 12/11/00 09:02 AM | Subject:
> |
> | | Please respond to | RE: Problem in
> |
> | | Foxboro DCS Mail List| Foxapi/CIMIO
> |
> | | |
> |
> |------------------------+------------------------+-----------------------
> -|
>
>
>
>
>
>
>
>
> We've been told by some very knowledgeable folks at Foxboro that it takes
> roughly fifteen minutes after re-booting before an AW is really itself.
> I've just learned not to expect much from CIMIO or Foxapi during that
> time.
> It's annoying, but unfortunately I've gotten used to it.
>
>
> -----Original Message-----
> From: Harshad Viradia [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 11, 2000 7:53 AM
> To: Foxboro DCS Mail List
> Subject: Re: Problem in Foxapi
>
>
>
>
> We have provided CIMIO start-up delay time 15 minutes.
>
> This is not CIMIO problem. Its certainly Foxapi as while using "Foxtst"
> utility
> to open the set Foxapi is getting killed and dumping core.
>
> We have installed even QF990341 before commit and still it did not work.
>
> Regards
> Harshad
>
>
> -----------------------------------------------------------------------
> 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]
>
> -----------------------------------------------------------------------
> 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]
