Makes permanent all the changes you made to relational and Oracle
       CODASYL DBMS databases since the most recent COMMIT or ROLLBACK
       statement or, if you have not performed a COMMIT or ROLLBACK,
       since the first database READY command.

       The COMMIT statement does not affect collections; collections
       are maintained. For Oracle CODASYL DBMS databases, the COMMIT
       statement performs a COMMIT RETAINING. For relational databases,
       the COMMIT statement starts a new transaction that gives you a
       new look at the database.

       When you have both relational and Oracle CODASYL DBMS databases
       readied, the COMMIT statement commits all Oracle CODASYL DBMS and
       relational databases, regardless of whether you made any changes
       to their data.

       Domains based on RMS files are not affected by the COMMIT
       statement.

       Format

         COMMIT

1  –  Arguments

    None.

2  –  Examples

       The following Oracle CODASYL DBMS example connects an employee
       named Hill to a part LA36 in the RESPONSIBLE_FOR set. The COMMIT
       statement makes this change permanent.

       DTR> FIND E IN EMPLOYEES WITH EMP_LAST_NAME = "HILL"
       DTR> SELECT 1
       DTR> FOR P IN PART WITH PART_DESC = "LA36"
       CON>   CONNECT P TO E.RESPONSIBLE_FOR
       DTR> COMMIT

       DTR>

       The following relational database example stores a record in
       the relation DEPARTMENTS. The COMMIT statement makes this change
       permanent:

       DTR> READY DATABASE PERSONNEL USING DEPARTMENTS WRITE
       DTR> STORE DEPARTMENTS
       Enter DEPARTMENT_CODE: SENG
       Enter DEPARTMENT_NAME: SOFTWARE ENGINEERING
       Enter MANAGER_ID: 87215
       DTR> COMMIT

       DTR>