Re: [foxboro] UPDATE: **IMPORTANT INFO FOR FOXAPI USERS: The Newer Y2k bug hits FoxAPI/Foxais
- From: "Mark Dumond" <mdumond@xxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 14 Jan 2004 17:20:14 -0500
Shared variables are sometimes known as Globals.
They are variables that reside in an AW, WP, or WP.
A shared variable can be identified by its name: it doesn't have the =
colon
or period in its name like a variable from a CP would.
Many shared variables are system variables, and you can create your own
Shared Variables with "omcrt" command in VT100.
Many third-party interfaces use Foxboro shared variables as the data
repository, instead of using up block space in a CP.
Application Objects are like shared variables in that they reside in an =
AW,
WP, or AP; but App Objects include a colon and period in the variable =
name,
to imitate variables from a CP. I do believe that App Objects are not =
part
of the standard IA system.
I am unsure if this problem also affects App Objects. If your system is
currently working (since Jan 10), then you are probably are OK.
Mark Dumond
Sr App Engineer
FeedForward, Inc
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Airhart, Chad M.
Sent: Wednesday, January 14, 2004 4:39 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] UPDATE: **IMPORTANT INFO FOR FOXAPI USERS: The =
Newer
Y2k bug hits FoxAPI/Foxais
What exactly do you mean by Shared Variables? How about Application =3D
Objects?
Chad M. Airhart
Senior Instrument, Electrical and Control Systems Engineer Equistar
Chemicals, LP Wk. (361)572-2568 Fx. (361)572-2541 Pgr. (361)270-2214 or
alpha paging at www.arch.com
-----Original Message-----
From: Mark Dumond [mailto:mdumond@xxxxxxxxxxxxxx]=3D20
Sent: Wednesday, January 14, 2004 3:23 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] UPDATE: **IMPORTANT INFO FOR FOXAPI USERS: The Newer =
=3D
Y2k bug hits FoxAPI/Foxais
This issue also affects users of AIM-API.
Foxboro TAC and Foxboro Development have identified this problem, and
Development is currently working on a fix. Although they have identified
this issue as a high-priority, they have =3D =3D3D not yet given a =
release date
for the fix.
CAR numbers are: 1005346 for FoxAPI
1005347 for AimAPI
Again this only affects you if you are using FoxApi/AimApi to open lists
that have writes to Shared Variables. Write lists to CP data
(Compound:Block.Parm) doesn't have this problem.
Mark Dumond
Sr App Engineer
FeedForward, Inc.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
=3D
=3D3D On Behalf Of Mark Dumond
Sent: Wednesday, January 14, 2004 11:48 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] **IMPORTANT INFO FOR FOAPI USERS: The Newer Y2k bug =
=3D =3D3D
hits FoxAPI/Foxais
*** IMPORTANT NOTE FOR FOXAPI USERS *********
FOXAPI WRITES TO SHARED VARIABLES STOP WORKING AFTER JANUARY 10
Well, there appears to be a bug that I have been scrambling to fix for =
=3D =3D3D
=3D3D3D days now. I have found this bug in two separate applications =
that are
=3D =3D3D using =3D3D3D Foxapi.
It appears that after January 10, FoxApi can not open Shared Variables =
=3D =3D3D
=3D3D3D in lists for writing. Variables that are in a CP are OK, as are =
shared
variables for reading.=3D3D3D20 Foxapi versions 4.2.4, 4.2.5, 4.2.7 all =
=3D have
=3D3D the same problem. Version 4.2.0 is immune.
I have not yet passed this information on to Foxboro yet.
Interestingly, this date coincides with the newer Y2K bug that has been =
=3D
=3D3D =3D3D3D in the tech news lately.
See: http://zdnet.com.com/2100-1105-5129875.html
Quote from the story:
This is a story of a software company that mistakenly chose about 1 =3D =
=3D3D3D
billion seconds--2 to the 30th power, to be precise--since Jan. 1, 1970,
which =3D3D3D is when the Unix operating system was developed and is =
Year =3D
=3D3D Zero for many =3D3D3D Unix applications.=3D3D3D20
Unix itself uses a similar method to resolve dates, but developers chose =
=3D
=3D3D =3D3D3D the maximum infinity value of 2 to the 31st power--about 2 =
billion
=3D3D seconds. =3D3D3D That means that the software will "time out" Jan. =
10,
while most =3D =3D3D Unix =3D3D3D programs will continue to operate =
until
2038.=3D3D3D20
Did Foxboro make this same mistake???
We need a fix!!!!
Helpless,
Mark Dumond
Sr. App Engineer
FeedForward, Inc
=3D3D20
=3D3D20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at =
=3D
=3D3D your own risks. Read =
http://www.thecassandraproject.org/disclaimer.html
=3D3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin
to unsubscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave
=3D3D20
=3D20
=3D20 =
_______________________________________________________________________
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
=3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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:
