R3006

name is an incorrect macro name.

Explanation: The macro name name does not conform to the rules for composing macro names as defined in C Language Reference. The Resource Compiler will ignore the definition.

Recovery: Choose a legal name for the macro.

Country code code is incorrect for this code page. RC is using previously-defined lead bytes.

Explanation: The country code is not defined for use with the specified code page.

Recovery: Confirm that the country code and code page are correct. For a list of supported code pages, refer to the "COUNTRYCODE" section of the OS/2 Warp Control Programming Guide and Reference.

Code page cp is incorrect. RC is using the default code page.

Explanation: The code page number cp is unknown, and the compiler will use a default code page.

Recovery: Select a supported code page. For a list of supported code pages, refer to the "COUNTRYCODE" section of the OS/2 Warp Control Program Programming Guide and Reference.

RC is ignoring excess operand text.

Explanation: The given text was an incorrect operand on the command line.

Recovery: Correct or remove the undefined text.

RC is ignoring the compression option for the NE format executable file filename.

Explanation: The compression option you specified is not valid for this operation.

Recovery: No action is necessary.

RC is ignoring the pack option for the NE executable file filename.

Explanation: The pack option you specified is not a valid for this operation.

Recovery: No action is necessary.

RC found no resource item in this file.

Explanation: The input binary resource file did not contain any resources.

Recovery: Confirm that the input file has the expected resource data.

RC found a resource type equal to zero.

Explanation: The input binary resource file contained a resource with type zero, which is incorrect.

Recovery: Correct the resource definition in the input file.

RC is using ordinal number as a text field.

Explanation: The specified number is the value of a text field on a resource statement.

Recovery: No action is necessary.

RC is truncating this text to 255 characters:

Explanation: The text that follows this message appeared in a field limited to 255 characters. The compiler will use only the text shown.

Recovery: No action is necessary.

RC is ignoring an extra comma in a CTLDATA statement.

Explanation: You used a CTLDATA statement with a list of data values separated by commas. The compiler will ignore the extra commas it found in the list.

Recovery: No action is necessary.

RC is truncating to a 16-bit value.

Explanation: You used a long integer value in a data field which is limited to 64K. The compiler will use only the least significant 16 bits of the number.

Recovery: No action is necessary.

All text after percent followed by 0 characters will be truncated to the end of the line.

Explanation: You enter a text string with a percent 0 (%0) in it.

Recovery: No action is necessary.

Parameters VIRTUALKEY, SCANMODE, and CHAR are mutually exclusive.

Explanation: You used parameters in an ACCELTABLE statement which cannot be used together.

Recovery: The rules for coding the accelerator-options field are given under

Parameters SYSCOMMAND, and HELP are mutually exclusive.

Explanation: You used parameters in an ACCELTABLE statement which cannot be used together.

Recovery: The rules for coding the accelerator-options field are given under ACCELTABLE Statement.

Numeric value in RCDATA statement has been overflowed.

Explanation: While evaluating numeric data in a block, the compiler computed a 32-bit number using a 16-bit data field. This conversion changed the value of the number.

Recovery: No action is necessary.

Numeric value in RCDATA statement has been modified.

Explanation: While evaluating numeric data in a block, the compiler computed a 32-bit number using a 16-bit data field. This conversion changed the value of the number.

Recovery: No action is necessary.

Numeric value in RESOURCE statement has been overflowed.

Explanation: While evaluating numeric data in a block, the compiler computed a 32-bit number using a 16-bit data field. This conversion changed the value of the number.

Recovery: No action is necessary.

Numeric value in RESOURCE statement has been modified.

Explanation: While evaluating numeric data in a block, the compiler computed a 32-bit number using a 16-bit data field. This conversion changed the value of the number.

Recovery: No action is necessary.

MENUITEM expected a style of MIS_SUBMENU.

Explanation: A MENUITEM statement having a submenu will use menuitem style MIS_SUBMENU by default.

Recovery: Specify MIS_SUBMENU in MENUITEM statement.

RC ignored text specified for SEPARATOR.

Explanation: A MENUITEM SEPARATOR statement had extra text at the end. Resource Compiler will ignore the extra text.

Recovery: Remove the extra text.

RC is ignoring a Message text line with no message ID.

Explanation: A MESSAGETABLE statement without an ID has been ignored by the Resource Compiler.

Recovery: To use the message, provide an identifier for it.

RC encountered a duplicate resource type and id. RC is ignoring resource ID id of type type.

Explanation: A resource of type type and id id has the same type and id as another resource. The Resource Compiler used the first and ignored the other.

Recovery: Provide a unique identifier for the duplicated resource.

The ID value to be used is value.

Explanation: The preprocessor will use value as the resource identifier.

Recovery: No action is necessary.

A parameter value is out of range. Valid signed range is -32768 to 32767, unsigned range is 0 to 65535.

Explanation: You supplied a value for a 16-bit parameter which was too large to be contained in the field.

Recovery: Resource Compiler has converted the value to the 16-bit number given.

RC is using the first DEFAULTICON statement, which you specified more than once.

Explanation: You supplied more than one DEFAULTICON statement for your resources. Resource Compiler will ignore all DEFAULTICON statements after the first one.

Recovery: Remove the extra DEFAULTICON statements.

'text' is not supported in this version of RC. It is being ignored.

Explanation: The given text is not supported by this version of the Resource Compiler. It is ignored.

Recovery: Remove the text.

The DBCS lead-byte option is no longer supported in RC.

Explanation: The command line and DBCS environment variable options will be ignored.

Recovery: Use an installed code page.