Previous Topic: Compiler MessagesNext Topic: TNT Compiler Messages


FMT Compiler Messages

The FMT compiler can issue the following return codes and messages:

Return code

Message

225001

'EJECT' NOT ALONE ON CARD. TOKEN ASSUMED

EJECT must appear as the only entry on the card, unless the function of the card is to be other than that of a compiler directive.

Severity: W

225002

INVALID 'SPACE' COMMAND PARAMETER

SPACE must be followed by a blank and, optionally, a one-digit number greater than zero indicating the number of lines to be spaced.

Severity: W

225003

'SPACE' NOT ALONE ON CARD. TOKEN ASSUMED

SPACE must appear as the only entry on the card, unless the function of the card is to be other than that of a compiler directive.

Severity: W

225004

SEQUENCE ERROR. RUN ABORTED.

Statements must be in sequential order.

Severity: F

225005

STRING EXCEEDS MAXIMUM OR AVAILABLE LENGTH

The number of characters in the character string specified exceeds the length that is allowed for this particular parameter.

Severity: E

225006

HEX STRING EXCEEDS MAXIMUM OR AVAILABLE LENGTH

The number of characters in the hexadecimal string specified exceeds the length that is allowed for this particular parameter.

Severity: E

225007

HEX STRING CONTAINS INVALID CHARACTERS

Nonhexadecimal characters appear in the hexadecimal string specified.

Severity: E

225008

DIAGNOSTIC TABLE SIZE EXCEEDED. TOO MANY ERRORS.

Too many errors have occurred, causing an overflow of the diagnostic table. Correct the previous error.

Severity: F

225009

INVALID ICTL PARAMETER SPECIFICATION

The input control parameter was specified incorrectly. Check the syntax.

Severity: E

225010

INVALID OCTL PARAMETER SPECIFICATION

The output control parameter was specified incorrectly. Check the syntax.

Severity: E

225011

INVALID ISEQ PARAMETER SPECIFICATION

The input sequence parameter was specified incorrectly. Check the syntax.

Severity: E

225012

UNEXPECTED END OF FILE (PERIOD MISSING)

Invalid syntax has been encountered. Check for missing periods.

Severity: F

225013

INVALID KEYWORD, SKIPPING TO NEXT STATEMENT

The keyword encountered is not valid. Compilation resumes with the next statement.

Severity: E

225014

EXPECTED PERIOD, SKIPPING TO NEXT STATEMENT

A period is missing after a statement. Statements must end with a period.

Severity: E

225015

INVALID FMT NAME

An FMT name must be specified as a 1- to 8-character alphanumeric string.

Severity: E

225016

INVALID FILE TYPE

File type must be KSDS/PATH/ESDS/RRDS.

Severity: F

225017

INVALID NUMBER SPECIFIED

Buffer space must be specified as a 1- to 5-digit number that ranges from 0 through 32,767.

Severity: E

225018

INVALID STARTING POSITION

Key or relative-record-number position must be specified as a 1- to 5-digit number that ranges from 0 through 32,767.

Severity: E

225019

INVALID LENGTH SPECIFICATION

Key length must be specified as a 1- to 3-digit number that ranges from 1 to 255.

Severity: E

225020

INVALID EXIT NAME

An exit name must be specified as a 1- to 8-character alphanumeric string.

Severity: E

225021

INVALID RECORD NAME

A record name must be specified as a 1- to 16-character alphanumeric string.

Severity: E

225022

INVALID SET NAME

A set name must be specified as a 1- to 16-character alphanumeric string.

Severity: E

225023

MISSING KEY LENGTH FOR KSDS OR PATH

A key length statement is required for file type KSDS or PATH.

Severity: E

225024

MISSING KEY POSITION FOR KSDS OR PATH

A key position statement is required for file type KSDS or PATH.

Severity: E

225025

KEY LENGTH INVALID FOR ESDS OR RRDS

A key length statement is not allowed for file type ESDS or RRDS.

Severity: E

225026

KEY POSITION INVALID FOR ESDS OR RRDS

A key position statement is not allowed for file type ESDS or RRDS.

Severity: E

225027

RRN POSITION INVALID FOR KSDS, PATH, ESDS

A relative-record-number position statement is used for file type RRDS only.

Severity: E