Serious Errors [ HP COBOL II/XL Reference Manual ] MPE/iX 5.0 Documentation
HP COBOL II/XL Reference Manual
Serious Errors
------------------------------------------------------------------------------------------------
401 ERROR ASSIGN CLAUSE REQUIRED WITH SELECT STATEMENT.
MESSAGE
CAUSE
------------------------------------------------------------------------------------------------
402 ERROR MISSING ! KEY CLAUSE.
MESSAGE
CAUSE RELATIVE, RECORD or ACTUAL KEY is missing.
------------------------------------------------------------------------------------------------
[REV BEG]
403 ERROR FUNCTION NOT ALLOWED AS OPERAND.
MESSAGE
CAUSE Functions are not allowed in the following cases:
1. Target of any statement.
2. Operand of a call.
3. Where specific rules of the statement disallow functions.
[REV END]
------------------------------------------------------------------------------------------------
[REV BEG]
404 ERROR NUMERIC FUNCTION NOT ALLOWED AS OPERAND.
MESSAGE
CAUSE Numeric functions are only allowed in arithmetic expressions.[REV
END]
------------------------------------------------------------------------------------------------
405 ERROR TOO MANY KEY CLAUSES.
MESSAGE
CAUSE More than one RELATIVE clause, or RECORD clause, or ACTUAL KEY
clause appears. Or the file organization does not support keys.
That is, the organization is sequential.
------------------------------------------------------------------------------------------------
406 ERROR ! ! FOR !.
MESSAGE
CAUSE This error message is for illegal or missing forward references.
The insertions are for the forward reference type, the name of the
forward reference, and the name of the file or table containing the
forward reference. The forward reference types are relative keys,
record keys, and actual keys.
------------------------------------------------------------------------------------------------
409 ERROR ILLEGAL OPERAND ! IN SET STATEMENT.
MESSAGE
CAUSE One of the operands must be an INDEX-NAME, MNEMONIC-NAME or
CONDITION-NAME. Any identifiers must be numeric integers.
------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
410 ERROR SYNTAX ERROR. FOUND: !; EXPECTING ONE OF THE FOLLOWING:!!.
MESSAGE
CAUSE [REV BEG]An item appears in some context that the compiler cannot
recognize. The items which are allowed at this point are listed.
EXPECTING...Disabled_reserved_word probably means the wrong entry
was used to invoke the compiler. The compiler attempts to recover
from this error.[REV END]
---------------------------------------------------------------------------------------
412 ERROR PARAMETER ! MUST BE 01 OR 77 LEVEL ITEM IN LINKAGE SECTION.
MESSAGE
CAUSE An illegal parameter was used in a PROCEDURE DIVISION USING
statement.
---------------------------------------------------------------------------------------
413 ERROR FILE NAME ! DOES NOT APPEAR IN A SELECT CLAUSE AND/OR FD/SD ENTRY
MESSAGE IS NOT UNIQUE.
CAUSE A name that appears in an FD or SD entry in the DATA DIVISION did
not appear in a SELECT clause in the ENVIRONMENT DIVISION or the
the name is not unique.
---------------------------------------------------------------------------------------
414 ERROR ! IS AN ILLEGAL KEY.
MESSAGE
CAUSE The data names identified as sort/merge keys must be described
within the records associated with the Sort/Merge file. For READ
and START statements, the KEY phrase must reference a valid key for
the Relative or Indexed file.
---------------------------------------------------------------------------------------
415 ERROR INVALID LIBRARY OR TEXT-NAME.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
416 ERROR COPYLIB OR $INCLUDE NESTED TOO DEEP.
MESSAGE
CAUSE The maximum $INCLUDE/COPY nesting is 10.
---------------------------------------------------------------------------------------
417 ERROR MACRO DEFINITION MAXIMUM LENGTH EXCEEDED.
MESSAGE
CAUSE Errors 417 and 418 may cause error 461.
---------------------------------------------------------------------------------------
418 ERROR PSEUDO-TEXT-BUFFER OVERFLOW.
MESSAGE
CAUSE Errors 417 and 418 may cause error 461.
---------------------------------------------------------------------------------------
419 ERROR MOVE OR COMPARE >32 K BYTES.
MESSAGE
CAUSE A MOVE statement or condition clause exceeds the maximum character
limit.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
420 ERROR SECTION MISPLACED OR DUPLICATED.
MESSAGE
CAUSE FILE SECTION, WORKING-STORAGE SECTION and LINKAGE SECTION must
appear in that order when used.
---------------------------------------------------------------------------------------
421 ERROR OPERAND ! HAS ILLEGAL FORMAT FOR STATEMENT.
MESSAGE
CAUSE
* This type of operand may not be used in the ACCEPT or
DISPLAY statements.
* Bad identifier-1 for CALL or identifier for CALL INTRINSIC.
* EXAMINE identifier not usage DISPLAY or literals not one
character.
* GO TO...DEPENDING identifier not an integer.
* INSPECT operands not usage DISPLAY or literals. (All but
tallying identifier-2, which must be numeric.)
* INSPECT identifier-1 not usage DISPLAY or a group.
* CHARACTERS operands must be one character.
* Replacing operands must be of the same size.
* Invalid identifier-1 or identifier-2 for SEARCH. SEARCH ALL
must have an INDEXED or KEY clause.
* SEARCH ALL must have a key referenced in each condition.
* STRING and UNSTRING POINTER must be numeric and large
enough.
* STRING INTO operands must be alphanumeric without JUST.
* STRING source and delimiter operands must be usage DISPLAY
or nonnumeric literals without ALL.
* UNSTRING identifier-1 must be usage DISPLAY.
* UNSTRING DELIMITED BE operands must be usage DISPLAY or
nonnumeric literals without ALL.
* UNSTRING identifier-4 must be usage DISPLAY and not edited.
* UNSTRING identifier-5 must be usage DISPLAY and not edited.
* POINTER, COUNT, TALLYING operands must be integers with no
P.[REV BEG]
* Parameters to a FUNCTION must be of the correct type. That
is, numeric or integer passed to alphanumeric or numeric
passed to integer.[REV END]
---------------------------------------------------------------------------------------
422 ERROR SIZE OF DATA SEGMENT GREATER THAN {1G OR 64K} BYTES.
MESSAGE
CAUSE The upper limit on the size of the data area has been reached. The
maximum is 1G bytes on HP COBOL II/XL and 64K bytes on HP COBOL
II/V.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
423 ERROR MORE THAN 500 ENTRIES IN A GO TO DEPENDING ON STATEMENT.
MESSAGE
CAUSE A GO TO DEPENDING ON statement has too many paragraph/section names
in the list.
---------------------------------------------------------------------------------------
424 ERROR MORE THAN {255/57} NON-REDEFINED 01/77 LEVEL ITEMS IN LINKAGE
MESSAGE SECTION.
CAUSE The limit of independent 01/77 level items in the LINKAGE SECTION
has been exceeded. The maximum is 255 on HP COBOL II/XL and 57 on
HP COBOL II/V. Use REDEFINES if possible.
---------------------------------------------------------------------------------------
425 ERROR PARAMETER #! MAY NOT BE A LITERAL.
MESSAGE
CAUSE A literal is attempted to be passed to an intrinsic which expects
an array or a pointer.
---------------------------------------------------------------------------------------
426 ERROR ILLEGAL END PROGRAM HEADER.
MESSAGE
CAUSE Check that the program-name here matches the one in the
IDENTIFICATION DIVISION.
---------------------------------------------------------------------------------------
427 ERROR PROGRAM-ID ! NOT UNIQUE.
MESSAGE
CAUSE Program names in a compilation unit must be unique.
---------------------------------------------------------------------------------------
428 ERROR MISSING END PROGRAM HEADER FOR PROGRAM !.
MESSAGE
CAUSE Batched or nested programs require END PROGRAM headers.
---------------------------------------------------------------------------------------
MPE/iX 5.0 Documentation