COBOL Standard -- Version 1.0
07/02/97 

• Purpose
• Scope
• Overview
• Identification Division
• Working Storage Naming
• Linkage Section
• Procedure Division
• MODIDs
• Control Reports and Control Records
• Report Writer

To establish standards for developing and maintaining COBOL programs. 

This standard applies to all COBOL programs. Exceptions may be considered for vendor delivered programs. 

The Working Group for Standards has developed the following simple, straight-forward practices that are significant and that can be consistently applied.

The following, then, are implemented as standards, to be applied via the Quality Control process.

1. Each program must contain a modification history (change log) within the Identification Division.
2. Each entry in the modification history must contain the
• date of the modification
• the programmer's initials
• a brief description of the modification, and
• ENDEVOR Change Control ID (CCID).

1. Name and define all constants, numeric and literal, with meaningful names within working storage.
2. Each data element must have only one function or purpose. Do not re-use existing data elements simply because the PICTURE clause satisfies your need (i.e., don't use a date field defined as 9(6) as a calculation field for an unrelated item.)

1. Linkage items must have the same name and displacement in both calling and called programs.
2. The calling program's parameter size must exactly equal the size of the called program's Linkage Section.

1. Mainline batch modules must terminate execution with the STOP RUN or GOBACK statement.
2. Programs must use the standard catalogued procedures and copybooks that are available. Examples are system abend routines and system standard heading routines. Consult your Team Leader regarding procedures specific to your project.
3. Terminating errors in a program must cause an abend condition (use system abend routines).

See separate MODID Standard.

1. Program Name must be the first value of each run control record.
2. Each program must provide, at a minimum, a control report. The control report must show:
• the content of the run control records (so the options that are in effect are displayed)
• successful end-of-job message, OR
• abend conditions
• the key record information (account number, student number, edit errors, etc.) when an abend occurs

Use of Report Writer is prohibited.