CICS Runtime Messages

Messages

CICS Runtime Messages provide the following information:

•	Description: The meaning and context of the message.

•	Action: What steps you can take to correct any problems identified.

•	See Also: A pointer to related information (not specified for all messages).

Preprocessor Messages

Error Messages

Invalid CICS Messages

Error messages are printed whenever an invalid CICS instruction is found use the following format:

•	Error summary.

•	Text of the CICS statement (without margins).

•	More detailed explanations, if necessary.

Summaries may contain "Instruction invalid" (in the case of IGNORE and HANDLE instructions), "No rules matching the following instruction", "Several rules matching the following instruction".

IGNORE and HANDLE instructions messages are quite straightforward:

"IGNORE should be constructed with CONDITION"

When no rules match a CICS instruction, the error message lists, for all commands starting by the same keyword, why this command does not fit.

•	<command> expects one of <keyword list>, but none is present.

•	<command> expects <keyword>, but could not find it.

•	<command> does not know about <keyword>.

•	In <command>, <keyword> expects either: … <keyword> (one of <keyword list>), … but none of them were found.

•	In <command>, <keyword> is present and not <keyword> even if they must be used at the same time.

•	In <command>, <keyword> and <keyword> cannot be used at the same time.

•	Default value of <keyword> is supposed to be computed with value of <keyword>, but its value (<value>) is not a charstring.

If several commands match, the preprocessor lists them all. This will not actually happen, as the preprocessor checks the commands for ambiguity before translation.

Other Error Messages

The following error messages occur naturally if the preprocessor is used with the wrong options:

•	Cannot open file <file name> means that the CICS instruction file is not present or not readable.

•	Cannot open $dir/KIX--***.cpy means that the preprocessor was asked to generate copies in a wrong place (nonexistent or read-only directory…).

Maintenance Messages

These messages are encountered if your CICS instruction file is corrupted.

•	<keyword> defined as <Pic clause 1> and <Pic clause 2> in same group.

•	<keyword> defined twice in same rule.

•	A part of a (|) construct has no required keyword.

•	Instruction <instruction name> uses <nb1> keyword(s) but describes <nb2> keyword(s).

•	Keyword <keyword> in instruction <instruction name> is not described.

•	Instructions <instruction name 1> and <instruction name 2> share all their required keywords.

•	Line not recognized.

ARTDPL Messages

Abend messages

When abend occurs, following message is logged:

Abend <abend code> detected in transaction <transaction name> program <program name>

The abend code is assigned to URCODE. The first character of abend code is assigned to highest byte of URCODE, the second character is assigned to the second high byte, the third character is assigned to the third byte, and the last character of abend code is assigned to least byte of URCODE. The abend code is also filled in the field CX_ABENDCODE of FML buffer.