R2002

RC expected at least one argument for option.

Explanation: You coded command-line option option without argument.

Recovery: Supply the required argument for the option.

This input is incorrect:

Explanation: The given text is incorrect.

Recovery: Correct the syntax of the statement.

RC encountered an incorrect character in the source file.

Explanation: The input file had a character which was incorrect in context.

Recovery: Remove the incorrect character from the file.

You defined too many macros from the command line.

Explanation: You specified more than eight macro definitions on the command line.

Recovery: Supply extra macro definitions as #define statements within an input file.

You specified the incorrect code page value value.

Explanation: You coded command-line option -cp or -k or environment variable DBCS but gave an incorrect value for the code page.

Recovery: Use a value from the table of code pages and country codes in "COUNTRYCODE" in the OS/2 Warp Control Program Programming Guide and Reference.

You specified no code page value.

Explanation: You coded command-line option -cp or -k or environment variable DBCS but gave no value for the code page.

Recovery: Use a value from the table of code pages and country codes in "COUNTRYCODE" in the OS/2 Warp Control Program Programming Guide and Reference.

The resource identifiers have too many long strings.

Explanation: Your resource data contained more than 64K bytes of strings used as resource identifiers. The resources could not be bound to the executable file.

Recovery: Use fewer characters in the string identifiers of your resource file.

RC cannot delete old resources within instance pages.

Explanation: The input executable file contained original resources inside instance pages.

Recovery: Do not link resources into the executable file prior to running Resource Compiler.

The resources have too many objects.

Explanation: The input executable file contained an incorrect format.

Recovery: Correct the object table of the input file.

The page table has too many entries.

Explanation: The input executable file contained too many pages.

Recovery: Correct the page table of the input file.

The executable file has too many fixups.

Explanation: The input executable file contained too many fixups.

Recovery: Correct the fixup page table of the input file.

RC cannot write a resident Format Directive.

Explanation: The input executable file contained resident format directives which the compiler could not rewrite during the binding operation.

Recovery: Correct the format directives table of the input file.

RC cannot read the OS/2 segment table in file filename.

Explanation: The input executable file was not in the correct format.

Recovery: Correct the segment table of the input file.

RC cannot delete temporary file filename.

Explanation: The temporary executable file could not be deleted.

Recovery: Be sure that you have specified a value for the TMP or TEMP environment variable.

RC cannot write extended attributes for filename.

Explanation: Resource Compiler was unable to write extended attributes to the output executable file.

Recovery: Be sure that no other process is using the executable file.

The default icon exceeds 64K.

Explanation: The input executable file contained a default icon in excess of 64K in size.

Recovery: Use a default icon smaller than 64K.

The association table exceeds 64K.

Explanation: The input executable file contained an association table in excess of 64K in size.

Recovery: Use an association table smaller than 64K.

You must specify an executable file name.

Explanation: You did not specify the name of an executable file to which to bind resources.

Recovery: Specify the name of an executable file.

You must specify a resource or script file name.

Explanation: You did not specify the name of an input file.

Recovery: Specify the name of an input file.

RC encountered an error while binding resources to executable file filename.

Explanation: During the binding step, Resource Compiler found errors described in other messages.

Recovery: Follow the recovery steps given for the accompanying messages.

RC encountered an error while reading the resource file.

Explanation: Resource Compiler had an I/O error on the binary resource file.

Recovery: Confirm the spelling of the file name and path, and be sure that no other process is using a file of that name.

RC encountered an error while writing the resource file.

Explanation: Resource Compiler had an I/O error on the binary resource file.

Recovery: Confirm the spelling of the file name and path, and be sure that no other process is using a file of that name.

You must specified a resource and a script file name.

Explanation: Resource Compiler could not determine the names of the input script file and the output binary file.

Recovery: Give names for both of these files on the command line.

The executable file has an unknown format.

Explanation: You tried to bind resources to an executable file in an unknown format.

Recovery: Use an executable file in either the NE (16-bit) or LX (32-bit) linear executable format.

You specified the duplicate operand, which already exist in the group.

Explanation: You used a command line operand more than once.

Recovery: Remove the extra operand specification.

RC cannot create resource item type 'type' and id 'number'.

Explanation: One of your resource statements specified an incorrect combination of resource type and resource ID.

Recovery: Do not duplicate resource IDs of the same type.

RC cannot create resource item type 'type' and id 'string'.

Explanation: One of your resource statements specified an incorrect combination of resource type and resource ID.

Recovery: Do not duplicate resource IDs of the same type.

This resource name is too long (limit 512):

Explanation: You coded the given name as a resource id, but its length exceeds the legal limit.

Recovery: Use a resource name shorter than 512 characters.

RC failed to add a resource. The return code is nnnnn.

Explanation: An error occurred while creating a resource.

Recovery: Refer to the OS/2 return code nnnnn for more information.

The script file has an incorrect integer or hex or octal literal.

Explanation: You provided a numeric literal in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the literal.

The script file has an incorrect floating point literal.

Explanation: You provided a numeric literal in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the literal.

The script file has an incorrect floating point value.

Explanation: You provided a numeric literal in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the literal.

The script file has an integer literal too large for its type.

Explanation: You provided a numeric literal in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the literal.

You specified a character literal with more than one byte.

Explanation: You provided a character literal in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the literal.

You specified an empty character literal.

Explanation: You provided a character literal in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the literal.

The script file has a Hex or Octal escape sequence out of range.

Explanation: You provided an escape sequence in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the sequence.

A Hex escape sequence contained no hex digits.

Explanation: You provided an escape sequence in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the sequence.

You specified an incorrect escape sequence.

Explanation: You provided an escape sequence in an incorrect format, or with a value out of the legal range.

Recovery: Correct the format or value of the sequence.

The given directive requires a valid macro name.

Explanation: You specified preprocessor directive on which the expected macro name was missing or incorrect.

Recovery: Correct the macro name on the directive.

You specified an incorrect expression specified on a conditional directive.

Explanation: You specified an incorrect expression on an #if or #elif preprocessor directive.

Recovery: Correct the syntax of the expression.

The expression on a conditional directive results in division by zero.

Explanation: You specified an incorrect expression on an #if or #elif preprocessor directive.

Recovery: Correct the syntax of the expression.

#elif or #else or #endif appeared in an incorrect context.

Explanation: You specified an #elif or #else or #endif preprocessor directive without a preceding #if or #ifdef or #ifndef preprocessor directive.

Recovery: Correct the logic of the preprocessor conditional blocks.

The preprocessor expected #endif but the input stream ended with open scope.

Explanation: You specified #if or #elif or #ifdef or #ifndef preprocessor directive without a concluding #endif preprocessor directive.

Recovery: Correct the logic of the preprocessor conditional blocks.

You did not complete a #define parameter list before the end of the source line.

Explanation: You specified a function-type macro definition in a #define preprocessor directive but did not end the parameter list with a closing parenthesis.

Recovery: Correct the syntax of the macro definition.

You specified an incorrect #define parameter list.

Explanation: You specified a function-type macro definition in a #define preprocessor directive but did not end the parameter list with a closing parenthesis.

Recovery: Correct the syntax of the macro definition.

#define parameter list has a duplicate parameter.

Explanation: You repeated a parameter when specifying a function-type macro.

Recovery: Correct the syntax of the macro definition.

You invoked a macro with incorrect arguments.

Explanation: You specified incorrect arguments to a macro with a function-type definition.

Recovery: Correct the syntax of the macro reference.

You did not complete a directive before the end of the source line.

Explanation: You specified a preprocessor directive but did not complete it on the same line.

Recovery: Write the entire directive on the same line.

You did not end a character or string or #include literal before the end of the line.

Explanation: You specified a string or literal token which did not end before the line ended.

Recovery: Write the entire token on the same line.

An rcinclude statement must have a filename to include.

Explanation: You specified an RCINCLUDE statement but omitted the file name.

Recovery: Code the name of the file on the RCINCLUDE statement.

A statement has an incorrect expression.

Explanation: You specified an statement with an incorrect arithmetic expression.

Recovery: Correct the syntax of the expression.

The stringizing operator(#) appeared on a function-like macro.

Explanation: You specified a stringizing operator on a function-like macro.

Recovery: Refer to C Language Reference for the rules governing the stringizing operator.

You specified the Concatenation operator (##) incorrectly.

Explanation: You specified a concatenation operator in an incorrect context.

Recovery: Refer to C Language Reference for the rules governing the concatenation operator.

The script file has an incorrect wide character or wide string literal.

Explanation: You specified a wide character or wide string literal in an incorrect format.

Recovery: Refer to C Language Reference for the rules governing wide characters and wide strings.

A literal has an incorrect multibyte character.

Explanation: You specified a literal containing an incorrect multibyte character.

Recovery: Use only characters from your multibyte character set in multibyte literal constants.

You used a wide character string on an #include.

Explanation: You specified an #include preprocessor directive containing a wide character string. This usage is prohibited.

Recovery: Correct the syntax of the directive.

A predefined macro can not be defined again.

Explanation: You used a #define or #undef preprocessor directive to redefine a predefined macro. These macro names cannot be changed using directives.

Recovery: For control over the values of macros, use macro names which are not reserved for special use by the preprocessor.

A predefined macro can not be undefined.

Explanation: You used a #define or #undef preprocessor directive to undefine a predefined macro. These macro names cannot be changed using directives.

Recovery: For control over the values of macros, use macro names which are not reserved for special use by the preprocessor.

The filename to be searched contained only whitespace.

Explanation: You used an #include preprocessor directive to process a file which had no tokens.

Recovery: Eliminate the reference to the file, or supply the correct information inside it.

The file cannot be searched because of missing include options.

Explanation: You asked for a file to be included on an #include directive and wrote the file name without a path name inside angle brackets, and gave no path search specifications with the -I option. With no search criteria, the preprocessor will be unable to locate the file.

Recovery: Specify search paths to the file by using the -I option.

You redefined a macro name with different replacement text.

Explanation: You defined a macro, then redefined it to a different value.

Recovery: To change the value of a macro, first undefine it and then use another #define directive.

An unexpected newline appeared within quotes.

Explanation: You defined a string spanning more than one line, when this usage is not permitted.

Recovery: Remove the newline from the string.

A Hex escape must be followed by 2 or 4 hex digits.

Explanation: You used a hexadecimal escape sequence in the wrong format.

Recovery: Only one-byte and two-byte characters are recognized as hex escapes. For example, use the form \x00 for a single-byte zero or \x0000 for a double-byte zero.

A resource_Item has incorrect Window Data.

Explanation: Resource Compiler encountered incorrect binary data while examining the child windows of a resource.

Recovery: The message appears together with other messages describing the particular errors of the child window. Follow the recovery instructions of the accompanying messages.

You specified a non-numeric button item style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric combo box style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric control style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric entry field style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric frame style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric list box style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric static style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric window style.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric control id.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric resource id.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified a non-numeric frame control flag.

Explanation: You coded a field using a string token.

Recovery: Replace the string by a defined numeric constant or expression.

You specified an incorrect window class.

Explanation: You coded a window class field using an unknown string or number.

Recovery: Use a correct value for the window class.

You specified an incorrect code page.

Explanation: You coded a code page field using an unknown number.

Recovery: Use a value from the table of code pages and country codes in "COUNTRYCODE" in the OS/2 Warp Control Program Programming Guide and Reference.

RC is using code page codepage.

Explanation: You coded a code page field that is not defined. The compiler chose codepage as the code page value.

Recovery: Use a value from the table of code pages and country codes in "COUNTRYCODE" in the OS/2 Warp Control Program Programming Guide and Reference.

You specified an incorrect memory or load option.

Explanation: You used an incorrect memory or load option.

Recovery: Valid memory options are FIXED, MOVEABLE, and DISCARDABLE. Valid load options are PRELOAD and LOADONCALL.

You specified a non-numeric menu item style.

Explanation: You used an incorrect menu item style.

Recovery: Use a style as documented under MENUITEM Statement.

The value of the height must be from 0 to 65535.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

You specified a non-numeric height.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

The value of width must be from 0 to 65535.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

You specified a non-numeric width.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

The value of X Coordinate must be from -32768 to 32767.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

You specified a non-numeric X Coordinate.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

The value of Y Coordinate must be from -32768 to 32767.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

You specified a non-numeric Y Coordinate.

Explanation: You used an incorrect token in a numeric field.

Recovery: Confirm that each macro you used has a definition. You might have omitted a field from a list of parameters separated by commas.

A left parenthesis is incorrect or missing.

Explanation: You used a numeric expression which lacked balanced parentheses.

Recovery: Correct the parentheses in the expression.

The value of a custom-resource type must be from 1 to 65535.

Explanation: A RESOURCE statement contained a type field which evaluated to a number outside the legal range.

Recovery: Use a value from 1 to 65535 as a resource type.

You specified an incorrect Assocname in ASSOCTABLE.

Explanation: An ASSOCTABLE statement contained an incorrect field as indicated.

Recovery: Use a legal value for the field. The syntax rules appear under ASSOCTABLE Statement.

You specified an incorrect File-match-string in ASSOCTABLE.

Explanation: An ASSOCTABLE statement contained an incorrect field as indicated.

Recovery: Use a legal value for the field. The syntax rules appear under ASSOCTABLE Statement.

You specified an incorrect ea-flag in ASSOCTABLE.

Explanation: An ASSOCTABLE statement contained an incorrect field as indicated.

Recovery: Use a legal value for the field. The syntax rules appear under ASSOCTABLE Statement.

An iconfile parameter is missing from the ASSOCTABLE.

Explanation: An ASSOCTABLE statement contained an incorrect field as indicated.

Recovery: Use a legal value for the field. The syntax rules appear under ASSOCTABLE Statement.

You specified an incorrect parameter in SUBITEMSIZE.

Explanation: A SUBITEMSIZE statement contained an incorrect value as indicated.

Recovery: Use a legal value for the field. The syntax rules appear under SUBITEMSIZE Statement.

The size value in SUBITEMSIZE must be 2 or greater.

Explanation: A SUBITEMSIZE statement contained an incorrect value as indicated.

Recovery: Use a legal value for the field. The syntax rules appear under SUBITEMSIZE Statement.

A font file has an incorrect kern pair identifier or non-zero usKerningPairs.

Explanation: A FONT or RESOURCE statement referred to a font file which has an incorrect binary format.

Recovery: Correct the kerning information table in the referenced font file.

A font file has an incorrect additional metrics identifier or font signature.

Explanation: A FONT statement referred to a file containing incorrect data as indicated.

Recovery: Use a properly-formatted font file.

You specified an incorrect data type in RCDATA.

Explanation: An RCDATA statement contained an incorrect numeric or string data item.

Recovery: Correct the syntax of the item. The syntax rules appear under RCDATA Statement.

You specified an incorrect data type in RESOURCE.

Explanation: RESOURCE statement contained an incorrect numeric or string data item.

Recovery: Correct the syntax of the item. The syntax rules appear under RESOURCE Statement.

You specified an incorrect text string or ordinal.

Explanation: A statement contained an incorrect numeric or string data item.

Recovery: Correct the syntax of the item.

The value of an ordinal must be from 0 to 65535.

Explanation: A statement contained an incorrect numeric or string data item.

Recovery: Correct the syntax of the item.

A logical OR cannot follow another logical OR.

Explanation: A statement contained an incorrect expression with logical operators.

Recovery: Correct the syntax of the expression.

An integer value must follow the not operator.

Explanation: A statement contained an incorrect expression with logical operators.

Recovery: Correct the syntax of the expression.

RC found an incorrect character in an Expression.

Explanation: A statement contained an expression with incorrect characters.

Recovery: Correct the syntax of the expression.

An ordinal value must be preceded by a #.

Explanation: A MENUITEM statement with style MIS_BITMAP accepts in its text field a quoted value of a previously-defined bitmap, in the form "#n", where n is the bitmap id. You coded this field in an incorrect format as indicated in the message.

Recovery: Correct the syntax of the text field.

You must specify an ordinal value from 0 to 65535 after a '#'.

Explanation: A MENUITEM statement with style MIS_BITMAP accepts in its text field a quoted value of a previously-defined bitmap, in the form "#n", where n is the bitmap id. You coded this field in an incorrect format as indicated in the message.

Recovery: Correct the syntax of the text field.

You specified an incorrect text parameter.

Explanation: A statement contained a text field with an incorrect string.

Recovery: Correct the syntax of the field.

You specified a non-numeric parameter.

Explanation: A statement contained a numeric field that did not evaluate to a number.

Recovery: Correct the syntax of the field.

The Resource ID must be a value from 1 to 65535 (unsigned).

Explanation: A statement contained a resource ID field that did not evaluate to a number in the expected range.

Recovery: Correct the value of the id field.

The Resource ID must be a value from 0 to 65535 (unsigned) or -32768 to 32767 (signed).

Explanation: A statement contained a resource ID field that did not evaluate to a number in the expected range.

Recovery: Correct the value of the id field.

The Resource ID must not be negative.

Explanation: A statement contained a resource ID field that did not evaluate to a number in the expected range.

Recovery: Correct the value of the id field.

The Resource ID must not be 0.

Explanation: A statement contained a resource ID field that did not evaluate to a number in the expected range.

Recovery: Correct the value of the id field.

The Control ID must be a value from 0 to 65535 (unsigned) or -32768 to 32767 (signed).

Explanation: A statement contained a resource ID field that did not evaluate to a number in the expected range.

Recovery: Correct the value of the id field.

Only one top level window is allowed.

Explanation: A WINDOWTEMPLATE or DLGTEMPLATE statement contained more than one WINDOW or DIALOG.

Recovery: Use only one window per template.

A Template statement is empty. You must specify a top level window.

Explanation: A WINDOWTEMPLATE or DLGTEMPLATE statement contained no WINDOW or DIALOG.

Recovery: Use exactly one window per template.

RC found a duplicate string id.

Explanation: A STRINGTABLE statement contained a duplicate identifier.

Recovery: Use unique string ids.

RC found a duplicate message id.

Explanation: A MESSAGETABLE statement contained a duplicate identifier.

Recovery: Use unique and message ids.

A key-value character code in double quotation marks is a missing parameter.

Explanation: An ACCELTABLE statement contained a key-value field in an incorrect format as indicated by the message.

Recovery: Correct the format or value of the field. The syntax rules appear under ACCELTABLE Statement.

Parameter key-value has more than the allowed characters.

Explanation: An ACCELTABLE statement contained a key-value field in an incorrect format as indicated by the message.

Recovery: Correct the format or value of the field. The syntax rules appear under ACCELTABLE Statement.

Parameter key-value with control (^) is out of the valid range (^A - ^Z).

Explanation: An ACCELTABLE statement contained a key-value field in an incorrect format as indicated by the message.

Recovery: Correct the format or value of the field. The syntax rules appear under ACCELTABLE Statement.

Parameter key-value must be in the range (0 - 255).

Explanation: An ACCELTABLE statement contained a key-value field in an incorrect format as indicated by the message.

Recovery: Correct the format or value of the field. The syntax rules appear under ACCELTABLE Statement.

Parameter key-value must be string or numeric.

Explanation: An ACCELTABLE statement contained a key-value field in an incorrect format as indicated by the message.

Recovery: Correct the format or value of the field. The syntax rules appear under ACCELTABLE Statement.

Parameter command must be numeric.

Explanation: An ACCELTABLE statement contained a command field in an incorrect format as indicated by the message.

Recovery: Correct the format or value of the field. The syntax rules appear under ACCELTABLE Statement.

Parameter command must be a value from 0 to 65535.

Explanation: An ACCELTABLE statement contained a command field in an incorrect format as indicated by the message.

Recovery: Correct the format or value of the field. The syntax rules appear under ACCELTABLE Statement.

Parameter accel-option is incorrect.

Explanation: An ACCELTABLE statement contained a accel-option field in an incorrect format (or missing) as indicated by the message.

Recovery: Supply the correct value of the field. The syntax rules appear under ACCELTABLE Statement.

Accel-option (CHAR, SCANCODE, or VIRTUALKEY) is a missing parameter.

Explanation: An ACCELTABLE statement contained a accel-option field in an incorrect format (or missing) as indicated by the message.

Recovery: Supply the correct value of the field. The syntax rules appear under ACCELTABLE Statement.

The accelerator table is empty.

Explanation: An ACCELTABLE statement contained an empty data block.

Recovery: Supply the missing table. The syntax rules appear under ACCELTABLE Statement.

You specified a non-numeric menu item attribute.

Explanation: A MENUITEM statement contained an undefined attribute.

Recovery: Supply the missing attribute value. The syntax rules appear under MENUITEM Statement.

The menu is empty.

Explanation: A MENU statement contained an empty data block.

Recovery: Supply the missing menu items. The syntax rules appear under MENU Statement.

You specified an incorrect presentation parameter.

Explanation: A control statement contained an incorrect presentation parameter.

Recovery: Correct syntax of the value or parameter.

You specified an incorrect control data value.

Explanation: A control statement contained an incorrect control data value.

Recovery: Correct syntax of the value or parameter.

DLGINCLUDE statement must have a filename to include.

Explanation: You specified a DLGINCLUDE statement but omitted the file name.

Recovery: Code the name of the file on the DLGINCLUDE statement.

Data in a STRINGTABLE statement BEGIN/END body is missing or incorrect.

Explanation: You specified incorrect string data inside the data block of a STRINGTABLE statement, as indicated by the message.

Recovery: Correct the syntax of the string. The syntax rules appear under STRINGTABLE Statement.

Data in a MESSAGETABLE statement BEGIN/END body is missing or incorrect.

Explanation: You specified incorrect string data inside the data block of a MESSAGETABLE statement, as indicated by the message.

Recovery: Correct the syntax of the string. The syntax rules appear under MESSAGETABLE Statement.

An Assocname is missing in ASSOCTABLE.

Explanation: The field indicated by the message is missing from an ASSOCTABLE statement.

Recovery: Supply the missing field.

A file-match-string is missing in ASSOCTABLE.

Explanation: The field indicated by the message is missing from an ASSOCTABLE statement.

Recovery: Supply the missing field.

Data in an RCDATA statement BEGIN/END body is missing or incorrect.

Explanation: Data items are wrong or omitted in the statement indicated by the message.

Recovery: Supply the correct data.

Data in RESOURCE statement BEGIN/END body is missing or incorrect.

Explanation: Data items are wrong or omitted in the statement indicated by the message.

Recovery: Supply the correct data.

Data in ASSOCTABLE statement BEGIN/END body is missing or incorrect.

Explanation: Data items are wrong or omitted in the statement indicated by the message.

Recovery: Supply the correct data.

RC expected a SUBITEMSIZE statement before the parameter.

Explanation: A HELPSUBTABLE statement was missing the SUBITEMSIZE statement required when a size other than the default is to be used.

Recovery: Supply the missing SUBITEMSIZE statement. The syntax rules appear under HELPSUBTABLE Statement

Elements in HELPSUBITEM do not match with SUBITEMSIZE statement.

Explanation: The structure of a HELPSUBITEM statement did not conform to the size specified in the SUBITEMSIZE statement.

Recovery: Correct the format of the HELPSUBITEM statement. The syntax rules appear under HELPSUBITEM Statement

The Resource Type value overflowed when creating the LR formatted record.

Explanation: A Resource Type cannot exceed 65535.

Recovery: Specify a value between 0 and 65535.

The Resource ID value overflowed when creating the LR formatted record.

Explanation: A Resource ID cannot exceed 65535.

Recovery: Specify a value between 0 and 65535.

The Resource Flag value overflowed when creating the LR formatted record.

Explanation: A Resource Flag cannot exceed 65535.

Recovery: Specify a value between 0 and 65535.

The Resource Size value overflowed when creating the LR formatted record.

Explanation: A Resource Size cannot exceed 65535.

Recovery: Specify a value between 0 and 65535.

Data in MSGDATA statement BEGIN/END body is missing or incorrect.

Explanation: The MSGDATA body is missing or incorrect.

Recovery: Correct the syntax or add the missing data.

A suffix letter is missing after the message id.

Explanation: You left out a required suffix letter after the message id.

Recovery: Correct your input and try again.

A colon (:) is missing after the suffix letter.

Explanation: You left out a required colon (:) after the suffix letter.

Recovery: Correct your input and try again.

A MSGDATA statement has a duplicate message ID.

Explanation: You cannot use the same message ID on more than one MSGDATA statements.

Recovery: Use a unique message ID.

The segment name contains extended characters, which must be less than or equal to ASCII 127.

Explanation: Segment names must use ASCII characters with a value less than or equal to 127.

Recovery:

A Resource statement must have either a file specification or a BEGIN/END block.

Explanation: You coded a RESOURCE statement without a file specification or a data block, or you provided both a file specification and a data block. Exactly one of these forms must be provided.

Recovery: Correct the format of the RESOURCE statement. The syntax rules appear under

The source file ended with a continuation sequence.

Explanation: Your input script file ended prematurely before the end of a continued line.

Recovery: Supply the completion of the incomplete line.

The source file ended while a comment was active.

Explanation: Your input script file ended prematurely before the end of a comment.

Recovery: Supply the completion of the incomplete comment.

You specified an unknown preprocessor directive.

Explanation: You used a # directive which is unknown to the preprocessor.

Recovery: Remove the unknown directive.

A header filename was missing from an #include directive.

Explanation: You used an #include directive without naming a file to include.

Recovery: Supply the missing file name on the directive.

A header filename contained only whitespace.

Explanation: The file referenced by an #include directive contained no tokens to parse.

Recovery: Supply the missing contents of the file, or remove the directive.

RC could not find the header filename on an #include directive.

Explanation: The file referenced by an #include directive could not be located by the preprocessor.

Recovery: Check the spelling of the file and path, and confirm that the file exists.

#undef appeared with unknown macro name.

Explanation: The macro referenced by an #undef directive was not known to the preprocessor.

Recovery: Check the spelling of the macro, or remove the #undef directive.

You specified an include filename recursively.

Explanation: The name on an #include directive has already been included at a higher level.

Recovery: Remove the nested #include directive.

A source filename contains no characters.

Explanation: The input file was empty.

Recovery: Check the spelling of the name, and confirm that the proper data are contained in it.

RC is ignoring a typecast in an expression.

Explanation: You used a type cast in an expression in a preprocessor directive. The cast will be ignored.

Recovery: Remove the type cast.

RC found the characters /* inside a C style comment.

Explanation: The input file had a C comment which contained the start of another comment.

Recovery: Do not use the characters /* inside a C comment; comments cannot be nested.

You defined a macro with the name of a resource statement.

Explanation: You used the name of a resource statement (for example, search file for more e.g.'s. DLGTEMPLATE) as the name of a macro to be defined. The names of resource statements are reserved words.

Recovery: Use another name for the macro.

The given directive is missing its end-of-line character.

Explanation: You used a preprocessor directive (such as #define) but started another statement later on the same line. A preprocessor directive needs to be contained on one line.

Recovery: Use the preprocessor directive alone on a line.

You specified conflicting or redundant memory or load options.

Explanation: Memory or load options you specified conflict or are redundant.

Recovery: Specify non-conflicting or non-redundant memory or load options.