HP 3000 Manuals HP 3000 Manuals
List of Messages 0110 -0256
0110 ENVIRONMENT missing
* You have omitted the word ENVIRONMENT.
* Add the word ENVIRONMENT.
0111 CONFIGURATION missing
* You have omitted the word CONFIGURATION.
* Add the word CONFIGURATION.
0112 SOURCE-COMPUTER missing
* You have omitted the words SOURCE-COMPUTER.
* Add the words SOURCE-COMPUTER.
0113 SPECIAL-NAMES clause error
* You have not specified the SPECIAL-NAMES paragraph
correctly.
* Check your Language Reference for the correct format of
the SPECIAL-NAMES paragraph.
0114 OBJECT-COMPUTER missing
* You have omitted the words OBJECT-COMPUTER.
* Add the words OBJECT-COMPUTER.
0115 OBJECT-COMPUTER clause not recognized
* You have specified the OBJECT-COMPUTER paragraph
incorrectly.
* Check your Language Reference for the correct format of
the OBJECT-COMPUTER paragraph.
0116 Character specified twice in alphabet
* You have specified at least one character twice in the
ALPHABET clause. For example, you may have included a
character in a range and also specified it as a literal.
* Edit your source code so that the characters specified in
the ALPHABET clause are referenced only once.
0117 SWITCH clause error or system name/mnemonic name error
* There is an error in the coding of the SWITCH clause of
the SPECIAL-NAMES paragraph in the Environment Division
of your program.
* Refer to your Language Reference for details of the
correct syntax for this clause and revise your program
accordingly. Ensure that each condition named in this
clause is declared in the Data Division.
0118 COMMA expected
* You have omitted the word COMMA from the DECIMAL-POINT
clause.
* Add the word COMMA.
0119 CRT expected
* You have used a COBOL word or user-defined word where
your COBOL system expected the reserved word CRT.
* Edit your code so that the reserved word CRT is used.
0120 Illegal currency symbol
* The literal which you have specified in the CURRENCY SIGN
IS clause in the SPECIAL-NAMES paragraph of your program
is not one of those permitted under the rules of COBOL
syntax, or if it is then you have failed to enclose it in
quotation marks. The literal must be a single character,
not a digit, and cannot be any of the following, A B C D
L P R S V X Z * + - , . ; ( ) " / = or space (except in
ANS85 and VSC2 where L is valid).
* Change the literal to a permitted character and ensure
that it is enclosed in quotation marks.
0121 Cannot specify DYNAMIC or EXTERNAL with literal file-name
* You can specify DYNAMIC or EXTERNAL in the ASSIGN clause
of a file description entry only if the file name is
contained in a data item rather than given as a literal
file name.
* Redesign your program so that the file name is contained
in a data item.
0122 Cannot use Double Byte characters in alphabet or class
definition
* When defining an alphabet or class, you may not use
double-byte characters.
* Redesign your program so that your alphabet or class
definition does not include any double-byte characters.
0123 I-O-CONTROL missing
* You have omitted the heading I-O-CONTROL.
* Add the heading I-O-CONTROL.
0124 INPUT-OUTPUT missing
* You have omitted the heading INPUT-OUTPUT.
* Add the words INPUT-OUTPUT.
0125 FILE-CONTROL missing
* You have omitted the heading FILE-CONTROL.
* Add the heading FILE-CONTROL.
0126 ASSIGN missing
* You have used a SELECT clause to give a file a file-name
which the program will recognize, but you have failed to
use a corresponding ASSIGN clause to give the file an
implementor-name (the name which the system will
recognize).
* Insert the relevant ASSIGN clause after the SELECT
clause.
0127 [LINE] SEQUENTIAL, RELATIVE or INDEXED missing
* In the ORGANIZATION IS clause of the FILE-CONTROL
paragraph you have failed to specify the logical
structure your file is to take.
* Insert [LINE] SEQUENTIAL, INDEXED, or RELATIVE into this
clause depending on how you wish your records to be
stored and accessed in your file.
0128 ACCESS missing on indexed/relative file
* The format of this clause depends on the organization of
the data-file. If you have specified the ORGANIZATION
clause for a file as either INDEXED or RELATIVE you must
specify an ACCESS MODE clause for it, indicating which
mode you will use to access that file. If no mode is
specified, sequential access mode is assumed.
* Refer to your Language Reference for further details on
the use of this clause.
0129 Too many keys or key components
* The number of separate data items making up the record
key and alternate key fields of one indexed file is too
great.
* Simplify your program so you do not need so many keys, or
components of keys, to the file.
0130 Illegal ORGANIZATION/ACCESS/KEY combination
* If you have specified these clauses in your program, they
must be compatible, but in your program they are not.
* Details of permitted combinations can be found in your
Language Reference. Ensure that these clauses are
compatible.
0131 Unrecognized phrase in SELECT clause
* Your COBOL system has failed to accept part of your
SELECT clause. This message could be given if the
file-name which you have given in the SELECT clause does
not conform to the rules for the naming of COBOL files.
* Details of these can be found in your Language Reference,
as can a description of the correct coding of the SELECT
clause.
0132 Unable to validate contents of DBCS literals
* Your COBOL system is unable to check that the contents of
a DBCS literal are valid. If the contents are invalid,
the results will be unpredictable.
0133 SAME AREA clause syntax error
* This optional clause, by which you allow two or more
files to access the same central storage space, does not
conform to the relevant syntax rules.
* Refer to your Language Reference for a description of the
correct format for this clause.
0134 FILE SECTION missing
* You have omitted the heading FILE SECTION.
* Add the heading FILE SECTION.
0135 DATA DIVISION missing
* You have omitted the heading DATA DIVISION.
* Add the heading DATA DIVISION.
0136 Illegal use of phrase for National Language operation
* You have included one or more of the following COBOL
clauses in your program:
PROGRAM COLLATING SEQUENCE IS
ALPHABET IS
CURRENCY SIGN IS
DECIMAL-POINT IS COMMA
and you have submitted the program with the NLS (National
Language Support) directive on, which is not allowed.
* Either turn the NLS directive off, or edit your source
code to ensure none of the above clauses appear in the
program.
0137 Program collating sequence not defined
* You have included the PROGRAM COLLATING SEQUENCE clause
within the OBJECT-COMPUTER paragraph of your code but
have failed to code a corresponding ALPHABET-NAME in the
SPECIAL-NAMES paragraph. Your code must contain an
ALPHABET-NAME clause if it has a PROGRAM COLLATING
SEQUENCE clause within it.
* Insert the necessary ALPHABET-NAME clause ensuring it has
the same user-defined name as that used in the SEQUENCE
entry. If you have specified both of these clauses in
your code but have still received this message then
ensure that you have used the same user-defined name in
each and that it is spelled the same in both. Correct
any spelling error your code may contain.
0138 `EXCLUSIVE', `AUTOMATIC' or `MANUAL' missing
* The LOCK MODE clause within the FILE-CONTROL paragraph of
the Environment Division does not contain one of the
words EXCLUSIVE, AUTOMATIC, or MANUAL, or if it does,
your COBOL system has failed to recognize the word,
perhaps owing to a spelling mistake. The LOCK MODE
clause controls access to files shared between a number
of users in a multi-user environment. Its form is
determined by the file-type with which it is used.
* Further details on the use of the LOCK MODE clause can be
found in your Language Reference.
0139 Illegal LOCK MODE/file type combination
* The format of the LOCK MODE clause depends on the file
type. You have specified a LOCK MODE clause which is
incompatible with the type of the specified file.
Non-shareable files must have lock mode EXCLUSIVE whilst
shareable files may have lock mode AUTOMATIC or MANUAL.
* Refer to your Language Reference for further details on
the use of this clause.
0140 For indexed file, PASSWORD phrase must follow KEY
* For an indexed sequential file description entry, any
PASSWORD phrase must immediately follow the KEY phrase.
* Edit your program so that the PASSWORD phrase immediately
follows the KEY phrase.
0141 File name appears in more than one SAME clause of same type
* A file may appear in only one SAME AREA or SAME RECORD
AREA clause.
* Revise your program.
0142 Can only be used in nested program
* A clause you have specified is allowed only in a nested
program. For example, the COMMON clause, as defined by
ANSI.
* Revise your program.
0143 Unknown IDENTIFICATION DIVISION paragraph
* The paragraph header specified is not a legal paragraph
of the IDENTIFICATION DIVISION; at least, not in the
selected COBOL dialect.
* Revise your program or select another COBOL dialect.
0144 OCCURS DEPENDING subsidiary to OCCURS only allowed with ODOSLIDE
* You have a record containing OCCURS DEPENDING ON as part
of a record defined with OCCURS.
* Set the ODOSLIDE directive.
0199 LINE clause also specified in containing group
* The LINE clause cannot appear in an elementary item if
the containing group already contains a LINE clause.
0200 Empty paragraph
* Your paragraph contains no statements.
0201 Sort file cannot have ACCESS or ORGANIZATION clauses
* An SD file control entry cannot have ACCESS or
ORGANIZATION clauses, because the access mode and
organization of such files are fixed.
* Delete the clauses in error.
0202 Too many levels of OCCURS
* You have specified more than the permitted number of
OCCURS clauses in the definition of a table item.
* Check your Language Reference for details of how many
levels of OCCURS you can specify. Delete the excess
OCCURS clauses.
0203 CODE must be specified for all reports or no report
* You have specified the CODE clause in the definition of a
report. If you are defining more than one report for the
specified file, you must specify the CODE clause either
for all reports or for none of them for that file.
* Add CODE clauses to the other reports you have defined,
or ensure that no report definition contains a CODE
clause for that file.
0204 REDEFINES on incorrect field
* A REDEFINES clause must have the same level number as the
item it redefines.
* Change the level number in error.
0205 RECORD missing or has zero size
* You have declared a file using the SELECT statement
within the Environment Division of your program, but have
either failed to define it in a corresponding FD entry in
the Data division or have used a different file-name in
the FD entry, perhaps owing to a spelling mistake. If a
mismatch of the two occurs then the record associated
with the file does not exist although the necessary space
has been created for it.
* Add or revise the FD entry.
0206 01 or 77 level required
* The specified data item must have level number 01 or 77.
* Change the level number of the item to 01 or 77.
0207 FD, CD or SD qualification syntax error
* These source code entries describe the structure of a
specified file and take the form FD or CD or SD followed
by a file name and a description of the records in that
file. The file name must be the name of a file defined
in the FILE-CONTROL paragraph of your program.
* Refer to your Language Reference for details of the
format of this syntax.
0208 WORKING-STORAGE missing
* The words WORKING-STORAGE are missing from the relevant
section heading within the Data Division or, if present,
have not been recognized by your COBOL system. This may
be due to a spelling mistake or to their position in your
code.
* Refer to your Language Reference for details of how the
Data Division should be structured.
0209 PROCEDURE DIVISION missing or unknown statement
* The Procedure Division header is missing from your
program or, if present, your COBOL system has failed to
recognize it. This may be due to a spelling mistake or
you could have placed the header at the wrong place in
your code.
Alternatively, your code may contain a statement in the
Procedure Division that your COBOL system has failed to
recognize. This is probably because you have used a
reserved word but have spelled it incorrectly.
* Insert the header immediately after the last entry in the
Data Division.
Correct your spelling error.
0210 Unrecognized data description qualifier or '.' missing
* A qualifier (for example, JUST or COMP) is misspelled in
the description of a data-item.
Alternatively you have not placed the necessary period at
the end of a PICTURE clause.
* A list of possible qualifiers can be found in the
Language Reference. Check the spelling of the qualifier
in your code.
Add the period.
0211 PICTURE clause not compatible with qualifiers
* Your code contains a PICTURE clause that is qualified by
the wrong type of qualifier. For example, a data item
may not be defined as PIC XX USAGE COMP because it is an
alphanumeric PICTURE clause but the qualifier is numeric.
* Revise your code so that the PICTURE clause and its
qualifiers are of the same type.
0212 Illegal data item used with BLANK clause
* The BLANK WHEN ZERO clause can be used only as part of
the data description entry for data-items which are
numeric (those which contain a 9 in the PICTURE clause)
or numeric edited (ordinary edited data-items with
special characters added to allow the data-items to be
presented in a form which can be easily understood). You
have used this clause with a non-numeric data-item in
your source code or with a numeric data-item that
contains a 'P', 'S', or 'V'.
* Delete this clause or redefine the data item to be either
numeric or numeric edited, or remove the 'P', 'S', or 'V'
characters.
0213 Item is longer than USAGE allows or contains more than 18
numeric positions
* A PICTURE string defined in a PICTURE clause in your Data
Division exceeds the maximum permitted by your COBOL
system. Numeric data-items can be up to 18 characters in
length, numeric edited up to 512 characters and
alphanumeric up to eight megabytes.
* Revise the clause in error to lie within the relevant
range.
0214 VALUE too long for data item or has too many decimal positions
* The value you have specified in a VALUE clause is too
big, or has too many decimal places, to fit in the data
item. For example, a declaration such as PIC 99 VALUE
123, where 123 is too large to fit into the receiving
field without truncation.
* Alter your code so that the data item is large enough to
receive the value that is to be placed in it.
0215 VALUE in error or illegal for PICTURE type
* You may have made a mistake in the coding of a VALUE
clause in your program. For example, you have used a
numeric data item with a nonnumeric VALUE clause.
Alternatively, you have used a VALUE clause in an illegal
place, for example in conjunction with a data item which
has been redefined.
* Refer to your Language Reference for a full description
of the rules governing the use of the VALUE clause.
0216 Non-elementary item has JUSTIFIED or BLANK clause
* These clauses can be used in the data description entry
of the Data Division but must be used only with
elementary data items. Elementary data items are the
most basic subdivisions of a record as they are not
subdivided into higher level data items. You have used
one of these clauses in conjunction with a non-elementary
data item (that is, one which contains higher level data
items).
* Revise your program to ensure that these clauses appear
only with elementary data items.
0217 Preceding item at this level has zero length
* You have defined a data item but have failed to give it a
size, either by not using a PICTURE clause in conjunction
with it, or, if it is a group item, by failing to define
any elementary items to go with it. If you enter
something similar to:
01 my-data-item. 01 prog-data-item pic x.
you will receive this message after prog-data-item
because, although it is my-data-item that is in error,
the error is detected only when the next item at the same
level as the data-item in error is encountered.
* Add the necessary PICTURE clause or elementary items to
the level hierarchy.
0218 Illegal arithmetic operator
* You have specified an invalid operator in an arithmetic
expression.
* Check your Language Reference for details of valid
arithmetic operators and correct the expression.
0219 Illegal level number
* You have specified an illegal level number in a data
description entry.
* Check your Language Reference for details of how to
specify level numbers. Correct the level number.
0220 Literal type does not match data type
* You have specified a literal value that is incompatible
with the PICTURE clause of the associated data item.
* Make the literal value compatible with the data item.
0221 Data description qualifier inappropriate or repeated
* You have used a data description qualifier which is
incompatible with the associated PICTURE clause. For
example, you may have used a BLANK WHEN ZERO clause for a
PIC XX data item. This is illegal as the data item is
alphanumeric but the associated qualifier refers only to
numeric items.
Alternatively, you have used more than one PICTURE clause
to define a single data item when each data item should
have only one PICTURE clause associated with it.
* Revise the qualifier or the data type to ensure that they
are compatible.
Delete any extra PICTURE clause to leave only one for
that data item.
0222 REDEFINES data-name not declared
* You have not declared the data name which you have used
in conjunction with a REDEFINES clause.
* Ensure that the data name is declared in your Data
Description entry and that the relevant REDEFINES clause
is placed immediately after the data name which it
describes.
0223 Unknown USAGE
* You have specified an invalid USAGE qualifier in a data
description entry.
* Check your Language Reference for details of USAGE
qualifiers. Correct the USAGE qualifier. Note that this
COBOL system does not support USAGE COMP-1 or USAGE
COMP-2.
0224 SIGN must be LEADING or TRAILING
* This optional clause can be specified only for numeric
description entries which contain the character S in
their PICTURE clause. The key word SIGN must be followed
by either LEADING or TRAILING depending on the position
you wish the operational sign to take.
* Add one of these words.
0225 Level hierarchy wrong
* The structure of level numbers in a group data item is
incorrect.
* Check the hierarchy of the level numbers and correct it.
0226 Variable length group not unitary
* You cannot declare a variable-length group item within an
OCCURS clause.
* Make the group item fixed length.
0227 ZERO missing
* The BLANK clause must be followed by the word ZERO, ZEROS
or ZEROES.
* Delete any other word that you may have used in place of
ZERO and ensure that the clause contains no spelling
errors.
0228 Group VALUE truncated
* The value you have specified for a group item exceeds its
defined length.
* Redefine the length of the group item or the value.
0229 Incompatible qualifiers
* The qualifiers you have specified in the description of a
data item are not compatible.
* Check your Language Reference for the rules governing
qualifiers in data descriptions. Revise the data
description.
0230 PICTURE string has illegal precedence or illegal character
* You have used a character within a PICTURE clause that
your COBOL system does not recognize, or which is illegal
for that particular type of PICTURE string.
* A full list of permitted characters can be found in your
Language Reference. Alter the relevant PICTURE clause.
0231 INDEXED data-name missing or already declared
0232 Edited PICTURE string is too large
* A PICTURE string which you have defined for an edited or
numeric edited (one which presents numeric data items in
a more readable form, for example, with leading zeros
removed or with currency signs inserted) data item
exceeds the maximum permitted for your COBOL system.
Note that a string comprises 32 'slots', each containing
16 characters. If no two consecutive characters in the
string are the same, a new slot will be allocated to each
character. For example:
X(32)B(480)
will work, but:
XBXBXBXBXBXBXBXBXBXBXBXBXBXBXBXBX
will fail.
* Alter the format of the string so that it contains no
more than 32 groups of characters, each group holding up
to 16 identical, contiguous edit characters.
0233 Unknown data description qualifier data-name
* You have either used a reserved word as a data-name, or
used an invalid qualifier in a data description: this is
probably a misspelling of a valid qualifier.
* Correct the data description.
0234 DEPENDING missing
* You have defined a variable length table without
specifying the DEPENDING phrase that at run time allows
your COBOL system to determine the actual table size.
* Specify the DEPENDING phrase.
0235 Record < minimum size given in FD statement
0236 Record > maximum size given in FD statement
0237 Cannot have more than one initial CD
* Only one of the CD entries in the communications section
can have the INITIAL clause specified.
* Delete the INITIAL clauses from all but one of the CD
entries.
0238 RENAMES missing
* You have omitted the word RENAMES in the definition of a
level 66 data item.
* Add the word RENAMES.
0239 First data name does not precede second
* You have included the syntax data-name-1 RENAMES
data-name-2 THRU data-name-3 in your program, but the
data item you have specified for data-name-2 is declared
after the data item for data-name-3. This is not valid
COBOL syntax, as data-name-2 in a THRU clause must be
declared before data-name-3.
* Check that you have specified the THRU phrase correctly.
0240 Only allowed at 01 level
* You have used either the NEXT or TYPE clauses in a report
description entry, or the GLOBAL or EXTERNAL clauses in a
report file description entry, which is not an 01 level
item.
* Edit your source code to ensure that everywhere you have
used NEXT, TYPE, GLOBAL or EXTERNAL the clause applies to
an 01 level item.
0241 Only allowed in WORKING-STORAGE section
* The syntax indicated may be used only in the
Working-Storage Section.
* Edit your source code to ensure that the syntax appears
only in the Working-Storage Section.
0242 Only allowed in WORKING-STORAGE and FILE sections
* The syntax indicated is allowed only in the
Working-Storage Section or the FILE Section.
* Edit your source code to ensure that the syntax appears
only in the Working-Storage or FILE Sections.
0243 VALUE of group item must be non-numeric or figurative constant
* If you specify a VALUE clause for a group item, the value
in the clause must be either a non-numeric literal or a
figurative constant.
* Revise the value in the VALUE clause.
0244 FD missing for file file-name
* You have not made an FD entry for all the files named in
the FILE-CONTROL paragraph.
* Ensure that there is an FD entry for each file named in a
SELECT clause in the File-Control paragraph.
0245 DEPENDING ON item data-name missing or illegal
* You have not declared a data item named in the DEPENDING
phrase of an OCCURS clause.
* Add a declaration of the missing data item.
0246 KEY key-name missing or illegal
* You have not specified the RECORD KEY clause in the file
description of an indexed sequential file.
* Add the RECORD KEY clause to the file description.
0247 Index-name has been declared explicitly
* You have declared an index data item explicitly. The
item is declared implicitly by its appearance in an INDEX
phrase, so you have in effect declared the same item
twice.
* Delete the explicit declaration of the index data item.
0248 ISAM key key-name too long
* A data item that is to be used as an indexed sequential
file key is longer than the maximum length allowed for
such keys.
* Your COBOL System Reference contains a formula which you
can use to find out how long indexed sequential file keys
can be. Redefine the key accordingly.
0249 Alternate keys have same reference
* The two alternate keys you have defined for an indexed
sequential file overlap. Alternate keys must be
completely distinct from one another.
* Redefine the alternate keys so that they do not overlap,
or define them as split keys (which are allowed to
overlap).
0250 STATUS field data-name missing or illegal
* You have either not declared the data item specified in
the FILE STATUS clause of a file control entry, or you
have declared it incorrectly.
* Check your Language Reference for details of the correct
form of the FILE STATUS data item. Add or revise the
definition of the FILE STATUS data item.
0251 CURSOR field data-name missing or illegal
* You have either not declared the data item specified in
the CURSOR IS clause in the SPECIAL-NAMES paragraph, or
you have declared the item incorrectly.
* Check your Language Reference for the correct form of the
cursor data item. Add or revise the declaration of the
data item in the CURSOR IS clause.
0252 PASSWORD field data-name missing or illegal
* You have either not declared the data item specified in
the PASSWORD clause in a file description entry, or you
have declared the item incorrectly.
* Check your Language Reference for the correct form of the
password data item. Add or correct the declaration of
the data item in the PASSWORD clause.
0253 LABEL RECORD or DATA RECORD record-name missing or illegal
* You have either not declared the record item specified in
the LABEL RECORD or DATA RECORD clauses in a file
description entry, or you have declared the item
incorrectly.
* Check your Language Reference for the correct format of
the label record and data record item. Add or correct
the declaration of the record item in the LABEL RECORD or
DATA RECORD clause.
0254 'VALUE OF' field data-name missing or illegal
* You have either not declared one or more of the data
items named in the VALUE OF clause of an FD entry in the
file section, or you have declared such an item
incorrectly.
* Check your Language Reference for the correct format of
such data items. Add or correct the declaration of the
data item(s) in the VALUE OF clause.
0255 User name data-name same as special register
* You have declared a data item with the same name as one
of the special registers, which are data items that are
automatically declared by your COBOL system.
* Check your Language Reference for a list of the names of
these special registers. Alter the name of the data item
in error.
0256 Preceding record has zero length
* You have defined a file record with zero length. This is
probably due to errors in all of the elementary item
descriptions in the record definition.
* Correct the record description.