### Fatal Error Messages 1050 - 1099

LNK1050
  too many groups in one module
  Explanation: ILINK found more than 32 group definitions (GRPDEF) in a single module.
  Action: Reduce the number of group definitions by splitting the module, by eliminating one or more group definitions, or combining group definitions.
LNK1051
  too many groups
  Explanation: The program defines more than 32 groups in addition to DGROUP.
  Action: Reduce the number of group definitions by splitting the module, by eliminating one or more group definitions, or combining group definitions.
LNK1052
  specified base value too high
  Explanation: The value you specified for the /BASE option is too high (greater than 0X80000000).
  Action: Reduce the /BASE value.
LNK1053
  out of memory for symbol table
  Explanation: The program has more symbolic information, such as public, external, segment, group, class, and file names, than the amount that could fit in available real memory.
  Action: Combine modules or segments and recreate the object files. Eliminate as many public symbols as possible or use shorter names.
LNK1054
  requested segment limit too high
  Explanation: There is not enough memory to allocate the necessary tables for the amount of segments requested.
  Action: Reduce the number of segments by combining or creating additional executable modules.
LNK1057
  data record too large
  Explanation: An LEDATA record (in an object module) contained more than 1024 bytes of data. This is a translator (compiler or assembler) error.
  Action: Note which translator (compiler or assembler) produced the incorrect object module and the circumstances, and contact your supplier.
LNK1063
  out of memory for debugging information
  Explanation: ILINK was given too many object files with debug information, and ran out of space to store them.
  Action: Reduce the number of object files that have debug information.
LNK1064
  out of memory - name heap exhausted
  Explanation: The linker ran out of heap space; name = near or far.
  Action: Reduce the number of background processes or install more memory.
LNK1065
  IBM vendor extension type number1 not supported
  Explanation: The linker attempted to process an object that contains an unsupported IBM vendor extension type record number1.
  Action: Recompile the object with a compiler that does not generate the extension type.
LNK1066
  Vendor extension number number1 not supported
  Explanation: The linker attempted to process an object that contains a vendor extension record number1 with a vender number that does not identify IBM.
  Action: Recompile the source for the object with an IBM compiler.
LNK1070
  name: segment size exceeds 64K
  Explanation: A single segment contains more than 64K of code or data. This could be because you attempted to combine identically named segments.
  Action: Try compiling (or assembling) and linking using a larger memory model or breaking up the named segment.
LNK1071
  segment _TEXT larger than 65,520 bytes
  Explanation: This error is likely to occur only in small-model C programs, but it can occur when any program with a segment named _TEXT is linked using the /DOSSEG option of the ILINK command. Small-model C programs must reserve code addresses 0 and 1; the reserve is increased to 16 for alignment purposes.
  Action: Make the program source code smaller, or change to a larger memory model.
LNK1072
  image size is larger than the maximum
  Explanation: The resulting executable is bigger than the specified maximum. This maximum could be set in the memory map file.
  Action: Make the program source code smaller, or increase the image size limit in the memory map file.
LNK1073
  file-segment limit exceeded
  Explanation: There are more than 255 physical or file segments.
  Action: Reduce the number of physical or file segments. You could use the Combine Contiguous Data (/PACKD[ATA]) option for combining data segments or the Combine Contiguous Code (/PACKC[ODE]) option for combining code segments.
LNK1074
  name: group larger than 64K
  Explanation: A group contains segments that total more than 65,536 bytes.
  Action: Reduce the number or size of segments or remove segments from the group.
LNK1075
  entry table larger than 65,535 bytes
  Explanation: You have exceeded a linker table size limit because of an excessive number of entry names.
  Action: Reduce the number of names in the modules that you are linking or create additional executable modules.
LNK1076
  name: segment size exceeds numberM
  Explanation: The named segment is larger than the specified size.
  Action: Break the segment into smaller segments and try again.
LNK1077
  common area longer than 4G-1 bytes
  Explanation: The space for the C languages common area is too big.
  Action: If the load module is an executable, consider putting some routines in .DLL; otherwise, link without debugging information or create additional executable modules.
LNK1078
  exported name name1 exceeds 255 characters, truncating to: name2
  Explanation: Due to OS/2 system limitations, exported names cannot be longer than 255 characters.
  Action: Reduce the length of the name by choosing shorter names for member functions and classes.
LNK1079
  imported name name1 exceeds 255 characters, truncating to: name2
  Explanation: Due to OS/2 system limitations, exported names cannot be longer than 255 characters.
  Action: Reduce the length of the name by choosing shorter names for member functions and classes.
LNK1080
  External or public name is longer than 64000 characters
  Explanation: An EXTDEF or PUBDEF record contains a name greater than 64000 characters long.
  Action: Reduce the length of the name by choosing shorter names for member functions and classes.
LNK1081
  out of space for run file
  Explanation: The disk on which the executable file is being written is full.
  Action: Delete or move files to make space and restart ILINK.
LNK1082
  name: stub file not found
  Explanation: The stub file specified in the module definition file could not be found.
  Action: Check that the correct path to the stub file has been specified.
LNK1084
  an access violation occurred opening the named file
  Explanation: Possible problems are: the name refers to a directory rather than a file,
  or you do not have read access to the file, or the file is in use by another process.
  Action:Make sure the name and permissions are correct, and make sure the file is not being used by another process.
LNK1085
  out of file handles opening file
  Explanation: There are no more file handles available to the linker.
  Action: Reduce the number of file handles. Try combining object files into a library file, and then linking to the library file.
LNK1088
  error reading file
  Explanation:ILINK could not read from the specified file.
  Action: If an object file is corrupted, recompile it. Check that the I/O devices are working properly.
LNK1089
  filename: cannot open response file
  Explanation: ILINK cannot find the specified response file. This usually indicates a typing error.
  Action: Include the drive specifier or path, or both, for the response file.
LNK1090
  filename: cannot read response file
  Explanation: ILINK cannot read the specified response file. This usually indicates a file in the wrong format.
  Action: Make sure you are specifying the correct file. Make sure the file is in the correct format. Retry when ready.
LNK1091
  unexpected end-of-file on library
  Explanation: The disk containing the library has probably been removed or is corrupted.
  Action: Replace the disk containing the library and restart ILINK.
LNK1092
  cannot open module definition file
  Explanation: The specified module definition file cannot be opened, or an invalid file name was specified.
  Action: Check that the specified file name is correct. Include the drive specifier or path, or both, for the module definition file.
LNK1093
  could not open file
  Explanation: ILINK could not open the file you specified.
  Action: Make sure the file is in the correct format. If it is an object file, make sure it was compiled correctly by the current version of the compiler.
LNK1094
  could not find file
  Explanation: ILINK could not find the file you specified.
  Action: Specify full path name or directory in which object module resides.
LNK1096
  unexpected end-of-file
  Explanation: ILINK encountered an end-of-file character while reading an input file AND expected more information.
  Action: Check input files for errors and relink.
LNK1097
  I/O error - string
  Explanation: The linker encountered the I/O error shown while reading from a file.
  Action: Make sure the file is not corrupted or on a bad disk sector and relink.
LNK1098
  cannot open include file filename - reason
  Explanation: ILINK could not open the include file for the stated reason.
  Action: Correct the problem and restart ILINK.
LNK1099
  error creating .exp file
  Explanation: An .exp file used to build a DLL could not be created. This could happen if ILIB could not be invoked.
  Action: Check if ILIB is on the path. Make sure you have enough available
  disk space, including in the TEMP area.

Linker Error Messages