COBCH1021 - COBCH1040

• COBCH1021 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.
• COBCH1022 Table item not subscripted or indexed. First occurrence assumed
  
• COBCH1023 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.
• COBCH1024 VALUE clause literal does not conform to PICTURE. Changed to blanks.
  A numeric value has been specified for a nonnumeric data item. The data item is filled with spaces.
• COBCH1025 MOVE edited field to edited field - treated as alphanumeric move
  A move of one edited field to another is treated as an alphanumeric move.
• COBCH1026 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.
• COBCH1027 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.
• COBCH1028 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.
• COBCH1029 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.
• COBCH1030 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.
• COBCH1031 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.
• COBCH1032 Filenames illegally specified 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.
• COBCH1033 Filenames 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.
• COBCH1034 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.
• COBCH1035 Key is not wholly contained within minimum record length
  The specified key is greater in length than the minimum size of the record.
• COBCH1036 Entry name illegal
  
• COBCH1037 Data-name must be specified for an EXTERNAL record - EXTERNAL ignored
  Related Topics
• COBCH1038 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.
• COBCH1039 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.
• COBCH1040 ALL not allowed here - ALL ignored
  Related Topics

Parent topic: Messages COBCH1001 to COBCH1100

---

---