R1001
Explanation: Resource Compiler was unable to open the given file.
Recovery: Check the format of the file. The same file might be in use by another process.
Explanation: Resource Compiler was unable to locate the given file.
Recovery: Check the spelling of the file name and its path, and be sure that the file exists.
Explanation: Resource Compiler was unable to read or write the given file.
Recovery: Check the spelling of the file name and its path. If the file exists, confirm that its format is correct.
Explanation: You did not name an input file on the command line.
Recovery: Correct the syntax of your command line.
Explanation: You did not name an output file on the command line, in a context which required an output file name.
Recovery: Correct the syntax of your command line.
Explanation: Resource Compiler detected an error when examining your system's double-byte character set environment vector.
Recovery: Correct your system's double-byte character set environment.
Explanation: You specified extra file operands following the output file name on your command line.
Recovery: Correct the syntax of your command line.
Explanation: On the command line, your input and output file names were identical.
Recovery: Give a different name for the output file.
Explanation: The compiler was unable to complete the compile process.
Recovery: Correct the errors noted on your display.
Explanation: File filename did not contain certain data that Resource Compiler needed.
Recovery: Correct the contents of the file.
Explanation: Resource Compiler detected an incorrect data state.
Recovery: Follow your local problem reporting procedures to notify IBM of the error.
Explanation: Resource Compiler could not continue the compile process.
Recovery: Correct the file according to the error messages printed.
Explanation: Resource Compiler detected an incorrect internal state.
Recovery: Follow your local problem reporting procedures to notify IBM of the error.
Explanation: You requested that Resource Compiler bind resources to an executable file, but the file could not be loaded.
Recovery: Use a loadable executable file for binding resources.
Explanation: A request for system memory could not be satisfied.
Recovery: Your system's swapper file might not have enough disk space to grow to a necessary size. Clear some space on the device containing your swapper file.
Explanation: Tried an operation that use more than the available memory.
Recovery: Stop some programs to give more memory.
Explanation: Resource Compiler attempted a file I/O operation which was unsuccessful.
Recovery: Check the spelling of the file name and its path, and be sure that the file exists. Be sure that other processes have released the file for operations by the Resource Compiler.
Explanation: Resource Compiler attempted a file I/O operation which was unsuccessful.
Recovery: Check the spelling of the file name and its path, and be sure that the file exists. Be sure that other processes have released the file for operations by the Resource Compiler.
Explanation: Resource Compiler attempted a file I/O operation which was unsuccessful.
Recovery: Check the spelling of the file name and its path, and be sure that the file exists. Be sure that other processes have released the file for operations by the Resource Compiler.
Explanation: Resource Compiler attempted a file I/O operation which was unsuccessful.
Recovery: Check the spelling of the file name and its path, and be sure that the file exists. Be sure that other processes have released the file for operations by the Resource Compiler.
Explanation: Resource Compiler attempted to read an empty file.
Recovery: Confirm that your input files have the proper data format.
Explanation: The code page specified does not exist.
Recovery: Specify an existing code page.