SQL/MX 2.x Messages Manual (H06.10+, J06.03+)

SQL/MX MXCMP Messages (2000 through 2999)
HP NonStop SQL/MX Messages Manual—544518-011
4-32
Effect. The operation fails.
Recovery. Verify the spelling of the module name and retry the command.
SQL 2223
Where file name is the name of the application file.
Cause. You invoked mxCompileUserModule on the named application file, which does
not exist or is not readable.
Effect. The operation fails.
Recovery. Verify the spelling of the application file name and retry the command.
SQL 2233
Where nodename is the name of the node such as
\system.$data_volume.$data_subvolume on which the failure occurred.
Where error-num is the file system error number.
Cause. The nodename you specified is not available.
Effect. The compiler tried to produce a plan without using that node. This might result
in a suboptimal plan.
Recovery. See the Guardian Procedures Errors and Messages to diagnose and
correct the problem.
SQL 2900
Where number is the line number.
Cause. An error occurred in file name at line number.
Effect. Compilation failed because of a syntax error.
Recovery. This is a general error that is issued before a more specific error. Use the
error that follows this one to diagnose and correct the problem.
2223 Application file file name does not exist or is not
readable.
2233 Query involves remote node nodename that is currently
down. Compiler encountered a file system error error-num. It
may produce a plan that is suboptimal or of incompatible
version.
2900 in file file name at line number.