HP 3000 Manuals HP 3000 Manuals
List of Messages (0734 - 1168)
0734 OO: FUNCTION skeleton cannot use RETURNING/GIVING parameter
parameter-name
* User-defined syntax FUNCTIONs cannot include the
RETURNING/GIVING parameter as parameter to the
function.
0735 OO: Invalid use skeleton verb
* You are trying to use a reserved word as the verb of
user-defined syntax definition.
* Choose a different verb.
0736 OO: FACTORY factory-name not declared
* factory-name is not declared as a FACTORY in the
SPECIAL-NAMES paragraph of a program. It's definition
might be required as a result of specified
inheritance.
* Include an appropriate FACTORY statement in the
SPECIAL-NAMES paragraph and resubmit.
0737 OO: Object types do not conform (type-1,type-2)
* You are trying an operation involving incompatible
types of OBJECT REFERENCEs, as defined by the
inheritance hierarchy. Such objects are said to be
non-conforming.
0738 OO: Use skeleton must contain SELF, OBJECT once
* User defined syntax definitions must contain SELF or
OBJECT exactly once.
0739 OO: Use skeleton includes OF, "(" after parameter. Might be
ambiguous.
* The use of "OF" or parentheses in user defined syntax
definitions can lead to ambiguities in parsing which
might give unexpected results. For example,
parentheses following a parameter might be interpreted
as subscripting.
0740 OO: Sorry, too many use skeletons to consider
* There is a limitation as to how many user defined
syntax definitions with the same verb or function name
can be considered at one time. For example, you have
many definitions of the same verb.
* Reduce the number of definitions of each verb, or
shorten those definitions.
0741 OO: Only allowed in an instance method
* You have tried to use syntax that is only permitted in
an instance method.
0742 OO: Implicit use of SELF only allowed in a METHOD
* INVOKE statements might omit the initial object
reference, and this implies an object reference of
SELF. This can only be done in a METHOD, not a
program.
0743 Expressions in SQL statements not affected by ARITHMETIC
directive
* Arithmetical expressions in SQL statements are
processed by the database engine and are therefore not
affected by the ARITHMETIC directive.
0744 BY VALUE not allowed in nested programs
* You have tried to pass a parameter BY VALUE when
calling a nested program.
1001 Character other than *, D, /, -, or $ found in column 7.
Blank assumed
* You might have mistyped one of the characters allowed
in column 7. Your COBOL system cannot interpret the
character in column 7, and has treated it as a space.
1002 Continuation character invalid at this point. Blank assumed
* You have placed a hyphen in column 7, though your
COBOL system is not expecting the syntax to be
continued at this point. The continuation character
is ignored.
1003 First character of a continued literal not a quote. Quote
assumed
* You have included a continuation character in column
7, but you have forgotten to start the continuation of
the literal with a quotation mark. Your COBOL system
assumes that the quotation mark is included.
1004 Continuation character expected. End of literal assumed
* The literal in the previous line of source code is not
delimited by quotation marks, so your COBOL system is
expecting a continuation character in column 7, and a
continuation of the literal. Your COBOL system has
assumed that you meant to end the literal on the
previous line.
1005 Name ends in hyphen. Processed as written
* You have used a hyphen as the last character in a
user-defined-name, which is against the rules of COBOL
syntax. Your COBOL system has accepted this as a
valid name, however, and has not changed the name in
any way.
1006 COBOL word contains more than 30 characters. Word truncated
* The name that you have specified is longer than 30
characters. Your COBOL system treats this as a name
consisting of the first 30 characters of your original
name.
1007 VALUE literal size size1 > data item size size2. Literal
truncated
* The literal you have specified in the VALUE clause is
too long to fit into the data item. Your COBOL system
inserts characters from the literal into the data
item, until the data item is full.
1008 DBCS literal must contain an even number of characters.
Literal truncated
* All Double Byte Character Set (DBCS) symbols are two
bytes (two characters) long. You have specified a
literal that consists of an odd number of characters.
Your COBOL system ignores the last, single character
of the literal.
1009 Closing delimiter for DBCS literal not found. Delimiter
assumed
* You have not included the quotation mark to show the
end of the Double Byte Character Set (DBCS) literal.
Your COBOL system has assumed that you intended to end
the literal at this point.
1010 Nonnumeric literal has length of zero. One SPACE assumed
* The alphabetic or alphanumeric literal you have
defined in your source code is empty, that is, you
have a pair of quotation marks with no character
between them. Your COBOL system has assumed that the
literal contains one space character.
1011 DBCS literal has length of zero. Length of one DBCS
character assumed
* The Double Byte Character Set (DBCS) literal you have
defined in your source code is empty, that is, you
have a pair of quotation marks with no DBCS character
between them. Your COBOL system has assumed that the
literal is two characters long, and that it has a
value of spaces.
1012 DIVISION missing or misspelled. DIVISION assumed
* You have omitted the word DIVISION from a Division
header, or you have spelled it incorrectly. Your
COBOL system has assumed that DIVISION is what was
meant.
1013 SECTION missing or misspelled. SECTION assumed
* You have omitted the word SECTION from a Section
header, or you have spelled it incorrectly. Your
COBOL system has assumed that SECTION is what was
meant.
1014 Period missing. Period assumed
* You have omitted a period in a place where one is
expected by the rules of COBOL syntax. Your COBOL
system has assumed the period is present.
1015 OCCURS integer-1 exceeds OCCURS integer-2. Zero is assumed
for integer-1
* You have included the OCCURS integer-1 TO integer-2
DEPENDING clause in your source code, but the value
given for integer-1 is greater than that for
integer-2, which is against the rules of COBOL syntax.
Your COBOL system has effectively changed the value of
integer-1 to 0.
1016 Expected SEPARATE before CHARACTER in SIGN clause. SEPARATE
assumed
* You have incorrectly coded the SIGN clause because you
have included the word CHARACTER, which is not
required, but you have omitted the required word
SEPARATE. Your COBOL system has assumed that you
intended the clause to be SIGN IS LEADING (or
TRAILING) SEPARATE CHARACTER.
1017 REDEFINES ignored for 01 level item in File or Communication
Section
* You have tried to REDEFINE a data item in the File or
Communication Section, but the data item is an 01
level item. Level 01 items for the same FD or CD
automatically redefine one another.
1018 VALUE clause not allowed here. Clause processed as comment
* You have tried to assign a value to a data item
defined in the File Section or the Linkage Section.
The VALUE clause is ignored.
1019 Unsigned numeric literal expected. Sign ignored
* You have specified a sign where one is not expected,
for example, you have used the AFTER ADVANCING +1 or
BEFORE ADVANCING -2 clause to the WRITE statement.
Your COBOL system ignores the sign, and treats the
digits as a positive value.
1020 Unsigned numeric field. Sign in VALUE clause ignored
* You have defined a numeric data item (that is, PIC 9)
and you have tried to assign a signed number as its
value. Your COBOL system ignores the sign you have
specified. Where you are trying to move a number with
a negative sign into a numeric field, the result is
not as expected.
1021 Slack bytes added in conversion of COMP-6 to COMP
* You are using a program converted from RM/COBOL that
contains a COMP-6 numeric data item which has been
converted to a COMP numeric data item. As a result of
this conversion, less data space might have been
allocated to the numeric data item and, therefore,
your COBOL system adds leading binary zeros to pad the
space, if required.
1022 Table item not subscripted or indexed. First occurrence
assumed
1023 WORKING-STORAGE SECTION expected. Start of Working-Storage
assumed
* Your program begins with an 01 level entry. It is
assumed that this is the first item of the
Working-Storage Section.
1024 VALUE clause literal does not conform to PICTURE. Changed to
spaces.
* A numeric value has been specified for a nonnumeric
data item. The data item is filled with spaces.
1025 MOVE edited field to edited field--treated as alphanumeric
move
* A move of one edited field to another is treated as an
alphanumeric move.
1026 Source literal is nonnumeric--substituting zero
* A MOVE statement is trying to MOVE a nonnumeric
literal to a numeric data item. This cannot be done.
To avoid undefined results, ZERO is moved to the
target data item.
1027 Literal is numeric--treated as nonnumeric
* A numeric literal is being used in relation to a
nonnumeric data item; for example, as the VALUE of an
88 level entry attached to a nonnumeric data item.
The literal is converted to an alphanumeric literal.
1028 Statement should not reference an alphabetic data item
* A statement would cause invalid data to be contained
in an alphabetic data item. Your COBOL system
executes the statement as written.
1029 A non-integer is being moved to an alphanumeric data item
* A MOVE statement is trying to move a noninteger item
to an alphanumeric data item. The decimal point is
ignored and all the digits moved as if they
constituted an integer.
1030 Cannot SORT or MERGE USING or GIVING two files with SAME AREA
* Two files specified in a SORT or MERGE statement are
defined as sharing the same area. The files are
allocated different areas.
1031 SORT file appears in more than one SAME SORT (-MERGE) AREA
clause
* A SORT file has been referenced in more than one SAME
SORT (-MERGE) AREA clause. The files are allocated
different areas.
1032 File-names illegally speciffied in same SAME RECORD AREA
clause
* Two files in a SORT or MERGE statement are defined as
sharing the same record area. The files are allocated
different record areas.
1033 File-names illegally specified in same SAME SORT (-MERGE)
AREA clause
* Two files in a SORT or MERGE statement are defined as
sharing the same sort (-merge) area. The files are
allocated different sort-merge areas.
1034 Source item is ALPHABETIC or ALPHANUMERIC-EDITED--treated as
alphanumeric
* You have moved either an alphabetic, alphabetic
justified, edited alphabetic or edited alphanumeric
field to a numeric display field. The source field
has been treated as though it were a numeric field.
1035 Key is not wholly contained within minimum record length
* The specified key is greater in length than the
minimum size of the record.
1036 Entry name illegal
1037 Data-name must be specified for an EXTERNAL record--EXTERNAL
ignored
1038 RECORD key or ALTERNATE key has same starting position as
another key
* The specified key has the same starting position in
the file's record as a previously defined key.
1039 Error in structure information. No structure diagram created
* You are trying to perform structure animation of a
program in which a PERFORM THRU statement performs
sections in the Declaratives.
* Normal animation can be performed, but not structure
animation.
1040 ALL not allowed here--ALL ignored
1041 Data item has zero size, or group not yet completed. Value
of 0 assumed
1042 A numeric item is being moved to an ALPHABETIC data item
1043 PERFORM might be recursive
1044 Load failure on SLOAD--STRUCT ignored
1045 Capacity of POINTER might be exceeded
1046 Host variable name might cause problems if not unique, even
if qualified
1047 Phrase ignored--unsuccessful chain will cause program
termination
1048 DBCS literal includes invalid data
1049 KEY clause not allowed with sequential READ--clause ignored
1050 Invalid condition in $IF
1051 Value evaluated left to right, differs from normal arithmetic
precedence
1052 ALL specified more than once--repeated occurrences ignored
* You have specified the word ALL more than once in an
ALL literal.
* We recommend that you remove any repetition of the
word ALL, although any further occurrences are
actually ignored.
1053 Multiple 01 level EXTERNAL records with same name--treated as
same record
1054 Variable length group redefines or is redefined
1055 Requested SQLSTDLVL incompatible with your version of DBM.
Directive ignored
* You have specified a directive which has no meaning on
your database manager
1056 CALL-CONVENTION does not match that specified in prototype
1057 REFERENCE/ CONTENT/ VALUE phrase does not match that
specified in prototype
1058 Number of parameters is greater than in prototype
1059 Parameter is not consistent with that defined in prototype
1060 Can only use DELIMITED with alphanumeric items
1061 Previous CALL has fewer parameters than corresponding
prototype
1062 Not allowed in EXTERNAL program
1063 EXTERNAL not allowed with INITIAL or COMMON
1064 Illegal use of literal
1065 OOPS: SELF only allowed in FACTORY program
1066 OOPS: SUPER not allowed--FACTORY has no INHERITING phrase
1067 OOPS: RETURNING phrase not allowed in METHOD
1068 OOPS: FACTORY-NAME factory-name missing in SPECIAL-NAMES
1069 Identifier in area A assumed procedure name. Period missing
before it
1070 OOPS: Incorrect structure of FACTORY program
1071 OOPS: Missing OBJECT-STORAGE SECTION, required for
inheritance
1072 OOPS: Not allowed in PROGRAM-ID. OBJECT
1073 Can only use LOCAL-STORAGE with PERFORM TYPE"MF".
PERFORM-TYPE"MF" assumed
1074 OOPS: INVOKE data-item not yet supported by OOPS run-time
1075 Invalid combination of RECORD and RECORDING MODE clauses
1076 Reference modified length should not be > 8191 at run-time
1077 Host variable name longer than permitted by database
engine--truncated
1079 Positive integer expected, positive integer assumed
* You have used a negative integer where a positive
integer was expected. Your COBOL system has ignored
the negative sign.
1080 Odd number of hexadecimal digits
* Hexadecimal constants should be specified in pairs.
The constant contains an odd number of characters and
a leading zero has been assumed.
1081 More than 255 BLL Cells
* You have exceeded the limit of 255 BLL cells in your
Linkage Section.
1082 Source line is too long
* You have coded a source line greater than 80
characters. Your chosen flagging dialect does not
support this.
1101 No COBOL statement between periods
* You have placed one period immediately following
another period. This is not against the rules of
COBOL syntax, but it might indicate a fault in your
program, for example, you might have wanted to include
a line of source code here.
1102 Blank continuation source line. Line ignored
* You have placed a hyphen in column 7, but the rest of
the line contains no other code. The next line should
also contain a hyphen in column 7, to continue
correctly.
1103 Sequence number out of order or missing
1104 77 level item in File Section. Processed as 01 level
* You have assigned a level of 77 to a data item in the
File Section, which is against the rules of COBOL
syntax. Your COBOL system assumes that you had
intended to code this as an 01 level item, and
processes it as such.
1105 No CORRESPONDING items were found. Statement has no effect
* Your COBOL system found no matching data items for the
CORRESPONDING clause, so no intermediate code is
produced for this statement.
1106 ZERO value for BY operand. Statement processed as written
* You have used the BY operand with the verb PERFORM,
but the value you have specified for the increment is
zero. Your COBOL system produces code to execute this
statement, but the value is never incremented.
1107 Statement exceeds COMP subset
* The COMP subset code you have written could be
rewritten to execute more efficiently. Refer to your
COBOL User Guide for information on writing efficient
code.
1108 Signed numeric compared with group. Processed as
alphanumeric compare
* You have written your code so that a signed numeric
field is compared with a group item. Your COBOL
system has treated the signed numeric field as an
alphanumeric field for the comparison. There are no
problems with comparing a signed numeric field with an
elementary item.
1109 WITH DEBUGGING MODE not specified. Section ignored
* Your program includes the USE FOR DEBUGGING statement
in a section in the Declaratives of your Procedure
Division, but you have not included the WITH DEBUGGING
MODE clause in the Source-Computer paragraph. Your
COBOL system ignores all code in this section.
1110 First literal is greater than second. Processed as written
* In the ALPHABET clause the first literal that is
specified has a value greater than that of the second,
for example, P THRU D. Your COBOL system accepts this
as written, that is, the characters are processed in
reverse order.
1111 Boundary violation. Processed as written
* You have tried to access an item beyond the end of a
table. Your COBOL system generates code to access the
appropriate line of code beyond the end of the table,
but the result of this is undefined.
1112 Compatibility directive forcing non-standard behavior
* When the RM directive is set and an alphanumeric data
item is MOVEd to a numeric data item which is defined
as larger, your COBOL system adds space characters to
the front of the MOVEd data item. Under the RM/COBOL
system, however, leading zeros are added to the front
of the alphanumeric data item when it is MOVEd to a
numeric data item which is defined as larger.
1113 Imperative statement missing--CONTINUE assumed
* Your program contains a conditional statement which
has not been followed by an imperative statement.
Your COBOL system executes the code, but the result of
this might be undefined.
1114 Clause treated as documentary
* You have assigned more than one external file
reference to a SELECT...ASSIGN clause. Your COBOL
system accepts the first external file reference, but
treats all remaining external file references in that
clause as documentary.
1115 SAME AREA treated as SAME RECORD AREA
* You are using a program converted from DG Interactive
COBOL to this COBOL that contains a SAME AREA clause.
Your COBOL system has assumed that the SAME RECORD
AREA clause is what was meant.
1116 ACCEPT qualifier used with display-only field--qualifier
ignored
* The qualifier used with a DISPLAY only field, or in a
DISPLAY statement, can be used only with an ACCEPT. It
is ignored.
1117 Zero suppression follows floating insertion--treated as
floating insertion
* As an example, PIC ++Z.ZZ is treated as PIC +++.++.
1118 Index-name belongs to different table
* The index used to subscript a table item is not one
used in the INDEXED BY clause for this table. The
results are unpredictable.
1119 Record size size1 <minimum size given in FD statement size2
* The definition of a record following an FD clause is
smaller than the minimum size specified in the RECORD
CONTAINS phrase of that FD clause.
1120 Record size size1 >maximum size given in FD statement size2
* The definition of a record following an FD clause is
larger than the maximum size specified in the RECORD
CONTAINS phrase of that FD clause.
1121 VALUE in File, Linkage, or Local-Storgae Section--processed
as comment
* A data item in the File or Linkage Section cannot be
given a value. The VALUE clause specified is ignored.
1122 Period must be followed by a space
* In all cases a period must be followed by a space.
1123 Neither NAMED nor CHANGED specified. Will be treated as
formatted DISPLAY.
* An EXHIBIT statement has been used without the NAMED
or CHANGED phrase. The resulting display is formatted
by separating each item with a space.
1124 CALL parameter is literal (or LENGTH OF). BY CONTENT assumed
* You are using a program converted from RM/COBOL to
this COBOL that contains a CALL...USING literal
statement. Your COBOL system has assumed that
CALL...USING BY CONTENT literal is what was meant.
1125 Punctuation character not followed by a space. Assume space
* A punctuation character should be followed by a space.
1126 Punctuation character not preceded by a space. Assume space
* In accordance with ANS85 specifications, the
relational operator "=" is considered to be a COBOL
reserved word; all reserved words must be both
preceded and delimited by a space.
1127 Double-Byte character(s) might be corrupted by use of this
move
* This MOVE statement might cause a double-byte data
item to be corrupted by changing one byte of a
double-byte pair.
1128 No STOP RUN, GOBACK, or EXIT PROGRAM statements encountered
in source
* The source has no STOP RUN, GOBACK or EXIT PROGRAM
statement. The COBOL system automatically inserts an
EXIT statement followed by a STOP RUN statement
following the last line in the program. However, this
might not have the effect you desire.
1129 Statement cannot be reached
* The program flow prevents the statement flagged from
being executed.
1130 Prefix of filename treated as documentary
1131 Statement generated no executable code
* This error might be produced when, for example, an
INITIALIZE statement does not cause any code to be
created. It is an indication that the statement can
be removed from the program. If the error is ignored
the effect is as if the statement were removed.
1132 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 are unpredictable.
1133 SQL warning/ recoverable error
* The SQL processor generated a warning. Check your SQL
documentation for further details.
1134 Entry name has been converted following OS/VS COBOL and VS
COBOL II rules
* The name you specified for an ENTRY statement would be
altered if your source program were processed by an
IBM OS/VS COBOL or VS COBOL II compiler.
1135 No OPEN statement was found for file
1136 No CLOSE statement was found for file
1137 'KEPT' omitted for file with multiple record locking
* The KEPT phrase has not been included in your multiple
record locked file.
1138 Name truncated to characters -characters
1139 SQL host variable does not have suitable data-type
1140 SQL host variable not enclosed with BEGIN DECLARE and END
DECLARE
1141 Name longer than 8 characters
1142 Name includes characters that would be changed by OS/VS COBOL
and VS COBOL II
1143 Name includes characters that would be illegal for OS/VS
COBOL and VS COBOL II
1144 String will be null terminated when returned by SQL
1145 DUPLICATES phrase with keys generates slower sort; remove if
possible
1146 procedure-name lies in more than one PERFORM THRU range
1147 End precedes start in PERFORM procedure-name THRU
procedure-name
* The procedure-name after the THRU comes earlier in the
source program than the one before the THRU.
1148 Segmentation specified in nested program--ignored
1149 Operand data-name ambiguous in corresponding target
* In a MOVE, ADD or SUBTRACT CORRESPONDING, the sending
group contains an item, data-name, which is ambiguous
in the receiving group.
* Although data-name occurs in both the sending and
receiving groups, no relevant MOVE, ADD or SUBTRACT is
generated: this is in accordance with ANSI defined
behavior.
1150 Redefinition of internal floating-point item. Might not be
portable
1151 Forward overlapping move might produce unpredictable results
* You have specified a MOVE to a target whose starting
position is before the ending position of the source
data item.
1152 Comparison involving floating point data might not be
portable
1153 Some mainframe values for this data-type cannot be handled on
PC
1154 PC allows values for this data-type that cannot be handled on
mainframes
1155 Both PANVALET and LIBRARIAN specified--not mainframe
compatible
1156 BLOCK or LABEL clause in SD not allowed. Ignored
1157 JUSTIFIED specified on edited field
1158 CBL PROCESS *CBL or *CONTROL record encountered. Directives
ignored
1159 Portion of name following first "-" treated as documentary.
1160 Changes before first statement cannot be checked. Ignored
1161 Paragraph/section definition has changed. Ignored
1162 Attempt to define item as procedure. Ignored
1163 Animator restriction--can't check this statement
1164 Too many basic blocks for GNTANLZ"COUNT" to work, recompile
with GNTANLZ"COUNT"
1165 GIVING option treated as documentary
1166 BLANK WHEN ZERO phrase ignored
1167 Use of COMP-5 data-type
1168 COMP-5 redefinition
* You have redefined a COMP-5 data item. Porting your
code to other environments might produce inconsistent
results.