[foxboro] Unreliable API calls.
- From: "Schouten, Frits JF" <Frits.Schouten@xxxxxxxxxxxxxxxxxx>
- To: "Foxboro DCS Mail List (E-mail)" <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 20 May 2005 10:36:48 +1200
Hello Gang,
I have a bit of an issue with API calls and in particular the one offs li=
ke uread and uwrite.
They are extensively used within our 'C' applications to get the odd few =
values to and from control blocks.
A logfile snippet:
-------
15/05/2005:12:52:30 - nextladle : CBP:C1SETUP:NEXT_LADLE.IO0002, ValType:=
6, Error:1=20
15/05/2005:12:52:30 - nextladle : CBP:C1SETUP:NEXT_LADLE.RI0001, ValType:=
3, Error:1=20
15/05/2005:12:52:30 - nextladle : CBP:C1SETUP:NEXT_LADLE.RI0002, ValType:=
3, Error:1
15/05/2005:12:52:35 - nextladle : CBP:C1SETUP:CAST_LADLE.SN0008. Error: 3=
4=20
15/05/2005:12:52:39 - nextladle : CBP:C1SETUP:CAST_LADLE.SN0003. Error: 3=
4=20
-------
Error 1, according to foxdoc B0193UD appendix D, means:
1 noaccs Unable to access object (object-level error).
Object not found; check "name" argument of FoxAPI call for typographical=20
error; check I/A Series database for existence of object and create,
if necessary.
Error 34, according to foxdoc B0193UD appendix D, means:
34 nostg String not found.
Object(s) not found; check "name" argument of sread() for typographical
error; check I/A Series database for existence of object and create it,
if necessary.
But the objects do exist and the program only fails like 2-3 times a day =
while it runs well over 150 times a day.
And if the program then tries to write back to I/A about the issue it get=
s yet another error:
15/05/2005:12:52:43 - nextladle : CBP:C1SETUP:COMMON.II0001, ValType:6, E=
rror:-35=20
15/05/2005:12:52:43 - nextladle : CBP:C1SETUP:COMMON.II0002, ValType:6, E=
rror:-35=20
Error -35, according to foxdoc B0193UD appendix D, means:
ENOTACTIVE (-35) Caller not active with IPC.
My question really is, why are API calls so unreliable.=20
Some years ago all programs got changed from OM calls to API calls and ev=
er since I have this issue with reliablility.
The host is running V7.1 with Fox API Version 4.2.8.
Regards,
Frits Schouten=20
Process Computing Department=20
New Zealand Steel Ltd
EOM=0A=0ANOTICE - This message and any attached files may contain informa=
tion that is confidential and/or subject of legal privilege intended only=
for use by the intended recipient. If you are not the intended recipient=
or the person responsible for delivering the message to the intended rec=
ipient, be advised that you have received this message in error and that =
any dissemination, copying or use of this message or attachment is strict=
ly forbidden, as is the disclosure of the information therein. If you hav=
e received this message in error please notify the sender immediately and=
delete the message.
_______________________________________________________________________
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:
- » [foxboro] Unreliable API calls.
