diff --git a/RELEASE_NOTES.html b/RELEASE_NOTES.html index 8c3b5bfa6..136bee5fb 100644 --- a/RELEASE_NOTES.html +++ b/RELEASE_NOTES.html @@ -1,202 +1,395 @@ - - EPICS Release baseR3.13.0.beta11 + <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> + <META NAME="GENERATOR" CONTENT="Mozilla/4.03 [en] (X11; U; SunOS 5.5.1 sun4u) [Netscape]"> + <TITLE>EPICS Release baseR3.13.0.beta12 - -

EPICS Release baseR3.13.0.beta11

- -

July 17, 1997

- -

All major functionality that will be in R3.13 is now in place. It has -been build on solaris, sunos, HPUX, alpha, SG, and winXX. -There are still some c++ related problems. In particular c++ code -does not build properly on SGI. Thus we are not yet ready for the -first official 3.13 release. Since none of the c++ code is necessary -for IOC applications this should not stop anyone from upgrading to 3.13.

+

+EPICS Release baseR3.13.0.beta12

+

+Feb 19, 1998

+All major functionality that will be in R3.13 is now in place. It has been +build on solaris, sunos, HPUX, alpha, SG, and winXX. There are still some +c++ related problems. In particular c++ code does not build properly on +SGI. Thus we are not yet ready for the first official 3.13 release. Since +none of the c++ code is necessary for IOC applications this should not +stop anyone from upgrading to 3.13.

The Application Developer's Guide is a major revision of the 3.12 edition. All Application Developer's should get a hard copy (from the postscript version) and read it. It describes the features in the latest release. -The latest version is for beta11 base release.

+The latest version is for beta11 base release.

LANL has a revision of the Record Reference Manual available. See the -LANL EPICS documentation.

+LANL EPICS documentation. -

The document "EPICS -IOC Applications: Building and Source/Release Control" provides -guidlines for developing applications with 3.13.

+

The document "EPICS +IOC Applications: Building and Source/Release Control" provides guidlines +for developing applications with 3.13. +

+Changes between beta11 and beta12

-

Changes between beta4 and beta11

+

+IOC Applications: Building

+The config.CONFIG_APP file must be edited. Remove the following lines: +
ifndef T_A
+T_A = $(HOST_ARCH)
+endif #ifndef T_A
-

Support for win95 and winNT

+

+aoRecord

+This did not work properly if DOL  is a channel access link that fails. +

+Access Security

+Previously it was possible to crash an IOC if access security was restarted +after iocInit. This is now fixed. Two major changes were made. +
    +
  1. +asCaTask is no ]longer deleted and restarted. Instead it just clears all +channels and than adds the new channels
    2. -

    Epics base now builds on windows platforms

    +
  2. +The locking mechanism was changed and made more roibust and easier to understand.
    3. -

    GDD and Portable Channel Access Server

    +
  3. +Fixed bug that caused asRegisterClientCallback to fail on UNIX.
    4. -

    The gdd library and the portable channel access server now build on -all platforms, except SGI and cygwin32, listed above. -This also means that C++ is supported on these platforms.

    +
  4. +asLib_lex.l changed to allow more characters(like dbLoadxxx)
    5. +
+Access Security now supports macro substitutions. A new vxWorks shell command +is: +
  + +The Application developer's Guide was updated. +

+tsdefs.h and tsSubr.c

+tsTextToStamp and tsTimeTextToStamp no longer modify the pointer or the +string referenced by pText. -

Application Developer's Guide

+

The nextField routines used by tsSubr were moved inside tsSubr.c  +and made static routines. +

+drvTS

+Checked for Y2K complience. It turns out it was even ok when NTP time overflows +in 2036. However it was modified so that no overflows should occur while +converting between NTP, UNIX, and EPICS epochs. In addition the conversion +of fractions of a second to nanaoseconds was changed and formatting was +changed so that interesting code does not run off right side of page. Hopefully +EPICS base is now fine for Y2K. In fact it should be fine (as far as time +is converned) until the Unix epoch overflows a 32 unsigned integer in the +year 2106. +
  +

+nextFieldSubr.c

+Removed from base. +

+vxWorks

+Base now builds with either vxWorks 5.2 or vxWorks 5.3. The default is +to build vxWorks 5.3. In CONFIG_COMMON a new definition "VX_IS_TORNADO += 1" is present. If this statemant is commented out then vxWorks 5.2 is +assumed. +

+makeBaseApp

+Only the perl version is now supported. Due to encouragement from Rozelle +Wright (LANL) and the developers at BESSY, makeBaseApp now uses template +files instead of being one huge ugly perl script. It is now executed as +
<base>/bin/<arch>/makeBaseApp.pl -e
+or
+<base>/bin/<arch>/makeBaseApp.pl -i ioc ... 
+or
+<base>/bin/<arch>/makeBaseApp.pl app ...
-

The chapter "Building IOC Applications" is gone. It is replaced -by the document "EPICS IOC Applications, Building and Source/Release -Control". Other changes are minor. Following is a brief list:

+
  • +See the new WWW documentation on Application Source Release for details
    • + +

    +dbStaticLib

    +The include path now supports the unix convention that an empty directory +name means the current directory. Thus the following are OK +
    -I nnn::mmm    # Current directory is between nnn and mmm
+-I :nnn        # Current directiry is first
+-I nnn:        # Current directiry is last
    +The lex grammer was changed so that it for quoted strings can contain any +ascii character except a quote. A quote itself can be given as the escape +sequence \". This same change was made to dbLoadRecords and dbLoadTemplates. + +

    For all fields in a .db file, a non null string is considered as not +the default. + +

    For winNT the path seperator is a ; + +

    Field attributes (psuedo fields) are now supported. In particular RTYP +(record type) and VERS (verssion) mare now supported. In addition a new +request type DBR_CLASS is supported. See Application Developer's guide +for details. +

    +base.dbd

    -

    NOTE: The initHooks described in the appDevGuide is not in beta11. +

    +initHooks

    +Changed to support initHookRegister. See Application Developer's Guide +for details. The 3.13.0beta11 version explains the new method. Note that +to use the new the startup file must contain the statement: + +If you have your own version of initHooks.c it should be changed to support +the new features. At a minumum the statement +
      + +must be changed to +
      +
        void initHooks( initHookState state)
    + +

    +menuAlarmStat.dbd

    +The no alarm string changed from "" to "NO_ALARM" +

    +Linear Conversion for ai and ao records:

    +Before beginning it should be stated that the previous linear conversion +method is still valid. + +

    The following, which is designed by Benjamin Franksen at BESSY, is now +the recommended method: + +

    A new field EOFF exists.  The new linear conversion algorithm is +now +

    +AVAL is the raw value adjusted by ASLO and AOFF. + +

    Thus device support should now compute ESLO and EOFF instead of ESLO +and ROFF. + +

    For example let an ADC be a 16 bits adc with raw values between -32767 +and 32767. +

    +NOTES: + + +

    +64 bit architectures

    +Some changes were made to build on 64 bit architectures. A new include +and source file (adjustment.h and adjustment.c) were created to aid this +support. We can thank Peregrine McGehee for this new support. +

    +errlog

    +This is a replacement for the old code that implemented errMessage, errPrintf, +and epicsPrintf. It provides for multiple system wide error loggers. The +existing iocLog has been modified to use the new code. The new code supports +the old calls and adds some new calls. See Application Developer's guide  +for details. +
      +

    +devABSLCDCM

    +Changed Scl to Slc wherever this occured. Added support for signed 16 bit +analog values. Stephanie Allison (SLAC) made these changes. +
      +

    +devMpc

    +Removed from base. +

    +devVXStats

    +Major rewrite of this routine. It computes the cpu usage via a low priority +taks rather than using spy. It reports file descriptor usage rather than +tcp connections (this is what is actually measures). The format of the +INP ,and OUT fields has changed since the previous version.  The new +device definitions are: + +The INP fields now have the form + +The OUT fields now have the form + +The source file has comments showing a sample database. +

    +devSymb

    +This has been drastically changed. ??????? what to say +

    +Changes between beta4 and beta11

    + +

    +Support for win95 and winNT

    +Epics base now builds on windows platforms +

    +GDD and Portable Channel Access Server

    +The gdd library and the portable channel access server now build on all +platforms, except SGI and cygwin32, listed above. This also means that +C++ is supported on these platforms. +

    +Application Developer's Guide

    +The chapter "Building IOC Applications" is gone. It is replaced by the +document "EPICS IOC Applications, Building and Source/Release Control". +Other changes are minor. Following is a brief list: + +NOTE: The initHooks described in the appDevGuide is not in beta11. In beta11 initHooks is the same as previous releases. The new version will -be in the next release.

    - -

    Compiler warning messages:

    - -

    All of base except drv/old is now being built with

    +be in the next release. +

      +

    +Compiler warning messages:

    +All of base except drv/old is now being built with - -

    Most warning messages have now been eliminated. The remaining messages -should not be removed without looking hard at code.

    - -

    recSubArray

    - -

    get_control_double routine returned incorrect values for fields INDX -and NELM.

    - -

    devAiStats

    - -

    This is now renamed devVXStats. The new device definitions are:

    -
    -device(ai,VME_IO,devAiVXStats,"VX stats")
-device(ao,VME_IO,devAoVXStats,"VX stats")
-
    -

    Thus if an application has an old base.dbd and baseLIBOBJS -including definitions for this device support they must be modified.

    - -

    SysMon device support

    - -

    This is removed from base. It is for APS designed and build -VME create system monitoring. The support code is available -from APS if needed. NOTE: In some beta releases baseLIBOBJS, -had an include for devSysmon.o. Applications using -an old version of baseLIBOBJS will not build until this statement is -deleted.

    - -

    dbToRecordtypeH

    - -

    The enums for menus had a comma after last item.

    - -

    pulseTrainRecord

    - -

    recGblInitConstantLink for sgl was referencing wrong field.

    - -

    gphLib

    - -

    This did not properly support multiple clients in multi-thread environment. -

    - -

    dbPvdLib

    - -

    Modified to be faster.

    - -

    devMz8311

    - -

    Use maxCards from module_types.h instead of a #define

    - -

    calcRecord

    - -

    Allow CALC to be 40 characters. Increase rpbuf from 184 to 200

    - -

    mbbiDirectRecord

    - -

    Add call to refresh_bits.

    - -

    mbbxDirectRecord

    - -

    Bx becomes no prompt for mbbi and prompt for mbbo. It was the reverse -before.

    - -

    calcoutRecord

    - -

    A new record type that replaces old wait record. It is like a calc record -with an output and a delay. It makes the wait record obsolete.

    - -

    dbAccess

    - -

    dbGetPdbAddrFromLink is a new routine. It returns NULL for all except -LINK_DB links, for which it returns the address of the associated DB_ADDR -structure.

    - -

    escape characters in database files

    - -

    dbLoadDatabase, dbLoadRecords, and dbLoadTemplate all allow the standard +Most warning messages have now been eliminated. The remaining messages +should not be removed without looking hard at code. +

    +recSubArray

    +get_control_double routine returned incorrect values for fields INDX and +NELM. +

    +devAiStats

    +This is now renamed devVXStats. The new device definitions are: +
    device(ai,VME_IO,devAiVXStats,"VX stats")
+device(ao,VME_IO,devAoVXStats,"VX stats")
    +Thus if an application has an old base.dbd and baseLIBOBJS including definitions +for this device support they must be modified. +

    +SysMon device support

    +This is removed from base. It is for APS designed and build VME create +system monitoring. The support code is available from APS if needed. NOTE: +In some beta releases baseLIBOBJS, had an include for devSysmon.o. Applications +using an old version of baseLIBOBJS will not build until this statement +is deleted. +

    +dbToRecordtypeH

    +The enums for menus had a comma after last item. +

    +pulseTrainRecord

    +recGblInitConstantLink for sgl was referencing wrong field. +

    +gphLib

    +This did not properly support multiple clients in multi-thread environment. +

    +dbPvdLib

    +Modified to be faster. +

    +devMz8311

    +Use maxCards from module_types.h instead of a #define +

    +calcRecord

    +Allow CALC to be 40 characters. Increase rpbuf from 184 to 200 +

    +mbbiDirectRecord

    +Add call to refresh_bits. +

    +mbbxDirectRecord

    +Bx becomes no prompt for mbbi and prompt for mbbo. It was the reverse before. +

    +calcoutRecord

    +A new record type that replaces old wait record. It is like a calc record +with an output and a delay. It makes the wait record obsolete. +

    +dbAccess

    +dbGetPdbAddrFromLink is a new routine. It returns NULL for all except LINK_DB +links, for which it returns the address of the associated DB_ADDR structure. +

    +escape characters in database files

    +dbLoadDatabase, dbLoadRecords, and dbLoadTemplate all allow the standard C escape sequences in quoted strings. For example a string can contain: -"\x00 \27 \t" Thus these sequences pass though the lexical analyzer -.

    - -

    dbTranslateEscape

    - -

    A new routine in libCom. It is used to translate escape sequences. It -is defined in file epicsString.h. It typical place to use this is on parm -fields that contain escape sequences like "\x00 \27 \t".

    - -

    Slow booting

    - -

    iocs with big databases were taking a long time to boot. It was discovered +"\x00 \27 \t" Thus these sequences pass though the lexical analyzer . +

    +dbTranslateEscape

    +A new routine in libCom. It is used to translate escape sequences. It is +defined in file epicsString.h. It typical place to use this is on parm +fields that contain escape sequences like "\x00 \27 \t". +

    +Slow booting

    +iocs with big databases were taking a long time to boot. It was discovered that allocating and then freeing small amounts of memeory frequently resulted -in a VERY long memory free list. This is now fixed.

    +in a VERY long memory free list. This is now fixed. +

    +boRecord, mbboRecord

    +init_record now initialized the RVAL field. +

    +ProcessCallback

    +Benjamin Franksen at BESSY reported a serious bug in the routine ProcessCallback +(not used in base). It has been fixed. +

    +CALC fields

    +postfix and calcPerform (used by calcRecord) have been changed so that +a 0 byte now ends the postfix expression. Also if postfix detects an illegal +expression it generates a 0 length postfix string. When calcPerform is +given a 0 length string it returns a error status. Thus calcRecord no longer +causes the IOC to crash if an illegal CALC fields is loaded. +

    +Etc.

    +Many other minor problems, bugs, etc. were fixed. +
    +
    +

    +Notes for Release 3.13 of EPICS Base

    -

    boRecord, mbboRecord

    - -

    init_record now initialized the RVAL field.

    - -

    ProcessCallback

    - -

    Benjamin Franksen at BESSY reported a serious bug in the routine -ProcessCallback (not used in base). It has been fixed.

    - -

    CALC fields

    - -

    postfix and calcPerform (used by calcRecord) have been changed -so that a 0 byte now ends the postfix expression. Also if postfix -detects an illegal expression it generates a 0 length postfix string. -When calcPerform is given a 0 length string it returns a error status. -Thus calcRecord no longer causes the IOC to crash if an illegal -CALC fields is loaded.

    - -

    Etc.

    - -

    Many other minor problems, bugs, etc. were fixed.

    - -

    - -

    Notes for Release 3.13 of EPICS Base

    - -

    For Release 3.13 major changes have been made to EPICS base. The IOC Application Developer's Guide has been extensively modified and now describes release 3.13. If you are upgrading for a 3.12.xxx or earlier release you -must obtain and read the new App Dev Guide.

    +must obtain and read the new App Dev Guide.

    In porting EPICS to multiple architectures, the previous method of using utilities to convert the database definition files to a binary file (default.dctsdr) @@ -204,78 +397,87 @@ caused problems. The problem is that the binary file is created on one architecture and used on another. This has worked so far for sun4 and hp hosts combined with motorola 68xxx processors. As support for more host and more ioc architectures is developed problems are appearing. This paper -describes changes that solve the problems.

    +describes changes that solve the problems.

    Because the changes result in extensive changes to database access, other changes are also made. The file syntax is changed. The internal database structures are simplified and also changed to make it easier to support -runtime add/delete of record types and record instances.

    - -

    Goals

    +runtime add/delete of record types and record instances. +

    +Goals

    -

    Backward Compatibility

    +

    +Backward Compatibility

    -

    Incompatibilities

    +

    +Incompatibilities

    -

    Overview of new database support

    - -

    EPICS defines a set of database file formats. In addition any of these +

    +Overview of new database support

    +EPICS defines a set of database file formats. In addition any of these files can contain include statements. For each ioc, the application developer will create a set of files specifying the record types, devices, and drivers needed for that ioc. Normally a master file will be created which consists of include statements that bring in record, device, and driver definitions. Default configurations can be provided for new users or for particular -applications.

    +applications.

    Database configuration and utility tools access the database via the static database access library. This library reads the files. It provides routines for reading the information in the database and for creating and modifying record instances. Database definition files can be read incrementally. -

    Other database configuration tools (capfast, relational database systems, object oriented databases, etc.) can also be used as long as they generate record instances in the format described below. In this case, however, it is still necessary to generate the other files because they are needed -by database access and for record and device support modules.

    +by database access and for record and device support modules.

    Tools are provided that generate C code from the database files. Header files are generated for menu and record type definitions. These header @@ -283,698 +485,706 @@ files are used by record and device support. In addition the record type definitions contain code which computes field offsets and sizes and record sizes. This code is compiled by the same cross compiler that is used to compile other ioc code. Thus cross platform compatibility is achieved. -

    In order to initialize an ioc, all files needed by that ioc have to be loaded. It is also necessary to load the record/device/driver support -modules.

    - -

    Everything is designed so that the following are possible:

    +modules. +

    Everything is designed so that the following are possible:

    - -

    An additional feature is that, for database configuration tools, record +An additional feature is that, for database configuration tools, record instance numeric fields and menu fields are stored as character strings. -This solves the following problems.

    - +This solves the following problems. +Another feature is is that it is now possible to distinguish link constants +with a value of 0 from links that have never been given a value. -

    Another feature is is that it is now possible to distinguish link constants -with a value of 0 from links that have never been given a value.

    - -

    Other changes have been made while the opportunity was available.

    - +

    Other changes have been made while the opportunity was available.

    -

    Database Definition File format

    - -

    Formats are defined for the following:

    - +

    +Database Definition File format

    +Formats are defined for the following: - -

    See the Application Developer's Guide for details.

    +See the Application Developer's Guide for details.

    The menu choices replace the existing global, record, and conversion choices. The global and record choices are very similar and thus are easy to combine. The method of handling the old conversion choices is described -below. That section also describes the breakpoint tables.

    +below. That section also describes the breakpoint tables.

    The record type description format has been completely changed. It now -has a "real" syntax. It should be MUCH easier to generate new -definitions.

    +has a "real" syntax. It should be MUCH easier to generate new definitions.

    The device choice and driver support definitions are defined so that -it is easy to provide incremental definitions.

    +it is easy to provide incremental definitions.

    The record instance format is an extension of the 3.12.beta13 and later -GDCT .db format.

    +GDCT .db format.

    Path and include statements are supported. This provides a powerful tool for combining definitions from many sources. The path is a unix style -path, i.e. a colon separated list of directory names.

    - -

    default.dctsdr conversion tools

    - -

    NOTES

    - +path, i.e. a colon separated list of directory names. +

    +default.dctsdr conversion tools

    +NOTES - -

    The following tools are provided:

    - +The following tools are provided: +
    All device definitions are placed in a file called device.dbd +
  • +sdr2driver [default.dctsdr]
    • -

    For all utilities the required database definition files are generated +
    All driver definitions are placed in a file called driver.dbd +For all utilities the required database definition files are generated from a dctsdr file from a previous epics release. A dctsdr file can be specified or else the utilities can be run in a directory which contains default.dctsdr (or a soft link with that name). sdr2recordtype also requires -the header file generated by a previous epics release.

    - -

    Conversions - replacement for DBF_CVTCHOICE

    - -

    Let's briefly review database conversion, i.e. the LINR field for ai -and ao records.

    - -

    The allowed conversions are:

    +the header file generated by a previous epics release. +

    +Conversions - replacement for DBF_CVTCHOICE

    +Let's briefly review database conversion, i.e. the LINR field for ai and +ao records. +

    The allowed conversions are:

      -
    1. None
      2. +
    2. +None
      3. -
    3. Linear
      4. +
    4. +Linear
      5. -
    5. Breakpoint Tables
      6. +
    6. +Breakpoint Tables
    - -

    The main complication results from the breakpoint tables. Previously -EPICS handled breakpoint tables as follows:

    +The main complication results from the breakpoint tables. Previously EPICS +handled breakpoint tables as follows:

    The user prepares files in one of two formats: The first is just a list -of "raw value, eng units value". The second format is a file -with a header line followed by a table of raw data values that represent -data at equally spaced engineering unit values. In either case the ascii -data is converted to an internal binary format containing breakpoint tables. -This data is part of default.dctsdr.

    - -

    Here is how breakpoint table are now handled.

    +of "raw value, eng units value". The second format is a file with a header +line followed by a table of raw data values that represent data at equally +spaced engineering unit values. In either case the ascii data is converted +to an internal binary format containing breakpoint tables. This data is +part of default.dctsdr. +

    Here is how breakpoint table are now handled.

    - -

    One other comment needs to be made about conversions. The Allen Bradley +One other comment needs to be made about conversions. The Allen Bradley device support for the IXE module uses the LINR field in a non standard way. This was a mistake but compatibility must be maintained. Thus menuConvert -contains a lot of choices used only by the IXE device support.

    +contains a lot of choices used only by the IXE device support. +

    +Converting existing applications

    -

    Converting existing applications

    +

    +Database Configuration Tools

    -

    Database Configuration Tools

    +
  • +DCT - Rather than making major changes to DCT, a TCL/TK replacement has +been written. The executable is named DCT313.
    • -
  • DCT - Rather than making major changes to DCT, a TCL/TK replacement -has been written. The executable is named DCT313.
    • +
  • +GDCT - A new version is provided that supports 3.13. The executable is +named GDCT313.
    • -
  • GDCT - A new version is provided that supports 3.13. The executable -is named GDCT313.
    • - -
  • CAPFAST
    • +
  • +CAPFAST
    • -

    Application Source/Release Control

    - -

    At the present time There are at least three Application Source/Release +

    +Application Source/Release Control

    +At the present time There are at least three Application Source/Release Control Systems in active use. The old technique of having cat_ascii and replace_ascii directories no longer work. In addition makesdr no longer exists. The new system offers developers far more flexibility but it also means that each Application Source/Release Control system has to be modified to take advantage of the new capabilities. Again the changes in RULES and -makeBaseApp should make this task easier.

    +makeBaseApp should make this task easier. -

    The document "EPICS -IOC Applications: Building and Source/Release Control" describes -a utility makeBaseApp which can be used for small applications. It also -provides guidlines that can be used for large applications.

    - -

    Locally developed Record/Device support

    +

    The document "EPICS +IOC Applications: Building and Source/Release Control" describes a +utility makeBaseApp which can be used for small applications. It also provides +guidlines that can be used for large applications. +

    +Locally developed Record/Device support

    + +
  • +link.h
    • + +
    All parm fields are now declared char * parm rather than char parm[] In addition the defines INSTIO_FLD_SZ to VXI_PARAM_SZ no longer exist. -This is done so that unused links now use less storage. - +This is done so that unused links now use less storage. -

    Record Instance Definitions

    +

    +Record Instance Definitions

    -

    Convert to proper format

    - -

    All record instances must be capable of being loaded into an ioc via -dbLoadDatabase, dbLoadRecords, or dbLoadTemplate. This is the same format -that dbLoadRecords and dbLoadTemplate used in 3.12 releases. Note that -if any files contain the statements:

    - -
            database(x) { nowhere() {
-        }
-        }
+
    
+Convert to proper format
    
+All record instances must be capable of being loaded into an ioc via dbLoadDatabase,
+dbLoadRecords, or dbLoadTemplate. This is the same format that dbLoadRecords
+and dbLoadTemplate used in 3.12 releases. Note that if any files contain
+the statements:
+
            database(x) { nowhere() {
+        }
+        }
 
 or
 
-        database(x) {
-        }
-
    
-
-
    These statements must be removed. They were in pre 3.12 releases. 
    
-
-
    CONSTANT Links with value "0"
    
-
-
    Release 3.13 is now capably of distingushing between a null link (a
-link that is not given any value at all) and a constant link with the value
+        database(x) {
+        }
    +These statements must be removed. They were in pre 3.12 releases. +

    +CONSTANT Links with value "0"

    +Release 3.13 is now capably of distingushing between a null link (a link +that is not given any value at all) and a constant link with the value 0. This cause problems for some old record instance files. For example -if a record instance is defined as:

    - -
            record(fanout,name) {
-                field(SELN,"1")
-                field(SELL,"0")
-        }
-
    - -

    Such definitions can be fixed by either completly removing the link -definition or changing the value from "0" to "".

    +if a record instance is defined as: +
            record(fanout,name) {
+                field(SELN,"1")
+                field(SELL,"0")
+        }
    +Such definitions can be fixed by either completly removing the link definition +or changing the value from "0" to "".

    here is a complete list of record types and fields that may have this -problem:

    +problem: +