List of Messages 0257 - 0378 [ COBOL/HP-UX Error Messages for the Series 700 and 800 ] MPE/iX 5.0 Documentation
COBOL/HP-UX Error Messages for the Series 700 and 800
List of Messages 0257 - 0378
0257 KEY data-name missing or already declared
* You have either not declared a data item specified in the
KEY phrase of an OCCURS clause, or you have declared it
twice.
* Declare the data item or remove the extra declaration.
0258 ASSIGN data-name data-name illegal
* You have specified an ASSIGN data-name in a SELECT ...
ASSIGN clause that is not unitary, that is, the data
definition contains an OCCURS clause.
* Edit your source code to ensure that the ASSIGN data item
does not include an OCCURS clause.
0259 Illegal report-name or bad RD clause
* You have defined a report-name that is either not unique
or which does not conform to the rules for user-defined
words. Alternatively, you have specified a clause in an
RD entry incorrectly.
* Check your Language Reference for the correct syntax of
an RD entry. Correct your program accordingly.
0260 Inconsistent page specification
* The values you have specified in the PAGE LIMIT clause
are not consistent; for example, the integer in the LAST
DETAIL phrase is smaller than the integer in the FIRST
DETAIL phrase.
* Check your Language Reference for the rules governing the
PAGE LIMIT clause. Correct your program accordingly.
0261 Only allowed in REPORT SECTION
* You have tried to specify syntax for a report outside the
Report Section of the Data Division.
* Check your Language Reference to see what syntax is
allowed in the Report Section. Delete the syntax in
error or relocate it in the report section.
0262 Not a CONTROL for this report
* The data-name in a TYPE CH or TYPE CF clause must appear
in the CONTROL clause of the associated RD entry. You
may have misspelled the data-name.
* Ensure that the correct data-name appears in both the
TYPE CF/CH and CONTROL clauses.
0263 Not allowed when PAGE not specified in RD
* You have either specified a TYPE PH or TYPE PF clause
without specifying a PAGE clause in the associated RD
entry, or you have specified an absolute line number in
the LINE NUMBER clause without specifying a PAGE clause
in the associated RD entry.
* Add a PAGE clause to the RD entry.
0264 Only one report group with this TYPE allowed per RD
* You have specified a duplicate of one of the TYPE clauses
(for example, you have specified two TYPE PF clauses);
only one clause of each type is allowed in a particular
RD entry.
* Delete the duplicate TYPE clause.
0265 Not allowed with this TYPE
* You are using a qualifier in a statement that either does
not allow any qualifiers, or that does not allow this
particular qualifier.
* Check your Language Reference for details of the
qualifiers allowed with this statement. Revise your
program.
0266 No TYPE specified
* All level 01 entries in the Report Section must have a
TYPE clause.
* Add a TYPE clause.
0267 LINE specification missing or inconsistent
* There are three possible causes of this message:
You can specify a NEXT PAGE clause only in the first LINE
clause of a report group description entry.
The absolute line numbers in the LINE clauses of a report
group description entry are not in ascending order.
You have not specified a LINE clause in a particular
report group description entry.
* Depending on the cause of this message, you should:
Delete the NEXT PAGE clause from any but the first LINE
clause.
Rearrange the LINE clauses so that absolute line numbers
are in ascending order.
Add a LINE clause.
0268 REPORT specified in more than one FD
* You have specified the same report name in more than one
FD.
* Delete the duplicate report name.
0269 Duplicate CONTROL field
* You have specified the same CONTROL field value in more
than one RD entry.
* Delete the duplicate CONTROL field value.
0270 COLUMN specification overlapping or not left to right
0271 Only allowed with DETAIL groups
* You can specify a GROUP INDICATE clause only with DETAIL
report groups.
* Delete the GROUP INDICATE clause.
0272 Only allowed with CONTROL FOOTING groups
* You can specify a SUM clause only in a control footing
report group.
* Delete the SUM clause.
0273 Non-elementary item has invalid qualifier, or PICTURE missing
* You have specified in a group item a qualifier that can
be used only in an elementary item. Possibly you
intended the item to be elementary but omitted the
PICTURE clause.
* Check your Language Reference for details of the correct
syntax. Delete the clause in error, or insert the
PICTURE clause.
0274 GROUP INDICATE without COLUMN
* You have specified the GROUP INDICATE clause but no
COLUMN clause in the same report group description.
* Include the COLUMN qualifier.
0275 NEXT GROUP not allowed with this group TYPE
* You have specified NEXT GROUP in a group with TYPE RF or
PH.
* Delete the NEXT GROUP clause.
0276 NEXT GROUP NEXT PAGE not allowed with this group TYPE
* You have specified NEXT GROUP or NEXT PAGE in a group
with TYPE PF.
* Delete the clause.
0277 LINE NEXT PAGE not allowed with this group TYPE
* You may specify the LINE NEXT PAGE clause only with a
group of TYPE CH, CF, or DE.
* Delete the LINE NEXT PAGE clause.
0278 RESET item is lower CONTROL level than group
* The control group on which a sum is reset must be at
either the same level as or a lower level than the sum.
* Check your Language Reference for the rules governing the
resetting of sums. Revise your code accordingly.
0279 Report line too long
* The syntax you have specified is attempting to create a
report line which is longer than the maximum allowed.
* Ensure that any report lines are not longer than the
permitted length.
0280 THRU phrase not allowed with DBCS field
* DBCS is Double Byte Character Set.
* Check your Language Reference for the rules governing the
use of DBCS. Revise your code accordingly.
0281 Illegal use of DBCS field
* DBCS is Double Byte Character Set.
* Check your Language Reference for the rules governing the
use of DBCS. Revise your code accordingly.
0282 Number of BLL cells incorrect
* You have submitted your program with the CICS directive
on, so your COBOL system has calculated the number of BLL
cells that should occur after the DFHCOMMAREA definition.
There should be a BLL cell for each 01 level data item in
the Linkage Section, plus one further BLL cell.
Additionally, if the 01 level Linkage Section data item
requires more than 4096 bytes, each 4096-byte block of
data requires one BLL cell.
* Check the number of BLL cells that are required for the
Linkage Section in your program as described above, and
ensure that you have defined the correct number of BLL
cells.
0283 An EXTERNAL file cannot be subject of SAME RECORD AREA clause
* You have specified a file in a SAME RECORD AREA clause in
your program that is specified as EXTERNAL in an FD
entry.
* Delete the EXTERNAL file in error from the SAME RECORD
AREA clause in your program.
0284 Not allowed in REPORT SECTION
* The syntax you have specified is not allowed in the
Report Section.
* Delete the syntax from the Report Section.
0285 First LINE NUMBER clause in PAGE FOOTING group is relative
0286 Not specified in CONTROL clause of RD
0287 Data record specified for Report file
0288 SYNC with USAGE IS INDEX
0289 SYNC at group level
0290 Index key key-name not alphanumeric
* You have specified a key item that is not alphanumeric,
in an index key clause where an alphanumeric key item is
expected.
* Specify an alphanumeric key item.
0291 Group FILLER
0292 SIGN different from that at group level
0293 REDEFINES of smaller item
0294 REDEFINES of larger item
0295 VALUE clause in FILE or LINKAGE SECTION. Clause processed as
comment
* You have specified a VALUE clause in either the File
Section or the Linkage Section where you should not have
specified one.
* You can delete the VALUE clause, although this has no
effect on your program.
0296 BLANK WHEN ZERO with zero suppression
0297 OCCURS .. DEPENDING clause without "integer TO". "1 TO"
assumed
0298 OCCURS at level 01 or 77
0299 FILLER omitted
* You have omitted the word FILLER.
* Add the word FILLER.
0300 LABEL RECORDS clause omitted
* You have omitted the heading LABEL RECORDS.
* Add the LABEL RECORDS clause.
0301 Unrecognized verb
* You have either used a verb in the Procedure Division of
your program that your COBOL system does not recognize as
a valid COBOL verb, or have misspelled a COBOL verb.
* Consult your Language Reference to see which verbs are
permitted in the COBOL language, and ensure that you have
spelled them correctly. Note that you may need to set a
language-enabling directive if the verb you require is
not part of your system's standard COBOL language.
0302 IF....ELSE or scope-delimiter mismatch
* There is an error in your coding of an IF statement in
the Procedure Division of your program. The two halves
of one IF statement do not match.
Alternatively, you have made an error in coding a
construct that uses one of the scope delimiters (for
example, END-ADD). There is a mismatch between the number
of scope delimiters and the statements whose scope they
delimit.
* Ensure you do not have more ELSE phrases than IF phrases.
Revise your source code.
0303 Operand has wrong data-type
* You have used a data item with the wrong data-type in one
of your statements. For example, you have used a
file-name instead of a record-name in a WRITE statement.
* Revise the relevant item.
0304 Procedure name not unique
* Two or more sections in the Procedure Division, or two or
more paragraphs in a section, of your program have the
same title.
* Rename or qualify the sections or paragraphs in error to
ensure uniqueness of reference.
0305 Procedure name same as data-name
* A paragraph in the Procedure Division of your program has
the same title as a data item declared in the Data
Division.
* Retitle either the paragraph or the relevant data item to
ensure uniqueness of reference.
0306 Entry name not unique
* You have used the same entry point name more than once in
your program. (This may be because the entry point name
is the same as the program-id.)
* Alter the entry name in error or qualify it.
0307 Wrong combination of data-types
* You are trying to manipulate data items which are not
compatible.
* Ensure that the data items are of the same type.
0308 Conditional statement not allowed in this context
* You have used a conditional statement (one which
specifies that the truth value of a condition is to be
determined at run-time) in the Procedure Division where
an imperative statement is expected.
* Replace the statement with one that begins with an
imperative verb and is followed by a specification of an
unconditional action to be taken at run-time.
0309 Malformed subscript
* You have probably specified two subscripts for a
one-dimensional table item.
* Revise your code to ensure that you do not specify more
than one subscript for a one-dimensional table item.
0310 ACCEPT/DISPLAY syntax incorrect
* You have either used invalid syntax with an ACCEPT or
DISPLAY statement, or have incorrectly coded that part of
your code containing the communications syntax. The most
likely cause of this message is that there is a spelling
mistake in your code.
* Correct the spelling mistake.
0311 Illegal syntax used with I-O verb
* Code following an I/O verb (for example READ or WRITE)
violates the rules of COBOL syntax.
* See your Language Reference for details on the usage of
the particular verb in your code which has caused this
error message. Revise your code accordingly.
0312 Invalid arithmetic statement
* An arithmetic statement which you have used in the
Procedure Division does not conform to the rules of COBOL
syntax. These statements must begin with an arithmetic
verb (for example SUBTRACT or DIVIDE), followed by the
relevant numeric literals or identifiers which the verb
will act upon when the program is executed. The
statement which you have specified is not a valid one.
* See your Language Reference for details of arithmetic
statements. Ensure that the one you wish to use conforms
to the relevant rules.
0313 Invalid arithmetic expression
* An arithmetic expression which you have used in the
Procedure Division is not a valid one.
* See your Language Reference for details of the COBOL
syntax for complicated mathematical tasks.
0314 Illegal key
* The key value in a file operation or in a SEARCH
statement is the wrong size.
* Check the key definition and correct the key value.
0315 Invalid conditional expression
* A conditional expression which you have specified in the
Procedure Division of your program does not conform to
the rules of COBOL syntax. These expressions, an example
of which is the statement immediately following an IF,
allow one of two following statements to be executed at
run-time depending on the truth value.
* See your Language Reference for details on the coding of
the particular statement which you have used. Revise
your code accordingly.
0316 Too many AFTERs in PERFORM statement
* A PERFORM statement can be followed only by six AFTER
phrases.
Your code exceeds this limit.
* Rewrite your code ensuring that no PERFORM statement has
more than six associated AFTER phrases.
0317 Incorrect structure of PROCEDURE DIVISION
* You have made a mistake in the coding of the Procedure
Division. For example, you may have forgotten one of the
section headers.
* Ensure that the Procedure Division follows a logical
order and that each section in it has its own header.
0318 File must have ACCESS SEQUENTIAL
* The file named in this statement must have sequential
access mode. A file's access mode is derived from its
SELECT statement; it is either implied by the file's
organization or specified by its ACCESS MODE clause.
* Change the access mode of the file to sequential.
0319 Only index-names allowed with this format
* An index name is required at this point in the operation
you are attempting.
* Edit your source code to ensure that the name you have
specified is an index name.
0320 Too many operands in one statement
* A statement in the Procedure Division of your program
contains too many operands or individual operands that
are too lengthy.
* Reduce the number of operands, or shorten those operands
that are too lengthy.
0321 Only one GIVING file allowed
* You have specified more than one file name in the GIVING
phrase of a SORT or MERGE statement, where only one file
name is allowed.
* Delete any additional file names from the GIVING phrase.
0322 Cannot reference DEBUG-ITEM outside declaratives
* You have referred to your COBOL system-generated data
item DEBUG-ITEM in a procedure that is not in the
Declaratives section of your program's Procedure
Division. References to DEBUG-ITEM are only permitted in
the Declaratives section.
* Delete the reference to DEBUG-ITEM, or move it to the
Declaratives section.
0323 More than one USE procedure on same file
* You have associated two or more USE procedures with the
same file when you may associate only one.
* Delete the additional USE references.
0324 More than one USE procedure for same open mode
* You have associated two or more USE procedures with the
same file open mode when you may associate only one.
* Delete the additional USE references.
0325 Illegal combination of debugging procedures
* You have specified an invalid combination of USE FOR
DEBUGGING procedures in the Declaratives.
* Check your Language Reference for details of debugging
procedures. Correct the declaratives.
0326 Literal cannot be receiving field
* You have specified a literal value as the receiving field
in an operation involving an implicit or explicit move.
A receiving field must be a data item.
* Change the literal value to a reference to a data item.
0327 Index item not permitted
* You have named an index data item as the sending or
receiving field in a MOVE statement. This is not
permitted.
* Move the value into a nonindex data item and use this
data item in the MOVE statement.
0328 Not allowed with OPTIONAL file
0329 WHEN phrase missing from SEARCH statement
* You have specified a SEARCH statement with no WHEN
phrase. You must specify at least one WHEN phrase in a
SEARCH statement.
* Add a WHEN phrase to the SEARCH statement.
0330 Not a record name
* You must specify the name of a file record in this
context (as defined in an FD entry in the file section).
You have probably misspelled a valid record name.
* Correct the reference so that it is a reference to a file
record.
0331 Program is nested - must compile with NESTCALL directive
* Your program contains one or more nested programs.
* Specify the NESTCALL directive when you submit your
program to the COBOL system.
0332 AFTER phrase not allowed with in-line perform
* You cannot specify an AFTER phrase in an in-line PERFORM
statement.
* Delete the AFTER phrase.
0333 Not an alterable paragraph
* The paragraph you have named in an ALTER statement is not
an ALTERable paragraph. An ALTERable paragraph must
consist of a single sentence containing only a single GO
TO statement (without a DEPENDING phrase).
* Change the reference in the ALTER statement to refer to a
paragraph that is ALTERable, or edit the named paragraph
so that it is an ALTERable paragraph.
0334 Cannot follow WHEN OTHER
* The WHEN OTHER phrase, if specified, must be the last
phrase in an EVALUATE statement.
* Ensure any WHEN phrases precede the WHEN OTHER phrase.
0335 Selection object does not match selection subject
* There is a type mismatch between one of the selection
subjects in an EVALUATE statement and the corresponding
selection object.
* Check your Language Reference for the correct syntax of
EVALUATE. Correct the EVALUATE statement.
0336 Variable length group not allowed
* You cannot INITIALIZE a variable-length item.
* Delete the item name from the INITIALIZE statement.
0337 Cannot repeat same category
* You have repeated the same data class in the REPLACING
phrase of an INITIALIZE statement.
* Delete the repeated class from the INTIALIZE statement.
0338 REPORT not specified in an FD
* You have referred to a report for which there is no FD
entry in the Report Section. You may have forgotten to
specify the report entry, or you may have misspelled a
correct report name.
* Correct the report name or add the necessary report
definition to the Report Section.
0339 Not allowed with SEQUENTIAL files
* You have specified an operation that cannot be performed
on a file opened in sequential access mode.
* See your Language Reference for details of the operations
you can perform on sequential files.
0340 Not allowed with RANDOM ACCESS files
* You have specified an operation that cannot be performed
on a file opened in random access mode.
* See your Language Reference for details of the operations
you can perform on random access (relative or indexed
sequential) files.
0341 Not allowed with LINE SEQUENTIAL files
* You have specified an operation that cannot be performed
on a line sequential file.
* See your Language Reference for details of the operations
you can perform on line sequential files.
0342 Not allowed with LINAGE files
* You have performed an illegal operation on a file defined
with a LINAGE clause (for example, WRITE AFTER CO1).
* Delete the illegal operation or redefine the file without
a LINAGE clause.
0343 Can only be used within in-line PERFORM
0344 Should be level 01 or 77
* You have specified a data item that is not a level 01 or
level 77 data item where your COBOL system is expecting
the data item to be either one of these levels.
* Redefine the data item to be level 01 or level 77.
0345 USING parameter used twice in parameter list
* You have specified the same data item name twice in the
USING phrase of the Procedure Division header. All the
names in the USING phrase must be different.
* Delete the extra reference.
0346 Only one WHEN phrase allowed with SEARCH ALL
* You have specified two WHEN phrases in a SEARCH statement
using the ALL option. You can specify only one WHEN
phrase in this context.
* Delete the extra WHEN phrase.
0347 MERGE needs at least two USING files
* You have specified fewer than two file names in the USING
phrase of a MERGE statement.
* Ensure that there are at least two file names in the
USING phrase of the MERGE statement.
0348 Procedure name procedure-name undeclared, first used on line
line-number
* You have referred to a nonexistent paragraph or section.
You have probably misspelled a valid procedure name.
* Ensure that the procedure you have referred to exists and
that you have spelled it correctly.
0349 `LOCK' clause expected
* You have not specified the LOCK phrase with a READ
statement.
* Insert a LOCK phrase in the READ statement.
0350 Illegal use of `NO LOCK'
* You have used a READ statement with the NO LOCK phrase on
a file for which no record locking is required.
* Delete the NO LOCK phrase.
0351 `LOCK' clause specified for 'EXCLUSIVE' file
* You have specified a LOCK clause in a READ statement for
a file that you have already locked with an EXCLUSIVE
lock (in the FILE-CONTROL paragraph of your code).
* Record locking is impossible on a file which your run
unit has already locked with an EXCLUSIVE lock. To
ensure that the two LOCK entries are compatible, you will
have to either delete the LOCK entry in the relevant READ
statement, or alter the LOCK MODE IS entry in the
FILE-CONTROL paragraph.
0352 `KEPT' specified for file with single record locking
* This message applies only to multi-user syntax. You have
specified a WITH KEPT LOCK phrase in a READ statement
which accesses a file that does not support multiple
record locking.
* Either change the file-type or delete the WITH KEPT LOCK
phrase to ensure compatibility between the two entries.
0353 Cannot reference a report section item that is not a sum-counter
0354 Multiple receiving fields in MOVE CORRESPONDING
0355 Only `=' and `NOT =' allowed for pointer data-items
* You can use the operators = and NOT = only in comparisons
involving pointer data items.
* Correct the comparison.
0356 Not allowed with REPORT files
* You have attempted to perform a file operation (READ,
WRITE, REWRITE) on a file whose FD entry indicates that
it is a report.
* Delete the input-output statement.
0357 Screen is display-only
* You have named a screen in an ACCEPT statement that
contains only display fields.
* Make sure that you have named the correct screen.
0358 Missing comma
* COBOL syntax expects a comma at this point. Check your
Language Reference for the correct syntax.
* Add the missing comma.
0359 Mismatch of table dimensions
* There is a mismatch between the number of dimensions in a
data item in an ACCEPT/DISPLAY statement and the
corresponding screen section item.
* Make the two item definitions consistent.
0360 File must have ACCESS DYNAMIC
* You have specified an operation on a file that can be
performed only if the file has access mode DYNAMIC.
* Change the file control entry for the file so that it has
access mode DYNAMIC.
0361 Operation exceeds COMP subset
* Your program contains a statement that cannot be compiled
to comp subset instructions.
0362 data-name not declared for file or wrong type for CODE-SET
* The data-names you have specified in the CODE-SET clause
do not belong to a record in the file.
* Edit your source code so that the data-names in the
CODE-SET clause refer to a record in the file.
0363 data-name not in same record as first item in CODE-SET clause
* You have specified data-names in the CODE-SET clause that
belong to more than one record. All data-names specified
in this clause must belong to a single record in the
file.
* Edit your source code to delete one or more of the
CODE-SET data-names to ensure that all data-names belong
to only one record.
0364 data-name overlaps another item in CODE-SET clause
* One or more of the data-names specified in the CODE-SET
clause is redefined, or you may have specified the whole
record, rather than individual data-names contained in
that record, in the CODE-SET clause.
* Edit your source code so that the data-names in the
record are specified only once.
0365 Variable size table not last in group or subsidiary to OCCURS
* OCCURS DEPENDING ON item must be last item in a group.
* Restructure your data items so that the OCCURS DEPENDING
ON item is the last item in the group.
0366 Variable length delimiter not allowed
* You cannot use a reference modified item or a group
containing an OCCURS ... DEPENDING ON clause in this
context.
* Replace the reference modified item, or specify a valid
item in the OCCURS DEPENDING ON clause.
0367 Description of operand does not contain the INDEXED BY clause
* A SEARCH is not possible as the description of the
operand does not contain the INDEXED BY clause.
* Include an INDEXED BY clause in your operand description.
0368 Exception phrase inappropriate
* The specified exception is not appropriate with this
statement in the specified access mode. For example an
AT END has been specified with random access, or INVALID
KEY with sequential access.
0369 OPEN EXTEND on file with LINAGE clause
* OPEN EXTEND is not allowed on a file defined with a
LINAGE clause.
0370 Operand must be a table
* The operand used in this situation can only be a table.
* Revise your code so that the operand is a table.
0371 Data size is too large
* Your program's data size exceeds the maximum size
permitted.
* Redesign your program to include less data.
0372 Illegal use of SORT file
* You have specified a SORT file incorrectly.
* Check your Language Reference for the correct syntax.
0373 PICTURE string contains more than 18 numeric positions
* Your PICTURE string may contain a maximum of 18 numeric
positions.
* Change your PICTURE string so that it contains no more
than 18 numeric positions.
0374 Illegal use of floating-point item
* You have specified a floating-point item incorrectly.
* Do not use a floating-point item in this context.
0375 Literal includes repeated characters
0376 Table superordinate to operand is not indexed
0377 SORT table does not support complex OCCURS DEPENDING ON tables
0378 More than seven AFTER phrases
* You may include a maximum of seven AFTER phrases in a
PERFORM statement.
* Delete any extra AFTER phrases.
MPE/iX 5.0 Documentation