COBEC0011S <x> is not a valid EXEC Type The word <x> which immediately followed the EXEC word is not recognized as a valid EXEC type. The preprocessor will recognize CICS, DLI,
and SQL as valid types.
COBEC0012S EXEC <x> Preprocessor is not active Your source code contains EXEC DLI or EXEC SQL statements, but the appropriate preprocessor is not begin used according to
the options specified to the TX preprocessor. See the chapter on Working with Databases.
COBEC0014S Too many Options in EXEC CICS statement The EXEC CICS statement has more than 100 options specified between the 'command' and the END-EXEC. Note that this is about
16 larger than the largest number of distinct options possible in any valid EXEC CICS statement.
COBEC0015S EXEC CICS Option Argument exceeds 1024 char The source text for a single options argument exceeded 1024 characters (all blanks compressed to minimum required) without
encountering the close parenthesis, ")", marking the end of the option value (argument).
COBEC0019I <opt> option is ignored for <cmd> The option <opt> is ignored on the EXEC CICS <cmd> command. This normally applies to options which have no effect on the API behavior, but are specified for efficiency considerations
in the mainframe implementation of the CICS API.