Re: [foxboro] OAJ in Aim

We noticed something similar here while trying to get OAJ records via 
ODBC.  The date field is missing the first two characters of the (4-digit) 
year.  Other fields may have issues as well, but this one was the most 
obvious and seemed an obvious reason for our problem: it gives our PAS 
alarm management software fits.

I thought it might be the PAS application (wouldn't be the first problem 
we had there), but I ran the same query with an ODBC test utility and got 
the same results.  The system on which we observed this behavior is not 
one of the ones I'm responsible for, and therefore I didn't feel I was in 
a position to troubleshoot it, so I neither filed a CAR nor researched 
existing ones.


Corey Clingo
BASF Corporation






"Ron Schafer" <rschafer@xxxxxxxxxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
06/20/2008 12:28 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
[foxboro] OAJ in Aim






Content-Type: text/plain;
                 charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
I'm running Aim 3.2.3.53 and all the operator action acknowledge (Unack
to ack) records are missing data. They are missing the first 2
characters for each field starting with the act_type and below. Has
anyone seen this in their system or know of a fix or CAR?

=20

Ronald G. Schafer

Distributed Controls System Administrator

White Birch Paper Company

Bear Island L.L.C. Division

Ashland VA, 23005

Phone 804-227-4034

Fax 804-227-4052

Email: rschafer@xxxxxxxxxxxxxxxxxxxxxx




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