![]() |
![]() |
![]() |
![]() |
![]() |
Error and Warning Messages
This section contains a list of the error and warning messages in the ASN.1 Utilities. Each message has a short explanation and, where applicable, a reference to the appropriate section of the recommendations X.680,X.681,X.682, X.683 or Z.105.
Some messages include a reference to the object that is the source of the diagnostic. These messages adhere to the format adopted in the SDL Suite. See SDT References for a reference to this format and for examples.
WARNING 2000 Unknown option `#1'
This warning message indicates that the ASN.1 Utilities were started with an unknown option. See Command-Line Interface for an overview of the valid options.
WARNING 2001 No #1 specified after '#2' option
This warning message indicates that the ASN.1 Utilities were started with an illegal combination of options. See Command-Line Interface for an overview of the valid options.
In this case no output file for sdl generation is specified after '-s' option.
ERROR 2002 Too many errors
This error message indicates that the maximum number of errors was reached when analyzing an ASN.1 module. The analysis has been aborted by the ASN.1 Utilities.
ERROR 2003 Multiple #1 paths
This warning message indicates an incorrect usage of the options of the ASN.1 Utilities.
asn1util -Tdir1 -Tdir2 -s MyModule.pr MyModule.asn
Multiple target directories provide a warning message
WARNING 2004 Option missing
This warning message indicates that no option is specified after dash.
ERROR 2005 Can not open #1
This error message indicates that an error occurred when the ASN.1 Utilities attempted to open a file. Modify, if necessary, the file protection and try to run the ASN.1 Utilities again. If the error persists, contact IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
asn1util -Tdir -i MyModule.ttcn MyModule.asn
This command line can cause an error message "Can not open air/MyModule.ttcn" if there is no target directory 'dir' in the catalogue from which asn1util is called.
ERROR 2006 Illegal characters in bstring
This message indicates that an ASN.1 binary string item (used in BIT STRING and OCTET STRING) contains illegal characters. The only characters allowed are `0', `1' and white space characters. (X.680: 9.9)
ERROR 2007 Illegal characters in hstring
This message indicates that an ASN.1 hexadecimal string item (used in BIT STRING and OCTET STRING) contains illegal characters. The only characters allowed are `0'-'9', `A'-'F' and white space characters. (X.680: 9.10)
For example: 'F30C 973D'H is a valid hexadecimal string item.
ERROR 2008 'H' or 'B' expected
This error message indicates that an ASN.1 BIT STRING or OCTET STRING value is not ended with a `B or an `H. (X.680: 9.9 and 9.10).
For example: '0110'B or '1AFC'H are valid values for BIT STRING and OCTET STRING, '01110' is illegal.
ERROR 2009 Unclosed #1 string
This error is reported when there is no closing apostrophe at the end of string
WARNING 2010 Unknown token `#1'
This warning indicates a syntax error in the ASN.1 module.
ERROR 2011 Syntax error
This message indicates a syntax error in the ASN.1 module with syntax from standard X.680-X.683. This could be caused by a misspelling. It could also be caused by X.228 constructs that are not part of X.680.
ERROR 2012 Out of memory
This message indicates that the ASN.1 Utilities ran out of memory. Try to make the ASN.1 module smaller or supply more memory. If the error persists, contact IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
WARNING 2013 No semantic support for `#1'
This warning indicates that an ASN.1 construct is used that is not supported by the ASN.1 Utilities. The construct will be ignored by the ASN.1 Utilities.
ERROR 2014 Export-file `#1' corrupt
This message indicates that the export file format of an ASN.1 module was corrupt or unknown. This error should normally not occur. Contact IBM Rational Customer Support. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support.
ERROR 2015 Old ASN1,#1
This message indicates that an ASN.1 construct of the older X.228 recommendation is used that has been superseded in the X.680 Recommendation.
is old ASN.1. Correct X.680 ASN.1 is:
S ::= SEQUENCE { field1 INTEGER }
ERROR 2016 Recursive expansion of COMPONENTS OF in type #1
This error message indicates that the ASN.1 type uses directly or indirectly COMPONENTS OF itself.
ERROR 2017 Recursive #1
This message indicates that the ASN.1 construct is recursively defined.
For example: T1::=T2, T2::=T1; T::=SET OF T, or v T ::= v
ERROR 2018 Recursive #1 constraint
This error message indicates that type being constrained is recursively used in applied constraint.
For example: I ::= INTEGER ( 1 .. 10 | INCLUDES I)
ERROR 2019 Field '#1' should be initialized by #2
This message is reported when you assign wrong kind of value for the field in the object, for example when you try to assign a value for the type field in the object
ERROR 2020 Value for `#1' can not be #2
This error message indicates a semantic error in the ASN.1 module.
For example, T ::= BIT STRING { a(-1)} causes the error "Value for 'named bit' can not be negative"
WARNING 2021 Construct `#1' has no mapping in SDL
This warning indicates that an ASN.1 construct is used that can not be mapped to SDL.
s SEQUENCE { a INTEGER OPTIONAL } ::= {}
-- value for SEQUENCE/SET without components
ERROR 2022 Ambiguous reference, symbol `#1' imported more than once
A value is used that is imported more than once. Use an external value reference to specify unambiguously the module of the value that you want to use.
ERROR 2023 Multiple definition of #1
This error message appears, when the same identifier appears more then once on the right side of assignment.
For example, X ::= INTEGER, X ::= SET OF REAL
ERROR 2024 Exported symbol #1 not defined
This error message is reported when symbol is exported, but it is neither defined in the module nor imported to it
ERROR 2025 Ambiguous export, symbol #1 is imported more than once
This error message indicates that it is impossible to decide which symbol to export, because two symbols with the name #1 are imported to the module
ERROR 2026 Ambiguous export, symbol #1 is defined and imported
This error message indicates that it is impossible to decide which symbol to export, because symbol #1 is defined in the module and imported to it at the same time
ERROR 2027 Nothing known about module #1
This message appears when module referenced from imports clause does not exist. You should specify all modules from which symbols are imported to the analyzed module in the same command line, otherwise it is impossible to perform global semantic analysis
ERROR 2028 Import from empty module #1
This message appears when importing symbols from a module, that does not contain any definitions
ERROR 2029 Module does not export symbols
This message appears when you are trying to import symbols from module with empty export: "EXPORTS ;"
ERROR 2030 Imported symbol #1 is not exported from module #2
This message appears when symbol #1 is present in imports from module #2 clause, but it is not exported from #2. "EXPORTS ;" indicates that nothing is exported, while empty exports clause indicates that all definitions are exported from the module.
ERROR 2031 Imported symbol #1 is not defined in module #2
This error situation occurs when symbol is imported from module that exports all, but symbol is not defined there
ERROR 2032 Ambiguous import, symbol #1 imported more than once to module #2
This indicates that all symbols are exported from module #2, but it is impossible to import symbol #1 from module #2 because symbol #1 is imported more than once to #2. The symbols have the same name, but defined in different modules.
ERROR 2033 Ambiguous import, symbol #1 defined and imported to module #2
This indicates that all symbols are exported from module #2, but it is impossible to import symbol #1 from module #2 due to ambiguity between symbol #1defined in module #2 and symbol #1 imported to module #2.
M1 DEFINITIONS ::= BEGIN
IMPORTS a FROM M2;
ENDM2 DEFINITIONS ::= BEGIN
IMPORTS a FROM M3;
a INTEGER ::=5
ENDM3 DEFINITIONS ::= BEGIN
EXPORTS a;
a BOOLEAN ::= TRUEIn the above case you can not import a to M1, although a is exported from M2.
ERROR 2034 Multiple declaratiom of module name #2
Module name shall appear only once in IMPORTS clause.
IMPORTS a , b FROM X c FROM X; is wrong ASN.1 declaration
ERROR 2035 Recursive import for #1
This error message is reported, for example, when module A imports T from B, and B imports T from A at the same time
ERROR 2036 Multiple occurance of #1 '#2' in #3
This error is reported when some types are defined incorrectly - they have the same identifier, for example enumeration can not have the same identifiers, named number list for INTEGER type can not have the same identifiers in the list, #2 is a string
ERROR 2037 Multiple occurance of #1 #2 in #3
The same class of error as ERROR 2036 above, but #2 is an integer value.
ERROR 2038 External references are not allowed
When imports clause looks like "IMPORTS ;",no external references are allowed from the module (X.680, 10.14, d), NOTE 2)
ERROR 2039 Referenced #1 '#2' not defined
This error is reported when you use reference that is not assigned value or type anywhere.
ERROR 2040 Value of type #1 needed
This error message indicates that value does not correspond to the type. For example x INTEGER ::= TRUE - this results in an error "Value of type INTEGER needed"
ERROR 2041 #1 type needed after COMPONENTS OF
The type after in COMPONENTS OF expansion should be either SET or SEQUENCE, and it should be the same as the type to which it is extracted.
For example SET { a INTEGER, b COMPONENTS OF T }, where T is SEQUENCE type is wrong usage of COMPONENTS OF notation(X.680, 22.4, 24.2)
ERROR 2042 Field names in type after COMPONENT OF already declared
After performing the COMPONENTS OF transformation, all field names should be distinct.
For example, type S1 is wrong (it has two fields named 'a')
S ::= SET { a INTEGER, b REAL }
S1 ::= SET { a SET OF IA5String, COMPONENTS OF S }
ERROR 2043 #1 type needed
This error is reported when type in selection type is not choice.
For example x < INTEGER does not satisfy that requirement
ERROR 2044 No alternative named #1 in Choice type
This error is reported when type notation is "#1 < type", type is a CHOICE type, but it does not have alternative named #1
ERROR 2045 Too many components
This error message appears when you are trying to assign extra components, which are not defined in the type, when specifying the value of SET or SEQUENCE
ERROR 2046 No such field '#1' in #2 type
This error indicates that type #2 does not have field named #1, but you are trying to assign it a value.
ERROR 2047 Missing values for non-optional #1 fields : #2
This message indicates that not all required #1 components have been initialized in the value, and #2 is the list of names of fields, for which values are missing. The example S ::= SET { a INTEGER, b REAL, c NULL OPTIONAL }, s S ::= { a 57 } results in error message "Missing values for non-optional SET fields: 'b'".
ERROR 2048 More than one #1 for the field '#2'
This error occurs when you are trying to assign more then one component to one field.
T ::= SET { a IA5String , b NULL }
t T ::= { a "val1", b NULL, a "val2" }
ERROR 2049 Nothing known about bit named '#1'
This error is reported when bitstring value contains identifier that is not declared in the correspondent type definition
ERROR 2050 Value for #1 should be #2
If you specify table for the value of IA5String, TableColumn should be in the range from 0 to 7, if this constraint is violated then the above error message is reported
ERROR 2051 Type is required to be derived from #1
This error indicates that type used in SubtypeConstraint is not derived from the type being constrained and thus does not satisfy X.680,45.3.2
ERROR 2052 Can not apply #1 constraint to #2 type
Not all constraints can be applied to every type, X.680, Table 6 describes which constraints can be applied to which types, if the requirements declared in Table 6 are not satisfied, the above error message is reported
ERROR 2053 There shall be at most one #1
Two presents constraints are not allowed when constraining a CHOICE type.
C ::= CHOICE { a T1 , b T2 } (WITH COMPONENTS {a PRESENT, b PRESENT} )
ERROR 2054 Wrong value : out of constraint
This error is reported when value does not correspond to the constraint applied to the type.
For example: x INTEGER (1..10) ::= -1, x is out of constraint
ERROR 2055 The same tags for #1 components
This error message indicates that type does not correspond to the requirements for distinct tags specified in X.680, 22.5, 24.3, 26.2; If you use AUTOMATIC TAGS in the module, requirement for distinct tags will always be satisfied if automatic tagging has been applied
ERROR 2056 OBJECT IDENTIFIER value should have at least two components
x OBJECT IDENTIFIER ::= { iso } is wrong object identifier value because encode/decode functions require at least two components for object identifier value
WARNING 2057 Construct #1 has no mapping in SDL
This warning is reported if no mapping to sdl exist but it does not prevent further code generation.
ERROR 2058 Construct #1 has no mapping in SDL
This error indicates that no mapping to sdl exist and is fatal for further code generation.
WARNING 2059 Value given for #1 component
This warning indicates that a value has been given to an optional or default component of an ASN.1 SEQUENCE or SET type. Values for optional and default components cannot be translated to SDL.
WARNING 2060 Constraint could have been extended when mapped to sdl
This warning indicates that constraint transformation has been applied when mapping complex ASN.1 constraints to sdl but the sdl type can allow more values than the ASN.1 type. This can occur when there is no exact mapping of ASN.1 constraints.
ERROR 2061 INTERNAL ERROR in #1
This message indicates an error in the implementation in the utilities. Please send a report to IBM Rational Customer Support, especially if the error can be reproduced as the only error message of an analysis. Contact information for IBM Rational Customer Support can be found in How to Contact Customer Support
ERROR 2062 Code generation : #1
Error in the generation of SDL, TTCN or encode/decode output.
WARNING 2063 Too big exponent
Exponent in a real value is too big to translate to SDL. This warning message is shown if the exponent is bigger than 1000 or less than -1000.
WARNING 2064 Duplicate synonym name, this synonym will not be mapped to SDL
This message indicates that there are synonym name clashes between named numbers and named bits from INTEGER and BIT STRING types and ASN.1 values if they all will be mapped to SDL (see Integer and Bit String), and in order to avoid errors only one synonym will be mapped, others are ignored.
ERROR 2065 Number #1 is already assigned to previously defined enumeration item
This error message is reported when NamedNumber alternative is used in an enumerated type definition in an addition enumeration after extension marker and the number #1 has already been assigned to identifier from root enumeration, for example A ::= ENUMERATED {a,b, ... , c(0)} First corresponding numbers are assigned to identifiers in root enumeration, and then in additional enumeration. The above case is invalid, since both 'a' and 'c' are equal to 0.
ERROR 2066 Value for the field '#1' needed #2
This message indicates that value for the field '#1' is missing, but it should be present in #2
ERROR 2067 #1 omitted in #2
Indicates that #1 is omitted, but it should be present in #2
ERROR 2068 #1 should reference #2
This message indicates that a field name references an object class field that is not allowed to be referenced.
ERROR 2069 Wrong object specification
This message indicates that an object specification is incorrect
ERROR 2070 #1 of class #2 needed
This message indicates that an object or object set does not match the governing object class specified in object or object set's definitions
ERROR 2071 Wrong defined syntax
This message indicates that an error in defined syntax for the object definition
ERROR 2072 #1 can not be used in object set specification
This message indicates that an illegal construct is used in the object set specification
ERROR 2073 #1 in the field '#2' is not specified in the #3
This message is reported when information, for example, type or value, is extracted from object field that has not been initialized in the object. This can occur when the field is optional or default in the object class.
WARNING 2074 #1 is not supported in the encoders / decoders
This warning message is reported when ASN.1 notation is used that the encoder / decoder library cannot support
ERROR 2075 #1 can be used only for #2
This message is reported when #1 is used in a component relation constraint but is not allowed to be used in that context.
ERROR 2076 #1
This is used for several different messages concerning component relation constraint, each message is listed and explained below:
Referenced component should refer to the same object class as the referencing one
This message indicates that the referenced and referencing components in a component relation constraint do not stem from the same object class.
Only fixed type value fields are allowed to be specified in a referenced component
This message indicates that a referenced component in a component relation constraint is not a fixed type value field, for example
SET {a MY-CLASS.@id ({My-set}),b MY-CLASS.@TypeField ({My-set})}For the field a, @id should reference fixed type value field in class 'MY-CLASS'
Only values of INTEGER types can be used as component relation identifiers";
This message is reported when a referenced fixed type value field is not an INTEGER, only INTEGERS are supported.
SET {a MY-CLASS.@id ({My-set}),b MY-CLASS.@TypeField ({My-set})}In the example above @id should be derived from an INTEGER.
Wrong referenced component
This message indicates that a wrong type of component is referenced in a component relation constraint, for example not using ObjectClassFieldType notation.
Referenced components should be constrained by the same object set as the referencing one
This message indicates that the referenced and referencing component are not constrained with the same object sets.
ERROR 2077 ASN.1 identifier #1 is a keyword, it will be replaced by #2
This message is reported when an ASN.1 identifier is a keyword in one of the target languages and will be changed according to the keywords configuration file during mapping for avoiding syntax errors in the target languages.
ERROR 2078 Module #1 has got name clashes within joined modules group '#2'
This message is reported when an ASN.1 definition name causes name clashes within joined SDL package and will be prefixed by the original ASN.1 module name during mapping to avoid errors in SDL (see Joining modules).
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |