Object declared as a pointer to a function is not allowed when TARGET(TPF) is specified.
Recovery: Remove the declaration.
Function parameter cannot be a pointer to a function if target is TPF.
Recovery: Remove the declaration.
Calling a function with a function pointer is not allowed when TARGET(TPF) is specified.
Recovery: Call the function by its name.
External function names must have a length of four bytes if target is TPF.
Recovery: Change the function name.
Objects with extern storage class are not allowed.
A structure was passed as parameter to a function. Under TPF, this might cause the stack to overflow.
Recovery: Avoid passing structures to a function. (Use pointers to structures instead.)
Function "main" is not allowed when TPF is targeted.
Recovery: Use a function name other than "main".
The zero-sized array must be the last member in the structure.
Recovery: Remove members that occur after the zero-sized array.
The storage class is not appropriate for this declaration. Restrictions include: 1) Storage class specifier not allowed on aggregate members, casts, sizeof or offsetof declarations. 2) Declarations at file scope cannot have 'register' or 'auto' storage class.
Recovery: Specify a different storage class.
The linkage specified in the declaration is inconsistent with that specified in the previous declaration. _Export linkage is assumed.
Either the _Export or _Import keyword, or #pragma export or #pragma import was used with data or a function which is not external.
The __thread keyword was specified for data that is not external or static or for a function.
Recovery: Remove the __thread keyword.
Valid sub specifiers for __declspec are thread, dllimport and dllexport.
A function or variable that is declared as import cannot also be defined in the same compilation unit.
The specified qualifier is not supported on the target platform and will have no effect.
A #pragma is referring to an identifier that has not been defined.
Recovery: Define the identifier or remove the #pragma.
The identifier does not exist on the alignment stack. The new packing value is set to either the alignment specified in the pragma or the default alignment for the module.
Recovery: Remove the identifier, or ensure that the alignment stack has been set up correctly.
The alignment stack is empty. The new packing value is set to either the alignment specified in the pragma or the default alignment for the module.
Recovery: Remove the pop operation, or ensure that the alignment stack has been set up correctly.
A variable which has thread local storage cannot also be exported or imported.
Recovery: Remove either the thread specification or the export or import specification so there is no longer a conflict.
Although "&1" is not a keyword, it is a special function that cannot be inlined or declared as static.
Recovery: Remove the inline or static specifier from the declaration of "&1".
The pragma is not supported by this compiler.
Recovery: The pragma can be removed if desired.
The specified keyword is not supported on the target platform and will have no effect.
The specified #pragma is not supported on the target platform and will have no effect. See the C and C++ Language Reference for the list of valid #pragma directives.
Recovery: Change or remove the #pragma directive.
This message traces #include file processing.
Recovery: No response required.
#pragma import is not supported on the target platform. The _Import keyword should be used instead.
Suboption &1 of &2 cannot be specified with option &3. &1 is ignored.
Recovery: Remove the suboption &1 or the option &3.
The compiler cannot resolve the conflicting declarations.
Recovery: Remove one of the declarations.
A macro was expanded in the context of a pragma directive. Please ensure that this is the desired result.
Recovery: Ensure that the macro was intended for expansion.
The "%%" and "%%%%" digraphs will not be supported in the next release. Please use the new digraphs "%:" and "%:%:".
Recovery: Replace the old digraphs with the new digraphs.
(1) If this a USEPCH compile, the PCH address space (heap area) is not the same as in the GENPCH compile. (2) If this is a GENPCH compile, the persistent heap area is full. In either case, the compilation will continue by ignoring the GENP/USEP options.
Recovery: (1) If this is a USEP compile, make sure all the options/pragmas are the same as in GENPCH compile, and the run time environment of the compiler is the same (e.g. region size). (2) If this is a GENP compile, try to reduce the number/size of #include files in the initial sequence.
Timestamp information must be present in ALL #include header files when using PCH. Timestamp is absent in sequential datasets, and maybe absent PDS.
Recovery: Change any sequential dataset header files into a PDS member. Make sure all PDS member header files contain timestamp information.
#pragmas appearing before the Initial Sequence must be the same between the GENP and USEP compile.
Recovery: Make sure the #pragmas before the Initial Sequence are the same. Use GENPCH to regenerate the PCH file would also solve the problem.
If an enum constant is initialized in the definition of an enum tag, the initial value must be an integral expression that has a value representable as an long.
Recovery: Remove the initial value, or ensure that it is an integral constant expression that has a value representable as an long.
If an enum constant is initialized in the definition of an enum tag, the value that it is initialized to must be an integral expression that has a value representable as an long.
Recovery: Remove the initial value, or ensure that it is an integral constant expression that has a value representable as an long.
The number of enumerator constant must not exceed the value of &1.
Recovery: Remove additional enum constants.
errno can not be used in program when ignerrno options is turned on.
Recovery: Change the code that references errno, or do not is the ignerrno optino.
The linkage type of the function puts certain restrictions on the parameter type, on which the function definition violated.
Recovery: Check the linkage type restrictions and change the parameter type.
The specified option is not supported in this release.
Recovery: Remove the option.
This scheduling type cannot have a parameter.
Recovery: Remove the parameter or change the scheduling type.
Constant expression inside schedtype clause must have a value greater than zero.
Recovery: Correct the expression.
Expression inside the schedtype clause must have an integral type
Recovery: Correct the expression
Number of iterations must be an integral constant expression with a positive value.
Recovery: Correct the expression
String literal size cannot be larger than the compiler limit
Recovery: Reduce the size of the string literal.
The keyword __far cannot be used on a function pointer.
Recovery: Remove the keyword __far from the declaration.
![]()
Summary of Compiler Error Messages