COBOL static code analysis

Filtered: 22 rules found

convention

Impact

Clean code attribute

Programs should begin with titles
Code Smell
Level 77 should not be used
Code Smell
SQL "OR" clauses testing equality on the same identifier should be replaced by an "IN" clause
Code Smell
A SQL "BETWEEN" clause should be used instead of "X>=Y AND X<=Z"
Code Smell
Data items should never be accessed using more than one "OF" clause
Code Smell
Data item declarations should be aligned
Code Smell
"TO" keywords should be aligned in a sequence of "MOVE" statements
Code Smell
Paragraphs should follow a naming convention
Code Smell
Procedures used in "PERFORM ... THRU ..." should share a naming convention
Code Smell
Paragraphs should be documented
Code Smell
Logical files should follow a naming convention
Code Smell
First level data items should follow a naming convention
Code Smell
File-Codes should comply with a naming convention
Code Smell
File names should comply with a naming convention
Code Smell
Program names should comply with a naming convention
Code Smell
Track lack of copyright and license headers
Code Smell
Ending words should be aligned with what they close
Code Smell
Sections should end with an empty paragraph
Code Smell
Sections should be documented
Code Smell
Paragraphs and statements should be indented consistently
Code Smell
Statements should be on separate lines
Code Smell
Tabulation characters should not be used
Code Smell

Ending words should be aligned with what they close

consistency - formatted

maintainability

Code Smell

Aligning opening and ending words of statements is critical to keep the code readable, especially when blocks contain nested statements.

For IF statements, this rule also checks the alignment of the ELSE word.

IF SOME-STATUS = 1
  DISPLAY something
      END-IF.  *> Noncompliant

IF SOME-STATUS = 1
  DISPLAY something
END-IF.

Available In: