ContentsIndexPreviousNext

C.2.9 Handling Transactions

The issuance of a COMMIT WORK database command terminates a transaction and makes all work permanent and accessible to other users. Acu4GL/Oracle runtime will issue this command automatically when no locks are held, but you can cause it to happen under other conditions by setting the value of the COMMIT-COUNT configuration file variable, which is discussed in detail in section C.3 "Configuration File Variables."

For direct control over the transaction logging facility in Oracle, use the transaction management features available with compiler version 2.4.0 and later. See Chapter 5 in Book 1, "User's Guide" of the ACUCOBOL-GT compiler documentation.

Important: You are now ready to use the sql.acu program. Go to the section in Chapter 2 on "Using the sql.acu Program" to learn about using this Acucorp-provided utility.
After you learn about and use this utility, you will then be ready to find out about preparing and compiling your COBOL program, followed by learning to use the demonstration program. All of this information can also be found in Chapter 2.