Home Page   We Generate Your Software.
Products Services Company Technology Demo Contact Site Map Search
The Somusar/SoProTech[tm] Booklet Series
Volume VII

"somusar/SoProMach: User's Guide"

Printer friendly


Contents
1. Introduction
2. Package Contents
3. Installing SoProMach
4. Verifying the Installation
5. Generating software with SoProMach
6. SoProMach Models
7. Sisendel Messages
7.1 Sisendel Error Messages
7.2 Sisendel Warning Messages
8. Tefigel Messages
9. Contacting Somusar
10. Further Reading

Chapter 7 - Sisendel Messages

7.1 - Sisendel Error Messages        top

The following list describes all fatal errors of the Sisendel translator, that is, all error conditions that cause Sisendel to stop processing entities and terminate with an error condition. The official definition of the syntax and semantics of Sisendel is documented in "Somusar/Sisendel[tm]: Reference Guide ".

- ... are not allowed within section "..."

The specified Sisendel language construct cannot be used in the specified section.

- arrays of functions are not allowed

Sisendel does not allow to associate a cardinality with a field of type function; alternatively, it is possible to define an entity A containing only a function field, and define a field of another entity B to be an array of A entities.

- can't get current directory: ...

An attempt to retrieve the current working directory has failed. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation".

- checking NULL directory

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- comment "..." is too long (longer than 4096 characters)

The specified comment - resulting from the concatenation of the sequence of comment lines starting at the specified line - exceeds the maximum allowed length, which is currently 4096.

- complete collection of entity fields is too long

The full list of field identifiers yields a string exceeding the maximum allowed length. Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- could not convert string "..." into number

The specified enumeration value definition does not contain a valid numeric value.

- creating dir. "..."

An attempt to create the specified directory has failed. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation".

- creating NULL directory

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- environment variable "..." not set

A value for the specified environment variable must be defined prior to starting the Sisendel translator.

- empty definition for field "..."

The definition for the specified field in section DEFS is empty.

- empty description

The specified field (or entity) description (or label) is an empty string.

- entity "..." multiply defined (files "..." and "...")

The same entity file prefix - i.e., the user-defined type id - is used more than once within the project tree, therefore the entity type is not unique.

- enumeration definition associated with field of type "..."

A definition of an enumeration field in section DEFS refers to a field whose type is not enum.

- enumeration symbol "..." used more than once

The definition of an enumeration field in section DEFS contains two identical, non-unique symbolic values.

- enumeration value ... ('...') used more than once

The definition of an enumeration field in section DEFS contains two identical, non-unique numeric or character values.

- exec... failed

An attempt to start the Tefigel processor has failed probably due to a system overload. A check of the system status is highly recommended.

- extension "..." in mold "...", layer "...", is reserved

The generatable file extension used in the specified mold is reserved by Sisendel and cannot be used for generatable files.

- failed to read range lower bound from "..."

The specified range definition in section DEFS contains a non-numeric value for the lower bound of the range field.

- failed to read range upper bound from "..."

The specified range definition in section DEFS contains a non-numeric value for the upper bound of the range field.

- field "..." not a member of collection "..."

The specified adjusting parameter in section ADJUST refers to a collection that does not contain the specified field.

- field "..." previously defined

Multiple definition of the specified field, that is, the same field identifier is used more than once.

- file "..." not part of library "..."

The specified entity file does not belong to the current Sisendel library, that is, it is not within the file-system subtree starting at directory SISENDEL_LIBRARY.

- file "..." not part of project "..."

The specified entity file does not belong to the current Sisendel project, that is, it is not within the file-system subtree starting at directory SISENDEL_PROJECT.

- fixed-size arrays of links are not allowed

Sisendel does not allow to define fixed-size arrays of links. A list of entities can be used instead.

- fork failed

An attempt to start the Tefigel processor has failed probably due to a system overload. A check of the system status is highly recommended.

- function definition associated with field of type "..."

A definition of a function field in section DEFS refers to a field whose type is not function.

- identifier "..." is too long

The specified identifier exceeds the maximum allowed length, which is currently 512 characters.

- illegal adjusting section "..."

The section identifier in the specified adjusting parameter does not correspond to any legal Sisendel section.

- illegal character '...' (0x...) in identifier "..."

Sisendel identifiers may only contain lower case letters, digits, and underscores _.

- illegal step 0 under "..."

The specified mold directory contains a generation step directory called "0": legal generation steps directories start from "1".

- imported fields must be of a basic type

The type of the source field for the specified imported field is not a basic type.

- imported fields of type "..." are not allowed

The type of the source field for the specified imported field cannot be used for imported fields.

- importing from a basic type is not allowed

The entity part of the source field for the specified imported field refers to a basic type instead of referring to an entity file.

- importing from within the same user type is not allowed

The entity part of the source field for the specified imported field refers to the same entity file defining the imported field.

- items collection "..." is empty

No fields have been listed as members for the specified collection.

- library entity dir. "..." and project dir. "..." are not separated

One of the directories specified as SISENDEL_PROJECT and SISENDEL_LIBRARY is currently a subtree of the other: these directories must be separated in order for Sisendel to distinguish library entities from project entities. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation".

- links to basic types are not allowed

The keyword link must be followed by a user type (i.e., an entity id).

- lists of basic types are not allowed

The keyword list must be followed by a user type (i.e., an entity id).

- lower bound of range "..." not smaller than the upper bound

The specified range definition in section DEFS is not in the form "lower-bound/upper-bound".

- missing/bad/too high ordinal number in mold "...", layer "..."

The mold ordinal number in the directory name of the specified mold does not correctly specify the mold position in the mold group sequence.

- missing cardinality for "string ..."

A cardinality definition for the specified string field must be supplied in the field definition.

- missing collection identifier before member list

No identifier has been specified before the specified collection.

- missing definition for "enum ..."

A definition for the specified enum field must be supplied in section DEFS.

- missing definition for "range ..."

A definition for the specified range field must be supplied in section DEFS.

- missing definition of range lower bound

The specified range definition in section DEFS is not in the form "lower-bound/upper-bound".

- missing description of entity

No entity id and label have been specified in section CORE.

- missing field reference before enumeration definition

The specified enum definition in section DEFS is not associated with any field: a field identifier must be specified before the specified line.

- missing field reference before function definition

The specified function definition in section DEFS is not associated with any field: a field identifier must be specified before the specified line.

- missing field reference before range definition

The specified range definition in section DEFS is not associated with any field: a field identifier must be specified before the specified line.

- missing section "..."

The specified entity file does not contain the specified mandatory section.

- missing signature for "function ..."

An interface definition (signature) for the specified function field must be supplied in section DEFS.

- missing step ... under "..."

The specified mold directory does not contain any generation step subdirectory for the specified step number (i.e., the generation step slot is empty).

- missing subdirectory for mold ... in layer "..."

The mold group for the specified layer does not contain any mold for the specified ordinal number (i.e., the mold group slot is empty).

- multiple definition for range field "..."

Section DEFS contains more than one definition for the specified range field.

- multiple definition of collection "..." within section "..."

The specified collection id is used more than once within the specified section.

- multiple definition of entity

The specified entity file contains more than one entity definition line in section CORE.

- multiple enumeration definitions for field "..."

Section DEFS contains more than one definition for the specified enum field.

- multiple reference to field "..." within collection "..."

The specified collection contains more than one reference to the specified field.

- multiple value definition for enumeration symbol "..."

Section DEFS contains more than one definition for the specified enum symbolic value.

- no field defined with id "..."

The specified line contains a reference to an invalid field identifier.

- no field defined with index ...

The specified line contains a reference to an invalid field.

- opening directory (...) "..."

An attempt to access the specified directory has failed. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation".

- opening entity directory "..."

An attempt to access the specified directory has failed. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation".

- opening mold directory "..."

An attempt to access the specified directory has failed. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation".

- ordinal number multiply used in mold "...", layer "..."

The ordinal number used in the name of the specified mold has already been used in the same mold group, therefore the mold group sequence is not properly defined.

- processed file contains no entity definition

Either the entity definition or the entity label is empty, or both are missing from the specified entity file.

- ran out of space

An attempt of the Sisendel processor to allocate memory has failed probably due to a system overload. A check of the system status is highly recommended.

- range definition associated with field of type "..."

The range definition in section DEFS refers to the a field of the specified type.

- reconversion of lower bound fails, value ... is probably too small

The number specified for the lower bound in the range definition in section DEFS cannot be converted without changes from/to string format; the value is probably too small (underflow).

- reconversion of upper bound fails, value ... is probably too big

The number specified for the upper bound in the range definition in section DEFS cannot be converted without changes from/to string format; the value is probably too large (overflow).

- removing dir. "..."

An attempt to remove the specified directory has failed. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation".

- removing NULL directory

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- section "..." multiply defined

The specified entity file contains more than once the specified section.

- section "..." must appear before section "..."

The correct section order for entity files is:
(CORE), DEFS, DB, LOGIC, UI, ADJUST.

- step ... under "..." defined more than once

More than one step subdirectory of the specified mold corresponds to the specified step, possibly due to different directory names that map to the same number (such as "1" and "01").

- syntax error >>...<<.

The specified line does not match any of the syntax rules specified by the Reference Guide of Sisendel: possible errors could be missing labels, tabs before or between collection members, upper case letters in identifiers, semicolon missing from collection labels, and several others. The syntax of Sisendel is defined in "Somusar/Sisendel[tm]: Reference Guide ".

- too many (max: 50) collections of items

The specified entity file exceeds the maximum level of collections (50).

- too many (max: 100) entity fields

The specified entity file exceeds the maximum number of entity fields (100).

- too many directories (max: 32) in input pathname "..."

The specified file pathname exceeds the maximum number of directory nesting (32).

- too many (max: 200) property adjustings

The specified entity file exceeds the maximum number of adjusting parameters (200).

- too many members (max: 200) for enumeration "..."

The specified enum field exceeds the maximum number of enumeration values (200).

- too many (max: ...) molds defined for layer "..."

The specified maximum number of molds has been exceeded. An upgrade to a higher edition of SoProMach is recommended.

- too many parameters (max: 100) for function "..."

The specified function field exceeds the maximum number of input parameters (100).

- too many signatures (max: 8) for function "..."

The specified function field exceeds the maximum number of function signatures (8).

- too many steps (max: 15) under "..."

The specified maximum number of file generation steps has been exceeded by the specified mold.

- too many user-defined types (max: ...)

The specified maximum number of entity files has been exceeded. An upgrade to a higher edition of SoProMach is recommended.

- undefined collection "..." for section "..."

The specified adjusting parameter of section ADJUST refers to a collection which is not defined in the specified section.

- undefined type "..."

The type of the specified field is neither a basic type, nor a user-defined type (entity file).

- unknown section id "..."

The specified section id is invalid. The correct section order for entity files is:
(CORE), DEFS, DB, LOGIC, UI, ADJUST.

- user type "..." has no field called "..."

The field part of the imported field type of the specified field does not correspond to a field of the referenced entity.

7.2 - Sisendel Warning Messages        top

The following list describes all warning messages issued by the Sisendel translator, that is, all error conditions that do not cause Sisendel to stop processing entities.

- cannot open molds directory "..."

The mold group for the specified layer cannot be found or accessed by the Sisendel translator; should this be intentionally so, due to project conventions, it is possible to turn off this warning by simply creating an empty directory for the specified layer under SISENDEL_MOLDS.

- enumeration description "..." used more than once

The label for the specified enum value in section DEFS has been already used within the same enumeration definition.

- ignoring unnecessary mold directory "..."

The mold kit directory SISENDEL_MOLDS contains a layer directory for the specified entity file section, that by Sisendel definition cannot contain any collection of fields, and is thus never searched by the Sisendel translator for molds to be applied to the input entity files.

- mold processing failed

The mold processing performed by the Tefigel processor has failed, probably due to a missing file or a mold error. The Tefigel error message should provide hints on the reason of the error.

[Previous chapter]    [Next chapter]    [Back to top]

http:// www.somusar.com  / doc  / booklets  / usr_guide  - Powered by SoProMach
Copyright © 2003-2012 Somusar - Trademarks - Legal - Privacy - Webmaster