HP 3000 Manuals HP 3000 Manuals
Questionable Errors (Continued)
---------------------------------------------------------------------------------------
260 ERROR FILE NAME ! IS NOT DEFINED IN THIS SCOPE.
MESSAGE
CAUSE A file access is being attempted in a scope in which the file is
not defined. The 'FD' may require the 'GLOBAL' clause.
---------------------------------------------------------------------------------------
262 ERROR KEY WORD "!" IGNORED.
MESSAGE
CAUSE For CLOSE REEL/UNIT the close will not be performed. Otherwise the
keyword is ignored (END & BEFORE).
---------------------------------------------------------------------------------------
266 ERROR NAME OF "SD" ENTRY FOUND, EXPECTED "FD" ENTRY.
MESSAGE
CAUSE I/O statements should reference an "FD" name.
---------------------------------------------------------------------------------------
267 ERROR NAME OF "FD" ENTRY FOUND, EXPECTED "SD" ENTRY.
MESSAGE
CAUSE SORT and MERGE statements should reference an "SD" name.
---------------------------------------------------------------------------------------
268 ERROR LINAGE MUST BE SPECIFIED TO USE "WRITE AT END-OF-PAGE".
MESSAGE
CAUSE A "WRITE AT END-OF-PAGE" was found for a file without a LINAGE
clause specified.
---------------------------------------------------------------------------------------
269 ERROR LINAGE MUST BE SPECIFIED TO USE "LINAGE-COUNTER."
MESSAGE
CAUSE "LINAGE-COUNTER" was reference for a file which does not have a
LINAGE clause.
---------------------------------------------------------------------------------------
272 ERROR INTRINSIC RETURN VALUE MISMATCH.
MESSAGE
CAUSE The GIVING operand does not match intrinsic definition.
---------------------------------------------------------------------------------------
273 ERROR INCOMPATIBLE NUMBER OF PARAMETERS FOR INTRINSIC !.
MESSAGE
CAUSE The number of parameters in the USING phrase of the CALL statement
is incompatible with the parameter count specified for the[REV BEG]
intrinsic in the SYSINTR file. The intrinsic does not have OPTION
EXTENSIBLE/VARIABLE.[REV END]
---------------------------------------------------------------------------------------
274 ERROR INVALID SCOPE FOR THIS $ COMMAND.
MESSAGE
CAUSE This command is in effect for all programs in the file and,
therefore, must appear within or before the IDENTIFICATION DIVISION
of the first program in the file.[REV BEG] This applies to the
$CONTROL CODE, NOCODE, VERBS, NOVERBS, SYMDEBUG, and OPTIMIZE
options.[REV END]
---------------------------------------------------------------------------------------
281 ERROR INVALID MACRO NAME, EXPECTED ! AS FIRST CHARACTER.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
282 ERROR INVALID SUBSYSTEM COMMAND PARAMETER.
MESSAGE
CAUSE Invalid or missing parameter.
---------------------------------------------------------------------------------------
283 ERROR INVALID SUBSYSTEM COMMAND.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
284 ERROR TOO MANY PARAMETERS IN MACRO CALL.
MESSAGE
CAUSE Check macro definition.
---------------------------------------------------------------------------------------
285 ERROR INVALID FILENAME IN $INCLUDE COMMAND.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
286 ERROR INVALID CHARACTER IN $PREPROCESSOR COMMAND.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
287 ERROR PSEUDO-TEXT CAN'T BE NULL, BLANK, COMMA, OR SEMICOLON.
MESSAGE
CAUSE Pseudo-text-1 ignored in COPY REPLACING or REPLACE statement.
---------------------------------------------------------------------------------------
288 ERROR INVALID IDENTIFIER USED AS QUALIFIER.
MESSAGE
CAUSE Qualifier in COPY REPLACING or REPLACE identifier.
---------------------------------------------------------------------------------------
289 ERROR INVALID TOKEN IN COPY...REPLACING OR REPLACE CLAUSE.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
290 ERROR ILLEGAL TERMINATION OF NONNUMERIC LITERAL !.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
291 ERROR UNABLE TO FIND LIBRARY MODULE !.
MESSAGE
CAUSE The specified library module was not found in the COPYLIB file.
The specified name is not valid.
---------------------------------------------------------------------------------------
306 ERROR VOL MUST BE A NONNUMERIC LITERAL <= 6 CHARACTERS LONG.
MESSAGE
CAUSE When the VOL phrase of the value of clause specifies a literal, the
literal must be nonnumeric and no more than six characters long.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
307 ERROR LABELS MUST BE NONNUMERIC LITERAL = "IBM" OR "ANS".
MESSAGE
CAUSE When the LABELS phrase of the value of clause specifies a literal,
the literal must be "IBM" or "ANS".
---------------------------------------------------------------------------------------
308 ERROR SEQ MUST BE AN UNSIGNED NUMERIC LITERAL.
MESSAGE
CAUSE When the SEQ phrase of the value of clause specifies a literal, the
literal must be numeric and unsigned.
---------------------------------------------------------------------------------------
309 ERROR EXDATE MUST BE NONNUMERIC LITERAL OF THE FORM "MM/DD/YY".
MESSAGE
CAUSE When the EXDATE phrase of the value of clause specifies a literal,
the literal must be nonnumeric and of the form "MM/DD/YY".
---------------------------------------------------------------------------------------
310 ERROR LINAGE MUST BE AT LEAST 1.
MESSAGE
CAUSE When the lines phrase of the LINAGE clause specifies an integer it
must be >=1.
---------------------------------------------------------------------------------------
311 ERROR FOOTING MAY NOT BE LESS THAN 1.
MESSAGE
CAUSE When the footing phrase of the LINAGE clause specifies an integer,
it is necessary that 1<= footing integer <= LINAGE integer (if
specified).
---------------------------------------------------------------------------------------
312 ERROR FOOTING MAY NOT BE GREATER THAN LINAGE.
MESSAGE
CAUSE When the footing phrase of the LINAGE clause specifies an integer,
it is necessary that 1 <= footing integer <= LINAGE integer (if
specified).
---------------------------------------------------------------------------------------
314 ERROR ! MAY NOT BE LESS THAN 0.
MESSAGE
CAUSE When the TOP or BOTTOM phrase of the LINAGE clause specifies an
integer it must be >=0.
---------------------------------------------------------------------------------------
318 ERROR FILE RECORD ! SMALLER THAN MINIMUM SIZE IN RECORD CONTAINS CLAUSE.
MESSAGE
CAUSE When the record contains clause is specified in an FD or SD every
record subordinate to that file description must have a size that
is within the specified bounds.
---------------------------------------------------------------------------------------
319 ERROR FILE RECORD ! LARGER THAN MAXIMUM SIZE IN RECORD CONTAINS CLAUSE.
MESSAGE
CAUSE When the record contains clause is specified in an FD or SD every
record subordinate to that file description must have a size that
is within the specified bounds.
---------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
320 ERROR FILE ! RECORD SIZE IS ZERO.
MESSAGE
CAUSE When the largest record for a file is 0 characters and there is a
block contains clause in the file description which contains the
characters phrase, it is impossible to compute the blocking factor.
------------------------------------------------------------------------------------------------
321 ERROR INTEGER-1 MUST BE <= INTEGER-2 IN 'TO' PHRASE.
MESSAGE
CAUSE
------------------------------------------------------------------------------------------------
322 ERROR INVALID REFERENCE MODIFICATION.
MESSAGE
CAUSE Either the starting position or length is incorrect or the item is
not USAGE DISPLAY.
------------------------------------------------------------------------------------------------
[REV BEG]
330 ERROR ILLEGAL INTRINSIC FUNCTION NAME !.
MESSAGE
CAUSE The specified name is not valid.
------------------------------------------------------------------------------------------------
331 ERROR WRONG NUMBER OF ARGUMENTS FOR FUNCTION !.
MESSAGE
CAUSE An incorrect number of arguments was specified or the function
doesn't take ALL for subscripts.[REV END]
------------------------------------------------------------------------------------------------
337 ERROR NEXT SENTENCE IS ILLEGAL WITH END-IF OR END-SEARCH.
MESSAGE
CAUSE The NEXT SENTENCE phrase must not be used when an explicit scope
terminator exists.
------------------------------------------------------------------------------------------------
338 ERROR AFTER PHRASE IS ILLEGAL WITH INLINE PERFORM.
MESSAGE
CAUSE
------------------------------------------------------------------------------------------------
347 ERROR PROCEDURE ! HAS MORE THAN ONE DEBUGGING SECTION.
MESSAGE
CAUSE The specified procedure-name is included in more than one USE FOR
DEBUGGING Statement.
------------------------------------------------------------------------------------------------
348 ERROR DEBUGGING SECTION AFTER NON-DEBUGGING SECTION.
MESSAGE
CAUSE A Debugging Section was found after a non-debugging Section. If
the ALL PROCEDURES phrase is specified, the sections prior to the
Debugging Section would not cause the Debugging Section to be
executed.
------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
349 ERROR REFERENCE TO A DEBUG-ITEM OUTSIDE OF A DEBUG SECTION.
MESSAGE
CAUSE A reference to DEBUG-ITEM or one of its subordinate items was made
outside of a Debugging Section.
---------------------------------------------------------------------------------------
350 ERROR [REV BEG]NO CORRESPONDING OR INITIALIZE ITEMS FOUND.
MESSAGE
CAUSE A CORRESPONDING statement has no CORRESPONDING pairs. An
INITIALIZE statement didn't find any items.[REV END]
---------------------------------------------------------------------------------------
351 ERROR REFERENCE TO ! IS NOT UNIQUE.
MESSAGE
CAUSE Reference needs additional qualification(s) to make it unique.
---------------------------------------------------------------------------------------
352 ERROR ILLEGAL CORRESPONDING OPERAND.
MESSAGE
CAUSE The operands are of the wrong type, that is, non-numeric for ADD or
SUBTRACT.
---------------------------------------------------------------------------------------
354 ERROR COMPILER ERROR: INVALID SYMBOL/DATA TABLE REFERENCE.
MESSAGE
CAUSE An invalid symbol or data table reference has occurred internal to
compiler. See directions on line .3 of the file COBCAT.PUB.SYS if
it is the only error or warning.
---------------------------------------------------------------------------------------
355 ERROR SECTION HEADER MUST PRECEDE PARAGRAPH.
MESSAGE
CAUSE The program has an improper construct, for example, it has a
section appearing in a PROCEDURE DIVISION starting with a
paragraph.
---------------------------------------------------------------------------------------
356 ERROR UNDEFINED DATA NAME !.
MESSAGE
CAUSE The referenced data name is undefined, replaced by TALLY.
---------------------------------------------------------------------------------------
357 ERROR DUPLICATE PARAGRAPH OR SECTION NAME: !.
MESSAGE
CAUSE A duplicate paragraph or section name appears.
---------------------------------------------------------------------------------------
358 ERROR ILLEGAL PARAGRAPH OR SECTION NAME !.
MESSAGE
CAUSE A paragraph or section name is illegal, for example, a signed
numeric literal.
---------------------------------------------------------------------------------------
359 ERROR UNDEFINED OR IMPROPER PROCEDURE NAME: !.
MESSAGE
CAUSE The referenced procedure name is undefined or improper, for
example, data name, signed numeric literal, or paragraph name where
section name is required. It could also occur if the paragraph
name does not appear in the current section and duplicate names
appear in other sections. No code is generated for the statement.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
360 ERROR ILLEGAL GO TO STATEMENT.
MESSAGE
CAUSE The GO TO statement is incorrect, for example, GO TO. appears, but
it is not the first statement in a paragraph, so it can't be
ALTERed.
---------------------------------------------------------------------------------------
361 ERROR ILLEGAL ALTER STATEMENT.
MESSAGE
CAUSE The ALTER statement references a non-existent paragraph name or it
does not reference an alterable GO TO.
---------------------------------------------------------------------------------------
362 ERROR ILLEGAL PERFORM TIMES COUNT.
MESSAGE
CAUSE The count must be an unsigned, positive integer.
---------------------------------------------------------------------------------------
363 ERROR RECURSIVE PERFORM.
MESSAGE
CAUSE The PERFORM statement is recursive through itself or its parent.
Use of recursive PERFORMs, although an ANSI extension in HP
COBOLII, is not recommended for upward compatibility to future HP
systems.
---------------------------------------------------------------------------------------
364 ERROR TOO MANY PARAMETERS.
MESSAGE
CAUSE A CALL statement or USING option contains too many parameters. The
maximum number of parameters on HP COBOL II/XL is 255. The maximum
number of parameters on HP COBOL II/V is 60.
---------------------------------------------------------------------------------------
365 ERROR ILLEGAL RELATIONAL COMPARE.
MESSAGE
CAUSE For example, comparing CONDITION-CODE against non-zero literal.
Also, CLASS test on the wrong category operands, or abbreviated
relation condition without subjects.
---------------------------------------------------------------------------------------
366 ERROR COMPOSITE OF OPERANDS TOO BIG.
MESSAGE
CAUSE The composite of operands for the statement is more than 18 digits.
---------------------------------------------------------------------------------------
367 ERROR ILLEGAL NUMERIC OPERAND !.
MESSAGE
CAUSE The operand is not an allowed numeric operand. The reference is
replaced with a reference to TALLY.
---------------------------------------------------------------------------------------
368 ERROR REFERENCE TO ! BY ! IS NOT UNIQUE.
MESSAGE
CAUSE The reference to the data item named requires further qualification
to be unique. Reference is used as a key or DEPENDING ON variable.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
369 ERROR ILLEGAL FUNCTION NAME !.
MESSAGE
CAUSE Mnemonic-name is ACCEPT/DISPLAY statements may only be SYSIN,
SYSOUT or CONSOLE. The function name is changed to SYSIN/OUT.
---------------------------------------------------------------------------------------
370 ERROR ILLEGAL STATEMENT FORMAT.
MESSAGE
CAUSE For example, PERFORM-VARYING statement with more than 7 levels.[REV
BEG] ACCEPT...ON INPUT ERROR without the FREE option. SEARCH ALL
with missing keys or referencing the same key twice.[REV END]
---------------------------------------------------------------------------------------
371 ERROR INTRINSIC ! NOT FOUND IN INTRINSIC FILE.
MESSAGE
CAUSE The system intrinsic file (SYSINTR.PUB.SYS) does not contain the
intrinsic.
---------------------------------------------------------------------------------------
372 ERROR INVALID RECORD NAME !.
MESSAGE
CAUSE The record name in this WRITE, REWRITE, or RELEASE statement is not
an "01" level item. No code is generated for this statement.
---------------------------------------------------------------------------------------
373 ERROR LINKAGE SECTION WITHOUT $CONTROL SUBPROGRAM/DYNAMIC; SUBPROGRAM
MESSAGE ASSUMED.
CAUSE A LINKAGE SECTION header was found in a program which does not
contain a $CONTROL command with either the SUBPROGRAM or DYNAMIC
parameter specified. Compilation continues as if $CONTROL
SUBPROGRAM has been specified.
---------------------------------------------------------------------------------------
374 ERROR UNINITIALIZED GO TO IN ! NOT REFERENCED IN AN ALTER STATEMENT.
MESSAGE
CAUSE A GO TO statement without a procedure name specified was found
without a corresponding ALTER statement.
---------------------------------------------------------------------------------------
377 ERROR CALL TO ! HAS A DIFFERENT PARAMETER COUNT THAN A PREVIOUS CALL.
MESSAGE
CAUSE The number of parameters listed in the USING phrase of a CALL
statement is different than a previous call to the same routine.
---------------------------------------------------------------------------------------
378 ERROR NON-UNIQUE INTERNAL (RBM) NAME !.
MESSAGE
CAUSE Two non-contiguous sections have the same internal name. The
internal name is formed by taking the first 12 non-hyphen
characters and adding the segment number and a single quote (').
For example, PROCESS-INPUT-RECORD SECTION 01 has the internal name
PROCESSINPUT01'.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
379 ERROR FROM/INTO IDENTIFIER ! SHARES SAME AREA AS RECORD-NAME.
MESSAGE
CAUSE The compiler has found a READ, REWRITE, RELEASE, RETURN, or WRITE
statement that refers to the same area as the record-name reserved
for the file.
---------------------------------------------------------------------------------------
380 ERROR INVALID USE OF A SEPARATOR CHARACTER.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
381 ERROR MISSING PERIOD IN COPY OR REPLACE STATEMENT.
MESSAGE
CAUSE The statement must be terminated by a period.
---------------------------------------------------------------------------------------
382 ERROR ERROR OR MISSING PROGRAM-ID PARAGRAPH.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
383 ERROR INCORRECT TABLE REFERENCE OR IMPROPER SUBSCRIPTING.
MESSAGE
CAUSE For example, illegal subscript is used, or table reference as
simple variable, or index-name does not belong to table-name or too
many or too few subscripts, or subscripts beyond 7.[REV BEG] This
will also occur when ALL is incorrectly used as a subscript.[REV
END]
---------------------------------------------------------------------------------------
384 ERROR CODEGEN INTERNAL ERROR IN !.
MESSAGE
CAUSE Some type of error occurred in the code generator of the compiler.
Errors 5000-7999 are substituted for !. For 5209 through 5211,
this is probably due to some type of user error on the COBOBJ file.
For 7204 through 7207, the object file, COBOBJ, is too small or
there was some kind of error writing to it, such as $NULL. For
errors 5213 through 5214, this is probably due to some type of user
error on the COBASSM file. For errors 5380 through 5383, 5980 or
5985 through 5990, this is probably some type of user error on the
COBOBJ file as a NMRL. For error 6305, and this occurs with
$OPTIMIZE, this is a compiler limitation; you must remove
$OPTIMIZE. For all other errors, see directions on line .3 of the
file COBCAT.PUB.SYS if it is the only error or warning.
---------------------------------------------------------------------------------------
387 ERROR ILLEGAL MOVE.
MESSAGE
CAUSE A move statement (or an implied move statement, for example, a
write from) has an illegal combination of "from" and "to" operands,
or the number of digits to move is greater than 31 on HP COBOL
II/XL or 28 on HP COBOL II/V.
---------------------------------------------------------------------------------------
388 ERROR ILLEGAL COMPARE.
MESSAGE
CAUSE The subject and object of a relational operator are incompatible.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
389 ERROR PARAMETER ! IS NOT ALIGNED PROPERLY.
MESSAGE
CAUSE A data item being passed by reference is required to be on a word
or half-word boundary. Use SYNC or move to 01/77. For CM, it is
16-bit word boundary only.
---------------------------------------------------------------------------------------
390 ERROR COMPILER ERROR: UNIMPLEMENTED CASE ! IN PROCEDURE !.
MESSAGE
CAUSE The compiler was not prepared for a given situation. See
directions on line .3 of the file COBCAT.PUB.SYS if it is the only
error or warning.
---------------------------------------------------------------------------------------
391 ERROR ENTRY STATEMENT NOT ALLOWED IN MAIN PROGRAM OR IN DECLARATIVES
MESSAGE SECTION.
CAUSE An ENTRY statement has been found in the Declaratives Section of
the program. The compiler ignores the ENTRY statement.
---------------------------------------------------------------------------------------
392 ERROR 'DELIMITER IN' OR 'COUNT IN' PHRASE WITHOUT 'DELIMITED BY' PHRASE.
MESSAGE
CAUSE The DELIMITER IN and COUNT IN phrases of the UNSTRING statement may
only be used if a DELIMITED BY phrase is specified.
---------------------------------------------------------------------------------------
393 ERROR DUPLICATE ENTRY POINT NAME !.
MESSAGE
CAUSE The same name is used in more than one ENTRY statement or the name
used in an ENTRY statement is the same as the name in the
PROGRAM-ID paragraph. Entry names are formed from the first[REV
BEG] 30 non-hyphen characters.[REV END]
---------------------------------------------------------------------------------------
394 ERROR !! EXPECTED FOR PARAMETER #!.
MESSAGE
CAUSE The parameter passed to the intrinsic cannot be mapped to the type
of parameter the intrinsic expects.
---------------------------------------------------------------------------------------
395 ERROR NUMBER OF SUBJECTS ! OBJECTS IN EVALUATE.
MESSAGE
CAUSE The number of objects on each WHEN must match the number of
subjects.
---------------------------------------------------------------------------------------
396 ERROR BEFORE/AFTER CLAUSE SPECIFIED TWICE IN INSPECT.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
397 ERROR ILLEGAL OBJECT OPERAND FOR EVALUATE SUBJECT.
MESSAGE
CAUSE The type of the object operand does not match its corresponding
subject. For example, comparing TRUE with an item instead of a
condition. Or comparing an item or literal with a condition.
---------------------------------------------------------------------------------------
398 ERROR ILLEGAL OPERAND ! FOR INITIALIZE.
MESSAGE
CAUSE The operand does not exist or is illegal.
---------------------------------------------------------------------------------------
399 ERROR REPLACING CATEGORY IS SPECIFIED TWICE IN INITIALIZE.
MESSAGE
CAUSE
---------------------------------------------------------------------------------------