### ILIB Error Messages (OS/2, Windows)

LIB0001E
  Fatal: Invalid object object at offset offset Explanation: The object has an invalid record format. The error was detected at a location offset bytes from the beginning of the file. User Response: Recompile the object to make sure that it is built properly
LIB0002E
  Warning: Duplicate symbol symbol name ignored (library name) Explanation: The symbol already exists in the target library. User Response: Remove all but one of the modules defining the symbol from the library. This message is a warning and can be ignored.
LIB0004E
  Warning (module name): Unable to locate module Explanation: The library utility cannot delete or extract object module module name because it cannot find it in the library User Response: Ensure that the correct source library and object module name is specified.
LIB0006E
  General Failure! Explanation: The library utility had an unexpected non-fatal error during the last operation. The success or failure of the operation can be determined by other messages. User Response: If the other messages indicate that the operation failed, then recover the original library file from the backup file created. The backup file will exist on the same directory as the original library and have the same name, but with the extension "BAK".
LIB0007E
  Error: Unable to open file name. Explanation: The library utility cannot open file file name. User Response: Ensure that the file exists and is not being used by another process.
LIB0008E
  Error: Unable to read file name. Explanation: The library utility cannot read file file name. User Response: Check the system to ensure that the file can be read successfully. Ensure that it is a valid library or object file.
LIB0009E
  Error: Unable to write file name. Explanation: The library utility cannot write to file file name. User Response: Check the conditions below and take the appropriate corrective action:
  - The file has the read only attribute set Action: Clear the read only attribute on the file or use a different file name.
  - Attempted to write to a read only LAN drive Action: Get write access to the drive from the LAN administrator or use a different drive.
  - Attempted writing to a read only media Action: Choose a different media.
  - The file is being used by another process Action: Wait for the termination of the other process or cancel the other process using the file.
  - There is insufficient disk space Action: Free up space on the target disk or use a different target disk.
LIB0010E
  Error: Out of Memory! Abandoning any changes. Explanation: There was insufficient memory available on the system to complete the requests. User Response: Free up storage by terminating one or more current processes and retry the action.
LIB0011E
  Error: Out of space in the extended dictionary! Explanation: A limit of 128K maximum size for the extended dictionary was reached. User Response: Break the library into two or more smaller libraries. The library can be built without the extended dictionary however, this will slow down the link process.
LIB0017E
  Error: No more space in the dictionary. Split the library and retry. Explanation: The IBM library utility supports a maximum of 509 blocks for the dictionary. This limit has been reached. User Response: Break the library into two or more smaller libraries. This may also improve the library build time as well as the link time.
LIB0030E
  Fatal: Could not open backup file Explanation: The IBM library utility could not open the backup file. User Response: Check the conditions below and take the appropriate corrective action:
  - There is not enough space available on the drive. Action: Free up space on the target drive or use a different target drive.
  - The backup file already exists and is being used by another process. Action: Wait for the termination of the other process or cancel the other process using the file.
  - The backup file already exists and has the read only attribute set. Action: Clear the read only attribute on the target backup file.
LIB0033E
  Fatal: Could not open response file file name Explanation: The IBM library utility could not open the response file file name. User Response: Ensure that the file exists and is not being used by another process.
LIB0038E
  Fatal: Syntax error: Ctrl-Z is not allowed Explanation: An unexpected file termination character (Ctrl-Z) was found in the ILIB input. User Response: Remove any occurrence of Ctrl-Z from the ILIB input and try your command again. For information on ILIB input, see Managing Libraries.
LIB0040E
  Fatal: Syntax error: input is not allowed after '&' Explanation: Characters were found after the '&' character on the fixed format command line (i.e. on the same line). ILIB accepts the '&' character as a continuation character to allow ILIB input to span multiple lines. The '&' character must be the last character on the command line before the new line character. User Response: Remove any characters following the '&' character on the fixed format command line and try your command again.
LIB0046E
  Fatal: Unrecognized option option Explanation: The option specified is not valid for ILIB. User Response: Specify a valid option and try your command again. For information on valid ILIB options, see ILIB options.
LIB0047E
  Fatal: Syntax error: invalid operation Explanation: An invalid operation was specified on the fixed format command line. User Response: Specify a valid operation and try your command again.
LIB0048E
  Warning: New library specification ignored. Explanation: On the fixed format command line, a new library name was specified but will not be used. It is needed only if the first library specified already exists. If the first library specified does not exist, ILIB will create an output library with that name and ignore the new library specification. User Response: Try the command again. ILIB will use the second library specification as the new library specification, as the last command created the first library.
LIB0049E
  Fatal: Could not open list file list file Explanation: The library utility could not open the list file. User Response: Check the conditions below and take the appropriate corrective action:
  - There is not enough space available on the drive. Action: Free up space on the target drive or use a different target drive.
  - The list file already exists and is being used by another process. Action: Wait for the termination of the other process or cancel the other process using the file.
  - The list file already exists and has the read only attribute set. Action: Clear the read only attribute on the target list file.
LIB0050E
  Fatal: No library name was specified Explanation: Operations on library objects were requested (for example, /extract, /remove, etc.), but no input library was specified. User Response: Ensure that an input library is specified, and try the command again.
LIB0051E
  Fatal: Ctrl-C or Ctrl-Break was intercepted. Old library will be restored. Explanation: ILIB was interrupted at your request. The input library has been restored. User Response: Restart, if necessary.
LIB0052E
  Fatal: Unbalanced double quote detected Explanation: The ILIB input has an opening double quote, but no closing double quote. User Response: Add the missing double quote and try the command again.
LIB0053E
  Fatal: Could not open new library file library file Explanation: The library utility could not open the new library file. User Response: Check the conditions below and take the appropriate corrective action:
  - There is not enough space available on the drive. Action: Free up space on the target drive or use a different target drive.
  - The library file already exists and is being used by another process. Action: Wait for the termination of the other process or cancel the other process using the file.
  - The library file already exists and has the read only attribute set. Action: Clear the read only attribute on the target library file.
LIB0054E
  Fatal: The response file name file name is too long Explanation: The response file name is too long. The maximum length of the response file name is defined in the _MAX_PATH variable in stdlib.h. User Response: Change the response file name and try the command again.
LIB0055E
  Fatal: A comma or new line character is missing Explanation: ILIB was expecting a comma or new line character after the name of the list file on the fixed format command line. User Response: Add the missing comma or new line character and try the command again.
LIB0058E
  Fatal: The input line is too long. Explanation: A line in the response file is greater than 256 characters long. User Response: Split the line into 2 or more lines of 256 characters or less. ILIB accepts multiple lines in a response file. For details on response file format, see Managing Libraries.
LIB0084E
  Warning: Library library name does not contain IBM Browser information Explanation: The input library that you specified on the command line does not contain IBM Browser information. User Response: If you want IBM Browser information included in your output library, recreate the input library using the /BROWSE option.
LIB0086E
  Warning: Object object name with no public symbols can never be used Explanation: An object containing no public symbols was added to the library. User Response: Objects containing no public symbols can never be used and make the library bigger. Unless there is a reason to include the object in the library, it should be removed.
LIB0087E
  Warning: Unsupported option option ignored Explanation: The option specified is not supported by ILIB. User Response: Specify a valid option and try your command again. For a list of valid ILIB options, see ILIB options.
LIB0088E
  Error: DEF file keyword keyword ignored Explanation: The DEF file keyword specified is not supported by ILIB. User Response: Specify a valid keyword and try your command again. For a list of valid DEF file keywords, refer to ... link goes here.
LIB0090E
  Warning: No objects specified for output library Explanation: No objects were specified for the output library, so ILIB created an empty library. It is not useable. User Response: Check the command line and try your command again.
LIB0097E
  Fatal: Ambiguous option option ignored Explanation: A unique option name was not entered after the option indicator (/). User Response: Use the correct minimum option abbreviation and try your command again. For a list of valid ILIB options and their abbreviations, see ILIB options.
LIB0098E
  Warning: Option option can only be used with the free format command line. Ignored. Explanation: You specified an option that is only valid for the free format command line. Because you also specified the /NOFREEFORMAT option, ILIB will only allow you to enter options that are valid for the fixed format command line. User Response: There are two alternative actions that you can take:
  - Use the free format command line and try the command again, or
  - Try the command again using only options that are valid for the fixed format command line. For a list of options that are valid on the fixed format command line, refer to VisualAge for C++ User's Guide.
LIB0099E
  Warning: Unrecognized subsystem type type ignored Explanation: The value specified as argument for the /SUBSYSTEM option is not recognized. User Response: Specify a valid /SUBSYSTEM argument and try the command again. For information on /SUBSYSTEM arguments, refer to VisualAge for C++ User's Guide.
LIB0100E
  Error: Numeric value value out of range Explanation: The numeric argument for one of the ILIB options is out of range. User Response: Specify a valid numeric argument and try the command again. For information on valid ILIB options, see ILIB options.
LIB0101E
  Error: Numeric option option invalid Explanation: ILIB expected a numeric argument for option, but found alphabetic characters. User Response: Specify a numeric argument for option and try the command again.
LIB0102E
  Error: Can not suppress message msgnum Explanation: You tried to suppress an error message that is not a warning. User Response: Check that the message number was specified correctly.
  - If the message number was not specified correctly, then try the command again using the correct message number.
  - If the message number was entered correctly, then remove the suppress option. You can only suppress warning messages.
LIB0103E
  Warning: Plus ignored on command line Explanation: You used the plus (+) operator on the free format command line. The plus operator is valid only on the fixed format command line. User Response: Remove the plus character and try the command again.
LIB0104E
  Warning: Semi-colon ignored on command line Explanation: You used a semi-colon (;) on the free format command line. The semi-colon is valid only on the fixed format command line. User Response: Remove the semi-colon character and try the command again.
LIB0105E
  Warning: Option option ignored if not in the ilib environment variable or at the beginning of the command line Explanation: You specifed the option specifying command line format at a position other than first on the command line or first in the ilib environment variable. The option specifying command line format has a position restriction. It must be specified either immediately following ilib on the command line, or first in the ilib environment variable. User Response: Try the command again, while making sure to enter the command line format option in the appropriate place.
LIB0106E
  Fatal: Cannot nest response files Explanation: You named a second response file from within a response file. User Response: Edit the response file to remove the reference to the second response file. You can, however, specify multiple response files on the command line, making sure to precede the name of each one with the at sign (@) character.
LIB0107E
  Fatal: Unable to read response file file name Explanation: ILIB encountered a problem reading from the response file. User Response: This error usually means that the file is in an incorrect format. Check that you are specifying the correct file and that it is in the correct format.
LIB0108E
  Fatal: Unable to find file file name Explanation: ILIB is unable to find the specified input file. User Response: Check the conditions below and take the appropriate corrective action:
  - Check that the file name was specified correctly. Action: Correct the spelling of the file name, if it was not specified correctly.
  - Check that the path information was specified correctly. Action: Correct the path information, if it was not specified correctly.
LIB0109E
  Fatal: File file name is of unknown type Explanation: ILIB tries to identify the file type of any input files by examining the file contents. ILIB was not able to recognize the type of the specified file. User Response: Make sure that all the files given as input to ILIB are valid input types. ILIB accepts LIB, OBJ, DLL, and DEF files as input. If the input file is a valid type, check that the file has not been corrupted.
LIB0110E
  Fatal: Invalid library library name Explanation: The library specified as input is not valid. User Response: The library may not have been specified properly or may be corrupted.
  - If the input library was not specified correctly on the command line, update the command line and try the command again.
  - If the input library is corrupted, use ILIB to recreate it.
LIB0111E
  Fatal: Error parsing string string Explanation: ILIB encountered an error while parsing string. User Response: Correct string and try the command again.
LIB0112E
  Fatal: Line line number in DEF file too long Explanation: ILIB encountered a line in the DEF file that is greater than 65535 characters long. User Response: Correct the line in the DEF file and try the command again.
LIB0113E
  Warning: Module name truncated to module name Explanation: The module name specified in the DEF file is too long and was truncated to module name. User Response: Correct the module name in the DEF file and try the command again.
LIB0116E
  Fatal: Missing or bad include file name Explanation: The include file specified in the DEF file was not found. User Response: Check that the include file exists and was specified correctly.
LIB0117E
  Fatal: Syntax error in DEF file, line line number. Explanation: ILIB encountered a syntax error in the specified moduled definition (DEF) file. User Response:
  - Correct the syntax error and try your command again, or
  - Allow cppfilt or ILIB to generate the DEF file for you.
LIB0118E
  Fatal : DEF file must contain LIBRARY keyword Explanation: The input module definition (DEF) file does not contain the LIBRARY keyword. User Response: The LIBRARY keyword is required. Update your DEF file to include the LIBRARY statement and try the command again.
LIB0119E
  Warning: DEF file keyword keyword ignored Explanation: ILIB does not support the specified keyword. User Response: Remove the keyword from the DEF file and try the command again.
LIB0120E
  Warning: OMF object(s) put in COFF library. This will not work with all linkers and library managers. Please see documentation for details. Explanation: A COFF library was created that contains OMF objects. User Response: Make sure that your linker supports a COFF library that contains OMF objects. If not, create separate OMF and COFF libraries.
LIB0121E
  Fatal: Could not open DEF file Explanation: The DEF file specified was not found. User Response: Check that the DEF file exists and was specified correctly.
LIB0122E
  Error: Could not erase temporary file file name Explanation: ILIB was not able to erase the specified temporary file. User Response: Check the conditions below and take the appropriate corrective action:
  - The temporary file is being used by another process. Action: Wait for the termination of the other process or cancel the other process using the file and then erase the file.
  - The temporary file has the read only attribute set. Action: Clear the read only attribute on the temporary file and erase the file.
LIB0123E
  Fatal: Unable to close file name Explanation: ILIB was not able to close the file file name. User Response: Try the command again.
LIB0124E
  Warning: DLL DLL name exports no symbols by name Explanation: The DLL DLL name exports no symbols by name, only by ordinals. User Response: Make sure that you don't try to access the DLL with GetProcAddr by name, only by ordinal.
LIB0125E
  Fatal: Zero ordinal ignored in file name, line line number Explanation: The module definition (DEF) file contains a zero ordinal for a symbol. User Response: Remove the zero ordinal or assign a different ordinal.
LIB0126E
  Warning: Invalid symbol symbol ignored in DEF file, line line number Explanation: ILIB encountered an invalid symbol in the DEF file. User Response:
  - Remove the invalid symbol and try your command again, or
  - Allow CPPFILT or ILIB to generate the DEF file for you.
LIB0127E
  Fatal: Nothing to do Explanation: No action was requested from ILIB by the user. User Response: Check to see that you entered the ilib command correctly.
LIB0128E
  Fatal: file name is not an object file -- unable to add to library Explanation: ILIB was unable to add file name to the library, as it is not a valid object file. User Response: Check to see that the object file was specified correctly and try the command again.
LIB0129E
  Warning: Library library name is being created with an empty dictionary Explanation: ILIB created an empty library, or a library with objects that define no symbols. User Response: Check that the ilib command and objects were specified correctly and try the command again.
LIB0130E
  Warning: Unable to use demangler DLL. Explanation: ILIB was unable to access/use the demangler dynamic link library (demangli.dll). User Response: Make sure that the demangler DLL is available and the appropriate version. If the error persists, please call IBM.
LIB0131E
  Warning: Module redefinition ignored module name Explanation: You requested that module name be added to the output library twice. The second definition is ignored. User Response: Remove the second definition and try the command again.
LIB0132E
  Warning: Library redefinition ignored library name Explanation: You requested that library name be added to the output library twice. The second definition is ignored. User Response: Remove the second definition and try the command again.
LIB0133E
  Fatal: Duplicate ordinal ordinal for symbol symbol ignored in DEF file Explanation: You specified two ordinals for the same symbol in the module definition (DEF) file. The second definition is ignored. User Response: Remove the second definition of the symbol and try the command again.
LIB0135E
  Warning: Library must be specified before operation, operation ignored Explanation: The input library must be specified on the command line before any operations. User Response: Correct the order of parameters on the command line and try the command again.
LIB0136E
  Warning: File name truncated to filename1 Explanation: The filename was too long for the operating system to handle and had to be truncated. User Response: Use a shorter name.