HP NonStop SQL/MX Messages Manual page 123

SQL/MX MXCMP Messages (2000 through 2999)
Effect. The operation fails.
Recovery. Verify that application pathname exists and is readable by the user.
Verify that application pathname is spelled correctly, and retry the command.
SQL 2204
2204 SQL compilation of module name failed.
Where module name is the name of the module.
Cause. You invoked mxCompileUserModule on an application file that has embedded
module definition(s). The SQL compilation of the named embedded module definition
produced an MXCMP warning or error.
Effect. The operation fails.
Recovery. Review the MXCMP warning or error. Trace the diagnostic back to the
source file of the named module. Correct offending source statements. Retry
preprocessing, translating, compiling, and SQL compiling the application file.
SQL 2205
2205 A temporary filename could not be created.
Cause. You invoked mxCompileUserModule on an application file that has many
embedded module definitions. The tool cannot create another temporary file name to
hold the contents of an embedded module definition. The tool used tmpnam() to create
a string that is not the name of an existing file which tmpnam() could not do.
Effect. The operation fails.
Recovery. Clean up TMPDIR (the directory where temporary files are created) by
deleting unused temporary files. Retry the command.
SQL 2206
2206 Temporary file temp filename could not be created.
Where temp filename is the name of the temporary file.
Cause. You invoked mxCompileUserModule on an application file that has many
embedded module definitions.The tool cannot create another temporary file to hold the
contents of an embedded module definition.
Effect. The operation fails.
Recovery. Verify that you have write access to TMPDIR (the directory where
temporary files are created) and that TMPDIR has free space. Delete unused
temporary files from TMPDIR and retry the command.
HP NonStop SQL/MX Messages Manual—640324-001
4- 27