IDMS COBOL Standard -- Version 1.0
09/03/97 

• Purpose
• Scope
• Documentation Requirements
• Overview
• Identification Division
• IDMS-Control Section
• Schema Section
• Standard Copies
• Data Base Sweeps
• FINISH Command
• DC RETURN Command
• Status Code Check

To establish uniform IDMS COBOL coding techniques. 

These coding standards apply to all IDMS COBOL programs. Exceptions may be made for vendor delivered programs. 

IDMS-DC: Programs must be entered into the system generation (SYSGEN) parameters by the DBA.

The IDMS COBOL standards are a supplement to the general COBOL Programming Standard. Both should be used and followed in order to ensure efficient coding and to simplify future program modification. These standards are applicable to both IDMS-DB and IDMS-DC unless otherwise noted. 

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. An IDMS-CONTROL section is required in the ENVIRONMENT DIVISION to establish operating mode, debug sequence, and variable storage allocation.
2. Protocol Statement
• Specify the DEBUG option in the protocol statement. This provides DML sequence numbers on each IDMS statement.
• IDMS-DC: The program must specify an IDMS-DC operating mode.
• IDMS-RECORDS Statement: Specify the MANUAL option of the IDMS-RECORDS statement so that records can be copied in as needed from the IDD.

Note: The "AUTOSTATUS" protocol handles status checking automatically but allows for the testing of only one non-zero return code.

 Do not use the global subschema(s) without approval of the DBA. If a global subschema is used, the DB statement must be followed by a comment:

     SUBSCHEMA APPROVED BY DATE

     IAZSS001 D.Maher 03/15/91

1. Use the "COPY IDMS SUBSCHEMA-CONTROL", "COPY IDMS SUBSCHEMA-CTRL", and the "COPY IDMS SUBSCHEMA-NAMES" statements to copy in appropriate subschema components.
2. Use the "COPY IDMS SUBSCHEMA-BINDS" statements. The DML preprocessor will insert appropriate record/map bind statements for records found in the programs DATA DIVISION.
3. Use the "COPY IDMS IDMS-STATUS" statement to utilize the standard abend process.

IDMS-DC: Do not use an area sweep in an IDMS-DC COBOL program.

 IDMS-DB: A "FINISH" should always be issued before terminating a program. Issue the FINISH as soon as database I/O is completed to free-up resources and to prevent potential time-outs.

 IDMS-DC: A "DC RETURN" should always be issued before terminating a program to return control to a program at the next higher level within a task.

 IDMS-STATUS (a routine that checks for non-zero database return codes) should be processed after every DML verb with the exception of "ROLLBACK". Errors can be immediately identified and linked to the appropriate verb.