Error Codes and Messages › ENCP9xx Messages

ENCP9xx Messages

This section describes the messages generated during parsing, along with possible causes and actions to take in error situations.

ENCP901E

A literal or identifier was expected, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP902E

A literal was expected, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP903E

An identifier was expected, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP904E

Invalid wording was encountered, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP905E

A keyword was expected, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP906E

Command not recognized, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP907E

The value specified is too long: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP908E

An ending quote was not found for: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP909E

Expecting a number from 0 to 2,147,483,647, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP910E

Storage was not available to parse: x

Reason:

A parsing error occurred as noted in the message.

Action:

Increase the size parameter and rerun.

ENCP911E

Expecting a number from 0 to 32,767, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP912E

Expecting the end of a statement, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP913E

An invalid hexadecimal constant was specified, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP914E

Expected a keyword or an end-of-statement, found: x

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP915E

Expected a keyword or an end-of-statement, found: "end-of-file"

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP916E

Expected an end-of-statement, found end-of-file

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP917E

Internal error: The CALL stack size was exceeded

Reason:

A parsing error occurred as noted in the message.

Action:

Call CA Technical Support.

ENCP918E

Internal error: The CALL stack is empty. A RTRN is mismatched

Reason:

A parsing error occurred as noted in the message.

Action:

Call CA Technical Support.

ENCP919E

Unbalanced expression: Too many parentheses were found

Reason:

A parsing error occurred as noted in the message.

Action:

Correct the statement in error.

ENCP920E

Internal error: An invalid syntax rule was found

Reason:

A parsing error occurred as noted in the message.

Action:

Call CA Technical Support.

ENCP921E

Internal error: The CALL stack not empty at the end of the statement

Reason:

A parsing error occurred as noted in the message.

Action:

Call CA Technical Support.

ENCP922E

Internal error: A nested statement is not complete at the end of the statement

Reason:

A parsing error occurred as noted in the message.

Action:

Call CA Technical Support.

ENCP923E

Internal error: An ALLOC rule did not precede a store operation

Reason:

A parsing error occurred as noted in the message.

Action:

Call CA Technical Support.

ENCP924E

An I/O error occurred reading the input file

Reason:

A parsing error occurred as noted in the message.

Action:

Check for other error messages. Correct and resubmit.

ENCP925E

Internal error: The syntax tree is invalid. The end of the tree may have been reached

Reason:

A parsing error occurred as noted in the message.

Action:

Call CA Technical Support.