TOP

Compiler Errors Reference (1300-9999)

C1300E

Message Format

C1300E: The time-optimized OER encoder/decoder does not support <feature>.

Message Cause

<feature> is not supported for the time-optimized OER encoder/decoder.

Example

BP ::= BIT STRING (SIZE (0..11)) (CONTAINING INTEGER (0..10) ENCODED BY
 {joint-iso-itu-t(2) asn1(1) packed-encoding(3) basic(0) aligned(0)})

Error Message

"bcc.asn", line 3 (BCC): C1300W: The time-optimized OER encoder/decoder does not support ContentsConstraint with ENCODED BY.

Possible Solution

Remove the directive or the type.

C1301E

Message Format

C1301E: Size constraint is always violated because size of OER encoding is a multiple of eight bits.

Message Cause

The size constraint of BIT STRING with CONTAINING is not a multiple of eight bits.

Example

	B ::= BIT STRING (SIZE (11)) (CONTAINING INTEGER (0..10))

Error Message

"bcc.asn", line 2 (BCC): C1301W: Size constraint is always violated because size of OER encoding is a multiple of eight bits.

Possible Solution

Change the size constraint.

C1305E

Message Format

C1305E: The asn1dflt configuration file must be the first input file.

Message Cause

An asn1dflt configuration file is preceded by other ASN.1 files on the command line. The asn1dflt must be the first input file.

Example

   asn1 -ber z.asn asn1dflt.x86

Error Message

"z.asn" (): C1305E: The asn1dflt configuration file must be the first input file.

Possible Solution

Make sure the configuration file is the first input file.

L1306W

Message Format

L1306W: OER encoding rules are not currently supported by <runtime>, therefore -oer option is ignored. Please contact OSS Nokalva (info@oss.com), if you are interested in OER support for this runtime.

Message Cause

You have specified the -lean, -soed, and -oer compiler options, but OER encoding rules are not supported by the ASN.1/C Lean Encoder/Decoder.

Example

  asn1 -soed -lean -oer test.asn

Error Message

L1306W: OER encoding rules are not currently supported by the ASN.1/C Lean Encoder/Decoder, therefore -oer option is ignored. Please contact OSS Nokalva (info@oss.com), if you are interested in OER support for this runtime.

Possible Solution

Compile the generated files using -DOSS_USE_FULL_SOED_ONLY and link with the SOED runtime. For information about OER support for the LEAN runtime, contact Technical Support ‹support@oss.com›.

NOTE: This error message is deprecated as of release 10.1.

C1307W

Message Format

C1307W: The value 'value reference' of the 'type reference' type is truncated to count elements to satisfy the size constraints applied to the type.

C1307W: The value of the 'type reference' type nested in 'value reference' is truncated to count elements to satisfy the size constraints applied to the type.

Message Cause

An ASN.1 value does not conform to a size constraint applied to SEQUENCE OF or SET OF in the value type and it will be truncated.

Example 1

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   A ::= SEQUENCE (SIZE (1..2)) OF INTEGER
   val A ::= {1, 2, 3}
END

Error Message

"sof1.asn", line 3 (M): C1307W: The value 'val' of the 'A' type is truncated to 2 elements to satisfy the size constraints applied to the type.

Example 2

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   S ::= SEQUENCE {
   b SEQUENCE (SIZE(0..1)) OF INTEGER
   }
   sv S ::= { b { 1, 2, 3 } }
END

Error Message

"sof2.asn", line 6 (M): C1307W: The value of the SEQUENCE OF type nested in 'sv' is truncated to 1 elements to satisfy the size constraints applied to the type.

Possible Solution

Make sure the value falls within the minimum and maximum values of the size constraint.

C1308W

Message Format

C1308W: The value for ''value reference' is being added with zero octets to satisfy the constraints.

Message Cause

An ASN.1 value of OCTET STRING with the PADDED directive applied does not conform to a fixed size constraint.

Example

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   O ::= OCTET STRING (SIZE (3)) --<PADDED>--
   val O ::= '0011'H
END

Error Message

"foct.asn", line 3 (M): C1308W: The value for 'val' is being added with zero octets to satisfy the constraints.

Possible Solution

Make sure the value falls within the fixed size constraint.

C1309W

Message Format

C1309W: The PADDED directive is not supported for type reference types with the -lean option and will be ignored.

Message Cause

An ASN.1 type definition with the PADDED directive applied is not supported for the LEAN runtime.

Example

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   B ::= BIT STRING (SIZE (3)) --<PADDED>--
   val B ::= '011'B
END

Error Message

"bits.asn", line 2 (M): C1309W: The PADDED directive is not supported for BIT STRING types with the -lean option and will be ignored.

Possible Solution

Remove the PADDED directive.

C1310I

Message Format

C1310I: No critical errors found, but message(s) were suppressed due to the compiler's default permissive mode. Compile with -noRelaxedMode to see all messages.

Message Cause

Certain errors or warnings are ignored when using the default relaxed mode.

Example

Module-C1310I DEFINITIONS ::= BEGIN
   My_Type ::= SET OF INTEGER
END

Error Message

C1310I: No critical errors found, but message(s) were suppressed due to the compiler's default permissive mode. Compile with -noRelaxedMode to see all messages.

Possible Solution

The message can be ignored. To enable a more thorough ASN.1 syntax checking, use the -noRelaxedMode option.

C1314W

Message Format

C1314W: This version of the OSS ASN.1 C# Compiler does not support %s.

Message Cause

The ASN1.DeferDecoding directive was specified with -exer and one or more compiler options. The directive cannot be used with the -exer compiler option due to implementation limitations.

Example

To compile the following example, specify the -exer and -noRelax compiler options.

--<ASN1.DeferDecoding C1314W.Type.f>--
 
C1314W DEFINITIONS ::= BEGIN
     Type ::= SET {
             f INTEGER
     }
END

Error Message

"c1314w.asn", line 5 (C1314W): C1314W: This version of the OSS ASN.1 C# Compiler does not support the ASN1.DeferDecoding directive with the EXTENDED-XER encoding rules.

A1315E

Message Format

A1315E: The outermost type where the 'fieldname' occurs is not set or sequence.

Message Cause

The 'At notation' is not inside a SET or SEQUENCE type.

Example

Module-A1315 DEFINITIONS ::= BEGIN
   MYCLASS ::= CLASS { &id INTEGER, &Type }
   MySet MYCLASS ::= { ... }

   T ::= CHOICE {
      id  MYCLASS.&id ({MySet}),
      val MYCLASS.&Type ({MySet}{@.id})
   }
END

Error Message

"a1315e0.asn", line 9 (Module-A1315): A1315E: The outermost type where the 'val' occurs is not set or sequence.

Possible Solution

Make sure the component relation constraints are correctly applied.

A1316E

Message Format

A1316E: The exponent of a REAL value after 'e' or 'E' shall not be empty.

Message Cause

The input ASN.1 syntax contains a REAL type value, but the exponent specified in the value is empty.

Example

Module-A1316E DEFINITIONS ::= BEGIN
   SomeType ::= REAL
   value SomeType ::= 1e
END

Error Message

"a1316e.asn", line 3 (Module-A1316E): A1316E: The exponent of a REAL value after 'e' or 'E' shall not be empty.
value SomeType ::= 1e

Possible Solution

Provide the appropriate exponent.

A1317E

Message Format

A1317E: The field 'identifier' is marked DEFAULT with the value that does not satisfy the constraints on its type.

Message Cause

The input ASN.1 syntax contains a SEQUENCE field that is marked as DEFAULT; however, its value does not conform to the constraint applied in the base type.

Example

Module-A1317E DEFINITIONS ::= BEGIN
    S ::= SEQUENCE {
        a IA5String (SIZE(1..10)) DEFAULT "CharacterString"
    }
END

Error Message

"a1317e.asn", line 3 (Module-A1317E): A1317E: The field 'a' is marked DEFAULT with the value that does not satisfy the constraints on its type.

Possible Solution

Make sure the value conforms to the subtype constraints.

C1318E

Message Format

C1318E: The CONTAINING alternative of the value of BIT/OCTET STRING is not supported by the Lean and Micro Encoder/Decoder for Java.

Message Cause

The CONTAINING keyword cannot be used in a value definition when the -lean or the -microEdition compiler option is specified.

Example

CCAC DEFINITIONS ::= BEGIN
   CCaC ::= BIT STRING (
   CONTAINING INTEGER
   )

   cCaC CCaC ::= CONTAINING 255
END

Error Message

"ccac.asn", line 3 (CCAC): C0730W: The type BIT/OCTET STRING with Contents Constraint is not supported by the Lean and Micro Encoder/Decoder for Java.

"ccac.asn", line 7 (CCAC): C1318E: The CONTAINING alternative of the value of BIT/OCTET STRING is not supported by the Lean and Micro Encoder/Decoder for Java.

Possible Solution

When you specify the value notation for a BIT STRING or an OCTET STRING with contents constraints, use the bstring or the hstring alternative.

C1319W

Message Format

C1319W: The %s directive is not supported without the %s option and will be ignored.

Message Cause

The specified directive has no effect without the compiler option(s).

Example

To compile the following example, specify the -noRelax compiler option.

--<OSS.InfoCallback C1319W.Type.f "InfoF">--

C1319W DEFINITIONS ::= BEGIN
      Type ::= SET {
              f INTEGER
      }
END

Error Message

"c1319w.asn", line 1 (): C1319W: The InfoCallback directive is not supported without the -enablePartialDecode/-partialDecodeOnly option and will be ignored.

Possible Solution

Specify the required compiler option or remove the directive.

A1320E

Message Format

A1320E: To use the -enablePartialDecode or -partialDecodeOnly compiler option, the ASN.1 input must include an OSS.DataCallback or OSS.InfoCallback directive.

Message Cause

The specified compiler option should not be used without at least one OSS.DataCallback or OSS.InfoCallback directive in the working set.

Example

To compile the following example, specify the -enablePartialDecode and -per compiler options.

A1320E DEFINITIONS ::= BEGIN
      Type ::= SET {
              f INTEGER
      }
END

Error Message

"a1320e.asn" (A1320E): A1320E: To use the -enablePartialDecode or -partialDecodeOnly compiler option, the ASN.1 input must include OSS.DataCallback and OSS.InfoCallback directives.

Possible Solution

Make sure that at least one OSS.DataCallback or OSS.InfoCallback directive is applied or remove the compiler option.

C1322W

Message Format

C1322W: The character {'number1','number2','number3','number4'} does not fit the current representation for UTF8String. Please consider using the OSS.UNIVERSALSTRING directive.

Message Cause

A UTF8String value contains characters that cannot be represented as code points within the Universal Character Set (UCS) code space. The C# string type (the standard representation of the ASN.1 UTF8String type) does not support these characters.

Example

Module- C1322W DEFINITIONS ::= BEGIN
    A ::= UTF8String
    a A ::= {0,20,0,0}
END

Error Message

"c1322w.asn", line 3 (Module- C1322W): C1322W: The character {0,20,0,0} does not fit the current representation for UTF8String. Please consider using the OSS.UNIVERSALSTRING directive.

Possible Solution

You can either remove the character from the string or apply the OSS.UNIVERSALSTRING directive to the corresponding type.

L1323W

Message Format

L1323W: The -microedition option has been deprecated and will not be available in future versions of the OSS ASN.1 Tools for Java.

Message Cause

The ASN.1 compiler command line contains the -microedition option. The -microedition option is deprecated as of release 6.2 of the OSS ASN.1 Tools for Java.

Possible Solution

Remove the -microedition option.

C1327E

Message Format

C1327E: Name '%s' identifying the %s of %s is not unique due to the '%s' encoding instruction.

Message Cause

There are two causes:

  • The ASN.1 type encoded as a JSON object contains JSON member name strings that are not unique.
  • Strings identifying enumeration items in the ASN.1 ENUMERATED type are not unique.

This occurs when the 'NAME' or the 'TEXT' JER encoding instruction is applied.

C1327E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Seq ::= SEQUENCE { 
		color [NAME AS "shape"] IA5String,
		shape IA5String 
  }
  Enum ::= [TEXT zero AS "one"] ENUMERATED {zero(0), one(1)}
END

Error Message

"c1327e.asn", line 3 (C1327E): C1327E: Name 'shape' identifying the component of Seq is not unique due to the 'NAME' encoding instruction.

"c1327e.asn", line 6 (C1327E): C1327E: Name 'one' identifying the enumeration item of Enum is not unique due to the 'TEXT' encoding instruction.

Possible Solution

Make sure the instruction does not violate uniqueness.

C1328E

Message Format

C1328E: TEXT encoding instruction refers to non-existing enumeration item '%s' in %s.

Message Cause

The identifier in the TEXT JER encoding instruction refers to an enumeration item that is not present in the ENUMERATED type.

C1328E DEFINITIONS JER INSTRUCTIONS  ::= BEGIN
  Enum ::= [TEXT zer AS "Null"] ENUMERATED {zero(0), one(1)}
END

Error Message

"c1328e.asn", line 2 (C1328E): C1328E: TEXT encoding instruction refers to non-existing enumeration item 'zer' in Enum.

Possible Solution

Correct the instruction and recompile.

A1329E

Message Format

A1329E: Duplicate %s in the TEXT encoding instruction applied to %s.

Message Cause

A duplicate identifier was found in the 'TEXT' JER encoding instruction.

A1329E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Enum ::= [TEXT zero AS "Null", zero AS "Zero"] ENUMERATED {zero(0), one(1)}
END

Error Message

"a1329e.asn", line 2 (A1329E): A1329E: Duplicate enumeration identifier 'zero' in the TEXT encoding instruction applied to Enum.

Possible Solution

Correct the instruction and recompile.

C1330E

Message Format

C1330E: The alternative '%s' shall not be %s.

Message Cause

The CHOICE alternative does not satisfy the restrictions imposed by the encoding rules.

C1330E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [UNWRAPPED] CHOICE {
		null NULL,
		...
	}
  }
END

Error Message

"c1330e.asn", line 3 (C1330E): C1330E: The alternative 'a1' shall not be an extensible CHOICE type with a final UNWRAPPED encoding instruction.

Possible Solution

Correct the specification and recompile.

C1331E

Message Format

C1331E: The alternative '%s' shall not produce a JSON value of the same kind as alternative '%s' of the [UNWRAPPED] CHOICE type '%s'.

Message Cause

Two alternatives of an [UNWRAPPED] CHOICE produce a JSON value of the same kind for one or more of their abstract values. The following kinds can be conflicting:

  • The null JSON token
  • The false JSON token
  • The true JSON token
  • A JSON number
  • A JSON string
  • A JSON array
C1331E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [TAG:1] INTEGER,
	a2 [TAG:2] INTEGER
  }
END

Error Message

"c1331e.asn", line 4 (C1331E): C1331E: The alternative 'a2' shall not produce a JSON value of the same kind as alternative 'a1' of the [UNWRAPPED] CHOICE type 'Ch'.

Possible Solution

Correct the specification and recompile.

C1332E

Message Format

C1332E: The alternative '%s' shall not produce a JSON object because it is already produced by alternative '%s' of the [UNWRAPPED] CHOICE type '%s'.

Message Cause

In an [UNWRAPPED] CHOICE there are two alternatives that produce a JSON object for one or more of their abstract values, but the alternative types are not SEQUENCE or SET types.

C1332E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [TAG:1] REAL,
	a2 [TAG:2] REAL
  }
END

Error Message

"c1332e.asn", line 4 (C1332E): C1332E: The alternative 'a2' shall not produce a JSON object because it is already produced by alternative 'a1' of the [UNWRAPPED] CHOICE type 'Ch'.

C1333E

Message Format

C1333E: The alternative '%s' shall be either a SEQUENCE type or a SET type because the [UNWRAPPED] CHOICE type '%s' has two or more alternatives that produce a JSON object.

Message Cause

The [UNWRAPPED] CHOICE type already contains an alternative which is either a SEQUENCE or SET that produces a JSON object for its abstract values. All other alternatives that produce a JSON object for one or more of their abstract values must be SEQUENCE or SET types without an extension marker.

C1333E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 SEQUENCE {
		f1 BOOLEAN
	},
	a2 REAL
  }
END

Error Message

"c1333e.asn", line 6 (C1333E): C1333E: The alternative 'a2' shall be either a SEQUENCE type or a SET type because the [UNWRAPPED] CHOICE type 'Ch' has two or more alternatives that produce a JSON object.

Possible Solution

Correct the specification and recompile.

C1334E

Message Format

C1334E: None of the alternatives '%s' and '%s' of the [UNWRAPPED] CHOICE type '%s' have at least one mandatory component whose JSON member name string differs from the JSON member name strings of all the components of the other.

Message Cause

Two or more [UNWRAPPED] CHOICE alternatives that are either SEQUENCE or SET types produce a JSON object for one or more of their abstract values. For any two such types, one of them must have at least one component that is not marked OPTIONAL or DEFAULT and whose JSON member name string differs from the JSON member name strings of all the components of the other type.

C1334E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [TAG:1] SEQUENCE { f1 INTEGER },
	a2 [TAG:2] SEQUENCE { f1 INTEGER }
  }
END

Error Message

"c1334e.asn", line 2 (C1334E): C1334E: None of the alternatives 'a1' and 'a2' of the [UNWRAPPED] CHOICE type 'Ch' have at least one mandatory component whose JSON member name string differs from the JSON member name strings of all the components of the other.

Possible Solution

Correct the specification and recompile.

A1335W

Message Format

A1335W: The -allow BadExplicitAutomaticTagging command line option forces the field 'fieldName' to have explicit automatic tagging. It may cause errors at runtime.

Message Cause

The -allow BadExplicitAutomaticTagging command-line option instructs the compiler to conform to the pre-2002 ASN.1 standard (X.680 clause 31.2.7 c) interpretation and use explicit automatic tagging for untagged and tagged CHOICE types, open types, and "DummyReference" types.

Example

B4114 DEFINITIONS AUTOMATIC TAGS ::= BEGIN
    Seq ::= [65] SEQUENCE { ch Cho }
    Cho ::= [65] CHOICE { b BOOLEAN }
END

Error Message

"b4114.asn", line 2 (B4114): A1335W: The -allow BadExplicitAutomaticTagging command line option forces the field 'ch' to have explicit automatic tagging. It may cause errors at runtime.

Possible Solution

Remove the -allow BadExplicitAutomaticTagging option from the command line.

C1336E

Message Format

C1336E: Invalid Java module name 'module name'. Please provide a name that can be used as Java module name.

Message Cause

The name specified using the -javaModule compiler option is invalid and cannot be used as a Java 9 module name because it does not conform to Section 7.7 Module Declarations of the Java Language Specification Version 9.

Possible Solution

Correct the parameter of the -javaModule compiler option.

C1337W

Message Format

C1337W: This version of OSS ASN.1 Tools for %s does not support the SET OF type with the CANONICAL-PER encoder and CANONICAL-PER decoder set to the strict conformance level.

Message Cause

You have specified the -cper or -cuper compiler option, but the SET OF type is not supported due to implementation restrictions.

Example

C1337W DEFINITIONS ::= BEGIN
    S ::= SET OF INTEGER
END

Error Message

"c1337w.asn", line 3 (C1337W): C1337W: This version of OSS ASN.1 Tools for C# does not support the SET OF type with the CANONICAL-PER encoder and CANONICAL-PER decoder set to the strict conformance level.

Possible Solution

The warning message can be suppressed with the -suppress 1337 compiler option.

NOTE: Even if the message is suppressed, the attempt to encode a SET OF value with the CANONICAL-PER encoder or to decode a SET OF encoded value with the CANONICAL-PER decoder set to strict conformance level will cause a runtime error.

C1338W

Message Format

C1338W: This version of OSS ASN.1 Tools for %s does not support the GeneralString, GraphicString and ObjectDescriptor types with the CANONICAL-PER encoder and PER decoder set to the strict conformance level.

Message Cause

You have specified the -cper or -cuper compiler option, but the GeneralString, GraphicString, and ObjectDescriptor types are not supported due to implementation restrictions.

Example

C1338W DEFINITIONS ::= BEGIN
    G ::= GeneralString
    GR ::= GraphicString
    OD ::= ObjectDescriptor
END

Error Message

"c1338w.asn", line 3 (C1338W): C1338W: This version of OSS ASN.1 Tools for C# does not support the GeneralString, GraphicString and ObjectDescriptor types with the CANONICAL-PER encoder and PER decoder set to the strict conformance level.

"c1338w.asn", line 4 (C1338W): C1338W: This version of OSS ASN.1 Tools for C# does not support the GeneralString, GraphicString and ObjectDescriptor types with the CANONICAL-PER encoder and PER decoder set to the strict conformance level.

"c1338w.asn", line 5 (C1338W): C1338W: This version of OSS ASN.1 Tools for C# does not support the GeneralString, GraphicString and ObjectDescriptor types with the CANONICAL-PER encoder and PER decoder set to the strict conformance level.

Possible Solution

The warning message can be suppressed with the -suppress 1338 compiler option.

NOTE: Even if the message is suppressed, the attempt to encode a GeneralString, GraphicString and ObjectDescriptor value with the CANONICAL-PER encoder or to decode a GeneralString, GraphicString, and ObjectDescriptor encoded value with the PER decoder set to strict conformance level will cause a runtime error.

A1339E

Message Format

A1339E: The node identifier(number1) conflicts with the predefined node 'identifier(number2).

Message Cause

An OBJECT IDENTIFIER value has an identifier(number1) node, but identifier is assigned to number2 according to Rec. ITU-T X.660 | ISO/IEC 9834-1.

Example

Module-A1339E DEFINITIONS ::= BEGIN
   O ::= OBJECT IDENTIFIER
   o O ::= {itu-t(0) recommendation (7)}
END

Error Message

"a1339e.asn",line 3(Module-A1339E): A1339E: The node 'recommendation(7)' conflicts with the predefined node 'recommendation(0)'.

Possible Solution

Rename the node to avoid the name conflict.

C1341E

Message Format

C1341E: With the CANONICAL-XER encoder the Remove directive cannot be applied to the component '%s' because components with a DEFAULT value must be encoded and therefore cannot be removed.

Message Cause

You have specified the -cxer compiler option, but the ASN1.Remove directive is applied to a SET or SEQUENCE component with a default value. According to ITU-T Recommendation X.693 (11/2008) paragraphs 9.5 and 9.6.3, this is not supported due to implementation restrictions.

Example

--<ASN1.Remove C1341E.Seq.d>--

C1341E DEFINITIONS ::=
BEGIN
    Seq ::= SEQUENCE {
        d OCTET STRING DEFAULT '0'H
    }
END

Error Message

"c1341e.asn", line 6 (C1341E): C1341E: With the CANONICAL-XER encoder the Remove directive cannot be applied to the component 'd' because components with a DEFAULT value must be encoded and therefore cannot be removed.

Possible Solution

Choose one of the following options:

  • Do not specify the -cxer compiler option.
  • Do not apply the ASN1.Remove directive to components with a default value.
  • Do not specify default values for SET or SEQUENCE components.

C1342E

Message Format

C1342E: The directive name directive is not permitted on elements of SEQUENCE OF and SET OF types. C1342E: The directive name directive is not permitted here.

Message Cause

The OSS.NODECODE or OSS.NODECODE directive is applied to a type or a component on which it is not permitted. The directives can be applied only to OPTIONAL fields, extension additions, and to PDU types.

Example

--<OSS.NODECODE Module-C1342E.S.*>--

Module-C1342E DEFINITIONS ::= BEGIN
    S ::= SEQUENCE OF BOOLEAN
END

Error Message

"c1342e.asn", line 2 (Module-C1342E): C1342E: The NODECODE directive is not permitted on elements of SEQUENCE OF and SET OF types.

Possible Solution

Remove the directive.

C1343E

Message Format

C1343E: The directive name directive is applied to the field 'identifier' but not to all fields of the extension group.

Message Cause

The OSS.NODECODE or OSS.NODECODE directive is applied to some, but not all, fields of an extension addition group.

Example

Module-C1343E DEFINITIONS ::= BEGIN
    S ::= SEQUENCE {
		...,
		[[
        b BOOLEAN --<NOENCODE>--,
        i INTEGER
		]]
    }
END

Error Message

"c1343e.asn", line 6 (Module-C1343E): C1343E: The NOENCODE directive is applied to the field 'b' but not to all fields of the extension group.

Possible Solution

Remove the directive or apply it to all the fields of the extension addition group.

C1344E

Message Format

C1344E: The directive name directive is applied to field 'identifier' which is not an OPTIONAL field or an extension addition.

Message Cause

The OSS.NOENCODE or OSS.NODECODE directive is applied to a mandatory or DEFAULT field that is not an extension addition.

Example

Module-C1344E DEFINITIONS ::= BEGIN
    S ::= SEQUENCE {
        f OCTET STRING --<NODECODE>--,
        ...
    }
END

Error Message

"c1344e.asn", line 3 (Module-C1344E): C1344E: The NODECODE directive is applied to field 'f' which is not an OPTIONAL field or an extension addition.

Possible Solution

Remove the directive.

C1345E

Message Format

C1345E: The NOENCODE directive is applied to the extension addition 'identifier' but not to all subsequent extension additions.

Message Cause

The OSS.NOENCODE directive is not applied to an extension addition but it is applied to a preceding extension addition of the type.

Example

--<OSS.NOENCODE Module-C1345E.S.e1>--
Module-C1345E DEFINITIONS AUTOMATIC TAGS ::= BEGIN
    S ::= SEQUENCE {
        ...,
        e1 INTEGER,
        e2 REAL
    }
END

Error Message

"c1345e.asn", line 5 (Module-C1345E): C1345E: The NOENCODE directive is applied to the extension addition 'e1' but not to all subsequent extension additions.

Possible Solution

Make sure the directive is applied to all trailing extension additions or remove the directive.

C1346W

Message Format

C1346W: The type 'type reference' is not a PDU type. The directive name directive will be ignored.

Message Cause

The OSS.NODECODE or OSS.NODECODE directive is applied to a named type that is not a PDU type.

Example

--<OSS.NOENCODE Module-C1346W.I>--
Module-C1346W DEFINITIONS AUTOMATIC TAGS ::= BEGIN
    I ::= INTEGER
    S ::= SEQUENCE {
        f1 REAL OPTIONAL,
        f2 I
    }
END

Error Message

"c1346w.asn", line 2 (Module-C1346W): C1346W: The type 'I' is not a PDU. The NODECODE directive will be ignored.

Possible Solution

Remove the directive.

C1347W

Message Format

C1347W: The NOENCODE directive is applied to the DEFAULT field 'identifier'. The directive will be ignored by the CANONICAL-XER encoder.

Message Cause

The OSS.NOENCODE directive is applied to a DEFAULT field. According to the CANONICAL-XER rules, this is not allowed; DEFAULT fields must be encoded.

Example

--<OSS.NOENCODE Module-C1347W.S.e1>--
Module-C1347W DEFINITIONS AUTOMATIC TAGS ::= BEGIN
    S ::= SEQUENCE {
        ...,
        e1 INTEGER DEFAULT 10,
        e2 REAL
    }
END

Error Message

"c1347w.asn", line 5 (Module-C1347W): C1347W: The NOENCODE directive is applied to DEFAULT field 'e1'. The directive will be ignored by the CANONICAL-XER encoder.

Possible Solution

Remove the directive or suppress the warning using the -suppress 1347 compiler option.

C1348W

Message Format

C1348W: The directive name directive is not permitted on components of a SET/SEQUENCE/CHOICE and will be ignored.

Message Cause

The OSS.ENCODEONLY or OSS.DECODEONLY directives is applied to a component of a SET, SEQUENCE, or CHOICE type.

Example

--<OSS.DECODEONLY Module-C1348W.S.e1>--
Module-C1348W DEFINITIONS AUTOMATIC TAGS ::= BEGIN
    S ::= SEQUENCE {
        ...,
        e1 INTEGER DEFAULT 10,
        e2 REAL
    }
END

Error Message

"c1348w.asn", line 5 (Module-C1348W): C1348W: The DECODEONLY directive is not permitted on components of a SET/SEQUENCE/CHOICE and will be ignored.

Possible Solution

Remove the directive.

C1349W

Message Format

C1349W: DECODEONLY and ENCODEONLY directives are deprecated, use NOENCODE and NODECODE, respectively.

Message Cause

You have specified the OSS.ENCODEONLY or OSS.DECODEONLY deprecated directive.

Example

--<OSS.ENCODEONLY Module-C1349W.S.*>--

Module-C1349W DEFINITIONS ::= BEGIN
    S ::= SEQUENCE OF BOOLEAN
END

Error Message

""c1349w.asn", line 4 (Module-C1349W): C1349W: DECODEONLY and ENCODEONLY directives are deprecated, use NOENCODE and NODECODE, respectively.

Possible Solution

Use the OSS.NODECODE directive instead of OSS.ENCODEONLY and the OSS.NOENCODE directive instead of OSS.DECODEONLY.

C1352W

Message Format

C1352W: Runtime constraint checking may fail for the field inside 'type reference' which has a component relation constraint and a type constraint because the type specified in the type constraint is not included in the constraining information object set 'information object set name' for the classfield 'field name'.

Message Cause

Runtime constraint checking cannot be performed when the type specified in the type constraint is not included in the constraining information object set.

Example

C1352W DEFINITIONS ::= BEGIN
    EXT-TYPE ::= CLASS {
        &extRef INTEGER UNIQUE,
        &ExtValue
    } WITH SYNTAX {&ExtValue IDENTIFIED BY &extRef}

   SAMapplicationData::= OCTET STRING
   ServiceInfoExtTypes EXT-TYPE ::= {
        { SAMapplicationData    IDENTIFIED BY 85 },
        ...
   }
   TST ::= SEQUENCE {
        extensionId EXT-TYPE.&extRef({ServiceInfoExtTypes }),
        value  EXT-TYPE.&ExtValue({ServiceInfoExtTypes }{@.extensionId})
   } (WITH COMPONENTS {
        extensionId (85),
        value (SAMapplicationData (CONTAINING INTEGER)) }) 
END

Error Message

"c1352w", line 13 (C1352W): C1352W: Runtime constraint checking may fail for the field inside 'TST' which has a component relation constraint and a type constraint because the type specified in the type constraint is not included in the constraining information object set 'ServiceInfoExtTypes' for the classfield '&ExtValue'.

Possible Solution

Add an information object along with the type specified in the type constraint to the constraining information object set or replace the type specified in the type constraint with the type included in the information object set.

C1353W

Message Format

C1353W: The 'directive-name' directive is not supported with the type 'type-name' and will be ignored.

Message Cause

The input ASN.1 syntax contains a compiler directive application that is not supported with the specified ASN.1 type.

Example

----
  Mod DEFINITIONS ::= BEGIN
    A ::= ENUMERATED {one, two}
  END
END

Error Message

C1353W: The UserClass directive is not supported with the type ENUMERATED and will be ignored.

Possible Solution

Refer to the OSS ASN.1 Compiler Directives section of the online manual to learn about applying directives to types.

A1354W

Message Format

A1354W: The extensible type 'type reference' contains an untagged open type, check the field 'field name', for which a tag is required to distinguish it from the conceptually added element.

Message Cause

The input ASN.1 syntax contains an extensible type that includes an open type listed before the extension marker without an explicit tag. This violates the tag uniqueness requirement in X.681 14.2 b) NOTE 2, X.680, 52.7.3, 52.7.4, and therefore 25.7.

Example

B4613 DEFINITIONS  ::= BEGIN
C ::= CLASS {
	&id INTEGER,
	&T
}
OS C ::= {{&id 13, &T REAL }}
S ::= SEQUENCE {
	a C.&id ({OS}),
	b C.&T({OS}{@a})  OPTIONAL,
	...
}
END

Error Message

"b4613.asn", line 13 (B4613): A1354W: The extensible type 'S' contains an untagged open type, check the field 'b', for which a tag is required to distinguish it from the conceptually added element.

Possible Solution

Add an explicit tag to the open type.

C1355W

Message Format

C1355W: The OSS.%s directive is ignored because the DeferDecoding directive is applied to the same component.

Message Cause

The OSS.DataCallback or OSS.InfoCallback directive is applied to the same component to which the ASN1.DeferDecoding directive is applied.

Example

--<OSS.DataCallback M.Company.address "test">-- 
--<ASN1.DeferDecoding M.Company.address>-- M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
    Company ::= SEQUENCE {
        name VisibleString,
        address VisibleString
    }
END

Error Message

"c1355w.asn", line 6 (M): C1355W: The OSS.DataCallback directive is ignored because the DeferDecoding directive is applied to the same component.

Possible Solution

Remove the OSS.DataCallback directive.

L1358W

Message Format

"L1358W: The '%s' option will be ignored by the %s."

Message Cause

The ASN.1 compiler option is not supported by the encoder or decoder for the specified encoding rules and will be ignored.

Example

asn1 -jer -uper -enablePartialDecode rrc.asn

The -enablePartialDecode option can be used with -uper but not it cannot be used with -jer.

Error Message

"L1358W: The '-enablePartialDecode' option will be ignored by the JER decoder.

Possible Solution

Suppress the warning by the -suppress 1358 option or ignore it.

C1359E

Message Format

C1359E: Using different binary and textual encoding rules for a top-level PDU and inside contents constraint is not supported by the -partialDecodeOnly option.

Message Cause

The -partialDecodeOnly ASN.1 compiler option is not supported when the binary encoding rules (BER, DER, PER, or OER) are used for a PDU type that includes a contents constraint for which one of the textual encoding rules (XER, EXER, JER, or AVN) is specified in the ENCODED BY syntax and vice versa.

Example

asn1 -uper -jer -partialDecodeOnly abc.asn

OS ::= OCTET STRING (CONTAINING INTEGER (0..10) ENCODED BY
 {joint-iso-itu-t asn1(1) json-encoding (8)})

The OSS_PER_ALIGNED rules were set before the ossPartialDecode() call was issued.

Message Format

C1359E: Using different binary and textual encoding rules for a top-level PDU and inside contents constraint is not supported by the -partialDecodeOnly option.

Possible Solution

Use the -enablePartialDecode compiler option instead of -partialDecodeOnly.

C1360W

Message Format

C1360W: Automatic decoding of the open type field 'field name' will not be possible when it precedes the referenced field 'field name' in the JSON encoding.

Message Cause

The -json option is specified and the ASN.1 syntax contains a component relation constraint whose referenced field belongs to an upper nesting level related to an open type. When that particular open type precedes the referenced field in a JSON encoding, the TOED decoder cannot automatically decode it. Only its encoded form is left in the open type representation.

Note that in ASN.1 specifications, an open type field usually follows its referenced field. In JSON encodings produced by OSS encoders, the field order corresponds to the order in the ASN.1 specification, therefore automatic decoding is possible for these encodings.

Example

Module-C1360W DEFINITIONS ::=
BEGIN
    ERROR-CLASS ::= CLASS {
        &code   INTEGER UNIQUE,
        &Type
    }
    WITH SYNTAX {&code &Type}

    ErrorSet ERROR-CLASS ::=
			{ {1 BIT STRING}, ..., {2 INTEGER} }

    ErrorReturn ::= SEQUENCE {
        code ERROR-CLASS.&code ({ErrorSet}),
        error SEQUENCE {
            info ERROR-CLASS.&Type ({ErrorSet}{@code})
        }
    }
END

JSON encoding of the ErrorReturn PDU:

{
  "error":{
    "info":100
  },
  "code":2
}

Error Message

"otp.asn", line 13 (Module-C1360W): C1360W: Automatic decoding of the open type field 'info' will not be possible when it precedes the referenced field 'code' in the JSON encoding

Possible Solution

To make automatic decoding possible, ensure open type fields always follow their referenced fields in JSON encodings, as shown in the following JSON encoding of the ErrorReturn PDU (notice how info follows code):

{
  "code":2,
  "errors":{
    "info":100
  }
}

L1361E

Message Format

L1361E: The 'path' directory, specified in the -getFiles option, does not exist.

Message Cause

The directory specified in the -getFiles option must exist and contain encoding files with the filename extension matching the second argument.

Example

asn1step bcas -getFiles myPath,ber -decode BBCard -xer

Error Message

L1361E: The 'myPath' directory, specified in the -getFiles option, does not exist.

Possible Solution

Specify a correct directory where encoding files to be used in decoding are located.

L1362E

Message Format

L1362E: Invalid 'ext' encoding filename extension, supported extensions are ber, der, cer, per, uper, xer, cxer, exer, xml, oer, coer, cper, cuper, json, jer, csv, cdr.

Message Cause

The mandatory second argument to the -getFiles option must be one of the pre-defined encoding filename extensions that are used to determine which encoding rules to use in decoding.

Example

asn1step bcas -getFiles myPath,abc -decode BBCard -xer

Error Message

L1362E: Invalid 'abc' encoding filename extension, supported extensions are ber, der, cer, per, uper, xer, cxer, exer, xml, oer, coer, cper, cuper, json, jer, csv, cdr.

Possible Solution

Specify one of pre-defined filename extensions.

L1363E

Message Format

L1363E: No encoding files with the 'ext' extension found in the 'path' directory.

Message Cause

The directory specified in the -getFiles option does not contain encoding files with the filename extension matching the second argument.

Example

asn1step bcas -getFiles myPath,per -decode BBCard -xer

Error Message

L1363E: No encoding files with the 'per' extension found in the 'myPath' directory.

Possible Solution

Specify a correct directory where encoding files to be used in decoding are located.

L1364E

Message Format

L1364E: The '-getFiles' option is supported only with the '-decodePdu' option.

Message Cause

The -getFiles option is specified with other than the -decodePdu option, for example with the -encodeValue or -generateMessages option.

Example

asn1step bcas -getFiles myPath,per -encodeValue myCard

Error Message

L1364E: The '-getFiles' option is supported only with the '-decodePdu' option.

Possible Solution

Remove the -getFiles option if you don't need to use -decodePdu or specify -decodePdu and remove the other option from the command line.

C1365E

Message Format

C1365E: The 'num' requested number of messages to generate exceeds the limit of '10000'.

Message Cause

The second argument to the -generateMessages option, which specifies the maximum number of messages to generate, is greater than the implementation limit of 10 in the trial version or 10,000 in the production version of ASN-1Step.

Example

asn1step bcas -generateMessage BBCard,10001 -ber

Error Message

C1365E: The '10001' requested number of messages to generate exceeds the limit of '10000'.

Possible Solution

If you are using the trial version, specify a number that is less than or equal 10 or contact OSS to obtain the production version of ASN-1Step. If you are using the production version and need to generate more than 10,000 messages with one invocation of ASN-1Step, contact OSS to request this feature.

C9999S

Message Format

C9999S: Porting error. Inform OSS technical support.

Message Cause

The ASN.1 compiler has encountered an error when porting the ASN.1 compiler to your platform.

This error can occur if your ossinfo file is corrupt, is outdated, or is not compatible with your installation set up.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.


This documentation applies to the latest versions of the OSS® ASN.1 Tools software.

Copyright © 2022 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.