Restriction:This topic applies to Windows environments only.
XU001: No more RAM memory available to application. Insufficient memory (RAM) was available to execute a command sent to the SQL Engine. Try running the application from outside
the main or application menu to see if that gives you enough memory to continue. If you have other memory resident programs
loaded, remove them and try again. Load network drivers into high memory or remove them. Reduce DOS memory consumption by
using fewer FILES= and fewer BUFFERS= in CONFIG.SYS.
XU004: Filename name is too long. The filename you have entered exceeded the maximum length. Filenames must be 8 characters or fewer. Enter a shorter filename.
XU005: File name not found. Cannot find the file specified. Check to make sure that the correct directory is being used, and that the specified file exists
there.
XU006: Error opening file name. error-descr. The system could not open the file named due to the specific operating system error. See your operating system manual for
the error described and make any necessary corrections.
XU007: Error reading file name. error-descr. The system could not read from the file named due to the specified operating system error. See your operating system manual
for the error described and make any necessary corrections.
XU008: Error writing file name. error-descr. The system could not write to the file named due to the specified operating system error. See your operating system manual
for the error described and make any necessary corrections.
XU009: Error closing file name. error-descr. The system could not close the file named due to the specified operating system error. See your operating system manual for
the error described and make any necessary corrections.
XU010: Error deleting file name. error-descr. The system could not delete the file named due to the specified operating system error. See your operating system manual for
the error described and make any necessary corrections.
XU011: Error seeking file name. error-descr. The system could not seek the file named due to the specified operating system error. See your operating system manual for
the error described and make any necessary corrections.
XU014: Incorrect file version in file name. The file specified is not the current version. If it is a help file or error file, you must recompile the file using the current
version of the help compiler, XDBHELPC. If the file is a message file, you must recompile it using the message compiler, XDBMSGC.
XU015: Corrupted file format in file name. The file specified could not be entirely read. Check to see if it is the correct file. You may consider trying a backup file
name.
XU020: Maximum of 3 unsuccessful attempts to login. You have attempted to log on to a XDB Server using an invalid user ID and/or password three consecutive times, so XDB Server
will automatically exit the client application.
XU021: More than 15 errors... The active program has issued more error messages than this dialog box can display. Only the first 15 are shown.
XU022: Invalid server name. The string of characters you have entered does not constitute a valid server name. For example, the string contains an illegal
character (such as a space) or is too long.
XU023: Invalid location name. The string of characters you have entered does not constitute a valid location name. For example, the string contains an illegal
character (such as a space) or is too long.
XU031: Object name is not an alias. The alias requested by an internal operation is not defined as an alias in the SYSIBM.SYSTABLES. This usually indicates an
inconsistency in your catalog tables.
XU032: Error Querying SYSTABLES An internal operation encountered an error while attempting to get alias information from SYSTABLES.