Experimental Physics and
Industrial Control System

[email protected] (Marty Kraimer) · Thu, 16 Feb 1995 08:47:19 -0600

I just tried this on my system and it works fine.
My guess is that you are still getting the old version of dct when you think
you have the 3.12 version. I just noticed that the dct version number was never
updated so looking at the dct version does not help.
Please type "which dct" and see if you are using the 3.12 version.

Here is what is supposed to happen:

All new dct tools (sf2db, atdb, etc) use the static database access library.
It, in turn, always write CT_HEX fields with a leading 0x. When it converts
from ascii to int it uses strtol (ASCII standard library routine) to perform
conversion. This allows a leading 0x for hex and leading 0 for octal.
Previously DCT wrote CT_HEX field in hex without a leading 0x. It was modified
so that it accepts fields CT_HEX fields with or without a leading 0x.
This if you do the following:
1) use new DCT to restore from short form report
2) generate new short form report
3) use sf2db on new short form report

then it should work just fine. The .db file should have a 0x in frount
of all CT_HEX field values.

Since this is what you said you did, my olny guess is that you are still
getting the old version of DCT.

Marty Kraimer

> From [email protected] Wed Feb 15 16:39 CST 1995
> Date: Wed, 15 Feb 1995 14:38:50 -0800
> From: Ric Claus <[email protected]>
> Subject: EPICS 3.12 questions
> To: [email protected]
> Reply-To: [email protected]
> X-Envelope-To: [email protected]
> Content-Transfer-Encoding: 7BIT
> Content-Type> : > text> 
> Content-Length: 1739
> 
> I'm trying to upgrade my EPICS 3.11.1 applications to run under 3.12.0.  In
> building the database, I made a short report under 3.11 dct and created a new
> database using v1.15 dct under 3.12.  Then I modified from text file with the
> short report I made.  Then I sf2db to generate a .db file which is loaded by
> dbLoadRecords after default.dctsdr is loaded by dbLoad.  The dbLoadRecords
> results in:
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> Cannot set field TEVL to a
> Cannot set field ELVL to b
> Cannot set field TVVL to c
> Cannot set field TTVL to d
> Cannot set field FTVL to e
> Cannot set field FFVL to f
> It turns out that these are my mbbi records and it appears that hex values are
> no longer allowed for these fields, even though dct now shows a 0x in front of
> each value and allows you to enter these values.  However, dct won't let me put 
> in leading zeros to try and solve this problem.  If somebody's got a fix, could
> we please have it?
> 
> Secondly, perhaps I've missed it somewhere (in which case please point me in
> the right direction), but I haven't seen a translation tool to convert OPIs,
> either .dl or .adl files from 1.16 edd/dm to 2.0 edd/dm.  What do I need to do
> to bring up my old displays?  I really hope I don't have to redraw them.
> 
> Any help is greatly appreciated!
> 
> 	Thanks,
> 		Ric
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System