We stand with Ukraine Compiler Errors Reference (1000-1299)
C1000W
Message Format
C1000W: XSD directive applied to a Type which is not a PDU: '<type reference>'.
Message Cause
The OSS.XSD compiler directive is incorrectly applied to a type that is not a PDU.
Example
--<OSS.XSD Module-C1000W.T1 "First.xsl">--
Module-C1000W DEFINITIONS ::= BEGIN
T1 ::= BOOLEAN
T2 ::= SET OF T1
END
Error Message
"c1000w.asn", line 4 (Module-C1000W): C1000W: XSD directive applied to a Type which is not a PDU: 'T1'.
Possible Solution
You can either eliminate the incorrect OSS.XSD directive or apply the PDU directive to the corresponding type.
C1001W
Message Format
C1001W: The global XML element name '<name>' is being used as the outermost XER element name for two different ASN.1 types (see lines <number> (<module reference>) and <number> (<module reference>)). The generated XSD file '<filename.xsd>' will reflect only the first of these types; the second one is being ignored. Consider renaming the second ASN.1 type to avoid ambiguity.
Message Cause
Two or more PDUs have the same element name in the XER encoding. Due to the name conflict caused by two global elements in the same namespace, the PDUs cannot be processed correctly in the generated XSD file.
Example
--<OSS.ROOT>-- Module-C1001W-1 DEFINITIONS ::= BEGIN PDU ::= INTEGER END Module-C1001W-2 DEFINITIONS ::= BEGIN PDU ::= SET OF INTEGER END
Error Message
"c1001w.asn", line 7 (Module-C1001W-2): C1001W: The global XML element name 'PDU' is being used as the outermost XER element name for two different ASN.1 types (see lines 3 (Module-C1001W-1) and 7 (Module-C1001W-2)). The generated XSD file 'c1001w.xsd' will reflect only the first of these types; the second one is being ignored. Consider renaming the second ASN.1 type to avoid ambiguity.
Possible Solution
Rename the second ASN.1 type.
C1002W
Message Format
C1002W: The ObjectSet '<object set reference>' used for the definition of '<type reference>' (see line <number>) contains two anonymous CHOICEs with identical alternative names ('<name>'). To avoid schema ambiguity, a wildcard is used for this element.
Message Cause
The ObjectSet contains several anonymous CHOICEs with identical alternative names.
By default, when two identical alternative names are present, the OpenType ASN.1 type is mapped to the XSD choice type as follows(note the 'info' field):
Module DEFINITIONS ::= BEGIN
ERROR ::= CLASS {
&code INTEGER,
&Type
}
MySet ERROR ::= {
{&code 1, &Type CHOICE {a INTEGER }} |
{&code 2, &Type CHOICE {b BOOLEAN }}
}
ErrorReturn ::= SEQUENCE {
code ERROR.&code ({MySet}),
info ERROR.&Type ({MySet}{@code})
}
END
<xsd:complexType name="ErrorReturn">
<xsd:sequence>
<xsd:element name="code">
<xsd:simpleType>
<xsd:restriction base="INTEGER"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="info">
<xsd:complexType mixed="true">
<xsd:choice>
<xsd:element name="CHOICE" minOccurs="0">
<xsd:complexType>
<xsd:choice>
<xsd:choice>
<xsd:element name="a" type="BOOLEAN"/>
</xsd:choice>
<xsd:choice>
<xsd:element name="b" type="INTEGER"/>
</xsd:choice>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
For identical alternative names, for example 'a', the mapping is as follows:
<xsd:element name="CHOICE" minOccurs="0">
<xsd:complexType>
<xsd:choice>
<xsd:choice>
<xsd:element name="a" type="BOOLEAN"/>
</xsd:choice>
<xsd:choice>
<xsd:element name="a" type="INTEGER"/>
</xsd:choice>
</xsd:choice>
</xsd:complexType>
</xsd:element>
This schema is invalid because the Unique Particle Attribution rule is violated. To avoid the schema error and to allow all valid XER encodings, a wildcard is used for element 'a':
<xsd:element name="CHOICE" minOccurs="0">
<xsd:complexType>
<xsd:choice>
<xsd:element name="a" minOccurs="0">
<xsd:complexType>
<xsd:choice>
<xsd:any processContents="lax"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
Example
Module-C1002W DEFINITIONS ::= BEGIN
ERROR ::= CLASS {
&code INTEGER,
&Type
}
MySet ERROR ::= {
{&code 1, &Type CHOICE {a INTEGER }} |
{&code 2, &Type CHOICE {a BOOLEAN }}
}
ErrorReturn ::= SEQUENCE {
code ERROR.&code ({MySet}),
info ERROR.&Type ({MySet}{@code})
}
END
Error Message
"c1002w.asn", line 10 (Module-C1002W): C1002W: The ObjectSet 'MySet' used for the definition of 'ErrorReturn' (see line 16) contains two anonymous CHOICEs with identical alternative names ('a'). To avoid schema ambiguity, a wildcard is used for this element.
C1003W
Message Format
C1003W: The ObjectSet '<object set reference>' used for the defintion of '<type reference>' (see line <number>) contains two anonymous types (<type reference>s) with identical field names. To avoid schema ambiguity, a wildcard is used for element '<name>'.
Message Cause
ObjectSet contains several anonymous types (SEQUENCE, SEQUENCE OF or SET OF) with identical field names.
By default, (if there are no identical alternative names) OpenType ASN.1 type is mapped to an XSD choice type as follows (note 'info' field):
Module DEFINITIONS ::= BEGIN
ERROR ::= CLASS {
&code INTEGER,
&Type
}
MySet ERROR ::= {
{&code 1, &Type SEQUENCE {a INTEGER, b IA5String }} |
{&code 2, &Type SEQUENCE {c BOOLEAN }}
}
ErrorReturn ::= SEQUENCE {
code ERROR.&code ({MySet}),
info ERROR.&Type ({MySet}{@code})
}
END
<xsd:complexType name="ErrorReturn">
<xsd:sequence>
<xsd:element name="code">
<xsd:simpleType>
<xsd:restriction base="INTEGER"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="info">
<xsd:complexType mixed="true">
<xsd:choice>
<xsd:element name="SEQUENCE" minOccurs="0">
<xsd:complexType>
<xsd:choice>
<xsd:sequence>
<xsd:element name="c" type="BOOLEAN"/>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="a" type="INTEGER"/>
<xsd:element name="b" type="IA5String"/>
</xsd:sequence>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
For identical alternative names, for example 'a', the mapping is as follows:
<xsd:element name="SEQUENCE" minOccurs="0">
<xsd:complexType>
<xsd:choice>
<xsd:sequence>
<xsd:element name="a" type="BOOLEAN"/>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="a" type="INTEGER"/>
<xsd:element name="b" type="IA5String"/>
</xsd:sequence>
</xsd:choice>
</xsd:complexType>
</xsd:element>
This schema is invalid because the Unique Particle Attribution rule is violated. To avoid the schema error and to allow all valid XER encodings, a wildcard is used for the element 'SEQUENCE':
<xsd:element name="SEQUENCE" minOccurs="0">
<xsd:complexType>
<xsd:choice>
<xsd:any processContents="lax"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
Example
Module-C1003W DEFINITIONS ::= BEGIN
ERROR ::= CLASS {
&code INTEGER,
&Type
}
MySet ERROR ::= {
{&code 1, &Type SEQUENCE {a INTEGER, b IA5String }} |
{&code 2, &Type SEQUENCE {a BOOLEAN }}
}
ErrorReturn ::= SEQUENCE {
code ERROR.&code ({MySet}),
info ERROR.&Type ({MySet}{@code})
}
END
Error Message
"c1003w.asn", line 7 (Module-C1003W): C1003W: The ObjectSet 'MySet' used for the defintion of 'ErrorReturn' (see line 12) contains two anonymous types (SEQUENCEs) with identical field names. To avoid schema ambiguity, a wildcard is used for element 'SEQUENCE'.
L1004W
Message Format
L1004W: Ignoring filename: <filename1>. XML Schema will be written to <filename2>.
Message Cause
The ASN.1 compiler command line contains two or more instances of the -xsd option followed by different filename arguments. The last filename specified will be used.
Possible Solution
Remove the extra -xsd instances and their arguments.
C1005E
Message Format
C1005E: The '<option name>' option must have a mandatory argument '<argument>'
Message Cause
A mandatory argument is missing from the ASN.1 compiler command-line option.
Example
asn1 a.asn -compat
Error Message
C1005E: The -compat option must have a mandatory argument <VersionNumber or Option>
Possible Solution
Add the missing argument after the option.
A1006E
Message Format
A1006E: The type of the value 'name' and the type of the value it is assigned to are not compatible.
Message Cause
The value assigned in the ASN.1 value assignment has a governor that is not compatible with the governor used in the value assignment and the -allowBadValues compiler option is not specified.
Example
E1 ::=ENUMERATED{a(1), b(2), c(3)}
E2 ::=ENUMERATED{red(1), blue(3), green(5)}
e1 E1 ::= b
e2 E2 ::= e1
Error Message
"test.asn", line 5 (UseOperation): A1006E: The type of the value 'e2' and the type of the value it is assigned to are not compatible.
A1007W
Message Format
A1007W: The type of the value 'name' and the type of the value it is assigned to are not compatible.
Message Cause
The value assigned in the ASN.1 value assignment has a governor that is not compatible with the governor used in the value assignment and the compiler option -allowBadValues is specified. It occurs under the same conditions as the A1006E error message.
Example
E1 ::=ENUMERATED{a(1), b(2), c(3)}
E2 ::=ENUMERATED{red(1), blue(3), green(5)}
e1 E1 ::= b
e2 E2 ::= e1
Error Message
"test.asn", line 5 (UseOperation): A1007W: The type of the value 'e2' and the type of the value it is assigned to are not compatible.
C1009E
Message Format
C1009E: The Remove directive cannot be applied to a Contents Constraint contained type. Check the contained type with the absolute reference absolute reference.
Message Cause
An ASN1.Remove directive is applied to the contents constraint contained type.
Example
--<ASN1.Remove Module-C1009E.CC.*>-- Module-C1009E DEFINITIONS ::= BEGIN CC ::= OCTET STRING (CONTAINING INTEGER) END
Error Message
"c1009e.asn", line 4 (Module-C1006E): C1009E: The Remove directive cannot be applied to a Contents Constraint contained type. Check the contained type with the absolute reference 'Module-C1009E.CC.*'."
Possible Solution
Delete the ASN1.Remove directive or apply it to the contents constraint that references the type to be removed.
C1010W
Message Format
C1010W: XER encoding instructions are present in the input notation. EXTENDED-XER encoding rules are not currently supported when the ' codefile' option is specified, therefore the XER encoding instructions present will always be ignored. Please contact OSS Nokalva (info@oss.com), if you are interested in EXTENDED-XER support in conjunction with '-codefile'.
Message format when using the compiler GUI
C1010W: XER encoding instructions are present in the input notation. EXTENDED-XER encoding rules are not currently supported by the time-optimized encoder/decoder, therefore the XER encoding instructions present will always be ignored. Please contact OSS Nokalva (info@oss.com), if you are interested in EXTENDED-XER support for this runtime.
Message Cause
This error is issued for all combinations of product/runtime that do not support EXTENDED-XER, such as ASN.1/C (-code), ASN.1/C++ (all versions). For these products, the compiler can check the syntax of the EXTENDED-XER but no code is generated for use with the runtime.
Example
c1010w.asn:
C1010W DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS END
ASN.1 Compiler command line:
asn1 c1010w.asn -code
Error Message
C1010W: XER encoding instructions are present in the input notation. EXTENDED-XER encoding rules are not currently supported when the '-codefile' option is specified, therefore the XER encoding instructions present will always be ignored. Contact OSS Nokalva (info@oss.com), if you are interested in EXTENDED-XER support in conjunction with '-codefile'.
Possible Solution
You can use either the OSS ASN.1/C and SOED, or the OSS ASN.1/ Java tools.
A1011E
Message Format
A1011E: 'TextBoolean' and 'EmptyElementBoolean' may not appear in the same XMLValueAssignment.
Note that instead of "BOOLEAN", other messages may be display: "INTEGER", "ENUMERATED", or "BIT STRING".
Message Cause
Two mutually exclusive forms of XML Value for the same ASN.1 type are present within a single XMLValueAssignment.
Example
A1011E DEFINITIONS ::= BEGIN
S ::= SEQUENCE {f1 BOOLEAN, f2 BOOLEAN}
s ::= <S>
<f1><true/></f1>
<f2>true</f2>
</S>
END
Error Message
"a1011e.asn", line 5 (A1011E): A1011E: 'TextBoolean' and 'EmptyElementBoolean' may not appear in the same XMLValueAssignment.
<f2>true</f2>
Possible Solution
Make sure you are consistent: use one of the two mutually exclusive forms of XML Value in the scope of each XMLValueAssignment.
See Also
A1012E
Message Format
A1012E: When EmptyElementBoolean or EmptyElementEnumerated is used for the value then XMLValueList shall be used.
Message Cause
The XMLValueAssignment includes a value for a SET OF or SEQUENCE OF type with a BOOLEAN or ENUMERATED element. The value is defined as an XMLDelimitedItemList (a value of each element is wrapped by a pair of tags corresponding to its type) but element values are represented by empty-element XML tags. This combination is not supported.
Example
A1012E DEFINITIONS ::= BEGIN S ::= SEQUENCE OF b BOOLEAN s ::= <S><b><true/></b></S> END
Error Message
"a1012e.asn", line 3 (A1012E): A1012E: When EmptyElementBoolean or EmptyElementEnumerated is used for the value then XMLValueList shall be used.
s ::= <S><b><true/></b></S>
Possible Solution
Remove the wrapping tags from the elements of the SET OF or SEQUENCE OF value:
s ::= <S><true/></S>
See Also
L1013E
Message Format
L1013E: Error creating directory, dirname.
Message Cause
The ASN.1 compiler was unable to create the specified output directory.
Possible Solution
Make sure the process running the ASN.1 compiler has the proper write-permissions in the directory where the output is created.
C1014W
Message Format
C1014W: The 'DirectiveName' directive cannot be applied to 'identifier' since the type has a final 'DECIMAL' encoding instruction.
Message Cause
A REAL type employs a combination of a DECIMAL encoding instruction and an OSS.FLOAT, OSS.DOUBLE, or OSS.MIXED directive. This is not supported (only OSS.DECIMAL is allowed for the DECIMAL encoding instruction).
NOTE: After issuing the warning, the compiler disables the incorrect directive and applies the OSS.DECIMAL directive internally. In other words, the encoding instruction takes precedence over the directive. The compiler also implies OSS.DECIMAL if REAL has no directives.
Example
C1014W DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
a [DECIMAL] REAL --<MIXED>--
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1014w.asn", line 4 (C1014W): C1014W: The 'MIXED' directive cannot be applied to 'a' since the type has a final 'DECIMAL' encoding instruction.
Possible Solution
Remove the directive.
C1015W
Message Format
C1015W: The recommended prefix 'prefix1' for the namespace name 'uri1' has been replaced by 'prefix2' in order to resolve its conflict with the recommended prefix 'prefix1' for the namespace name 'uri2'.
Message Cause
Two distinct namespaces (specified by NAMESPACE or GLOBAL DEFAULTS CONTROL NAMESPACE encoding instructions) have the same prefix. In case of name conflict, the ASN.1 compiler will rename one of the prefixes.
Example
C1015-1 DEFINITIONS XER INSTRUCTIONS ::= BEGIN R1 ::= REAL ENCODING-CONTROL XER NAMESPACE AS "www.xxx.org" PREFIX "oss" END C1015-2 DEFINITIONS XER INSTRUCTIONS ::= BEGIN IMPORTS R1 FROM C1015-1; R2 ::= INTEGER ENCODING-CONTROL XER NAMESPACE AS "www.yyy.org" PREFIX "oss" END
Error Message
"c1015w.asn", line 17 (C1015-2): C1015W: The recommended prefix 'oss' for the namespace name 'www.yyy.org' has been replaced by 'oss1' in order to resolve its conflict with the recommended prefix 'oss' for for the namespace name 'www.xxx.org'.
Possible Solution
Rename one of the conflicting prefixes.
A1016E
Message Format
A1016E: The 'encodingreference' shall not be 'TAG'.
Message Cause
The "encodingreference" in an encoding control section is used as "TAG".
Example
A1016E DEFINITIONS XER INSTRUCTIONS ::= BEGIN IA5 ::= IA5String ENCODING-CONTROL TAG BASE64 IA5 END
Error Message
"a1016e.asn", line 8 (A1016E): A1016E: The 'encodingreference' shall not be 'TAG'.
ENCODING-CONTROL TAG
Possible Solution
Make sure you do not use 'TAG' as "encodingreference".
A1017E
Message Format
A1017E: There shall be no qualifying information in the 'TargetList' for the 'instruction name' encoding instruction.
Message Cause
The encoding instruction does not allow the presence of qualifying information in its 'TargetList'. Qualifying information may be present only in the NAMESPACE, TEXT, and NAME encoding instructions.
Example
A1017-1 DEFINITIONS XER INSTRUCTIONS ::= BEGIN R ::= A1017-2.R ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS DECIMAL R:a END A1017-2 DEFINITIONS XER INSTRUCTIONS ::= BEGIN R ::= REAL END
Error Message
"a1017e.asn", line 7 (A1017-1): A1017E: There shall be no qualifying information in the 'TargetList' for the 'DECIMAL' encoding instruction.
Possible Solution
Make sure you do not use qualifying information (part of the target that starts from ":") for instructions that do not allow it.
A1018E
Message Format
A1018E: The qualifying information 'identifier' is invalid since there is no 'identifier' in the definition of 'Type'.
Message Cause
The identifier (not 'ALL') in the qualifying information of the target is not present in the type definition identified by the target.
Example
A1018E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
BS ::= BIT STRING { a(1), b(2) }
ENCODING-CONTROL XER
NAME BS:c AS UNCAPITALIZED
END
Error Message
"a1018e.asn", line 6 (A1018E): A1018E: The qualifying information 'c' is invalid since there is no 'c' in the definition of 'BS'.
NAME BS:c AS UNCAPITALIZED
Possible Solution
Make sure the identifier matches one of the identifiers used in the type definition.
A1019E
Message Format
A1019E: The qualifying information 'information' is invalid; valid qualifying information for 'Type' is 'information1'.
Message Cause
The specified qualifying information is not supported for the given type. The qualifying information must be 'ALL', an identifier in the type definition (for ENUMERATED types, INTEGER types with named values, and BIT STRING types with named bits), or "false" or "true" for BOOLEAN types.
Example
A1019E DEFINITIONS XER INSTRUCTIONS ::= BEGIN IA5 ::= IA5String ENCODING-CONTROL XER NAMESPACE IA5:c AS "urn:oid:2.1.5.2.0.1" END
Error Message
"a1019e.asn", line 6 (A1019E): A1019E: The qualifying information 'c' is invalid; valid qualifying information for 'IA5' is 'ALL'.
NAMESPACE IA5:c AS "urn:oid:2.1.5.2.0.1"
Possible Solution
Correct the qualifying information.
A1020E
Message Format
A1020E: The qualifying information is not expected for 'Type' if the encoding instruction being assigned is not the 'NAMESPACE' encoding instruction.
Message Cause
The target with qualifying information identified a restricted character string type, but the targeting encoding instruction is not NAMESPACE.
Example
A1020E DEFINITIONS XER INSTRUCTIONS ::= BEGIN A ::= IA5String ENCODING-CONTROL XER NAME A:ALL AS "Hi" END
Error Message
"a1020e.asn", line 6 (A1020E): A1020E: The qualifying information is not expected for 'A' when the encoding instruction being assigned is not the 'NAMESPACE' encoding instruction.
NAME A:ALL AS "Hi"
Possible Solution
You can either use NAMESPACE encoding instruction or remove the qualifying information.
A1021E
Message Format
A1021E: The 'TargetList' of the 'DEFAULT-FOR-EMPTY' encoding instruction does not identify a single target.
Message Cause
The "TargetList" of the DEFAULT-FOR-EMPTY encoding instruction contains more than one target.
Example
A1021E DEFINITIONS XER INSTRUCTIONS ::= BEGIN A ::= BIT STRING B ::= OCTET STRING ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS DEFAULT-FOR-EMPTY A, B AS '11'H END
Error Message
"a1021w.asn", line 8 (A1021E): A1021E: The 'TargetList' of the 'DEFAULT-FOR-EMPTY' encoding instruction does not identify a single target.
Possible Solution
When assigning the DEFAULT-FOR-EMPTY encoding instruction, make sure you have a single target in the TargetList.
A1022W
Message Format
A1022W: The 'TypeIdentification' does not identify any target. The encoding instruction assignment is being ignored.
Message Cause
The target of "TypeIdentification" is a type (not ALL) that is not defined.
Example
A1022W DEFINITIONS XER INSTRUCTIONS ::= BEGIN A ::= INTEGER ENCODING-CONTROL XER BASE64 B END
Error Message
"a1022w.asn", line 6 (A1022W): A1022W: The 'TypeIdentification' does not identify any target. The encoding instruction assignment is being ignored.
BASE64 B
Possible Solution
Make sure the "TargetList" identifies at least one target.
A1023W
Message Format
A1023W: The component 'identifier' is not textually present in the type 'Type'. The encoding instruction assignment is being ignored.
Message Cause
The "ComponentId" in the TypeIdentification is not textually present in the type definition. The compiler ignores such targets in accordance with X.693.
Example
A1023W DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S1 ::= SEQUENCE {
a IA5String
}
S2 ::= S1
ENCODING-CONTROL XER
BASE64 S2.a
END
Error Message
"a1023w.asn", line 8 (A1023W): A1023W: The component 'a' is not textually present in the type 'S2'. The encoding instruction assignment is being ignored.
BASE64 S2.a
Possible Solution
Apply the encoding instruction to the textually present component of the type. For the previous example, instead of S2.a, use S1.a.
A1024W
Message Format
A1024W: The 'identifier' is not a component of the identified type. The encoding instruction assignment is being ignored.
Message Cause
The identifier in the "IdentifiersInContext" target is not present in the identified type.
Example
A1024W DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
a IA5String
}
ENCODING-CONTROL XER
BASE64 b IN S
END
Error Message
"a1024w.asn", line 6 (A1024W): A1024W: The 'b' is not a component of the identified type.
BASE64 b IN S
Possible Solution
Make sure the identifier matches one of the component names.
A1025W
Message Format
A1025W: The type identified by the 'IdentifiersInContext' syntax is not a SEQUENCE, SET, CHOICE, SEQUENCE OF or SET OF. The target will be ignored.
Message Cause
The "Type" identified by the "TypeIdentification" within the "IdentifiersInContext" is not a SEQUENCE, SET, CHOICE, SEQUENCE OF, or SET OF type.
Example
A1025W DEFINITIONS XER INSTRUCTIONS ::= BEGIN BS ::= BIT STRING (CONTAINING IA5String) ENCODING-CONTROL XER NAMESPACE ALL IN BS AS "test.org" END
Error Message
"a1025w.asn", line 6 (A1025W): A1025W: The type identified by the 'IdentifiersInContext' syntax is not a SEQUENCE, SET, CHOICE, SEQUENCE or SET OF. The target will be ignored.
NAMESPACE ALL IN BS AS "test.org"
Possible Solution
Use ALL only with SET, SEQUENCE, CHOICE, SEQUENCE OF, or SET OF.
A1026E
Message Format
A1026E: Empty NCName value is illegal.
Message Cause
The compiler expects non-empty value for NCName since empty values do not conform to the production for "NCName" from the W3C XML Namespaces document.
Example
A1026E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE AS "www.oss.com" PREFIX "" END
Error Message
"a1026e.asn", line 7 (A1026E): A1026E: Empty NCName value is illegal.
NAMESPACE AS "www.oss.com" PREFIX ""
Possible Solution
Make sure the string value is non-empty.
A1027E
Message Format
A1027E: Invalid character found in (NCName|'NewName') value. Character code in hex is 'code'.
Message Cause
The error message is issued in the following cases:
- The "NewName" value specified within a TEXT encoding instruction contains a non-XML character.
- The "NCName" value contains an invalid character that is not permitted in accordance with the production for "NCName" from the W3C XML Namespaces document.
Example
A1027E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE AS "hello2" PREFIX "\" END
Error Message
"a1027e.asn", line 8 (A1027E): A1027E: Invalid character found in the NCName value. Character code in hex is '5C'.
Possible Solution
Remove the invalid characters.
A1028E
Message Format
A1028E: NCName shall not commence with characters that when uppercased are "XML".
Message Cause
The "NCName" starts with characters that are "XML".
Example
A1028E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE AS "www.oss.com" PREFIX "XmL" END
Error Message
"a1028e.asn", line 7 (A1028E): A1028E: NCName shall not commence with characters that when uppercased are "XML".
NAMESPACE AS "www.oss.com" PREFIX "XmL"
Possible Solution
Make sure you do not use "XML" at beginning of names.
A1028W
Message Format
A1028W: NCName shall not commence with characters that when uppercased are "XML".
Message Cause
The "NCName" starts with the uppercase characters "XML".
Example
A1028W DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE AS "www.oss.com" PREFIX "XmL" END
Error Message
"a1028w.asn", line 7 (A1028W): A1028W: NCName shall not commence with characters that when uppercased are "XML".
NAMESPACE AS "www.oss.com" PREFIX "XmL"
Possible Solution
Make sure you do not use "XML" at the beginning of names.
A1029E
Message Format
A1029E: Invalid URI value.
Message Cause
The value does not conform to the syntax of URI defined in IETF RFC 2396.
Example
A1029E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE AS "1:" END
Error Message
"a1029e.asn", line 8 (A1029E): A1029E: Invalid URI value.
Possible Solution
Make sure you use only correct URIs. Refer to RFC2396 for more details.
A1030E
Message Format
A1030E: The 'instruction' encoding instruction shall only be assigned in an encoding control section.
Message Cause
The error is issued if a GLOBAL-DEFAULTS encoding instruction is assigned in prefixed form.
Example
A1030E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= [GLOBAL-DEFAULTS MODIFIED-ENCODINGS] INTEGER END
Error Message
"a1030e.asn", line 3 (A1030E): A1030E: The 'GLOBAL-DEFAULTS' encoding instruction shall only be assigned in an encoding control section.
I ::= [GLOBAL-DEFAULTS MODIFIED-ENCODINGS] INTEGER
Possible Solution
Assign the encoding instruction only in the ENCODING-CONTROL section.
A1031E
Message Format
A1031E: The negating 'instruction' encoding instruction shall never be assigned.
Message Cause
The ASN.1 input contains a negation of GLOBAL-DEFAULTS encoding instruction.
Example
A1031E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER NOT GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE AS "http://www.aaa.com" END
Error Message
"a1031e.asn", line 6 (A1031E): A1031E: The negating 'GLOBAL-DEFAULTS' encoding instruction shall never be assigned.
NOT GLOBAL-DEFAULTS MODIFIED-ENCODINGS
Possible Solution
Make sure you do not use negating GLOBAL-DEFAULTS.
A1032E
Message Format
A1032E: The 'GLOBAL-DEFAULTS' encoding instruction shall not be preceded by any other encoding instructions except other 'GLOBAL-DEFAULTS' encoding instructions.
Message Cause
The GLOBAL-DEFAULTS encoding instruction are preceded by other encoding instructions.
Example
A1032E DEFINITIONS XER INSTRUCTIONS ::= BEGIN OS ::= OCTET STRING ENCODING-CONTROL XER BASE64 OS GLOBAL-DEFAULTS MODIFIED-ENCODINGS END
Error Message
"a1032e.asn", line 7 (A1032E): A1032E: The 'GLOBAL-DEFAULTS' encoding instruction shall not be preceded by any other encoding instructions except other 'GLOBAL-DEFAULTS' encoding instructions.
Possible Solution
Place GLOBAL-DEFAULTS instructions before other instructions.
A1033E
Message Format
A1033E: A duplicate 'encodingreference' encoding control section was found.
Message Cause
The ASN.1 module contains at least two encoding control sections with the same encoding reference.
Example
A1033E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
a INTEGER
}
ENCODING-CONTROL XER
NAMESPACE ALL AS "www.oss.com"
ENCODING-CONTROL XER
NOT NAMESPACE ALL
END
Error Message
"a1033e.asn", line 7 (A1033E): A1033E: A duplicate XER encoding control section was found.
Possible Solution
Make sure you have only one ENCODING-CONTROL section. You can combine the content of two or more ENCODING-CONTROL sections.
A1034E
Message Format
A1034E: The 'ModuleAndTypeReference' shall not be used unless the typereference consists of the same characters as one of the EXTENDED-XER keywords. Its use for 'Type' is illegal.
Message Cause
The 'modulereference' shall prefix the 'typereference' if and only if 'typereference' consists of the same characters as one of the EXTENDED-XER keywords.
Example
A1034E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
a INTEGER
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
UNTAGGED A1034E.S.a
END
Error Message
"a1034e.asn", line 7 (A1034E): A1034E: The 'ModuleAndTypeReference' shall not be used unless the typereference consists of the same characters as one of the EXTENDED-XER keywords. Its use for 'S' is illegal.
UNTAGGED A1034E.S.a
Possible Solution
Remove the module reference from the encoding instruction.
A1035E
Message Format
A1035E: The 'ModuleAndTypeReference' shall be used to denote the typereference 'Type' since it consists of the same characters as one of the EXTENDED-XER keywords.
Message Cause
You must explicitly add 'modulereference' before 'typereference' if the latter consists of the same characters as the EXTENDED-XER keywords.
Example
A1035E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
NAME ::= SEQUENCE {
a INTEGER
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
UNTAGGED NAME.a
END
Error Message
"a1035e.asn", line 7 (A1035E): A1035E: The 'ModuleAndTypeReference' shall be used to denote the typereference 'NAME' since it consists of the same characters as one of the EXTENDED-XER keywords.
UNTAGGED NAME.a
Possible Solution
Add a module reference to the type identification.
A1036E
Message Format
A1036E: 'ALL' is used as a 'ComponentId', it shall not be followed by 'QualifyingInformation'.
Message Cause
The ASN.1 standard states that qualifying information shall not be present if TypeIndentification is used with ComponentId which is ALL.
Example
A1036E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
b BIT STRING { one(1), two(2) }
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
NAMESPACE BS.ALL:one AS "www.oss.com"
END
Error Message
"a1036e.asn", line 7 (A1036E): A1022W: The 'TypeIdentification' does not identify any target. The encoding instruction assignment is being ignored.
NAMESPACE BS.ALL:one AS "www.oss.com"
"a1036e.asn", line 7 (A1036E): A1036E: 'ALL' is used as a 'ComponentId', it shall not be followed by 'QualifyingInformation'.
NAMESPACE BS.ALL:one AS "www.oss.com"
Possible Solution
Remove the qualifying information.
A1037E
Message Format
A1037E: There is no negating encoding instruction for 'ELEMENT'.
Message Cause
The ELEMENT encoding instruction has no negating form. To remove an ELEMENT encoding instruction, a subsequent UNTAGGED encoding instruction must be used.
Example
A1037E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= [NOT ELEMENT] SEQUENCE {
a INTEGER
}
END
Error Message
"a1037e.asn", line 3 (A1037E): A1037E: There is no negating encoding instruction for 'ELEMENT'.
S ::= [NOT ELEMENT] SEQUENCE {a INTEGER}
Possible Solution
Replace NOT ELEMENT instruction with UNTAGGED instruction.
A1038E
Message Format
A1038E: The 'TEXT' encoding instruction shall only be assigned with qualifying information identifying one or more of the identifiers used in the definition of the type.
Message Cause
The "TEXT" encoding instruction is specified without qualifying information: either the encoding instruction is assigned in prefixed form or it is assigned in targeted form where TargetList contains Target without qualifying information.
Example
A1038E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
I ::= INTEGER {one(1), two(2)}
ENCODING-CONTROL XER
TEXT I AS "three"
END
Error Message
"a1038e.asn", line 6 (A1038E): A1038E: The 'TEXT' encoding instruction shall only be assigned with qualifying information identifying one or more of the identifiers used in the definition of the type.
TEXT I AS "three"
Possible Solution
Add qualifying information (possibly "ALL") to the TargetList.
A1039E
Message Format
A1039E: Illegal character string value is used in a 'PI-OR-COMMENT' encoding instruction. The value must be the concatenation of one or more character strings each of which conforms to the syntax of an XML Processing Instruction or to the syntax of an XML Comment.
Message Cause
The restricted character string value specified for a "PI-OR-COMMENT" instruction does not match the required format.
Example
A1039E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER PI-OR-COMMENT I AS "<?xm2?><!--->" BEFORE-TAG END
Error Message
"a1039e.asn", line 6 (A1039E): A1039E: Illegal character string value is used in a 'PI-OR-COMMENT' encoding instruction. The value must be the concatenation of one or more character strings each of which conforms to the syntax of an XML Processing Instruction or to the syntax of an XML Comment.
Possible Solution
Correct the PI-OR-COMMENT instruction.
A1040E
Message Format
A1040E: 'NewName' shall not be used in the 'instruction' encoding instruction since its 'TargetList' contains 'Targets' where 'QualifyingInformation' is 'ALL'.
Message Cause
NewName is specified in a NAME and TEXT encoding instruction assigned in targeted form and qualifying information in the encoding instruction's target list is ALL.
Example
A1040E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
BS ::= BIT STRING {a(1), b(2)}
ENCODING-CONTROL XER
NAME BS:ALL AS "new"
END
Error Message
"a1040e.asn", line 5 (A1040E): A1040E: 'NewName' shall not be used in the 'NAME' encoding instruction since its 'TargetList' contains 'Targets' where 'QualifyingInformation' is 'ALL'.
Possible Solution
Replace NewName with CaseKeyword (CAPITALIZED).
A1041E
Message Format
A1041E: A "URIList" for the 'instruction' encoding instruction shall not contain more than one occurrence of 'ABSENT'.
Message Cause
The error is issued if ABSENT occurs in a URI list of an ANY-ATTRIBUTES or ANY-ELEMENT encoding instructions more than once.
Example
A1041E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE { a SET OF UTF8String (CONSTRAINED BY {}) }
ENCODING-CONTROL XER
ANY-ATTRIBUTES S FROM ABSENT ABSENT
END
Error Message
"a1041e.asn", line 6 (A1041E): A1041E: A 'URIList' for the 'ANY-ATTRIBUTES' encoding instruction shall not contain more than one occurrence of 'ABSENT'.
ANY-ATTRIBUTES S FROM ABSENT ABSENT
Possible Solution
Make sure that ABSENT occurs only once.
C1042E
Message Format
C1042E: The 'GLOBAL-DEFAULTS CONTROL-NAMESPACE' in the modules 'mod1' and 'mod2' define different control namespaces.
Message Cause
The error is issued if there are GLOBAL-DEFAULTS CONTROL-NAMESPACE encoding instructions in the ASN.1 specification that define different control namespaces.
NOTE: Currently this restriction is not present in X693 Amd.1 and it is considered an OSS-specific restriction.
Example
C1042E-1 DEFINITIONS XER INSTRUCTIONS ::= BEGIN I1 ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS CONTROL-NAMESPACE "www.fff.com/XSD" PREFIX "ff" END C1042E-2 DEFINITIONS XER INSTRUCTIONS ::= BEGIN I2 ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS CONTROL-NAMESPACE "www.eee.com/XSD" PREFIX "ee" END
Error Message
"a1041e.asn", line 6 (A1041E): A1041E: A 'URIList' for the 'ANY-ATTRIBUTES' encoding instruction shall not contain more than one occurrence of 'ABSENT'.C1042E: The 'GLOBAL-DEFAULTS CONTROL-NAMESPACE' in the modules 'C1042E-1' and 'C1042E-2' define different control namespaces.
Possible Solution
Use the same control namespace throughout all input ASN.1 modules.
A1043E
Message Format
A1043E: 'Type' is not among the permitted types for the 'instruction' encoding instruction (line x).
Message Cause
The error is issued if the type is not supported for the given final encoding instruction.
Example
A1043E DEFINITIONS XER INSTRUCTIONS ::= BEGIN I ::= [BASE64] INTEGER END
Error Message
"a1043e.asn", line 3 (A1043E): A1043E: 'I' is not among the permitted types for the 'BASE64' encoding instruction.
Possible Solution
Certain encoding instructions may be applied only to particular ASN.1 types. Make sure you do not apply them to other types. Refer to X.693 standard for more details.
A1044E
Message Format
A1044E: 'Type' is not constrained to constraint specification.
Message Cause
The error is issued if:
- UTF8String with ANY-ELEMENT is not constrained so as to conform to ANY-ATTRIBUTES format. A SEQUENCE OF or SET OF type with ANY-ATTRIBUTES is not constrained to conform to ANY-ATTRIBUTES format.
- The SEQUENCE with EMBED-VALUES is not constrained so as to conform to ITU-T Rec. X.693 | ISO/IEC 8825-4, clause 25.
- The SEQUENCE OF type for supporting USE-ORDER is not constrained so as to conform to ITU-T Rec. X.693 | ISO/IEC 8825-4, clause 36.
Example
A1044E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {a [ANY-ATTRIBUTES] SET OF UTF8String }
END
Error Message
"a1043e.asn", line 3 (A1043E): A1043E: 'I' is not among the permitted types for the 'BASE64' encoding instruction.
Possible Solution
Add constraints to user-defined types (CONSTRAINED BY {}).
A1045E
Message Format
A1045E: 'Type' with 'instruction' encoding instruction applied (line x) shall only be used as a component of a SEQUENCE or SET type.
Message Cause
The type with the given encoding instruction is not a component of a SET or SEQUENCE type. The current encoding instruction may be applied only to a component of SEQUENCE or SET.
Example
A1045E DEFINITIONS XER INSTRUCTIONS ::= BEGIN S ::= SET OF a [ATTRIBUTE] INTEGER END
Error Message
"a1045e.asn", line 3 (A1045E): A1045E: 'S.*' with 'ATTRIBUTE' encoding instruction applied shall only be used as a component of a SEQUENCE or SET type.
Possible Solution
Remove the encoding instruction or replace the enclosing type with a SET or a SEQUENCE.
A1046E
Message Format
A1046E: The 'instruction1' encoding instruction (line x) applied to 'Type' conflicts with 'instruction2' encoding instruction (line y).
Message Cause
The combination of the two given final encoding instructions applied to the same type is not permitted according to X.693.
Example
A1046E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
CH ::= SEQUENCE { a INTEGER }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
UNTAGGED CH.a
PI-OR-COMMENT CH.a AS "<?P?>" BEFORE-TAG
END
Error Message
"a1046e.asn", line 3 (A1046E): A1046E: The 'PI-OR-COMMENT' encoding instruction
(line 8) applied to 'CH.a' conflicts with 'UNTAGGED' encoding instruction (line 7).
Possible Solution
Remove one of the conflicting encoding instructions.
A1047E
Message Format
A1047E: The 'instruction' encoding instruction (line x) shall not be assigned to 'Type' unless a 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Message Cause
The encoding instruction can be assigned only when GLOBAL-DEFAULTS MODIFIED-ENCODINGS is present.
Example
A1047E DEFINITIONS XER INSTRUCTIONS ::= BEGIN R ::= REAL ENCODING-CONTROL XER DECIMAL R END
Error Message
"a1047e.asn", line 3 (A1047E): A1047E: The 'DECIMAL' encoding instruction (line 6) shall not be assigned to 'R' unless a 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Possible Solution
Add GLOBAL-DEFAULTS MODIFIED-ENCODINGS into the encoding control section.
A1048E
Message Format
A1048E: The 'DEFAULT-FOR-EMPTY' encoding instruction (line x) is being applied to the component 'identifier' of a [SEQUENCE|SET] 'Type' with a DEFAULT value.
Message Cause
DEFAULT-FOR-EMPTY encoding instruction is not supported for a component of a SET or SEQUENCE type with a DEFAULT value.
Example
A1048E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE { a [DEFAULT-FOR-EMPTY AS 121] INTEGER DEFAULT 212 }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1048e.asn", line 3 (A1048E): A1048E: The 'DEFAULT-FOR-EMPTY' encoding instruction is being applied to the component 'a' of a SEQUENCE 'S' with a DEFAULT value.
Possible Solution
Remove DEFAULT ASN.1 keyword or DEFAULT-FOR-EMPTY encoding instruction.
A1049W
Message Format
A1049W: The 'DEFAULT-FOR-EMPTY' encoding instruction (line x) will be ignored since it is applied to the component of 'Type' that is type description with 'instruction' encoding instruction.
A1049W: The 'DEFAULT-FOR-EMPTY' encoding instruction applied to the type 'Type1' (line x) will be ignored when this type is used as a component of 'Type' that is type description with 'instruction' encoding instruction.
Message Cause
The DEFAULT-FOR-EMPTY will be ignored if it is applied to a character-encodable type which has an enclosing type that is a SEQUENCE OF or SET OF type with a final LIST encoding instruction, or a CHOICE type with a final USE-UNION encoding instruction.
Example
A1049W DEFINITIONS XER INSTRUCTIONS ::= BEGIN
I ::= [DEFAULT-FOR-EMPTY AS 10] INTEGER
S ::= SEQUENCE { l [LIST] SEQUENCE OF I }
L ::= [LIST] SET OF [DEFAULT-FOR-EMPTY AS 11] INTEGER
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1049w.asn", line 5 (A1049W): A1049W: The DEFAULT-FOR-EMPTY encoding instruction applied to the type 'I' (line 3) will be ignored when this type is used as a component of 'S.l' that is SEQUENCE OF with 'LIST' encoding instruction.
"a1049w.asn", line 7 (A1049W): A1049W: The 'DEFAULT-FOR-EMPTY' encoding instruction will be ignored since it is applied to the component of 'L' that is SET OF with 'LIST' encoding instruction.
Possible Solution
Make sure you do not use DEFAULT-FOR-EMPTY encoding instruction or apply it selectively to the components not used within types with LIST and USE-UNION encoding instructions.
A1050E
Message Format
A1050E: The qualifying information shall not be used for the 'NAME' encoding instruction (line x) applied to 'Type' when a 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Message Cause
NAME encoding instructions with qualifying information cannot be applied when GLOBAL-DEFAULTS MODIFIED-ENCODINGS is present.
Example
A1050E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
BS ::= BIT STRING { one(1), two(2) }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
NAME BS:ALL AS CAPITALIZED
END
Error Message
"a1050e.asn", line 3 (A1050E): A1050E: The qualifying information shall not be used for the 'NAME' encoding instruction (line 7) applied to 'BS' when a 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Possible Solution
You can either remove GLOBAL-DEFAULTS MODIFIED-ENCODINGS or remove the qualifying information from NAME encoding instruction.
A1051E
Message Format
A1051E: The final character strings used for the values 'value1' and 'value1' of 'Type' in the 'instruction' encoding instruction are not distinct.
Message Cause
The final character strings used for the values of the type to which a TEXT or NAME encoding instruction (with qualifying information) is applied are not distinct.
Example
A1051E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
A1 ::= BIT STRING { a(1), b(2)}
ENCODING-CONTROL XER
TEXT A1:a AS "name1"
TEXT A1:b AS "name1"
END
Error Message
"a1051e.asn", line 3 (A1051E): A1051E: The final character strings used in the 'TEXT' encoding instruction for the values 'b' and 'a' of 'A1' are not distinct.
Possible Solution
Make sure all TEXT values of the type are distinct.
A1052E
Message Format
A1052E: 'Type' shall have only one component with 'instruction' encoding instruction.
Message Cause
The ANY-ATTRIBUTES encoding instruction is assigned to more than one component of a SEQUENCE or SET type.
Example
A1052E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
a [ANY-ATTRIBUTES FROM "http://a.com"]
SEQUENCE (CONSTRAINED BY {}) OF UTF8String,
b [ANY-ATTRIBUTES EXCEPT "http://a.com"]
SEQUENCE (CONSTRAINED BY {}) OF UTF8String
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1052e.asn", line 6 (A1052E): A1052E: 'S' shall have only one component with 'ANY-ATTRIBUTES' encoding instruction.
Possible Solution
Make sure only one field of the type contains ANY-ATTRIBUTES encoding instruction.
A1053E
Message Format
A1053E: The component 'identifier' of 'Type' with an assigned 'instruction' encoding instruction (line x) shall not be an extension addition and marked OPTIONAL or DEFAULT.
Message Cause
The error is issued if:
- The ANY-ATTRIBUTES encoding instruction is assigned to a component of the SEQUENCE or SET type which is OPTIONAL or has a DEFAULT value.
- The UNTAGGED encoding instruction is assigned to a character-encodable component of the SEQUENCE or SET type which is an extension addition, OPTIONAL or has a DEFAULT value.
Example
A1053E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
a [ANY-ATTRIBUTES] SEQUENCE (CONSTRAINED BY {}) OF UTF8String OPTIONAL
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1053e.asn", line 4 (A1053E): A1053E: The component 'a' of 'S' with an assigned 'ANY-ATTRIBUTES' encoding instruction shall not be marked OPTIONAL or DEFAULT.
Possible Solution
Make sure the component supporting the ANY-ATTRIBUTES encoding instruction is non-optional and non-DEFAULT.
A1054E
Message Format
A1054E: All components of the SEQUENCE 'Type' except field 'identifier' of this type shall have a final 'ATTRIBUTE' or 'ANY-ATTRIBUTES' encoding instruction.
Message Cause
A SEQUENCE or SET type with an UNTAGGED character-encodable component contains one or more non-UNTAGGED components that have no final ATTRIBUTE or ANY-ATTRIBUTES encoding instruction.
Example
A1054E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
f1 [UNTAGGED] INTEGER,
f2 SET OF BOOLEAN
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1054e.asn", line 3 (A1054E): A1054E: All components of the SEQUENCE 'S' except field 'f1' shall have a final 'ATTRIBUTE' or 'ANY-ATTRIBUTES' encoding instruction.
Possible Solution
You can either apply ATTRIBUTE or ANY-ATTRIBUTES instructions to remaining fields of the type or remove such fields completely.
A1055E
Message Format
A1055E: The component of 'Type' with a 'LIST' encoding instruction shall be a character encodable type.
Message Cause
The component of a SEQUENCE OF or SET OF type with a final LIST encoding instruction is not a character-encodable type.
Example
A1055E DEFINITIONS XER INSTRUCTIONS ::= BEGIN S ::= [LIST] SET OF BOOLEAN END
Error Message
"a1055e.asn", line 3 (A1055E): A1055E: The component of 'S' with a 'LIST' encoding instruction shall be a character-encodable type.
Possible Solution
Make sure the element of the LIST is a character encodable type (GLOBAL-DEFAULTS MODIFIED-ENCODINGS).
A1056E
Message Format
A1056E: The [first|second] component of 'Type' is not constrained to constraint specification.
Message Cause
A SEQUENCE type with a USE-QNAME encoding instruction contains two components, one of which is not constrained to a correct value (a correct URI for first component and a correct NCName for the second one).
NOTE: To satisfy the required restrictions, each component of the SEQUENCE with USE-QNAME must have a user-defined constraint applied.
Example
A1056E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= [USE-QNAME] SEQUENCE {
a UTF8String OPTIONAL,
b UTF8String (CONSTRAINED BY {})
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1056e.asn", line 3 (A1056E): A1056E: The first component of 'S' is not constrained to represent an URI.
Possible Solution
Add a user-defined constraint to the field (CONSTRAINED BY {}).
A1057E
Message Format
A1057E: The 'instruction1' encoding instruction (line x) applied to the type 'Type' conflicts with 'instruction2' encoding instruction (line y) applied to the [alternative|field] 'identifier' of this type.
Message Cause
One of the two encoding instructions is applied to a type and the other is applied to an element or component of this type, and therefore are in conflict (for example, USE-TYPE is applied to a CHOICE type and UNTAGGED is applied to one of alternatives of the CHOICE type).
Example
A1057E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
A ::= [USE-TYPE] CHOICE {
a [UNTAGGED] SET OF INTEGER
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1057e.asn", line 3 (A1057E): A1057E: The 'USE-TYPE' encoding instruction applied to the type 'A' conflicts with 'UNTAGGED' encoding instruction applied to the alternative 'a' of this type.
Possible Solution
Remove one of the conflicting instructions either manually or by assigning of negating instruction from the same category.
A1058W
Message Format
A1058W: The 'instruction' encoding instruction (line x) applied to 'Type' will be ignored since cause for ignoring.
Message Cause
The USE-NUMBER encoding instruction is applied to a type that is not an enumeration.
Example
A1058W DEFINITIONS XER INSTRUCTIONS ::= BEGIN IA5 ::= [USE-NUMBER] IA5String END
Error Message
"a1058w.asn", line 3 (A1058W): A1058W: The 'USE-NUMBER' encoding instruction applied to 'IA5' will be ignored since this type is not an enumerated type.
Possible Solution
Make sure you do not apply the USE-NUMBER encoding instruction to non-ENUMERATED types.
A1059E
Message Format
A1059E: There is no one-to-one correspondence between ENUMERATED values and the components (in the optional component) of the sequence type 'Type' with a final 'USE-ORDER' encoding instruction (line x).
Message Cause
A SEQUENCE type with a final USE-ORDER encoding instruction does not contain a one-to-one correspondence between the values of the ENUMERATED component that supports USE-ORDER and:
- the components of the SEQUENCE following the components that support final USE-ORDER and EMBED-VALUES (if present) - if there is no final USE-NIL on the SEQUENCE type.
- the components of the the optional element for supporting final USE-NIL (a SEQUENCE type) of the SEQUENCE with final USE-ORDER - if there is final USE-NIL along with final USE-ORDER on the SEQUENCE type.
The ENUMERATED type must contain identifiers for the enumerations that correspond to (and are in the same textual order as) the identifiers of the components of the corresponding SEQUENCE type.
Example
A1059E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= [USE-ORDER] SEQUENCE {
order SEQUENCE (CONSTRAINED BY {}) OF ENUMERATED {a, b},
b BOOLEAN
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1059e.asn", line 3 (A1059E): A1059E: There is no one-to-one correspondence between ENUMERATED values and the components of the sequence type 'S' with a final USE-ORDER encoding instruction.
Possible Solution
Make sure you use an enumeration value for each field of the SEQUENCE and you use a field for each enumeration value. Add the missing fields or enumeration values, remove them if they are unnecessary.
A1060E
Message Format
A1060E: The sequence type 'Type' with a 'USE-NIL' encoding instruction (line x) must have an optional component that supports this encoding instruction.
Message Cause
USE-NIL must be applied to SEQUENCE type with a single OPTIONAL component that does not have an ATTRIBUTE or ANY-ATTRIBUTES encoding instruction and is not the SEQUENCE OF component that supports a USE-ORDER or EMBED-VALUES encoding instruction applied to the same SEQUENCE type.
Example
A1060E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= [USE-NIL] SEQUENCE { }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1060e.asn", line 3 (A1060E): A1060E: The sequence type 'S' with a USE-NIL encoding instruction must have an optional component that supports this encoding instruction.
Possible Solution
Add an OPTIONAL field to the SEQUENCE type.
A1061E
Message Format
A1061E: The optional component 'identifier' of the sequence type 'Type' with a final 'USE-NIL' encoding instruction (line lineno) shall have a final 'ATTRIBUTE' encoding instruction since there is already an OPTIONAL component without an 'ATTRIBUTE' or 'ANY-ATTRIBUTES' encoding instruction.
Message Cause
All components of the type with USE-NIL encoding instruction except the optional component that supports USE-NIL and the SEQUENCE OF components that support USE-ORDER or EMBED-VALUES encoding instruction must have a final ATTRIBUTE encoding instruction.
Example
A1061E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= [USE-NIL] SEQUENCE {
a INTEGER OPTIONAL,
b BOOLEAN OPTIONAL
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1061e.asn", line 3 (A1061E): A1061E: The optional component 'b' of the sequence type 'S' with a final 'USE-NIL' encoding instruction shall have a final 'ATTRIBUTE' encoding instruction since there is already an optional component without an 'ATTRIBUTE' or 'ANY-ATTRIBUTES' encoding instruction.
Possible Solution
Add the ATTRIBUTE encoding instructions.
A1062E
Message Format
A1062E: In a sequence type 'Type' with final 'EMBED-VALUES' (line x) and 'USE-NIL' (line y) encoding instructions, the optional component 'identifier' supporting 'USE-NIL' shall not be a character-encodable type.
Message Cause
The optional component (of the SEQUENCE with EMBED-VALUES and USE-NIL encoding instructions) supporting the USE-NIL encoding instruction must not be a character-encodable type.
Example
A1062E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= [USE-NIL][EMBED-VALUES] SEQUENCE {
z SEQUENCE OF UTF8String,
a INTEGER OPTIONAL
} (CONSTRAINED BY {})
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1062e.asn", line 5 (A1062E): A1062E: In a sequence type 'S' with final 'EMBED-VALUES' and 'USE-NIL' encoding instructions, the optional component 'a' supporting 'USE-NIL' shall not be a character-encodable type.
Possible Solution
Replace the type of the OPTIONAL field with a non-character encodable type.
A1063E
Message Format
A1063E: In a sequence type 'Type' with final 'DEFAULT-FOR-EMPTY' (line x) and 'USE-NIL' (line y) encoding instructions, optional component supporting 'USE-NIL' shall be a character-encodable type.
Message Cause
The optional component of a SEQUENCE with DEFAULT-FOR-EMPTY and USE-NIL encoding instructions (but without an EMBED-VALUES encoding instruction) must be a character-encodable type.
Example
A1063E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
T ::= [DEFAULT-FOR-EMPTY AS {""}][USE-NIL] SEQUENCE {
a SEQUENCE OF UTF8String OPTIONAL
} (CONSTRAINED BY {})
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1063e.asn", line 3 (A1063E): A1063E: In a sequence type 'T' with final 'DEFAULT-FOR-EMPTY' and 'USE-NIL' encoding instructions, optional component 'a' supporting 'USE-NIL' shall be a character-encodable type.
Possible Solution
Replace the type of the OPTIONAL field with a character encodable type.
A1064E
Message Format
A1064E: 'Type' has [a|an] 'instruction' encoding instruction (line x) but is not a character-encodable type.
Message Cause
The type with a final encoding instruction is not a character-encodable type. The encoding instruction (ATTRIBUTE) must be applied only to a character-encodable type.
Example
A1064E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
A ::= [ATTRIBUTE] SEQUENCE {
a INTEGER }
END
Error Message
"a1064e.asn", line 3 (A1064E): A1064E: 'A' has an 'ATTRIBUTE' encoding instruction but is not a character-encodable type.
Possible Solution
Make sure the type with a final encoding instruction is a character encodable type (GLOBAL-DEFAULTS MODIFIED-ENCODINGS).
A1065E
Message Format
A1065E: 'Type' with 'WHITESPACE' encoding instruction applied (line x) shall be constrained to contain no HORIZONTAL TABULATION, LINE FEED, and CARRIAGE RETURN characters.
Message Cause
The type with a final WHITESPACE encoding instruction is not constrained. Its abstract values do not contain HORIZONTAL TABULATION, LINE FEED, and CARRIAGE RETURN characters.
Example
A1065E DEFINITIONS XER INSTRUCTIONS ::= BEGIN A ::= [WHITESPACE REPLACE] IA5String END
Error Message
"a1065e.asn", line 3 (A1065E): A1065E: 'A' with 'WHITESPACE' encoding instruction applied shall be constrained to contain no HORIZONTAL TABULATION, LINE FEED, and CARRIAGE RETURN characters.
Possible Solution
Add a constraint that excludes HORIZONTAL TABULATION, LINE FEED, and CARRIAGE RETURN characters for the string type, such as a PermittedAlphabet of user-defined constraint.
C1066E
Message Format
C1066E: The type of the field 'identifier' of 'Type' has a contents constraint applied. Such a type is not supported by the OSS runtime as an alternative of a CHOICE with the 'USE-UNION' encoding instruction.
Message Cause
As an OSS specific restriction, character-encodable types with ContentsConstraint are not permitted as alternatives of a CHOICE type with USE-UNION.
Example
C1066E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
enc-PER-Aligned OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) asn1(1) packed-encoding(3) basic(0) aligned(0)}
T ::= [USE-UNION] CHOICE {
f1 OCTET STRING (CONTAINING INTEGER ENCODED BY enc-PER-Aligned),
f2 BIT STRING }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1066e.asn", line 7 (C1066E): C1066E: The type of the field 'f1' of 'T' has a contents constraint applied. Such a type is not supported by the OSS runtime as an alternative of a CHOICE with the 'USE-UNION' encoding instruction.
Possible Solution
You can either remove the contents constraint from the component type or remove USE-UNION from the CHOICE type.
A1067E
Message Format
A1067E: The content model for 'Type' is non-deterministic: reason.
Message Cause
An ASN.1 specification is illegal unless all abstract values, a decoder can determine unambiguously (using only the name of the XML tag and the contents of any previous XML element) the ASN.1 component that an XML element is associated with.
Example
A1067E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SET OF [UNTAGGED] SET {
a INTEGER,
b BOOLEAN OPTIONAL }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1067e.asn", line 3 (A1067E): A1067E: The content model for 'S' is non-deterministic: there are two elements from the same namespace, 'ABSENT' with the same local name, 'b' (optionality determination requirement is violated).
Possible Solution
Make sure there is no determinism violation: it must be possible to determine the component to be decoded by the input XML tag name. For the example above, replace the SET OF component from SET with SEQUENCE.
C1068W
Message Format
C1068W: The content model for 'Type' may be non-deterministic.
Message Cause
The determinism requirement is violated but the compiler was unable to make a final determination due to presence of a Presence Constraint or User Constraint (depending on the constraint, the specification might be legal).
Example
C1068W DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
A ::= SEQUENCE {
a INTEGER OPTIONAL,
b INTEGER OPTIONAL,
c INTEGER
}
B ::= CHOICE {
x [UNTAGGED] A (WITH COMPONENTS {a PRESENT}),
y [UNTAGGED] A (WITH COMPONENTS {b PRESENT})
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1068w.asn", line 8 (C1068W): C1068W: The content model for 'B' may be non-deterministic.
Possible Solution
Although the compiler accepts such notations, it is not recommended to use Presence Constraint or User Constraint when a determinism violation could occur, and runtime will work slower. Disambiguate the specification by removing UNTAGGED, renaming the fields etc.
C1069E
Message Format
C1069E: The extensible type 'Type' shall not have a final 'UNTAGGED' encoding instruction.
Message Cause
The final UNTAGGED encoding instruction on an extensible type is not allowed because it might violate the determinism rule.
Example
C1069E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
Seq1 ::= [UNTAGGED] SEQUENCE {
x INTEGER,
... }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1069e.asn", line 3 (C1069E): C1069E: The extensible type 'Seq1' shall not have a final 'UNTAGGED' encoding instruction.
Possible Solution
Remove the UNTAGGED encoding instruction or the extensibility marker for the type.
C1070E
Message Format
C1070E: A component 'identifier' of the type 'Type' that supports the 'instruction' encoding instruction must not have any directives that change its representation in the target language.
Message Cause
The OSS EXTENDED-XER runtime supports only default representations for the utility fields of the following encoding instructions:
- ANY-ATTRIBUTES SEQUENCE OF UTF8String
- ANY-ELEMENT UTF8String
- ENBED-VALUES SEQUENCE OF UTF8String
- USE-ORDER SEQUENCE OF ENUMERATED
- USE-QNAME pair of UTF8String fields
Example
C1070E DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
S ::= SEQUENCE {
a [ANY-ELEMENT] UTF8String (CONSTRAINED BY {}) --<VARYING>--}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1070e.asn", line 4 (C1070E): C1070E: A component 'a' of the type 'S' that supports the 'ANY-ELEMENT' encoding instruction must not have any directives that change its representation in the target language other than OSS.UNBOUNDED directive.
Possible Solution
Remove the OSS directive by replacing the C representation of the utility field with an encoding instruction.
C1071S
Message Format
C1071S: COMPILER ERROR #55 (location).
Message Cause
The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.
Next Action
Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.
C1072E
Message Format
C1072E: The content model for 'Type' may be non-deterministic.
Message Cause
Although the determination requirement might be violated, the ASN.1 compiler could not take any action due to a Presence Constraint or User Constraint (depending on the constraint, the specification might be legal). However, as an implementation restriction, the runtime does not support such possible determinism violations for the types with final USE-ORDER and EMBED-VALUES encoding instructions.
Example
C1072E DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
T ::= [USE-ORDER] SEQUENCE {
order SEQUENCE (CONSTRAINED BY {}) OF ENUMERATED { a, x, c },
a [NAME AS "x"] INTEGER,
x INTEGER,
c [NAME AS "a"] INTEGER
} (CONSTRAINED BY {})
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1072e.asn", line 3 (C1072E): C1072E: The content model for 'T' may be non-deterministic: [USE-ORDER] SEQUENCE contains two elements from the same namespace 'ABSENT' with the same local name 'x'.
Possible Solution
It is not recommended to use PresenceConstraint or User Constraint when there might be a determinism violation without the constraint applied and when USE-ORDER or EMBED-VALUES is enabled. Disambiguate the specification by removing UNTAGGED, renaming the fields etc.
C1073S
Message Format
C1073S: The command-line option '-encoding rule' was specified, but you
are not licensed to use 'ENCODING RULE'. Please contact OSS Nokalva,
Inc. for more information.
Message Cause
You are using 8.0B or an earlier version of the ASN.1/C compiler and there is no license in your ossinfo file for using the encoding rule specified in the ASN.1 compiler command line.
Example
asn1 -per foo.asn
Error Message
C1073S: You specified the -per command- line option, but are not
licensed to use PER. Please contact OSS Nokalva, Inc. for more
information.
Possible Solution
Remove the option or contact Sales ‹info@oss.com› for information about renewing your license or obtaining updated software.
A1074E
Message Format
A1074E: The 'UNIQUE' keyword shall not be present since the field 'name of field' is not a fixed-type value field.
Message Cause
The "UNIQUE" keyword is applied to a non-fixed-type value field in an information object class.
Example
Module-M DEFINITIONS ::= BEGIN
CONTENT-RULE ::= CLASS {
&structuralClass OBJECT-CLASS UNIQUE }
WITH SYNTAX {
&structuralClass }
OBJECT-CLASS ::= CLASS {
&numb INTEGER }
WITH SYNTAX {&numb}
END
Error Message
"a1074e.asn", line 5 (Module-M): A1074E: The 'UNIQUE' keyword shall not be present since the field '&structuralClass' is not a fixed-type value field.
Possible Solution
Make sure you do not apply the UNIQUE keyword to a non-fixed-type value field in an information object class.
A1075E
Message Format
A1075E: The final character string used for the value 'value' of 'Type' in the 'TEXT' encoding instruction conflicts with the permitted encodings of another value of the INTEGER/BIT STRING/BOOLEAN type.
Message Cause
The character string assigned to the value of the type in the TEXT encoding instruction conflicts with a valid EXTENDED-XER encoding for this type (it can be an INTEGER type with named numbers, a BIT STRING type with named bits, or a BOOLEAN type). Such character strings are not allowed.
Example
A1075E DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
I ::= INTEGER {one(1), two(2)}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
TEXT I:one AS " 1 "
END
Error Message
"a1075e.asn", line 7 (A1075E): A1075E: The final character string used for the value 'one' of 'I' in the 'TEXT' encoding instruction conflicts with the permitted encodings of another value of the INTEGER type.
Possible Solution
Replace the character string used for value one with one that is not a valid EXTENDED-XER encoding for the INTEGER type.
A1076E
Message Format
A1076E: A final 'TEXT' encoding instruction is assigned to the value 'value1' of 'Type' but no final 'TEXT' encoding instruction is assigned to the value 'value2' of this type (line x). This encoding instruction shall either be assigned to all values of the type or to none of them, unless a 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Message Cause
This error is issued in the absence of GLOBAL-DEFAULTS MODIFIED-ENCODINGS when a final TEXT encoding instruction is assigned to certain values of the type but is not assigned to other values of the same type. If a value of a type has a final TEXT encoding instruction, all values of the type must have a final TEXT encoding instruction, unless a GLOBAL-DEFAULTS MODIFIED-ENCODINGS encoding instruction is present.
Example
A1076E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
BS ::= BIT STRING {bit1(1), bit2(2), bit3(2)}
ENCODING-CONTROL XER
TEXT BS:bit1, BS:bit2
END
Error Message
"a1076e.asn", line 3 (A1075E): A1075E: A 'TEXT' encoding instruction is assigned to the value 'bit2' of 'BS' but no 'TEXT' encoding instruction is assigned to the value 'bit3' of this type (line 6). This encoding instruction shall either be assigned to all values of the type or to none of them, unless a 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Possible Solution
You can either assign a TEXT encoding instruction to a named bit 'bit3' of the type 'BS' or remove the TEXT encoding instruction from all named bits of this type.
A1077E
Message Format
A1077E: The 'NAME' encoding instruction (line x) assigned to the value 'value' of 'Type' conflicts with the 'TEXT' encoding instruction (line y) assigned to the values of this type.
Message Cause
This error is issued in the absence of GLOBAL-DEFAULTS MODIFIED-ENCODINGS, when a NAME encoding instruction (with QualifyingInformation) assigned to a value of a type conflicts with a final TEXT encoding instruction that is also assigned to the type.
Example
A1077E DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
E ::= ENUMERATED {one, two, three}
ENCODING-CONTROL XER
TEXT E:ALL AS UPPERCASED
NAME E:one AS "One"
END
Error Message
"a1077e.asn", line 3 (A1076E): A1076E: The 'NAME' encoding instruction (line 7)
assigned to the value 'one' of 'E' conflicts with the 'TEXT' encoding instruction (line 6) assigned to the values of this type.
Possible Solution
You can either remove the NAME encoding instruction from the value "one" of type "E" or remove the TEXT encoding instruction from all values of the type "E".
A1078E
Message Format
This error is issued when the encoding instruction that should only be applied to character-encodable types is applied to a restricted character string type this string type is not considered to be a character-encodable one by the OSS ASN.1 compiler (probably it has constraints applied that the compiler ignores when checking if given type is character-encodable).
Message Cause
This error is issued when the encoding instruction is applied to a restricted character string type. This string type is not supported as a character-encodable type for the OSS ASN.1 compiler (it might have constraints applied that will be ignored by the compiler when checking if a given type is character-encodable).
NOTE: When THE OSS ASN.1 compiler checks if the restricted character string type is a character-encodable type, only the following types of constraints are considered:
- SingleValue constraints
- PermittedAlphabet constraints
Example
A1078E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S ::= SEQUENCE {
a [ATTRIBUTE] UTF8String (PATTERN "\d*"),
b [UNTAGGED] INTEGER
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1078e.asn", line 4 (A1078E): A1078E: 'a' has an 'ATTRIBUTE' encoding instruction but is not a character-encodable string type.
Possible Solution
You can either add an explicit PermittedAlphabet or SingleValue constraint to the type to exclude the control characters from all possible abstract values of this type, or specify the -ignoreError 1078 command-line option to ignore this error message. For the example above, add the following PermittedAlphabet constraint to the field a of the type S: (FROM ("0" .. "9")).
A1079E
Message Format
A1079E: The character string [alternative 'identifier'| component] of 'Type' with [a|an] 'instruction' encoding instruction (line x) shall be a character encodable type.
Message Cause
The LIST encoding instruction is applied to the SEQUENCE OF or SET OF type with a restricted character string element or the USE-UNION encoding instruction is applied to the CHOICE type with a restricted character string alternative. This character string type is not a character-encodable type by the OSS ASN.1 compiler (might have constraints which may be ignored by the compiler when checking if given type is character-encodable).
Example
A1079E DEFINITIONS XER INSTRUCTIONS ::= BEGIN L ::= SEQUENCE OF a UTF8String (PATTERN "[a-zA-Z0-9]+") ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS LIST L END
Error Message
"a1079e.asn", line 3 (A1079E): A1079E: The character string component of 'L' with a 'LIST' encoding instruction (line 7) shall be a character encodable type.
Possible Solution
Add an explicit PermittedAlphabet or SingleValue constraint to the type to exclude all control characters from all possible abstract values of this type. For the above example, add the SEQUENCE OF type to the following PermittedAlphabet constraint or to the component of the SEQUENCE OF type:
(FROM ({0,0,0,33} .. {0,0,0,127})).See Also
A1080E
Message Format
A1080E: 'Type' is a SEQUENCE type with the final 'DEFAULT-FOR-EMPTY' encoding instruction (line x). It has a character-encodable field 'identifier' with the final 'USE-QNAME' encoding instruction and a TableConstraint applied to one of the fields. The OSS runtime does not support references to such fields through a ComponentRelationConstraint.
Message Cause
The DEFAULT-FOR-EMPTY encoding instruction is applied to a SEQUENCE type with an UNTAGGED character-encodable field that is a SEQUENCE type with the final USE-QNAME encoding instruction and one of the fields of the SEQEUNCE type with the final USE-QNAME encoding instruction has a TableConstraint applied.
Example
A1080E DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
ERROR-CLASS ::= CLASS {
&id UTF8String (CONSTRAINED BY {}),
&Type
}
WITH SYNTAX {&id &Type}
ErrorSet ERROR-CLASS ::= {
{ "A" BIT STRING } | { "B" OCTET STRING }
}
ErrorReturn ::= SEQUENCE {
a [DEFAULT-FOR-EMPTY AS { u "Q1", n "Q1" }] SEQUENCE {
untg [UNTAGGED][USE-QNAME] SEQUENCE {
u ERROR-CLASS.&id ({ErrorSet}) OPTIONAL,
n ERROR-CLASS.&id ({ErrorSet}{@.u})
}
},
b ERROR-CLASS.&Type({ErrorSet}{@.a.untg.n})
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1080e.asn", line 14 (A1080E): A1080E: 'a' is a SEQUENCE type with the final
'DEFAULT-FOR-EMPTY' encoding instruction. It has a character-encodable field 'untg' with the final 'USE-QNAME' encoding instruction and a TableConstraint applied to one of the fields. The OSS runtime does not support references to such fields through a ComponentRelationConstraint.
Possible Solution
Remove a TableConstraint from the field of the SEQUENCE type with the final USE-QNAME encoding instruction.
A1081E
Message Format
A1081E: The recursive definition of ContentsConstraint for '%s' is illegal.
Message Cause
The ContentsConstraint is defined recursively.
Example
M DEFINITIONS ::= BEGIN
T ::= OCTET STRING (CONTAINING T)
END
Error Message
"a1081e.asn", line 2 (M): A1081E: The recursive definition of ContentsConstraint for 'T' is illegal.
Possible Solution
Make sure the ContentsConstraint is not defined recursively.
A1082E
Message Format
A1082E: The final character string used for the value 'value' of 'Type' in the 'TEXT' encoding instruction contains [illegal character|illegal character sequence] while this type has a final 'WHITESPACE WhiteSpaceAction' encoding instruction (line x).
Message Cause
The WHITESPACE encoding instruction is applied to a type with the final TEXT encoding instruction but the final strings specified in the TEXT encoding instruction do not satisfy the restrictions for abstract values of the type with a final WHITESPACE encoding instructions.
The type has a final WHITESPACE REPLACE or a final WHITESPACE COLLAPSE encoding instruction and the value in the TEXT encoding instruction contains one or more of the following:
- LINE FEED character
- CARRIAGE RETURN character
- HORIZONTAL TABULATION character
The type has a final WHITESPACE COLLAPSE encoding instruction and the value in the TEXT encoding instruction contains one of the following:
- multiple adjacent space characters
- leading spaces
- trailing spaces
Example
A1082E DEFINITIONS ::= BEGIN
T1 ::= BOOLEAN
T2 ::= T1
ENCODING-CONTROL XER
WHITESPACE T1, T2 COLLAPSE
TEXT T1:true AS "- -"
TEXT T2:false AS " ++++"
END
Error Message
"a1082e.asn", line 8 (A1082E): A1082E: The final character string used for the value 'true' of 'T1' in the 'TEXT' encoding instruction contains multiple adjacent space characters while this type has a final 'WHITESPACE COLLAPSE' encoding instruction (line 7).
"a1082e.asn", line 9 (A1082E): A1082E: The final character string used for the value 'false' of 'T2' in the 'TEXT' encoding instruction contains leading spaces while this type has a final 'WHITESPACE COLLAPSE' encoding instruction (line 7).
Possible Solution
You can either remove illegal characters from the value specified in the TEXT encoding instruction or remove the final WHITESPACE encoding instruction from the type.
A1083W
Message Format
A1083W: The content model for 'Type' is non-deterministic: reason.
Message Cause
The determinism requirement is violated. For an ASN.1 specification to be legal, a decoder must be able to determine, for all abstract values, the ASN.1 component that an XML element is associated with, using only the name of the XML tag and the contents of any previous XML element. A warning, and not an error, (see A1067E) is issued because these cases could result from XSD mapping.
Example
Module-A1083W DEFINITIONS XER INSTRUCTIONS ::=BEGIN
Element ::= [ELEMENT] EmptyType
EmptyType ::= [UNTAGGED] SEQUENCE {
empty EmptyType OPTIONAL
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1083w.asn", line 7 (Module-A1083W): A1083W: The content model for 'untagged component' is non-deterministic: recursively defined type with empty content found.
"a1083w.asn", line 7 (Module-A1083W): A1043W: 'empty' is not among the permitted types for the 'UNTAGGED' encoding instruction: the encoding instruction is applied to a component of a sequence or set type with OPTIONAL or DEFAULT that may have an empty 'ExtendedXMLValue' encoding for one of its abstract values.
"a1083w.asn", line 4 (Module-A1083W): A1083W: The content model for 'Element' is non-deterministic: recursively defined type with empty content found.
Possible Solution
Disambiguate the specification by removing any UNTAGGED elements, renaming the fields, etc.
A1084E
Message Format
A1084E: The "URIList" shall not contain two identical "QuotedURI"s.
Message Cause
This error is issued when "URIList" in a ANY-ATTRIBUTES or in a ANY-ELEMENT encoding instruction contains two identical "QuotedURI"s.
Example
A1084E DEFINITIONS ::= BEGIN
A ::= SEQUENCE (CONSTRAINED BY{}) OF UTF8String
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
ANY-ATTRIBUTES A EXCEPT "test.org" ABSENT "test.org"
END
Error Message
"a1084e.asn", line 8 (A1084E): A1084E: The "URIList" shall not contain two identical "QuotedURI"s.
Possible Solution
Remove the duplicated "QuotedURI"s from "URIList".
A1085E
Message Format
A1085E: The final 'NAMESPACE' encoding instruction (line x) applied to 'Type' to qualify empty-element tags for special characters does not match the ASN.1 namespace.
Message Cause
The NAMESPACE encoding instruction cannot be applied with the QualifyingInformation to a restricted character string type to qualify empty-element tags for special characters unless the URI in the NAMESPACE encoding instruction matches the ASN.1 namespace.
Example
A1085E DEFINITIONS ::= BEGIN T ::= VideotexString ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE T:ALL AS "test.org" END
Error Message
"a1085e.asn", line 3 (A1085E): A1085E: The final 'NAMESPACE' encoding instruction (line 7) applied to 'T' to qualify empty-element tags for special characters does not match the ASN.1 namespace.
Possible Solution
Replace the "URI" in the NAMESPACE encoding instruction applied with the QualifyingInformation with a restricted character string type to the URI of the ASN.1 namespace: urn:oid:2.1.5.2.0.1.
A1086E
Message Format
(line x): A1086E: The 'instruction' encoding instruction is used as a prefixed encoding instruction in combination with the prefixed 'instruction' encoding instruction (line y).
Message Cause
This error is issued when:
- NAME encoding instruction is used as a prefixed encoding instruction in combination with any of the following prefixed encoding instructions: ANY ATTRIBUTES, ANY-ELEMENT or UNTAGGED.
- ELEMENT encoding instruction is used as a prefixed encoding instruction in combination with any of the following prefixed encoding instructions: ANY ATTRIBUTES, ANY-ELEMENT or ATTRIBUTE.
Example
A1086E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
T2 ::= SEQUENCE {
f1 [ANY-ATTRIBUTES]
[ELEMENT] SEQUENCE (CONSTRAINED BY {}) OF UTF8String,
f2 UTF8String
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"a1086e.asn", line 5 (A1086E): A1086E: The 'ELEMENT' encoding instruction is used as a prefixed encoding instruction in combination with the prefixed 'ANY-ATTRIBUTES' encoding instruction (line 4).
Possible Solution
Remove the prefixed ELEMENT or the prefixed NAME encoding instruction.
A1087E
Message Format
A1087E: The final 'NAMESPACE' encoding instruction (line x) applied to 'Type' with a final 'ATTRIBUTE' encoding instruction must not match the control namespace.
Message Cause
The final NAMESPACE encoding instruction applied to a type with a final ATTRIBUTE encoding instruction matches the control namespace.
Example
A1087E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
S1 ::= [USE-NIL] SEQUENCE {
f0 SEQUENCE OF INTEGER OPTIONAL,
f1 [NAME AS "nil"][ATTRIBUTE] BOOLEAN OPTIONAL
} (CONSTRAINED BY {})
ENCODING-CONTROL XER
GLOBAL-DEFAULTS CONTROL-NAMESPACE "test" PREFIX "ns"
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
NAMESPACE ALL IN S1 AS "test" PREFIX "ns"
END
Error Message
"a1087e.asn", line 5 (A1087E): A1087E: The final 'NAMESPACE' encoding instruction (line 11) applied to 'f1' with a final 'ATTRIBUTE' encoding instruction must not match the control namespace.
Possible Solution
Replace the name of the namespace and make sure it is different from the control namespace.
A1088E
Message Format
A1088E: The "RestrictedCharacterStringValue" in "NewName" in the final 'NAME' encoding instruction (line x) applied to 'Type' is an empty character string but this type is not an alternative of a choice type with a final 'USE-UNION' encoding instruction.
Message Cause
The "RestrictedCharacterStringValue" in "NewName" in the NAME encoding instruction is an empty character string. Unless the NAME encoding instruction is applied to a type that is an alternative of a CHOICE type with a final "USE-UNION" encoding instruction, the "RestrictedCharacterStringValue" must not be an empty character string.
Example
A1088E DEFINITIONS ::= BEGIN
T ::= SEQUENCE {
a [XER:NAME AS ""] INTEGER,
b BOOLEAN
}
END
Error Message
"a1088e.asn", line 4 (A1088E): A1088E: The "RestrictedCharacterStringValue" in "NewName" in the final 'NAME' encoding instruction applied to 'T.a' is an empty character string but this type is not an alternative of a choice type with a final 'USE-UNION' encoding instruction.
Possible Solution
Replace the "NewName" in the NAME encoding instruction with a non-empty string that matches the "NCName" production from the W3C XML Namespaces document.
C1090W
Message Format
C1090W: The recommended prefix prefix1 for the XML namespace has been replaced by prefix2.
Message Cause
A NAMESPACE XER encoding instruction assigns a prefix to the XML namespace (identified by the http://www.w3.org/XML/1998/namespace URL string), but the prefix is not xml. This is not allowed, because the above URI is bound to the prefix xml. In this case, the compiler automatically changes the namespace prefix to xml.
Example
Module-C1090W DEFINITIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE I AS "http://www.w3.org/XML/1998/namespace" PREFIX "lmx" END
Error Message
"c1090w.asn", line 7 (Module-C1090W): C1090W: The recommended prefix 'lmx' for the XML namespace has been replaced by 'xml'.
Possible Solution
Make sure you do not specify the recommended prefix for XML namespaces; the xml prefix is automatically assigned.
C1092W
Message Format
C1092W: The VARYING directive is incompatible with extensible size constraints and prevents '%s' from containing extension values. Please consider use of the UNBOUNDED directive instead, otherwise extension values received by the decoder will cause runtime error messages.
Message Cause
The VARYING directive is used with a type with an extensible size constraint and the compat flag useVaryingForExtensible is specified on the ASN.1 compiler command-line.
Example
M DEFINITIONS ::= BEGIN O ::= OCTET STRING (SIZE(1..17, ...)) --<VARYING>-- END
Error Message
"c1092w.asn", line 3 (M): C1092W: The VARYING directive is incompatible with extensible size constraints and prevents 'O' from containing extension values. Please consider use of the UNBOUNDED directive instead, otherwise extension values received by the decoder will cause runtime error messages.
Possible Solution
Make sure you do not use the VARYING directive for the type with an extensible size constraint. Instead, you can use the UNBOUNDED directive.
See Also
C1093W
Message Format
C1093W: The VARYING directive is incompatible with extensible size constraints and prevents '%s' from containing extension values. The UNBOUNDED representation is used for the type. To revert to the VARYING representation use compiler option -compat useVaryingForExtensible.
Message Cause
The VARYING directive is used for a type with an extensible size constraint.
Example
M DEFINITIONS ::= BEGIN O ::= OCTET STRING (SIZE(1..17, ...)) --<VARYING>-- END
Error Message
"c1093w.asn", line 3 (M): C1093W: The VARYING directive is incompatible with extensible size constraints and prevents 'O' from containing extension values. The UNBOUNDED representation is used for the type. To revert to the VARYING representation use compiler option -compat useVaryingForExtensible.
Possible Solution
Make sure you do not use the VARYING directive for the type with an extensible size constraint.
See Also
C1094E
Message Format
"C1094E: No valid ossinfo file was found. If you changed the location of the file, click File/Preferences menu item and specify its new location. If you don't have a valid license file, please contact OSS Nokalva, Inc. to obtain a new one."
Message Cause
The OSS configuration file, ossinfo, is missing or does not provide access to all the features of ASN-1Step.
Possible Solution
Place the correct ossinfo file in the valid directory or contact Sales ‹info@oss.com› for information about renewing your license or obtaining updated software.
A1095E
Message Format
A1095E: The 'xmlhstring' shall not be an odd number of hexadecimal digits.
Message Cause
An XMLValueAssignment contains a value for an OCTET STRING type with an odd number of hex digits. According to X.693 standard, this is not allowed.
Example
A1095E DEFINITIONS ::= BEGIN
S ::= SEQUENCE { f OCTET STRING }
s ::= <S><f>123</F></S>
END
Error Message
"a1095e.asn", line 3 (A1095E): A1095E: The 'xmlhstring' shall not be an odd number of hexadecimal digits.
s ::= <S><f>123</F></S>
Possible Solution
Add a single zero digit to the end of the OCTET STRING value.
C1096E
Message Format
C1096E: No input files specified.
Message Cause
No input file is specified on the command line, but some compiler options are present. The most likely cause is an option that takes a non-mandatory argument that can be confused with the file name.
Example
In the following example, the filename has been specified, but the compiler interprets it as an optional parameter for the -xsd command-line option.
asn1 -xsd file.asn
Error Message
C1096E: No input files specified.
Possible Solution
Provide a correct parameter for the option or, if the optional parameter is missing, make sure that the option is the last one:
- asn1 -xsd file.xsd file.asn
- asn1 file.asn -xsd
C1097I
Message Format
C1097I: The PDU directive can only be applied to a top-level type reference. Consider application of the directive to the referenced type '%s' itself.
Message Cause
The PDU directive is applied to a type reference which is the component of a complex type, but it must be applied to the top-level type reference.
Example
Module-C1097I DEFINITIONS ::= BEGIN
S ::= SEQUENCE --<UNBOUNDED|PDU>-- OF I --<PDU>--
I ::= INTEGER
END
Error Message
"c1097i.asn", line 2 (Module-C1097I): C1097I: The PDU directive can only be applied to a top-level type reference. Consider application of the directive to the referenced type 'I' itself.
Possible Solution
Apply the PDU directive to the definition of the type.
C1098I
Message Format
C1098I: The PDU directive can only be applied to a top-level type reference.
Message Cause
The PDU directive is applied to a BuiltinType (an ASN.1 type that is an ASN.1 keyword such as INTEGER or SET, as opposed to an ASN.1 type that is defined by a type assignment) which is the component of a complex type.
Example
Module-C1098I DEFINITIONS ::= BEGIN
S ::= SEQUENCE --<UNBOUNDED|PDU>-- OF INTEGER --<PDU>--
END
Error Message
"c1098i.asn", line 2 (Module-C1098I): C1098I: The PDU directive can only be applied to a top-level type reference.
Possible Solution
Create a new type that references the BuiltinType with a directive applied to the PDU and apply the directive to that type, removing the directive from the type defined within the type assignment:
Module-C1098I DEFINITIONS ::= BEGIN
SPrime ::= INTEGER --<PDU>--
S ::= SEQUENCE --<UNBOUNDED|PDU>-- OF SPrime
END
L1129W
Message Format
L1129W: Ignoring filename: 'fname'. Only one DTD file is permitted.
L1129W: Ignoring filename: 'fname'. Only one XSL stylesheet file is permitted.
Message Cause
You may specify only one .xsl and one .dtd or one .pdtd file on the ASN-1Step command line. Any extra filename is ignored.
Possible Solution
Make sure you have only one file.
A1130E
Message Format
A1130E: The 'GlobalModuleReference' with the module name 'MyModule' and a non-empty 'AssignedIdentifier' specified in the 'Imports' clause of the module 'MyModule' does not appear in the 'ModuleDefinition' of any input module.
Message Cause
A module reference, specified in the IMPORTS clause by the module name and an OBJECT IDENTIFIER, is not defined. A module with the same name may be defined but the OBJECT IDENTIFIERs do not match.
Example
M1 DEFINITIONS ::= BEGIN
IMPORTS I FROM M2 {2 3};
S ::= SEQUENCE OF I
END
M2 {1 2} DEFINITIONS ::= BEGIN
I ::= INTEGER
END
Error Message
"A1130E.asn", line 3 (M1): A1130E: The 'GlobalModuleReference' with the module name 'M2' and a non-empty 'AssignedIdentifier' specified in the 'Imports' clause of the module 'M2' does not appear in the 'ModuleDefinition' of any input module.
Possible Solution
Replace the OBJECT IDENTIFIER in the module reference with the correct OBJECT IDENTIFIER obtained from the module definition.
Instead of modifying the input ASN.1 files, you can force the ASN.1 compiler to ignore the error message A1130E by specifying the ASN.1 compiler option ignoreError 1130. Note that if you choose to ignore the error A1130E you are not protected from the other ASN.1-compilation errors.
C1131E
Message Format
C1131E: The same function_kind, 'function_name', cannot be used for the ASN.1 types, defined on lines line1 and line2, having different C representations. Use OSS directives to align the C representations for both types.
Message Cause
A user-defined function such as the one defined by the OSS.XEREncodeFunction directive affects two types having different C representations, or several such directives apply the same user-defined function to incompatible C types. Functions like the XER encoding formatter function are compatible with all C structures therefore all C types using the same function must be compatible.
Example
--<OSS.XEREncodeFunction C1131E.T "myF">-- C1131E DEFINITIONS ::= BEGIN T ::= INTEGER --<PDU>-- LL ::= T --<LONGLONG>-- END
Error Message
"c1131e.asn", line 3 (C1131E): C1131E: The same user-defined XER encoding formatter, 'myF', cannot be used for the ASN.1 types, defined on lines 3 and 4, having different C representations. Use OSS directives to align the C representations for both types.
Possible Solution
Assign a different user-defined function. Use distinct functions for unrelated types that have different representations in C.
C1132W
Message Format
C1132W: There is a function_kind, 'function_name', that is not used by any type in the resulting WorkingSet. Check whether it has been overridden by another user-defined XER encoding formatter applied to the same type.
Message Cause
A user-defined function such as an XER encoding formatter function is introduced by a corresponding OSS directive that is not used by any type from the resulting control table. However, the directive itself is used. This means that either the function is overridden by another function of the same kind or it is applied to the ASN.1 type that is not present in the resulting WorkingSet.
Example
--<OSS.XEREncodeFunction C1132W.T "myF">-- --<OSS.XEREncodeFunction C1132W.T "myFF">-- C1132W DEFINITIONS ::= BEGIN T ::= INTEGER END
Error Message
"c1132w.asn" (C1132W): C1132W: There is a user-defined XER encoding formatter, 'myF', that is not used by any type in the resulting WorkingSet. Check whether it has been overridden by another user-defined XER encoding formatter applied to the same type.
Possible Solution
Remove the directives.
C1133E
Message Format
C1133E: The parameter of the function_kind, 'function_name', is either unknown or not present in the current WorkingSet.
Message Cause
A user-defined function such as the one defined by the OSS.XEREncodeFunction directive contains an optional parameter, but the C typedef for this parameter is not included in the resulting control table and header file. The ASN.1 type identified by the parameter with an absolute reference does not exist or is not included in the WorkingSet.
Example
--<OSS.XEREncodeFunction C1133E.T "myF" M.S>-- M DEFINITIONS ::= BEGIN S ::= SEQUENCE OF INTEGER END C1133E DEFINITIONS ::= BEGIN T ::= INTEGER END
Error Message
"c1133e.asn" (C1133E): C1133E: The parameter of the user-defined XER encoding formatter, 'myF', is either unknown or not present in the current WorkingSet.
Possible Solution
Make sure that the parameter with an absolute reference is spelled correctly. Associate the type that has a user-defined function applied with the function parameter in one PDU type.
C1134E
Message Format
C1134E: The OSS.NOCOPY directive cannot be applied to this type of function_kind or to its components.
Message Cause
A user-defined function is applied to a type that has a component marked with the NOCOPY directive. Functions that exchange C structures cannot be applied to these types because a type with the NOCOPY requires special handling to obtain the value.
Example
--<OSS.XEREncodeFunction C1134E.T "myF">--
C1134E DEFINITIONS ::= BEGIN
T ::= SEQUENCE { o OCTET STRING --<NOCOPY>-- }
END
Error Message
"c1134e.asn", line 3 (C1134E): C1134E: The OSS.NOCOPY directive cannot be applied to this type of user-defined XER encoding formatter or to its components.
Possible Solution
Remove the NOCOPY directive. If you need the OSS.XEREncodeFunction directive to support these functions, contact Technical Support ‹support@oss.com› .
C1135E
Message Format
C1135E: The same function_kind, 'function_name', cannot be used both with and without a parameter.
Message Cause
A user-defined function such as XER encoding formatter is used with two directives; the first one does not define an optional parameter of this function and the second one does. The two directives generate incompatible function prototypes for the same function, which is not allowed.
Example
--<OSS.XEREncodeFunction C1135E.T1 "myF">--
--<OSS.XEREncodeFunction C1135E.T2.i "myF" C1135E.T2.p>--
C1135E DEFINITIONS ::= BEGIN
T1 ::= INTEGER
T2 ::= SEQUENCE { p BOOLEAN, i INTEGER}
END
Error Message
"c1135e.asn", line 5 (C1135E): C1135E: The same user-defined XER encoding formatter, 'myF', cannot be used both with and without a parameter.
Possible Solution
Make sure that parameters of all OSS directives that reference the same user-defined function are synchronized.
C1136E
Message Format
C1136E: The same function_kind, 'function_name', cannot be used with two incompatible parameters defined on lines line1 and line2. Use OSS directives to align the C representations for both parameters.
Message Cause
A user-defined function such as an XER encoding formatter is used with two directives, but both have an optional parameter; however, the C types of the function parameters are incompatible. The two directives generate incompatible function prototypes for the same function, which is not allowed.
Example
--<OSS.XEREncodeFunction C1136E.T1.i "myF" C1136E.T1.r>--
--<OSS.XEREncodeFunction C1136E.T2.i "myF" C1136E.T2.p>--
C1136E DEFINITIONS ::= BEGIN
T1 ::= SEQUENCE {r OCTET STRING, i INTEGER}
T2 ::= SEQUENCE {p BOOLEAN, i INTEGER}
END
Error Message
"c1136e.asn", line 4 (C1136E): C1136E: The same user-defined XER encoding formatter, 'myF', cannot be used with two incompatible parameters defined on lines 4 and 5. Use OSS directives to align the C representations for both parameters.
Possible Solution
Make sure that C types of all parameters of all OSS directives that reference the same user-defined function are synchronized.
A1137E
Message Format
A1137E: The value reference 'reference' with an assigned negative value may not be used as an object identifier component.
Message Cause
An OBJECT IDENTIFIER value contains a node that has a negative INTEGER value assigned. All nodes of the OBJECT IDENTIFIER tree must be non-negative.
Example
Module-A1137E DEFINITIONS ::= BEGIN
PDU ::= OBJECT IDENTIFIER
i INTEGER ::= -2
pdu PDU ::= {1 2 i}
END
Error Message
"a1137e.asn", line 4 (Module-A1137E): A1137E: The value reference 'i' with an assigned negative value may not be used as an object identifier component.
Possible Solution
Make sure that the value used as an object identifier component is non-negative.
A1138E
Message Format
A1138E: The 'NewName' in the final 'TEXT' encoding instruction assigned to the named bit 'value' of the bitstring type 'Type' is not correct: reason.
Message Cause
The character string value specified in the "NewName" parameter of a TEXT encoding instruction assigned via QualifyingInformation to the named bit of the bitstring type contains an invalid character. There are two possible reasons:
- The "NewName" value contains a white-space character.
- The "NewName" value begins with "0" or "1".
Using such values for named bits of BIT STRING types in TEXT encoding instructions is not permitted according to X.693.
Example
A1138E DEFINITIONS ::= BEGIN
BS1 ::= BIT STRING {bit1(1), bit2(2)}
BS2 ::= BIT STRING {bit3(3), bit4(4)}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
TEXT BS1:bit1 AS " bit1"
TEXT BS2:bit3 AS "0bit3"
END
Error Message
"a1138e.asn", line 8 (A1138E): A1138E: The 'NewName' in the final 'TEXT' encoding instruction assigned to the named bit 'bit1' of the bitstring type 'BS1' is not correct: the value contains a white-space character.
"a1138e.asn", line 9 (A1138E): A1138E: The 'NewName' in the final 'TEXT' encoding instruction applied to the named bit 'bit3' of the bitstring type 'BS2' is not correct: the value commences with a "0" (DIGIT ZERO).
Possible Solution
Remove the invalid characters.
A1139W
Message Format
A1139W: The default encoding reference 'encodingreference' for the module 'modulereference' is unknown and all encoding instructions within the module identified by this encoding reference will be ignored.
Message Cause
A default encoding reference specified in the module header from the ASN.1 input is unknown and is not supported by the OSS ASN.1 compiler. The compiler will ignore all encoding instructions within the module identified by this encoding reference, that is, all the encoding instructions will not have any impact on the behavior of the OSS ASN.1 compiler and runtime.
Example
A1139W DEFINITIONS PER INSTRUCTIONS ::= BEGIN I ::= INTEGER END
Error Message
"a1139w.asn", line 1 (A1139W): A1139W: The default encoding reference 'PER' for the module 'A1139W' is unknown and all encoding instructions within the module identified by this encoding reference will be ignored.
A1139W DEFINITIONS PER INSTRUCTIONS ::= BEGIN
Possible Solution
For more information about the encoding instructions identified by the encoding reference, contact Technical Support ‹support@oss.com› .
See Also
A1140W
Message Format
A1140W: The encoding instruction identified by the unknown encoding reference, 'encodingreference', is being ignored.
A1140W: The encoding instruction, 'encodinginstruction', identified by the unknown encoding Reference, 'encodingreference', is being ignored.
Message Cause
A prefixed encoding instruction is identified by an encoding reference that is unknown and is not supported by the OSS ASN.1 compiler. The compiler will ignore this encoding instruction.
Example
A1140W DEFINITIONS ::= BEGIN I ::= [QWERTY:INSTRUCTION] INTEGER END
Error Message
"a1140w.asn", line 3 (A1140W): A1140W: The encoding instruction, 'INSTRUCTION', identified by the unknown encoding reference, 'QWERTY', is being ignored.
I ::= [QWERTY:INSTRUCTION] INTEGER
A1141W
Message Format
A1141W: The encoding control section for an unknown encoding reference 'encodingreference' is being ignored.
Message Cause
An encoding control section is identified by an unknown encoding reference that is not supported by the OSS ASN.1 compiler. The compiler will ignore all encoding instructions within the encoding control section.
Example
A1141W DEFINITIONS ::= BEGIN I ::= INTEGER ENCODING-CONTROL QWERTY INSTRUCTION1 END
Error Message
"a1141w.asn", line 5 (A1141W): A1141W: The encoding control section for an unknown encoding reference 'QWERTY' is being ignored.
ENCODING-CONTROL QWERTY
See Also
C1143W
Message Format
C1143W: OSS.HelperMacro directive ignored because -noHelperMacro option was specified.
C1143W: OSS.NoHelperMacro directive ignored because -helperMacro option was specified.
C1143W: OSS.HelperListAPI directive ignored because -noHelperListAPI option was specified.
C1143W: OSS.NoHelperListAPI directive ignored because -helperListAPI option was specified.
Message Cause
The options -helperMacro, -noHelperMacro, -helperListAPI, and -noHelperListAPI override corresponding directives.
Possible Solution
To generate helper macros or helper list API functions for several selected types use a combination of the corresponding global and local directives.
C1144W
Message Format
C1144W: OSS.[HelperMacro|NoHelperMacro|HelperListAPI|NoHelperListAPI] directive is ignored because the -helperNames option is not specified.
Message format when using the compiler GUI
C1144W: OSS.HelperMacro directive is ignored because the "Do not generate context-based names, helper- and helper list API macros" box within the "Helper Options" group in the "More Options" tab of the "Compiler Options" window is checked.
Message Cause
One or more compiler directives (OSS.HelperMacro, OSS.NoHelperMacro, OSS.HelperListAPI, OSS.NoHelperListAPI) require the helperNames option to be specified.
Example
--<OSS.HelperMacro Module-C1144W.S>-- Module-C1144W DEFINITIONS ::= BEGIN S ::= IA5String END
Error Message
C1144W: OSS.HelperMacro directive is ignored because the -helperNames option is not specified.
Possible Solution
Specify the -helperNames option or remove the helper directives from the input syntax.
C1145W
Message Format
C1145W: OSS.[HelperMacro|NoHelperMacro|HelperListAPI|NoHelperListAPI] directive is ignored because the -noHelperNames option is specified.
Message format when using the compiler GUI
C1145W: OSS.[HelperMacro|NoHelperMacro|HelperListAPI|NoHelperListAPI] directive is ignored because the "Do not generate context-based names, helper- and helper list API macros" box within the "Helper Options" group in the "More Options" tab of the "Compiler Options" window is checked.
Message Cause
One or more compiler directives (OSS.HelperMacro, OSS.NoHelperMacro, OSS.HelperListAPI, OSS.NoHelperListAPI) and the noHelperNames are specified on the command line.
Example
--<OSS.HelperMacro Module-C1145W.S>-- Module-C1144W DEFINITIONS ::= BEGIN S ::= IA5String END
Error Message
C1145W: OSS.HelperMacro directive is ignored because the -noHelperNames option is specified.
Possible Solution
Remove the -noHelperNames option or remove helper directives from the input syntax.
C1146W
Message Format
C1146W: Directive Directive-name is not supported with the helper API and will be ignored.
Message Cause
A compiler directive has been applied but is not supported when the helperName option is specified or implied or when other helper options are specified.
Example
Module-C1146W DEFINITIONS ::= BEGIN P ::= SET --<LINKED>-- OF INTEGER END
Error Message
C1146W: Directive LINKED is not supported with the helper API and will be ignored.
Possible Solution
See Compiler Directives to learn which directives are supported in the helperAPI.
C1147W
Message Format
C1147W: The Directive-name directive is not supported for the field 'field-id' within the type 'Type-name' in the helper mode and will be ignored.
Message Cause
A compiler directive is not supported for the specified ASN.1 item if the -helperName option is specified or implied with other helper options.
Example
Module-C1147W DEFINITIONS ::= BEGIN
Name ::= CHOICE {
a VisibleString --<POINTER>--
}
END
Error message when compiling with -helperNames
C1147W: The POINTER directive is not supported for the field 'a' within the type 'Name' in the helper mode and will be ignored.
Possible Solution
See Compiler Directives to learn which types are supported for the directive.
L1148E
Message Format
L1148E: The compiler option option-name is deprecated and is not available in this copy of the ASN.1 compiler. Please contact OSS Nokalva (info@oss.com) to get a trial of the ASN.1/C tools that has this option available.
Message Cause
The RAD ASN.1 compiler does not support certain deprecated options from the Classic one (-compat,for example). This error is generated only in pre-9.0 versions of the Tools.
Error message when using the trial version of the asn1c compiler with -compat v4.2.0
L1148E: The compiler option -compat is deprecated and is not available in this copy of the ASN.1 compiler. Please contact OSS Nokalva (info@oss.com) to get a trial of the ASN.1/C tools that has this option available. This is found only in the trial RAD ASN.1 compiler.
Possible Solution
Remove the option from the command line or contact OSS Nokalva (info@oss.com) to get a trial version of the ASN.1/C tools that supports this option.
NOTE: This error message is deprecated starting with release 8.1.
L1149E
Message Format
L1149E: The compiler option option-name is not available in this copy of the ASN.1 compiler. Please invoke the compiler using the name "asn1" in order to use this option.
Message Cause
The RAD ASN.1 compiler does not support certain deprecated options from the ASN.1 compiler (-compat,for example). This is found only in the non-trial RAD ASN.1 compiler in pre-9.0 versions of the Tools.
Error message when using the trial version of the asn1c compiler with -compat v4.2.0
L1149E: The compiler option -compat is not available in this copy of the ASN.1 compiler. Please invoke the compiler using the name "asn1" in order to use this option.
Possible Solution
Remove the option from the command line or contact OSS Nokalva (info@oss.com) to get a trial version of the ASN.1/C tools that supports this option.
NOTE: This error message is deprecated starting with release 8.1.
C1150W
Message Format
C1150W: The compiler directive Directive-name is deprecated and will be ignored in this copy of the ASN.1 compiler. Please contact OSS Nokalva (info@oss.com) to get a trial of the ASN.1/C tools that has this directive available.
Message Cause
A compiler directive is deprecated and is not supported for the RAD ASN.1 compiler. This message is generated only in the trial version of the RAD ASN.1 compiler in pre-9.0 versions of the Tools.
Example
Module DEFINITIONS ::= BEGIN P ::= SET --<LINKED>-- OF INTEGER END
Error Message
C1150W: The compiler directive LINKED is deprecated and will be ignored in this copy of the ASN.1 compiler. Please contact OSS Nokalva (info@oss.com) to get a trial of the ASN.1 Tools for C that has this directive available.
Possible Solution
See Compiler Directives to learn which directives are supported for the RAD ASN.1 compiler.
NOTE: This error message is deprecated starting with release 8.1.
C1151W
Message Format
C1151W: The compiler directive Directive-name is not available and will be ignored in this copy of the ASN.1 compiler. Please invoke the compiler using the name "asn1" in order to use this directive.
Message Cause
The input ASN.1 syntax contains a compiler directive application that is deprecated in the RAD ASN.1 compiler. This is found only in the non-trial RAD ASN.1 compiler in pre-9.0 versions of the Tools.
Example
Module DEFINITIONS ::= BEGIN P ::= SET --<LINKED>-- OF INTEGER END
Error message when using the asn1c compiler with -compat v4.2.0
C1151W: The compiler directive LINKED is not available and will be ignored in this copy of the ASN.1 compiler. Please invoke the compiler using the name "asn1" in order to use this directive.
Possible Solution
See Compiler Directives to learn which directives are supported for the RAD ASN.1 compiler (and remove unsupported directives) or invoke the compiler with "asn1" to use this directive.
NOTE: This warning message is deprecated starting with release 8.1.
C1152W
Message Format
C1152W: The Directive-name directive is not supported with the [ lean| toed] option and will be ignored.
Message format when using the compiler GUI
C1152W: The Directive-name directive is not supported by the [lean|toed] encoder/decoder and will be ignored.
Message Cause
A particular compiler directive is not supported if the -helperName option is specified or implied with other helper options.
Example
Module-C1152W DEFINITIONS ::= BEGIN I ::= INTEGER --<SHORT>-- END
Error message when compiling with -lean
C1152W: The SHORT directive is not supported with the -lean option and will be ignored.
Possible Solution
See Compiler Directives to learn which directives are supported for the -lean option.
C1153W
Message Format
C1153W: The Directive-name directive is not supported for the type 'Type-name' in the helper mode and will be ignored.
C1153W: The Directive-name directive is not supported for 'Some-name' in the helper mode and will be ignored.
Message Cause
A particular compiler directive is not supported if the -helperName option is specified or implied with other helper options.
Example
Module-C1153W DEFINITIONS ::= BEGIN S ::= IA5String --<POINTER>-- END
Error message when compiling with -helperNames
C1153W: The POINTER directive is not supported for the type 'S' in the helper mode and will be ignored.
Possible Solution
See Compiler Directives to learn which types are supported for the directive.
C1154W
Message Format
C1154W: The OSS.HelperMacro directive applied to the field 'field-id' within the typereference 'Type-name' is ignored because no helper macros are generated for the parent type.
Message Cause
You can use the field-level macros only if helper macros are generated for the parent type.
Example
--<OSS.HelperMacro Mod.SetBoolHM.bool>--
Mod DEFINITIONS ::= BEGIN
SetBoolHM ::= SET {bool BOOLEAN --<POINTER>--}
END
Error message when compiling with -helperNames
C1154W: The OSS.HelperMacro directive applied to the field 'bool' within the typereference 'SetBoolHM' is ignored because no helper macros are generated for the parent type.
Possible Solution
Apply either a global OSS.HelperMacro directive or a type-specific directive to the top-most typereference.
C1155E
Message Format
C1155E: Multiple target namespaces are not supported by the XML Schema Extended XER generator. The [type|field] 'identifier1' and the type 'identifier2' have different target namespaces.
Message Cause
Certain types (typereferences, types of the SET, SEQUENCE, CHOICE fields or types of the SET OF, SEQUENCE OF elements) in the ASN.1 notation have different target namespaces. Currently, you can use at most one target namespace in the generated XML Schema file.
Example
M DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- One PDU with namespace "a" and one without namespace PDU1 ::= INTEGER PDU2 ::= IA5String ENCODING-CONTROL XER GLOBAL-DEFAULTS MODIFIED-ENCODINGS NAMESPACE PDU1 AS "a" PREFIX "ns" END
Error Message
"c1155e.asn", line 4 (M): C1155E: Multiple target namespaces are not supported by the XML Schema Extended XER generator. The type 'PDU2' and the type 'PDU1' have different target namespaces.
Possible Solution
Make sure that at most one URI is used in NAMESPACE XER instructions across all input ASN.1 modules. Additionally, if at least one of the ASN.1 types is namespace-qualified, all PDU types must be namespace-qualified.
If you need more information about removing the above restriction (by producing several schema files instead of one, one file per input ASN.1 module), contact Technical Support ‹support@oss.com›
A1162E
Message Format
A1162E: Type built-in type 'UniversalString' is illegally redefined.
A1162E: Type built-in type 'BMPString' is illegally redefined.
A1162E: Type built-in type 'UTF8String' is illegally redefined.
Message Cause
The name of a user-defined type definition is identical with the name of a built-in type: UniversalString, BMPString, or UTF8String.
Example
Module-A1162E DEFINITIONS ::= BEGIN UniversalString ::= [UNIVERSAL 28] IMPLICIT OCTET STRING END
Error Message
"a1162e.asn", line 5 (Mod1): A1162E: The built-in ASN.1 type 'UniversalString' is illegally redefined.
UniversalString ::= [UNIVERSAL 20] IMPLICIT OCTET STRING
Possible Solution
Specify a distinct name or use -ignoreError 1162 to suppress this error. When redefining your syntax make sure you use a valid definition of the corresponding ASN.1 type.
A1163E
Message Format
A1163W: OSS has relaxed the standards to allow the definition of a type with the tag [UNIVERSAL num] resulting in 'BltType-name1' to be redefined to 'BltType-name2'. This is normally an invalid ASN.1.
Message Cause
The input ASN.1 syntax contains a CHARACTER STRING or OCTET STRING type definition with an IMPLICIT tag whose UNIVERSAL tag class and number correspond to a restricted character string type.
This ASN.1 notation generates a compiler error message. The warning message is printed only if the -allow universaltags option is specified.
Example
Module-A1163W DEFINITIONS ::= BEGIN CS-U8 ::= [UNIVERSAL 12] IMPLICIT CHARACTER STRING END
Error Message
"a1163w.asn", line 2 (Module-A1163W): A1163W: OSS has relaxed the standards to allow the definition of a type with the tag [UNIVERSAL 12] resulting in 'CHARACTER STRING' to be redefined to 'UTF8String'. This is normally an invalid ASN.1.
CS-U8 ::= [UNIVERSAL 12] IMPLICIT CHARACTER STRING
Possible Solution
Make sure you do not use the UNIVERSAL tag class.
See Also
C1164I
Message Format
C1164I: Generating C# files.
Message Cause
The -debug <nonzero> option is specified.
Possible Solution
Make sure you do not specify the -debug option, if such status messages are not desired.
C1165E
Message Format
C1165E: Can't run Java Virtual Machine: 'cause'
Message Cause
The ASN.1 compiler could not run the Java virtual machine (JVM). The JVM is used by the ASN.1/C# compiler to produce C# output files after the initial ASN.1 syntax checking. The Sun JVM is copied into the Windows system32 directory which is in the system PATH and nothing special is required to be done on Windows after installing the Sun Java runtime. If the JAVA_HOME environment variable is already set or will be set, the OSS ASN.1/C# compiler expects that the JAVA_HOME environment variable points to the location of the Sun Java runtime home directory, that is where the Sun Java bin, lib, etc. subdirectories are located. For example:
C:\Program Files\Java\j2re1.4.2_09
Otherwise the JVM location must be set in the PATH environment variable. The compiler also expects that the OSS .jar files are accessible at compilation time. On Windows, the default installation location is the Program Files\OSS directory. If the default installation directory is selected, then the OSS_CSHARP_HOME environment variable must point to:
C:\Program Files\OSS\asn1csharp\win32\<version#>
where <version#> is the release version number.
Possible Solution
If the OSS command-prompt console window is used, nothing special is required on Windows. If not, check if the environment variables JAVA_HOME, PATH, and OSS_CSHARP_HOME are correctly set to access the JVM and the OSS .jar files.
A1166E
Message Format
A1166E: The 'PropertySettingsList' contains more than one setting for the property 'Property-name'.
Message Cause
More than one setting was specified for properties of Basic, Date, Year, Time, Local-or-UTC, Interval-type, SE-point, Recurrence, or Midnight in the PropertySettings syntax.
Example
Module-A1166E DEFINITIONS ::= BEGIN T ::= TIME (SETTINGS "Date=Y Year=Negative Date=YM") END
Error Message
"a1166e.asn", line 6 (Module-A1166E): A1166E: The 'PropertySettingsList' contains more than one setting for the property 'Date'.
T ::= TIME (SETTINGS "Date=Y Year=Negative Date=YM")
Possible Solution
Remove the extra settings.
A1167W
Message Format
A1167E: A setting for the property '[Time|Local-or-UTC|Interval-type|SE-point|Recurrence|Midnight]' is ignored because all abstract values with 'Basic=Date' are dates only.
A1167E: A setting for the property '[Date|Year|Interval-type|SE-point|Recurrence]' is ignored because all abstract values with 'Basic=Time' are time-of-days only.
A1167E: A setting for the property 'Interval-type|SE-point|Recurrence]' is ignored because all abstract values with 'Basic=Date-Time' are dates and time-of-days only.
A1167E: A setting for the property 'Recurrence' is ignored because all abstract values with 'Basic=Interval' are time intervals only.
Message Cause
The specified property conflicts with the setting of the Basic property, therefore the set of abstract values of this time type will be empty.
Example
Module-A1167E DEFINITIONS ::= BEGIN
T1 ::= TIME (SETTINGS "Basic=Date Time=HMS Year=Negative")
T2 ::= TIME (SETTINGS " Date=Y
Year=Proleptic
Time=H
Interval-type=D
SE-point=Date
Recurrence=Unlimited
Midnight=End
Basic=Time")
T3 ::= TIME (SETTINGS "Basic=Date-Time SE-point=Date")
T4 ::= TIME (SETTINGS "Basic=Interval Recurrence=Unlimited")
END
Error Message
"a1167w.asn", line 6 (Module-A1167W): A1167W: A setting for the 'Time' property is ignored because all abstract values with 'Basic=Date' are dates only.
T1 ::= TIME (SETTINGS "Basic=Date Time=HMS Year=Negative")
"a1167w.asn", line 14 (Module-A1167W): A1167W: A setting for the 'Date', 'Year','Interval-type', 'SE-point', 'Recurrence' property is ignored because all abstract values with 'Basic=Time' are time-of-days only.
Basic=Time")
"a1167w.asn", line 7 (Module-A1167W): A1167W: A setting for the 'SE-point' propety is ignored because all abstract values with 'Basic=Date-Time' are dates and time-of-days only.
T3 ::= TIME (SETTINGS "Basic=Date-Time SE-point=Date")
"a1167w.asn", line 7 (Module-A1167W): A1167W: A setting for the 'Recurrence' property is ignored because all abstract values with 'Basic=Interval' are time intervals only.
T4 ::= TIME (SETTINGS "Basic=Interval Recurrence=Unlimited")
Possible Solution
Remove the setting or change the settings of the Basic property.
A1168E
Message Format
A1168E: 'tstring' contains at least one invalid character 'character'.
Message Cause
The time value character string lexical item, tstring, must consist of one or more of the characters: 0 1 2 3 4 5 6 7 8 9 + - : . , / C D H M R P S T W Y Z.
Example
Module-A1168E DEFINITIONS ::= BEGIN T ::= TIME t T ::= "1949#20" END
Error Message
"a1168e.asn", line 6 (Module-A1168E): A1168E: 'tstring' contains at least one invalid character '#'.
t T ::= "1949#20"
Possible Solution
Remove invalid characters.
A1169E
Message Format
A1169E: The number identifying the recurrence digits after 'R' must be 1, 2, 3, etc or empty in the time value "tstring" in the valuereference 'name'.
Example
Module-A1169E DEFINITIONS ::= BEGIN T ::= TIME interval T ::= "R0/1985Y/1999Y" END
Error Message
"a1169e.asn", line 6 (Module-A1169E): A1169E: The number identifying the recurrence digits after 'R' must be 1, 2, 3, etc or empty in the time value "R0/1985Y/1999Y" in the valuereference 'interval'.
Possible Solution
Specify correct recurrence digits or remove the designator "R".
A1170E
Message Format
A1170E: A solidus ('/') is missing after the number of recurrences in the time value "tstring" in the valuereference 'name'.
Example
Module-A1170E DEFINITIONS ::= BEGIN T ::= TIME interval T ::= "R1219-12/2000" END
Error Message
"a1170e.asn", line 6 (Module-A1170E): A1170E: A solidus ('/') is missing after the number of recurrences in the time value "R1219-12/2000" in the valuereference 'interval'
Possible Solution
Add a solidus after the recurrence digits or after 'R' for "Unlimited" recurrence.
A1171E
Message Format
A1171E: The [minutes|seconds|decimal fraction] in the value representing the end of a calendar day "tstring" in the valuereference 'name' shall contain only zeros.
A1171E: The [time difference|UTC designator 'Z'] in the value representing the end of a calendar day "tstring" in the valuereference 'name' shall be absent.
Message Cause
In ISO 8601, midnight is represented "2400" or one with any second or fractional part of a second containing only zero digits.
Example
Module-A1171E DEFINITIONS ::= BEGIN time1 TIME ::= "24:01" time2 TIME ::= "24:00:00+01:00" END
Error Message
"a1171.asn", line 2 (Module-A1171E): A1171E: The minutes in the value
representing the end of a calendar day "24:01" in the valuereference 'time1' shall contain only zeros.
"a1171.asn", line 3 (Module-A1171E): A1171E: The time difference in the value representing the end of a calendar day "24:00:00+01:00" in the valuereference 'time 2' shall be absent.
Possible Solution
Set the minutes and seconds or fractional digits in the midnight value to zero and remove the time difference or UTC designator.
A1172E
Message Format
A1172E: A designation with a fractional part shall be the last one in the duration value "tstring" in the valuereference 'name'.
Message Cause
The duration value contains a designation that is placed after the designation which has a fractional part.
Example
Module-A1172E DEFINITIONS ::= BEGIN duration DURATION ::= "P12345.1113Y0M" END
Error Message
"a1172e.asn", line 6 (Module-A1172E): A1172E: A designation with a fractional part shall be the last one in the duration value "P12345.1113Y0M" in the valuereference 'duration'.
Possible Solution
Remove additional designation components from the duration value ("0M", in the example above) or remove the fractional part from the previous (year) designation.
A1173E
Message Format
A1173E: The century component of the time value "tstring" in the valuereference 'name' shall have at least 2 digits".
A1173E: The year component of the time value "tstring" in the valuereference 'name' shall have at least 4 digits".
A1173E: The [month|day of month|hour|minute|second] component of the time value "tstring" in the valuereference 'name' shall have 2 digits".
A1173E: The day of the ordinal date component of the time value "tstring" in the valuereference 'name' shall have 3 digits".
A1173E: The negative century component of the time value "tstring" in the valuereference 'name' shall be between -99 and -00.
A1173E: The negative year component of the time value "tstring" in the valuereference 'name' shall be between -9999 and -0001.
A1173E: The month component of the time value "tstring" in the valuereference 'name' shall be between 01 and 12.
A1173E: The day of month component of the time value "tstring" in the valuereference 'name' shall be between 01 and 31.
A1173E: The day in the common year of the ordinal date component of the time value "tstring" in the valuereference 'name' shall be between 001 and 365.
A1173E: The day in the leap year of the ordinal date component of the time value "tstring" in the valuereference 'name' shall be between 001 and 366.
A1173E: The hour component of the time value "tstring" in the valuereference 'name' shall be between 00 and 24.
A1173E: The minute component of the time value "tstring" in the valuereference 'name' shall be between 00 and 59.
A1173E: The second component of the time value "tstring" in the valuereference 'name' shall be between 00 and 60.
A1173E: The decimal representation with less than 5 digits of the year component of the time value "tstring" in the valuereference 'name' shall be between 0000 and 9999.
A1173E: The negative decimal representation with less than 5 digits of the year component of the time value "tstring" in the valuereference 'name' shall be between -9999 and -0001.
A1173E: The decimal representation with less than 3 digits of the century component of the time value "tstring" in the valuereference 'name' shall be between 00 and 99.
A1173E: The negative decimal representation with less than 3 digits of the century component of the time value "tstring" in the valuereference 'name' shall be between -99 and -01.
Message Cause
The number of digits or their value is incorrect in the specified date or time of day component.
Example
Module-A1173E DEFINITIONS ::= BEGIN date1 DATE ::= "-100C" date2 DATE ::= "1C" date3 DATE ::= "-01985-04-12" date4 TIME ::= "985-123:45" date5 DATE ::= "0000-0" date6 DATE ::= "0000-0123" END
Error Message
"a1173e.asn", line 2 (Module-A1173E): A1173E: The negative century component of the time value "-100C" in the valuereference 'date1' shall be between -99 and -01.
"a1173e.asn", line 3 (Module-A1173E): A1173E: The century component of the time value "1C" in the valuereference 'date2' shall have at least 2 digits.
"a1173e.asn", line 4 (Module-A1173E): A1173E: The negative year component of the time value "-01985-04-12" in the valuereference 'date3' shall be between -9999 and -0001.
"a1173e.asn", line 5 (Module-A1173E): A1173E: The year component of the time value "985-123:45" in the valuereference 'date4' shall have at least 4 digits.
"a1173e.asn", line 6 (Module-A1173E): A1173E: The month component of the time value "0000-0" in the valuereference 'date5' shall have 2 digits.
"a1173e.asn", line 7 (Module-A1173E): A1173E: The day of the ordinal date component of the time value "0000-0123" in the valuereference 'date6' shall have 3 digits.
Possible Solution
Correct the value.
A1174E
Message Format
A1174E: The interval component in the time value "tstring" in the valuereference 'name' incorrectly specified durations as the start and end points.
Message Cause
The interval component may not have durations as start and end points.
Example
Module-A1174E DEFINITIONS ::= BEGIN interval TIME ::= "R/P1219Y/P2000Y" END
Error Message
"a1174e.asn", line 6 (Module-A1174E): A1174E: The interval component in the time value "R/P1219Y/P2000Y" in the valuereference 'interval' incorrectly specified durations as the start and end points.
Possible Solution
A duration component starting with "P" may appear either before or after a solidus ("/") but not in both places in an interval value.
A1175E
Message Format
A1175E: A recurring interval with the start point component shall have either duration or the end point component after the solidus ('/') in the time value "tstring" in the valuereference 'name'.
Message Cause
The time value that starts with a recurrence designator ("R") and a start point component must have an end point component or duration after the solidus.
Example
Module-A1175E DEFINITIONS ::= BEGIN interval TIME ::= "R/1219Y" END
Error Message
"a1175e.asn", line 6 (Module-A1175E): A1175E: The recurring interval with the start point component shall have either duration or the end point component after the solidus ('/') in the time value "R/1219Y" in the valuereference 'interval'.
Possible Solution
Add a duration or end point component or remove the recurrence designator ("R").
A1176E
Message Format
A1176E: The time value "tstring" in the valuereference 'name' contains extra characters 'tstring' that are not associated with any date or time of day component.
Message Cause
The time value contains extra characters at the end of the "tstring" which do not belong to any time component.
Example
Module-A1176W DEFINITIONS ::= BEGIN date DATE ::= "0000-12-31-0" END
Error Message
"a1176e.asn", line 2 (Module-A1176W): A1176E: The time value "0000-12-31-0" in the valuereference 'date' contains extra characters '-0' that are not associated with any date or time component.
Possible Solution
Remove extra characters that appear at the end of the time value.
A1177E
Message Format
A1177E: A weeks designation shall be the last one in the date part of the duration component in the value "tstring" in the value reference 'name'.
A1177E: A days designation shall be the last one in the date part of the duration component in the value "tstring" in the value reference 'name'.
A1177E: A seconds designation shall be the last one in the time part of the duration component in the value "tstring" in the value reference 'name'.
Message Cause
One or more digits appear after a week, day or second designation in the duration component. The designations must be the last ones in the date or time part of the duration.
Example
Module-A1177E DEFINITIONS ::= BEGIN d1 DURATION ::= "P12345Y123D1234M" d2 DURATION ::= "P12345Y123DT0S1H" d3 TIME ::= "P1234W1D" END
Error Message
"a1177e.asn", line 6 (Module-A1177E): A1177E: A days designation shall be the last one in the date part of the duration component in the value "P12345Y123D1234M" in the value reference 'd1'.
"a1177e.asn", line 7 (Module-A1177E): A1177E: A seconds designation shall be the last one in the time part of the duration component in the value "P12345Y123DT0S1H" in the value reference 'd2'.
"a1177e.asn", line 7 (Module-A1177E): A1177E: A weeks designation shall be the last one in the date part of the duration component in the value "P1234W1D" in the value reference 'd3'.
Possible Solution
Remove extra designations from the duration value.
A1178E
Message Format
A1178E: An integral part of the [year|weeks|months|days|hours |minutes|seconds|unknown] designation of the value "tstring" in the valuereference 'name' shall contain at least one digit.
A1178E: An integral part of the [year|weeks|months|days|hours |minutes|seconds|unknown] designation of the value "tstring" in the valuereference 'name' shall contain at least one digit before '.' or ','.
A1178E: A fractional part of the [year|weeks|months|days|hours |minutes|seconds|unknown] designation of the value "tstring" in the valuereference 'name' shall contain at least one digit.
Message Cause
Any duration designation must contain at least one digit if no fractional part is present and at least one digit before and after a decimal point ("." or ",") if a fractional part is present. An "unknown" designation is printed if a character that is specified after digits doesn't match any valid designator.
Example
Module-A1178E DEFINITIONS ::= BEGIN d1 DURATION ::= "P12345Y123DTS" d2 DURATION ::= "P123WT10H0M.0S" d3 DURATION ::= "P123WT10H23.S" END
Error Message
"a1178e.asn", line 6 (Module-A1179E): A1178E: An integral part of the the seconds designation of the value "P12345Y123DTS" in the valuereference 'd1' shall contain at least one digit.
"a1178e.asn", line 7 (Module-A1178E): A1178E: An integral part of the the seconds designation of the value "P123WT10H0M.0S" in the valuereference 'd2' shall contain at least one digit before '.' or ','.
"a1178e.asn", line 7 (Module-A1178E): A1178E: A fractional part of the the seconds designation of the value "P123WT10H23.S" in the valuereference 'd3' shall contain at least one digit.
Possible Solution
Add a digit, ("0"), to complete a designation value.
A1179E
Message Format
A1179E: An integral part of a [year|weeks|months|days|hours |minutes|seconds|unknown] designation of the value "tstring" in the valuereference 'name' shall not contain leading zeros.
Message Cause
Any duration designation must not contain leading zeros. An "unknown" designation is printed if a character that is specified after the digits doesn't match any valid designator.
Example
Module-A1179E DEFINITIONS ::= BEGIN d DURATION ::= "P12345Y00123M" END
Error Message
"a1179e.asn", line 6 (Module-A1179E): A1179E: An integral part of a minutes designation of the value "P12345Y00123M" in the valuereference 'd' shall not contain leading zeros.
Possible Solution
Remove leading digits.
A1180E
Message Format
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting one of designators 'W', 'Y', 'M', 'D' but found 'character'.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting one of designators 'W', 'Y', 'M', 'D' but found the end of value.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting one of designators 'M', 'D' but found 'character'.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting one of designators 'M', 'D' but found the end of value.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting one of designators 'H', 'M', 'S' but found 'character'.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting one of designators 'H', 'M', 'S' but found the end of value.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting a designator 'D' but found 'character'.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting a designator 'D' but found the end of value.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting a designator 'S' but found 'character'.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting a designator 'S' but found the end of value.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting a designation part after 'P' but found 'character'.
A1180E: The duration component in the time value "tstring" in the value reference 'name' is invalid: expecting a designation part after 'P' but the end of value'.
Message Cause
An expected designator such as "W", "Y", "M", "D" for the date and "H", "M", or "S" for the time in the duration component is missing.
Example
Module-A1180E DEFINITIONS ::= BEGIN d1 DURATION ::= "PY" d2 DURATION ::= "P1123" d3 DURATION ::= "P123WT10H0M0." END
Error Message
"a1180e.asn", line 6 (Module-A1180E): A1180E: The duration component in the time value "PY" in the value reference 'd1' is invalid: expecting a designation part after 'P' but found 'Y'.
"a1180e.asn", line 7 (Module-A1180E): A1180E: The duration component in the time value "P1123" in the value reference 'd2' is invalid: expecting one of designators 'W','Y','M','D' but found the end of value.
"a1180e.asn", line 8 (Module-A1180E): A1180E: The duration component in the time value "P123WT10H0M0." in the value reference 'd3' is invalid: expecting a designator 'S' but found the end of value.
Possible Solution
Add a designator "W", "Y", "M", or "D" for the date and "H", "M", or "S" for the time.
A1181E
Message Format
A1181E: The UTC designator component shall be the last time component in the value "tstring" in the value reference 'name'.
A1181E: The century component shall be the last time component in the value "tstring" in the value reference 'name'.
Message Cause
The UTC designator or century component must be the last component in the date-time value.
Example
Module-A1181E DEFINITIONS ::= BEGIN time TIME ::= "00:00,123456Z+12:30" date DATE ::= "11CT11:20" END
Error Message
"a1181e.asn", line 6 (Module-A1181E): A1181E: The UTC designator component shall be the last time component in the value "00:00,123456Z+12:30" in the value reference 'time'.
"a1181e.asn", line 7 (Module-A1181E): A1181E: The century component shall be the last time component in the value "11CT11:20" in the value reference 'date'.
Possible Solution
Remove extra characters specified after the UTC or century component.
A1182E
Message Format
A1182E: The time difference component shall not have a [UTC designator|seconds| fractional|time difference] part in the time value "tstring" in the value reference 'name'.
Message Cause
The time difference component must be the exact time difference in minutes if it is not an exact multiple of hours and must not contain other time components.
Example
Module-A1182E DEFINITIONS ::= BEGIN time1 TIME ::= "00:00,123456+12Z" time2 TIME ::= "00:00,123456+12:20:20" time3 TIME ::= "00:00,123456+12:20,20" time4 TIME ::= "00:00,123456+12:20+20" END
Error Message
"a1182e.asn", line 6 (Module-A1182E): A1182E: The time difference component shall not have a UTC designator part in the time value "00:00,123456+12Z" in the value reference 'time1'.
"a1182e.asn", line 7 (Module-A1182E): A1182E: The time difference component shall not have a seconds part in the time value "00:00,123456+12:20:20" in the value reference 'time2'.
"a1182e.asn", line 8 (Module-A1182E): A1182E: The time difference component shall not have a fractional part in the time value "00:00,123456+12:20,20" in the value reference 'time3'.
"a1182e.asn", line 6 (Module-A1182E): A1182E: The time difference component shall not have a time difference part in the time value "00:00,123456+12:20+20" in the value reference 'time4'.
Possible Solution
Remove extra characters specified after the time difference component.
A1183E
Message Format
A1183E: A hyphen ('-') shall be used within the date component expression in the time value "tstring" in the value reference 'name'.
Message Cause
A separator ":" is specified within a year-month-day component instead of "-".
Example
Module-A1183E DEFINITIONS ::= BEGIN date-time DATE ::= "-1985:12:31T06:59:59" END
Error Message
"a1183e.asn", line 6 (Module-A1183E): A1183E: A hyphen ('-') shall be used within the date component expression in the time value "-1985:12:31T06:59:59" in the value reference 'date-time'.
Possible Solution
Replace ":" with "-" in the date expression.
A1184E
Message Format
A1184E: A character 'T' can be used as a separator only in the date-time value, a date component is absent in the time value "tstring" in the value reference 'name'.
Message Cause
A character "T" must not appear at the beginning of the time value.
Example
Module-A1184E DEFINITIONS ::= BEGIN date-time DATE ::= "T12:00:01" END
Error Message
"a1184e.asn", line 6 (Module-A1184E): A1184E: A character 'T' can be used as a separator only in the date-time value, a date component is absent in the time value "T12:00:01" in the value reference 'date-time'.
Possible Solution
Remove "T" or add a date component in front of it.
A1185E
Message Format
A1185E: The time value "tstring" in the value reference 'name' is invalid: expecting digits of the year or time component but found 'character'.
A1185E: The time value "tstring" in the value reference 'name' is invalid: expecting digits of the year or time component but found end of the value.
Message Cause
You have not specified digits of the year or time component.
Example
Module-A1185E DEFINITIONS ::= BEGIN date-time1 DATE ::= ":1985-12T06:59:59" date-time2 TIME ::= "R/" END
Error Message
"a1185e.asn", line 6 (Module-A1185E): A1185E: The time value ":1985-12T06:59:59" in the value reference 'date-time1' is invalid: expecting digits of the year or time component but found ':'.
"a1185e.asn", line 7 (Module-A1185E): A1185E: The time value "R/" in the value reference 'date-time2' is invalid: expecting digits of the year or time component but found end of the value.
Possible Solution
Specify the digits.
A1186E
Message Format
A1186E: A time of day component with the separator 'T' shall be absent because a day is not specified in the date component in the time value "tstring" in the value reference 'name'.
Message Cause
The time of day component must be specified only if a day is present in the date component of the date-time value.
Example
Module-A1186E DEFINITIONS ::= BEGIN date-time DATE ::= "-1985T06:59:59" END
Error Message
"a1186e.asn", line 6 (Module-A1186E): A1186E: A time of day component with the separator 'T' shall be absent because a day is not specified in the date component in the time value "-1985T06:59:59" in the value reference 'date-time'.
Possible Solution
Remove the time component or add a day component.
C1187I
Message Format
C1187I: Configuration file: filename
Message Cause
The -debug <nonzero> option was specified.
Possible Solution
Make sure you do not specify the -debug option.
A1188W
Message Format
A1188W: The VARYING directive is not supported for BMPString/UniversalString types. The UNBOUNDED representation is used for <typename>.
Message Cause
The VARYING directive applied to a BMPString or UniversalString type. The directive cannot be applied to these types.
Example
Module-A1188W DEFINITIONS ::= BEGIN BMPS ::= BMPString (SIZE(12)) --<VARYING>-- UnS ::= UniversalString (SIZE(12)) --<VARYING>-- END
Error Message
"a1188w.asn", line 2 (Module-A1188W): A1188W: The VARYING directive is not supported for BMPString/UniversalString types; the UNBOUNDED representation is used for 'BMPS'.
"a1188w.asn", line 3 (Module-A1188W): A1188W: The VARYING directive is not supported for BMPString/UniversalString types; the UNBOUNDED representation is used for 'UnS'.
Possible Solution
Remove the compiler directive.
C1189E
Message Format
C1189E: The ASN.1 component is represented as an [attribute|element] 'identifier1' in the Extended XER encoding. The encoding instruction(s) 'instructions list' are not supported for such a component by the ASN.1 to XML Schema Extended XER generator.
Message Cause
The input ASN.1 syntax contains an E-XER instruction which is not supported. The ASN.1 to XSD translator in E-XER mode has limited support for E-XER instructions. For a list of supported XER encoding instructions, see the doc/README.TXT file included in the ASN.1 to XSD translator shipment.
Example
M DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
PDU1 ::= SEQUENCE {
a [UNTAGGED] OCTET STRING
b [ATTRIBUTE] INTEGER
}
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1189e.asn", line 3 (M): C1189E: The ASN.1 component is represented as an element 'a' in the Extended XER encoding. The encoding instruction(s) UNTAGGED are not supported for such a component by the ASN.1 to XML Schema Extended XER generator.
Possible Solution
If you need more information about supporting the encoding instructions, contact Technical Support ‹support@oss.com› .
C1190E
Message Format
C1190E: The GLOBAL-DEFAULTS XER encoding instruction with the MODIFIED-ENCODINGS setting should be either applied to all input ASN.1 modules or should be absent when XML Schemas for Extended XER encodings are generated. Two ASN.1 modules 'identifier1' and 'identifier2' violate this restriction.
Message Cause
The input ASN.1 syntax contains a pair of modules with different MODIFIED-ENCODINGS settings. All ASN.1 modules must have MODIFIED-ENCODINGS instructions.
Example
M1 DEFINITIONS AUTOMATIC TAGS ::= BEGIN
PDU1 ::= INTEGER
END
M2 DEFINITIONS AUTOMATIC TAGS ::= BEGIN
IMPORTS PDU1 FROM M1;
PDU2 ::= INTEGER
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1190e.asn" (M2): C1190E: The GLOBAL-DEFAULTS XER encoding instruction with the MODIFIED-ENCODINGS setting should be either applied to all input ASN.1 modules or should be absent when XML Schemas for Extended XER encodings are generated. Two ASN.1 modules 'M2' and 'M1' violate this restriction.
Possible Solution
Make sure all modules have the same MODIFIED-ENCODINGS setting. If you need more information about removing the restriction, contact Technical Support ‹support@oss.com› .
C1191W
Message Format
C1191W: No automatic encoding/decoding will be performed for the 'type_name' type with ContentsConstraint since the 'OSS.NoConstrain' directive is applied to the type.
Message Cause
A type with a contents constraint in the input syntax has a OSS.NoConstrain directive which prevents generation of constraint data needed for automatic encoding or decoding.
Example
--<OSS.NoConstrain C1191W.OS>--
C1191W DEFINITIONS ::= BEGIN
OS ::= OCTET STRING (
CONTAINING SEQUENCE OF INTEGER
ENCODED BY { 2 1 1 }
)
END
Error Message
"c1191w.asn", line 3 (C1191W): C1191W: No automatic encoding/decoding will be performed for the 'OS' type with ContentsConstraint since the 'OSS.NoConstrain' directive is applied to the type.
Possible Solution
Remove the directive.
A1192E
Message Format
A1192E: The content model of the extensible complex type '<identifier>' is ambiguous: <description of conflicting particles>. Through the use of optionality they may appear at the same place within an encoding. This makes it impossible for a decoder to distinguish an extension addition from the root element when using an earlier version of the type definition.
Message Cause
The input ASN.1 syntax results in ambiguous XML encodings. An extensible SEQUENCE type and data sent by the application using a newer version of its definition may be interpreted incorrectly by the application that uses an earlier version of this type.
Example
M DEFINITIONS XER INSTRUCTIONS AUTOMATIC TAGS ::= BEGIN
Type1 ::= [TAG:1] SEQUENCE {
...,
a [NAME AS "c"] INTEGER,
b INTEGER,
...,
c INTEGER
}
END
Error Message
"a1192e.asn", line 3 (M): A1192E: The content model of the extensible complex type 'Type1' is ambiguous: there are two elements from the same namespace 'ABSENT' with the same local name 'c'. Through the use of optionality they may appear at the same place within an encoding. This makes it impossible for a decoder to distinguish an extension addition from the root element when using an earlier version of the type definition.
Possible Solution
Make sure you do not define ambiguous extensible types because they may generate interoperability problems for applications that use different versions of the type. Rename one of the conflicting XML particles (preferably the one in the extension additions section, as the one in the root section might be used by existing applications).
C1193W
Message Format
C1193W: You are not licensed to use 'ENCODING RULE'. The option ' option' is ignored. Please contact OSS Nokalva, Inc. to obtain the new license that supports 'ENCODING RULE'.
Message format when using the compiler GUI
C1193W: You are not licensed to use 'ENCODING RULE'. The corresponding check box within the "Encoding rules available at run-time" group from the "Runtime Control" tab of the "Compiler Options" window is ignored. Please contact OSS Nokalva, Inc. to obtain the new license that supports 'ENCODING RULE'.
Message Cause
You do not have a license for using the encoding rule specified in the ASN.1 compiler command line.
Example
asn1 -per foo.asn
Error Message
C1193W: You are not licensed to use PER. The option '-per' is ignored. Please contact OSS Nokalva, Inc. to obtain the new license that supports PER.
Possible Solution
Remove the option or contact Sales ‹info@oss.com› to receive a new license.
C1194E
Message Format
C1194E: You are not licensed to use encoding rules specified on the command line. No output files can be produced. Please contact OSS Nokalva, Inc.
Message format when using the compiler GUI
C1194E: You are not licensed to use encoding rules checked within the "Encoding rules available at run-time" group in the "Runtime Control" tab of the "Compiler Options" window. No output files can be produced. Please contact OSS Nokalva, Inc. to obtain the new license that supports these encoding rules.
Message Cause
You do not have a license for generating code for the specified encoding rules.
Possible Solution
Make sure the OSSINFO environment variable points to the correct version of the ossinfo file that permits use of the specified encoding rules. If you don't have an ossinfo file, Sales ‹info@oss.com› to receive a new license.
C1196W
Message Format
C1196W: The value '%s' of the REAL type with the OSS.FLOAT directive does not fit in a single-precision floating number.
Message Cause
A value of REAL type cannot fit in a single-precision floating number without the value precision loss due to the type conversion.
Example
Module-C1196W DEFINITIONS ::= BEGIN
F ::= REAL --<FLOAT>--
f F ::= {1,2,200}
END
Error Message
"c1196w.asn", line 3 (Module-C1196W): C1196W: The value 'f' of the REAL type with the OSS.FLOAT directive does not fit in a single-precision floating number.
Possible Solution
Remove the directive from the definition of REAL type. Instead, use OSS.DOUBLE directive.
C1197I
Message Format
C1197W: Your trial <license_info> license is expired. As a courtesy, OSS will let it continue to run for <N> more days. Please contact sales@oss.com to purchase the tools.
Message Cause
Your current trial license for using the ASN.1 compiler or runtime will expire in <N> days.
Possible Solution
For information about purchasing the tools, contact Sales ‹info@oss.com›.
C1198E
Message Format
C1198E: COMPILER ERROR #65.
Message Cause
The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.
Next Action
Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.
C1202W
Message Format
C1202W: The helper mode is overridden by the '%s' compatibility flag. The traditional naming rules are implied and no support for helper macros and functions is available. Please remove the compatibility flag if you want to use helper names, macros, or functions.
Message format when using the compiler GUI
C1202W: The helper mode is overridden by the 'flag' compatibility flag. The traditional naming rules are implied and no support for helper macros and functions is available. Please uncheck the corresponding box in the scroll down menu within the "Compatibility options" group in the "Output Files" tab of the "Compiler Options" window if you want to use helper names, macros, or functions.
Message Cause
The compatibility flag used with the compiler has disabled helper mode. All version compat flags v7.0.0 and earlier will disable helper mode.
C1203I
Message Format
C1203I: The '%s' compatibility flag is assumed in the helper mode and has no effect, please remove it from the compiler command line.
Message Cause
If the v5.1typesharing and/or noSharedTypes feature compat flags are called in helper mode, the informatory message above is issued and the helper mode remains active.
C1204W
Message Format
C1204W: The '%s' compatibility flag may produce unexpected results in the helper mode. Consider either using the '-noHelperAPI' option or removing the compatibility flag from the compiler command line.
Message format when using the compiler GUI
C1204W: The 'flag' compatibility flag may produce unexpected results in the helper mode. Consider either unchecking the corresponding box in the scroll down menu within the "Compatibility options" group in the "Output Files" tab of the "Compiler Options" window or checking the "Do not generate context-based names, helper- and helper list API macros" box within the "Helper Options" group in the "More Options" tab of the "Compiler Options" window.
Message Cause
When the following sharing-related feature compat flags are used, the warning is issued and the helper mode remains active:
- noParamTypesharing
- oldParamTypesharing
- oldSharingFieldsWithDirectives
- v4.1typesharing
- v4.2.5typesharing
- v5.1parameterizedTypes
- v5.2noExtraParamRef
- v5.2sharing
- v5.2typesharing
When the following feature compat flags are used, the warning is issued and the helper mode remains active.
- nestunions
- allowUnnamed
- badExternalPrefix
- extSizeNotUnbounded
- extraLinkedSETOFPointer
- implicitTypeInArray
- charUTF8String
- oldNamesManglingWithPrefix
- padded
- paddedForNamedBits
- badpaddedutf8string
- typedefsForGenNames
- unnamedStructForConstrBy
- v4.1.6extraLinkedSETOFPtr
- v4.2badSetOfWithGlobalDir
- v4.2defaults
- v4.2objHandleCstrPointer
- v4.2octetStringDefault
- v5.1extraPointer
- v5.1unnamedStructForConstrBy
- v5.2paramNickName
- v6.0stringswithMAXsize
- v6.1.3varyingbitstring
- v6.1.4DefineNameSharing
- v6.1.4extrapointer
- v6.1.4ReferencesToLeanTypes
- oldObjectNames
- unbndBit
- badLengthDirectives
- badNameConflicts
- badRefNames
- badSetOfOidWithPointer
- badTypedefsForUserNames
- badTYPENAMEdirectives
- badUnderscorePrefix
- badValuePrefix
- extensionWithMask
- extraNameShortening
- ignoreNicknamesInConflictResolution
- intEnums
- noBTypeValues
- noDecoupledNames
- noMacroArgumentPDUs
- noObjectSetsFromDummyObjects
- noOssterm
- noULength
- oldBooleanType
- oldEncodableNames
- oldExternObjHdl
- oldInternalDefineNames
- v4.1.6encodable
- v4.2badUnderscorePrefix
- v4.2namesForOpenTypes
- v4.2nicknames
- v5.0.0badNamesForNamedItems
- v5.0.0namesPrefixes
- v5.0.0nicknames
- v5.2nestedUsethisTypes
- v5.2paramRangeConstraints
- v5.4integer
Possible Solution
You can either remove the compatibility flag or use the noHelperAPI option.
A1207E
Message Format
A1207E The 'RootComponentTypeList' of the type 'Type1' used in the COMPONENTS OF notation within 'Type2' shall not be empty.
Message Cause
The ASN.1 standard has been changed to forbid a COMPONENTS OF in all cases where there is an empty root in the Type referenced in the COMPONENTS OF construction.
Example
Module-A1207 DEFINITIONS ::= BEGIN
T ::= SEQUENCE {a [0] NULL, ..., [[ COMPONENTS OF W ]], ..., b [5] NULL}
W ::= SEQUENCE {..., c [1] NULL,...}
END
Error Message
"a1207e.asn", line 2 (Module-A1207): A1207E: The 'RootComponentTypeList' of the type 'W' used in the COMPONENTS OF notation within 'T' shall not be empty.
Possible Solution
Remove the COMPONENTS OF or specify the -ignoreError 1207 option to generate a warning instead of an error. Note that problems with encodings might occur if the only component in a components addition is a COMPONENTS OF that has no root and no extension additions.
A1208E
Message Format
A1208E: The field 'name', which is an extension addition in the type 'Type', is skipped by the 'COMPONENTS OF Type' notation. The value of this field shall be absent.
Message Cause
Extension markers and extension additions, if any, are ignored by the "COMPONENTS OF Type" notation. The value of the type containing COMPONENTS OF includes a value for an extension addition from the type referenced in the COMPONENTS OF.
Example
Module-A1208 DEFINITIONS ::= BEGIN
T ::= SEQUENCE {a [0] NULL, ..., [[ COMPONENTS OF W ]], ..., b [5] NULL}
W ::= SEQUENCE {..., c [1] NULL,...}
t T ::= {a NULL, c NULL, b NULL}
END
Error Message
"a1208e.asn", line 4 (Module-A1208): A1208E: The field 'c', which is an extension addition in the type 'W', is skipped by the 'COMPONENTS OF W' notation. The value of this field shall be absent.
t T ::= {a NULL, c NULL, b NULL}
Possible Solution
Remove the value.
A1209E
Message Format
A1209E: The 'Value' syntax references a non-existent or skipped by 'COMPONENTS OF' field 'name'.
Message Cause
Extension markers and extension additions, if any, are ignored by the "COMPONENTS OF Type" notation. The value of the type containing COMPONENTS OF incorrectly includes a value for an extension addition from the type referenced in the COMPONENTS OF.
Example
Module-A1209 DEFINITIONS ::= BEGIN
Param{Type} ::= SEQUENCE { COMPONENTS OF Type }
Seq ::= Param{SEQUENCE { ..., a INTEGER, ..., b INTEGER} }
s Seq ::= {a 10, b 20}
END
Error Message
"a1209e.asn", line 4 (Module-A1209): A1209E: The 'Value' syntax references a non-existent or skipped by 'COMPONENTS OF' field 'a'.
Possible Solution
Remove the value.
See Also
A1211E
Message Format
A1211E: The reference name 'Name' is incorrectly assigned to 'ObjectSet' using the 'TypeAssignment'.
A1211E: The reference name 'Name' is incorrectly assigned to 'ParameterizedObjectSet' using the 'TypeAssignment'.
Message Cause
To assign a reference name to an ObjectSet, you must use the ObjectSetAssignment. For more information, see ITU-T Rec. X.681 clause 12.1:
ObjectSetAssignment ::=
objectsetreference DefinedObjectClass "::=" ObjectSet
ObjectSet ::= "{" ObjectSetSpec "}"
Example
Module-A1211 DEFINITIONS ::= BEGIN
MYCLASS ::= CLASS {
&SetField MYCLASS OPTIONAL,
&code INTEGER
}
ParamObjectSet { MYCLASS: ParamSet } MYCLASS ::= {
ParamSet.&SetField }
ObjectSet ::= ParamObjectSet { { classTypeValue, ... } }
classTypeValue MYCLASS ::= { &code 1 }
END
Error Message
"a1211e.asn", line 11 (Module-A1211): A1211E: The reference name 'ObjectSet' is incorrectly assigned to 'ParameterizedObjectSet' using the 'TypeAssignment'.
ObjectSet ::= ParamObjectSet { { classTypeValue, ... } }
Possible Solution
Replace the syntax with the ObjectSetAssignment as follows or use the -ignoreError 1211 option.
ObjectSet MYCLASS ::= { ParamObjectSet { { classTypeValue, ... } } }
A1213E
Message Format
A1213E: The CONTAINING value can only be used if there is a ContentsConstraint on the [bit|octet] string which includes CONTAINING, check the value 'value_name'.
Message Cause
A CONTAINING alternative of a BIT STRING or OCTET STRING value was encountered while parsing the input ASN.1 syntax, but the corresponding type was not constrained using ContentsConstraint. These problems may occur with complex InnerSubtype constructions.
Error Message
"a1213e.asn", line 2 (Module-A1213E): A1213E: The CONTAINING value can only be used if there is a ContentsConstraint on the bit string which includes CONTAINING, check the value 'val'.
Possible Solution
Add ContentsConstraint to the appropriate BIT STRING or OCTET STRING type or change the value to a bstring or hstring.
A1214E
Message Format
A1214E: A ContentsConstraint has been applied to the type 'TypeName' more than once.
Message Cause
A ContentsConstraint was applied to the specified type more than once using an InnerSubtype notation from one of the enclosing parent types.
Example
H1 ::= SEQUENCE {
encoding OCTET STRING (CONTAINING INTEGER)}
H1-1 ::= H1 (WITH COMPONENTS {encoding (CONTAINING BOOLEAN)})
Error Message
"a1214e.asn", line 13 (Module-A1214E): A1214E: A ContentsConstraint has been applied to the type 'H1-1' more than once.
Possible Solution
Remove the extra CONTAINING syntax.
C1215W
Message Format
C1215W: The definition of the [type|value] identified by the absolute reference 'AbsRef' is incomplete and will be ignored.
C1215W: The definition of the parameterized [type|value] identified by the absolute reference 'AbsRef' is incomplete and will be ignored.
Message Cause
This warning is issued if the -ignoreIncompleteItems option is specified with verbose, and the input syntax contains undefined types or values. It is issued for all incomplete items that are ignored because they directly or indirectly reference undefined items or incomplete items.
Example
C1215W DEFINITIONS ::= BEGIN
A ::= SEQUENCE {
a1 A1,
a2 A2,
b B1
}
A1 ::= INTEGER
A2 ::= BOOLEAN
B ::= REAL
END
Error Message
"c1215w.asn", line 4 (C1215W): C1215W: The definition of the type identified by the absolute reference 'C1215W.A' is incomplete and will be ignored.
Possible Solution
The warning message can be ignored. To suppress the warning, make sure you do not specify verbose. The compiler can issue errors instead of warnings for undefined types. To do this, make sure you do not specify the -ignoreIncompleteItems option.
A1217W
Message Format
A1217W: ASN.1 supports time differences from UTC in the range -15 to +16 hours only, check the time value "tstring" in the valuereference 'name'.
Example
Module-A1217W DEFINITIONS ::= BEGIN time TIME ::= "1985-11-06T21:06:27+23:59" END
Error Message
"a1217w.asn", line 3 (A1217W): A1217W: ASN.1 supports time differences from UTC in the range -15 to +16 hours only, check the time value "1985-11-06T21:06:27.3+23:59" in the valuereference 'time'.
Possible Solution
This warning can be ignored. Note that unsupported values might cause problems at runtime.
A1218E
Message Format
A1218E: The [hour|minute] component with a fractional part shall be the last one in the time value "tstring" in the valuereference 'name'.
Message Cause
Time-of-day values may have an accuracy of hours, minutes, or seconds.
Example
Module-A1218E DEFINITIONS ::= BEGIN time TIME ::= "21:06.06:22" END
Error Message
"a1218e.asn", line 20 (A1218E): A1218E: The minute component with a fractional part shall be the last one in the time value "1985-01-01T21:06.06:22-23:59" in the valuereference 'time'.
Possible Solution
Remove the time component.
A1219E
Message Format
A1219E: The start and end points of the interval value "tstring" in the valuereference 'name' shall have the same time properties except a time difference can be omitted in the end point if it is the same as in the start point.
Message Cause
The time properties of the start and end points in the interval value do not match. Note that all properties, including the number of digits in the year component or in the fractional part or if a year is proleptic or basic, must match.
Example
Module-A1219E DEFINITIONS ::= BEGIN interval1 TIME ::= "1985/19C" interval2 TIME ::= "1999-W12-1T12:36.000003/2002-W12-7T12:36.003" END
Error Message
"a1219e.asn", line 2 (Module-A1219E): A1219E: The start and end points of the interval value "1985/19C" in the valuereference 'interval1' shall have the same time properties except a time difference can be omitted in the end point if it is the same as in the start point.
"a1219e.asn", line 3 (Module-A1219E): A1219E: The start and end points of the interval value "2002-W12-1T12:36.000003/1999-W12-7T12:36.003" in the valuereference 'interval2' shall have the same time properties except a time difference can be omitted in the end point if it is the same as in the start point.
Possible Solution
Make sure the start and end point values have the same properties.
A1220E
Message Format
The designator [T] shall be absent if all of the time components are absent in the value "tstring" in the valuereference 'name'.
Message Cause
No time component is listed after the designator [T] in the time value.
Example
Module-A1220E DEFINITIONS ::= BEGIN time1 TIME ::= "1985-121T" time2 TIME ::= "P198YT" END
Error Message
"a1220e.asn", line 2 (Module-A1220E): A1220E: The designator [T] shall be absent if all of the time components are absent in the value "1985-121T" in the valuereference time1'.
"a1220e.asn", line 3 (Module-A1220E): A1220E: The designator [T] shall be absent if all of the time components are absent in the value "P198YT" in the valuereference time2'.
Possible Solution
Remove the extra [T] designator or add values for the time of day components.
A1222E
Message Format
A1222E: A PropertySettings constraint is incorrectly applied to 'Name' that is not a Time type.
Message Cause
A PropertySettings constraint was applied to an ASN.1 type that is not an 8601 Time type.
Example
Module-A1222E DEFINITIONS ::= BEGIN T1 ::= GeneralizedTime (SETTINGS "Basic=Date-Time") T2 ::= UTCTime (SETTINGS "Basic=Date-Time") T3 ::= INTEGER (SETTINGS "Basic=Date-Time") END
Error Message
"a1222e.asn", line 3 (Module-A1222E): A1222E: A PropertySettings constraint is incorrectly applied to 'T1' that is not a Time type.
"a1222e.asn", line 4 (Module-A1222E): A1222E: A PropertySettings constraint is incorrectly applied to 'T2' that is not a Time type.
"a1222e.asn", line 5 (Module-A1222E): A1222E: A PropertySettings constraint is incorrectly applied to 'T3' that is not a Time type.
Possible Solution
Remove the PropertySettings constraint or replace the type to which it is applied with TIME or DATE, DURATION, or a type derived from them.
A1223W
Message Format
A1223W: The 'PropertySettingsList' restricts the type to be represented as a duration only, settings for date and/or time properties will be ignored.
Message Cause
Time and date properties affect values in the start and/or end points in an interval. These properties do not have an effect when the interval type is a duration.
Example
Module-A1223W DEFINITIONS ::= BEGIN T ::= TIME (SETTINGS "Basic=Interval Interval-type=D Year = Proleptic Time = H") END
Error Message
"a1223w.asn", line 3 (Module-A1223W): A1223W: The PropertySettingsList' restricts the type to be represented as a duration only, settings for date and/or time pr operties will be ignored.
T ::= TIME (SETTINGS "Basic=Interval Interval-type=D Year=Proleptic Time=H")
Possible Solution
This warning can be ignored. To suppress it, remove unused property settings from the PropertySettings constraint or replace the interval type with DE, SD, or SE.
A1224W
Message Format
A1224W: The '+' sign shall be specified for the 'Large' years component in the time value "tstring" in the valuereference 'name'.
A1224W: The '+' sign shall not be specified for the '[Basic|Proleptic]'
years component in the time value "tstring" in the valuereference 'name'.
Message Cause
The ISO 8601 format for the Large year component is [-Y..YYYY] or [-Y..YYC]. The format for Basic or Proleptic years is [YYYY] or [YYC] without the "+" sign.
Example
Module-A1224W DEFINITIONS ::= BEGIN v1 TIME ::= "12345" v2 TIME ::= "+12C" v3 TIME ::= "+1999" END
Error Message
"a1224w.asn", line 3 (Module-A1224W): A1224W: The '+' sign shall be specified for the 'Large' years component in the time value "12345" in the valuereference 'v1'.
"a1224w.asn", line 4 (Module-A1224W): A1224W: The '+' sign shall not be specified for the 'Proleptic' years component in the time value "+12C" in the valuereference 'v2'.
"a1224w.asn", line 5 (Module-A1224W): A1224W: The '+' sign shall not be specified for the 'Basic' years component in the time value "+1999" in the valuereference 'v3'.
Possible Solution
This warning can be ignored. To suppress it, remove or add the "+" sign.
C1225E
Message Format
C1225E: COMPILER ERROR #67.
Message Cause
The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.
Next Action
Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.
A1226E
Message Format
A1226E: The values in the 'TimePointRange' shall have identical settings for all time properties except 'Midnight' and shall have the same time differences if there is a property setting of 'Local-or-UTC=LD'; check range ("tstring1".."tstring2") in Name.
Message Cause
The settings of the time properties of the lower and upper bound values specified in the "TimePointRange" do not match. The settings of all properties, including the number of digits in the year component, or in the fractional part, or if a year is proleptic or basic, must match - except for the Midnight property. The latter may have either the "Start" or "End" setting. Starting with version 8.2, the compiler implements the latest changes in the X.680 standard. An ordered relationship between TIME abstract values, with time of day components that include time differences, exists not only if they have the same properties and the same settings of those properties, but also if they have exactly the same time differences. Note that time differences in the end and start points of intervals may have different values.
Example
Module-A1226E DEFINITIONS ::= BEGIN
T1 ::= TIME ("1999" .."2006-12")
T2 ::= TIME ("1234" .."21:00:00")
T3 ::= TIME ("1234" .."1999")
T4 ::= TIME ("12-14:12" .."15+14:12")
T5 ::= TIME ("12-14:12" .."15+14")
END
Error Message
"a1226e.asn", line 2 (Module-A1226E): A1226E: The values in the 'TimePointRange' shall have identical settings for all time properties except 'Midnight' and shall have the same time differences if there is a property setting of 'Local-or-UTC=LD'; check range ("1999".."2006-12") in T1.
"a1226e.asn", line 3 (Module-A1226E): A1226E: The values in the 'TimePointRange' shall have identical settings for all time properties except 'Midnight' and shall have the same time differences if there is a property setting of 'Local-or-UTC=LD'; check range ("1234".."21:00:00") in T2.
"a1226e.asn", line 4 (Module-A1226E): A1226E: The values in the 'TimePointRange' shall have identical settings for all time properties except 'Midnight' and shall have the same time differences if there is a property setting of 'Local-or-UTC=LD'; check range ("1234".."1999") in T3.
"a1226e.asn", line 5 (Module-A1226E): A1226E: The values in the 'TimePointRange' shall have identical settings for all time properties except 'Midnight' and shall have the same time differences if there is a property setting of 'Local-or-UTC=LD'; check range ("12-14:12".."15+14:12") in T4.
"a1226e.asn", line 6 (Module-A1226E): A1226E: The values in the 'TimePointRange' shall have identical settings for all time properties except 'Midnight' and shall have the same time differences if there is a property setting of 'Local-or-UTC=LD'; check range ("12-14:12".."15+14") in T5.
Possible Solution
Make sure the values in the TimePointRange have identical settings for all properties and the same time differences if a 'Local-or-UTC' property has the setting LD.
A1227E
Message Format
A1227E: The values in the 'DurationRange' shall both specify durations with the same time components and the same accuracy: the least significant components shall be present and be of the same kind; check range ("duration1".."duration2") in 'Name'.
Message Cause
Both the lower and upper bound values specified in the "DurationRange" are not durations that satisfy the following subtype: SETTINGS "Basic=Interval Interval-type=D", or the values do not have the same time components. Time components must have identical values except for the least significant time component (which may have a different value, but must have the same accuracy).
Example
Module-A1227E DEFINITIONS ::= BEGIN
T1 ::= TIME ("P0Y" .."21:00:00")
T2 ::= TIME ("R/P0Y" .."R/P11Y")
T3 ::= TIME ("P1Y0MT20.0S" .. "1994-12-31/2004-12-01")
END
Error Message
"a1227e.asn", line 5 (Module-A1227E): A1227E: The values in the 'DurationRange' shall both specify the duration with the same time components; check range ("P0Y".."21:00:00") in 'T1'.
"a1227e.asn", line 6 (Module-A1227E): A1227E: The values in the 'DurationRange' shall both specify the duration with the same time components; check range ("R/P0Y".."R/P11Y") in 'T2'.
"a1227e.asn", line 7 (Module-A1227E): A1227E: The values in the 'DurationRange' shall both specify the duration with the same time components; check range ("P1Y0MT20.0S" .. "1994-12-31/2004-12-01") in 'T3'.
Possible Solution
Make sure the values in the DurationRange have the same time components.
A1228E
Message Format
A1228E: The 'DurationRange' ("tstring1".."tstring2") in 'Name' is invalid. Values must differ only in the least significant time component and the latter must have the same accuracy.
Message Cause
The lower and upper bound values specified in the "DurationRange" must have the same time components with identical values, except for the least significant time component which may have a different value, but must have the same accuracy (no fractional part, or the same number of digits in the fractional part).
Example
Module-A1228E DEFINITIONS ::= BEGIN
T1 ::= TIME ("P1.0002Y".."P1.002Y")
T2 ::= TIME ("P1Y0MT20.0S" .. "P1YT1H10.5S")
T3 ::= TIME ("P1Y".."P1M")
END
Error Message
"a1228e.asn", line 2 (Module-A1228E): A1228E: The 'DurationRange' ("P1.0002Y".."P1.002Y") in 'T1' is invalid. Values must differ only in the least significant time component and the latter must have the same accuracy.
"a1228e.asn", line 3 (Module-A1228E): A1228E: The 'DurationRange' ("P1Y0MT20.0S".."P1YT1H10.5S") in 'T2' is invalid. Values must differ only in the least significant time component and the latter must have the same accuracy.
"a1228e.asn", line 4 (Module-A1228E): A1228E: The 'DurationRange' ("P1Y".."P1M") in 'T3' is invalid. Values must differ only in the least significant time component and the latter must have the same accuracy.
Possible Solution
Change the values in the DurationRange.
A1229E
Message Format
A1229E: The values in the 'RecurrenceRange' in 'Name' shall be positive
integers or a value of 'MAX'.
Message Cause
The values in the RecurrenceRange constraint the number of recurrence digits specified as settings of the Recurrence property. These values are always positive. An INTEGER value of MAX may be used within the RecurrenceRange to include the setting Recurrence=Unlimited.
Example
Module-A1229E DEFINITIONS ::= BEGIN T1 ::= TIME (-1..200) T2 ::= TIME (MIN..MAX) END
Error Message
"a1229e.asn", line 2 (Module-A1229E): A1229E: The values in the 'RecurrenceRange' in 'T1' shall be positive integers or a value of 'MAX'.
"a1229e.asn", line 5 (Module-A1229E): A1229E: The values in the 'RecurrenceRange' in 'T2' shall be positive integers or a value of 'MAX'.
Possible Solution
Specify positive INTEGERs in the RecurrenceRange.
A1230E
Message Format
A1230E: The 'RecurrenceRange' subtype is not permitted on 'T' because the time type is not constrained to have recurring interval values.
Message Cause
The RecurrenceRange subtype is permitted on time types whose abstract values are also present in the subtype (SETTINGS "Basic=Rec-interval").
Example
Module-A1230E DEFINITIONS ::= BEGIN T ::= DATE (12..20) END
Error Message
"a1230e.asn", line 2 (Module-A1230E): A1230E: The 'RecurrenceRange' subtype is not permitted on 'T' because the time type is not constrained to have recurring interval values.
Possible Solution
Remove the RecurrenceRange or make sure the base type allows recurring intervals.
A1231E
Message Format
A1231E: The 'MAX' value is not permitted in the time range in 'Name'.
A1231E: The 'MIN' value is not permitted in the time range in 'Name'.
Message Cause
The MIN or MAX value was specified within DurationRange or TimePointRange.
Example
Module-A1231E DEFINITIONS ::= BEGIN
T1 ::= TIME ("1245"..MAX)
T2 ::= TIME (MIN.."1245")
END
Error Message
"a1231e.asn", line 2 (Module-A1231E): A1231E: The 'MAX' value is not
permitted in the time range in 'T1'.
"a1231e.asn", line 3 (Module-A1231E): A1231E: The 'MIN' value is not permitted in the time range in 'T2'.
Possible Solution
Specify a valid time value in the DurationRange or TimePointRange.
A1232E
Message Format
C1232E: The time value "tstring" in 'Name' with the large year outside the signed integer range (INT_MIN..INT_MAX) is not currently supported.
Message Cause
A time value includes a Large year component with a value that does not fit within a signed INTEGER type. Currently, these values are not supported for the OSS ASN.1 Tools.
Example
Module-C1232E DEFINITIONS ::= BEGIN
T1 ::= TIME ("+2147483649-12-01")
T2 ::= TIME ("-2147483649-123")
END
Error Message
"a1232e.asn", line 2 (Module-C1232E): C1232E: The time value "+2147483649-12" in 'T1' with the large year outside the signed integer range (INT_MIN..INT_MAX) is not currently supported.
"a1232e.asn", line 3 (Module-C1232E): C1232E: The time value " 2147483649-12" in 'T2' with the large year outside the signed integer range (INT_MIN..INT_MAX)is not currently supported.
Possible Solution
Remove the time value.
A1233E
Message Format
C1233E: The [time|duration\recurring interval] value "tstring" in 'Name' with the [fraction|recurrence|...] component exceeding UINT_MAX is not currently supported.
Message Cause
A time value includes a fraction or recurrence in a duration component with a positive value that exceeds the maximum unsigned INTEGER type. Currently, these values are not supported for the OSS ASN.1 Tools.
Example
Module-C1233E DEFINITIONS ::= BEGIN
T1 ::= TIME ("12:12:01.4294967296")
T2 ::= TIME ("R4294967296/PT12H12M1S")
T3 ::= TIME ("P4294967299Y12M")
END
Error Message
"a1233e.asn", line 2 (Module-C1233E): C1233E: The time value "12:12:01.4294967296" in 'T1' with the fraction component exceeding UINT_MAX is not currently supported.
"a1233e.asn", line 3 (Module-C1233E): C1233E: The recurring interval value "R4294967296/PT12H12M1S" in 'T2' with the recurrence component exceeding UINT_MAX is not currently supported.
"a1233e.asn", line 4 (Module-C1233E): C1233E: The duration value "P4294967299Y12M" in 'T3' with the year component exceeding UINT_MAX is not currently supported.
Possible Solution
Remove the time value.
A1234E
Message Format
A1234E: Information object classes specified in the 'ObjectClassFieldType' notations of the component 'Name1' referenced in the ComponentRelationConstraint and of the referencing component 'Name2' must be the same.
Message Cause
The references and all the referenced components must be ObjectClassFieldTypes that reference the same class. For more information, see ITU-T Rec. X.682 clause 10.14.
Example
Module-A1234 DEFINITIONS ::= BEGIN
MYCLASS1 ::= CLASS { &id INTEGER, &Type }
MySet1 MYCLASS1 ::= { ... }
MYCLASS2 ::= CLASS { &code IA5String, &Type }
MySet2 MYCLASS2 ::= { ... }
T ::= SEQUENCE {
id MYCLASS1.&id ({MySet1}),
val MYCLASS2.&Type ({MySet2}{@id}) OPTIONAL
}
END
Error Message
"a1234e.asn", line 8 (Module-A1234): A1234E: Information object classes specified in the 'ObjectClassFieldType' notations of the component 'id' referenced in t he ComponentRelationConstraint and of the referencing component 'val' must be the same.
Possible Solution
Make sure all components reference the same class.
A1235E
Message Format
A1235E: The value "tstring" of the 'DATE' type in the valuereference 'vname' must be a valid date with basic years, months, and days components.
A1235E: The value "tstring" of the 'TIME-OF-DAY' type in the valuereference 'vname' must be a valid local time-of-day with hours, minutes, and seconds components.
A1235E: The value "tstring" of the 'DATE-TIME' type in the valuereference 'vname' must be a valid date with basic years, months, and days components and local time-of-day with hours, minutes, and seconds components.
A1235E: The value "tstring" of the 'DURATION' type in the valuereference 'vname' must be a valid duration.
Message Cause
The useful time types DATE, TIME-OF-DAY, DATE-TIME, and DURATION are regarded as independent types rather than as subtypes of the TIME type. Values of these types must have properties and settings as specified in their notations:
DATE - "Basic=Date Date=YMD Year=Basic"
TIME-OF-DAY - "Basic=Time Time=HMS Local-or-UTC=L"
DATE-TIME - "Basic=Date-Time Date=YMD Year=Basic Time=HMS
Local-or-UTC=L"
DURATION - "Basic=Interval Interval-type=D"
Example
Module-A1235E DEFINITIONS ::= BEGIN vt TIME-OF-DAY ::= "11:50:60.001" vd DATE ::= "1560-12-12" vdt DATE-TIME ::= "2234-12-16T12:12:12+00:00" vdr DURATION ::= "R/P1200Y0M" END
Error Message
"a1235e.asn", line 2 (Module-A1235E): A1235E: The value "11:50:60.001" of the 'TIME-OF-DAY' type in the valuereference 'vt' must be a valid local time-of-day with hours, minutes, and seconds components.
"a1235e.asn", line 3 (Module-A1235E): A1235E: The value "1560-12-12" of the 'DATE' type in the valuereference 'vd' must be a valid date with basic years, months, and days components.
"a1235e.asn", line 4 (Module-A1235E): A1235E: The value "2234 12 16T12:12:12+00:00" of the 'DATE-TIME' type in the valuereference 'vdt' must be a valid date with basic years, months, and days components and local time-of-day with hours, minutes, and seconds components.
"a1235e.asn", line 5 (Module-A1235E): A1235E: The value "R/P1200Y0M" of the 'DURATION' type in the valuereference 'vdr' must be a valid duration.
Possible Solution
Specify valid values of the useful time types.
A1236E
Message Format
A1236E: 'Name' contains the InnerSubtype constraint that uses the 'DURATION-EQUIVALENT' type but it is not a duration subtype.
Message Cause
The InnerSubtype constraint using the "DURATION-EQUIVALENT" type can be applied only to time types that are duration subtypes. Any subset of the TIME type, all of whose abstract values have the property settings "Basic=Interval Interval-type=D" (whether UNIVERSAL 34 or UNIVERSAL 14), is called a duration subtype.
Example
Module-A1236E DEFINITIONS ::= BEGIN
T-duration-subtype ::= DURATION (WITH COMPONENTS {years (2), days (10)})
T-bad ::= TIME (WITH COMPONENTS {years (2), days (10)})
END
Error Message
"a1236e.asn", line 3 (Module-A1236E): A12346: 'T-bad' contains the InnerSubtype constraint that uses the 'DURATION-EQUIVALENT' type but it is not a duration subtype.
Possible Solution
Replace the time type that includes the InnerSubtype with a duration subtype, or remove the InnerSubtype.
A1237E
Message Format
A1237E: The InnerSubtype applied to the duration subtype 'Name' incorrectly constrains all of the time components in a duration to be absent.
Message Cause
The InnerSubtype constraints applied to components of the DURATION-EQUIVALENT SEQUENCE type are constraints on the corresponding time components of the duration type. The rules for duration types require that at least one of the time components must be present.
Example
Module-A1227E DEFINITIONS ::= BEGIN
T ::= TIME (SETTINGS "Basic=Interval Interval-type=D")
(WITH COMPONENTS {
-- FullSpec, implies ABSENT on all OPTIONAL that are not listed
fractional-part (WITH COMPONENTS {
number-of-digits (2..3),
fractional-value})})
END
Error Message
"a1237e.asn", line 5 (Module-A1237E): A1237E: The InnerSubtype applied to the duration subtype 'T' incorrectly constrains all of the time components in a duration to be absent.
Possible Solution
Correct the InnerSubtype. You can replace the FullSpecification with the PartialSpecification that does not imply absent constraints on components that are not listed, or remove it.
A1238E
Message Format
A1238E: The InnerSubtype applied to the duration subtype 'Name' constrains a week component in a duration to be present, no other time component shall be constrained to be present.
Message Cause
The InnerSubtype constraints applied to components of the DURATION-EQUIVALENT SEQUENCE type are constraints on the corresponding time components of the duration type. The rules for duration types require that no other time components must be present when the week component is present.
Example
Module-A1238E DEFINITIONS ::= BEGIN
T ::= DURATION (WITH COMPONENTS {weeks (2), days (10..12)})
END
Error Message
"a1228e.asn", line 2 (Module-A1228E): A1238E: The InnerSubtype applied to the duration subtype 'T' constrains a week component in a duration to be present, no other time component shall be constrained to be present.
Possible Solution
Correct the InnerSubtype according to the rules for duration types.
A1239E
Message Format
C1239E: The extensible CHOICE 'Type' shall not have a final 'USE-UNION' encoding instruction.
Message Cause
There is a final USE-UNION encoding instruction on an extensible CHOICE type.
Example
Module-C1239E DEFINITIONS XER INSTRUCTIONS ::= BEGIN
T ::= [USE-UNION] CHOICE { i INTEGER, ... }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1239e.asn", line 2 (Module-C1239E): C1239E: The extensible CHOICE 'T' shall not have a final 'USE-UNION' encoding instruction.
Possible Solution
Remove the USE-UNION encoding instruction or remove the extensibility marker for the type.
A1240W
Message Format
C1240W: The OSS.ExtensibleUseType directive is ignored for 'Type'. It is permitted only for extensible CHOICE types with the final USE-TYPE XER encoding instruction.
Message Cause
OSS.ExtensibleUseType must be applied to an extensible CHOICE with the USE-TYPE XER encoding instruction assigned.
Example
Module-C1240W DEFINITIONS XER INSTRUCTIONS ::= BEGIN
T ::= [USE-TYPE] CHOICE { i INTEGER, b BOOLEAN }
--<ExtensibleUseType>--
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1240w.asn", line 2 (Module-C1235W): C1240W: The OSS.ExtensibleUseType directive is ignored for 'T'. It is permitted only for extensible CHOICE types with the final USE-TYPE XER encoding instruction.
Possible Solution
Add the extensibility marker or apply the USE-TYPE XER encoding instruction to the CHOICE type.
A1240W
Message Format
C1240W: The OSS.ExtensibleUseType directive is ignored for 'Type'. It is permitted only for extensible CHOICE types with the final USE-TYPE XER encoding instruction.
Message Cause
OSS.ExtensibleUseType must be applied to an extensible CHOICE with the USE-TYPE XER encoding instruction assigned.
Example
Module-C1240W DEFINITIONS XER INSTRUCTIONS ::= BEGIN
T ::= [USE-TYPE] CHOICE { i INTEGER, b BOOLEAN }
--<ExtensibleUseType>--
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1240w.asn", line 2 (Module-C1235W): C1240W: The OSS.ExtensibleUseType directive is ignored for 'T'. It is permitted only for extensible CHOICE types with the final USE-TYPE XER encoding instruction.
Possible Solution
Add the extensibility marker or apply the USE-TYPE XER encoding instruction to the CHOICE type.
A1242E
Message Format
A1242E: The start point in the interval value "tstring" in the valuereference 'name' must chronologically precede the end point.
Message Cause
The values specified in the start and end points of the interval value must be in chronological order.
Example
Module-A1242E DEFINITIONS ::= BEGIN
T1 ::= TIME("1994-12-12T01:01.0000/1990-12-12T01:01.1233")
T2 ::= TIME ("R12/-10000-12/-10001-10")
END
Error Message
"a1242e.asn", line 3 (Module-A1242E): A1242E: The start point in the interval value "1994-12-12T01:01.0000/1990-12-12T01:01.1233" in the valuereference 'T1' must chronologically precede the end point.
"a1242e.asn", line 4 (Module-A1242E): A1242E: The start point in the interval value "R12/-10000-12/-10001-10" in the valuereference 'T2' must chronologically precede the end point.
Possible Solution
Make sure the interval values are in chronological order.
A1243W
Message Format
A1243W: A negative zero 'RealValue' shall not have a decimal point, a fractional part, and an exponential part.
Message Cause
The input ASN.1 syntax contains an invalid notation for a zero REAL value. According to X.680 clause 20.6, the "-" sign cannot precede a zero REAL value unless it is the special value MINUS ZERO ("-0") that does not have a decimal, fractional, or exponential part.
Example
Module-A1243W DEFINITIONS ::= BEGIN
R ::= REAL
b1 R ::= -0.0
END
Error Message
"a1243w.asn", line 3 (Module-A1243W): A1243W: A negative zero 'RealValue' shall not have a decimal point, a fractional part, and an exponential part.
b1 R ::= -0.0
Possible Solution
Specify a correct value for the REAL type that either has no sign and has a decimal part, or has a sign and it is the special REAL value MINUS ZERO (-0).
L1244I
This error message is generated only for the OSS ASN.1 GUI.
Message Format
L1244I: Command line: 'cmd_line_options'
Message Cause
The message is printed by the OSS ASN.1 GUI in the ASN.1 compiler or syntax checker log.
Possible Solution
This informatory message is issued only for your convenience and can be ignored.
A1245E
Message Format
A1245E: The 'PropertySettingsList' restricts the type to be represented as a date and time of day, the date component's setting must not restrict dates to be represented with reduced accuracy, valid settings of the 'Date' property are 'YD', 'YMD', 'YWD'.
Message Cause
The ISO 8601 standard restricts dates within the date and time of day representations to have representations other than ones with a reduced accuracy.
Example
Module-A1245E DEFINITIONS ::= BEGIN
DateTime1 ::= TIME (SETTINGS "Basic=Date-Time Date=C Year=Basic")
DateTime2 ::= TIME (SETTINGS "Basic=Date-Time Date=Y")
Interval ::= TIME (SETTINGS "Basic=Rec-Interval Interval-type=SD
SE-point=Date-Time Date=YM")
Error Message
"a1245e.asn", line 3 (Module-A1245E): A1245E: The 'PropertySettingsList' restricts the type to be represented as a date and time of day, the date component's setting must not restrict dates to be represented with reduced accuracy, valid settings of the 'Date' property are 'YD', 'YMD', 'YWD'.
DateTime1 ::= TIME (SETTINGS "Basic=Date-Time Date=C Year=Basic")
"a1245e.asn", line 4 (Module-A1245E): A1245E: The 'PropertySettingsList' restricts the type to be represented as a date and time of day, the date component's setting must not restrict dates to be represented with reduced accuracy, valid settings of the 'Date' property are 'YD', 'YMD', 'YWD'.
"Basic=Date-Time Date=Y")
"a1245e.asn", line 6 (Module-A1245E): A1245E: The 'PropertySettingsList' restricts the type to be represented as a date and time of day, the date component's setting must not restrict dates to be represented with reduced accuracy, valid settings of the 'Date' property are 'YD', 'YMD', 'YWD'.
SE-point=Date-Time Date=YM")
Possible Solution
Make sure the PropertySettings syntax uses the correct settings of the Date property.
A1246E
Message Format
A1246E: There must be at least one value that satisfies the subtype constraint: the PropertySettings applied to the type 'Name' restricts all abstract values to represent dates with reduced accuracy within date and time of day representations.
Message Cause
The ISO 8601 standard restricts dates within date and time of day representations to have representations other than ones with a reduced accuracy. The input ASN.1 syntax contains a set of PropertySettings constraints which defines an empty set of values.
Example
Module-A1246E DEFINITIONS ::= BEGIN
DateTime ::= TIME (SETTINGS "Basic=Date-Time")
(SETTINGS "Date=C Year=Basic Time=H Local-or-UTC=Z")
Interval ::= TIME (SETTINGS "Basic=Interval Interval-type=SE
SE-point=Date-Time")
(SETTINGS "Date=Y Year=Basic Time=H Local-or-UTC=L")
END
Error Message
"a1246e.asn", line 3 (Module-A1246E): A1246E: There must be at least one value that satisfies the subtype constraint: the PropertySettings applied to the type 'DateTime' restricts all abstract values to represent dates with reduced accuracy within date and time of day representations.
"a1246e.asn", line 7 (Module-A1246E): A1246E: There must be at least one value that satisfies the subtype constraint: the PropertySettings applied to the type 'Interval' restricts all abstract values to represent dates with reduced accuracy within date and time of day representations.
Possible Solution
Change the PropertySettings constraint so that the combined set does not yield an empty set.
C1247W
Message Format
C1247W: The ASN.DeferDecoding or OSS.ENCODABLE directive applied to a recursively defined field with the reference 'Reference' is not supported and will be ignored.
Message Cause
An ASN1.DeferDecoding or OSS.ENCODABLE directive is applied to a field whose type is defined recursively. These directives are not supported by the compiler.
Example
--<OSS.PDU Module-C1247W.ZZ>--
--<ASN1.DeferDecoding Module-C1247W.ZZ.b>--
Module-C1247W DEFINITIONS ::= BEGIN
ZZ ::= SEQUENCE {
b ZZ OPTIONAL
}
END
Error Message
"c1247w.asn", line 7 (Module-C12474W): C1247W: The ASN.DeferDecoding or OSS.ENCODABLE directive applied to a recursively defined field with the reference 'ZZ-b' is not supported and will be ignored.
Possible Solution
This warning message can be ignored. To suppress this warning, remove the directive.
C1248W
This warning message is generated only for the ASN.1 Tools for Java compiler.
Message Format
C1248W: Generation of initialized Java values of the class 'Name' for types with the OSS.OBJHANDLE/OSS.NOCOPY directive is not currently supported. The structure within the value 'name' will be initialized to zeros.
Message Cause
The OSS ASN.1 Tools for Java compiler does not support initialization values of types with the OSS.OBJHANDLE or OSS.NOCOPY directive. You must manually initialize these values.
Example
C1248W DEFINITIONS ::= BEGIN
SetT ::= SET {
g OCTET STRING --<NOCOPY>--
}
set-data SetT ::= {
g 'A'H
}
END
The module Java class contains the following Java value:
// Value references
public static final SetT set_data =
new SetT (
null
);
Error Message
"c1248w.asn", line 6 (C1248W): C1248W: Generation of initialized Java values of the class 'com.oss.asn1.HugeOctetString' for types with the OSS.OBJHANDLE/OSS.NOCOPY directive is not currently supported. The structure within the value 'set-data1' will be initialized to zeros.
Possible Solution
Initialize the Java values.
C1249E
This warning message is generated only for the ASN.1 Tools for Java compiler.
Message Format
C1249E: You have a nodelocked license that does not permit you to use the -microedition option.
Message Cause
The -microedition option was specified for the OSS ASN.1 Tools for Java compiler, but the license is nodelocked.
Possible Solution
Remove the -microedition option from the command line or contact Sales ‹info@oss.com› to obtain a new license.
L1250W
Message Format
L1250W: The 'keyword1' option is not supported when it is specified together with 'keyword2 keyword3 ...' options and will be ignored.
Message Cause
The ASN.1 compiler command line contains a combination of options that is not currently supported. The ASN.1 compiler will ignore one of the originally specified options.
Example
The following ASN.1 compiler options are specified to compile foo.asn:
asn1 foo.asn -codefile -exer -relaySafe
Error Message
L1250W: The '-relaySafe' option is not supported when it is specified together with '-codefile -exer' options and will be ignored.
Possible Solution
Remove one of the options.
C1254W
Message Format
C1254W: The OSS.ExerNumericBoolean directive is ignored for 'Type'. It is permitted only when 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Message Cause
The OSS.ExerNumericBoolean is applied to a BOOLEAN type but the GLOBAL-DEFAULTS MODIFIED-ENCODINGS encoding instruction is absent.
Example
Module DEFINITIONS XER INSTRUCTIONS ::= BEGIN
B ::= BOOLEAN --<ExerNumericBoolean>--
b1 B ::= TRUE
END
Error Message
"c1254w.asn", line 2 (Module): C1254W: The OSS.ExerNumericBoolean directive is ignored for 'B'. It is permitted only when 'GLOBAL-DEFAULTS MODIFIED-ENCODINGS' encoding instruction is present.
Possible Solution
Add the GLOBAL-DEFAULTS MODIFIED-ENCODINGS XER encoding instruction.
A1257W
Message Format
A1257W: Values of the identifier field, if supplied, are required to be unique within any information object set. Values of the UNIQUE field 'fieldname' in the information objects on the line 'line number of first object' and 'line number of second object' are the same in the information object set 'object set reference'.
Message Cause
The objects from an ObjectSet have equal UNIQUE field values.
Example
X DEFINITIONS ::= BEGIN
ERROR-CLASS ::= CLASS {
&code INTEGER UNIQUE,
&Type
} WITH SYNTAX {&Type IDENTIFIED BY &code}
ErrorSet ERROR-CLASS ::= {
{ INTEGER IDENTIFIED BY 1 } |
{ REAL IDENTIFIED BY 2 } |
{ IA5String IDENTIFIED BY 1 }
}
ErrorReturn ::= [1] SEQUENCE {
errorCategory PrintableString,
errorCode ERROR-CLASS.&code ({ErrorSet}),
errorInfo ERROR-CLASS.&Type ({ErrorSet}{@.errorCode})
}
END
Error Message
"a1257w.asn", line 10 (X): A1257W: The value of the UNIQUE field 'code' of the information object in the ObjectSet 'ErrorSet' line '7' is equal to a value of the field of information object on line '8' of the same ObjectSet.
Possible Solution
Make sure UNIQUE field values for objects in the same ObjectSet are different.
C1258W
This warning message is generated only for the ASN.1 Tools for Java compiler.
Message Format
A1257W: Values of the identifier field, if supplied, are required to be unique within any information object set. Values of the UNIQUE field 'fieldname' in the information objects on the line 'line number of first object' and 'line number of second object' are the same in the information object set 'object set reference'.
Message Cause
The objects from an ObjectSet have equal UNIQUE field values.
Example
X DEFINITIONS ::= BEGIN
ERROR-CLASS ::= CLASS {
&code INTEGER UNIQUE,
&Type
} WITH SYNTAX {&Type IDENTIFIED BY &code}
ErrorSet ERROR-CLASS ::= {
{ INTEGER IDENTIFIED BY 1 } |
{ REAL IDENTIFIED BY 2 } |
{ IA5String IDENTIFIED BY 1 }
}
ErrorReturn ::= [1] SEQUENCE {
errorCategory PrintableString,
errorCode ERROR-CLASS.&code ({ErrorSet}),
errorInfo ERROR-CLASS.&Type ({ErrorSet}{@.errorCode})
}
END
Error Message
"a1257w.asn", line 10 (X): A1257W: The value of the UNIQUE field 'code' of the information object in the ObjectSet 'ErrorSet' line '7' is equal to a value of the field of information object on line '8' of the same ObjectSet.
Possible Solution
Make sure UNIQUE field values for objects in the same ObjectSet are different.
C1261E
Message Format
C1261E: There is no value notation (no predefined test cases) in the ASN.1, so there is nothing to test. Please remove the -test option.
Message Cause
The compiler option -test was specified but there is no value notation in the ASN.1 syntax.
Error Message
"c1261e.asn", (Module-C1261E): C1261E: There is no value notation (no predefined test cases) in the ASN1, so there is nothing to test. Please remove the -test option.
Possible Solution
Remove the -test option.
C1263W
Message Format
C1263W: The value for 'field' is being truncated to satisfy the constraints on its Type. Consider using the -allowBadValues option to override such truncation.
Message Cause
A value does not conform to the constraints.
Example
Module-C1263W DEFINITIONS ::= BEGIN
S ::= SET {
a BIT STRING(SIZE(1..5)),
b BOOLEAN
}
s S ::= { a '111111'B, b TRUE }
END
Error Message
"c1263w.asn", line 6 (Module-C1263W): C1263W: The value for 's.a' is being truncated to satisfy the constraints. Consider using the allowBadValues option to override such truncation.
Possible Solution
Change the value to conform to the constraints or re-ASN.1-compile your syntax with the -allowBadValues option to override the truncation.
C1268E
Message Format
C1268E: Invalid arc #<arc level> in the OID-IRI value 'value name'.
Message Cause
The error is issued if the OID-IRI value does not conform to Annex A of ITU-T Rec. X.660 (07/2011) | ISO/IEC 9834-1:2012.
Example
Module-C1268E DEFINITIONS ::= BEGIN
bad01 OID-IRI ::= "/3"
END
Error Message
"c1268e.asn", line 3 (Module-C1268E): C1268E: Invalid arc #1 in the OID-IRI value 'bad01'.
Possible Solution
Change the invalid arc number value.
C1269E
Message Format
C1269E: Invalid OID-IRI/RELATIVE-OID-IRI value 'value name'.
Message Cause
The error is issued if the OID-IRI value does not conform to Annex A of ITU-T Rec. X.660 (07/2011) | ISO/IEC 9834-1:2012.
Example
Module-C1969E DEFINITIONS ::= BEGIN
bad02 RELATIVE-OID-IRI ::= "0%"
END
Error Message
c1269e.asn", line 3 (C1969E): C1269E: Invalid RELATIVE-OID-IRI value 'bad02'.
Possible Solution
Change the invalid value.
A1270W
Message Format
A1270W: 'name' has already been defined on line <number>. Its redefinition is being ignored.
Message Cause
The -ignoreRedefinedAssignments option is enabled (usually via the default -relaxedMode option) and the input syntax contains redefinitions of ASN.1 named types and values that appear within the same ASN.1 modules. It is issued for all redefined types and values that were ignored by the ASN.1 compiler.
Example
Module-A1270W DEFINITIONS ::= BEGIN Type ::= INTEGER Type ::= INTEGER END
Error Message
"a1270w.asn", line 5 (Module-A1270W): A1270W: 'Type' has already been defined on line 3. Its redefinition is being ignored.
Possible Solution
Remove the duplicate definitions.
A1271E
Message Format
A1271E: The low line character ('_') is not among the permitted characters for ASN.1 names. Please use the '-allow UnderscoresInAsn1Names' command-line option to force the compiler to accept such invalid names.
Error Message
"a1271e.asn", line 3 (Module-A1271E): A1271E: The low line character ('_') is not among the permitted characters for ASN.1 names. Please use the '-allow UnderscoresInAsn1Names' command-line option to force the compiler to accept such invalid names.
Possible Solution
Remove the characters from all ASN.1 names or specify the -allow UnderscoresInAsn1Names command-line option.
C1276W
Message Format
C1276W: The element name 'name' has been used for XML in place of the missing field identifier.
Message Cause
The -ignoreError 832 ASN.1 compiler option is enabled (usually via the default -relaxedMode option) to allow the use of the XML encoding rules (XER, CXER or EXER), but the ASN.1 specification contains a SET, SEQUENCE, or CHOICE component without an identifier.
Example
Module-C1276W DEFINITIONS ::= BEGIN
S ::= SEQUENCE {
INTEGER
}
END
Error Message
"c1276w.asn", line 4 (Module-C1276W): C1276W: The element name 'integer' has been used for XML in place of the missing field identifier.
Possible Solution
Add an identifier for the component.
A1277W
Message Format
A1277W: 'type reference' is assumed to be a misspelling of the built-in type 'built-in type name'.
Message Cause
The warning is issued if the -allow MixedCaseForSomeBuiltInTypesNames option is enabled (usually via the default -relaxedMode option) and the input syntax contains a mixed case name for an ASN.1 built-in type that is recognized by the compiler as a misspelling for the corresponding ASN.1 built-in type.
Example
Module-A1277W DEFINITIONS ::= BEGIN Type ::= IA5STRING value Type ::= "abc" END
Error Message
"a1277w.asn", line 3 (Module-A1277W): A1277W: 'IA5STRING' is assumed to be a misspelling of the built-in type 'IA5String'.
Possible Solution
Replace the mixed case names for ASN.1 built-in types.
C1278E
Message Format
A1278E: An invalid UTF-8 character was encountered inside the user comment. Please re-encode the file to UTF8 before passing as input.
Message Cause
The ASN.1 input contains an invalid UTF-8 character within a user comment.
Possible Solution
Make sure the ASN.1 comments are valid according to the character set definition (ISO-10646) or specify the -ignoreError 1278 option which converts the error into a warning and instructs the compiler to replace the invalid UTF8 characters with question marks ("?"). Note that in the latter case, it is not always possible to correctly determine the next valid character and the comment may be garbled.
C1279S
Message Format
C1279S: Licensing error. Please contact OSS Nokalva, Inc.
Message Cause
Your license is not valid.
Possible Solution
For information about renewing your license or obtaining updated software, contact Sales ‹info@oss.com›.
C1280S
Message Format
C1280S: Licensing error. Please contact OSS Nokalva, Inc.
Message Cause
Your license is not valid.
Possible Solution
For information about renewing your license or obtaining updated software, contact Sales ‹info@oss.com›.
C1281W
Message Format
C1281W: 'ModuleName' is identified as an ECN module and is being skipped. To process ECN modules, please contact OSS to obtain a copy of the OSS ECN Tools.
Message Cause
The input ASN.1 syntax contains ECN modules, namely, modules that include ENCODING-DEFINITIONS or LINK-DEFINTIONS keywords in the module definition. They can be processed only by the OSS ECN tools and are ignored by other OSS ASN.1 compilers.
Error Message
"c1281w.asn", line 9 (Module): C1281W: 'Module-EDM' is identified as an ECN module and is being skipped. To process ECN modules, please contact OSS to obtain a copy of the OSS ECN Tools.
Possible Solution
For information about using the ECN-specific encoding rules defined in the skipped ECN modules, contact Technical Support ‹support@oss.com›. Otherwise, this warning can be ignored.
C1283S
Message Format
C1283S: COMPILER ERROR #70 (number).
Message Cause
The ASN.1 compiler has encountered an internal error.
Your ASN.1 input likely contains erroneous syntax, but in a new and unexpected form, which we need to further analyze.
Next Action
Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.
C1284W
Message Format
C1284W: A sample value for PDU 'type' created by the ASN.1 compiler may not satisfy the constraints on its Type.
Message Cause
When the -sampleCode (without argument) or the -sampleCode pdus command-line option is specified (or similar global OSS.SampleCode directives), the compiler tries to create artificial values for each PDU type defined in the input syntax so that these values satisfy all constraints on their types. The warning is issued when the compiler fails to create a value that conforms to all constraints on its type (due to internal limitations or empty sets of permitted values allowed by subtype constraints for the type) so the generated sample code might fail with a runtime constraint violation for the indicated PDU.
Example
--<OSS.PDU Module-C1284W.SeqOf>-- Module-C1284W DEFINITIONS ::= BEGIN SeqOf ::= SEQUENCE (SIZE (1..5)) OF SeqOf END
Error Message
"c1284w.asn", line 3 (Module-C1284W): C1284W: A sample value for PDU 'SeqOf' created by the ASN.1 compiler may not satisfy the constraints on its Type.
Possible Solution
Remove the PDU type from the sample code generation by applying the OSS.NoSampleCode directive to the type.
C1285W
Message Format
C1285W: The lower bound in size constraint for the type 'type reference' is too large (number). The sample value created for this type will be truncated to 1024 characters to limit the size of created sample code.
Message Cause
The warning is issued when the -sampleCode command-line option with the pdus argument or without one, is specified and the input ASN.1 syntax contains a type with a size constraint whose lower bound is greater than 1024. This constraint will result in a large code generation. The ASN.1 compiler limits all created sample Character String, Octet String, or Bit string, SEQUENCE OF, SET OF values to consist of 1024 elements at maximum, even if this results in a constraint violation to avoid a very large C values initialization in the sample code.
Example
Module-C1285W DEFINITIONS ::= BEGIN
BigCharStr ::= PrintableString (SIZE(1500..7000))
END
Error Message
"c1285.asn", line 2 (Module-C1285W): C1285W: The lower bound in size constraint for the type 'BigCharStr' is too large (1500).
The sample value created for this type will be truncated to 1024 characters to limit the size of created sample code.
Possible Solution
Remove the type from the sample code generation by applying the OSS.NoSampleCode directive to the PDU type.
C1286W
Message Format
C1286W: No sample code was created due to absence of "true" PDUs in the input syntax. Please use the OSS.SampleCode directive to mark PDU types for which the sample code should be created.
Message Cause
The warning is issued when the -sampleCode command-line option with the pdus argument or without an argument is specified and the input ASN.1 syntax does not contain true PDU types, namely, defined types that are not referenced by any other type, are not imported and are not used in information object sets or as types in the ContentsConstraint. The compiler cannot create the sample code because it has no values to use in the sample code.
Example
Module1 DEFINITIONS ::= BEGIN
PDU ::= SEQUENCE { a INTEGER}
END
Module2 DEFINITIONS ::= BEGIN
IMPORTS PDU FROM Module1;
value PDU ::= {a 1}
END
Error Message with the -sampleCode pdus
"c1286w.asn", line 7 (Module2): C1286W: No sample code was created due to absence of "true" PDUs in the input syntax. Please use the OSS.SampleCode directive to mark PDU types for which the sample code should be created.
Possible Solution
Apply the OSS.SampleCode compiler directives to PDU types.
C1287W
Message Format
C1287W: The 'OSS.SampleCode [count|selection]' directive is permitted only for ASN.1 type(s) and will be ignored for 'type reference'.
Message Cause
The input ASN.1 syntax contains an invalid OSS.SampleCode directive application.
Example
--<OSS.PDU Module-C1284W.SeqOf>--
--<OSS.SampleCode selection Module-C1287W.S.b>--
Module-C1287W DEFINITIONS ::= BEGIN
S ::= SEQUENCE {
a INTEGER --<SampleCode count:4>--,
b IA5String
}
END
Error Message
"c1287w.asn", line 4 (Module-C1287W): C1287W: The 'OSS.SampleCode count' directive is permitted only for SEQUENCE OF or SET OF types and will be ignored for 'a'.
"c1287w.asn", line 5 (Module-C1287W): C1287W: The 'OSS.SampleCode selection' directive is permitted only for a CHOICE alternative and will be ignored for 'b'.
Possible Solution
Remove the directive.
C1288I
Message Format
C1288I: Nesting level of inline type definition in the generated header file exceeded implementation limit of some C-compilers. Consider use of the OSS.ExtractType and OSS.TYPENAME directives.
Message Cause
The informatory message is issued if the -compat generateInlineDeeplyNestedTypes and norelaxedMode are set. The cause of the message is the presence of a deeply nested type definition whose nesting level exceeds 13.
Example
Module-C1288I DEFINITIONS ::= BEGIN
S ::= SEQUENCE {
f1 SEQUENCE {
f2 SEQUENCE {
f3 SEQUENCE {
f4 SEQUENCE {
f5 SET {
f6 SEQUENCE {
f7 SET {
f8 SEQUENCE {
f9 SET {
f10 SEQUENCE {
f11 SET {
f12 SEQUENCE {
f13 SET {
f14 SEQUENCE {
f15 SET {
i INTEGER
}
}
}
}
}
}
}
}
}
}
}
}
}
}
}
}
END
Error Message
"c1288i.asn", line 16 (Module-C1288I): C1288I: Nesting level of inline type definition in the generated header file exceeded implementation limit of some C-compilers. Consider use of the OSS.ExtractType and OSS.TYPENAME directives.
Possible Solution
Consider the following solutions:
- Remove -compat generateInlineDeeplyNestedTypes from the command line to allow the ASN.1 compiler to automatically decrease nesting level.
- Use the OSS.ExtractType directive to generate a standalone typedef for one or more of the nested types, thus decreasing the nesting level of inline structures. Also, you can use the OSS.TYPENAME directive to specify a name for the type (for the above example: --<OSS.ExtractType Module-C1288I.S.f1.f2.f3.f4.f5.f6.f7.f8.f9.f10>-- --<OSS.TYPENAME Module-C1288I.S.f1.f2.f3.f4.f5.f6.f7.f8.f9.f10 "Nested_SEQUENCE">-- ).
C1290W
Message Format
C1290W: The directive 'DIRECTIVE' is ignored because it refers to the absent module 'MODULE NAME'.
Message Cause
The module referred to by an OSS.ROOT or the ASN1.WorkingSet compiler directive is not present in the input ASN.1 specification.
Example
--<ASN1.WorkingSet common Absent1, M.Foo>--
--<OSS.ROOT Absent2>--
M DEFINITIONS ::= BEGIN
Foo ::= INTEGER
Bar ::= Foo(1..10)
f Foo ::= 6
END
Error Message
"c1290w.asn", line 1 (M): C1290W: The directive 'ASN1.WorkingSet common Absent1.Bar' is ignored because it refers to the absent module 'Absent1'.
"c1290w.asn", line 2 (M): C1290W: The directive 'OSS.ROOT Absent2' is ignored because it refers to the absent module 'Absent2'.
Possible Solution
Correct the module reference or remove the directive.
A1291W
Message Format
A1291W: The BIT STRING type 'type reference' has no size constraint; therefore its minimum length is zero and its maximum length is unbounded.
Message Cause
A BIT STRING type with named bits has an unconstrained size.
Example
M DEFINITIONS ::= BEGIN
Flags ::= BIT STRING {
first-flag (0),
second-flag (1),
third-flag (2),
fourth-flag (3),
fifth-flag (4),
sixth-flag (5)
}
END
Error Message
line 2 (M): A1291W: The BIT STRING type 'Flags' has no size constraint; therefore its minimum length is zero and its maximum length is unbounded.
Possible Solution
Unless its size is intentionally unbounded, apply a size constraint to the BIT STRING type with named bits.
C1291W
Message Format
C1291W: A CHOICE type 'type reference' with USE-UNION encoding instruction has two fields, 'identifier1' and 'identifier2', that allow the same encoded value.
C1291W: A CHOICE type 'type reference' with USE-UNION encoding instruction has two fields, 'identifier1' and 'identifier2', that possibly allow the same encoded value.
C1291W: A CHOICE type 'type reference' with USE-UNION encoding instruction has two fields, 'identifier1' and 'identifier2', that may not be distinguished unless a SOED constraint checker is linked (LED E-XER implementation restriction).
Message Cause
A [USE-UNION] type is used as an ATTRIBUTE and/or a LIST element could allow a duplicate encoded value. Under the X.693 standard, this is not allowed. However, these cases may result from XSD mapping, when a warning is issued instead of an error. Note that at runtime the decoder will always assume the first of these conflicting alternatives.
Example
Module-C1291W DEFINITIONS XER INSTRUCTIONS ::= BEGIN
A ::= [ATTRIBUTE] [USE-UNION] CHOICE { a INTEGER, b VisibleString }
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
Error Message
"c1291w.asn", line 3 (Module-C1291W): C1291W: A CHOICE type 'A' with USE-UNION encoding instruction has two fields, 'a' and 'b', that allow the same encoded value.
Possible Solution
Make sure there are no determination violations: use alternatives that do not conflict, add constraints, etc. For the above example, see the following solution:
b VisibleString (FROM("abcdef"))
A1292W
Message Format
A1292W: In PER/UPER, the size of the encoding of a non-extensible enumerated type depends on the total number of enumerators present in the definition. Type 'type reference' will be encoded in 'number of bits' bits, and the integers associated with the enumerators (e.g., the integer 'element value' associated with 'element name') will never be transmitted.
Message Cause
The input ASN.1 syntax compiled with the -per | -uper and -designerWarning options contains a non-extensible ENUMERATED type with explicitly specified numbers starting with 0 and the maximum number is the power of two minus one. The compiler assumes you want the encoding of the last element to be a SEQUENCE OF one, but the encoding will be different.
Example
M DEFINITIONS ::= BEGIN
A ::= ENUMERATED {
first (0),
second (1),
last (255)
}
END
Error Message
line 2 (M): A1292W: In PER/UPER, the size of the encoding of a non-extensible enumerated type depends on the total number of enumerators present in the definition. Type 'A' will be encoded in 2 bits, and the integers associated with the enumerators (e.g., the integer 255 associated with 'last') will never be transmitted.
Possible Solution
Use successive values starting with 0 for an ENUMERATED type.
A1293W
Message Format
A1293W: In PER/UPER, the size of the encoding of the selector of a non-extensible choice type depends on the total number of alternatives present in the definition. The selector of type 'type reference' will be encoded in 'number of bits' bits, and the tag numbers of the alternatives (e.g., the tag number 'tag value' of 'field name') will never be transmitted.
Message Cause
The input ASN.1 syntax compiled with the -per | -uper and -designerWarning options contains a non-extensible CHOICE type with alternatives tagged so that the lowest tag is zero, the maximum tag is the power of two minus one, and its binary representation differs from the PER/UPER encoding of the CHOICE selector. It is assumed the user wants an encoding of a selector for the last alternative as a SEQUENCE OF of one, but the encoding will be different.
Example
M DEFINITIONS ::= BEGIN
A ::= CHOICE {
first [0] INTEGER,
second [1] INTEGER,
last [15] INTEGER
}
END
Error Message
line 5 (M): A1293W: In PER/UPER, the size of the encoding of the selector of a non-extensible choice type depends on the total number of alternatives present in the definition. The selector of type 'A' will be encoded in 2 bits, and the tag numbers of the alternatives (e.g., the tag number 15 of 'last') will never be transmitted.
Possible Solution
Use successive values that start with 0 for tags in the CHOICE type.
A1296W
Message Format
A1296W: OSS has relaxed the ASN.1 standard to allow a string list notation for IRITypes. Use a UTF-8 file containing Unicode characters in a string notation to be in full compliance with the ASN.1 standard.
Message Cause
The current ASN.1 standard does not allow string list notation for IRI types. However, unless you specify the -designerWarnings option, the OSS ASN.1 compiler will accept them. Otherwise, unless you specify the -relaxedMode option, the compiler will issue a warning.
Example
M DEFINITIONS ::= BEGIN
OidIri ::= OID-IRI
voir1 OidIri ::= {"/abc/Umlaute/", {0, 0, 0, 228}, {0, 0, 0, 196},
{0, 0, 0, 246}, {0, 0, 0, 214}, {0, 0, 0, 252}, {0, 0, 0, 220}}
END
Error Message
"c1296.asn", line 3 (M): A1296W: OSS has relaxed the ASN.1 standard to allow a string list notation for IRITypes. Use a UTF-8 file containing Unicode characters in a string notation to be in full compliance with the ASN.1 standard.
Possible Solution
Consider the following solutions:
- Pass the input ASN.1 files in UTF-8 encoding with Unicode characters in the string notation to the compiler.
- Make sure you do not use the -designerWarnings compiler option.
A1297E
Message Format
A1297E: 'type reference' contains an untagged 'CHOICE|ANY|open type' as the item in a 'SET|CHOICE|SET or CHOICE'. It is not permitted by Octet Encoding Rules (OER). Consider adding a tag to the type or using AUTOMATIC tagging.
Message Cause
The input ASN.1 syntax contains an untagged CHOICE, ANY, or open type as the item in a SET or CHOICE.
Example
M DEFINITIONS ::= BEGIN
Ch ::= CHOICE {
a INTEGER (1..8),
b CHOICE {
c BOOLEAN
}
}
END
Error Message
"oech.asn", line 4 (M): A1297E: 'Ch' contains an untagged CHOICE as the item in a CHOICE. It is not permitted by Octet Encoding Rules (OER). Consider adding a tag to the type or using AUTOMATIC tagging.
Possible Solution
Add a tag to the type or use AUTOMATIC tagging.
C1298W
Message Format
C1298W: EXTENSIBILITY IMPLIED was specified for module <modulename>, but the compiler command -line option[s] <options> {was|were} specified.
This is likely to cause interoperability problems when two different versions of your specification are used. Please consider removing the EXTENSIBILITY IMPLIED keywords, or consider using -ber or -der only.
C1298W: --<OSS.EXTENSIBLE>-- was specified, but the compiler command-line option[s] <options> {was|were} specified. This is likely to cause interoperability problems when two different versions of your specification are used. Please consider removing the --<OSS.EXTENSIBLE>-- directive, or consider using -ber or -der only.
C1298W: --<EXTENSIBLE>-- was specified, but the compiler command-line option[s] <options> {was|were} specified. This is likely to cause interoperability problems when two different versions of your specification are used. Please consider removing the --<EXTENSIBLE>-- directive, or consider using -ber or -der only.
Message Cause
Using EXTENSIBILITY IMPLIED in a module header (or the OSS.EXTENSIBLE global directive) is similar to adding an extension marker ("...") to the definition of each type in the module (or in each module where the directive is present) for which it is permitted. However, this creates an unexpected overhead on PER, CPER, OER, or COER encodings of the types and is likely to cause interoperability problems when two different versions of your specification are used.
Example
The following specification is compiled with the -per and -oer options.
M DEFINITIONS EXTENSIBILITY IMPLIED ::= BEGIN
S ::= SEQUENCE {
a INTEGER
}
END
Error Message
"C1298", line 1 (M): C1298W: EXTENSIBILITY IMPLIED was specified for module M, but the compiler command-line options -per, -oer were specified. This is likely to cause interoperability problems when two different versions of your specification are used. Please consider removing the EXTENSIBILITY IMPLIED keywords, or consider using -ber or -der only.
Possible Solution
Remove EXTENSIBILITY IMPLIED or OSS.EXTENSIBLE or use -ber or -der instead of -per and -oer.
A1299W
Message Format
A1299W: The second node of OBJECT IDENTIFIER value exceeds implementation limit.
Message Cause
Due to implementation restrictions, the compiler does not accept a value of the OBJECT IDENTIFIER type if its second node exceeds LONG_MAX - 80 and type nodes are represented by a long INTEGER.
Example
M DEFINITIONS ::= BEGIN
OU ::= OBJECT IDENTIFIER --<UNBOUNDED|LONG>--
out OU ::= { 2 4294967224 }
END
Error Message
"t2.asn", line 3 (M): A1299W: The second node of OBJECT IDENTIFIER value exceeds implementation limit.
Possible Solution
Avoid using such large values on the second node, or use the default ENCODED representation for the type.
C1299W
Message Format
C1299W: Please consider replacing the EXTENSIBLE directive with an ellipsis("...") inside the SEQUENCE, SET or CHOICE type.
or (if the -per/-uper compiler option is used)
C1299W: Please consider replacing the EXTENSIBLE directive with an ellipsis("...") inside the SEQUENCE, SET or CHOICE type to avoid interoperability problems when two different versions of your specification are used.
Message Cause
The local EXTENSIBLE directive is applied to a type (and the -per | -uper option is specified). Using these directives is similar to adding an extension marker ("...") to the type definition before the closing brace.
Example
M DEFINITIONS ::= BEGIN
S ::= SET {
a BOOLEAN
} --<EXTENSIBLE>--
END
Error Message
"c1299.asn", line 4 (M): C1299W: Please consider replacing the EXTENSIBLE directive with an ellipsis("...") inside the SEQUENCE, SET or CHOICE type.
Possible Solution
Replace the EXTENSIBLE directive with an ellipsis ("...") in the type definition.
This documentation applies to the latest versions of the OSS® ASN.1 Tools software.
Copyright © 2025 OSS Nokalva, Inc. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic, mechanical, photocopying, recording or otherwise, without the prior permission of OSS Nokalva, Inc.
Every distributed copy of the OSS® ASN.1 Tools is associated with a specific license and related unique license number. That license determines, among other things, what functions of the OSS ASN.1 Tools are available to you.