Description:
MOD-00001 unable to open file string
Cause:
SQL*Module was unable to open a temporary file for internal use. There might be insufficient disk space, too many files, or read-only protection on the output directory.
Description:
MOD-00002 invalid syntax at column number in line number of file string
Cause:
There is a syntax error in the SQL statement or the statement is not properly terminated in the module file.
Description:
MOD-00003 invalid SQL Identifier at column number in line number of file string
Cause:
The symbol in a SQL descriptor is invalid.
Description:
MOD-00004 unsupported datatype in line number of file string
Cause:
A host variable defined in the procedure definition of the module file has an unsupported datatype or has a scale or precision outside the supported range.
Description:
MOD-00005 invalid include file name at column number in line number of file string
Cause:
A host variable used in SQL statement was not defined in the procedure definition or has an unsupported datatype.
Description:
MOD-00007 unable to open a cursor at line number in file string
Cause:
The syntax in the SQL statement is faulty. The module compiler was expecting a host variable, but found something else.
Description:
MOD-00008 unable to open include file “string” at line number in file string
Cause:
SQL*Module is not able to open the input file that was specified with the INAME option. This error can result from any of the following:
Action: Check that the appropriate permission to read the file has been granted. Check that the name and directory hierarchy have been specified correctly. Rerun the compiler.
Description:
MOD-00011 unable to open output file “string“
Cause:
SQL*Module is not able to create an output file, such as the specification file or the output code file. This usually happens when write permissions on the current directory or on the directory specified for the ONAME or SNAME options do not exist. It can also happen if the name or directory path is not legal or a directory on the path does not exist.
Description:
MOD-00012 unable to parse statement at line number in file string
Cause:
This is caused by a syntax error in the Module Language file. For example, if the SQL statement
SELECT ename INTO :name FORM emp WHERE ...
is in a module procedure, this message is raised. This message is not triggered by semantic errors. See MOD-00075.
Description:
MOD-00013 expected “string“, but found “string” at line number in file string
Cause:
The syntax in a SQL statement is faulty. The module compiler found an unexpected or illegal token.