I don't have the code that you want, but if you play with apitst (or foxtst
whichever you have), you can query the alarms by hand.
Once you know the sequence of commands, you can create a script that does
the following:
/opt/fox/ais/bin/foxtst <<INPUT
<commands go here>
INPUT
This will send the messages to 'stdout'.
Perhaps it will get you by for now.
Regards,
Alex Johnson
The Foxboro Company
10707 Haddington
Houston, TX 77043
713.722.2859 (v)
713.722.2700 (sb)
713.932.0222 (f)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Lowell, Tim: [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, May 10, 2000 9:27 AM
To: 'Foxboro DCS Mail List'
Subject: C programming with AIM*API
I've got TAC on this case, but they might not be the best place to
go for
this, so I thought I'd throw it on the list server to see if any of
you
Foxboro wizards can help me out:
We have AIM*Historian, and it does not provide any tools to extract
alarm
messages into a text format. Unlike the legacy historian,
AIM*Historian
doesn't generate a flat circular file like "almhist", it actually
stores its
data in tables that are located in files that you can store for
years. I
know what tables they are stored in, and I even know the syntax of
the C
call to access the tables. Unfortunately, I cannot figure out all
the
little important things you need to do to write a C application for
this
purpose, such as what header files to include, how to declare the
variables,
what kind of output the C call actually generates, and how to
compile and
link the finished source code.
The AIM*API documentation provides the syntax for the C call, which
is
called fh_FdbMsgQuery, but it doesn't have a sample program using
this call,
which is really what I need. Someone at Foxboro developed a C
program
called fh_sacego that queries the same tables and extracts System
Monitor
messages and Operator Action Journal messages, presumably using the
same
calls. If someone at Foxboro could send me the source code for this
application, or a stripped down version that at least illustrates
what is
required to properly declare the variables, handle the output, and
compile
and link the C code, it would be much appreciated. Anybody up to
the task?
Has anybody else written any code with AIM*API?
Thanks,
Tim
-----------------------------------------------------------------------
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]
