Here is the problem:
sf2db passes along PP or NPP IF it is defined. If neither PP or NPP
is defined then the .db file will not have it defined.
If the .db file does not have have PP or NPP defined,
NPP is the default.
This default is made by the Static Database Access Library,
which can not be changed without causing problems for non-capfast
users.
If DCT reads in a short form report that does not have PP .or NPP
defined the default is PP.
Thus if CAPFAST Users do not define PP on pv links there will
be a different result using dct to convert the short form report
vs using sf2db.
In hindsite the default for capfast users should also have been
NPP. Since capfast users relied on dct to convert short form reports,
the default become PP.
What to do??
Marty Kraimer
From: Philip Taylor <[email protected]>
Date: Tue, 26 Mar 1996 14:10:57 +0000 (GMT)
Subject: Problem changing to use ASCII database
Message-Id: <Pine.SOL.3.91.960326140356.15828F-100000@hobbit>
I have just changed over from using the old type EPICS
database loading to use ASCII databases, using sf2db
to generate the .db files. I used the same original
Capfast schematics as before.
My system stopped working - even though I was using the same
short-form report to generate the old and new (ASCII) databases.
It eventually turned out that links that had previously
defaulted to be Process Passive have now become Non
Process Passive when loaded from an ASCII database file.
So has some default changed - and how do you ensure that
links are process passive now?
Philip
------------------------------------------------------------
Philip Taylor, Royal Greenwich Observatory,
Madingley Road, CAMBRIDGE. CB3 0EZ. UK
Email : [email protected] Phone : (UK+) (0)1223-374710
------------------------------------------------------------
- Replies:
- Re: Problem changing to use ASCII database watson
- Navigate by Date:
- Prev:
Problem changing to use ASCII database Philip Taylor
- Next:
Re: Problem changing to use ASCII database watson
- Index:
1994
1995
<1996>
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Problem changing to use ASCII database Philip Taylor
- Next:
Re: Problem changing to use ASCII database watson
- Index:
1994
1995
<1996>
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|