COBCH1121 - COBCH1140

• COBCH1121 VALUE in File, Linkage, or Local-Storage Section - processed as comment
  A data item in the File or Linkage Section cannot be given a value. The VALUE clause specified is ignored.
• COBCH1122 Period must be followed by a space
  In all cases a period must be followed by a space.
• COBCH1123 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.
• COBCH1124 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.
• COBCH1125 Punctuation character not followed by a space. Assume space
  A punctuation character should be followed by a space.
• COBCH1126 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.
• COBCH1127 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.
• COBCH1128 No STOP RUN, GOBACK, or EXIT PROGRAM statements encountered in source
  The source has no STOP RUN, GOBACK or EXIT PROGRAM statement. Your 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.
• COBCH1129 Statement cannot be reached
  The program flow prevents the statement flagged from being executed.
• COBCH1130 Prefix of filename treated as documentary
  
• COBCH1131 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.
• COBCH1132 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.
• COBCH1133 SQL warning/ recoverable error
  The SQL processor generated a warning. Check your SQL documentation for further details.
• COBCH1134 Entry name has been converted following OS/VS COBOL and VS COBOL II rules
  
• COBCH1135 No OPEN statement was found for file
  Related Topics
• COBCH1136 No CLOSE statement was found for file
  Related Topics
• COBCH1137 "KEPT" omitted for file with multiple record locking
  The KEPT phrase has not been included in your multiple record locked file.
• COBCH1138 Name truncated to characters characters
  
• COBCH1139 Operand operand does not have suitable data type
  

Parent topic: Messages COBCH1101 to COBCH1200

---

---