Message Class 1004 - IDL Compiler

This message class is returned if an error occurred concerning the Software AG IDL Compiler. Messages of this class have the format:

1004nnnn

where 1004 is the message class, and
nnnn is the message number in the range 0000 - 9999.

Overview of Messages

10040001 | 10040002 | 10040003 | 10040004 | 10040005 | 10040006 | 10040007 | 10040008 | 10040009 | 10040010 | 10040011 | 10040012 | 10040013 | 10040014 | 10040015 | 10040016 | 10040017 | 10040018 | 10040019 | 10040020 | 10040021 | 10040022 | 10040023 | 10040024 | 10040025 | 10040026 | 10040027 | 10040028 | 10040029 | 10040030 | 10040031 | 10040032 | 10040033 | 10040034 | 10040035 | 10040036 | 10040037 | 10040038 | 10040039 | 10040040 | 10040041 | 10040042 | 10040043 | 10040044 | 10040045 | 10040046 | 10040047 | 10040048 | 10040049 | 10040050 | 10040051 | 10040052 | 10040053 | 10040054 | 10040055 | 10040056 | 10040057 | 10040058 | 10040059 | 10040060 | 10040061 | 10040062 | 10040063 | 10040064 | 10040065 | 10040066 | 10040067 | 10040068 | 10040069 | 10040070 | 10040071 | 10040072 | 10040073 | 10040074 | 10040075 | 10040076 | 10040077 | 10040078 | 10040079 | 10040080 | 10040083 | 10040084 | 10040085 | 10040086 | 10040087 | 10040088 | 10040089 | 10040090 | 10040091 | 10040092 | 10040093
10040001 No template file given
Explanation

A template file is mandatory to run the Software AG IDL Compiler.
Action

Specify a template file using the -t option.

10040002 Template file <file-name> open failed
Explanation

The template file specified could not be opened for one of the following reasons:

  1. The path or template file does not have read access.

  2. The template file is missing.
Action

Depending on the situation above, provide the template file and grant read access to the IDL Compiler.

10040003 Template file <file-name> is too large (Max. 1MB)
Explanation

The maximum size for the template file has been exceeded.
Action

  1. For customer-written template files:
    Create several smaller files from your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040004 #endif expected in template
Explanation

When parsing the template file, the following error was detected: An expected #endif preprocessor statement was not found in the template file.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040005 Premature end of template file occurred
Explanation

When parsing the template file, an unexpected end-of-file condition occurred.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040006 Illegal opcode in template
Explanation

When running the template file an illegal operation code was detected.

Action

Contact Software AG Support.
10040007 Illegal number
Explanation

When running the template file, an illegal number was found in a template variable.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040008 Illegal character occurred in code: '<code>'
Explanation

When parsing the template file, an illegal character was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040009 %block without block
Explanation

When parsing the template file, the following error was detected:
A block was missing.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040010 %library{ } must not be an inner loop
Explanation

When parsing the template file, the following error was detected:
A library loop could not be placed within another library loop.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040011 %program{ }-loop must be embedded in %library{ }-loop
Explanation

When parsing the template file, the following error was detected:
A program loop must be placed within a library loop.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040012 %name{ }-loop must be embedded in %program or %x_struct { }-loop
Explanation

When parsing the template file, the following error was detected:
A name loop must be placed within a program or x_struct loop.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040013 %x_struct{ }-loop must be embedded in %library{ }-loop
Explanation

When parsing the template file, the following error was detected:
An x_struct loop must be placed within a library loop.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040014 Illegal environment variable syntax
Explanation

When parsing the template file, the following error was detected:
The syntax for environment variables is incorrect.
Environment variables must be surrounded by parentheses: '(' and ')'.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040015 Illegal numeric variable: '%compute'
Explanation

When parsing or running the template file, an illegal numeric variable was found in a template variable.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040016 Illegal string variable <variable>: '%assign'
Explanation

When parsing or running the template file, an illegal string was detected in a template variable.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040017 Illegal closing brackets of array string variable <variable>: '%assign'
Explanation

When parsing or running the template file, an array string variable could not be determined correctly.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040018 Illegal opening brackets of array string variable <variable>: '%assign'
Explanation

When parsing or running the template file, an array string variable could not be determined correctly.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040019 Array string variable out of bounds
Explanation

When running the template file, an array string variable could not be determined correctly. Array variables must be in the range 0 - 8.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040020 %Sanitize<flag> is unknown
Explanation

When parsing the template file, an illegal statement was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040021 %using I must have specified 1, 2 or 4
Explanation

When parsing the template file, an illegal length for the data type integer was detected.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040022 %using F must have specified 4 or 8
Explanation

When parsing the template file, an illegal length for the data type float was detected.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040023 Illegal character occurred in %using <type>: '<char>' (0x%.2X)
Explanation

When parsing the template file, an illegal data type was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040024 Recursive type specification, <output-statement> used in %u clause
Explanation

When parsing the template file, an error was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040025 Illegal %-specification '<char>'
Explanation

When parsing the template file, an illegal statement was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040026 } without block
Explanation

When parsing the template file, a closing brace was detected without the corresponding opening one.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040027 Unsupported %-format: <char>
Explanation

When running the template file, an unsupported format was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040028 <statement> is unknown
Explanation

An incorrect <statement> was found in the template file.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040029 Illegal string
Explanation

When parsing the template file, a string could not be determined correctly.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040030 String continues on next line
Explanation

When parsing the template file, a string could not be determined correctly. A string must not continue on the next line.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040031 String missing: <string>
Explanation

When parsing the template file, a string was expected but did not occur.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040032 Missing ')' in expression
Explanation

When running the template file, an illegal expression was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040033 Bad expression (read '<expression>')
Explanation

When running the template file, an illegal expression was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040034 Level nesting exceeded
Explanation

When running the template file, the maximum number of levels was exceeded.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040035 Recursion too deep
Explanation

When parsing the template file, an error was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040036 <statement> blocks exceeded, maximum is <number>
Explanation

When parsing the template file, the maximum number of nested blocks for statement <statement> of <number> was exceeded.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040037 Internal error
Explanation

An unexpected error occurred when running the Software AG IDL Compiler.
Action

Contact Software AG Support.
10040038 Can access <output-statement> only in <control-statement>-loop
Explanation

When running the template file, a statement was executed which was not placed in its proper loop statement.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040039 Premature EOF within preprocessor block in template
Explanation

When parsing the template file, an unexpected end-of-file condition occurred.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040040 Unknown preprocessor command <command> in template
Explanation

When parsing the template file, an unknown statement was detected.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040041 #endif found without #ifdef in template
Explanation

When parsing the template file, an #endif was found without a corresponding #ifdef preprocessor statement.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040042 #else found without #ifdef in template
Explanation

When parsing the template file, an #else was found without a corresponding #ifdef preprocessor statement.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040043 #elif found without #ifdef in template
Explanation

When parsing the template file, an #elif was found without a corresponding #ifdef preprocessor statement.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040044 #elif found after #else in template
Explanation

When parsing the template file, an #elif was found after a corresponding #else preprocessor statement.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040045 #ifdef found before #endif in template
Explanation

When parsing the template file, an #ifdef was found before an #endif preprocessor statement.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040046 <statement> found without DEFINITION in template
Explanation

An incorrect <statement> was found in the template file.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040047 Software AG IDL file <file-name> open failed
Explanation

The Software AG IDL file specified could not be opened for one of the following reasons:

  1. The path or Software AG IDL file does not have read access.

  2. An incorrect name was given for the IDL file or it is missing.
Action

Depending on the situation above, provide the Software AG IDL file and/or give read access to the IDL Compiler.

10040048 Software AG IDL file parse error
Explanation

When parsing the Software AG IDL file, an error occurred.
Action

Correct your IDL file and rerun the IDL Compiler.
10040049 Usage error
Explanation

The Software AG IDL Compiler was called with an incorrect template file, IDL file or option settings.

Action

Supply the IDL Compiler with correct parameters.
10040050 Out of memory
Explanation

A memory request by the IDL Compiler could not be fulfilled by the operating system.

Action

Increase your memory resources and rerun the IDL Compiler.
10040051 Pushback character limit reached
Explanation

The maximum number of pushback characters was reached by the operating system.

Action

Contact Software AG Support.
10040052 Label table overflow
Explanation

The maximum number of labels was reached by the operating system.
Action

Contact Software AG Support.
10040053 Output buffer overflow
Explanation

An overflow of the output buffer occurred.
Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040054 Library name is too long
Explanation

A library name specified in the IDL file is too long. The maximum number of characters is 128.

Action

Correct your IDL file and rerun the IDL Compiler.
10040055 Library name is empty
Explanation

A library name specified in the IDL file contains no characters.
Action

Correct your IDL file and rerun the IDL Compiler.
10040056 Library alias name is too long
Explanation

A library alias name specified in the IDL file is too long. The maximum number of characters is 128.

Action

Correct your IDL file and rerun the IDL Compiler.
10040057 Library alias name is empty
Explanation

A library alias name specified in the IDL file contains no characters.

Action

Correct your IDL file and rerun the IDL Compiler.
10040058 Program <program-name> already defined
Explanation

A program with the same name has already been defined in the IDL file.

Action

Correct your IDL file and rerun the IDL Compiler.
10040059 Program alias <alias-name> already defined
Explanation

A program alias with the same name has already been defined in the IDL file.

Action

Correct your IDL file and rerun the IDL Compiler.
10040060 Program name is too long
Explanation

A program name specified in the IDL file is too long. The maximum number of characters is 128.

Action

Correct your IDL file and rerun the IDL Compiler.
10040061 Program name is empty
Explanation

A program name specified in the IDL file contains no characters.
Action

Correct your IDL file and rerun the IDL Compiler.
10040062 Program alias name is too long
Explanation

A program alias name specified in the IDL file is too long. The maximum number of characters is 128.

Action

Correct your IDL file and rerun the IDL Compiler.
10040063 Program alias name is empty
Explanation

A program alias name specified in the IDL file contains no characters.

Action

Correct your IDL file and rerun the IDL Compiler.
10040064 Structure <structure-name> already defined
Explanation

A structure with the same name has already been defined in the IDL file.

Action

Correct your IDL file and rerun the IDL Compiler.
10040065 Structure name is too long
Explanation

A structure name specified in the IDL file is too long. The maximum number of characters is 128.

Action

Correct your IDL file and rerun the IDL Compiler.
10040066 Structure name is empty
Explanation

A structure name specified in the IDL file contains no characters.
Action

Correct your IDL file and rerun the IDL Compiler.
10040067 Structure <structure-name> not defined
Explanation

An structure not defined in the IDL file was referenced.
Action

Correct your IDL file and rerun the IDL Compiler.
10040068 Level must be at least <level-number>
Explanation

An incorrect level for parameters is specified in the IDL file.
Action

Correct your IDL file and rerun the IDL Compiler.
10040069 Level must be <level-number>
Explanation

An incorrect level for parameters is specified in the IDL file.
Action

Correct your IDL file and rerun the IDL Compiler.
10040070 Parameter name is too long
Explanation

A parameter name specified in the IDL file is too long. The maximum number of characters is 31.

Action

Correct your IDL file and rerun the IDL Compiler.
10040071 Maximum level is <level-number>
Explanation

An incorrect level for parameters is specified in the IDL file.
Action

Correct your IDL file and rerun the IDL Compiler.
10040072 Index bound is too high
Explanation

A dimension specification for a parameter in the IDL file was too high. The maximum limit for upper bounds is 1073741824.

Action

Correct your IDL file and rerun the IDL Compiler.
10040073 Invalid dimension specification
Explanation

The specification of a dimension for a parameter in the IDL file was incorrect.

Action

Correct your IDL file and rerun the IDL Compiler.
10040074 Errors in the IDL file <file-name> detected
Explanation

Errors in the IDL file were detected - generation failed.
Action

Correct your IDL file and rerun the IDL Compiler.
10040075 Recursion of parameter detected - invalid IDL file
Explanation

A parameter recursion occurred in the IDL file.
Action

Correct your IDL file and rerun the IDL Compiler.
10040076 Group parameter '<parameter-name>' has no members
Explanation

A group defined in the IDL file has no members.
Action

Correct your IDL file and rerun the IDL Compiler.
10040077 No output file open
Explanation

When running the template file, an output statement was supposed to be executed but no file was open.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040078 Could not open %f file <file-name>
Explanation

An output file could not be opened for one of the following reasons:

  1. The path or file does not have write access.

  2. The file name is incorrect.
Action

Depending on the situation above, provide write access to the IDL Compiler or correct the file name.
10040079 -P Option is limited to 32 characters
Explanation

The IDL Compiler was called with incorrect parameter -P. The length of an option is limited to 32 characters.

Action

Supply the IDL Compiler with correct parameters.
10040080 Max. -P options = <max-number>
Explanation

The IDL Compiler was called with too many options. The maximum possible number of options is <max-number>.

Action

Supply the IDL Compiler with correct parameters.
10040083 Illegal option - <option>
Explanation

The IDL Compiler was called with incorrect parameters.
Action

Supply the IDL Compiler with correct parameters.
10040084 Option must be followed by whitespace - <option>
Explanation

The IDL Compiler was called with incorrect parameters. All options must be followed by whitespace.

Action

Supply the IDL Compiler with correct parameters.
10040085 Option requires an argument - <option>
Explanation

The IDL Compiler was called with incorrect parameters. The given option requires an argument.

Action

Supply the IDL Compiler with correct parameters.
10040086 Option must not be clustered - <option>
Explanation

The IDL Compiler was called with incorrect parameters. Options must not be clustered.

Action

Supply the IDL Compiler with correct parameters.
10040087 Recursion for structure <structure-name> detected - Invalid IDL file
Explanation

A structure recursion occurred in the IDL file.
Action

Correct your IDL file and rerun the IDL Compiler.
10040088 Syntax error in %execute statement
Explanation

When parsing the template file, an illegal %execute statement was detected.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040089 Parameter <parameter name> has the wrong type in return statement
Explanation

When parsing the template file, a wrong parameter type was detected in the return declaration of the %execute statement.

Action

  1. For customer-written template files:
    Check the return declaration of the %execute statement and the parameter of the %return statement. The parameter types must match.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040090 Count of parameter is wrong in return statement
Explanation

When parsing the template file, the wrong number of parameters was detected in the return declaration of the %execute statement.

Action

  1. For customer-written template files:
    Check the return declaration of the %execute statement and the parameter of the %return statement. The count of parameters must match.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040091 Parser exception occurred in template file <template file name>
Explanation

When parsing the template file, a wrong statement or a syntax error has been detected by the template parser.

Action

  1. For customer-written template files:
    Correct your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040092 %UnsupportedProgram statement must be embedded in %program or %name loop
Explanation

%UnsupportedProgram statement needs a %library { %program { }} loop.

Action

  1. For customer-written template files:
    Create several smaller files from your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.

10040093 %UnsupportedProgram statement cannot be used if an output file is open
Explanation

%UnsupportedProgram must be used before an output file is opened.

Action

  1. For customer-written template files:
    Create several smaller files from your template file and rerun the IDL Compiler.

  2. For template files delivered by Software AG:
    Contact Software AG Support.